Hello,
I have GT-N7000 UK O2
Android version 4.1.2
Ever since the JB update, my bluetooth requires me to restart it almost daily for it to pair with my car.
Prior to the update I'd set my visibility to 'never timeout' and it connected fine every time. With no intervention from me.
Now I have to swipe down the alert bar click on the bluetooth toggle turn it on and off, then select cancel once the bluetooth pop up appears.
The bluetooth works fine after that but it is annoying to have to remember to do it everyday.
Is there anyway to fix this or is a rollback to ICS the only thing I can do?
Your help would be greatly appreciated.
Thanks.
on JB if you turn the bluetooth on; it will be visible by only paired devices till you don't turn bluetooth off. So I don't think the problem is with the JB. unpair the car's device and pair it again and let the bluetooth be on.
Related
Hi guys, my capitvate just always disconnect with my car's bluetooth randomly.
I have to restart the phone each time becuase to reconnect doesn't work somehow.
is there any fix? anybody on the same table?
please advise.
chaolanren said:
Hi guys, my capitvate just always disconnect with my car's bluetooth randomly.
I have to restart the phone each time becuase to reconnect doesn't work somehow.
is there any fix? anybody on the same table?
please advise.
Click to expand...
Click to collapse
i have the same problem as some other people do as well. There's no actual fix, afaik, although the gingerbread roms seemed to have fixed it for me.
You can ask in the appropriate Q&A for your ROM.
chaolanren said:
Hi guys, my capitvate just always disconnect with my car's bluetooth randomly.
I have to restart the phone each time becuase to reconnect doesn't work somehow.
is there any fix? anybody on the same table?
please advise.
Click to expand...
Click to collapse
bravomail said:
You can ask in the appropriate Q&A for your ROM.
Click to expand...
Click to collapse
in his defense - although I could be wrong, I found that it has nothing to do with one particular rom. I had this problem on stock eclair and many of the custom froyo roms. Once I ran GB, the bluetooth was more reliable.
I'm having the same issue with stock 2.2.
I found a quicker method to fix it.
I downloaded a Bluetooth widget that toggles Bluetooth on and off - this seems to reconnect with my Jeep after the toggle:
com.curvefish.widgets.bluetoothonoff
I'm sure there are a ton of widgets out there; but, you may want to give that a try!
Thanks,
Shawn
I also ran into this as after chatting with Samsung support it turns out that the Galaxy line is set to never auto connect to any bt device even if the connection was already there.
I had trouble with disconnections from my car deck (jvc kw-xr810) when it was trying to share contacts. Once I set the phone to deny contact sharing and set up a separate phone book in the deck, it connects perfectly and never drops.
It's not a perfect solution if you want your whole address book access accessible from the car however.
Sent from my SAMSUNG-SGH-I897 using XDA App
SaintJohnShawn said:
I'm having the same issue with stock 2.2.
I found a quicker method to fix it.
I downloaded a Bluetooth widget that toggles Bluetooth on and off - this seems to reconnect with my Jeep after the toggle:
com.curvefish.widgets.bluetoothonoff
I'm sure there are a ton of widgets out there; but, you may want to give that a try!
Thanks,
Shawn
Click to expand...
Click to collapse
I use tasker for this. I have a task setup that as soon as I turn my car off and BT disconnects, toggle BT off and back on. I noticed that as long as BT is toggled off and back on, it will connect and hold it the next time I use it.
although, I have since turned that task off because GB roms seemed to have fixed the BT issues with my car. I rarely have this problem since switching to gingerbread.
Captivate stock 2.2 intermittent bluetooth problems
I have a stock Captivate with 2.2 android and I'm using a Motorola S10-HD headset to listen to music while I'm at work.
The bluetooth will randomly disconnect causing the music to pause. Sometimes it will reconnect on it's own several seconds later and I am able to continue listening by clicking the play button on the headset. If it doesn't reconnect on it's own then I have to turn off bluetooth on the phone and turn it back on. This will cause it to reconnect but the problem may occur again.
I have switched to listening to music on my Galaxy Tab 10.1 and haven't had any problems so it must be the phone.
Is there anything that will correct the problem?
Is this a defect with my phone or just a design problem with all Captivate phones?
Hello!
I bought an SBH20, paired with my XZ via NFC, listened to music, then disconnected the headset, using the NFC.
After a while, i tred to connect again via NFC but all i get is a 'connecting' message, BT turning on -white BT icon- but no real connection, therefore the BT turns off.
After several tries it finally connects, but it's not reliable this way.
I noticed, if i enter to settings(not turning anytihng on/off) and trying to connect (still using NFC), everything works fine: connects, disconnects perfectly, and handles the BT as it should.
I've reseted the headset, tried single and multi point modes aswell. Deleted the BT devices, then repaired, still got the problem.
Am i doing sth wrong? I want to connect and disconnect the headset with a simple touch, and not toggling the BT manually (NFC yeah...) Is this something, SBH20 is not compatible with?
(btw sony support says: "For subsequent connections between devices that have already been paired once, make sure that Bluetooth™ is turned on so that the devices can connect automatically." If it's a "must" , then what is the [email protected] use of the NFC??? Just to pair once???)
Please share your experiences! Any advice would be greatly appreciated!
Thanks for reading ( and sorry for my english)
I actually have the same problem using the SBH50. For me sometimes it connects perfectly fine, other times it doesn't and I have to go into bluetooth settings after which it seems to connect properly.
I have noticed that it also depends on how I disconnect it; if I remember to touch the headset to disconnect then next time when I try to connect I have more chance of it being successful. Also, when I try to connect I hold the headset aganist the phone even after the ‘connecting’ popup until I get the 'connected' popup.
These are just work-arounds which aren’t always 100% successful though so would be good to find out what the proper method is.
fl4r3 said:
I actually have the same problem using the SBH50. For me sometimes it connects perfectly fine, other times it doesn't and I have to go into bluetooth settings after which it seems to connect properly.
I have noticed that it also depends on how I disconnect it; if I remember to touch the headset to disconnect then next time when I try to connect I have more chance of it being successful. Also, when I try to connect I hold the headset aganist the phone even after the ‘connecting’ popup until I get the 'connected' popup.
These are just work-arounds which aren’t always 100% successful though so would be good to find out what the proper method is.
Click to expand...
Click to collapse
It is a real shame... In my case it's the opposite, if i touch the headset to disconnect, the next nfc-connect tends to be less successful.
(and i noticed that it also matters if i turn off the headset after disconnected, or not)
And what is really odd, that i don't have to do anything in the settings menu ( or bluetooth settings) just open it, and everything works like a charm...( all connect or disconnect tries are succesfull, no exception, even if i push the headset repeatedly to the pohone's back)
I'm not affraid to mod some system files, apps, maybe build.prop tweaks, but i don't know where to start. In bulild.prop there are only a few nfc related lines (tried to enable/disble those)
So i'm not alone...maybe even more people are in the same boat, trying to solve this.
Again; any related info is welcome
I also have a sbh50 but i normally disconnect by turning off the headset. I have set it in smartconnect to turn off bluetooth automatically when the connection shuts off but it doesnt always do that.
It reconnects with no issues when bluetooth is on and i turn the headset on again. I use the nfc tap only for the initial pairing.
The only issues I have is the google music skipping issue that i posted the other day and the gmail smart connect not working on the sbh50
swtam said:
I also have a sbh50 but i normally disconnect by turning off the headset. I have set it in smartconnect to turn off bluetooth automatically when the connection shuts off but it doesnt always do that.
It reconnects with no issues when bluetooth is on and i turn the headset on again. I use the nfc tap only for the initial pairing.
The only issues I have is the google music skipping issue that i posted the other day and the gmail smart connect not working on the sbh50
Click to expand...
Click to collapse
Well, then we don't have the same issue. I tought i could use the nfc for connect/disconnect (i actually still think it is capable of that, just sony messed up sth)
Could you try to connect/disconnect and connect again with your devices, please :angel:
I'm really curious about this whole nfc story ( why does the headset have the chip/tag if it only works for initial pairing -its not a big deal to pair manually, especially that it has to be done just once-, and on the other hand: if i put nfc in the device, why not put in this functoin too- not a big deal: a proper working BT toggle, but it brings a tad more functionality-
I am rooted but still using the stock ROM. I have two Bluetooth-enabled Pioneer head units and a Bluetooth adapter for my home stereo system with this issue, so I know it's not the other Bluetooth device that's the problem.
When I pair the other Bluetooth device, everything works fine until the Bluetooth device disconnects. I either leave the area with my One, or turn the car off. When I come back home or turn the car on, the One will not reconnect unless I manually turn Bluetooth off and turn it back on again. I don't have to redo the pairing, just cycle Bluetooth off and on. This gets really, really annoying with the car stereos because I have to do it every time I make a stop.
The weird thing is, I had the problem before and it went away when the KitKat update was released. Unfortunately it only worked for a few weeks because I sent my One in for the pink camera issue. I did a hard reset before sending it off and rooted it got back, and now the Bluetooth problem has returned even though it's still on 4.4.2.
Anyone know how to make this go away?
No one is having a similar problem or knows how to fix this?
Hey guys,
I'm running Oxygen 4.1.3 with the stock kernel but sometimes when I try to turn Bluetooth on it says no paired devices available and when I come back out of it and back to Bluetooth settings the Bluetooth is still turned off. Every once in a while it works perfectly, I turn Bluetooth on, all my paired devices show up and it connects and functions normally.
Does anyone have any suggestions other than factory reset?
Thanks
Hi,
when I start my car, my phone doesn't connect automatically to my car bluetooth (mitsubishi ASX 2012) and doesn't play music from phone like all my old phones do.
If I make or receive a call, then the phone connects to my car, but when the call is over it disconnects again form the car.
I found a solution to this problem: on bluetooth "other setting" I select my car device and turn off "multimedia audio" option and after a few seconds turn on it again. In this way all works well, but I would like fix it permanently without my manual intervention every time.
I have MIUI Global 12.0.1.0. (QFKMIXM, android 10 QKQ1.190825.002) but this bug was already present on MIUI 11.
Any ideas?
Thanks
Cervante$ said:
Hi,
when I start my car, my phone doesn't connect automatically to my car bluetooth (mitsubishi ASX 2012) and doesn't play music from phone like all my old phones do.
If I make or receive a call, then the phone connects to my car, but when the call is over it disconnects again form the car.
I found a solution to this problem: on bluetooth "other setting" I select my car device and turn off "multimedia audio" option and after a few seconds turn on it again. In this way all works well, but I would like fix it permanently without my manual intervention every time.
I have MIUI Global 12.0.1.0. (QFKMIXM, android 10 QKQ1.190825.002) but this bug was already present on MIUI 11.
Any ideas?
Thanks
Click to expand...
Click to collapse
Same thing for me in my Honda, im on mortal os latest. It worked on stable build xiaomi.eu 12.0.2.0
Now i have to do the same trick as you or use an aosp rom it works perfectly there).
I have similar issue with hotspot turned on - as soon as i turn it on, it repeatedly disconnects my bluetooth devices, and also hotspot client connections.
it was present in MIUI 11, also is present in MIUI12, nothing helped, even full factory reset.
It was last time i bought xiaomi i think.
Try resetting / wiping wifi and BT settings from share/connections.
I have my device in Spanish so not sure how it's called in English
:No-Frost: said:
Try resetting / wiping wifi and BT settings from share/connections.
I have my device in Spanish so not sure how it's called in English
Click to expand...
Click to collapse
I have tried that as first thing. Did not help.
* But I have changed rom so I did it in new rom and will test - thank you.
Sent from my Mi 9T Pro using Tapatalk
Cervante$ said:
Hi,
when I start my car, my phone doesn't connect automatically to my car bluetooth (mitsubishi ASX 2012) and doesn't play music from phone like all my old phones do.
If I make or receive a call, then the phone connects to my car, but when the call is over it disconnects again form the car.
I found a solution to this problem: on bluetooth "other setting" I select my car device and turn off "multimedia audio" option and after a few seconds turn on it again. In this way all works well, but I would like fix it permanently without my manual intervention every time.
I have MIUI Global 12.0.1.0. (QFKMIXM, android 10 QKQ1.190825.002) but this bug was already present on MIUI 11.
Any ideas?
Thanks
Click to expand...
Click to collapse
Same issue with my 2012 Mitsubishi Lancer! How annoying.
After trying all the suggestions listed, including turning the phone connection and media connection settings on both my phone and my car stereo off and on in various sequences, I've finally found a solution.
Go to developer options > networking > Bluetooth AVRCP version
The default setting is AVRCP 1.4, change it to AVRCP 1.5
This fixed it instantly for me.
Hope this helps anyone else with this issue :fingers-crossed: