I'm already looked for 3 days all over the internet and can't seem to find the fix.
Issue:
AT&T Note 3 + 2013 BMW X5 paired and happy for 6+ months using BME bluetooth and headset no problems. Phone paired, bluetooth always connects, all functions (phone, messages, music etc all work).
Early March, noticed that when connected to BMW, as soon as screen dims during call, both the bluetooth connection and headset icon stay active but the phone drops into handset (ie phone's own speaker/mic) and although bluetooth remains connected and headset icon on, the sound is now via phone. Touch phone and screen lights up, everything is fine again until screen dims, then repeat fiasco.
Can't find offending issue or setting. Could have been an app or app update.
So, to fix, flashed car into latest BMW updated firmware.
Tried again, same issue.
Then update phone to KitKat.
Tried again, same issue.
Yes, the proximity sensors are off and yes phone is set to not dim when on call. Still does.
Can't figure out why this is happening. Seems to happen quicker with Powersaving Mode on.
Any ideas??
I am now resorting to trying some of the Apps that keep screen lit while app is running....
Phone is OEM (ie not rooted) stock AT&T GN3. Also, previously, the phone would sit on passenger seat or console without any proximity settings and do just fine until this started happened. I suspect it is some kind of app or update that has caused the phone to behave like this. The problem is the phone.
TIA
Same issue with my Honda Accord, paired with bluetooth, phone will become unresponsive for 2-5 min when playing music, but then I formatted the phone and since then no issues.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Related
I have the Smartwatch and Smart wireless headset pro paired to my Xperia Z. I have noticed a couple of issues.
Smartwatch:
Disconnects quite a bit and requires me to swipe up on the watch screen to make it reconnect. I would say today it happened 30-40 times in a 10 hour period. Haven't had any issue with the watch like that on any of my other devices. Anyone else had this happen? Smartwatch is running the latest firmware.
Smart wireless headset pro:
It paired fine to the XZ and seems to work without issue. The thing I have noticed though is the Throw icon will pop up in the notification area and allow me to toggle between phone and the headset, or at least appears that way. If I change it to the headset via the throw function nothing changes. Sound continues based on how I have it setup in the bluetooth headset settings. Even stranger is if I disconnect the headset by turning it off the Throw icon will still be there. When I open it the headset will disappear from the options and when I go back to the home screen the throw icon is gone from the notification area but will return some time later again showing the headset even though it has been off that whole time.
Not sure why the throw options would show up if they won't change how the audio is handled or why it keeps showing up after I have disconnected the device. Anyone else with either of these accessories having any issues?
It could be a jellybean issue.
Those of us in the Nexus 7 forum had issues with bluetooth with jellybean, audio lag, skip & disconnects.
Seems to be much better after the latest jellybean update.
Q
DeadlyDazza said:
It could be a jellybean issue.
Those of us in the Nexus 7 forum had issues with bluetooth with jellybean, audio lag, skip & disconnects.
Seems to be much better after the latest jellybean update.
Click to expand...
Click to collapse
Didn't have the issue with my TL running the LT30p JB update though.
And tonight I unpaired the headset from the phone completely and turned the headset off. The phone still popped up the throw notification and had the headset listed there. This was after a reboot too.
Sent from my Sony Xperia™ Z
Spectre51 said:
I have the Smartwatch and Smart wireless headset pro paired to my Xperia Z. I have noticed a couple of issues.
Smartwatch:
Disconnects quite a bit and requires me to swipe up on the watch screen to make it reconnect. I would say today it happened 30-40 times in a 10 hour period. Haven't had any issue with the watch like that on any of my other devices. Anyone else had this happen? Smartwatch is running the latest firmware.
Click to expand...
Click to collapse
My Smart watch randomly disconnects to, sometimes it works for hours no issues other time disconnects every 2-3 mins, again both running the latest firmware.
Also when i restart the phone liveware/ (Smart Connect?) FC`s a couple of times before it settles.
The smartwatch works perfectly with my note 2, thought it would work just as good or better with the xz seeing as there both sonys. Strange
Sent from my GT-N7100 using xda premium
My AT&T GS5 will connect to my car's Sync system fine, but when I play music or audio, nothing happens. I have verified with Spotify and Stitcher. This only happens once in a while, but when it does, a full reboot will not resolve it. To be clear, the track plays (progresses in the status bar) but no audio is output. Anyone have this issue?
I stream music through bluetooth devices all the time. Not once have I had this issue. Maybe try turning the volume all the way down then back up? Seems like they have some bad S 5's out there but not all of them.
Try turning the volume up
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
So I got a new S5, and am having the same issue. Maybe it is a problem with my car? Rebooting the phone will allow it to connect, but music won't play still. Will have to take the car in.
Though one thing leading me to believe that there is an issue with the phone is I try to turn bluetooth off and back on to connect to the car. When I do this, bluetooth turns off, but will not toggle back on without a reboot. That is definitely an issue with the phone, no?
Hi everyone, main issue plaguing my N6 experience here... upgraded not too long ago from a G3.
There seems to be bluetooth stuttering with this phone. It is something that I haven't run into in any other phone (HTC One M7, M8, LG G3). I'm connecting to the car stereo and it connects calls okay, but when I connect it to a friend's car stereo (Sony stereo.. don't know the model #) or any of my bluetooth headsets (Sony MDR10BT primarily) I will get stuttering when trying to listen to music.
The main thing I noticed is the stuttering only happens when I have something in front of the device. I put it in my pocket and the stuttering starts. I wave my arm in front of it (in between the headset and the device), it will stutter.
I've looked around for solutions on this issue, no solution in sight. I think it has to do with the radio not getting enough power, this was never an issue with any of the other phones.
FAQ:
-I'm rooted, running stock kernel & Chroma 2015-06-05 build. Note this happens on Euphoria ROM as well.
-No, I'm not using a smartwatch
-This happens when the WiFi is both on and off
-This happens when screen rotation is set to automatic or portrait only
-Bluetooth is not being logged
-My jeans aren't sewn with any radio blocking materials
This has been driving me crazy. I noticed it seems to be much better with Developer M.
It only happens with my bluetooth headphones when I'm walking, so your description makes sense. It's the only time I really have my hands on my phone when using bluetooth.
When I'm using it for car audio, I have it in a dock. When I'm using a bluetooth speaker, it's on a table or desk.
I'll have to try some stuff out and see if it makes a difference, but as I said, I just switched to M and it seems to help.
Maybe hardware issue
I am experiencing the same behavior with a non rooted stock up to date Android on the nexus 6. It will sometimes stutter to the point where it just stops working and I have to restart the phone for Bluetooth to be usable again.
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Hmmm...My Bluetooth connection never have that issues. I used Bluetooth headphones and my car head unit. Running oos 4.1.1 as well.
Try dirty flashing your ROM, there might be something wrong with the drivers. Bluetooth commands (volume, pause, voice assistant, skip, etc.) work find on my headset, I don't believe its a compatibility issue.
If that fails, it might be a hardware defect?
I don't have problems with Bluetooth im using sony wireless earphones everyday. Try reformat the phone
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Assassin1985 said:
Hi!
Android Nougat has heavy issues regarding bluetooth connectivity. If you Google it you will see...
I have the very same Problems like you with my car radio...
This must be finally adressed by Google.
Click to expand...
Click to collapse
Huh? Must be an compatability issue between the BT device and your phone. I have 6 active BT devices I use all the time with this phone and my tablet. Car stereo, fitnessband, speakers and inear plugs.
Only issue I sometimes face is the 'stuck in connecting to last used device' where BT needs to be turned off and on again. Wouldn't call it a heavy issue.
bluetooth perfect here. better than my lg g3 that i had previous.
So, more info. If 2.4 GHz WiFi is active in ANY WAY, the bluetooth goes nuts. AVRCP (bidirectional commands) make it worse. Putting the phone in airplane mode to disable the "ambient" wifi location scanning and such, then turning bluetooth on manually and playing some downloaded music, seems to work fine. Switch the WiFi on though (even though my access point is 5 GHz), bam down the toilet. Ugh.
I did a complete reset and flashed OOS 4.1.1 from adb, no improvement. I'm trying the Open Beta 4 right now but I doubt it will be any better.
Did you turn off the scanning feature?
Happens to me like once every 3 days. I usually reboot by then
evilspoons said:
I just got a 128 GB OnePlus 3T a few days ago to replace a dead Nexus 6P. So far I'm very happy with the phone (performance, screen, etc, camera is almost as good, blah blah) except one thing.
My bluetooth is completely nuts. Sometimes I will turn it on via Settings or Quick Settings and it will not turn on at all (the slider moves to the right but stays greyed out, then moves back to the left). Other times I am "luckier" and it switches on and begins scanning, and I can see devices in the area. I pair to a speaker dock via NFC or my wireless headphones via tapping on them and the connection is established, you can hear the speakers go "hey something connected".
So that's all fine. But then you start playing music. About 40-60 seconds in it will skip, crackle, or pause the music entirely. Sometimes the device makes its disconnect noise immediately followed by its reconnect noise. At this point pressing 'play' again starts the cycle over again, usually, or sometimes it will just refuse to "talk to" anything any more until you reboot the phone.
The phone came with OOS 3.5.4 out of the box and immediately got an OTA to 4.1.1. I was suspect about the upgrade procedure and sighed and did a full reset and re-flashed the full 4.1.1 image using adb sideload, logged back in, did the barest of minimum updates to the Google apps to make it stop complaining, and then tried music again. More skipping and pausing. My headphones have a volume up/down key on them, pressing that pretty much immediately results in a disconnect.
It's like the AVRCP (command) bluetooth protocol is "fighting" the A2DP audio stream protocol? It doesn't make any sense. This would also explain why my car audio has NEVER worked, because my head unit uses AVRCP to read track names and my headphones and speaker dock don't have any sort of screen to speak of.
I want to love this phone and don't want to pay double for a similar Pixel, but I might just have to return it if it's effectively useless at one of the main things I have a phone for! :crying:
Click to expand...
Click to collapse
Hi, I have the exact same phone and been having stuttering performance with Bluetooth and Sony MDR-X330BT and worked fine with the 1+ 3. I decided to tell the phone to forget the headphones and start afresh; big mistake headphones kept refusing to pair. I noticed they have the NFC symbol on one of the earpads so I enabled NFC and used app I had downloaded a while back, 'Tap-and-Pair' that did not work either. I did a search today and found a great app that worked - 'NFC Easy Connect' from the Play Store. Now all I need is stable connection from car system which appeared to be tied in with length of screen life before going to sleep but think it may be faulty Twingo as been on the car forum and found others with similar issues but different smartphone to the 1+ 3T. Hope this helps.
I got the OTA and one of the issues I ran into was actually listening to any media app ( Spotify, Youtube, YT Music, etc. ). Whenever I turn the screen off, the audio stops and when you wake the screen to unlock it has a terrible slowdown. I tried this in Safe mode and even factory reset and the issue is still there. I does not happen with the screen on if you're watching a video, etc. only when the screen goes off. Anyone else having this problem?
Edit: I think I found and workaround for this and was driving me crazy cause I listen to a lot of podcast/music whie driving Go to settings/system/developer options/default usb configuration/ and switch it to " no data transfer ". DO NOT tick any other option.
Yes, I am having the same problem, and since I use a wired headset for work calls all day, this is a significant problem.
Your work-around appears to work, but this needs to get fixed.
I have the exact same problem on my Pixel 6 since the March update, identical symptoms including the massive slowdown, and it's infuriating. While doing tests to try to find a work around it suddenly also blasted to 100% volume for some reason causing hearing damage.
April update fixed this issue.