Fixed
Status Update
No update yet.
Comments
rk...@google.com
rk...@google.com
Information redacted by Android Beta Feedback.
ga...@gmail.com
Thanks for reporting this issue. We have passed this to the development team and will update this issue with more information as it becomes available.
rk...@google.com
I have the same problem on Pixel 6/Pixel 8 + Pixel Watch. When the watch is connected, the sound in the headphones is cut off.
ga...@gmail.com
I am having lots of Bluetooth issues with my wireless buds, smart watch and Android auto. I have a pixel 6.
rk...@google.com
The problem appears on many TWS headphones. If you listen to only one, then everything is fine. If you connect a second one, then breaks begin. This happens to me on Pixel Buds A, Marshall Minor III, Huawei Freebuds 4. The problem has existed for two months now and I have to turn off the watch to listen to music. I even changed my phone from Pixel 6 to Pixel 8 and it didn't help. Google Support, please pay attention to this problem. It is also described on Google Community. https://support.google.com/pixelphone/thread/239482780/pixel-buds-a-series-google-watch-2-audio-incompatibility-with-8-pro?msgid=239670939#
ga...@gmail.com
Woah, i didn't realise this was a wide spread issue. I too am facing the issue from around 2 months and was waiting for a fix. Since it was not in sight went ahead and logged this. Just an FYI, this issue started for me only when i enrolled into the Android 14 beta from 13 stable.
Hope Google takes this seriously
Hope Google takes this seriously
rk...@google.com
This happened to me a week after updating to the stable version of Android 14 on the Pixel 6. After purchasing the Pixel 8, the story repeated itself. There were no problems for exactly a week, but now the sound cuts out again. I assume that the problem is in the Bluetooth cache or in updating some system application via Google Play.
rk...@google.com
an...@google.com
Same thing happens to me, I have a pixel 7 pro, buds series a and a samsung s2 watch. annoying with both buds connected they will randomly stop playing any audio (audio is playing I just can't hear it any more) after about a minute or so the bluetooth disconnect sound plays then if I'm lucky it will reconnect again. if not I have to put them back in the case and take them out again. This happens very regularly, also I've tried it with my watched switched off but the problem still occurs. It happens in both instances while I am sitting still at a desk working or when walking.
The only way I think this does not occur is when I only one earbud in and the other in its case. this does not seem to present the problem. This issue was present in android 13 and now also 14.
Very annoying!
The only way I think this does not occur is when I only one earbud in and the other in its case. this does not seem to present the problem. This issue was present in android 13 and now also 14.
Very annoying!
an...@gmail.com
The same happens when I connect my Pixel Buds A series to my Pixel 6A and connect my Samsung Galaxy Watch 4 classic (Any watch with wear OS). My previous Crossbeat ACE (A non-wear OS watch) didn't cause this issue.
I have also raised a case with the Pixel Buds team. Ref Id: 5-2065000034485
I guess this happens for all devices with the below combo:
Andriod + Wear OS + Pixel Buds
I have also raised a case with the Pixel Buds team. Ref Id: 5-2065000034485
I guess this happens for all devices with the below combo:
Andriod + Wear OS + Pixel Buds
le...@gmail.com
Please follow the below instructions to enable persistent log and bluetooth hci snoop log:
- Open the settings app
- Go to “About phone”, and then scroll to the bottom. Tap the “Build Number” field 7 times.
- Go back to the main screen.
- Go to System > Advanced > Developer Options
- Change “Enable Bluetooth HCI snoop log” to "Enabled" (not "Enabled Filtered")
- Logger buffer sizes -> 16M(Maximum available option)
- Store logger data persistently on device -> All(This may not available on user builds)
- Reboot phone in order for the debug logging change to take effect
Please take the bugreport immediately after the issue reproduces and attach here for analysis.
Description
This is the correct behaviour in case characters of UCS-2 Encoding are used, but not for standard characters included into GSM 03.38
Ñ character is included into GSM 03.38 GSM 7-bit default alphabet:
In fact with a real phone only one SMS with 97 characters is received.
Code is pretty easy, see attached screenshots, with $ everything is ok, while with Ñ smsMessages array is made of 2 items
For privacy and security reasons I cannot attach more than this and full log files, but I think it may be enough because it's quite simple to reproduce.
Tested with emulator API 31 and API 35, both have the issue.
Studio Build: Build #AI-242.23726.103.2422.12816248, built on December 18, 2024
Version of Gradle: 8.9
Version of Java: 11
OS: Windows 11 Professional