Hi all,
New to posting so hope this is in the right spot.
I have recently flashed the Resurrection Remix Rom 5.1.0 for my GS3 on Verizon. I have been using it for a few days now and so far it seems pretty sold and really like it including all of the features it has to offer. However I have come across an issue with the Bluetooth staying connected. I am able to make a solid connection with my phone to my car where I can make calls and stream music however this connection only stays for about 30 seconds. After that my car displays Contact transfer failed, call history transfer failed, and audio player disconnected. My phone will reconnect however without me doing anything but will continue to cycle like this. I was wondering if anyone else has experienced anything like this and any possible fixes there might be? I wasn't sure if there was another Bluetooth.apk I could install or another Rom (not TW) that might be able to provide a more solid Bluetooth connection? Thanks.
Happens on my one plus 3 also. No idea on how to fix it. Choppy videos as well.
Related
I just got the charge today, and one issue is killing me. I drive about 6 hours per day. My android phone is connected to my stereo via the 3.5mm headphone jack. I use this to listen to music. On every other android phone i've had(beside the epic 4g), when i get a call, the music pauses, and when i press the button on my bluetooth, it answers the call, and my audio going out is picked up by the bluetooth, and the call audio coming in is heard through the bluetooth.
This phone for some reason tries to route audio through the 3.5 jack, even though the bluetooth answered the phone. worse yet, i can't find a way to switch it.
On the epic 4g this guy made an apk to hot fix the issue. Could someone port this by chance?
http://forum.xda-developers.com/sho...light=bluetooth+call+audio+routing+to+headset
THanks!
I had sold my charge a while back, but just eneded up buying one again. Anyone made progress on this issue? Thanks!
Hey - it seems the fix near the end of that thread you referenced does the trick. Flash this in cwm recovery. It should work on any FP1 or EP4D (haven't checked others) ROM - stock or custom - but as I have no bluetooth stuffs I haven't tested this thoroughly to see if anything else happens as a result of the minor change. Hope this helps folks!
I've searched extensively and can't seem to find the specific answer I'm looking for. Ever since my phone updated to 5.1.1 my Bluetooth media connection won't work, just my call audio. This really pisses me off because I JUST bought a new head unit for my car so I could stream audio from my phone. My phone is not rooted and I wasn't planning on going through the hassle of rooting this one. Is there a fix without rooting? If not, will rooting and flashing a custom ROM fix the issue? I see there are some marshmallow ROMs already out.
I'm on 5.1.1 and have to power on and off my Bluetooth adapter half the time. Phone doesn't connect to data wifi or blue tooth in till adaptor is rebooted. Says it's connected.
I've tried it. Turned off bluetooth and turned it back on, as well as went into the bluetooth settings and turned "call audio" and "media audio" off/on multiple times. For less than a second if I have music playing it will play through the car and then the phone kicks media audio off again.
After I'm connected, I can take a call and music resumes. I've had problems with some apps that updates have fixed. But not what your describing. Maybe one of the auto connect apps from the play store?
dochab1 said:
I've searched extensively and can't seem to find the specific answer I'm looking for. Ever since my phone updated to 5.1.1 my Bluetooth media connection won't work, just my call audio. This really pisses me off because I JUST bought a new head unit for my car so I could stream audio from my phone. My phone is not rooted and I wasn't planning on going through the hassle of rooting this one. Is there a fix without rooting? If not, will rooting and flashing a custom ROM fix the issue? I see there are some marshmallow ROMs already out.
Click to expand...
Click to collapse
You cannot root the phone even if you wanted to because of the locked bootloader. Do you have the latest firmware update for your head unit? If not see if updating it may help. I have a top of the line Kenwood NAV head unit that worked without a hitch on my S4. When I got the S6 calls worked fine but I couldn't get audio to work. I found a solution on a Kenwood support site and now it works without any issues. Somehow settings were changed when I switch from the S4 to the S6. Also could there be an issue with your mobile data?
Hi, I've been having some fairly big issues with my in-car Bluetooth and phones. I have a 2013 Subaru WRX with the stock stereo which is made by Clarion.
I first started experiencing problems with it about 2 years ago: I would be driving along when all of a sudden my phone would randomly disconnect from my car while I'm talking, listening to music or just had the GPS running (or a combination of these). Oftentimes my car stereo will spaz out once it disconnects and will actually freeze (all buttons are non functioning, including steering wheel controls, power button, am/fm buttons, volume, etc) and take many minutes to reset the connection or it won't do anything at all (the stereo says, "please wait" or "paused" or will get hung on the song title that was playing when the phone disconnected) and my phone won't reconnect to it - I'll have to restart my car. Sometimes the stereo will reset and simply won't reconnect to my phone.
The kicker is that it's an intermittent problem, but still happens semi-frequently for periods at a time then it seems to get better. I've tried deleting my paired phone list in the car and on the phone, I've tried formatting my phone and nothing worked. I even brought my car into Subaru to diagnose the problem because I feel it's a car issue and they claimed it worked with their own phone which I feel is BS because they didn't want to fix it while the car was still on warranty, but that's another story! They said they couldn't fix it because they saw no problem (couldn't reproduce it) even though I provided them with video and pictures of it occurring.
This first started happening with my unlocked, stock, HTC One, m7 (currently running lollipop) . I thought there was a chance it could be related to an app or the OS but was not able to diagnose or isolate the issue. I just recently bought a Nexus 5x (marshmallow), unlocked, stock, thinking if it was the phone then this would fix the problem. It actually seems to have gotten worse with the frequency, however I've noticed that the phone is better at pairing with my car after the connection is lost. I still can't reproduce this on a consistent basis.
Can anyone suggest some possible causes and fixes? I'm hoping someone here is a Bluetooth Guru!
Ever since I upgraded to the new ViperOneM8 4.3.0 ROM I have been experiencing bluetooth issues every now and again. For example, I typically have my Moto360 watch and my Plantronics earpiece connected. In the middle of a call it will do weird things like spudder some crazy noises really fast for about 10 seconds then disconnect, or just plan disconnect. When it does disconnect, my phone still thinks the earpiece is connected and does NOT switch back to phone headset (like it used to). Then if I wait another 10-30 seconds it will reconnect and pick up the call on my earpiece again.
Anyone else having bluetooth issues on this ROM? It's a brand new install with nothing other than the basic google apps (and a few remote apps like LogMeIn, TeamViewer, and RD Client).
arvo.bowen said:
Ever since I upgraded to the new ViperOneM8 4.3.0 ROM I have been experiencing bluetooth issues every now and again. For example, I typically have my Moto360 watch and my Plantronics earpiece connected. In the middle of a call it will do weird things like spudder some crazy noises really fast for about 10 seconds then disconnect, or just plan disconnect. When it does disconnect, my phone still thinks the earpiece is connected and does NOT switch back to phone headset (like it used to). Then if I wait another 10-30 seconds it will reconnect and pick up the call on my earpiece again.
Anyone else having bluetooth issues on this ROM? It's a brand new install with nothing other than the basic google apps (and a few remote apps like LogMeIn, TeamViewer, and RD Client).
Click to expand...
Click to collapse
Mods should probably move this to the Q&A forum.
In general, I had weird bluetooth issues with audio. After flashing HK BS switcher INCLUDING the ADSP, all my issues went away. You need to be S-OFF, if you're not, don't even bother.
You want version 4.3.1 of this mod, considering you're running Lollipop.
Choose the Verizon install, not the ViperOne or anything else (even though you have Viper rom)
It's your choice what sound system you want. HK or Boomsound. I chose HK but that's just me.
I'd make a nandroid and give it a shot. Not sure if it's going to work, but can't hurt, especially if you make a nandroid.
http://forum.xda-developers.com/htc-one-m8/development/mod-audio-hk-bs-aroma-switcher-4-1-0-t3035354
Hi all,
Recently upgraded to Cyanogen 13 (marshmallow) on one plus one and since update Bluetooth connection to car head unit is not stable. I can receive calls fine but if I try to make calls the phone reboots. Happens less if original one plus flip cover is open (sensor not blocked), didn't happen in 12.1 (Lollipop).
Have done the forget and re-pair on both car head unit and one plus, clear cash/data and have done factory reset, nothing works.
Seems to be worse when playing podcasts via BT, not an App problem as all was fine before update.
Have looked through previous posts on a lot of forums, looks like this is not restricted to just oneplus and may be a marshmallow issue. Anyone else experience this and come up with a fix?
Cheers.
I have connection issue too in car, connects for 2 seconds then drops, cannot hold the connection. It worked before I upgraded to COS13. Only thing I've seen is report the bug to developers and hope they come out with a fix..
jira.cyanogenmod.org/browse/BACON-4733
Same for me. Buetooth connection in CM13 is very bad. Phone reboots... Worked fine in CM12.x.
jlkahn said:
Same for me. Buetooth connection in CM13 is very bad. Phone reboots... Worked fine in CM12.x.
Click to expand...
Click to collapse
Same for me, the phone reboots if any call is made through Bluetooth & Car when the flip cover is closed. Looks like a bug is reported in jira, but closed with description as invalid.
Anyone knows workaround?
There is a small magnet about 45mm up and 10 mm in from the bottom left corner of the case, (looked at when the case is open) this interacts with a hall effect device. What I did was tape a piece of mu metal 10mm x 40mm over the magnet in the cover so that the phone doesn't turn the screen off or on when the cover is opened. It needed a bit of experimenting as the first time I tried it, enough magnetism leaked after 30 mins to activate the sensor.
[email protected] said:
Same for me, the phone reboots if any call is made through Bluetooth & Car when the flip cover is closed. Looks like a bug is reported in jira, but closed with description as invalid.
Anyone knows workaround?
Click to expand...
Click to collapse
Ran into this on my Samsung S3 running CM13. (Seems to be a core CM13 issue....) Only a problem on my phone when connecting to headphones and speakerphones that have BOTH media AND phone profiles.
The workaround (not great, but better than a rebooting phone) is to disable one of the two profiles in the device-specific Bluetooth settings. Then it only accepts/makes calls -or- plays music/audio.