This is a quick small release to fix a serious bug that can cause repeated device reboots - introduced in 0.6.7. If you’ve installed 0.6.7 you should update to this release, otherwise it isn’t critical.
I’m quite new to programming and find it easier to just flash prebuild firmware.
I searched hole Meshtastig github sources but can’t find any of flashable binaries.
Could some one please point me in the right direction. I’m currently using an older
TTGo board V1 I guess.
In addition to the new android app release (see message prior). 0.7.4 of the device code is out (thanks @dafeman for alpha testing).
Change nodenum and packet ID to be 32 bits (this should be backwards compatible with the apps, and this should be the last protocol change before 1.0). Longer nodenums enable the upcoming MQTT/internet gateway feature, longer packet IDs make the encryption more secure.
updated to 0.7.4 Looking good just a couple of minor things - On initial boot I got an assert failed, to do with ublox “ok” and it rebooted, not a big issue really, maybe gps responding to some spurious stuff during flashing.
When I sent 1st message after update it got very chatty seemed to loop and resulted in “Telling client we have new packet” up to 20 - like ping pong It may be nothing, or the app resending old stuff, new protocol? I updated for the first time in a few weeks and I used esptool directly to avoid having to redo the BT pairing and with self built firmware, just firmware.bin flashed to 0x10000, no erase, no device info - that may be an issue or not? So dont waste time looking at it unless others report it. It was not repeatable later, I send one message and see it sent and a reply - everything looks good all working fine logs attached in case they are of interest. https://pastebin.com/wc3YbcF3 https://pastebin.com/2eLU8Y2k
I think everyone should upgrade to this release (and also the latest android app).
Thank you to the alpha testers who tested an early version of these change. This release adds fixes based on their findings.
(finally) Fixed a super nasty bug in the bluetooth library code (that I didn’t even realize was there). Any packets sent from phone to device had a fair chance of corruption if they were larger than 20 bytes. With recent longer packets in the 0.7.x tree this manifested as “mysterious loss of bluetooth comms”.
Also - an an upstream change in the esp32-arduino libs introduced a bug that could cause bluetooth state corruption which manifested as inability to pair and repeated requirements to repair.
Other fixes:
Don’t leak BLE handles (found while debugging the big bug)
Fix out out packet errors if stress testing on big meshes
Fix a hang that could occur (rarely) white trying to enter sleep
0.7.8 device release notes (thank you alpha testers!)
A very important release for TBEAM users. Recent builds had a very high chance of failing to use the GPS correctly (bug #187).
Also fixes a bug in the esp32 arduino code where, if you disconnected bluetooth on the android side, the device would not reconnect to the phone for a very long time (many minutes)
Other fixes and improvements:
@zombodotcom fixed support for external GPSes on Heltec devices
@geeksville thanks a lot for this. I loaded new version today on my tbeams - no more gps bad message and all returned gps ok. I did try out the radio mesh. They all meshed well but the time between radio re-connection still seemed long. So I would have a message saying +70 minutes since last connection.
I am still trying to understand this - how to make a contact with the other radios? The centre button seems to be the way I can do this. But I am not clear whether this is the only way.
I am using the app version 7.80 - it found and paired with the radios well. But after pairing the radios would be lost and re-connection was very difficult. I had no messages about radio asleep but I never saw all my tbeam icons together on mapbox. I hit a report bug for this. Not too much time today to do more - I will try some more tests tomorrow.
0.7.10 device code released - thank you alpha testers for testing 0.7.9!
(This is basically 0.7.9 with a couple of small tweaks - so releasing more broadly)
Wow! This last week has so many more great commits from other devs (mostly @professr). I’m still working on my changes (one more BLE bug still exists I think in ardunio-esp32 but I’m still working on nailing it down - now that my house tasks are complete), but I wanted to get all this new goodness out there.
Highlights of this release:
@Professr added GPS DOP support, battery % full calculations, a very nice ‘polished looking’ node status display, and fixed utf8 characters (so Japanese etc… now looks better on the display) and changed display to be event driven.
@aHVzY2g improved the readme with a new 3D case and added the bluetooth name to the pairing screen
@rososaurus improved the readme with recommendations on different TBEAM versions
@zjwhitehead improved the compass display, so it is clearer when you don’t have a GPS lock vs the person you are trying to find doesn’t have one
@aHVzY2g and @professr worked together to add OLED brightness control (just longpress on the control button to change the display brightness)
0.7.11 is out of alpha-test - thank you to the brave early 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)
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
Thank you alpha testers for testing 0.9.1 - it sounds like it is pretty solid.
0.9.1 - Fix #266 (the ‘esp32 loses BLE pairing’ bug). Other benefits:
Bluetooth is 4x faster
substantially lower RAM and FLASH consumption (which makes plenty of IRAM space to leave wifi always enabled)
Eventually will allow the same BLE implementation on NRF52 and ESP32 targets - because NimBLE can run on both platforms
BLE ‘handles’ are assigned in a stable fashion, so eventually (after widely deployed) the nasty “force service refresh” hack needed on Android clients can be removed.
NOTE You will need to re-pair once after installing this new load (because it is keeping different device signing data than the old Bluedroid based implementation)
OTA firmware update to 0.9.01 (if you haven’t updated your device to 0.9.01 would you mind trying using the OTA to do it? - via the settings screen). You might need to manually press the reset button on the radio after the update (just this time - future updates won’t require this)
Fixed a few rare autobugs
Early this week (after I improve docs for @CycloMies) I’ll work on the items in the second column here:
0.9.01 android app Samsung Galaxy J3 Orbit
T-Beam V1 bin 0.8.2
Attempted OTA update, got Update failed message. Sent bug report.
Also got same update failed trying to update from 8.2 bin on tlora-v2-1-1.6.
Same results on both after clearing meshtastic data and resetiing both units.
Just got home from a long weekend away. Sorry I couldn’t test earlier.
Nice job!
Updated Android to 0.9.01 via appstore no problem.
On Android 7 phone updated a Tbeam and a Lora32v2 from 0.8.2 to 0.9.1 and both restarted without pushing resetbutton, then prompted to repair. All seems to work okay. BT OTA went 10x times faster and I had not to restart the app 15 at all!
My newer Android 10 phone did about double the time (15 minutes) to update each a Tbeam and a Lora32v2 from 0.8.2 to 0.9.1, but this must be related to its slower BT chip, as it’s a much cheaper phone.
Very cool screen gps & bat icons on the devices now !
all working fine logs attached in case they are of interest.
. 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)
after installing this new load (because it is keeping different device signing data than the old Bluedroid based implementation)