Android Android 12's biggest feature should be an easy upgrade to Android 13 |
- Android 12's biggest feature should be an easy upgrade to Android 13
- Xiaomi’s Mi 11 Ultra breaks cover with a 120X zoom camera and tiny secondary screen
- A new video editor, plus enhanced editing features
- NotebookCheck: "Proposed law in North Dakota may force Apple and Google to allow alternative app stores on mobile phones"
- Bluetooth Audio Quality Problems With Smartwatch: A Saga
- Xiaomi's Global version of the MIUI firmware has less features and isn't as optimized as the Chinese version of MIUI
- [NEW] PhoneBuff - S21 Ultra vs iPhone 12 Pro Max - Speed Test
| Android 12's biggest feature should be an easy upgrade to Android 13 Posted: 11 Feb 2021 12:23 PM PST
| ||
| Xiaomi’s Mi 11 Ultra breaks cover with a 120X zoom camera and tiny secondary screen Posted: 11 Feb 2021 04:57 PM PST
| ||
| A new video editor, plus enhanced editing features Posted: 11 Feb 2021 09:01 AM PST
| ||
| Posted: 11 Feb 2021 10:10 AM PST
| ||
| Bluetooth Audio Quality Problems With Smartwatch: A Saga Posted: 11 Feb 2021 10:04 AM PST I'm going to preface this by saying that this is a known issue that has been popping up on the internet since the inception of BLE devices/smartwatches. This is an aggregation of links I have found of others having the same issue. I have found evidence of this problem being reported by others going back to 2013.
The Problem: When a constantly-connected Bluetooth/BLE device, notably smartwatches (I've also had this problem in the past with Tile) has been set up on the phone; Bluetooth audio quality suffers immensely. Notable characteristics are that highs sound extremely compressed, often described as a "hissing" or "static" sound by those experiencing it. For audio nerds, it sounds like a sub-128kbps MP3 file, with lots of artifacts and noticeable data loss. The Devices: I have personally experienced this issue in two scenarios now: Samsung Galaxy S10 5G (Verizon), using a Fitbit, as well as the same problem when I was using a Tile locator. I used both the Fitbit and Tile with my Pixel 2 XL and never had the issue until I switched to my S10 5G. Samsung Galaxy S21 Ultra (Verizon), while using my Samsung Galaxy Watch 3. The problem seems isolated to certain phone models or manufacturers. Nexus/Pixel users historically don't seem to have any issues. Most reports seem to come from users of LG and Samsung phones. As mentioned, my problems I had a few years ago with my Fitbit and Tile didn't crop up until I switched from my Pixel to my Galaxy S10. The Details: In my personal experience, the audio quality is affected on any device using AAC or SBC. I have noticed this in my cars, as well as my non-AptX or LDAC headphones. On these devices, you typically cannot change Bluetooth codecs. I have tried every option imaginable in developer options to no avail. Others seem to report the same. The only way I have ever been able to remedy the problem is by completely disabling the smartwatch, "disconnecting" it in the phone companion app, and then restarting the phone with the watch turned off. Simply disconnecting or turning off the watch does not fix the problem, as the phone is still "searching" for the watch in the background even if it is disconnected, and even if you have force stopped the app. When I was using my Fitbit, the only way I could eliminate the issue entirely was by uninstalling the Fitbit app from my phone. It seems as though on certain platforms, particularly Samsung, a large chunk of Bluetooth bandwidth is being dedicated to the watch; and not enough is dedicated to the audio stream, and that dedication is permanent until the phone is restarted. Cycling Bluetooth on/off does not fix it. The Reality: This is, for me, a deal-breaking issue. It was with my Fitbit on my S10, and it is now with my Watch 3 on my S21 Ultra. I listen to a LOT of music, especially in the car. Very few cars support any codec other than SBC; so you're really up a creek without a paddle if this is something that affects you. I've tried using Tasker to automate disabling/disconnecting the watch when connecting to my audio device, but as mentioned before, the only way you can remedy the problem is by completely turning the watch off, disconnecting it, and then restarting the phone. This isn't really a reasonable workaround for every time you get in the car. This issue has been posted in a lot of places, and it seems to be a problem that has been around for 7-8+ years that has been completely unaddressed by Samsung, Google, or any relevant parties. When I selected my Watch 3 to go with my S21 Ultra, I had made the assumption that enough time had passed that the issue had to be resolved; especially with Bluetooth 5.0 and the improvements that have been made on the front of BT connectivity. But here we are; years later, with no solution. Samsung has gone the route of eliminating the 3.5mm jack, so now if you're in the same boat as me, you're forced to choose between having Bluetooth audio that doesn't sound like AM radio, or having a smartwatch. You apparently aren't allowed to have both. At this point I will likely be sending my Watch 3 back to Samsung, referencing what I've typed here today as my reasoning. I encourage anyone else with this issue to comment and add your input and experience as well. It may fall on deaf ears, but let the record show that Android users have been experiencing this same exact problem for almost a decade, and as manufacturers continue eliminating our choices and cornering us into Bluetooth, they fail to address the issues they present in doing so. [link] [comments] | ||
| Posted: 11 Feb 2021 07:46 AM PST
| ||
| [NEW] PhoneBuff - S21 Ultra vs iPhone 12 Pro Max - Speed Test Posted: 11 Feb 2021 07:59 AM PST https://www.youtube.com/watch?v=WYkRYhJVuXs (sorry, I'm new to reddit and idk how to embed a link) What do you guys think of the test? [link] [comments] |
| You are subscribed to email updates from Android. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment