-
-
Notifications
You must be signed in to change notification settings - Fork 938
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bluetooth Connection Lost Randomly, Requires Reset #527
Comments
Duplicate of #302 |
Several users reported that kind of issue (me included). In my case, I have to reset the watch ~ once a day. I do it in the morning so that BLE connectivity works the whole day. |
I would say it is not, as I experience my pinetime just dropping off with the phone in my pocket and the watch on my arm hanging around my house. Or when I leave my phone on the desk and I go to the other end of the house. |
With the 1.3.0 firmware and android+gadgetbridge, I can recreate this issue when the pinetime is taken out of bluetooth range from the phone. It seems as though the pinetime ends up in some kind of fail condition where it no longer attempts (or at least fails at) reconnecting. |
Just got my PineTime today and updated to the latest. I too am using gadgetbridge and it seems to lose its connection. Resetting restores connectivity. |
Might it be that this issue and #302 are connected but due to two different issues, one that GB is a bit flaky and the other where PineTime stops broadcasting? Once PineTime is not seen in my phone's Bluetooth connections the only option I have found is to reboot the PineTime, sometimes more than once. Is it possible to add into the settings the ability to turn Bluetooth on/off and force the service to restart without restarting the entire device? On/off may be nice for those looking to maximize battery and security and restarting the BLE broadcast may help with debugging. |
Yeah, got my PineTime yesterday, updated to the latest - doing the 8-second button hold and rebooting fixes it. I also updated the bootloader and recovery, but I don't think that's related. I use a Cosmo Communicator, and I disabled DuraSpeed on it, just in case that was the issue - same behaviour. At this stage, I suspect it is either GB or the firmware. I'm leaning towards the firmware.. it's almost like the BLE connection stops broadcasting, as my dev machine can't 'see' the PineTime at all. |
As an odd -- and not yet replicated -- data point, my watch managed to reconnect on it's own over a three to four day period. |
InfiniTime 1.5 and 1.6 brought many improvements the BLE connectivity. While I doubt those changes fix all connectivity issues, they certainly fix most of them. I think this one (BLE that stops working after a day) is one of them. I'll close this issue, but feel free to open a new one if you encounter another BLE issue on InfiniTime 1.6 (and if it doesn't exist yet). |
My phone will randomly disconnect from my
PineTime
and will not connect or advertise itself until it is reset.This seems to happen at random intervals and during a time when I am not actively using the watch. The shortest interval so far as been ~3 hrs and the longest has been ~2 days.
The strangest bit: I'm using
Gadget Bridge
as my companion app but when this issue occurs, I cannot re-connect until after I've connected + disconnected vianrfConnect
.The full "reset procedure" is:
PineTime
nrfConnect
and connect to thePineTime
PineTime
vianrfConnect
and closenrfConnect
Gadget Bridge
and connect to thePineTime
Has anyone else experienced this problem?
Phone: Pixel 2
InfiniTime Version:
1.2.0
and1.3.0
The text was updated successfully, but these errors were encountered: