Thanks larry - that did the trick. If curious hereās the stack trace. It seems like the brightness slider has an issue. One of us will fix it before 1.0:
Appreciate it.
This explains why the 0.7.7 beta was working until the upgrade to the latest 2 versions.
0.7.93 of the android app is up. Fixes a few rare autobugs and makes node movements update on the mapview (without having to switch away from map and back). If a couple of you kind souls could report back on if this app basically worked for you that would be great. Iām eager to release it more broadly. Full list of changes:
1 Like
Android: 0.7.93
Firmware: 0.7.10
Just did a quick test. Paired a couple t-beams. Sent some messages. Things seem good. No major crashes or anything.
2 Likes
Seems to work better than the last version. I had my map update, but it took almost 15+ minutes for the location to refresh. Might be nice if the map would update the location(s) whenever a message is received, or whenever the device āpingsā another node. Though, Iām not sure if the mapping service is limited on the number of updates/views which might make that troublesome.
1 Like
Android: 0.7.93
Firmware: 0.7.10 (upgraded OTA from 0.7.9)
upgraded through playstore, then loaded fw 0.7.9 on 2 tbeams and 2 ttgo-lora32-v2
paired to all four of them
managed to connect to one of either tbeam and lora32
updated them OTA to 0.7.10
iāll need a little time to connect to the other two but at first glance this looks great!
will keep you updated after my shortbreak this weekend.
thanks for all the good work!
Ps just filed small bug report when first connected to my 2nd tbeam I was OTAing it from 0.7.9to0.7.10. in the meantime wanted to send out a msg. Came up double on Android screen.2nd msg and further came up once.
Then went back to check on OTAupdate and even though button was blue but no more progress bar visible I didnāt manage to restart update. After quitting an restart of Meshtastic app OTAupdate went back okay.but I did not try to interrupt with msg anymore.
1 Like
Bin: 0.7.1
Android: 0.7.93
4 T-Beams v1.0
3 Android phones:
(1) ZTE Z812 w/Android 5.1
(2) BLU View1 B100DH w/Android 9
(3) Samsung Galaxy J3 Orbit w/Android 9
(4) 1 Galaxy Tab A 8" tablet w/Android 9
Cleared all app data and reset T-beams for a fresh start.
All phone pair with bluetooth no problem. All had GPS locks after a few minutes.
First try, all units could send a message to each other. After sleeping, Itās a different story.
Unit 1, ZTE, now continuosly shows the up arrow, device sleeping and shows the message Connected to radio, but it is sleeping.Itās not receiving or sending any texts. On the map view it only shows unit 1,2 and shows the generic 3f04 name for unit 3 and doesnāt show unit 4. The T-bean screen shows the other messages received. Bug report sent for Z812.
Unit 2 BLU sends and receives messages, and shows units 1,2 and 3 on the map and unit list, but not 4. Itās correct name shows on all the T-beams.
Unit 3 Galaxy J3 sends and receives messages, and they also show on the T-Beam screens, but T-Beams 1 and 4 show itās generic Mac name. It also shows units 1,2 and 3 on the map page and device list.
Unit 4 Galaxy Tab receives messages, upon sending, the messages only show on the T-Beam screens as from ??? on to, ?88 on one and with the correct name on the sending T-Beam.It shows all four units on the map and device list, but unit 3 name is the generic mac name. Bug report sent a Galaxy Tab A.
I hope this helps. Let me know if you need more info.
1 Like
I just received a pair of TTGO-LoRa32-V2.1 from Lilygo. I flashed them with firmware-ttgo-lora32-v2-US-0.7.10.bin. They boot up, connect to bluetooth, send and receive messages with the app, etc.
There is a problem if I Putty into them with a serial connection. The screen brightness function, along with the line, continuously cycles from low to high. The only way I have found to stop it while connected, is to reset it or power off/on. This, of course loses the serial connection. There is no way to toggle the screen as the only button on the board is reset. I also discovered the same results when using the Python API.
Is this a bug, or am I missing something? Iāve ordered some micro push buttons to add the needed screen toggle function. I understand GPIO0 to ground will do it. I just noticed that the TTGO-LoRa32-V2 is listed as supported but not the V2.1, so this may be an invalid issue.
galaxy a8 2017, 0.7.93, firmware 0.7.10
if the signal has arrived, the message has been delivered, the signal strength cannot be displayed on the dev. display as 0%(it is not correct)
the map was updated twice then stopped, although the program tab with the distance to the user after reconnecting the device was still updated. Messages between the two devices run well.
bug report recently sent
1 Like
Also noticed, attempting to the toggle the screen by pulling the GPIO0 low to ground does nothing, and the brightness function continues. After disconnecting from putty, everything is back to normal, including screen toggle.
galaxy a8 2017, 0.7.93, firmware 0.7.10 tbeam 433
Default setings
At a great distance(1300m), the display of the device: Signal 0% 68 min ago. But the message has been delivered.
when the device made a connection, the direction arrow began to show in the opposite direction (satellites are good)
bug report recently sent
1 Like
@lburrowes regarding #264 could you use the ESP32DownloadTool to completely erase the flash. After you have done that reflash your board and check if that fixes the problem?
Woot! 0.7.11 is up for alpha testers. One other feature of this release: almost all of code fixes and new features were by devs other than me 
. Please let me know how it works for you (Iāve been using it a couple of days here) and after a few of you bless, Iāll make it not alpha and include it in the next android release (for automatic updates of the firmware from the app)
THIS RELEASE IS FOR ALPHA TESTERS ONLY. If you donāt want an alpha test, download 0.7.10 instead.
Major changes since 0.7.10
- @professr made the device status screen even more pollished (bars for GPS signal quality). She also added ānorthā marker on the compass display - so you can see where the device thinks is north (estimated by your past movement) and fixed āautomatic location updatesā when you view a node on the device screen.
- @grcasanova - cleaned up namespace usage in the codebase
- @slavino added (working) support for the TBEAM0.7
- @mrvdb fixed drawing issues with sh1106 displays
https://github.com/meshtastic/Meshtastic-device/releases/tag/0.7.11
4 Likes
tbeam-EU433-0.7.11 and
ttgo-lora32-v1-EU433-0.7.11
They work wonderfully.
Itās a great idea to mark the north when the letter āNā in the right position climbs half the screen.
Maybe you should put it inside the circleā¦
0.7.11 after the firmware, the brightness slider increases cyclically. tbeam v1.0 and v1.1 433 firmware
returned version 0.7.10 back
1 Like
Tested 0.7.11 on four T-Beams V1.0 and two TTGO-LoRa32-V2.1ās. Everything is great! They all sent, received messages, showed positions and woke from sleep working properly. Really like the new display. I still have the earlier mentioned problem with the TTGO-LoRa32-V2.1ās with a serial connection, but thatās no biggie. Android app is still problematic after sleeping, on my old ZTE android 5.1 phone.
I thought there was a bug upon my first T-Beam flash, as the brightness slider immediately showed up cycling from low to high repeatedly. Then noticed I had flashed V .7 rather than the correct V1.0!
1 Like
Make sure youāre flashing The V1.0 bin and not the .7 which is the first T-beam to show in the list. I made this mistake on my first flash. Itās easy to do.
2 Likes
yep - slider going up repeatedly is because it thinks the button is pressed. the button is on a different GPIO on the two tbeams.
2 Likes
loaded 0.7.11 on a V0.7 Tbeam.
0.7.93 android version
unit reports 254% battery level on the android app.
Flashed Tbeam-US-0.7.11 with sh1106 display. Screen appeared to have issues, so I had to uncomment the SH1106 definition in configuration.h and build. Works fine after that. Incidentally, I accidentally flashed the uncommented SH1106 builds to one of my other boards that had a regular SSD1306 soldered to it, and it seems to be working fine.
Tested out on a walk today. Signal appeared higher than expected. Displayed 100% signal strength where I typically saw 50%-70% in the last version.
Really enjoying the compass integration. While it sometimes takes a few iterations of signal to correct big vector changes, it works rather well.
2 Likes