v1.2.0b5

[JosephHewitt]

Beta Release version 1.2.0b5

This version is a beta and is not yet considered to be stable.

Changes since 1.2.0b4:

• Improve WiFi scanning speed: Speed up Side A WiFi scan #138
• Fix BLE count on LCD: Feature/b improvements #137
• Log/display if Side B crashes: Feature/b improvements #137
• Improve speed of hashing files: Improve file hash speed function #136
• Add advanced config to auto reset, and override GPS coordinates: Add auto reset and static lat/lon #134
• Improvements to WiGLE connection and upload speeds: Improve WiGLE CA load time #133 & Improve WiGLE upload speed, add back button to upload UI #128
• Add buttons to choose desired branch (stable/beta) to OTA update: Allow user to choose branch to OTA install #132
• Add WiGLE automatic upload functionality: Implement WiGLE auto upload #130
• Fix crash which occurred when accessing some files: Fix crash when accessing disallowed files #129
• Fix display rotation not working: Fix display rotation #126
• Stop prompting to download/install Side B updates multiple times: Don't download/install B firmware multiple times #125
• Allow logging networks over UART for PC-tethering, even without an SD card: Allow found networks to be sent over UART. #121

Important note for users on previous betas:

Many of the previous releases contained issues with OTA updates. This release has no known problems which can prevent OTA updates from being installed. It is recommended to install this update manually if you are experiencing problems updating. It is recommended to update both A and B together for this release.

Known issues

• You may be prompted to install an already-installed update for Side B if you installed it manually (with Arduino IDE, esptool, etc) or after performing a factory reset. This will stop happening once you install any update for Side B using the OTA function.

---

This discussion was created from the release v1.2.0b5.

[pejacoby]

I hit the issues updating Side B based on manual install of beta 4. The full process ran but then as Side B completed I got "Failure: Hash mismatch | Update failed". Side A worked fine and is now on b5.

I ran through the manual upload process and installed B.bin from the build.zip and still got the hash failure.

It would be good to add a pointer to the OTA process on the wiki https://wardriver.uk/ota to the Github page so the instructions on how to update via all methods are there for reference. I'll admit I didn't think of the Wiki immediately

[pejacoby]

Installing via esptool.py v4.6.1 using the instructions here.

[JosephHewitt]

Interesting that you got the hash mismatch error again then. That could indicate communication problems between the 2 ESP32s. It could be another bug but I didn't have this problem when I was testing the last 2 releases so unfortunately this might take some time to track down.

[pejacoby]

If it's relevant, my last four startups as seen in test.txt, note the bsh hash from side B is just "xxxxx"

_BOOT_1.2.0b5, ut=2390117, rr=1, id=3893376
_BOOT_1.2.0b5, ut=2391919, rr=1, id=3893376, bc=264, ep=1700415119, bsh=xxxxx
_BOOT_1.2.0b5, ut=2407728, rr=1, id=3893376, bc=265, ep=1700417804, bsh=xxxxx
_BOOT_1.2.0b5, ut=2403219, rr=1, id=3893376

[JosephHewitt]

The hash there is only updated after a successful OTA update so it won't change if you update manually.

[pejacoby]

I guessed as much, will keep trying as things move along. Managed to install B.ino on side A by accident, so proved that display code still works :)

If I attach the serial console to side B during updates will I see anything different? I could give that a try.