meshtastic
Text formatting on node screen appears broken on 2.3.0
Attached image is how 2.3.0 now looks... vs 2.2.24
2.3--> Broken...
2.2.24 ---> works.
Try uninstalling the app, then reinstalling it fresh. I am running the new (2.3.0) version of this app and do not experience this problem.
If the problem persists please provide your phone make and model, your Android operating system version, and anything else you think might be relevant.
This is due to a combination of display size setting and font size. Setting a smaller system font or display size in Android settings should make the coordinates of the nodes stay on one line. The info on the connected node, however, looks like it needs some layout/wrapping adjustment.
Some examples: largest display, larger (largest) font size
largest display, large font size:
Reinstalling the app, cleared cache, etc. all that didn't do anything. This is an Android 7.1.2 generic unbranded device that has worked fine with the Meshstastic Android app for over a year now. Device physical screen is 3 1/4 inches. The font size and screen size are just a notch above default size, (not largest) but this problem also happens with default font and screen size.
Given that 2.2.24 worked just fine but 2.3 doesn't, I would like to ask for help and if someone could please fix this? Thank you very much.
Same issue. Using portrait caused text down the screen. All OK until 2.3.0. OnePlus Open in front screen portrait (normal use). Tried all of the above. All OK previously.
Last night 2.3.2 was pushed out onto my Samsung A13 so I woke up this morning to find the above formatting issues. I presume 2.3.0 and 2.3.1 had not been pushed onto my phone when they were released as this is first time I've been aware of the issue. Format is displayed ok in Landscape mode so only an issue in portrait mode
Agreed. Formatted still broken in 2.3.2 portrait. Very annoying when half the screen is lost to one node.
I have no issues on my google pixel 8 pro however i am on the meshtastic beta tester
There's a chance it was fixed for us beta testers in https://github.com/meshtastic/Meshtastic-Android/commit/e3f495e35261e46ae818c7d32b96ee9a1bae472a
There's a chance it was fixed for us beta testers in e3f495e
It is not. I've tried and 2.3.2 has that fix, its not fixed.
A new beta has been pushed out sometime on the 2nd of April via Google Play Store, So now thats out how's everyone finding it now if on the Beta? @eldoctorcool ?
If you not on the beta Go to Google Play Store > search for meshtastic- > scroll down to Join beta and then give it 10 mins and there should be a update.
Remember you can always leave the beta at anytime.
Same here. No improvement.
I get my beta/alpha builds directly from github. So, whatever its latest on the app, I get to test.
