I havenāt posted much as a tester because I am still in the early stages and learning. But Iām having problems with the setup.
Current setup is two T-beamās v1, 7.6 bin.
Android App 0.7.75
Galaxy Tab A Android 9
ZTE Z812 Phone with Android 5.1
Tracfone Blu B100DL Phone Android 9
(Iāll admit to buying the throw-away phones in the past, just for the Android!)
Currently, the Galaxy Tab connects, and the app works sending messages as it should. Although, sometimes I have to reset the T-Beams to get them to appear as a connect option in the app.,
The ZTE, which always has connected with Bluetooth, still does, but the app doesnāt connect to the T-Beams anymore. It did connect and send and receive messages a few versions ago.
The Blu B100DL has, and still does connect with Bluetooth, but no versions of the android app have ever connected to the T-Beams with it. I thought maybe it was just the cheap phone setup.
Sorry, Iām not giving more technical details, but this is my limited experience.
Thanks for all your hard work on this amazing project!
re: the phones that donāt connect anymore
Can you try going to android settings / bluetooth / connected devices and choose to forget the meshtastic devices and then re-pair? I think this new load might cause the devices to pick new private keys.
hmm bummer. Would you mind doing the following with the ZTE and Tracfone?
Start the app, try to connect to the tbeam. Then wait about 30 seconds (to capture some tasty logs) then click āreport bugā? Tonight Iāll pull the bugs from the google console and open github issues. Is thomslik also your github name?
To connect to device cleared cache and data of the app.
Send/Recieve messages(try long messages) and possition- OK. Duplicating outgoing messages remained(only in app- first message after wakeup).
Tracfone Blu:
T-Beam v1,7.6 bin
Android App 0.7.76
Phone upgraded to 0.7.76.
Cleared cache and data of the app.
Unpaired everything in Bluetooth, Turned it off, then back on. Repaired device.
App just shows None as a choice, you havenāt paired a Meshtastic radioā¦
Reset T-Beam, same result. Turned it off and restarted, same.
Unpaired and repaired, same.
Sent another bug report.
ZTE Z812 Phone with Android 5.1
Same latest versions of app and bin.
Did all the same resets, etc.
App shows the connected T-beam, but itās greyed out and not selectable. Also shows the non paired T-Beam as a choice. It wasnāt connectable and later disappeared.
Sent another bug report.
Finally got the above ZTE working with the app after numerous clearing caches, bluetooth unpair, off/on repair. T-Beam reset combinations! Still trying with the Tracfone Blu.
oh yes @thomslik can you confirm you have location permission enabled for the app? (android settings /apps / meshtastic /permissions)
BLE scan (per android rules - because seeing BLE devices could āleakā location info to apps) requires the location access be allowed. I thought I had the app put up a warning message if this permission was missing but perhaps that notification is missing?
well - thank you because you taught us of a bug that I bet explains many of the BLE connection problem complaints. Tonight Iāll add a warning if you have location services turned off.
