Dear All,
since having (official Oxygen OS) Android N on my OP3 my bluetooth headset (Sony SBH80) and most other devices are unusable. It seems the strength of the bluetooth signal has dropped by a factor of 10 - as soon as there is more than 1 meter air or more than one material (e.g. trouser pockets) between the phone and the headset the music starts skipping or drops out completely. When I have the phone in my hands near my chest, even tilting my head back breaks the connection.
- I tried other phones, they work completely with the headset fine in any normal use (phone in front pocket)
- The issue was NOT present when I was still on Android 6 (also stock Oxygen OS)
- I recently installed the Oxygen OS Beta (Android 7.1.1) with no change to the issue
I saw here in the forum and on various news sites posts about bluetooth issues with Android 7, but they were from the end of last year, still tried every "trick" or solution that was standing there. Here in the forum I only found posts about connection problems to car bluetooth. The thing is, I can connect fine, it's just that the signal seems to be too weak.
Is anyone facing the same issues or even better, was anyone facing the same issues and found a solution?
Thanks,
Georg
Related
Hi Guys,
I've been using my unit for quite a while now. Everything works fine except for Bluetooth. I'm using the latest Condu's ROM on a KLD device with up to date MCU. When I connect my iPhone and use it to stream songs the sound gets choppy as if it had a RAM outage. However I checked (and purged all processes) the RAM and it's fine, not even near full. What's interesting is that all other apps that are played locally (Spotify, Pandora, TuneIn) works fine. I already formated multiple times without success. Also tried Malaysk ROM once and the problem persisted. Is there any known solution for this?
Thanks,
Turn off the phone's WiFi, it is a known problem for all bluetooth audio devices when streaming close to WiFi as they share the same channel as WiFi.
Hi timk,
I tried with all WiFi off (my phone, the head unit, both combinations) and the problem persistis. I haven't had this problem in any other bluetooth audio device. Any other suggestion?
Thanks,
I have the same problem, electronical fizz in the sound, and it starts after a while not immediately.
I'm having similar issues from my Note 5. Even my Gear S2 seems to have weak connection as I get disconnected on the other side of the room.
Even with iPhones the bluetooth connection was horrible, popping like crazy and drove me crazy after 10 minutes.
Hi All,
My OP5T is running Android 8.0 with Oxygen 5.0.3, I have it paired with smartwatch (Samsung Gear S3). When I pair it to the car BT system (Renault R-Link2) it is a hit or miss: some times it connects some times it doesn't (if I disconnect the smartwatch the phone always connects to the car). Any one has a similar issue and found a workaround?
thnks/Pella
Same issue here...
Wonder if it's not rather car related, had the same issue with my nissan (nissan connect) and my GS8.. Sometimes everything was fine, sometimes I had to resync like it's a new device.
I've heard the car's softwares are messy things, very badly coded, full of bugs..
I have same problem.
As a workaround i go into blue tooth settings and turn off ability to make calls from Samsung gear.
It just has problem deciding what audio device to use. to bad you cant set priories anywhere
So, somewhere in May I received the automatic update to Oreo 8.0. Hurray! Sadly though, that's when my bluetooth problems started:
It connects to my car, as normal. And I can make and receive calls, as always. But during the call my bluetooth connection with my car would just drop. If the person on the other end of the line is patient enough, I can just reconnect while driving and continue. But it will drop once each minute. It's very frustrating. This worked flawlessly before the update.
Funny thing is there are no issues at all when playing music of a portable speaker. I can even play spotify through my car's speakers without problems. The problem only presents itself during calls on the carkit. To make sure it's not the car, I tried some other phones. My wife's samsung, also with 8.0, worked perfectly. So does my daughters Iphone with IOS. My car is a Volvo C30 from 2012. It has built-in phone connectivity.
What I tried:
- Unpairing and pairing again.
- Hard reset. In combination with re-pairing.
- Using the developer options to use Bluetooth AVRCP 1.4. In combination with unpairing and re-pairing.
- Using the developer options to use Bluetooth AVRCP 1.5. In combination with unpairing and re-pairing.
- Disabling automatic bluetooth/wifi scanning in the location settings.
- It even went to the repair center for a different issue (unresponsive touch-screen) and the repair notes stated that they also installed the newest software. So I had hopes that this would resolve my carkit issue, but it didn't.
Do you guys know any more tricks for me to try?
I have an XA1 ultra with Oreo 8 as well (build 48.1.A.2.21) and I'm experiencing the same problems, but adding that mine disconnects also when streaming music. Other problem I'm experiencing after the Oreo update is that,when using my watch (LG G Watch R) paired with the phone, the sound streaming is just crap, with lots of jumps and bad audio quality. This is so frustrating that I'm seriously considering buying a new phone ( not from Sony, of course)
:crying:
Anyone?
Hi,
I don't know if this thread is here in the right subboard but please let me explain my issue with Lineage 14.1 for the HTC M8 / single sim.
BT is generall works well with headphones and speaker but I have a serious problem with the phonebook function im my VW car navigation system RNS310.
The pairing is easy, also call-in and -out works.
The problem is the phonebook part: no phonebook, no arrived phone calls, no call history are available on the car system.
I tried it several times since the weekly updates dropped in cointaining less or more system changed but: No success since almost a year ago. Deleting the pairing and re-pairing also no success.
The latest rom "lineage-14.1-20181026-nightly-m8-signed" was tested, too.
Any ideas to help are welcome as the bugbash forum
P.S. The original HTC rom works flawlessly in this respect.
P.P.S. The jira bugbash community is dead on this issue.
Hi, I have the same setup and seems to work with my Mercedes no problems. I have noticed Bluetooth disconnecting randomly occasionally, but haven't worked out if its the merc command system or something with lineage 14
Sent from my m8 using Tapatalk
Hi,
that's good for you.
Anyhow it doesn't work in my Golf.
Commercial ROM works as well as other smartphones with factory versions.
So, it remains one of the big disadvantages of LOS 14.1 as well as the HDR camera crashes after second click.
Hopeless.
P.S. A big bunch of patches is forseen for the weekend even some changes in android_bt. Maybe this comes with a solution.
Finally I found a solution: It works !
In settings / apps / system processes I deleted data of the two available BT services.
Then I re-paired the phone and the car and after 30-40 seconds all phonebook stuff was displayes on the car navi screeen.
Case can be closed, I'm happy with the working status.
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
EDIT: this is wired using different cords for troubleshooting purposes.
I have none of those issues but my issue with aa is that it keeps turning off preview incoming message
Issue #3 I do get from time to time. Annoying AF. Also trusted device only last 4 hours I believe which I think is ridiculous.
imo... Spotify always sounds like crap.
Haven't had any of these issues at all. Everything works well for me on the December update.
I have none of these issues, but the issue I get is specific to Google Maps on Android Auto. When I'm navigating somewhere, often at the start of the trip Google Maps cannot get a GPS lock on me and the map skips all over the place, constantly rerouting me. After I continue to drive I eventually will get GPS lock and then everything works fine.
Using Waze on Android Auto, everything works fine. I get GPS lock instantly when I switch to the Waze app on Android Auto. So all I can conclude is the issue is specific to Google Maps... It's not that big of a deal but can be very annoying.
Edit: I'm on wireless with a Pioneer AVH deck.
My wifes Pixel 6 works fine apart from the battery icon constantly flashing on and off (on the car display)
I don't have any issues with Android Auto in my 2020 Subaru, and neither does my wife.
No, I don't have these issues either. Working fine for me on Lexus NX.
Edit: "wired" that is (to be clear).
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Caveman419 said:
I am not seeing any issues in my 2020 Kia Soul. I use the wireless android auto adapter (AAWireless from Indiegogo) so I do not have to plug it in though.
Could your uConnect system need an update? You can check here for one: https://www.driveuconnect.com/support/software-update.html
Click to expand...
Click to collapse
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
GtarSkater said:
Great Idea, unfortunately they are already up to date on the software. That AAWireless thing is pretty cool, but plugging it in doesn't bother me that much, plus I know its charging.
Click to expand...
Click to collapse
I always have issues with cables that keep disconnecting and have to unplug and re-plug in (both my car & my wife's 2016 Hyundai Sonata). The AAWireless is very handy in that regards. It will occasionally freeze up, but very rarely after a few OTAs ago. The only downside that I have found is that if you get too close to the vehicle with BT Headphones (mowing or other yardwork typically), it will connect to the AAWireless and cut off audio to the BT Headphones. I just unplug the AAWireless from the car until I am done then.
I should mention all my issues only occur when I'm wireless in my car. When I use wired in my friends car, it works fine.
GtarSkater said:
I tried to see if anyone posted a similar question but haven't found anything. Is anyone else having issues with their Pixel 6 Pro while connected to Android Auto? I have 3 issues that are bugging the crap out of me.
1. Every time I connect my phone to the car, it always pops up asking permission to connect to this "new" uConnect device. Its been connected hundreds of times, and even adding it as a trusted device, it still pops up.
2. The sound quality is absolute garbage. Its muddy and heavy on the mid level. I have tried to compensate by adjusting the EQ in the head-unit, and Spotify. It helps, but not much. I have tried my old Note 10+ and the quality is perfect.
3. Often when receiving a phone call, I can answer and control the call using the head-unit, but the audio is going to the phone and not the car speakers.
I have been able to replicate this with both of our Pixel 6 Pro's, and in both of our vehicles (2019 Durango R/T, and 2020 RAM 2500)
Anyone have any ideas?
Click to expand...
Click to collapse
Personally, I do not have an Android Auto enabled car.
I can tell though that there were numerous reports in the past (XDA, Reddit, Discord, Telegram) of people having problems with Android Auto. Now the problem with that, is...
a) Android Auto has always been buggy - even with cable. I have friends that have been trying to get Android Auto to reliably work with their Samsungs (cable) for years, and their attempt are still a work in progress. It's a hit-and-miss. Sometimes it works, sometimes it doesn't.
b) Android 12 is extra buggy and has been known to cause problems with Android Auto (reports of Samsung owners upgrading to A12)
c) Pixel 6 Pro is extra special buggy and it's more or less unknown at this point, if Android Auto issues are caused by Auto Auto being a buggy mess, Android 12 being a buggy mess, Pixel 6 being a buggy mess or a culmination of the three together.
d) Plus, there is a massive difference in reliability between Android auto cable vs. wireless.
I did see some workarounds floating in the web, you might be able to find them in Reddits GooglePixel group.
In the end though, your best bet (longterm) would probably be: Go into settings, report the problem directly to Google and make sure that all your friends and family that also use Android Auto do the same.