Fixed
Status Update
No update yet.
Comments
ra...@google.com
ra...@google.com
Because this feature request is over 3 years old and has five or fewer votes, I am closing it to better prioritize requests from developers. Please note that this request will still be used to inform future roadmap decisions.
If this is a critical issue, please comment here and I will triage the feature request. Thank you for your patience in addressing the backlog of issues and improving processes around feedback.
If this is a critical issue, please comment here and I will triage the feature request. Thank you for your patience in addressing the backlog of issues and improving processes around feedback.
le...@gmail.com
My team is experiencing the same issue. Hope to see an update on this. The HCI indicate 0x3e code for feature request LLCP packet. The sensor doesn't respond to it. What's interesting is that sensor reboot doesn't recover it, but phone Bluetooth restart OR phone reboot helps to recover for some time.
uw...@gmail.com
Hi. We are seeing the same issue when reconnecting to a Freestyle Libre 2 blood sugar sensor. This is a serious problem for diabetics that require to get alarms from this BLE device.
uw...@gmail.com
Issue also exists in Pixel 5 and Pixel 4a.
ma...@gmail.com
Confirmed on Pixel 4a running Android 13 as per above comment. Also with Freestyle Libre 2 device. To reiterate, this is a major concern for individuals who are using such devices to monitor blood glucose levels as alarms will not function if the connection has been lost.
ma...@gmail.com
Just to add, in my case, the potential severity of this issue left me with no choice but to roll back to Android 12 which completely eliminated the issue for me once more.
uw...@gmail.com
To add some more information about our app seeing the same (Diabox but also affects the offical Freestyle Libre 2 app, but you don't get logs from it).
This is an example of the app's log file trying o connect in a loop to reestablish the connection. This also drains battery:
15978,onStartCommand==========CONNECTING,2,ABBOTTBlue 2022-08-20 12:35:09,1660991709813
15979,Started 12:35,2,ABBOTTBlue 2022-08-20 12:35:09,1660991709820
15980,Attempting connection 12:35,2,ABBOTTBlue 2022-08-20 12:35:09,1660991709831
15981,checkConnection: Connection state: CONNECTING,2,ABBOTTBlue 2022-08-20 12:35:09,1660991709833
15982,"onConnectionStateChange called with status:133, state:DISCONNECTED， i2: 0",2,ABBOTTBlue 2022-08-20 12:35:14,1660991714796
15983,Sending disconnection,2,ABBOTTBlue 2022-08-20 12:35:14,1660991714809
15984,"onConnectionStateChange: mBluetoothGatt is not null, closing.",2,ABBOTTBlue 2022-08-20 12:35:14,1660991714813
15985,onConnectionStateChange: Disconnected from GATT server.,2,ABBOTTBlue 2022-08-20 12:35:14,1660991714819
15986,connect address: A4:7E:36:D7:69:EF status 133 disconnect 0,2,ABBOTTBlue 2022-08-20 12:35:14,1660991714824
15987,connect: going to connect to device at address: A4:7E:36:D7:69:EF : 0,2,ABBOTTBlue 2022-08-20 12:35:14,1660991714826
15988,connect: Trying to create a new connection.,2,ABBOTTBlue 2022-08-20 12:35:14,1660991714831
15989,onStartCommand==========CONNECTING,2,ABBOTTBlue 2022-08-20 12:35:39,1660991739852
15990,Started 12:35,2,ABBOTTBlue 2022-08-20 12:35:39,1660991739859
15991,Attempting connection 12:35,2,ABBOTTBlue 2022-08-20 12:35:39,1660991739863
15992,checkConnection: Connection state: CONNECTING,2,ABBOTTBlue 2022-08-20 12:35:39,1660991739865
15993,"onConnectionStateChange called with status:133, state:DISCONNECTED， i2: 0",2,ABBOTTBlue 2022-08-20 12:35:44,1660991744842
15994,Sending disconnection,2,ABBOTTBlue 2022-08-20 12:35:44,1660991744847
15995,"onConnectionStateChange: mBluetoothGatt is not null, closing.",2,ABBOTTBlue 2022-08-20 12:35:44,1660991744851
15996,onConnectionStateChange: Disconnected from GATT server.,2,ABBOTTBlue 2022-08-20 12:35:44,1660991744857
15997,connect address: A4:7E:36:D7:69:EF status 133 disconnect 0,2,ABBOTTBlue 2022-08-20 12:35:44,1660991744861
15998,connect: going to connect to device at address: A4:7E:36:D7:69:EF : 0,2,ABBOTTBlue 2022-08-20 12:35:44,1660991744863
15999,connect: Trying to create a new connection.,2,ABBOTTBlue 2022-08-20 12:35:44,1660991744866
16000,onStartCommand==========CONNECTING,2,ABBOTTBlue 2022-08-20 12:36:09,1660991769900
16001,Started 12:36,2,ABBOTTBlue 2022-08-20 12:36:09,1660991769909
16002,Attempting connection 12:36,2,ABBOTTBlue 2022-08-20 12:36:09,1660991769914
16003,checkConnection: Connection state: CONNECTING,2,ABBOTTBlue 2022-08-20 12:36:09,1660991769917
16004,"onConnectionStateChange called with status:133, state:DISCONNECTED， i2: 0",2,ABBOTTBlue 2022-08-20 12:36:14,1660991774879
16005,Sending disconnection,2,ABBOTTBlue 2022-08-20 12:36:14,1660991774883
16006,"onConnectionStateChange: mBluetoothGatt is not null, closing.",2,ABBOTTBlue 2022-08-20 12:36:14,1660991774899
16007,onConnectionStateChange: Disconnected from GATT server.,2,ABBOTTBlue 2022-08-20 12:36:14,1660991774903
16008,connect address: A4:7E:36:D7:69:EF status 133 disconnect 0,2,ABBOTTBlue 2022-08-20 12:36:14,1660991774909
16009,connect: going to connect to device at address: A4:7E:36:D7:69:EF : 0,2,ABBOTTBlue 2022-08-20 12:36:14,1660991774910
16010,connect: Trying to create a new connection.,2,ABBOTTBlue 2022-08-20 12:36:14,1660991774923
16011,Unbonding blukon at initialization====A4:7E:36:D7:69:EF,2,Blukon 2022-08-20 12:36:14,1660991774930
As shown by the reporter: The connection is started, but after exactly 4-5 seconds the GATT API reports onConnectionStateChange with status code 133. The app is seeing this as failure and then retrying forever until you restart bluetooth stack.
If the BLE device is out of reach, the whole code works as usual and you see a timeout after very long time (which is fine). But when device is reachable, the connection fails with status 133.
After a bluetooth stack restart all works well again:
17935,connect: going to connect to device at address: A4:7E:36:D7:69:EF : 0,2,ABBOTTBlue 2022-08-20 14:30:33,1660998633310
17936,connect: Trying to create a new connection.,2,ABBOTTBlue 2022-08-20 14:30:33,1660998633318
17937,"onConnectionStateChange called with status:0, state:CONNECTED， i2: 2",2,ABBOTTBlue 2022-08-20 14:30:43,1660998643749
17938,Attempting connection 14:30,2,ABBOTTBlue 2022-08-20 14:30:43,1660998643762
17939,checkConnection: Connection state: CONNECTED,2,ABBOTTBlue 2022-08-20 14:30:43,1660998643765
17940,Last Connected 14:30,2,ABBOTTBlue 2022-08-20 14:30:43,1660998643767
17941,write f17ec317b455e3b166d212e0enableTime==398687873===count==112,2,ABBOTTBlue 2022-08-20 14:30:44,1660998644512
17942,onCharacteristicWrite invoked: 0000f001-0000-1000-8000-00805f9b34fb code 0,2,ABBOTTBlue 2022-08-20 14:30:44,1660998644537
17943,12ad191016a18a62fb61fa6e8e54f5c978e86188,2,ABBOTTBlueBle 2022-08-20 14:30:44,1660998644560
17944,83f120ec7a49ff25148cb15e63e7ce7044c3,2,ABBOTTBlueBle 2022-08-20 14:30:44,1660998644563
17945,1bfdc867146cc15f,2,ABBOTTBlueBle 2022-08-20 14:30:44,1660998644566
17946,BLE Streaming packet received containing:12ad191016a18a62fb61fa6e8e54f5c978e8618883f120ec7a49ff25148cb15e63e7ce7044c31bfdc867146cc15f,2,ABBOTTBlue 2022-08-20 14:30:44,1660998644570
lp...@gmail.com
Same issue on Pixel 6 using smartwatches.
mb...@nosila.net
Same issue after updating P6P to 13 (TP1A.220624.021). Smartwatch connection was rock solid with P6P until this update. BT connection status cycles from "Connecting" to "Problem connecting. Turn device off & back on" every few seconds. Chews up battery on both P6P and smartwatch.
uw...@gmail.com
See also
ar...@fullpower.com
Same issue with Pixel 5A after updating to Android 13.
ms...@gmail.com
Same issue with Pixel 5 and Garmin Venu 2 Plus, Garmin Edge 1030 Plus after Android 13 upgrade. Had to re-set up Garmin Connect app profile several times. Then new bluetooth pixel pairing. Also drains battery quicker. Makes the smart watch pointless as no smart features usable with this.
mi...@gmail.com
Same issue also with a dexcom g6 and a Pixel 4a.this is really a major issue for a diabetic kid
co...@gmail.com
Same issue with Garmin forerunner 645 music and pixel 6a.
ma...@gmail.com
Also with Garmin 255 and Pixel 4a
be...@gmail.com
Same issue with Pixel 6 with android 13 after update. Another Pixel 6 in the house still on android 12 works flawlessly.
Interestingly, some devices are connecting, some are not.
BT earphones are working without issue.
My android head unit in the car no longer connects automatically.
One specific way I managed to force connection is that I use a device with Android 12 or below to connect first to the head unit, then while I disconnect the first device start to pair simultaneously my pixel device.
Needless to say it is an annoying faff to do every single time I start the car. Especially that android auto won't put my call on loudspeakers unless bluetooth connected.
I wonder if the new BLE tech interferes...?
I spotted in the developer options a greyed out toggle for Disabling BLE Audio. I wonder if this would already sort my issue, just need an access for that toggle.
At this point I am happy to sacrifice some battery life for it, honestly...
Interestingly, some devices are connecting, some are not.
BT earphones are working without issue.
My android head unit in the car no longer connects automatically.
One specific way I managed to force connection is that I use a device with Android 12 or below to connect first to the head unit, then while I disconnect the first device start to pair simultaneously my pixel device.
Needless to say it is an annoying faff to do every single time I start the car. Especially that android auto won't put my call on loudspeakers unless bluetooth connected.
I wonder if the new BLE tech interferes...?
I spotted in the developer options a greyed out toggle for Disabling BLE Audio. I wonder if this would already sort my issue, just need an access for that toggle.
At this point I am happy to sacrifice some battery life for it, honestly...
km...@gmail.com
Same issue with P6 Pro and TicWatch Pro 3 GPS. It occurs even when the device is 6 inches away, although I have not yet confirmed if the behavior will start when there is a lengthier distance first and then it's a point of no return sort of issue. I will experiment with distances to see if I can pinpoint when the issue starts.
jo...@gmail.com
Same issue. Most concern is the conection to my car. Doesn't connect automatically.
And wifi has not the best strength either. Miles away from Apple
And wifi has not the best strength either. Miles away from Apple
to...@gmail.com
Same issue on Pixel 6a recently upgraded to Android 13. My glucose monitor will not stay connected to alert me of high/low events - and the lows unfortunately for me seem to occur in the middle of the night when I wouldn't otherwise be aware of them. Also having issues with other bluetooth devices, but the CGM is the critical one.
mb...@nosila.net
FYI: I have to reboot my P6P sometimes to regain a somewhat "stable" connection to my smartwatch, otherwise the BT connection just flaps and drains battery on both devices - cycling BT off/on is not enough. The new BT software stack is broken :(
ad...@gmail.com
I tried factory resetting my watch, but that didn't fix it. This needs to be resolved ASAP. My galaxy watch 4 is useless, it just keeps draining battery.
jo...@gmail.com
We had a developer switch to enable the new BT stack optionally. Need a switch now to flip to the old stack for 'compatibility', at least until the new stack is more robust.
ma...@gmail.com
I’d like to report the issue as well. I have a Pixel 5 and have this issue with my Tesla phone key and Fitbit Sense.
be...@gmail.com
Same issue here with my Tesla phone key and Pixel 4 XL.
po...@gmail.com
Having to reboot heaps to get some devices to connect to Bluetooth. .hoping something to address the above helps me out .
ev...@gmail.com
This is effecting my Pixel 6 Pro with Bluetooth audio to multiple sets of headphones and my vehicle.
gr...@gmail.com
Same problem here with my Google Pixel 6 Pro and Tesla app supporting my Tesla Model 3 and Powerwalls, after updating to Android 13. After following steps advised by others in this post and by Tesla, I was finally able to reconnect after about a dozen tries. Sequence that worked for me:
1) Turn off VPN.
2) Delete app.
3) Restart Model 3 (long hold on two steering wheel rolling buttons).
4) Reinstall app on Pixel.
5) Then I was able to sign-in to Tesla app, re-pair my phone.
6) The phone key is working, but the Powerwall app information is not being updated on the phone app.
1) Turn off VPN.
2) Delete app.
3) Restart Model 3 (long hold on two steering wheel rolling buttons).
4) Reinstall app on Pixel.
5) Then I was able to sign-in to Tesla app, re-pair my phone.
6) The phone key is working, but the Powerwall app information is not being updated on the phone app.
bi...@gmail.com
Same issue on Pixel 4A 5G, impacting my ability to open and drive Tesla using app. Device reboot fixes for awhile, about 12 hour maybe. Almost got locked out of my car because of this (before I figured out need to reboot phone). Please fix ASAP!
ha...@gmail.com
I encountered the same issue on my Pixel 4A 5G. It consistently fails to reconnect to my Fitbit Sense once it got disconnected for a while. Device reboot temporarily fixes the problem, but having the need to restart everyday is a major inconvenience.
vi...@gmail.com
Can this be switched to P2?.
fi...@gmail.com
Seeing this on my Pixel 6 Pro. It keeps losing the ability to connect to my Pokemon Gotcha, and rebooting the phone very rarely provides a temporary fix. It seems to connect just fine to my car and to my Bluetooth speaker, but it just cannot maintain a reliable connection to the Gotcha. EXTREMELY annoying since I use the Gotcha pretty much daily.
jo...@gmail.com
> Can this be switched to P2?
I would support raising this to P2 as well, especially as enhanced BLE support has been featured in Android 13 yet it's clearly broken at the moment.
I would support raising this to P2 as well, especially as enhanced BLE support has been featured in Android 13 yet it's clearly broken at the moment.
si...@gmail.com
Comment has been deleted.
so...@gmail.com
Same here on Pixel 5 and Freestyle Libre 2 + Garmin Forerunner 955. Really unstable, need to reboot 2-3 times per day.
ma...@gmail.com
Having same issue with Pixel 5 and Dexcom G6. This is a huge issue for diabetics, please get this issue towards the top, or I'm going to be forced to rollback. I missed all my overnight alarms.
si...@gmail.com
Same on P6a and Amazfit Bip (Alert Bridge app)
os...@gmail.com
Both Garmin devices, car Bluetooth and Android Auto broken.
fu...@gmail.com
Comment has been deleted.
fl...@moticon.com
I have similar issues and can't connect to my own BLE peripheral since the update to Android 13 on a Pixel4a.
In my case the PHY_LE_2M mode seems the issue.
The Pixel 4a reports true on isLe2MPhySupported (). When trying to set PHY_LE_2M the connection hangs. When connecting with the default PHY_LE_1M, everything works as expected.
As I am using the NRF Android BLE library, I wrote a bug report there.https://github.com/NordicSemiconductor/Android-BLE-Library/issues/414
In my case the PHY_LE_2M mode seems the issue.
The Pixel 4a reports true on isLe2MPhySupported (). When trying to set PHY_LE_2M the connection hangs. When connecting with the default PHY_LE_1M, everything works as expected.
As I am using the NRF Android BLE library, I wrote a bug report there.
fu...@gmail.com
Comment has been deleted.
el...@gmail.com
Same problem here with Pixel 4a XL. Tesla phone key and Garmin smart watch keep dropping out consistently.
mk...@gmail.com
Same for Pixel 4a an Garmin ForeRunner 745
hf...@gmail.com
Having the same issue here with Pixel 6 Pro + Xiaomi Smart Band 7. The connection drops randomly (you can tell from the Bluetooth indicator on the band's display) but it seems the Android system is not aware of this (the Bluetooth button in the control center still shows the device is connected). In my case turning Bluetooth off and on may fix the issue temporarily but the issue will resurface as fast as minutes.
ch...@turnerlawoffice.com
Problem connecting to Tesla Model S with Pixel 6 pro. It won't connect even when set as priority device. I have to manually attach it every time.
gr...@gmail.com
Problem still exists with September update (TP1A.220905.004)
ka...@gmail.com
As others have noted, this impacts the Pixel 4A. Pretty severe; I first had this when I put my wife on a train, not realizing that the car was running on her phone key. I was able to drive away from the station, but hen had no ability to resume drive after stopping at a convenience store for coffee. I eventually thought to reboot my phone and then was on my way. It's been almost three weeks; this needs serious attention.
dg...@gmail.com
I use a Pixel 6 Pro and I have two family members who use a Pixel 4a and one using a Pixel 5a. All four of us have seen this issue when trying to use the Hiboy S2 app (https://play.google.com/store/apps/details?id=com.zydtech.hiboys2 ) after upgrading to Android 13. When on Android 12, the app was able to connect to the scooter through Bluetooth as intended, but after migrating to 13, the app never detects the scooter and connects to it. Instead, it just gets stuck searching for the device, but it never finds it. I had hoped to see this issue fixed with the September 2022 update, but unfortunately, it wasn't. I know it's not a hardware issue with the scooter either, because when I try connecting to it using Android 12 on my old Pixel 3 XL, the app connects just fine. This issue is a major blocker because the app is extremely important for proper use of the scooter. Until it gets fixed, I'll just carry my old Pixel 3 XL along with me, but I really look forward to the day when I no longer have to do that.
co...@punchthrough.com
Hello, I'm the issue reported. Retested our app with the September update (TP1A.220905.004) on Pixel 6, and there are a couple of new observations from repeatedly pairing (bond) and unpairing (forget the bond):
- We were able to get bonding to work the second time; however, the third time onwards, accepting the pairing dialog doesn't do anything anymore (see #2) — this seems like an even worse regression in our opinion.
- When we got to the third pairing attempt (meaning pair, unpair, pair, unpair, then finally pair again), and we try to start the bonding flow by reading an encrypted GATT characteristic, the pairing dialog appeared as expected. However, tapping "Pair and connect" doesn't result in an
onCharacteristicRead
Curious if any other developers are seeing something remotely similar to #2, as this is an even bigger problem than the initial issue (failing to reconnect to a bonded/paired BLE peripheral).
de...@gmail.com
Same issue here with Pixel 5 and Pixel 6, Tesla phone keys.
co...@punchthrough.com
To prevent conflating this original issue with the new one that seems specific to the September update, I've created a new issue here for the missing onCharacteristicRead callback:
ch...@gmail.com
I can confirm this issue as mentioned at the very top is still reproducible after the September update.
ka...@gmail.com
Same here, problem exists after the September update (Pixel 6).
I'm really disappointed as a Pixel used. Long term software support was one reason I chose this phone and not to be an alpha tester. My phone not being able to use basic Bluetooth devices, even the headset that came with it is absolutely ridiculous and seriously hurts my trust. Not sure if I want to invest more to be part of the Pixel ecosystem if things will continue to go like this.
I'm really disappointed as a Pixel used. Long term software support was one reason I chose this phone and not to be an alpha tester. My phone not being able to use basic Bluetooth devices, even the headset that came with it is absolutely ridiculous and seriously hurts my trust. Not sure if I want to invest more to be part of the Pixel ecosystem if things will continue to go like this.
be...@gmail.com
After September Update the connection with my Fitbit Versa 2 and JBL Live Pro+ TWS is still up after 12 hours! :) Synchronisation of Fitbit and connection of JBL Headphones in the application is possible after 12 hours :)
Before the September Update and now after, my Android Auto connection is possible and there are no problems, till now.
But now my chromebook can not find my Pixel 6 Pro :( Same after restart of my phone and chromebook. Disconnected both and tried again to connect... without success :(
Before the September Update and now after, my Android Auto connection is possible and there are no problems, till now.
But now my chromebook can not find my Pixel 6 Pro :( Same after restart of my phone and chromebook. Disconnected both and tried again to connect... without success :(
ba...@googlemail.com
Same issue for me. I am using a Pixel 5 and there are issues with my bluetooth headsets and the Tesla Phone key which also relys on bluetooth.
Issues still exists after the September Update.
Issues still exists after the September Update.
be...@gmail.com
Update to my Post #54! Connection between Pixel 6 Pro and Chromebook now works... Magic? Don't know why they suddenly connected successfully... now all worked fine with my devices...
With the September Update i resetted my Phone completely! To have a clean installation. Maybe that will work for others, too?
With the September Update i resetted my Phone completely! To have a clean installation. Maybe that will work for others, too?
m4...@gmail.com
Similar issues with P4a with Libre 2 CGM and also GN Resound Linx 7 hearing aid. Hearing aid reboot does not help, phone reboot solves the issue for maybe 12 hours or so. This is pretty severe especially the glucose monitoring side.
be...@gmail.com
Problem persists after September security update on pixel 6 not able to connect car Bluetooth/ android auto.
ar...@fullpower.com
Problem persists after September security update on pixel 5a not able to pair / bond with Bluetooth accessory health/wellness device.
nu...@gmail.com
Same issue with P6 Pro and TicWatch Pro 3 GPS and Android 13. I have reset, deleted, and reinstalled and the watch will stay connected for a while then I start seeing the connection status message "Problem connecting. Turn device off and back on." The watch battery then starts draining quickly. After the update yesterday I still have the same issue.
an...@gmail.com
Same issue here. I have pixel 4a and my Freestyle Libre 2 keeps disconnecting, meaning no glucose alarms. Especially when not knowing the alarms don't work it's a real issue!! Fitbit versa 2 also keeps disconnecting from my phone. After a phone reboot or switching between airplane mode it seems to work for a little moment to disconnect again shortly after.
ma...@gmail.com
google dropping some major ball...
clowns 🤣
clowns 🤣
pf...@gmail.com
Also affected, Pixel 4 XL.
be...@gmail.com
As several people mentioned before, this issue persists on Pixel 4A 5G even after the September update. Connection with the Freestyle Libre 2 is very weak. This is a huge problem for diabetics.
wa...@wadehyde.com
I knew was only a matter of time when I started saying to myself, "WHY did I buy another Pixel?" Really, Google. You're a multi-billion dollar corporation and, as you can see above, this is YOUR problem to fix. Do it!
uw...@gmail.com
Hi
I just want to give an update regarding Pixel 5 and Freestyle Libre 2 Sensor: It looks like at least for Pixel 5 (and after collecting some information from other users, also Pixel 4a) the reconnection problem of BLE devices is solved. On the other hand Pixel 6 users still complain about the same problems (and even worse) when connecting to the Freestyle Libre 2 BLE sensor device to receive alarms and blood sugar values.
I am trying to get log messages for Pixel 6 users, but with Pixel 5 all is back to normal: After connection loss (e.g. when you were in other room) you still get error 133, but when then the Diabox code is unbonding the device and reconnecting from scratch, the connection succeeds and stays awake. No stability issues.
Maybe
Here in this issue are also many other people complaining about Bluetooth issues. This is yes a general problem, but here it is only about BLE (Bluetooth Low Energy) devices, so it has nothing to do with connection problems to car audio, headphones, or similar "normal" Bluetooth devices. Here it is only about GATT devices.
Uwe
jo...@gmail.com
Pixel 5 Here.
Android 13 August Patch Level: Tesla BLE Car Key would "very often" not connect.
- Sometimes a Bluetooth off/on would help, sometimes it wouldn't.
- Sometimes a "long Bluetooth stop" --- turn off bluetooth. wait 15s, turn on bluetooth would help with the quick off/on wouldn't work
- Sometimes a reboot of the phone was necessary when the above did not work
August 14 September Patch Level: Tesla BLE Car Key issues persist, but less often
- So far, a single, quick bluetooth off/on has fixed the issue
fi...@gmail.com
No real change with my Pixel 6 and the Pokemon Gotcha thus far. It sometimes connects, often doesn't, and restarting the phone/reconnecting the device still only occasionally gets it to connect properly.
ra...@google.com
Thanks for reporting this issue. Could you please provide the bugreport with snooplog on latest public build. Here are steps to enable snoop log :
1. Settings -> System -> Advanced -> Developer options -> Enable Bluetooth HCI snoop logs -> Enable
2. turn off BT
3. on/off airplane mode
4. turn on BT
5. Start to reproduce, take bugreport when issue occurs.
co...@punchthrough.com
Hi
Bug report description
You should see an initial round of bonding success followed by a bond removal (done on purpose to illustrate this can work the first time). This first success case should look like this:
- Scan
- Connect and try to read an encrypted characteristic
- BLE bonding is triggered, user accepts, and the bonding was successful
- A bunch of characteristic writes and notifications/indications should be observed — this is the proprietary security handshake
- App-level pairing is deemed successful after said handshake completes — the firmware will disconnect from us and the app will have to reconnect to it using the bonded
BluetoothDevicehandle fromgetBondedDevices() - App reconnects successfully and everything is good.
- A user unpair is simulated: the GATT connection was closed and the bond was removed using Reflection (
BluetoothDevice.removeBond)
Then a second attempt was done which pretty much follows the previous scenario from steps 1–5, but instead, the following was observed, with the problematic observation in step 6 bolded:
- Scan
- Connect and try to read an encrypted characteristic
- BLE bonding is triggered, user accepts, and the bonding was successful
- A bunch of characteristic writes and notifications/indications should be observed — this is the proprietary security handshake
- App-level pairing is deemed successful after said handshake completes — the firmware will disconnect from us and the app will have to reconnect to it using the bonded
BluetoothDevicehandle fromgetBondedDevices(). - App was NOT able to reconnect successfully using the
BluetoothDevicehandle.onConnectionStateChangereports a status133almost instantly afterconnectGattwas called.
A device reboot will enable us to go back to the first success scenario, and the cycle repeats: after the first successful cycle, the second cycle onwards will see us run into the issue. This is working perfectly from Android 7–12.
To enable easier reproducing of the issue, I'm actually working on a barebones firmware that can be run on any Nordic nRF52840 development kit and also a companion barebones Android app that is configured to connect to it, bond, and allow anyone to reproduce this issue. I'll post updates here once they're available.
co...@punchthrough.com
Hi
uw...@gmail.com
Hi again, thanks for info and it is no problem if you have no Pixel 5 or 4a, it was just interesting to see why it differes between those phones. To me the whole issue looks like a bigger complex of several bugs in the new Gabeldorsche Bluetooth stack of Android 13. Some bugs seem to have been fixed in the September update, others not. When they occur, the damn error 133 happens all the time. It also looks like the Bluetooth hardware in the phone has an effect on the situation.
P.S.: The Freestyle Libre 2 uses EM9304 as SoC for communication with BLE.
co...@punchthrough.com
After testing on a Pixel 4a running the August security update TP1A.220624.014 and being able to reproduce the same issue as my Pixel 6, I want to note that a common thread between the two devices are the following log when the issue happens:
bt_btm_sec: packages/modules/Bluetooth/system/stack/btm/btm_sec.cc:3747 btm_sec_disconnected: Got uncommon disconnection reason:Connection Failed Establishment handle:0x0006 comment:stack::acl::btm_acl::btm_acl_disconnected
I'll have my team update the Pixel 4a to the September update and report back again if they're still able to reproduce the issue or not.
co...@punchthrough.com
Hi TP1A.220905.004 (the September update) and they were able to still reproduce the issue there. Perhaps the issue your team encountered was different than the one we're encountering? As mentioned in my earlier comment right above this one, we're seeing the following whenever we get the 133s:
bt_btm_sec: packages/modules/Bluetooth/system/stack/btm/btm_sec.cc:3747 btm_sec_disconnected: Got uncommon disconnection reason:Connection Failed Establishment handle:0x0006 comment:stack::acl::btm_acl::btm_acl_disconnected
In general, I think the Android Bluetooth stack needs a better way of surfacing errors than just a generic 133 catch-all — that'll be incredibly helpful for both developers and the Android team to help pinpoint what exactly is wrong when a bug like this surfaces.
ad...@gmail.com
Yup, confirmed that this is still an issue with Samsung Galaxy Watch 4 after taking the September update on my Pixel 6 Pro. The Bluetooth screen shows that the watch is constantly trying to reconnect and ends up draining battery.
It might start working properly on restarting the phone for a bit, but without notice it starts acting up. Have to turn off Bluetooth since it's unreliable. At anytime without my knowledge, the watch could go into this state of reconnecting and end up draining battery. If I'm out and about, I could go from 90% battery to 30% battery in a matter of a couple of hours.
This needs to be fixed urgently.
It might start working properly on restarting the phone for a bit, but without notice it starts acting up. Have to turn off Bluetooth since it's unreliable. At anytime without my knowledge, the watch could go into this state of reconnecting and end up draining battery. If I'm out and about, I could go from 90% battery to 30% battery in a matter of a couple of hours.
This needs to be fixed urgently.
ad...@gmail.com
Same issue. I have a Pixel 5a and have this issue with my Tesla phone key and Fitbit Sense.
ma...@gmail.com
I just got a new pixel 6 pro and boy am I regretting it. It came with Android 12, and everything was working fine, but on day 2 of ownership I made the mistake of upgrading to Android 13 without realizing it had all these Bluetooth problems and that Google won't allow you to flash back to Android 12.
My phone is unable to complete setup/activation of the "phone as a key" feature in the FordPass app for my Mustang Mach-E. It never displays the Bluetooth pairing prompt from the car which should appear during setup. (Confirmed it's not likely a car issue as pairing worked fine from another phone)
My phone is unable to complete setup of my galaxy 4 smart watch. The initial pairing is successful, but the Bluetooth connection drops within 20 to 30 seconds, before the Galaxy wearable app can finish the setup process. I've tried this process dozens of times after multiple factory resets of the phone and the watch with no luck.
I spent about 8 hours yesterday trying to overcome these issues but both persist, leaving my unable to use my smart watch, and unable to use my phone as a key for my car. Multiple factory resets of the phone did not help. I was stuck on the "August" release because the September update still wasn't available for my phone OTA. So I took the time to figure out how to manually load September update in hopes that it would fix it. It did not. I also tried loading the QPR December 2022 beta which also made no difference.
This phone is a huge disappointment.
My phone is unable to complete setup/activation of the "phone as a key" feature in the FordPass app for my Mustang Mach-E. It never displays the Bluetooth pairing prompt from the car which should appear during setup. (Confirmed it's not likely a car issue as pairing worked fine from another phone)
My phone is unable to complete setup of my galaxy 4 smart watch. The initial pairing is successful, but the Bluetooth connection drops within 20 to 30 seconds, before the Galaxy wearable app can finish the setup process. I've tried this process dozens of times after multiple factory resets of the phone and the watch with no luck.
I spent about 8 hours yesterday trying to overcome these issues but both persist, leaving my unable to use my smart watch, and unable to use my phone as a key for my car. Multiple factory resets of the phone did not help. I was stuck on the "August" release because the September update still wasn't available for my phone OTA. So I took the time to figure out how to manually load September update in hopes that it would fix it. It did not. I also tried loading the QPR December 2022 beta which also made no difference.
This phone is a huge disappointment.
nr...@gmail.com
Having the same issue with my pixel 6 pro on the September security update and my Garmin Forerunner. Saw a thread suggesting to toggle on "disable Bluetooth a2dp hardware offload" in the developer options. Going to give that a try
sc...@gmail.com
Same issue with Android 13. Bluetooth devices could not connect. Somehow I managed to get them working by toggling Bluetooth and Airplane mode. It appears the issue returns after every restart (3 so far) and after toggling airplane mode it resolved.
I'm still having an issue with Bluetooth connected headsets/speakers stop playing audio after an incoming call (through the Bluetooth headset/speaker). This issue requires a restart to fix.
So now I have Bluetooth issues causing me to restart to resolve and a new Bluetooth issues after restarting.. great work?
I'm still having an issue with Bluetooth connected headsets/speakers stop playing audio after an incoming call (through the Bluetooth headset/speaker). This issue requires a restart to fix.
So now I have Bluetooth issues causing me to restart to resolve and a new Bluetooth issues after restarting.. great work?
ch...@gmail.com
I have a Pixel 5 and am still experiencing this issue daily with the September 5th security update for Android 13. Affects both Garmin Fenix 6 watch and Omron blood pressure cuff.
bh...@gmail.com
I have pixel 6 pro. Bluetooth was working fine before the android 13 upgrade. After this upgrade, it is not stable and continuously gets disconnected randomly or fails to connect at all. It shows msg saying "Problem connecting to the device. Restart the device" most of the time. It also seems to have affected the battery life of the phone as well as the devices it is connected to due to this instability.
bh...@gmail.com
7p...@gmail.com
I am experiencing the same issue as
co...@gmail.com
Same issue as https://issuetracker.google.com/issues/242755161#comment14 on a Pixel 6 with the latest update (TP1A.220905.004). I've tried (multiple times):
- restarting (this used to work in the first update of Android 13 as it'd request connection to my sensor & pairing will eventually connect)
- toggling bluetooth
- disabling/enabling Bluetooth A2DP hardware offload
I've turned off "Pause app activity if unused" but no bluetooth request with my Dexcom transmitter is coming through. I don't see the transmitter as a connected device in my bluetooth menu but somehow my phone can't find it as a device to connect either.
This is exceptionally painful on a Dexcom since I do not want to restart my sensor since I still have 6 days left on this sensor (fortunately my Omnipod 5 can still see the bluetooth so I am using that). I do not want to re-install the app to see if I can reconnect as losing the local information may kill the current sensor session and these sensors are expensive medical devices that I cannot reuse. I'm also happy to debug with anyone if that'd be helpful.
- restarting (this used to work in the first update of Android 13 as it'd request connection to my sensor & pairing will eventually connect)
- toggling bluetooth
- disabling/enabling Bluetooth A2DP hardware offload
I've turned off "Pause app activity if unused" but no bluetooth request with my Dexcom transmitter is coming through. I don't see the transmitter as a connected device in my bluetooth menu but somehow my phone can't find it as a device to connect either.
This is exceptionally painful on a Dexcom since I do not want to restart my sensor since I still have 6 days left on this sensor (fortunately my Omnipod 5 can still see the bluetooth so I am using that). I do not want to re-install the app to see if I can reconnect as losing the local information may kill the current sensor session and these sensors are expensive medical devices that I cannot reuse. I'm also happy to debug with anyone if that'd be helpful.
ad...@gmail.com
any update on this bug? when can we expect the fix for this?
bh...@gmail.com
Can we get any update on this? Any workaround to use until we have an official fix?
fi...@gmail.com
Seconding requests for updates. Can the bluetooth stuff please be rolled back to what it was in 12 until you guys can actually fix it for 13? This is getting ridiculous.
While it's extremely inconvenient when things like car fobs and wireless audio stuff and such aren't connecting and working properly, it is more than merely an inconvenience when it's messing up vital medical devices like blood glucose and pulse monitoring devices that rely on Bluetooth. Fortunately I caught on to the issue in time to warn a friend who uses a Dexcomm to not update his phone, but the fact the update was pushed through with such a glaring issue is extremely alarming, along with the slow/lack of response to this issue.
While it's extremely inconvenient when things like car fobs and wireless audio stuff and such aren't connecting and working properly, it is more than merely an inconvenience when it's messing up vital medical devices like blood glucose and pulse monitoring devices that rely on Bluetooth. Fortunately I caught on to the issue in time to warn a friend who uses a Dexcomm to not update his phone, but the fact the update was pushed through with such a glaring issue is extremely alarming, along with the slow/lack of response to this issue.
ma...@gmail.com
Update please.
This is driving me mad having to manually connect and enter a pairing code 10 times a day to use my Garmin
This is driving me mad having to manually connect and enter a pairing code 10 times a day to use my Garmin
bo...@googlemail.com
Android 13 Pixel 6a does not pair bluethooth or only pairs after several tries with various apps or devices. This is rediculous - bluetooth isn't something new on the market and should work properly right away. Please fix ASAP
bj...@gmail.com
Same issue with me since upgrading to android 13. Garmin Venu 2s disconnects numerous times a day
co...@gmail.com
Pixel 4 XL and Pixel 5 - Tesla phone key won't connect to either. Have done all of the recommended steps via the car and phone (delete phone from car, add phones again etc) This works for less than 24hrs before the phone disconnects again. Have to use key card as phone is completely unreliable.
co...@gmail.com
Any updates? This is controlling a system that keeps me alive (I'm on a closed loop insulin pump and I just learned it doesn't work without the mobile app).
I've reinstalled the apps and reset the wifi and Bluetooth connections in Settings and that worked to connect my Dexcom sensor to start the sensor. The phone then shows a paring notification every 5 minutes as Dexcom attempts to connect again and if I don't accept the pairing, the connection dies. This also killed my battery (my phone could not charge even when plugged in). The pairing eventually stopped when I restarted my phone and has never started again (even after resetting Bluetooth connections in settings).
I've reinstalled the apps and reset the wifi and Bluetooth connections in Settings and that worked to connect my Dexcom sensor to start the sensor. The phone then shows a paring notification every 5 minutes as Dexcom attempts to connect again and if I don't accept the pairing, the connection dies. This also killed my battery (my phone could not charge even when plugged in). The pairing eventually stopped when I restarted my phone and has never started again (even after resetting Bluetooth connections in settings).
s....@signal.it
Same for me, but i'm just see the problem only with the Kyro processor..maybe its a bug related to this chip? I see problem whit oppo a74, red mi t9, moto g8 plus...there's some bug in software but where?
This is a serious problem, becouse yuo can't use simple pairing with device!
This is a serious problem, becouse yuo can't use simple pairing with device!
bh...@gmail.com
A quick update with my experience. I was asked by Google support to reach out to ubreakifix location as my phone is still under warranty. And when I reached there, guys at store told me that this problem is not fixable by them. Recently they changed motherboard on couple of devices but problem still persist. That means it is only software related and they said there will be patch soon for this. They don't know details when and how though.
co...@punchthrough.com
Hi Google Team, to add another data point, our team has found that the issue does not manifest on the Pixel 4a 5G but it does manifest on the Pixel 4a (4G). The issue is also reproducible on Pixel 6. All these devices are on the September update.
ar...@google.com
We have a fix prepared that should go out in the next QPR release, as well as in a security release in the coming months.
In the meantime, a workaround is to toggle Bluetooth and Airplane mode whenever you unbond the last device from a phone (i.e. after the list of bonded devices goes to empty, you should toggle Bluetooth). Then subsequent bonds and connections should be reliable. An edge case of note is that if you attempt to bond a device with none previously bonded, and pairing fails for any reason, you should treat this as a bonding followed by an unbonding event where the list goes to empty again, so you should again toggle Bluetooth.
Jo...@themoe.us
I have the same issue with my Pixel 5. Venu 2s is the worst issue. It loses connection all the time. Only reboot fixes for a short time. I also have issues with using device as a key for my Ford Mach-E. Very intermittent but if I open the Ford App it typically eventually comes back. Very frustrating since it is my key to my vehicle.
As for the intermittent, what exactly should we do to get this fix with devices that are pretty much supposed to be always connected. Please explain further.
As for the intermittent, what exactly should we do to get this fix with devices that are pretty much supposed to be always connected. Please explain further.
co...@punchthrough.com
Hi
Do you have an ETA on when the fix will make a QPR beta build, just so we could confirm that the fix is indeed effective towards the issue that was initially reported? Will it be included in QPR2? Thanks again.
co...@punchthrough.com
QPR1 Beta 2 was what I meant to comment above, apologies for the typo.
gi...@gmail.com
Just recently updated my Pixel 6 Pro, I seem to only be having issues with the Dexcom G6 app connection to the CGM sensor. I also have the Insulin pump connected using the Tandem T-Connect app and that app seems solid to the pump, and also is getting CGM data from the pump.
Very frustrating because the CGM data is shared with my wife for health data via the Dexcom app, as well the phone makes a max volume notification when it loses the connection (which is great at 3am)
Please fix ASAP
Running the september security update now, hoping that will help.
Very frustrating because the CGM data is shared with my wife for health data via the Dexcom app, as well the phone makes a max volume notification when it loses the connection (which is great at 3am)
Please fix ASAP
Running the september security update now, hoping that will help.
gi...@gmail.com
Side question, this defect was known in beta why did you release the gold version without resolving it?
uw...@gmail.com
Hi,
thanks
Known affected blood sugar medical devices:
- Freestyle Libre 2 (EM9304 SoC)
- Freestyle Libre 3 may also be affected; I have no information yet, as the internals of this sensor are currently reverse engineered by many people
- DEXCOM sensors (I don't have one, so SoC is unknown)
The serious issue here is that those devices stop alarming the user when blood sugar goes low or high, which can cause serious medical problems or even car accidents if those low sugar events are not recognized in time.
FYI, the blood sugar sensor problems could also come from
So it would really be good, if somebody at Google would open a separate issues for the more broad medical device reconnection problems to devices that went out of reachability and come back after some time and reconnecting then fails with dreaded 133.
It would also be good to add a feature request to allow more detailed error codes returned to apps, so you don't have to guess what dreaded 133 means in that case. Maybe return 133 only for lower API levels, but invent new error codes with good meaning for newer API versions. Thanks.
At least on my Pixel 5, the reconnection problems disappeared with the September update, but people with Pixel 6 series are really annoyed and their health is at risk! As
bo...@googlemail.com
Issue persists after October update on pixel 6 pro.
bh...@gmail.com
Yes. The above issue persists after the October update as well.
de...@gmail.com
Definitely happening on the 6a still. Seems less bad with my car, only disconnects 1-2 times instead of 3+ upon initial connection.
an...@gmail.com
Issue persists with pixel 6 & Oct update.
ma...@gmail.com
@Google - is this issue fixed in the QPR1 Beta 2 build that is being pushed right now? Wondering if I should join this beta... Thanks.
co...@punchthrough.com
QPR1 Beta 2 (T1B2.220916.004) appears to have fixed the issue I initially reported! Thank you, Google!
an...@gmail.com
Afraid it hasn't fixed my issue with Polar H6 heart rate monitor.
vi...@gmail.com
P6P with October update seems to have made it worse. BT toggles like 10 times in a day disconnecting everytthing.
au...@gmail.com
Just noticed this bug on my Pixel 4a after getting a Withings Steel HR. Watch disconnects and won't reconnect until bluetooth is turned off/on.
kl...@googlemail.com
Same problem with Pixel 6 connection to polestar digital key. The issue persists after the October update as well.
ha...@gmail.com
This kind of issue should absolutely not make it to production. I haven't been able to use my Galaxy Watch 4 with my Pixel 6 Pro for the last 2 months because of this issue. 90% of the time if I turn bluetooth back on from the watch, I instantly start getting persistent reconnections to the watch with a message of "problem connecting turn device off and on" from the phone's bluetooth menu. Once in a while the connection remains stable despite the "problem connecting" message and I can keep them connected for a while.
ka...@gmail.com
I added comment 47 above on Sept 6, more than a month ago. I have a Pixel 4A that is not working well as a key to my Tesla Model 3. My phone works fine as a key to the car for a day or two, but then it fails, and I need to reboot the phone. For me, toggling BT off/on doesn't help, and a brief journey to airplane mode doesn't help. I have the Oct security update on my phone, which didn't seem to help. The last comment from google was on Sept 28th, saying there was a fix that would go out in a security release. Q for ar...@google.com - did that fix get into the Oct 5th security update that's in my phone, but failed to solve the problem, or do I need to wait another 2-3 weeks for the Nov security release?
mi...@gmail.com
Pixel 4a, Android 13, build TP1A.221005.002. Bluetooth issues still persistent. My Garmin Forerunner 255 keeps loosing the Bluetooth connection. The critical issue for me is that my continuous glucose monitoring device Dexcom G6 keeps loosing the connection which is a health hazard. Anybody tried to roll back to Android 12? I am seriously considering this line of action as a last resort for this issue.
c....@gmail.com
I have a Pixel 4a too, and I was disappointed as after the upgrade to android 13 because of the Bluetooth connection problems. I use my telephone with an Android Car Box. After the Update, the Connection sometimes freezes during runtime and only a reboot of the phone could solve the problem. Other Bluetooth connections were very sluggish. Listening to music over Bluetooth does only work for the first 20 minutes, after that the audio was cutting out.
I decided to perform a roll back to Android 12, and now I wait for the Fix before I will Upgrade to Android 13 again. Whoever likes to perform the roll back to Android 12 keep in mind to save all your private data of the phone. After the rollback, all your data on the phone will be lost.
I did use this guide to perform the downgrade to Android 12:
https://9to5google.com/2022/08/16/how-to-downgrade-from-android-13-to-android-12-on-google-pixel/
I decided to perform a roll back to Android 12, and now I wait for the Fix before I will Upgrade to Android 13 again. Whoever likes to perform the roll back to Android 12 keep in mind to save all your private data of the phone. After the rollback, all your data on the phone will be lost.
I did use this guide to perform the downgrade to Android 12:
ap...@gmail.com
Have the same issue mentioned. Made my watch unusable and issues with my pixel buds and car and connecting to my car too. It's embarrassing that Google would allow this to production and still not fixed several patches later.
bo...@gmail.com
Seriously why has not been solved?!
Pixel 4a here... It's ridiculous to have purchased a Google official smartphone and having a bug like this for months!
Please apply a fix
Pixel 4a here... It's ridiculous to have purchased a Google official smartphone and having a bug like this for months!
Please apply a fix
sc...@gmail.com
This issue seems resolved for my devices.
de...@gmail.com
Which devices and what build number?
On Fri, Oct 28, 2022, 06:43 <buganizer-system@google.com> wrote:
On Fri, Oct 28, 2022, 06:43 <buganizer-system@google.com> wrote:
sc...@gmail.com
LE headphones and other LE devices.
Build # TP1A.221005.002
Build # TP1A.221005.002
de...@gmail.com
Sorry, I was unclear. Which Pixel phones?
On Fri, Oct 28, 2022, 07:58 <buganizer-system@google.com> wrote:
On Fri, Oct 28, 2022, 07:58 <buganizer-system@google.com> wrote:
uw...@gmail.com
Sorry, I was unclear. Which Pixel phones?
Build # TP1A.221005.002
This is Pixel 5 October update. In this phone all works fine since already October. The problems here are mostly Pixel 6.
du...@gmail.com
I have that same build (TP1A.221005.002) on a Pixel 5a and still have the issue where I can't unlock my Tesla with the phone key (as I've had for the last month+ now). Really wish I hadn't updated to Android 13.
or...@gmail.com
Brand new Pixel 7 pro. Add my Tesla as a Bluetooth connection. Everything works fine for maybe a day. Then randomly the phone will delete the Bluetooth connection and it's no longer on the list in the phone. I've tried this with two brand new Pixel 7 pros. Both will forget the Bluetooth connection or more accurately delete the Bluetooth connection from the phone.
Forgetting the connection does not require rebooting of the phone or any other activity that I can track it to. The longest it maintained a connection was about 30 hours. The shortest is probably about 4 hours. It's very frustrating that every time I get into the car I pretty much have to recreate my Bluetooth connection for phone use.
As a side note, the Tesla app for using the phone as a key works flawlessly. And so that Bluetooth activity is working fine
Forgetting the connection does not require rebooting of the phone or any other activity that I can track it to. The longest it maintained a connection was about 30 hours. The shortest is probably about 4 hours. It's very frustrating that every time I get into the car I pretty much have to recreate my Bluetooth connection for phone use.
As a side note, the Tesla app for using the phone as a key works flawlessly. And so that Bluetooth activity is working fine
da...@gmail.com
Didn't have any issues until build number TP1A.221005.002 which looks like it was supposed to fix the issue. Now Bluetooth device can be stored within Bluetooth of the phone, a pixel 6. But refuses to connect to the app in question.
da...@googlemail.com
Having issues with the Tesla app now not working reliably on Pixel 7 Pro , toggling Bluetooth on and off often fixes it. When can we expect a fix as this is super annoying
ma...@gmail.com
I would like to add that I'm on the beta program and the issue is still happening occasionally on the latest QPR beta release. I'm on a Pixel 7 build number T1B3.221003.003
ca...@gmail.com
I think the fix is just roll back to 12.. that's what I did
ke...@gmail.com
Samsung Galaxy S22 ultra. Signia Streamline mix. Will not stream audio of any sort. I do get a 1 in 50 connection to my right hearing aid. No help from Samsung, or signia as they have not heard of this. All was working well until the T-Mobile android 13 update. Now it's just crap.
ro...@gmail.com
Random disconnection of Bluetooth peripherals but they report connected in the Bluetooth menu.
Bluetooth peripherals connect but don't output sound or appear as an option in volume menu
Already connected items disconnect but look connected
In short, bluetooth has completely broken as many people have said - how can this still be an issue? Is something being done?
Bluetooth peripherals connect but don't output sound or appear as an option in volume menu
Already connected items disconnect but look connected
In short, bluetooth has completely broken as many people have said - how can this still be an issue? Is something being done?
ca...@gmail.com
Buy tasker and have it toggle BT and Airplane mode on BT connect inverse
lj...@gmail.com
Guys are awesome this 13 always a problem
On Tue, Nov 1, 2022, 7:54 AM <buganizer-system@google.com> wrote:
On Tue, Nov 1, 2022, 7:54 AM <buganizer-system@google.com> wrote:
go...@fastmail.com
Maybe this is related: seems like GAN smart cubes (BLE puzzle devices) quickly disconnect only from Pixel devices (tried with 6 and 6a). By "quickly" I mean seconds (10-60 sec). Windows PC with Intel AX200 and iOS devices works flawlessly and don't disconnect for hours.
https://www.reddit.com/r/GANCUBE_Official/comments/ylv5fw/comment/iv2jli3/?context=3
du...@gmail.com
Hopefully I'm not speaking too soon, but I installed the Nov update and I was able to unlock my car twice in a row!! 🤞
ka...@gmail.com
My Pixel 6 still fails to connect to the very headphones they shipped it with (Bose 700) after the November update.
I have to use my company iPhone and I am much more likely to pick an iPhone as my next phone for this reason. It is absolutely ridiculous how Google has not only published this bug in a "stable" release but was unable to fix it in 3 months and I have lost all my faith that they will do it in the next 3 months.
I was hyped for the new Pixels, but the software is borderline unusable..coming from an industry leading software company. 👏
I have to use my company iPhone and I am much more likely to pick an iPhone as my next phone for this reason. It is absolutely ridiculous how Google has not only published this bug in a "stable" release but was unable to fix it in 3 months and I have lost all my faith that they will do it in the next 3 months.
I was hyped for the new Pixels, but the software is borderline unusable..coming from an industry leading software company. 👏
kl...@googlemail.com
Problem with Pixel 6 connection to Polestar 2 car digital key (#112) persists after the November update as well.
br...@gmail.com
Google has different statuses for bug tickets. See upper right section on this page.
"Assigned" means that someone is working on the problem, but the problem is not solved yet
an...@gmail.com
Still not fixed in Nov update for me.
bo...@googlemail.com
This is getting ridiculous. It's been 3 months for a "top" priority issue and it's not even in the beta release.
sa...@gmail.com
Having similar issue with Pixel 7. Hearing aids paired, but will not re-connect unless I put them in pairing mode. Took several weeks and settings attempts just to get that far. Seems an issue when copying over data from old device... had to forget device, clear network/bluetooth/wifi settings, uninstall hearing aid app. Reboot... repair devices through the app. Been a full 24 hours that is has rememberd the connection. But... get out of range of the phone so devices lose connectivity to bluetooth... and I discover bluetooth is still on, but to get the devices to connect I have to put them in pairing mode. Turning bluetooth on and off doesn't work.
so...@gmail.com
Issue not fixed on Nov Pixel 7 Pro
kr...@gmail.com
Issue not fixed by November security update Pixel 5
fi...@gmail.com
It has been months now. I still cannot reliably connect my Bluetooth peripherals with my Pixel 6 Pro without first having to reboot the phone, toggle Bluetooth and/or airplane mode, and re-pair the devices every single freaking day and often multiple times daily. Thankfully I was able to warn my housemate NOT to update his phone since he relies on a Dexcom for his blood glucose tracking. I absolutely hate Apple but am seriously considering the possibility for my next phone given the sluggish response to this very serious issue with Android.
sh...@gmail.com
didn't have the issue before, october update broke it n still unfixed. cant consistently stay connected to anything
jm...@gmail.com
Replaced my Pixel 5 that was having this issue with a pixel 7. Have the same exact issue on the pixel 7 running the latest November update. Super frustrating. Bluetooth is such an absolute necessity these days and to still not have a solution after months is getting ridiculous.
li...@gmail.com
I am a a diabetic who wears a Freestyle Libre 2 device.
Ever since upgrading my samsung S22 to android 13, I get constant "alarm loss signal" which means, Bluetooth is no longer connected and the device cannot send life-saving low glucose and high-glucose alarms to my phone. To reiterate previous comments, this is a major concern for individuals who are using such devices to monitor blood glucose levels as alarms will not function if the connection has been lost. I have found that if I turn Bluetooth off then back on again, it works ok for 4-5 hours before Bluetooth signal is lost again. Reading above comments showing log files constantly trying to reconnect explains why my phone battery has been drained flat around 5pm every day since upgrading to android 13 4 days ago.
I've tried all troubleshooting suggestions from both Samsung and Abbott freestyle libre:
Reset network settings
Uninstall and reinstalling app
Ensuring app is latest version
Ensuring app says it supports android 13
I'm located in Australia so the android 13 update is only just starting to be rolled out. This needs a fix urgently
Ever since upgrading my samsung S22 to android 13, I get constant "alarm loss signal" which means, Bluetooth is no longer connected and the device cannot send life-saving low glucose and high-glucose alarms to my phone. To reiterate previous comments, this is a major concern for individuals who are using such devices to monitor blood glucose levels as alarms will not function if the connection has been lost. I have found that if I turn Bluetooth off then back on again, it works ok for 4-5 hours before Bluetooth signal is lost again. Reading above comments showing log files constantly trying to reconnect explains why my phone battery has been drained flat around 5pm every day since upgrading to android 13 4 days ago.
I've tried all troubleshooting suggestions from both Samsung and Abbott freestyle libre:
Reset network settings
Uninstall and reinstalling app
Ensuring app is latest version
Ensuring app says it supports android 13
I'm located in Australia so the android 13 update is only just starting to be rolled out. This needs a fix urgently
ar...@gmail.com
Pixel 6 Pro and 7 Pro affected as well here.
I stand like an idiot in front of my Tesla every other day trying to unlock it, then have to toggle BT for the car to see the phone. Also, when this happens, trying to discover new BT devices fails instantly.https://twitter.com/ArtemR/status/1592176285908103170 .
I stand like an idiot in front of my Tesla every other day trying to unlock it, then have to toggle BT for the car to see the phone. Also, when this happens, trying to discover new BT devices fails instantly.
ma...@gmail.com
@Google! Can we please get an update on the progression of fixes for this bug? and the estimated release date of said fixes?
rj...@gmail.com
My Google Google Pixel 3XL was updated to Android 12. I accepted an upgrade
for a Google Pixel 7 Pro. Besides the very important facts with the 7Pro
such as, *** It dropping service at my Home that has a LTE extender, it
drops service away from home. If I turn off the SIM card and disconnect it
from my service provider, then back on.. it works most of the time.*****
Android 13 is not compatible with my Security Camara App " Night Owl
Protect" as was the Pixel 3XL. As I am 65, and disabled this is a huge
issue for me, as well as the above listed. I've been on the phone and Chat
rooms with Night Owl Tech support Tear 2, and is ongoing at the
present time. I've sent them screenshots of the camara's, proof of
purchase, for their developers to communicate with Google developer's.
**** Google Pixel 7 Pro mind you, a Google product DOESN'T CONNECT TO
GOOGLE HOME! How can I expect it to perform on my Security App. Wow! For
the first time I am switching to Apple. This is Ridiculous Google
developer's! To say the very least! No updates as of yet as to when it will
work.
RJ Edler
On Mon, Nov 14, 2022, 12:36 PM <buganizer-system@google.com> wrote:
for a Google Pixel 7 Pro. Besides the very important facts with the 7Pro
such as, *** It dropping service at my Home that has a LTE extender, it
drops service away from home. If I turn off the SIM card and disconnect it
from my service provider, then back on.. it works most of the time.*****
Android 13 is not compatible with my Security Camara App " Night Owl
Protect" as was the Pixel 3XL. As I am 65, and disabled this is a huge
issue for me, as well as the above listed. I've been on the phone and Chat
rooms with Night Owl Tech support Tear 2, and is ongoing at the
present time. I've sent them screenshots of the camara's, proof of
purchase, for their developers to communicate with Google developer's.
**** Google Pixel 7 Pro mind you, a Google product DOESN'T CONNECT TO
GOOGLE HOME! How can I expect it to perform on my Security App. Wow! For
the first time I am switching to Apple. This is Ridiculous Google
developer's! To say the very least! No updates as of yet as to when it will
work.
RJ Edler
On Mon, Nov 14, 2022, 12:36 PM <buganizer-system@google.com> wrote:
sc...@gmail.com
As an IT professional I'm about to abandon Android and take all cliental with me over this issue. It was reported during beta and you rolled it out anyways. Pixel 4a 5g, nothing but problems with Bluetooth since Android 13 "upgrade" Have to reboot phone multiple times per day.
ho...@gmail.com
Same problem here on my p6a. Strange thing is that I first had no problems, I had the august security updates. Then I removed some bonds and now suddenly I can't get a bond anymore.
I updated to the latest beta version (T1B3.221003.008) but same problem exist.
When will this be fixed? I have customers reporting problems when they use our device but we can't fix this!
I updated to the latest beta version (T1B3.221003.008) but same problem exist.
When will this be fixed? I have customers reporting problems when they use our device but we can't fix this!
ol...@gmail.com
WOW. Also having this problem. Brand new Pixel 7 forgets my bluetooth device(s) every time I switch bluetooth off and on again and also forgets them randomly between minutes and several hours. How can that be? Who tested this?
Now I will sell the Pixel 7 and order a phone with Android 12. That was close Google. I almost switched to Apple.
Now I will sell the Pixel 7 and order a phone with Android 12. That was close Google. I almost switched to Apple.
ro...@gmail.com
Comment has been deleted.
ro...@gmail.com
Samsung Galaxy A53 5G. I bought it several months ago to have a reliable phone to work with Freestyle Libre 3 (glucose sensor for diabetes). Yesterday I have updated my phone to Android 13 and now I'm fucked. No rollback possible. Thanks, this is my last Android phone. I'll switch to Apple for sure.
er...@gmail.com
None of my Garmin devices are working reliably. This issues has been open for 3 months, has been a P1 S1 for most of that and still we can't even get a "we're working on it" from Google. C'mon man, this is pathetic.
li...@gmail.com
RE: Samsung phones One UI 5, Android 13, bluetooth connection issues for Freestyle Libre devices: This article has been brought to my attention: https://www.sammyfans.com/2022/11/02/breaking-samsung-releases-android-13-bluetooth-connection-issue-fix-update-for-galaxy-s22/ however I have had no official word about this from Samsung nor any indication when it will be available for my phone - Galaxy S22 - model SM-S901E in my region (Australia).
Quoting from this article: "Recently, the Samsung Members community moderator has informed that Samsung has started rolling out a new software update for Galaxy S22, S22+, and S22 Ultra devices, which installs a fix for the severe Bluetooth connection issue that was troubling customers after stable One UI 5.0."
Can ANYONE please confirm or deny this information, and a release date/roadmap for this fix please?
Quoting from this article: "Recently, the Samsung Members community moderator has informed that Samsung has started rolling out a new software update for Galaxy S22, S22+, and S22 Ultra devices, which installs a fix for the severe Bluetooth connection issue that was troubling customers after stable One UI 5.0."
Can ANYONE please confirm or deny this information, and a release date/roadmap for this fix please?
so...@gmail.com
My Pixel5 was having issue with Tesla app for car key right after Android 13 upgrade. Just replaced Pixel 5 with a pixel 7 and the same exact issue with latest November update. Reboot can help but issue would come back after few days. Can we have timeline for the fix, please?
ji...@gmail.com
Very similary problems found on Samsung Z Fold4 after upgrading to A13. Everything was OK until upgrade.
We are using BLE to open doors from our app which is not possible to do reliably anymore. Once BT get stuck like this, no app on phone is able to conect to BT devices.
Restart of phone seems to help for a while.
Is there any official reaction from Google?
We are using BLE to open doors from our app which is not possible to do reliably anymore. Once BT get stuck like this, no app on phone is able to conect to BT devices.
Restart of phone seems to help for a while.
Is there any official reaction from Google?
ru...@gmail.com
Same here, Pixel 4a, updated to 13 yesterday, all seemed fine then this morning, can't get into my car. Garmin is intermittent, people can't hear me when I'm making calls in the car. Tried reboots, forgetting and re-pairing etc etc etc. This is second rate, poor performance and VERY frustrating - please get it fixed asap.
lu...@gmail.com
Since my A53 updated to android 13, the bluetooth has stoped working. I have to restart the phone to be able to connect to the bluetooth devices... and works only for a few more hours... then another restart... this is a nightmare!
cb...@gmail.com
Allow Android 13 Bluetooth System app to delete cache and data instead of making it inaccessible. I removed all Bluetooth devices on Pixel6 Pro and have 14.34kb Cache & 550kb user data still showing that I am not able to delete. Mind you I cleared out all my devices by
forgetting them but they still have active connections. Tell me how that is possible?
Please advise,
cblengr@gmail.com
forgetting them but they still have active connections. Tell me how that is possible?
Please advise,
cblengr@gmail.com
wa...@gmail.com
Same Problem with BT Connection to my Tesla (Pixel 7 Pro). Really hoping for a solution soon!
tc...@googlemail.com
same - has broken connection to my Fitbit Inspire 2
ha...@gmail.com
Having the same problem with a Galaxy Flip 3 on A13 november release. Bluetooth works fine with Galaxy Watch5 and Bluetooth Audio in Tesla, but Tesla key (BLE) only works for a short time after phone reboot.
I'm really hoping for a update that resolves this since I already have walked away from the car unlocked several times as walk away lock does not work anymore...
I'm really hoping for a update that resolves this since I already have walked away from the car unlocked several times as walk away lock does not work anymore...
ma...@gmail.com
Same problem here: some devices wont maintain a connection. some devices wont connect until i reboot my phone
al...@gmail.com
I've set up tasker so that every hour, if my phone isn't using the BT connection, it will turn BT off then on again - this is mitigating this ridiculous issue for me for now.
I have a pixel 5 and my wife has a pixel 6 pro - both of these phone almost daily prevent us from unlocking our Tesla and even worse the walk away lock doesn't reliably work.
Between this and the sms bug that causes years old sms to be redelivered in cars, I'm about done with android. This coming from someone who has been in the depths of Android since the Android 'Eclair' days with a Motorola Milestone (droid).
Not that google really cares what I do personally but the failure to address the basics has me thinking my next phone may just well be an apple.
I have a pixel 5 and my wife has a pixel 6 pro - both of these phone almost daily prevent us from unlocking our Tesla and even worse the walk away lock doesn't reliably work.
Between this and the sms bug that causes years old sms to be redelivered in cars, I'm about done with android. This coming from someone who has been in the depths of Android since the Android 'Eclair' days with a Motorola Milestone (droid).
Not that google really cares what I do personally but the failure to address the basics has me thinking my next phone may just well be an apple.
ja...@gmail.com
My wife uses a Samsung S22 Ultra to connect to get Tandem diabetes insulin pump. She accidentally did the major upgrade to 13 and now can't bolus from her phone. Stable Bluetooth connections and wi-fi connections are ESSENTIAL base functionality. Why do the majority of medical devices program for iOS and not Android? Because of problematic Android updates like this. If a new Bluetooth feature breaks existing stability, it should never make it into a production build. Bluetooth instability introduced into a production build isn't something that phone users won't notice and it certainly increases user frustration and makes users and developers want to dump Android for Apple. Get your act together Google before you alienate more business and consumers!
th...@karcher.com
Same Problem with my TESLA an Samsung S22 Ultra on Android 13.
No automatic reconnect with the Car. The Phone is the Key, this is very bad!!!!!!!!
No automatic reconnect with the Car. The Phone is the Key, this is very bad!!!!!!!!
ch...@gmail.com
My partner and I are both having the problem here with our Pixel 5 phones and a Tesla Model 3. We've been waiting too long for a fix. Turning bluetooth off and back on and allows the phone key to work again.
dj...@gmail.com
having the same issue with my bluetooth headset and pixel 4a (4g). Has rendered my expensive headset completely useless. Please fix this
ne...@gmail.com
Problems with my Galaxy Z Flip 4 with A13 and Freestyle Libre 3 CGM. This issue is very serious. Please give the possibility to rollback the Update!
jg...@gmail.com
To all my fellows that look like an idiot standing in front of their Teslas: you can unlock your phone and hold it up to the B pillar where you'd hold the valet key to unlock the car. Not only will this allow you to unlock the car, but it will also allow you to start the car. It will not auto lock the car when you walk away though. This work around has prevented me from rage commenting on this bug tracker. Hope it helps!
ma...@gmail.com
Whatever your name is.... Thank you for this workaround (re.. Tesla unlocking with phone)...
ki...@gmail.com
Samsung Galaxy S20 Note 5G Ultra. After upgrade to Android13 Tesla Model Y mobile key stopped working. Upgrade had changed the battery saving settings by itself. Changed battery saving setting and mobile key works now for 24H or maybe even 48H. After that phone reboot is required.
cl...@gmail.com
My wife upgraded her Pixel 6 to Android 13 and immediately started having issues with her Tesla key. At first we thought it might be a bug in the latest Tesla software update but the phone key on my Samsung S22 running Android 12, still worked perfectly. Before realizing this, I upgraded my S22 to Android 13. Fortunately it appears to be working still. So either Samsung fixed the issue with the Bluetooth stack in their latest update for their devices or there is something hardware specific with the pixel phones that is incompatible with the latest Bluetooth stack in Android 13.
It's pretty pathetic that Samsung seems to understand Android better than Google at this point. This has clearly been an issue for months and sounds like it may have even been a known issue in beta. If this is not resolved soon we will ditch the Pixel and never look back.
It's pretty pathetic that Samsung seems to understand Android better than Google at this point. This has clearly been an issue for months and sounds like it may have even been a known issue in beta. If this is not resolved soon we will ditch the Pixel and never look back.
ca...@gmail.com
It looks like the Dec patch finally will fix this issue.
co...@punchthrough.com
I'm the initial issue reporter and can confirm that TQ1A.221205.011 has fixed the issue completely. Thank you, Android team!
li...@gmail.com
Hi, this is excellent news about the December update. Could anyone confirm please when update TQ1A.221205.011 will be rolled out to Samsung S22s in Australia? My phone currently has software version
TP1A.220624.014
Thanks
TP1A.220624.014
Thanks
kl...@googlemail.com
Worked only for some hours for my digital key of my polestar 2 car. Now
same problems as before the december update.
<buganizer-system@google.com> schrieb am Di., 6. Dez. 2022, 09:36:
same problems as before the december update.
<buganizer-system@google.com> schrieb am Di., 6. Dez. 2022, 09:36:
so...@gmail.com
Pixel 7 pro with Dec and my phone did not connect to Tesla 3 today. This is getting ridiculous, how can we go back to Android 12
bo...@googlemail.com
Still broken after Dec update on p6p. Getting"wrong passkey" or "can't communicate with device" when trying to pair now.
al...@gmail.com
For now this seems to have fixed it for me - although I'll give it a week or so before I'm content.
For those still having issues, making sure it's not causes by one of the many other things that can trip up phone keys, like the app not running after an update or boot, or allowing the phone to apply battery saving measures to the app.
For those still having issues, making sure it's not causes by one of the many other things that can trip up phone keys, like the app not running after an update or boot, or allowing the phone to apply battery saving measures to the app.
jo...@gmail.com
Tesla owners - After updating to Dec Update on my P7, my Tesla app lost "Nearby Devices" permission. After an initial growling from me as I walked up to the car, I opened the Tesla app and it detected this permission miss and I was able to quickly remediate. Tesla has been fine since, but its only been a day so far.
Anyone else with Polestar or other similar apps, check your permissions, maybe not all apps are as intelligent/prompty about the missing permission.
sa...@gmail.com
I am P6P and Tesla model3 owner. After update to TQ1A.221205.011 version. My phone key was activate normal. Thanks for the hard work to Googler.
ma...@gmail.com
Everything seemed good for a couple of days after the December update, but this morning it happened again. Stood there like an idiot toggling Bluetooth off and on to get into my Tesla.
an...@gmail.com
And, even after the update, I still can't pair my Polar H6 Bluetooth Heart Rate Monitors (that do pair with MS Windows & Apple iOS).
pa...@gmail.com
Same issue here with Tesla App, did not work for me today (am on `TQ1A.221205.011`).
kl...@googlemail.com
After Dec-Update of my Pixel 6 I have uninstalled and reinstalled my Polestar app with the digital key to my car. Worked fine for some hours, then the same problems as before Dec update. No real progress.
fi...@gmail.com
No change here. Even after the December update I still can't connect my Pokemon Gotcha without toggling Bluetooth on and off and/or rebooting the phone, sometimes multiple times. Once I DO get it to connect, my Pixel 6 Pro will detect it reliably for the next 12-18 hours, but every morning I have to fight with it before it will successfully connect.
ad...@gmail.com
Dec update, day 5, Tesla key and Garmin watch both back to being stable. For those still experiencing issues, try checking app permissions to make sure no permissions need to be re-enabled.
ma...@gmail.com
Android Beta QPR2 Beta 1 just released... Can Google confirm if the fix for this is included!?
bo...@googlemail.com
QPR2 Beta 1 didn't change a thing. As expected, the issue didn't change from "Assigned" for the past 4 months...
gr...@gmail.com
Pixel 6 Pro - Major Bluetooth issues began the day after Android 13 upgrade - disconnect/reconnect loops for all my devices. Issue slowly got better after 2 months and was working fairly well for Android Auto (wired or wireless), Pixel Buds, and working sometimes for my BT speakers. Then the December mega patch came along and blew it all back apart the next morning. If AA's Google Analytics setting records all the disconnects, ya'll gonna need a new server just for me.
j....@gmail.com
Am experiencing significant Bluetooth issues on a Pixel 4a immediately following Android 13 upgrade, and the connection to my Dexcom G6 continuous glucose monitor and Google Pixel Watch will break at exactly the same time. I need to toggle bluetooth and trigger a re-bonding to get the CGM to re-connect. As others have mentioned this bug is, in effect, resulting in an incredibly significant life safety risk to diabetics who depend on a CGM and this needs immediate resolution.
cc...@gmail.com
I am also experiencing this issue on after the update on a Veruzon Galaxy S21 Ultra.
ja...@whoop.com
One plus 8T - Major Bluetooth issues immediately after upgrading to Android 13. I can no longer connect to any device on that phone and its affecting not just me but multiple One plus users who upgraded their devices to Android 13 https://issuetracker.google.com/issues/263076532
gf...@googlemail.com
Same for me Galaxy S9 with custom Android 13. Not able to connect to several Bluetooth devices.
fi...@gmail.com
The December update seems to have slightly improved the Bluetooth issue. In 12 I could load Pokemon Go, click the icon in the app to tell it to connect to my Gotcha, and after a second the confirmation would pop up. Now I have to tap on the icon in-app, switch over to settings, go to Connected Devices and re-pair it there to get it to pop up the confirmation and connect. But for the most part I no longer have to reboot my phone in the process, so that's an improvement.
[Deleted User] <[Deleted User]>
Causing issues with my phone and apps installed. Please rectify this asap. Thanks
vi...@google.com
Re-
- adb shell setprop persist.bluetooth.btsnooplogmode full
- adb shell device_config put bluetooth INIT_logging_debug_enabled_for_all true
Other affected users running QPR1 builds can also share bugreport with us as stated above.
li...@gmail.com
Hi, Could anyone confirm please if update TQ1A.221205.011 is applicable for Samsung phones? Or is this applicable for pixel phones only? My phone currently has software build number
TP1A.220624.014.xxxx and this build number didn't change with the last software update from Samsung yesterday. The Android security patch level is now 1 December 2022 and the issue mentioned above is still just as bad with zero improvement. (I've checked permissions)
PLEASE anyone with knowledge of this please shed some light on this as I'm getting zero answers from Samsung who had promised this issue would be fixed in the "NEXT" software release, which I just installed, but I'm not sure if it's the correct one to fix this issue as the build number didn't change. Thanking you in advance for your help.
TP1A.220624.014.xxxx and this build number didn't change with the last software update from Samsung yesterday. The Android security patch level is now 1 December 2022 and the issue mentioned above is still just as bad with zero improvement. (I've checked permissions)
PLEASE anyone with knowledge of this please shed some light on this as I'm getting zero answers from Samsung who had promised this issue would be fixed in the "NEXT" software release, which I just installed, but I'm not sure if it's the correct one to fix this issue as the build number didn't change. Thanking you in advance for your help.
c....@gmail.com
Same issue with Sony Xperia 5 III. After update to android 13, my Polar H10 heart rate monitor does not work on my phone. With an older phone yes but with this android 13 nightmare nothing. The heart rate monitor is now completely useless, please fix this problem asap.
ch...@gmail.com
Someone has hacked my account My android is stuck at android 11 and won't
update I am a professional writer for Google beta I work for Google Maps
and have 19 million Views. My number 8154013830
My emails are
chadharrison72@gmail.com
chadderbox448369@gmail.com
chadharrison4483@outlook.com
chadderbox1650@gmail.com
The code write is unique and I need help
My phone is a Android phone TCL XE 20
And I need help and advice immediately
On Sun, Dec 25, 2022, 1:56 PM <buganizer-system@google.com> wrote:
update I am a professional writer for Google beta I work for Google Maps
and have 19 million Views. My number 8154013830
My emails are
chadharrison72@gmail.com
chadderbox448369@gmail.com
chadharrison4483@outlook.com
chadderbox1650@gmail.com
The code write is unique and I need help
My phone is a Android phone TCL XE 20
And I need help and advice immediately
On Sun, Dec 25, 2022, 1:56 PM <buganizer-system@google.com> wrote:
ca...@gmail.com
Same issue with a Samsung A53 5g uw. Unable to reliably connect with Freestyle Libre 3 diabetic blood sugar monitors, unable to reliably connect to my Ford Escape via bluetooth, unable to connect to my stereo receiver to play music. Not discovering local bluetooth devices. Essentially, all bluetooth connections are tenuous, not reconnectable and bricked. NEED A PATCH ASAP.
ra...@google.com
Please provide the requested information in
lk...@gmail.com
Re-
This is the output I get:
# adb shell setprop persist.bluetooth.btsnooplogmode full
Failed to set property 'persist.bluetooth.btsnooplogmode' to 'full'.
See dmesg for error reason.
...and on release builds of Android, we cannot read dmesg :(
# adb shell dmesg
dmesg: klogctl: Permission denied
The second command seems to go through though.
ag...@gmail.com
This issue exists since April 2022 and not fixed yet? Nobody cares of it. Continuing spreading to other phones with updates by schedule for Samsung. Samsung A53 was scheduled for updated on Dec 2022. And after update on Dec 24, 2022 my vehicle said there is no more connected phones. Never hspoend thar before. Restarting the phone was helping for a while. Resetting all network connection without restarting was more inconvenient to clear all data about connection and didn't help. After all devices were connected back the phone lost the bluetooth connection.
I would like to roll back that update but it's impossible. Just back up data and do hardware reset only I guess for now.
I would like to roll back that update but it's impossible. Just back up data and do hardware reset only I guess for now.
al...@gmail.com
The December pixel update fixed this issue for me and my wife with pixel 5 and pixel 6 pro.
I see a lot of comments here from non-google devices complaining of this bug. The bug is now fixed in android, so if it is not fixed on your other android 12 device, you need to be reaching out to your phone brand (Samsung etc.) Support to ask them to push the latest android patches from Google.
It is still crazy that this bug went unfixed from beta to stable but as it stands it is fixed now.
I see a lot of comments here from non-google devices complaining of this bug. The bug is now fixed in android, so if it is not fixed on your other android 12 device, you need to be reaching out to your phone brand (Samsung etc.) Support to ask them to push the latest android patches from Google.
It is still crazy that this bug went unfixed from beta to stable but as it stands it is fixed now.
al...@gmail.com
*android 13
za...@gmail.com
Please remove all malware and spyware bugs from my phone
On Thu, Dec 29, 2022, 5:22 PM <buganizer-system@google.com> wrote:
On Thu, Dec 29, 2022, 5:22 PM <buganizer-system@google.com> wrote:
ru...@gmail.com
I have same issue when reconnecting to a Freestyle Libre 2 blood sugar sensor. This is a serious problem for diabetics that require to get alarms from this BLE device. My device: Samsung Z flip 3 Android 13
pi...@gmail.com
I have the Google Pixel 7 Pro and Bluetooth is still having hard time keeping connection with many of my Bluetooth items. My car radio for phone and music is worthless with my pixel phone but wife's Motorola Edge with Android 12 connects flawlessly to the Bluetooth car radio. Soo those of you who say the problem was fixed with the December update are I guess lucky because it is not fixed on Googles flagship phone.
il...@gmail.com
Reporting issue happens on a pixel 5 Android 13, with a cheap smartwatch. After an hour it gets blocked, can't reconnect until reboot. Tested against another phone brand and it works there without this issue.
ni...@gmail.com
Once again breaking things in userspace. Samsung Z Fold 3 was pushed and it broke Fitbit pairing, pairing to my car (which is important for a Tesla but there are backup ways to start the vehicle).
Pretty sad that Fitbit a Google company now is so disjointed. Android devs just change things without care. Same for WiFi control apis but whatever.
I had a pixel I didn't want to leave android but I'm being pushed further away. I'd rather end up with a pinephone than IOS.
Pairing devices is a temporary and short lived fix for some devices that speak the way Android 13 now demands.
Pretty sad that Fitbit a Google company now is so disjointed. Android devs just change things without care. Same for WiFi control apis but whatever.
I had a pixel I didn't want to leave android but I'm being pushed further away. I'd rather end up with a pinephone than IOS.
Pairing devices is a temporary and short lived fix for some devices that speak the way Android 13 now demands.
il...@gmail.com
Testing December update on pixel 5, I report that the issue is gone now with a cheap smartwatch where the issue happened on a13 former patch level.
Now it works as expected here.
Now it works as expected here.
po...@gmail.com
Having issue after 13 update on my Galaxy a32 5g. Connecting to my paired Jabra Move 1.0 headset does not automatically stream audio to the headset like it used to. Have to manually toggle on sound in BT settings every time I connect.
mr...@gmail.com
Samsung S20FE using Libre 2 Continuous Glucose Monitor for type 1 diabetes, the latest phone update in Canada made the app unreliable and no longer get life saving alerts. Already had a half dozen lows glucose levels that didn't get noticed until symptoms were dangerous. Started googling and see this was reported first in August and I'm absolutely appalled that an emergency fix wasn't applied long ago.
ge...@gmail.com
HI there, I have a samsung S22 and am using the libre 2 also........ ever since android 13 update, the connectivity is crap and i cannot depend on the bluetooth being connected....... it's horrible, like i'm back in the stone ages!
al...@gmail.com
Comment has been deleted.
ja...@gmail.com
I'm an end user and we need alert for glucose sensor. As a test, we enabled dev options and switched Bluetooth AVRCP from 1.5 to 1.4
Alerts started working immediadelty. So AVRCP is a hint.
Alerts started working immediadelty. So AVRCP is a hint.
or...@gmail.com
My Garmin watch now disconnecting from Xiaomi 12 10-15 times a day since updated to Android 13
bl...@gmail.com
Same problem here, Panasonic link2cell that used to worked fine now can't pair to Pixel 6a since january security update (TQ1A.230105.001.A2). Tried AVRCP 1.4 whitout success.
sc...@gmail.com
$ adb shell
device_config put bluetooth INIT_gatt_robust_caching_client false
Miight help; this allows various smart watches to work again with recent Android 13.
03...@gmail.com
@
sc...@gmail.com
it reverts
mr...@gmail.com
My initial comment is #219. After reading
lk...@gmail.com
@
Our products have the Database Hash characteristic, so I guess this will not make any difference for us or other products which have the characteristic.
Our products have the Database Hash characteristic, so I guess this will not make any difference for us or other products which have the characteristic.
bl...@gmail.com
Just tried device_config put bluetooth INIT_gatt_robust_caching_client false
It doesn't make a difference, Panasonic KX-TG7644M show as paired on the Pïxel 6a but not on the Panasonic KX-TG7644M. When I tried to connect the Panasonic phone from the Pixel, it obviously doesn't work as the Panasonic has no pairing, this all happen after the TQ1A.230105.001.A2 update. Didn't find out how to revert this security update.
It doesn't make a difference, Panasonic KX-TG7644M show as paired on the Pïxel 6a but not on the Panasonic KX-TG7644M. When I tried to connect the Panasonic phone from the Pixel, it obviously doesn't work as the Panasonic has no pairing, this all happen after the TQ1A.230105.001.A2 update. Didn't find out how to revert this security update.
ni...@gmail.com
In the time dealing with this bug I found my blood pressure and blood sugar testing devices also failing to sync on a regular basis. Also my smart scale.
I have found anything with an audio profile connects but anything that needs to push data is broken.
Insanely frustrating that Samsung pushed Android 13 without a fix applied... Especially since Google had many weeks pushing one to some Pixel devices.
Whoever is running Android Dev is breaking too many things version to version. Changing UI for absolutely no reason. I guess that's the only benefit to iOS they don't change round and square and whatever other ugly UI changes. Breaking usability is a no no.
I have found anything with an audio profile connects but anything that needs to push data is broken.
Insanely frustrating that Samsung pushed Android 13 without a fix applied... Especially since Google had many weeks pushing one to some Pixel devices.
Whoever is running Android Dev is breaking too many things version to version. Changing UI for absolutely no reason. I guess that's the only benefit to iOS they don't change round and square and whatever other ugly UI changes. Breaking usability is a no no.
vi...@google.com
da...@gmail.com
Dexcom G6 CGM blood sensor, A53 , november security patch. Disconnects after a few hours. This is a big problem for anyone using always on devices pushing (vital) data
bl...@gmail.com
I wonder why the status of this issue still show "Assigned" after all that time. This is a severity level 1 and nobody at Google seems to care to inform us of any development on this.
Please move away from "Assigned" to "In Progress" and show us you're working on it.
HELLO GOOGLE - IS THERE ANYBOBY OUT THERE !!!
Please move away from "Assigned" to "In Progress" and show us you're working on it.
HELLO GOOGLE - IS THERE ANYBOBY OUT THERE !!!
ma...@gmail.com
HELLO GOOGLE - IS THERE ANYBOBY OUT THERE !!!
br...@gmail.com
Im on TQ1A.230105.002 and also still having the same issues.
da...@gmail.com
Just wanted to add that #226 has fixed my problem with pairing my Huawei Watch Fit. I was without a solution for this for weeks and wasn't sure what to do.
gh...@gmail.com
#266 didn't work
hp...@gmail.com
Issue also exists with A22 5g
mr...@gmail.com
Follow up to
After a carb miscalculation and too high insulin dose last night, and absolutely nothing from the developers after months of this issue being reported, I think this issue should be escalated to a team that can actually resolve it before someone dies or ends up in a diabetic coma.
After a carb miscalculation and too high insulin dose last night, and absolutely nothing from the developers after months of this issue being reported, I think this issue should be escalated to a team that can actually resolve it before someone dies or ends up in a diabetic coma.
je...@gmail.com
since android 13 update can not connect to tesla phone key. Have a samsung zfold 3. can connect an iphone but not an android to tesla s model
je...@gmail.com
just connected to a model 3 but cannot connect to model s
da...@gmail.com
Follow up on my previous comment.
It seems that for some reason the original setting returns back to true and I have to plug back my phone and do the adb shell command again and then it will work.
You guys need to fix this.
It seems that for some reason the original setting returns back to true and I have to plug back my phone and do the adb shell command again and then it will work.
You guys need to fix this.
ld...@gmail.com
Makes the fold 4 useless as a key for a Tesla Model-X.
ro...@gmail.com
New Samsung A33 problems bluetooth since update to android 13 in november 2022!
Very dissapointed in Android/google at the moment!
FIX THIS SOON!!!
Give us new software update!
Very dissapointed in Android/google at the moment!
FIX THIS SOON!!!
Give us new software update!
ld...@gmail.com
The January security update fixed my Tesla issue with the Fold 4 not being u8sable as a key
vi...@google.com
As requested earlier in
- adb shell setprop persist.bluetooth.btsnooplogmode full
- adb shell device_config put bluetooth INIT_logging_debug_enabled_for_all true
For information, Snoop logs can also be enabled using the instructions provided here:
el...@gmail.com
I'm having similar issues with Oneplus 8T and Polar H10 heart rate sensor. Cannot get heart rate data from sensor to my phone.
ka...@gmail.com
I also have problems with Polar H10 heart rate sensor and OnePlus 8.
pa...@gmail.com
Samsung A51 5G and Android 13, problems with Freestyle glycose continuous sensor.
Connection lost after some minutes to 4 hours.
Back to S7 and Android 8.
Connection lost after some minutes to 4 hours.
Back to S7 and Android 8.
da...@gmail.com
The problem remains on my S20 and is a serious medical problem. I have to turn BT Off and back On when I see the red alarm flag on LibreLink (used with Abbots Libre 2 glucose sensor). This is serious as it sometimes fails during the night and hence no low-sugar alarm is sent.
ed...@gmail.com
Samsung S21 5G with Android 13, using the FreeStyle LibreLink App. Because i use this to get Alarms on low sugar this i a serious problem and needs to be fixed ASAP!
Now it can happen that the values are low and no Alarm is given which then can lead to serious medical issues.
Now it can happen that the values are low and no Alarm is given which then can lead to serious medical issues.
be...@gmail.com
This issue has been resolved for me in the Jan 2023 security update - Samsung A52 5G on security patch level 1 January 2023.
bl...@gmail.com
Anyone knows if this bug is fix in QPR2 Beta 2.1 ?
eb...@stewartclan.net
Just adding on here that BT connection between PixelPro 6 and 2011 Toyota Prius (phone AND multimedia player) broke after the 1/5 security update.
kh...@gmail.com
I have used my Phonak hearing aids with my Samsung 8+ for a couple of years with zero issues. Not sure, but I believe it is running Android 11. I bought the Pixel 7 Pro and have always had it randomly stop sending any sound to the hearing aids even though it says it is connected. Since the last update in January, it now randomly disconnects altogether and won't reconnect until I reboot the hearing aids or phone. The hearing aids still work on the S8+, and work with my Amazon Fire HD8 tablet. The pixel connects to my GMC truck just fine. I have wanted the Pixel since it first came out, having had a couple of Nexus phones before, but now I'm sorry I upgraded so soon. I may have to go back to my S8+ as I rely heavily on my hearing aids.
vi...@gmail.com
Adding to the list. Note 20 ultra on the lastest update push for it as of Jan 2023. Device will not stay connected to my car radio for more than a few seconds. Will automatically reconnect but then disconnect. Just keeps doing that indefinitely. Also have my phone connected to a pair of hearing aids that seems to work most of the time. After a week of usage I have to reboot my phone to get audio on them again.
vi...@google.com
Please provide the information requested in
lp...@gmail.com
Samsung A52 5G alarms not working for FreeStyle Libre 2 need fix fast
kl...@googlemail.com Restricted+
Restricted+
ju...@gmail.com
Same as told in
Please, fix this ASAP. It is a Major health matter, and could become a matter of life or dead easily.
Please, fix this ASAP. It is a Major health matter, and could become a matter of life or dead easily.
ol...@gmail.com
polar h10 hasn't worked since update to android 13.
hear rate monitor polar can't be used during muay thai trainings
hear rate monitor polar can't be used during muay thai trainings
an...@gmail.com
My Polar H10 started working again with today's Pixel update. Sadly my H6s still don't work with Strava.
ca...@gmail.com
Can anyone confirm if this fixes Tesla Key
tr...@gmail.com
Comment has been deleted.
vi...@google.com
For further investigation, we would need the BT Snoop logs and a complete bug report (preferably from a Pixel device) as suggested in
ro...@gmail.com
still having issue on galaxy s20
kl...@googlemail.com Restricted
Restricted
kl...@googlemail.com
With this comment you will find bugreports in response to
My Pixel 6 with Andoid 13 (Februry Update) ( called P6) has still problems to reconnect with my car (Polestar 2) (called P2) to work as digital key for the car. The bugreports reflect the following situations:
Timestamp Situation
10-14-05 P6 "Not connected" because large distance to P2. (Ok) 11-02-49 P6 "Connected" near to P2. Car can be opened, locked and started with P6 as digital key. (Ok) 17-27-17 P6 "Not connected" near to P2. (Bug) 17-31-33 P6 "Connected" after "flightmode on/off". Car can be opened, locked and started with P6 as digital key. (Ok)
Please give feedback, if the bugreports are helpful for you or if you need more/other informations.
kl...@googlemail.com
Better formatted description of the different bugreports in
Timestamp Situation
10-14-05 P6 "Not connected" because large distance to P2. (Ok)
11-02-49 P6 "Connected" near to P2. Car can be opened, locked and started with P6 as digital key. (Ok)
17-27-17 P6 "Not connected" near to P2. (Bug)
17-31-33 P6 "Connected" after "flightmode on/off". Car can be opened, locked and started with P6 as digital key. (Ok)
vi...@google.com
Re-
kl...@googlemail.com
Re-
Please give feedback, if the bugreports are helpful for you or if you need more/other informations.
vi...@google.com
Re-
re...@gmail.com
jr...@gmail.com
Pixel 7, with pixels buds keep dropping Bluetooth when buds are removed from the case with android 13.0
e....@akveo.com
Hi everybody,
Probably the same issue with:
2109119DG - Xiaomi 11 Lite 5G NE
Probably the same issue with:
2109119DG - Xiaomi 11 Lite 5G NE
gf...@googlemail.com
Still same issue with my hearing aids. Not able to connect or instantly disconnect on A14 with January update.
wi...@gmail.com
I cant do much Im hacked from every thing. In google to microsoft
Dagoberto Lopez
On Wed, Feb 15, 2023, 6:55 AM <buganizer-system@google.com> wrote:
Dagoberto Lopez
On Wed, Feb 15, 2023, 6:55 AM <buganizer-system@google.com> wrote:
mi...@gmail.com
The same with Ford C-Max, Sync Connection and A22 after A13 Update
da...@gmail.com
Polar HR sensor h10 not transmitting heartrate since update of Asus Zenfone 9 to Android 13. This is very frustrating.
mi...@gmail.com
February security update solved my bluetooth issues with Dexcom G6 and Garmin watch
pb...@gmail.com
Devices used:
Samsung XCover 5 Android 13
Insulin pump: Accu-Chek Combo,
Sensor: Dexcom G6:
Smart watch Moto 360 3rd gen.
The BT problem still occurs, no improvement.
The error message 'Authentication error' appears regularly on the smartphone. at Combo & Dexcom.
After switching off / on everything runs normally again, as if nothing had happened.
Occurs 2-3 times a day as well.
Especially annoying at night when you're asleep and the 'no connection' alerts you.
With the Moto 360, the watch must always be re-paired after the watch is switched on.
Here the smartphone does not recognize the old pairing.
Also very annoying.
Already tried everything with cache deletion in the APP's and in the BT.
Didn't bring any improvement.
Why can't you import the BT stack from Android 12, everything worked fine there.
I had to restart my cell phone at most once a month.
Now it's 2-3x a day.
Samsung XCover 5 Android 13
Insulin pump: Accu-Chek Combo,
Sensor: Dexcom G6:
Smart watch Moto 360 3rd gen.
The BT problem still occurs, no improvement.
The error message 'Authentication error' appears regularly on the smartphone. at Combo & Dexcom.
After switching off / on everything runs normally again, as if nothing had happened.
Occurs 2-3 times a day as well.
Especially annoying at night when you're asleep and the 'no connection' alerts you.
With the Moto 360, the watch must always be re-paired after the watch is switched on.
Here the smartphone does not recognize the old pairing.
Also very annoying.
Already tried everything with cache deletion in the APP's and in the BT.
Didn't bring any improvement.
Why can't you import the BT stack from Android 12, everything worked fine there.
I had to restart my cell phone at most once a month.
Now it's 2-3x a day.
mi...@gmail.com
Still no success on Dexcom G6 testing through multiple apps.
Android 13 with Security Update: Feb 5, 2023
[Deleted User] <[Deleted User]>
Learning how to code buildapps
jo...@student.aiuonline.edu
Add
sa...@gmail.com
Mobile legends
pa...@gmail.com
Is it just me or is the issue back again in the latest official release? 13 (TQ1A.230205.002). Was gone for about two months but now issue occurs frequently again.
ju...@gmail.com
Abbott announced that they solved this problem and released a new Libre 3 App version, but nobody knows how they fixed
li...@gmail.com
To all diabetics using android 13 and freestyle libre, I can confirm that the latest version of the FreeStyle LibreLink App 2.8.4 is now compatible with Android OS 13. I installed it 4 days ago and since then the only sigal loss alarms are when I'm genuinely out of range of my phone. I'm using Samsung S22 with android 13 One UI 5.0 and Freestyle libre 2.
Thanks Abbott!!! 😁
If any Samsung users can confirm it works with One UI 5.1 I'd be interested, I'm scared to update my operating system now!
Thanks Abbott!!! 😁
If any Samsung users can confirm it works with One UI 5.1 I'd be interested, I'm scared to update my operating system now!
co...@punchthrough.com
Are there any Abbott Android devs in this thread? It'd be awesome if you could share what you did to work around these issues so other developers can follow suit. Thanks in advance!
ja...@gmail.com
My son has Galaxy A23, Android 13 and Libre 2. Latest update from Abbot restored full functionality.
mi...@gmail.com
While I do not expect a reply I did write Abbott at their app developer email on Google Play. I also hope there is someone willing at Abbott that may help provide more understanding or help to fix it in other medical apps.
mr...@gmail.com
In Pixel-7 with Feb-2023 Update, this issue did not reproduce. Can you please let us know the commit for the fix?
sh...@outlook.com
I have problem with Bluetooth after feb update/ Pixel 4 - bluetooth dont turn on. apps keeps stopping
he...@gmail.com
My Samsung Galaxy Z Flip4 also had the problem with the Freestyle Libre 2 sensor-alerts for 2 months. Updating the LibreLink app to 2.8.4 helped.
ro...@gmail.com
Sony xperia 10 III after update to 62.2.A.0.367 does not communicate with polar H10 HRM
jo...@gmail.com
yeah thnx no connection possible with my garmin
pe...@gmail.com
Sony xperia 10 IV after update to 65.1.A.4.8 does not communicate with polar H10 HRM
gh...@gmail.com
I'm on Android Feb security update, and the problem remains.
mi...@gmail.com
My Anker Liberty Air 2 work on the Feb 2023 update, but other devices like Dexcom G6 from any app available to work through bluetooth does not. Possibly a difference of Bluetooth LE?
mr...@gmail.com
Libre 2 Canada users: there are two Libre 2 apps. The one we have installed is apparently discontinued, as there's no update passed 2.8.2. You will need to install the OTHER Libre 2 app from Google Play to get the 2.8.4 update that solves this problem: https://www.freestyleandroid.com/ca-en/home.html
jo...@gmail.com
Has this been fixed?
ro...@gmail.com
still no fix today on sony xperia 10 III. Sony bames the BLE device manufacturers, polar blames sony/google.
nm...@cochlear.com
|
| Libre 2 Canada users: there are two Libre 2 apps. The one we have installed is apparently discontinued, as there's no update passed 2.8.2. You will need to install the OTHER Libre 2 app from Google Play to get the 2.8.4 update that solves | this problem:
From looking at the app, it looks like they're not relying on the underlying issue being fixed, but have an alarm that fires every couple of minutes, presumably to keep track of whether the BLE connection remains active.
mi...@gaia-group.com
Still no fix today on Nokia X10. The most recent Android version (Build number 00WW_3_370) still can't connect to Polar H10.
kl...@googlemail.com
re-
ma...@gmail.com
I have similar issues with Realme GT NEO2 and Polar H10 heart rate sensor. It cannot get heart rate data from the sensor to my phone.
fa...@gmail.com
Polar H10 HRM + Sony Xperia IV 10 still broken. Device can be scanned but no data is transmitted
mi...@gmail.com
Still broken. Just moved back to android (Pixel 7) from iPhone and this is a major annoyance. Drops from watch and any audio device on average every 5-10 minutes. Latest builds on all devices.
se...@gmail.com
same issue. Samsung Galaxy S23 Ultra (SM-S918B) running Android 13. My hearing aids are no longer connected by the Oticon app. the app "sees" the devices, but can no longer pair them.
wj...@gmail.com
Samsung galaxy S22. Headset will not automatically connect to audio, just calls. I have to manually go to media output and force it to connect and it takes several tries. This phone got the update yesterday and now it's just annoying AH!
se...@gmail.com
Non riesco a connettere il sensore cardiaco polar H10 mi dice che e collegato ad un altra app ma non è cosi
se...@gmail.com
Comment has been deleted.
ol...@gmail.com
Polar H10 sensor is still don't working properly
Xiaomi mi12lite
Miui 14
Android 13
Xiaomi mi12lite
Miui 14
Android 13
ei...@gmail.com
Polar H10 sensor either not connecting on when connected heart rate data is not shown.
Xiaomi Mi 11 Lite
MIUI 14
Android 13
Works on pixel 6a however
Xiaomi Mi 11 Lite
MIUI 14
Android 13
Works on pixel 6a however
ee...@essenberg.net
Same issue, OnePlus 8T. Worked perfectly with Android 12, broken since Android 13, including the late-Feb 2023 update issued by OnePlus.
kl...@gmail.com
Same issue with op10 pro android 13 and polar h9..... this is insane.
wi...@gmail.com
da...@gmail.com
Any word from any Android devs on here on a workaround? I'm using Ionic with Angular, but using a Capacitor plugin for all BLE stuff. Have been spinning my wheels for a couple days trying to figure out a solution but have come up empty.
cr...@gmail.com
Just getting in line. This issue has recently started effecting both my own Pixel 7 Pro and my wife's Galaxy S21 FE. The issue exists both with my Volkswagen and my Galaxy Watch 5.
ch...@gmail.com
I lost BT function with my Starkey Hearing Aids as soon as I updated to Android 13, the first week of January. My cell phone provider does not allow rolling back to Android 12 or I would gladly do so. This is a major issue for me. My phone is a Galaxy S21 5G. Starkey support says that it is Google's responsibility to fix it.
ma...@gmail.com
Pixel 7 user with type one diabetes and Abbott Freestyle Libre glucose sensors. This is impacting my health and might lead to serious harm. This used to work perfectly before Android 13.
c....@gmail.com
This Problem exists until the Android 13 release and isn't fixed. I use my Pixel 4a with Android 12 until this is fixed. I am an embedded Software engineer. Furthermore, I develop Software for any kind of hardware component. If you need help on resolving this issue soon, you can hire me. I would only need 1 month to fix this issue if all the necessary tools and information will be provided to me.
pl...@gmail.com
The sad and annoying thing is, that these posts come from people who inform themselves about this fault and find this issue tracker at all... There are many-many more with the same problem who doesn't even know where to report it, so Google can sweep it under the rugs, because "only so many" error reports come in.
ka...@gmail.com
The sad and annoying thing is that this was found in beta and they still released next version without first fixing it. Like connecting to vital BT devices (car charges, hearing aids) is a 'could have'.
lu...@gmail.com
After pairing, rename bluetooth device profile name. I have Xiaomi Mi Watch, I renamed bluetooth device profile to MiColorSD14C and working after I restart phone.
ni...@gmail.com
Nothing Phone (1) user here, worked perfectly fine until the OS upgraded to Android 13, now in one of the 2 cars I regularly drive, I have to disconnect and reconnect BT almost every time (often multiple times) until the phone audio works.
It is unbelievable to me how long this issue is known, and still no reliable fix.
Please folks, P1 priority tag is nice, but can we get an update or something?
It is unbelievable to me how long this issue is known, and still no reliable fix.
Please folks, P1 priority tag is nice, but can we get an update or something?
pi...@gmail.com
Maybe we should all band together find a lawyer and file a class action lawsuit to get them to fix the problem they created that effects so many peoples devices making them unreliable to use.
iv...@gmail.com
The handling of this issue is really embarrassing, for Google and e.g. my phone vendor Samsung. Samsung plays out (tickets are ignored/unanswered/provide solutions that I had tried over and over) and they are neither intersted nor capable of addressing this to Google IMHO.
And Google themselves do not provide any update here. P1 bug, yeah. For me, "only" car bluetooth is unreliable, it is a pain in the neck, but ok... But it is a really big, big problem for all those users being reliant on medical devices like hearing aids or glucose sensors. It's a shame!
And Google themselves do not provide any update here. P1 bug, yeah. For me, "only" car bluetooth is unreliable, it is a pain in the neck, but ok... But it is a really big, big problem for all those users being reliant on medical devices like hearing aids or glucose sensors. It's a shame!
th...@gmail.com
How is it that this has been a problem since August 2022 and still hasn't been fixed? This is more than stupid. Chine on Google!u
vi...@google.com
Re-comments: #323, #325, #326 : For further investigation we would need a bugreport, requesting the Pixel users to share a full bugreport.
c....@gmail.com
Reply to #334:
Please share a link to a manual on how to create a bug report.
Please share a link to a manual on how to create a bug report.
co...@punchthrough.com
vi...@google.com
Yes, you can refer to the link:
th...@gmail.com
Recorded from adb with esp32 and Google pixel. Not seen for earlier Android versions:
04-19 11:13:14.773 1138 14230 I bthal.flowcontrol: HciEventPreProcess: HCI Event 0xff Opcode 0 Length 250 unhandled by debug_VendorEvent
04-19 11:13:14.773 14179 14236 W smp_act : packages/modules/Bluetooth/system/stack/smp/smp_act.cc:2033 smp_link_encrypted: SMP state machine busy so skipping encryption enable:0 device:xx:xx:xx:xx:97:9b
04-19 11:13:14.773 14179 14236 E bt_bta_dm: packages/modules/Bluetooth/system/bta/dm/bta_dm_act.cc:3330 bta_dm_encrypt_cback: Failed to encrypt link peer:xx:xx:xx:xx:97:9b transport:BT_TRANSPORT_LE status:BTM_FAILED_ON_SECURITY callback:T
04-19 11:13:14.773 14179 14236 W bt_btif : packages/modules/Bluetooth/system/main/bte_logmsg.cc:194 LogMsg: btif_gatt_set_encryption_cb() - Encryption failed (1)
04-19 11:13:14.773 14179 14203 E bt_btif_gattc: packages/modules/Bluetooth/system/btif/src/btif_gatt_client.cc:248 btif_gattc_upstreams_evt: Unhandled event (17)!
04-19 11:13:14.774 14179 14236 E bt_btu_hcif: packages/modules/Bluetooth/system/stack/btu/btu_hcif.cc:204 btu_hcif_log_event_metrics: Unexpectedly received event_code:0xff that should not be handled here
04-19 11:13:14.774 14179 14236 W bt_stack: [WARNING:btif_bqr.cc(431)] Appro LSTO , Handle: 0x0041, DH1, Central, PwLv: 11, RSSI: -46, SNR: 0, UnusedCh: 26, UnidealCh: 0, ReTx: 1, NoRX: 0, NAK: 3, FlowOff: 0, OverFlow: 0, UndFlow: 0, TxTotal: 0, TxUnAcked: 0, TxFlushed: 0, TxLastSubEvent: 0, CRCError: 0, RxDuplicate: 0
04-19 11:13:14.774 14179 14236 E bluetooth: packages/modules/Bluetooth/system/stack/btm/btm_sco.cc:950 btm_sco_on_disconnected: Unable to find sco connection
04-19 11:13:14.774 14179 14236 I btm_acl : packages/modules/Bluetooth/system/stack/acl/btm_acl.cc:2567 btm_acl_iso_disconnected: ISO disconnection from GD, handle: 0x41, reason: 0x3d
04-19 11:13:14.775 14179 14236 I bluetooth: packages/modules/Bluetooth/system/stack/eatt/eatt_impl.h:893 disconnect: Device: 44:3b:d8:56:97:9b, cid: 0xffff
04-19 11:13:14.775 14179 14236 W bt_stack: [WARNING:eatt_impl.h(897)] disconnect no eatt device found
04-19 11:13:14.775 14179 14236 I bluetooth: packages/modules/Bluetooth/system/stack/gap/gap_ble.cc:303 client_connect_cback: No active GAP service found for peer:xx:xx:xx:xx:97:9b callback:Disconnected
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:3 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:4 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:5 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:6 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:7 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:8 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 W bt_btm_sec: packages/modules/Bluetooth/system/stack/btm/btm_sec.cc:3755 btm_sec_disconnected: Got uncommon disconnection reason:Unknown Error[3d] handle:0x0041 comment:stack::acl::btm_acl::btm_acl_disconnected
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 3
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 4
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 5
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 6
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 7
04-19 11:13:14.773 1138 14230 I bthal.flowcontrol: HciEventPreProcess: HCI Event 0xff Opcode 0 Length 250 unhandled by debug_VendorEvent
04-19 11:13:14.773 14179 14236 W smp_act : packages/modules/Bluetooth/system/stack/smp/smp_act.cc:2033 smp_link_encrypted: SMP state machine busy so skipping encryption enable:0 device:xx:xx:xx:xx:97:9b
04-19 11:13:14.773 14179 14236 E bt_bta_dm: packages/modules/Bluetooth/system/bta/dm/bta_dm_act.cc:3330 bta_dm_encrypt_cback: Failed to encrypt link peer:xx:xx:xx:xx:97:9b transport:BT_TRANSPORT_LE status:BTM_FAILED_ON_SECURITY callback:T
04-19 11:13:14.773 14179 14236 W bt_btif : packages/modules/Bluetooth/system/main/bte_logmsg.cc:194 LogMsg: btif_gatt_set_encryption_cb() - Encryption failed (1)
04-19 11:13:14.773 14179 14203 E bt_btif_gattc: packages/modules/Bluetooth/system/btif/src/btif_gatt_client.cc:248 btif_gattc_upstreams_evt: Unhandled event (17)!
04-19 11:13:14.774 14179 14236 E bt_btu_hcif: packages/modules/Bluetooth/system/stack/btu/btu_hcif.cc:204 btu_hcif_log_event_metrics: Unexpectedly received event_code:0xff that should not be handled here
04-19 11:13:14.774 14179 14236 W bt_stack: [WARNING:btif_bqr.cc(431)] Appro LSTO , Handle: 0x0041, DH1, Central, PwLv: 11, RSSI: -46, SNR: 0, UnusedCh: 26, UnidealCh: 0, ReTx: 1, NoRX: 0, NAK: 3, FlowOff: 0, OverFlow: 0, UndFlow: 0, TxTotal: 0, TxUnAcked: 0, TxFlushed: 0, TxLastSubEvent: 0, CRCError: 0, RxDuplicate: 0
04-19 11:13:14.774 14179 14236 E bluetooth: packages/modules/Bluetooth/system/stack/btm/btm_sco.cc:950 btm_sco_on_disconnected: Unable to find sco connection
04-19 11:13:14.774 14179 14236 I btm_acl : packages/modules/Bluetooth/system/stack/acl/btm_acl.cc:2567 btm_acl_iso_disconnected: ISO disconnection from GD, handle: 0x41, reason: 0x3d
04-19 11:13:14.775 14179 14236 I bluetooth: packages/modules/Bluetooth/system/stack/eatt/eatt_impl.h:893 disconnect: Device: 44:3b:d8:56:97:9b, cid: 0xffff
04-19 11:13:14.775 14179 14236 W bt_stack: [WARNING:eatt_impl.h(897)] disconnect no eatt device found
04-19 11:13:14.775 14179 14236 I bluetooth: packages/modules/Bluetooth/system/stack/gap/gap_ble.cc:303 client_connect_cback: No active GAP service found for peer:xx:xx:xx:xx:97:9b callback:Disconnected
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:3 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:4 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:5 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:6 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:7 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 I bt_bta_gattc: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_act.cc:1249 bta_gattc_conn_cback: Disconnected att_id:8 addr:xx:xx:xx:xx:97:9b, transport:BT_TRANSPORT_LE reason:UNKNOWN[61]
04-19 11:13:14.775 14179 14236 W bt_btm_sec: packages/modules/Bluetooth/system/stack/btm/btm_sec.cc:3755 btm_sec_disconnected: Got uncommon disconnection reason:Unknown Error[3d] handle:0x0041 comment:stack::acl::btm_acl::btm_acl_disconnected
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 3
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 4
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 5
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 6
04-19 11:13:14.776 14179 14236 E bta_gattc_main: packages/modules/Bluetooth/system/bta/gatt/bta_gattc_main.cc:395 bta_gattc_hdl_event: Ignore unknown conn ID: 7
bi...@gmail.com
9 months later, no solution, no workaround, just "send a report". I think that for 9 months, there is enough report to do something. I was always anti-iphone, but now I think it will be my next. Since this stupid Android 13 update, I can't do anything with bluetooth on my S22 Ultra. I have a smartwatch that is disconnected 98% of the time, no android auto, no headphones, etc.
In fact, I just wonder what you do with your days?
In fact, I just wonder what you do with your days?
p....@centrum.cz
Totally agreed with
Yet, despite what it looks like, I want to believe that Google actually works on this and while they totally fail to communicate, they will "silently" prepare some kind of fix eventually. This reminds me of
To add some practical finding, this issue also seems to affect phones with the
wi...@gmail.com
vi...@google.com
We believe the issue has been fixed and is no longer reproducible. We recommend Pixel users to check the issue on the latest Android version and feel free to create a new bug along with the relevant details if you encounter it again. Whereas, the non-Pixel users using Samsung, Xiaomi etc we recommend them to reach out to their respective OEM's.
hi...@gmail.com
This is not fixed. I am still encountering this issue on the latest build for Pixel 7 Pro. Issue began for me on the March update.
ma...@gmail.com
Not fixed here either... Hold on!
Pixel 7 user here...
I freaking love it when I walk up to my Tesa looking like idiot trying to get in and it doesn't unlock... I have to turn off the Bluetooth and turn it back on.
Pixel 7 user here...
I freaking love it when I walk up to my Tesa looking like idiot trying to get in and it doesn't unlock... I have to turn off the Bluetooth and turn it back on.
pi...@gmail.com
You have to be kidding. It is not fixed. My pixel 7 pro will not stay connected to my car radio. Connects and plays music, disconnects a few minutes later. Reconnects then disconnects again over and over. This did not happen until after android update. Google fix this dam problem you created already.
ma...@gmail.com
I encourage all Pixel users that gets a notification to please go to this thread and comment if your issue is not resolved. This is nuts.
mi...@gmail.com
So one of the steps to get this fixed was to help Google see the logs of whenr this happens on their Pixel devices. Maybe we already have such a port already? Those noting issues especially on Pixels should be the ones providing the logs so Google will fix it for everyone. I guess we can revert changes in AOSP to the Bluetooth stack in Android 12 which worked, but I'd have to look at why they originally did that change in Android 13 and why. Pixel devices people, you can really help show the bug using logcat as it happens.
mi...@gmail.com
So one of the steps to get this fixed was to help Google see the logs of whenr this happens on their Pixel devices. Maybe we already have such a post already? Those noting issues especially on Pixels should be the ones providing the logs so Google will fix it for everyone. I guess we can revert changes in AOSP to the Bluetooth stack in Android 12 which was working, but I'd have to look at why they originally did that change in Android 13 and why. Pixel devices people, you can really help by showing the bug using logcat as it happens.
fi...@gmail.com
Not fixed here either, I still have to jump through hoops to get my Pokemon Go Plus to connect to my Pixel 6 Pro every morning. After that it's usually fairly okay the rest of the day, but every morning that first connection will not go through properly unless I specifically start the connection in Pokemon Go, quickly switch over to my device settings and select to pair new device, and then quickly switch back over to the open Pokemon Go app where it then takes upwards of 30 seconds for the "Pair and connect" box to finally show up. If I don't do that or my timing is a little too slow, it throws that "wrong passkey" or "device not recognized" note and I have to completely restart the phone to try it again.
zh...@gmail.com
I have problems still with my Tile trackers and Phone as a Key for my Ford.
On Thu, May 18, 2023, 10:16 AM <buganizer-system@google.com> wrote:
On Thu, May 18, 2023, 10:16 AM <buganizer-system@google.com> wrote:
an...@gmail.com
Not true - this is not yet fixed. Polar H6 still don't work with my Pixel Pro 7. And my Volvo XC40 is requesting reconnection regularly. Closing a bug & asking people to resubmit is the oldest wheeze in the business.
vi...@google.com
Re-comments #343, #344, #345, #349, #350, #351. Requesting the users to share a bugreport for further investigation.
hi...@gmail.com
Can you share the exact steps to capture the bugreport you need?
vi...@google.com
For steps to capture a bug report, please refer:
In addition, before you capture bugreport we recommend to Enable Bluetooth HCI snoop logs option by following the below steps:
- Settings -> System -> Advanced -> Developer options -> Enable Bluetooth HCI snoop logs -> Enable
- turn off BT
- on/off airplane mode
- turn on BT
- Start to reproduce, take bugreport when issue occurs.
iv...@gmail.com
> [...] We recommend Pixel users to check the issue on the latest Android version [...]
Could you please provide any exact version ids that are supposed to contain this fix?
pi...@gmail.com
Hey Google how bout you set up and let us roll back to android 12 until you can fix the problem. Simple😎
je...@gmail.com
an...@gmail.com
Bur report attached. Love publishing 20 MB of my sensitive data to the Interwebs?
Recommend getting your hands on a Polar H6. This works with Android 12 and with current iPhones. It is visible using NRF Connect on my Android 13 Pixel 7 Pro running TQ2A.230505.002, but cannot be paired in Strava, Polar Flow or Polar Beat. Given I have two (now useless) of these devices and have produced the same symptoms across my Pixel 7 Pro, My son's Pixel 5 and my daughters' Pixel 4a & Pixel 6 and shown that both work on the Pixel 3 with earlier Android and multiple iOS devices. I can say with some justification that whatever this bug is, it is most definitely not fixed. This in additional to other unreliable behaviour (e.g. random XC40 requests to repair).
Recommend getting your hands on a Polar H6. This works with Android 12 and with current iPhones. It is visible using NRF Connect on my Android 13 Pixel 7 Pro running TQ2A.230505.002, but cannot be paired in Strava, Polar Flow or Polar Beat. Given I have two (now useless) of these devices and have produced the same symptoms across my Pixel 7 Pro, My son's Pixel 5 and my daughters' Pixel 4a & Pixel 6 and shown that both work on the Pixel 3 with earlier Android and multiple iOS devices. I can say with some justification that whatever this bug is, it is most definitely not fixed. This in additional to other unreliable behaviour (e.g. random XC40 requests to repair).
zh...@gmail.com Restricted+
Restricted+
vi...@google.com
Re-
vi...@google.com
Re-
ch...@gmail.com
It is unclear who
kr...@gmail.com
I am now up to 4 different Bluetooth devices that I use every day that continue to have this issue. Three of the devices are health related and causing issues testing or getting metrics that results in lost data. The 4th is getting into my vehicle which continues to be a safety issue. I thought it was an issue with Samsung S23 Ultra because that is when it started. That is also when I started using Android 13 and looks more like that is the source of the issue. Android 13 does not allow clearing cache on Bluetooth app. Not sure if that would help, but we need a faster workaround than rebooting the phone. Nothing like standing in the dark trying to get in your car while you wait for the phone to reboot. Or waking up to realize half of the nights medical tracking data is missing because Bluetooth disconnected in the middle of the night and the device buffer filled up before it could transmit.
zh...@gmail.com
If there is a way for me to share with Google only and not the entire internet, let me know.
vi...@google.com
Re-
vi...@google.com
Re-
zh...@gmail.com
Re-
I believe this bug report, I already had the hci log enabled. I got to my car, the phone would not connect to the Phone as a key (PaaK) in the car. I disabled Bluetooth, re enabled it. The phone connected, I created the hug report.
I believe this bug report, I already had the hci log enabled. I got to my car, the phone would not connect to the Phone as a key (PaaK) in the car. I disabled Bluetooth, re enabled it. The phone connected, I created the hug report.
vi...@google.com
Re-
vi...@google.com
Re-
mm...@gmail.com
And
���� ��� Outlook for Android<https://aka.ms/AAb9ysg >
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Wednesday, May 24, 2023 9:45:31 PM
To: b-system+1794283363@google.com <b-system+1794283363@google.com>
Cc: mmtenez@gmail.com <mmtenez@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
https://issuetracker.google.com/issues/242755161
Changed
vi...@google.com addedhttps://issuetracker.google.com/issues/242755161#comment370 >:
Re-https://issuetracker.google.com/issues/242755161#comment366 >, https://issuetracker.google.com/issues/242755161#comment368 >: Thanks for your input. We�ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
_______________________________
Reference Info: 242755161 Android 13: Unable to reconnect reliably to bonded peripheral
component: Android Public Tracker<https://issuetracker.google.com/components/190923 >
status: Assigned
reporter: co...@punchthrough.com
assignee: ra...@google.com
cc: co...@punchthrough.com, gu...@google.com
type: Bug
priority: P1
severity: S1
blocked by: 195410559<https://issuetracker.google.com/issues/195410559 >, 242968055<https://issuetracker.google.com/issues/242968055 >, 269191378<https://issuetracker.google.com/issues/269191378 >, 283990354<https://issuetracker.google.com/issues/283990354 >, 284197987<https://issuetracker.google.com/issues/284197987 >
blocking: 265919289<https://issuetracker.google.com/issues/265919289 >
hotlist: [AOSP] assigned<https://issuetracker.google.com/hotlists/468531 >, NeedsInfo<https://issuetracker.google.com/hotlists/468606 >
retention: Component default
ReportedBy: Developer
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTrackerhttps://issuetracker.google.com/issues/242755161 > where you have the role: starred.
Unsubscribe from this issue.<https://issuetracker.google.com/issues/242755161?unsubscribe=true >
���� ��� Outlook for Android<
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Wednesday, May 24, 2023 9:45:31 PM
To: b-system+1794283363@google.com <b-system+1794283363@google.com>
Cc: mmtenez@gmail.com <mmtenez@gmail.com>
Subject: Re:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
vi...@google.com added
Re-
_______________________________
Reference Info: 242755161 Android 13: Unable to reconnect reliably to bonded peripheral
component: Android Public Tracker<
status: Assigned
reporter: co...@punchthrough.com
assignee: ra...@google.com
cc: co...@punchthrough.com, gu...@google.com
type: Bug
priority: P1
severity: S1
blocked by: 195410559<
blocking: 265919289<
hotlist: [AOSP] assigned<
retention: Component default
ReportedBy: Developer
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.<
jo...@googlemail.com
Both me and my kid use Libre 2 sensors. This issue still exists and is causing our sensors to disconnect frequently through the day. I still haven't found a reliable way to have them reconnect. Is the only way to downgrade to flash the ROM?
vi...@google.com
Re-
We have found that the bug report has only successful connection and does not see the Bluetooth logs before BT turn OFF and turn ON.
Could you please share the bug report immediately after the issue is observed or request the user to increase the logging buffer size to max available and share the new bug report.
Steps to enable bt_snoop and increase buffer size:
1.Enable Developer options on the device.
2.In the Developer options menu, change the Enable Bluetooth HCI snoop log setting to Enabled.
3.In the "Logger buffer sizes", change the buffer size to "16M"(or highest possible).
4.Restart your phone for logging to take effect
5.Try reproducing your issue again and take a new bugreport
er...@okcuoglu.com
Comment has been deleted.
er...@okcuoglu.com
i have a similar issue on pixel 6.
can connect to bluetooth earpods without any issue.
cannot connect to a tablet with android 10. Bluetooth Versions are the same. Can't also connect to a windows 11 PC.
I've tried every common step, like restart, wipe cache, turn on/off clear cache.
I've also tried to install android 14 beta / remove it back and reinstalled fresh android 13.
No result unfortunately :(
Is there any solution planned?
can connect to bluetooth earpods without any issue.
cannot connect to a tablet with android 10. Bluetooth Versions are the same. Can't also connect to a windows 11 PC.
I've tried every common step, like restart, wipe cache, turn on/off clear cache.
I've also tried to install android 14 beta / remove it back and reinstalled fresh android 13.
No result unfortunately :(
Is there any solution planned?
vi...@google.com
Re-
In addition, before you capture bugreport we recommend Enable Bluetooth HCI snoop logs option and increase the logging buffer size to max available by following the below steps and then share the bugreport:
- Enable Developer options on the device.
- In the Developer options menu, change the Enable Bluetooth HCI snoop log setting to Enabled.
- In the "Logger buffer sizes", change the buffer size to "16M"(or highest possible).
- Restart your phone for logging to take effect.
- Try reproducing your issue again and take a new bugreport.
zh...@gmail.com
re-
Attached is the new report. This morning I set HCI on, and increased the log size to maximum and rebooted the phone. I was able to drive my car to work using the phone as a key without problem. After work today, I went out to my car, and could not get in. I turned Bluetooth off, then on, and the car immediately connected, and I was able to enter. I then immediately captured a full bug report. Additionally, all day I have been getting notices from Tile that it could not find my devices.
The other thing that is annoying is most of the time when I restart Bluetooth, I get a persistent notification that says "Looking for Android Auto". It never goes away without restarting Bluetooth again.
https://drive.google.com/file/d/1GaNlSIvLIrp3S8o8M-IA90ih5BamkFWb/view?usp=drive_link
Attached is the new report. This morning I set HCI on, and increased the log size to maximum and rebooted the phone. I was able to drive my car to work using the phone as a key without problem. After work today, I went out to my car, and could not get in. I turned Bluetooth off, then on, and the car immediately connected, and I was able to enter. I then immediately captured a full bug report. Additionally, all day I have been getting notices from Tile that it could not find my devices.
The other thing that is annoying is most of the time when I restart Bluetooth, I get a persistent notification that says "Looking for Android Auto". It never goes away without restarting Bluetooth again.
hi...@gmail.com
Here is a link to my bugreport. I set HCI snoop logs to enabled, logger buffer size to 8M, toggled Bluetooth and restarted the device last night. This morning at 10:22am, I force stopped the FordPass app, started it up and let Bluetooth connect and then started my car. I arrived at my destination and locked the car. At 10:28am, I returned to the car and Bluetooth would not connect - I toggled Bluetooth off and on and then Bluetooth connected and I unlocked/started the car, then created the bugreport.
https://drive.google.com/file/d/1072-vHji0OqtFa1J5wlYAh8m2rxHEtzL/view?usp=sharing
vi...@google.com
Re-
vi...@google.com
Re-
er...@gmail.com
It's back with a vengeance. Pixel 7a + Garmin Forerunner 945. It went from dropping every few hours to the point where it will not connect at all. C'mon people, how do you break something as simple as bluetooth this badly. I will have to strongly recommend people do not buy pixel devices if we end up being beta testers for connected devices.
Android 13 Security update May 5th, 2023 Play update May 1, 2023.
Android 13 Security update May 5th, 2023 Play update May 1, 2023.
vi...@google.com
Re-
In addition, before you capture bugreport we recommend Enable Bluetooth HCI snoop logs option and increase the logging buffer size to max available by following the below steps and then share the bugreport:
- Enable Developer options on the device.
- In the Developer options menu, change the Enable Bluetooth HCI snoop log setting to Enabled.
- In the "Logger buffer sizes", change the buffer size to "16M"(or highest possible).
- Restart your phone for logging to take effect.
- Try reproducing your issue again and take a new bugreport.
co...@punchthrough.com
hi...@gmail.com
Here is another bugreport, slightly different scenario this time. I don't have timestamps, but I force closed my app, started it up, and let the Bluetooth connection initiate so that I could unlock my car and start the car. After a few minutes (while still driving), I saw that the Bluetooth connection dropped in the app (which was still open on my phone) and I created a bugreport.
https://drive.google.com/file/d/168EqUt7lFjNGxB7uBWk6hybVLn5zrtyt/view?usp=sharing
vi...@google.com Restricted+
Restricted+
Comment has been deleted.
vi...@google.com
Re-
zh...@gmail.com
June update has not fixed the issue for me.
Phone as a key doesn't work, problems connecting hearing aids, tile trackers not working, etc. I never have problems with hands free calls or playing Bluetooth audio.
Right after I installed the June update, I was able to use my phone as a key for the car driving to work just fine. But I couldn't coming home until I restarted Bluetooth on the phone. I could submit another bug report, but sure if it will show anything more than the previous one.
Phone as a key doesn't work, problems connecting hearing aids, tile trackers not working, etc. I never have problems with hands free calls or playing Bluetooth audio.
Right after I installed the June update, I was able to use my phone as a key for the car driving to work just fine. But I couldn't coming home until I restarted Bluetooth on the phone. I could submit another bug report, but sure if it will show anything more than the previous one.
hi...@gmail.com
Confirming that the June update doesn't appear to have fixed it for me either. It seemed to work a little bit better, but I have had to force stop and/or toggle Bluetooth a few times to get the connection working again. My logs are available above unless new ones are needed with the June update applied.
ho...@gmail.com
This issue started for me with the June update. Had no issue prior but now every single Bluetooth device is like on circus mode disconnecting and reconnecting constantly.
hi...@gmail.com
Because I haven't seen a response, I'm uploading new bug reports after the June update was applied. This one is dated 6/28 and the process was:
- Device is connected to BLE (car)
- Walk around the block for 10 minutes
- Came back and the device showed disconnected state and did not auto-connect
- Force close the app and start it again, device connects, bug report taken
https://drive.google.com/file/d/1A6FIFAXqnUadkclhtpPn5O27I-Wn6Fqw/view?usp=drive_link
- Device is connected to BLE (car)
- Walk around the block for 10 minutes
- Came back and the device showed disconnected state and did not auto-connect
- Force close the app and start it again, device connects, bug report taken
hi...@gmail.com
This one is dated 6/29 and the process was:
- Device is connected to BLE and being used with Phone as a Key
- Turn off car, exit car, enter store
- Pre-emptively force close the app and start it again
- Exit store, approach car, device shows connecting, turn phone screen off and put it in my pocket
- Attempt to start car, received "Key not detected" message, pull out phone and open up the app and device shows disconnected state
- Force close the app again and start it again, device connects, start the car, bug report taken
https://drive.google.com/file/d/1ACPOGsdPxLwKgeK_w-yv-dqv20zpj88g/view?usp=drive_link
Is there active work being done on this issue? It's extremely frustrating at worst (not being able to use it with Phone as a Key reliably without restarting the phone every day) and life-threatening at worst (not able to maintain a connection to medical devices, per others in this issue tracker). The silence on this issue is frankly ridiculous and absolutely will push people off of the Android platform.
- Device is connected to BLE and being used with Phone as a Key
- Turn off car, exit car, enter store
- Pre-emptively force close the app and start it again
- Exit store, approach car, device shows connecting, turn phone screen off and put it in my pocket
- Attempt to start car, received "Key not detected" message, pull out phone and open up the app and device shows disconnected state
- Force close the app again and start it again, device connects, start the car, bug report taken
Is there active work being done on this issue? It's extremely frustrating at worst (not being able to use it with Phone as a Key reliably without restarting the phone every day) and life-threatening at worst (not able to maintain a connection to medical devices, per others in this issue tracker). The silence on this issue is frankly ridiculous and absolutely will push people off of the Android platform.
vi...@google.com
Re-
jb...@gmail.com
Can I take last update off my phone as my libre 2 sensors are not giving me warnings of low or high blood sugars things worked fine before last update this week
li...@gmail.com
Comment has been deleted.
li...@gmail.com
Hi everyone, I'm a diabetic who uses freestyle libre 2, Samsung Android phone.
I'm currently using version 2.8.4 of the FreeStyle LibreLink App which IS compatible with Android OS 13 and all alarms work correctly.
But now I'm hesitant to ever update my android operating system ever again.
I'm currently on this version
Build Number : S901EXXU2BVKM
Android version : T(Android 13)
Release Date : 2022-12-21
Security patch level : 2022-12-01
(One UI 5.0)
I'm considering upgrading to:
Build Number : S901EXXU5CWEC
Android version : T(Android 13)
Release Date : 2023-06-26
Security patch level : 2023-06-01
(One UI 5.1)
Please let me know if anyone has had experience with the latest Android version (June 2023) for Samsung and freestyle libre 2?
Thanks,
Lisa
I'm currently using version 2.8.4 of the FreeStyle LibreLink App which IS compatible with Android OS 13 and all alarms work correctly.
But now I'm hesitant to ever update my android operating system ever again.
I'm currently on this version
Build Number : S901EXXU2BVKM
Android version : T(Android 13)
Release Date : 2022-12-21
Security patch level : 2022-12-01
(One UI 5.0)
I'm considering upgrading to:
Build Number : S901EXXU5CWEC
Android version : T(Android 13)
Release Date : 2023-06-26
Security patch level : 2023-06-01
(One UI 5.1)
Please let me know if anyone has had experience with the latest Android version (June 2023) for Samsung and freestyle libre 2?
Thanks,
Lisa
la...@gmail.com
Hello,
since the June-Update our Galaxy A33 5G is having trouble with bluetooth - our Freestyle Libre3 sensor has many problems to connect with the app. Until May-Update we have had no trouble.
since the June-Update our Galaxy A33 5G is having trouble with bluetooth - our Freestyle Libre3 sensor has many problems to connect with the app. Until May-Update we have had no trouble.
je...@gmail.com
ro...@gmail.com
Same problem here on A53 5G with diabetes hardware Abbott Freestyle Libre 2 here. BLE connection stopped working after June update (A53BXXU6CWE9). On original Abbott's app - "Alarms unavailable, please scan sensor". On 3rd party app DiaBox and Juggluco - no connection. Manual scanning via NFC still works. Bluetooth connection is working fine on old A70 phone. Glad I haven't sold it :)
ba...@gmail.com
Comment has been deleted.
vi...@google.com
Re-
vi...@google.com
Re-
li...@gmail.com
Re
I'm currently on Samsung Build Number : S901EXXU5CWEC (Google play system update 1May 2023, android security patch level 1 June 2023), bluetooth alarms work for the librelink app
Perhaps it's the next update that breaks it?
I'm currently on Samsung Build Number : S901EXXU5CWEC (Google play system update 1May 2023, android security patch level 1 June 2023), bluetooth alarms work for the librelink app
Perhaps it's the next update that breaks it?
zh...@gmail.com
Re
Here is a new report. I was unable to use my Phone as a key and my Tile trackers were not detected even though I had them with me. I then captured the hug report without restarting Bluetooth.
https://drive.google.com/file/d/1hY9PLiRYlFnVBrethJcdf3R7IqHNm8JM/view?usp=drive_web (bugreport-panther-TQ3A.230605.012-2023-07-08-17-30-31.zip)
Here is a new report. I was unable to use my Phone as a key and my Tile trackers were not detected even though I had them with me. I then captured the hug report without restarting Bluetooth.
de...@gmail.com
I recently purchased a Google Pixel 6 Pro and the Buds Pro, together, and have been experiencing constant drops on my Bluetooth connection to different devices. Many accounts mention this is a car-related problem, but I don't have a car with built-in BT cnnection, and still experience this with anything I try to connect to - speakers, earbuds and BT receivers. My system was always kept up-to-date, and I had the latest update installed yesterday. Still had connection dropping intermittently today. Read somehwere that Changing the Bluetooth AVRCP Version from 1.5 to 1.4 and enabling Gabeldorsche should work. Some users said it did, others said it didn't. I couldn't find the "enable Gabeldorsche" on my Developer Options menu, though, so still uncapable of finding a proper solution.
ba...@gmail.com
vi...@google.com
Re-
he...@ruuvi.com
Hi, so of our customers are having the same issues with our wireless Bluetooth sensors (RuuviTag). Before the June update they were working without any issues and now range is limited to ~1 meter with some Samsung phones and users (not all). Reproducible with at least Samsung A23, A33 and A53. It seems that the sensitivity with Bluetooth HW is reduced in latest phone firmware (which probably causes also connection errors).
Has anyone tested to fix with this "hack"?
Go to the settings menu and click “About phone” → software information
Scroll down to the bottom where you see “Build number”
Tap it seven (7) times. Android developer settings are now enabled.
Go to the settings menu again and click Settings->Developer options->Bluetooth AVRCP version.
select which Bluetooth AVRCP Version you want such as AVRCP 1.4 from the previous response.
Has anyone tested to fix with this "hack"?
Go to the settings menu and click “About phone” → software information
Scroll down to the bottom where you see “Build number”
Tap it seven (7) times. Android developer settings are now enabled.
Go to the settings menu again and click Settings->Developer options->Bluetooth AVRCP version.
select which Bluetooth AVRCP Version you want such as AVRCP 1.4 from the previous response.
he...@ruuvi.com
Typically with our sensors (only broadcasting, not in connected mode) and Android phones open-air range is 100-250 meters. Now it's reduced in this test phone Samsung A53 to ~3 meters after the June firmware update. In test setup Samsung S20 is working normally and the range is not reduced.
vi...@google.com
Re-
-
The original issue in
comment#1 comment#407 -
Apart from Samsung models (A23, A33 and A53), are the Pixel phones also experiencing this issue?
-
For further investigation we would need a bugreport (prefer Pixel phones if it is reproducible on Pixel phones). You may follow the steps provided in
comment#382
he...@ruuvi.com
Re-
- It's not mandatory to use GATT connection with our devices but it's also the same issue with the range.
- Currently we have not got any reports from Pixel phones and they are not available for testing right now.
- It's not mandatory to use GATT connection with our devices but it's also the same issue with the range.
- Currently we have not got any reports from Pixel phones and they are not available for testing right now.
vi...@google.com
Re-
he...@ruuvi.com
Re-
vi...@google.com
Re-
he...@ruuvi.com
Re-
vi...@google.com
Thanks for the inputs. We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available. It would be great if you can add the drive link here in this bug to keep the information intact with this current bug.
he...@ruuvi.com
Yesterday there was released a new software version to Samsung A53 (region Finland), 1st of July 2023, A536BXXS7C2G2 and this fixed the Bluetooth range issues with RuuviTag sensors. Main fix in this software update was Bluetooth connection and stability.
vi...@google.com
Re-
an...@gmail.com
Finally fixed for me & my Polar H6's by Android 14 Beta released today. Could have been fixed in Aug update or/& earlier betas, but I didn't try them.
Thank you! Interested to know why this took quite so long.
Thank you! Interested to know why this took quite so long.
na...@gmail.com
I had recently purchased the P6P and fully updated. Running Android 13. The phone keeps disconnecting, then reconnecting, from my 2016 Landrover. My Huawei, N20, Zfold4, and N10+ had no connection issues. I have always wanted a Pixel for a pure Google experience. I love the phone, but this connection issue is disappointing. Another issue I found receiving phone calls, the sound quality sounds muffled through the earpiece. Is there a ADB fix I could use? I have tried other methods in developer options, which does not work.
na...@gmail.com
Solution: Tasker
I see several comments that turning off BT then turning BT on when connecting seems to provide stability. So I used the Tasker app. When initially connect, then turn off BT, then turn on BT. Tested on the 2016 Landrover seems to work.
I see several comments that turning off BT then turning BT on when connecting seems to provide stability. So I used the Tasker app. When initially connect, then turn off BT, then turn on BT. Tested on the 2016 Landrover seems to work.
bl...@gmail.com
Android 14 and still unable to stay connected with EcuTek BT->OBD2 dongle or 2013 Nissan - pairing "succeeds" but then immediately disconnects and either tries to reconnect to the Nissan incessantly until pairing is removed or in the case of the EcuTek OBD connector it does nothing when manually trying to force it to connect after pairing.
il...@gmail.com
Poco m6 pro 5g update miui 15 update Android 14 update any way today
vi...@google.com
Re-
st...@gmail.com
Oppo A74 (Android 13) and Samsung Watch 4, have the issue...its a pain!
bo...@gmail.com
I have the same issue with my P6P constantly disconnecting to my pixel buds a series and a recently installed head unit in my work car. I have replaced my buds 3 times and also my P6P once thinking it was a hardware issue. I'm running android 14 and have for a couple of weeks but issue was there during the Android 13 build. I have tried a couple of options listed by enabling developer mode, enabling Bluetooth JCI snoop log, changed the log buffer size to 8M (max), disabled the Bluetooth a2dp hardware offload and also changed all Bluetooth system apps battery to unrestricted. I haven't changed the Bluetooth MAP version (yet). I'll see how this goes and report back. Also awaiting a Google employee to make contact regarding this issue.
jo...@gmail.com
Not trying to inflate this thread; but maybe my 2 cents will help this wheel squeak a lil louder...
Diabetic here; Dexcom G7, and not having a working ble on my android really sucks.
Not much trust for Google; wonder if these stack changes are with intent for us 'users' or 'hardware vendors '
Diabetic here; Dexcom G7, and not having a working ble on my android really sucks.
Not much trust for Google; wonder if these stack changes are with intent for us 'users' or 'hardware vendors '
bo...@gmail.com
Any update on this issue? Do you need anymore information to assist? The lack of feedback on this is really frustrating and disappointing.
tr...@gmail.com
Anyone know if this issue happens on iOS? It's been over a year and this is still not fixed. For the first time in my life I might buy an iPhone if this fixes the issue.
ca...@gmail.com
I recently got a humidifier from switchbot I think it has the same problem everyone is experiencing. I'm on s22 ultra tho. Just won't connect after how many times I try it detects it but won't let me pair it only manual mode works wich defeats the whole purpose of me buying this product.
vi...@google.com
Re-
bo...@gmail.com
See bug report as requested. Please advise if this is suitable or another is required.
bugreport-raven-UP1A.231105.003-2023-11-29-08-04-33.zip -https://drive.google.com/file/d/173TV__B644d4GpT1FKgkYrryi4rJY4xi/view?usp=drive_web
bugreport-raven-UP1A.231105.003-2023-11-29-08-04-33.zip -
ad...@gmail.com
Xperia 1v on A14 not able to maintain Bluetooth connection with mercedes MBUX software for more than 5 seconds. It is now becoming seriously dangerous when driving and calls coming into wireless AA attempting to route through BT but defaults to the handset because of this issue.
Please can we have any kind of update from you?
Please can we have any kind of update from you?
ra...@google.com
Thanks for the information. We don't have access to shared google drive link in
bo...@gmail.com
Sent as per request in
ra...@google.com
Hi bonaventuradaniel@
Please provide below information to better understanding of issue.
1.Steps to reproduce the issue .
2.Expected behaviour and actual observed behaviour for the issue.
3.Issue observed time (video or screenshot is preferred)
4.Issue frequency (one time/always/occasionally)
Please provide below information to better understanding of issue.
1.Steps to reproduce the issue .
2.Expected behaviour and actual observed behaviour for the issue.
3.Issue observed time (video or screenshot is preferred)
4.Issue frequency (one time/always/occasionally)
bo...@gmail.com
See below for answers to
- No steps are required to reproduce the issue. The issue happens all the time when I am using your Google pixel buds a series and my cars radio. I haven't been able to reproduce the issue at all by doing any certain thing.
- The expected behaviour is that it doesn't disconnect at all and the actual observed behaviour varies. They range from my buds completely disconnecting and never reconnecting until I turn Bluetooth off and on again, the buds completely disconnecting and then reconnecting (sometimes straight away, sometimes after a certain amount of time), sometimes 1 bud disconnects.
- The time isn't specific and occur when using the Bluetooth device
- The frequency is always.
Please advise if you need anything else. A solution to this issue is desperately needed by everyone in this issue tracker .
- No steps are required to reproduce the issue. The issue happens all the time when I am using your Google pixel buds a series and my cars radio. I haven't been able to reproduce the issue at all by doing any certain thing.
- The expected behaviour is that it doesn't disconnect at all and the actual observed behaviour varies. They range from my buds completely disconnecting and never reconnecting until I turn Bluetooth off and on again, the buds completely disconnecting and then reconnecting (sometimes straight away, sometimes after a certain amount of time), sometimes 1 bud disconnects.
- The time isn't specific and occur when using the Bluetooth device
- The frequency is always.
Please advise if you need anything else. A solution to this issue is desperately needed by everyone in this issue tracker .
ra...@google.com
Hi
We are not able to find enough information in the bug report. Please try to reproduce the issue after enabling the logs as below.
Steps for enabling full bt_snoop and persistent logs.
1.Enable Developer options on the device.
2.In the Developer options menu, change the Enable Bluetooth HCI snoop log setting to Enabled.
3.In the "Logger buffer sizes", change the buffer size to "16M"(or highest possible).
4.Restart your phone for logging to take effect
5.Try reproducing your issue again and take a new bugreport
Also, request to get the detailed scenario as below.
-
We assume that the scenario is when both pixel earbud and Carkit is connected to the phone over Bluetooth. The connection with the pixel bud is not stable, connection or re connection is not happening reliably ((sometimes straight away, sometimes after a certain amount of time). Please confirm whether this assumption is correct.
-
When you are trying to reproduce the issue, please provide us with the exact sequence and the time at which user performed the actions - this will help us to identify the right entries in the bug report.
For example (just an example scenario).
1. Both car kit and pixel buds are un paired. (7:33 AM)
2. Bluetooth paired and connected with car kit.
3. Confirm that the BT connection to car kit is working fine
4. Bluetooth paired and connected with pixel buds.
5. Confirm that the pixel bud is getting connected and working fine, if it is all good.
6. Switched off the pixel bud so that it disconnects from the Phone
7. Switched on the pixel bud so that it should connect back - This was not working ! (7:40 AM)
co...@thekearneys.org
The issue persists. Am on a new Pixel 7 pro running android 14. Wish to pair with a Plat H10 LE Chest Strap heart rate monitor. Android recognizes the device but disconnects repeatedly as described in this issue tracker. Log from the myworkouts app attached
co...@thekearneys.org
Correction Plat H10 to Polar H10
bo...@gmail.com
Reply to
Another Case ID [8-2690000035285] have mentioned this bug has been filed for future repair in upcoming updates. Can you confirm the requested information is no longer required?
Another Case ID [8-2690000035285] have mentioned this bug has been filed for future repair in upcoming updates. Can you confirm the requested information is no longer required?
bo...@gmail.com
Additionally the assumption is incorrect. Both earbuds and carkit have same issues but separately. Both earbuds and carkit are NOT paired at the same time.
ra...@google.com
Reply to
Thanks for the reply. Please provide the requested information mentioned in
fa...@gmail.com
can I get help to fix this problems
ah...@gmail.com
ah...@gmail.com
ra...@google.com
As requested in
st...@gmail.com
It's incredible how many devices have this problem, and nobody care it.
bo...@gmail.com
Reply to
I'm not sure why my original information isn't sufficient. I had done exactly as instructed. It feels like none of this information being provided is leading to a solution. This bug goes back to August 2022 for crying out loud. The Samsung Galaxy S24 is looking better and better.
I'll see how I go getting this additional information. Might take a while...if ever.
I'm not sure why my original information isn't sufficient. I had done exactly as instructed. It feels like none of this information being provided is leading to a solution. This bug goes back to August 2022 for crying out loud. The Samsung Galaxy S24 is looking better and better.
I'll see how I go getting this additional information. Might take a while...if ever.
hm...@googlemail.com
Another user with a similar issue. Constantly dropping connection to Freestyle Libre blood glucose monitors. Eve since the android 14 update for me.
Anything I can provide, I'm happy to.
Anything I can provide, I'm happy to.
ra...@google.com
el...@gmail.com
co...@gmail.com
Plz inform me because i do believe my hisband is doing this. Im having one
problem after another. Penny cole vcolesuep@gmail.com
On Mon, Feb 19, 2024, 12:29 AM <buganizer-system@google.com> wrote:
problem after another. Penny cole vcolesuep@gmail.com
On Mon, Feb 19, 2024, 12:29 AM <buganizer-system@google.com> wrote:
bo...@gmail.com
Reply to
See attached bug report. Please advise who requires access so I can add access permissions to this file.
Additionally the sequence of events occured as follow:
1. Earbuds connected to pixel device
2. Video being watched and sound playing through earbuds
3. Earbuds suddenly stop producing sound
4. Bug report generated immediately
No car device was connected at this time.
Hopefully this is now enough
See attached bug report. Please advise who requires access so I can add access permissions to this file.
Additionally the sequence of events occured as follow:
1. Earbuds connected to pixel device
2. Video being watched and sound playing through earbuds
3. Earbuds suddenly stop producing sound
4. Bug report generated immediately
No car device was connected at this time.
Hopefully this is now enough
j....@allgon.com
We are facing a similar issue. In our case Pixel 8 with Android 14. Our app cannot connect to an ESP32 after the first bonding process.
We opened a ticket weeks agohttps://issuetracker.google.com/u/1/issues/309765122 and we didn't receive any solution.
Is there any intention to fix this from Google? It is unacceptable that an APP stops working due to a OS update and do not receive any solution from the support team.
We opened a ticket weeks ago
Is there any intention to fix this from Google? It is unacceptable that an APP stops working due to a OS update and do not receive any solution from the support team.
je...@gmail.com
bo...@gmail.com
Any update on this? Has the team been able to review the bug report successfully?
bo...@gmail.com
Any update on this bug report review?
ch...@gmail.com
That's because you have been Betrayed 😞
On Wed, Mar 13, 2024, 3:57 AM <buganizer-system@google.com> wrote:
On Wed, Mar 13, 2024, 3:57 AM <buganizer-system@google.com> wrote:
bo...@gmail.com
What a joke right? Why is this even an issue from one of the worlds biggest companies. Sort it out.
ch...@gmail.com
ce...@gmail.com Restricted+
Restricted+
Comment has been deleted.
me...@gmail.com
I have the same issue.
no...@gmail.com
Same issue here.
ad...@smit.id.au
this is driving me up the wall
wi...@gmail.com
jo...@gmail.com
Does anyone know if this issue has been resolved going to Android 14 or higher?
ma...@gmail.com
Is there any update on this topic?
wi...@gmail.com
Any news on this?
It's super annoying on the Pixel 8 Pro, even a GoPro/DJI Action 4 has serious issues to connect.
It's super annoying on the Pixel 8 Pro, even a GoPro/DJI Action 4 has serious issues to connect.
ra...@google.com
Reply on
Thanks for reporting this issue. We request to capture the bugreport immediately after reproducing the issue and share with us. For steps to capture a bug report, please refer:
In addition, before you capture bugreport we recommend Enable Bluetooth HCI snoop logs option and increase the logging buffer size to max available by following the below steps and then share the bugreport:
- Enable Developer options on the device.
- In the Developer options menu, change the Enable Bluetooth HCI snoop log setting to Enabled.
- In the "Logger buffer sizes", change the buffer size to "16M"(or highest possible).
- Restart your phone for logging to take effect.
- Try reproducing your issue again and take a new bugreport.
ar...@gmail.com Restricted
Restricted
wi...@gmail.com
ra...@google.com
Reply on
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
ra...@google.com
Reply on
Could you please clarify the following
- Is this issue exclusive to the Pixel 7a, or does it affect other Pixel phones as well?
- Do Samsung phones also experience the connecting/disconnecting loop issue?
- Could the reporter provide the model of the SportsTracker heart rate belt they are using?
- If the SportsTracker heart rate belt is reset, does the issue persist?
- Does the issue continue even after rebooting the phone?
ar...@gmail.com
Is this issue exclusive to the Pixel 7a, or does it affect other Pixel phones as well?
I only got one Pixel phone, Pixel 7a
Do Samsung phones also experience the connecting/disconnecting loop issue?
No, never had issues with the old Samsung. I still use it for SportsTracker.
Could the reporter provide the model of the SportsTracker heart rate belt they are using?
Written on the back: Polar iWL FCC ID: INWR7. Maybe this site tells a little bit more:
If the SportsTracker heart rate belt is reset, does the issue persist?
There is no reset button or what so ever. I removed the battery and put it back in. The issue still persists.
Does the issue continue even after rebooting the phone?
I turned the Pixel off and on again, started SportsTracker and still disconnecting and connecting every approx. 50 seconds (see also new attached video). The disconnecting starts at 31 seconds.
Today I've updated my Pixel to the latest September update but it did not solve the issue.
ra...@google.com
Reply on
We’ve investigated, but unfortunately have not been able to reproduce it with the steps provided. Please help to reset the device and verify again.
We’ve investigated, but unfortunately have not been able to reproduce it with the steps provided. Please help to reset the device and verify again.
ar...@gmail.com
Please help to reset the device and verify again.
This is what I did:
First of all I removed the battery from the heart rate sensor and put a new battery in it (resetting).
Then I removed the Polar iWL device (heart rate sensor) from the bluetooth known devices by ´forget device' in the bluetooth ´tab'.
To be sure it's removed, I checked the known bluetooth devices again (no Polar iWL being saved).
Powered off my Pixel 7a and booted again.
In the bluetooth 'tab' I pressed 'pair new device' so the Polar iWL becomes one of the bluetooth connected devices.
Tried SportsTracker again but the issue still remains, approx. 50 seconds connected, 10 seconds disconnected, over and over again.
This is what I did:
First of all I removed the battery from the heart rate sensor and put a new battery in it (resetting).
Then I removed the Polar iWL device (heart rate sensor) from the bluetooth known devices by ´forget device' in the bluetooth ´tab'.
To be sure it's removed, I checked the known bluetooth devices again (no Polar iWL being saved).
Powered off my Pixel 7a and booted again.
In the bluetooth 'tab' I pressed 'pair new device' so the Polar iWL becomes one of the bluetooth connected devices.
Tried SportsTracker again but the issue still remains, approx. 50 seconds connected, 10 seconds disconnected, over and over again.
ra...@google.com
Reply on
Disconnection was triggered from the remote SportsTracker. Please help to feedback to SportsTracker vendor to check the issue. Thanks.
ar...@gmail.com
I have asked SportsTracker the same questions today. I will let you know the results.
jo...@gmail.com
Problem persists through update to Android 14, using Samsung Galaxy S22... Unable to consistently connect to Android Auto-enabled vehicle radio. If connection is successful, connection only occurs after interval of between 3 and 10 minutes. Have tried resetting network connections (as clearing bluetooth cache and data is no longer possible through settings, as of Android 13), clearing Android Auto (AA) data and cache, restarting all devices, clearing cache of Android device (Galaxy S22), updating all software/firmware in Android Auto-enabled device. Connectivity remains sporadic and unstable.
ar...@gmail.com
Update on
Support from SportsTracker was very good but unfortunately they didn´t have a solution. They redirected me to Polar. I'll ask the same questions there.
Support from SportsTracker was very good but unfortunately they didn´t have a solution. They redirected me to Polar. I'll ask the same questions there.
co...@gmail.com
Abousulty not. Abort abort. She's at the IT TECHNICIAN WITH STATE POLICE..
Penny cole
On Mon, 18 Nov 2024 at 1:01 PM <buganizer-system@google.com> wrote:
Penny cole
On Mon, 18 Nov 2024 at 1:01 PM <buganizer-system@google.com> wrote:
ar...@gmail.com
Update on comment 480:
I finally know what caused the issue. Polar told me that the wearlink sensor I'm using has a bluetooth version lower than 4.0. In fact its using bluetooth version 2. By knowing this, I bought a new heart rate sensor with bluetooth version 5.0 and it works without any issues when connected to my Pixel 7a. Issue solved :-)
I finally know what caused the issue. Polar told me that the wearlink sensor I'm using has a bluetooth version lower than 4.0. In fact its using bluetooth version 2. By knowing this, I bought a new heart rate sensor with bluetooth version 5.0 and it works without any issues when connected to my Pixel 7a. Issue solved :-)
pj...@gmail.com
Pixel 7A + Garmin Quatix 5 with Garmin Connect app is also affected.
vv...@google.com
Thank you for reporting this issue. We have a fix rolling out in an upcoming release.
li...@gmail.com
fix this phone please and thanks
Scotty Lee Ferguson
On Thu, Dec 19, 2024, 4:32 PM <buganizer-system@google.com> wrote:
Scotty Lee Ferguson
On Thu, Dec 19, 2024, 4:32 PM <buganizer-system@google.com> wrote:
st...@gmail.com
Its incredible, there's a bug, and nobody found the issue. This week my Samsung Watch 4 have installed new firmware with One Ui 6, today when i'm watch a video on instagram and the watch is recharging, the boring pop up for pairing the watch is appared! So now i have to reset the watch and repeat the pairing. I done this operation 25 times this year.
I'm on Oppo A74, with android 13. (When was Android 12, i got never and i repeat NEVER issue with pairing), after the android 13 release i got nightware.
The bug is bord with android 13, and there's some issue when i think the phone want reproduce the audio from the watch ( i don't know why) and this cause the auto unbondig device.
I'm on Oppo A74, with android 13. (When was Android 12, i got never and i repeat NEVER issue with pairing), after the android 13 release i got nightware.
The bug is bord with android 13, and there's some issue when i think the phone want reproduce the audio from the watch ( i don't know why) and this cause the auto unbondig device.
st...@gmail.com
Today new Oppo a74 security update, and when i watch a video on instragram and the watch are recharging...sbam! Phone lost device and pop up says to repairing! WTF i want android 12!
Description
Summary
Ever since the Android 13 beta, we've observed Android 13 being very inconsistent with reconnection behavior when it comes to bonded Bluetooth Low Energy peripherals, or specifically, BLE peripherals with LE Privacy enabled. Connection attempts would often result in immediate failures that manifest as the dreaded
BluetoothGattstatus code133(undocumented publicly, but which meansGATT_ERROR).Reconnection strategy
The way we've always reconnected to a bonded peripheral that has been working consistently from Android 6.0 up to 12.0 is by saving the initial MAC address of the BLE peripheral (
BluetoothDevice.address) at the time of connection, and then queryingBluetoothAdapter.bondedDevicesto find a matchingBluetoothDevicehandle, which we then callBluetoothDevice.connectGatt(..)on.(Note: our BLE peripheral utilizes LE Privacy to rotate its MAC address periodically to help preserve our users' privacy.)
Repro Details
Devices on which the issue was reproducible
Repro steps
The steps described below were captured using our proprietary peripheral whose firmware I cannot provide, but a Logcat output capture will be provided.
BluetoothLeScanner.onConnectionStateChangeevent withinBluetoothGattCallback.BluetoothAdapter.bondedDevicesand filtering for the MAC address of the bonded peripheral, then connecting to thisBluetoothDevicehandle.133. Once the system is in this state, subsequent attempts to retry the connection attempt will also fail immediately with the133status code.Investigation notes
BluetoothGatt.refresh()via reflection, but this didn't seem to have an effect on the issue at all.