Category
Hardware Compatibility
Hardware
Other
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
Firmware Version
2.7.20.8858ec2
Description
its abaut T-Lora Pager.
not listed but supported under soft update.
bugs.
- device overheating while standing on the table and doing nothing. sometimes no sometimes yes. no rules.
- when the turn on via device menu bluetooth or wifi then they turn on, they turn on and everything is ok. and when turning off the device the device resets after that. !? in one direction when it turns on everything is ok and when it turns off the device resets.
- the following bug when you go under the "distance" menu select some node click on "node action settings" then some none, then key verification settings. and i chose that options. new popup windows appear to enter number keys. then when press reset button. after resetting the device when it turns on. the whole screen dims to at least 50% of the value that was previously set. and it is quite dark. when the screen turns off after about 30 seconds and I click the button to turn on. the screen is back to 100% backlight value. and acts as if nothing happened
-I have a random error that the device freezes by itself when I go to messages and select a user to send. It resets by itself. Also randomly.
-The view of the current time that is shown on the display when the analog is in the middle of the screen, the digital is moved to the right. It is not centered. preset is 24h display
-The next annoying problem is the wheel with which you move through the menus. Sometimes it catches immediately, sometimes it lags. There are literally no rules. Sometimes it takes 1-2 seconds to move to the next menu when choosing in the menu itself. Irritating. (I don't have this problem with mescore while it is installed, it catches normally, the same goes for stock firmware all works fine)
-Then when I add a user to favorites. And that user is "unmessegable" through favorites I can send a message to that user and they will receive it even though that user has it turned on. While I am connected to the mobile phone, that option works. The message cannot be sent. means via the device itself and the menu it is possible but not via the mobile phone while you are connected.
-the next bug is notifications. via the menu located on the device itself. it doesn't matter if I choose "all disabled" or just "dms only or "system only" it doesn't work. messages that come always ring the device, and vibrate. I have to turn off "external notifications" via android app "use i2S as buzzer" on my phone then all notifications with sound are turned off. but when I receive a message I feel the device vibrate slightly. there are literally no rules about setting the other checkboxes. only the last menu and the "Nag timeout in seconds 1 setting work". and it's really 1 sec or however long it's set. the rest doesn't work at all
the next problem is that the fonts are terribly small and tiny for me too, nothing is visible and nothing is legible.
the messages that are received are all in the same menu as the messages. which doesn't make sense if I received messages let them be separate which are public or from individuals or from private channels. it's totally unusable. and if I have 50 messages then the messages scroll by themselves from top to bottom and it's really slow and it can't be sped up in any way you have to wait for minutes until it gets to the last one. you literally can't see who wrote what and from which user or group. everything is in one chat. totally unusable.
and when a message is sent why does it count down the seconds next to the message? can't there be a check mark or a plus sign that it was delivered to someone or that someone forwarded it to someone that's enough or that bubble that it wasn't delivered. so users simply can't see conversations from another user because it's all together. it's mixed up.
furthermore if you don't have a plan to develop a graphic mesh UI for it then device. just give up full support for it. there's no point in supporting a platform that exists there and doesn't work. either make it work properly with the UI interface like other devices or abandon it completely, because it's so slow and full of bugs it makes no sense. the battery that charges in the morning at 8am-2pm is empty. the messages are too small. and don't even mention the other bugs. the most irritating thing is that it drains and overheats. well that's all other.
this is a list of bugs and it would be good to do something with it and fix it even if it doesn't already have a UI graphic interface that shares it with the same manufacturer. the competition has it and it works fine. so either leave it and delete the device from the list or do it properly.
I would be very happy to contribute but I have no idea about programming.
honestly if I had known it was so bad and clunky I wouldn't have spent the money and bought that device.
I thought it was supported and that it worked ok. Since I didn't find any bad comments or videos of it, that's why I bought it. It doesn't make sense that it's connected to my phone via Bluetooth, that's not the point and purpose of that device with that hardware.
Relevant log output
Category
Hardware Compatibility
Hardware
Other
Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?
Firmware Version
2.7.20.8858ec2
Description
its abaut T-Lora Pager.
not listed but supported under soft update.
bugs.
-I have a random error that the device freezes by itself when I go to messages and select a user to send. It resets by itself. Also randomly.
-The view of the current time that is shown on the display when the analog is in the middle of the screen, the digital is moved to the right. It is not centered. preset is 24h display
-The next annoying problem is the wheel with which you move through the menus. Sometimes it catches immediately, sometimes it lags. There are literally no rules. Sometimes it takes 1-2 seconds to move to the next menu when choosing in the menu itself. Irritating. (I don't have this problem with mescore while it is installed, it catches normally, the same goes for stock firmware all works fine)
-Then when I add a user to favorites. And that user is "unmessegable" through favorites I can send a message to that user and they will receive it even though that user has it turned on. While I am connected to the mobile phone, that option works. The message cannot be sent. means via the device itself and the menu it is possible but not via the mobile phone while you are connected.
-the next bug is notifications. via the menu located on the device itself. it doesn't matter if I choose "all disabled" or just "dms only or "system only" it doesn't work. messages that come always ring the device, and vibrate. I have to turn off "external notifications" via android app "use i2S as buzzer" on my phone then all notifications with sound are turned off. but when I receive a message I feel the device vibrate slightly. there are literally no rules about setting the other checkboxes. only the last menu and the "Nag timeout in seconds 1 setting work". and it's really 1 sec or however long it's set. the rest doesn't work at all
the next problem is that the fonts are terribly small and tiny for me too, nothing is visible and nothing is legible.
the messages that are received are all in the same menu as the messages. which doesn't make sense if I received messages let them be separate which are public or from individuals or from private channels. it's totally unusable. and if I have 50 messages then the messages scroll by themselves from top to bottom and it's really slow and it can't be sped up in any way you have to wait for minutes until it gets to the last one. you literally can't see who wrote what and from which user or group. everything is in one chat. totally unusable.
and when a message is sent why does it count down the seconds next to the message? can't there be a check mark or a plus sign that it was delivered to someone or that someone forwarded it to someone that's enough or that bubble that it wasn't delivered. so users simply can't see conversations from another user because it's all together. it's mixed up.
furthermore if you don't have a plan to develop a graphic mesh UI for it then device. just give up full support for it. there's no point in supporting a platform that exists there and doesn't work. either make it work properly with the UI interface like other devices or abandon it completely, because it's so slow and full of bugs it makes no sense. the battery that charges in the morning at 8am-2pm is empty. the messages are too small. and don't even mention the other bugs. the most irritating thing is that it drains and overheats. well that's all other.
this is a list of bugs and it would be good to do something with it and fix it even if it doesn't already have a UI graphic interface that shares it with the same manufacturer. the competition has it and it works fine. so either leave it and delete the device from the list or do it properly.
I would be very happy to contribute but I have no idea about programming.
honestly if I had known it was so bad and clunky I wouldn't have spent the money and bought that device.
I thought it was supported and that it worked ok. Since I didn't find any bad comments or videos of it, that's why I bought it. It doesn't make sense that it's connected to my phone via Bluetooth, that's not the point and purpose of that device with that hardware.
Relevant log output