IssueTracker

Microsoft doc: https://support.microsoft.com/en-ca/help/2999226/update-for-universal-c-runtime-in-windows
Platform 28.0.2 readme: https://developer.android.com/studio/releases/platform-tools
"
Updated Windows requirements
The platform tools now depend on the Windows Universal C Runtime, which is usually installed by default via Windows Update. If you see errors mentioning missing DLLs, you may need to manually fetch and install the runtime package.
"

Note: see also b/129008605

Bug cleaning...what is the status on this? Looks like the depending bug is fixed.

Confirming the same issue on 2 different pebble 2HR connected to two different Pixel 2 phones.

Issues started with Android 10 install.
Forgetting the bluetooth device on the phone causes the device to confirm re-pair, then will work until the device gets disconnected for any reason (range, reboot, etc.)
Forgetting the phone from the device has no impact.
It appears tied to the phone's stored memory of the device.

Same here, also having problems with my pixelbuds connection

I am having the exact same problem with my Google Pixel 2 and Pebble 2HR.
Everything was fine till I upgraded to Android 10 with the over the air install.
I received a warning that the Rebble/Pebble software might be incompatible and I should try upgrading it. Of course there is no updated software.  

Tried rebooting both devices one after another
Turning off the Bluetooth on both devices at different times and turning them on at different points.

The only thing which seems to work is unpairing the pebble from the Pixel2 and repairing them again every few weeks.

Feedback

Same issue for me! Please fix!

Same issue, Pixel 2XL not connecting to pebble 2

Pixel 2 with a Pebble 2 not staying connected here either, but the Pebble Time Steel works fine.

Other information, on Android 9 I was having similar issues until approximately the February 2019 security update that mentioned bluetooth improvements which allowed my Pebble 2 to work perfectly until the Android 10 update.

Having the same issue with Pixel 2XL. Tried doing a factory reset on the Pebble 2 but it's not able to maintain the connection and update the firmware. Means it is effectively bricked right now.

Temp fix for factory resetting is to setup the Pebble on another Android device that's not on Android 10. Once it's setup, pair it to your phone again. That'll get you past setup and connected. You'll have to re-pair the watch whenever it disconnects though.

Same issue with a Pebble 2 and Pixel 2xl. Have to forget the bluetooth connection and then re-pair every time. Seems to be that the watch goes out of BT range, disconnects, and then refuses to reconnect once back in range.

Same issue here with OnePlus 6 running Android 10

Fortunately, I got my pebble to work but unfortunately I do not know what was critical for its revival.
I did a factory reset, went through connecting my watch to the pebble app for the update, then moved over to rebble.io

It took MANY attempts (30?) to actually complete the update as it would repeatedly fail, but it worked, finally.
After seemingly moving over to rebble.io, my pebble2 kept disconnecting.  A few hours later, without any action, I started getting notifications and it's been 18 hr. of normal use.  No idea why it started to work again, just happy it did.

Hope this is helpful and good luck!

Deletel all

Is there any update on this?

Same issue here with Pixel 2 after upgrading to Android 10 with Pebble 2 +HR.

Restarting the phone allows it to reconnect until the next time the watch goes out of range and then does not reconnect.  Rebooting the phone reconnects.

any update on this?

I've observed same issue but only when paired to two devices from the same company. Connection to any of them doesn't work, unles unpairing the second one. Connecting when one device is paired is smooth.

Same issue here with OnePlus 6T running Android 10

Please fix it.

My pebble 2 was keeping a solid connection on Android 10 until today. It's now dropping connection regularly. I have to Forget in Bluetooth and the then pair in the pebble app. Even this can be hit and miss. Sometimes a reboot or even a Bluetooth/network settings reset it required. Nokia 8.1 Android 10.

GUYS..!! I think I night have found the issue.. I turned off battery optimization of the Pebble App. Now it remains connected continuously.

Love.
Fan from India

#28, I'm afraid you are wrong #28. I already have battery optimization turned off. It's not a question of whether it will stay connected. The problem is that it won't RECONNECT after it does get disconnected. All you have to do to test is take your Pebble 2 out of range and bring it back in range. It won't reconnect automatically without forgetting the Pebble 2 on the Bluetooth settings in Android 10.    Android 9 does NOT have this issue.

I understand the issue completly friend. It's reconnecting in my case. Just check weather you have turned off appwise battery optimization. And remaining Permissions as it is. I haven't forget it single time. It reconnects automatically. ( I have android 9 though on MIUI 10)

#30 - you are following the wrong issue thread. If you notice the title of this issue, it specifically mentions "won't re-connect" and "Android 10." This is completely, in every way, different from continuously losing connection, then re-connecting, nor does this apply in any way possible to Android 9, even if it's MIUI 10, which is still unrelated.

Experiencing similar lack of reconnection issue when bluetooth on Pixel XL disconnects due to moving out of range with Pebble 2, workaround requires forgetting watch from phone and then reconnecting and accepting pair request on watch, without doing this phone remains stuck "Connecting to Pebble" indefinitely.

My pebble 2 reconnected to my Pixel 2xl automatically today for the first
time since updating to Android 10. Build number: QP1A.191005.007.A1.

Hopefully this is permanently fixed now!

On Tue, Oct 29, 2019 at 7:08 PM <buganizer-system@google.com> wrote:

Mine has disconnected earlier today, but would NOT re-connect as always. I'm curious what may be different... Of course, I'm using an Essential PH-1 on Android 10, not a Pixel. Did you notice anything update?

And the fact there has been ZERO Google activity on this issue worries me it still won't be addressed for the November update...

Nothing updated. And I've just run a few more tests... it's not
reconnecting anymore. Somehow a fluke? So strange. Sorry for the false
alarm.

Yeah, for some reason I doubt Google cares about compatibility issues with
a product for a business that's been out of business for a few years now.

On Thu, Oct 31, 2019 at 3:07 PM <buganizer-system@google.com> wrote:

I've been meaning to look into more issues that include Bluetooth devices having similar issues. It may be a Bluetooth LE problem, not a Pebble problem. If other LE devices are also having similar problems, I was hoping to somehow link them together since that's the common denominator here. But haven't had time to do that - for one, I'm not sure which devices only use Bluetooth LE other than the Pebble 2 in order to start searching. That should draw more attention and get the ball rolling.

I'm having similiar issue with BLE device. Can't reconnect when bonded to multiple (same model) devices. Could someone confirm if this problem is  dependant on the list of bonded devices, so does it occur if only Pebble is bonded to the phone? Even if it does occur with single bonded device there's still probability that it's the same issue, so Android 10 breaks reconnection to bonded BLE device. https://issuetracker.google.com/issues/144057796

Still having the issue on PH-1 post Nov update. Happens enough I've got a tasker task to forget the connection on disconnect.  (issue persists with tasker disabled)

IIRC, issue is with devices that are BLE exclusive.  Old pebble with both doesn't have the issue reconnecting.  

Any update on this issue?

Our Engineering team is still working on this issue. We will provide more updates as they become available.

Issue 144057796 (linked below) may be related to this issue
https://issuetracker.google.com/issues/144057796

gr, are you suggesting this is only for folks with 2 different pebbles? I DO have another listed that is the same model.  Can anyone confirm this bug that doesn't have 2 pebbles in their BT paired list?

Or is this related but occurring to pebbles despite users only having one?

Going to drop my second devices and test.  

I originally had two different model Pebbles that were paired. I removed
all of them and paired only the Pebble 2 and the issue persists.

On Fri, Nov 29, 2019, 4:45 PM <buganizer-system@google.com> wrote:

Can confirm it exists with a single pebble. It does appear specific to BTLE devices.

Hmm...  dropped my other devices with the same model.  Successfully re-paired after phone restart but not after loss of connection due to distance.  

If this is related, does not appear to be fixed by removing similar/duplicate models.  Also, unlike some of my speakers and other BT devices, pebble device name includes the unique device identifier.  

Does the issue appear on first reconnection try or does it vary?

I updated my Essential PH-1 to the December Android security patch. I did see it listed some bluetooth fixes for the Pixel 4, it seems at least some of that made its way to the PH-1, hopefully other devices as well. Here are my results since the December update:

1. I walked out of range of my phone, Pebble 2 disconnected from my phone. I walked back in range and it automatically re-connected. I tried this several times and it worked consistently. Previously, it would not re-connect.

2. I opened the Pebble Android app, then manually disconnected from my Pebble 2. When I looked back at my watch to see if it had lost connection, it DID NOT. Pebble 2 remained connected after manually disconnecting from the Pebble app. I repeated this a few times and waited for a minute or so as well. The Pebble 2 would not disconnect if you chose to disconnect from the Pebble app. Previously, this worked. You could disconnect from the Pebble app prior to the Dec. update.

3. I turned off Bluetooth. The Pebble 2 immediately disconnected. I then re-enabled Bluetooth, the Pebble 2 immediately re-connected. Previously, this did not work. The Pebble 2 would disconnect as expected, but would not re-connect.

4. I opened the Bluetooth settings and selected the Pebble 2 from my list of connected devices. I wanted to select "disconnect" from this menu to test, however my choices were "forget" or "connect." Since "connect" was a choice, I assumed my phone thought it was not connected. I tested this by playing music and opening the Music Boss app on my Pebble 2. It worked just fine. I did not press "connect" to see what would happen. I do not recall if "disconnect" appeared here as I never needed to use this. However, "connect" never worked previously - unsure if it works now.

It appears most of this issue is resolved, but #2 is a little concerning. Some of us have multiple Pebbles and I'm unsure yet how it will behave when trying to connect to a 2nd Pebble. Also, sometimes it's nice to not wear the Pebble and conserve battery by disconnecting it. As it stands right now, the only way to disconnect is to turn Bluetooth off. This won't be a long-term solution. I hope more progress is made. And thank you for your progress on this issue.

Mine also started working from few days, it wasn't reconnecting earlier,
but now it's working as never before. Don't know what did this but recently
I updated all the apps which was pending in my playstore for long time.

Regards
Pankaj Beladiya
Petronet LNG Ltd.
Dahej, Gujarat
9726081597

On Tue, 3 Dec, 2019, 20:42 , <buganizer-system@google.com> wrote:

In reply to #comment47

I just updated my Pixel2 XL to the December update as well 10(QQ1A.191205.008). I am getting the same functionality except that I can disconnect from the Pebble app and the watch disconnects as expected, and then reconnects if I tap reconnect from the app.

It is so nice to have my watch back!! Thank you so much for fixing this bug 👍

please enter support for androib 10 the ability not to lose contact with the Pebble watch!

I thought it was fixed for my Pixel 3 as well. I can walk away from the phone and back and it will reconnect, but then just randomly while the phone is close it will disconnect and refused to reconnect without forgetting the bluetooth device and going through the pair process again.

So it is better, but not back to the Android 9 experience for me yet.

I experienced the same bug as the OP with a pebble 2HR and Blackberry Key running Android 8.1.   I confirmed the same bug exists in two different pebble 2HR's.     Since there is no available update for the Blackberry 2HR, I am afraid I will have to live with the inconvenience of forgetting the phone and forgetting the watch each time I want to reconnect.   Have tried excluding the pebble app from power management.

Please help.

Edit: Blackberry Key 2.

Apologies, resubmitting with corrections and clarifications.  I experienced the same bug as the OP with a Pebble 2HR and Blackberry Key 2 running Android 8.1.   I confirmed the same bug exists when trying with two different Pebble 2HR's (i.e. it wasn't the Pebble).     Since there is no available update for the Blackberry Key 2, I am afraid I will have to live with the inconvenience of forgetting the phone and forgetting the watch each time I want to reconnect.   Have tried excluding the pebble app from power management.   Have tried using Gadgetbridge in place of Pebble App, and experienced same failure to reconnect.   Have tried Pebble 2HR paired with Samsung Galaxy S8 running 8.0, and reconnect works as expected.  So isolated the problem to the Blackberry Key 2 or Android OS.

te...@gmail.com in #52~#54,
Not only is this is an Android 10 bug (notice how Android 8.1 is NOT in the title), but why are you posting about something that won't be fixed in an old version of Android on an outdated device?

I'm waiting for confirmation of it being completely fixed before updating my Pixel 3.

I confirm, with an update from PIE 9 to android 10 of my 4 pebbles, the pebble 2hr model has major Bluetooth connectivity problems.
 The smartwatch loses the connection immediately

My Pebble Time doesn't have connection issue reported here but does have battery drain issue after Android 10. Is it related and with me posting a bug report here? I've seen other reports of battery issue on web but no issue tracker entry specific to that alone.

Can confirm same issue with my Pebble 2 HR. The watch will randomly lose BT connection. The only way of re-connecting is to upair the watch from my phone (Galaxy S10 running Android 10), turn off BT on the phone, forget the phone from the watch and then turn on BT on my phone and go through the re-pairing process.

If BT is turned off on either the phone or the watch, I will need to go through the above process as well.

Pebble 2, Pixel XL, running QP1A.191005.007.A3

I am experiencing the same failure to reconnect after the watch disconnects, but I have been able to force it to reconnect by flipping airplane mode on and off repeatedly, with and without going through safe mode. This only lasts until the next disconnection, but it's better than re-pairing for me.

Not a terribly important comment, but I can confirm the solution posted on #58 works everytime, immediately. Pebble 2 + Zenfone 6 (Android 10).

RE: #58

To simplify the steps, I've found that if I just FORGET my P2HR in the Bluetooth settings, then DISCONNECT it within the app, and then CONNECT, it will search and the watch will prompt me to PAIR.

This is on my Pixel running QP1A.191005.007.A3.

I'm also having the same problem I have a Pixel 3 and did the same thing on the Pixel 2 on Android 10. The Pebble 2 doesn't want to stay connected it will if you first time set up but then right afterwards it disconnects and stays that way.

Same here after upgrading Nokia 7 plus to Android 10. On top of that the connection is somehow unstable, I'm not able to update firmware because in the middle of the process the pebble gets disconnected.

Same issue here. My pebble won't connect again after I go out of range and come back in

Yes, me too. I hane a Huawei P30 with Android 10.  It doesn't work on it, but it works on a Xiaomi Note 7 with Androin 9. Please help us!
P.S. "From Russia with LOVE"

Me too, Huawei Mate 20 Pro with Android 10, BLE Connection Problem in 2 different Apps with 2 different BLE Devices ! Also a Pain in the Ass is to need a activated GPS Phone Sensor to be able to connect to an external Bluetooth GPS Sensor, maybee the Same with Barometric sensors ? I don´t want to activate a internal Sensor to use a external Sensor only to discharge the Phone faster !

Same issue on my Umidigi F2. Forgetting the watch fixes the problem most of the time (set up a Tasker script to do it automatically for me). However if it doesn't work removing the app, factory resetting the watch and restart is the only way to get it to work again

This does not happen on a note 9 running the android 10 february patch (or
since the android 10 update). Sorry i have been out the loop. No issues, i
can go far and lose connection with no issue.

I do not have android wear installed, since it always causes disconnect.

An issue i have noticed is connecting to a non ble device, then losing
connection causes my pebble to completly finish its battery within the day,
like it was connected to a non ble but full bluetooth.

Sorry for the typos, on mobile.

Thanks

On Fri, 20 Mar 2020, 20:24 , <buganizer-system@google.com> wrote:

Having issues reconnecting Pebble 2 HR to Nokia 6.1 on Android 10 after leaving range, and sometimes without leaving range.

Same issue for me, Pebble 2, Samsung A50 (SM-A505FM), Android 10.
Unpair and pair again (after dozen of unsuccessful tries) helps to transfer the data, but no notifications anymore.
So sad.

Having issues to pair my Pebble 2 to Motorola G7+ since Upgrade to Android 10. Nö notifications anymore and dozen trys to pair. :(

Exact same issue with a pebble 2hr and an android 10 oneplus 7t... It's obviously a BT LE issue as I have no problem with other standard BT devices.When will a fix be provided?

I confirm the same problem.  
Pebble 2 HR Watch
Galaxy S9 Phone running Android 10

Extra Notes:
The Pebble app, when installed on Android 10, gives a warning that the app was designed for an older version of Android and may not work correctly on my phone.  Given that I can pair to my old phone, but I can't pair my watch to my new phone, and the Android version is specifically sited, it appears that the problem is with the software and not the hardware.

Same watch has no problems connecting to Android 6 phone, or Android 9 phone.  Problem appears to be specific to Android 10.

I reset the watch.  I uninstall/reinstall the watch app on the phone.  I clear the bluetooth cache.  I cannot get the device to pair through the app.
Sometimes I can get the phone to recognize that the watch is there, but there is no data passing between the two and my Pebble is now useless...
unless I carry around one phone for work and one just for the Pebble.  I love the Pebble, it's still the best smart-watch, but carrying two phones because of a software regression...???

br...@gmail.com,
I believe this is unrelated to the Pebble app. This was a widespread problem in 2019 with the launch of Android 10, and throughout the betas previously. If I remember correctly, Google acknowledged it and pushed an update. At least for many Pixel owners and myself (Essential PH-1 at the time), it was fixed. I have seen many others have the same complaints with other manufacturers, however. I have also seen the same behavior on some newer smartwatches, such as the Fossil HR Hybrid series, which is made for Android 10.

Also, make sure you disable battery optmizations for the Pebble app. This will ensure it doesn't get closed in the background and remains running.

What a pain... Pebble is great! Let them live!

Same problem stills in 2022. Any news?

Pepple is dead 😭
Think you can close this thread.

Recommend upgrading to Android 12. I experienced the same issues with my previous Android 10 phone but have had no problems at all using a Pebble 2 with an Android 12 phone (Pixel 5).

Android 11 also works, just not Android 10. Pebble time with a Vivo spin-off.

still facing the same error in 2023

Try the new apk from Rebble.io - they were able to update the app to be compliant with Android 13, might help older Android versions too.