- Joined
- Apr 4, 2013
- Messages
- 661
So there are two Bluetooth "bugs" that in combinations can cause 99.9% of TouchDRO connection issues:I have had a similar issue on occasion but put it down to the 8 year old Chromebook that I'm using. It would generally happen when I walk away from the machine for a period of time. Hitting the Bluetooth button in the app before leaving the workshop for the day has almost completely eliminated the error.
When it has happened, it seems like monkeying with Bluetooth on the Chromebook (or rebooting) would fix it. Rarely I have had to power cycle the interface board. It seems like the Chromebook occasionally tries to connect to the board at the OS level and then the connection to the app doesn't work after that. It's also quite possible that I have no idea what I'm talking about![]()
1. Some Android images (it was much more common with some older lower-end tablets with Android 4.2.x - 4.4.2 os versions) had a bug where the "socket" was left hanging when the connection was lost (i.e. the "slave" device got turned off or went out of range).
2. Some Bluetooth firmware would not reset "congested" flag when the connection was dropped due to the "master" device going out of range, or going to sleep. When the same device was re-connected, the physical connection would be restored, but the "congested" flag remained set.
These things have to happen together, usually require either the tablet to left sitting with the screen on for weeks, the adapter being powered off at a wrong time while the app is running. The connection issue can be resolved by rebooting the adapter and the tablet. This is also pretty rare, I had two cases last year, and may be 4-5 total cases with the ESP32 based adapter. One was my good friend who lives 20 minutes away, and we spent weeks trying to reproduce this once we knew what to look for.
What Dan is experiencing sounds very different, and given that his adapter is "patient 0" out of couple thousand adapters with this firmware/chip revision, I'm very inclined to believe that this is a failure somewhere.
What you are describing smells very much like some flavor of #2, with potential sprinkling of #1. I don't have a lot of information/data with regards to running TouchDRO via Android VM on a Chrome OS. I test this for basic functionality on Google Pixel Slate and Pixel Chrome, but I suspect there is some variability between different Chromebook implementations, especially around power management.
Regards
Yuriy