maybe this is not new to anyone of you...
I guess all of you know about the bluetooth issue by now for the WM5.
Issue: Bluetooth turns on OK but when the phone powers down, the bluetooth gets shuts off automatically...
having changed
[HKEY_CURRENT_USER\ControlPanel\Phone]
- Disable Phone Sleep. May help with Bluetooth disconnect issues.
I noticed that the bluetooth stays on even when the phone is turn off!!!
however upon powering up the phone, bluetooth turns off again...sigh..
maybe we are getting closer to gettting this bluetooth bug fixed ...
JK
I have an idea why BT disconnects itself.
It is definitely not Windows who disconnects it. BT chip disconnects by itself after some timeout. I think that there was a fix command in Init_Rom_V316.bts that instructs chip to be always on. Unfortunately BT driver in WM5 does not read this file. If it would be possible to take this file from 2003 ROM, send it to BT hardware, then I think the problem would disapear.
"Hi guys. Can anybody tell me how do I connect to a bluetooth headest manually through WM 6.0?
I understand that WM6.0 is supposed to do it automatically, but it doesnt . There has GOT to be a way for me to sync the TyTnII with my bluetooth headset manually.
My headset is Jabra320s (piece of crap), and it does not allow me to connect to the TyTnII manually through the headest because there is no menu LCD on the headset. Therefore, in order to connect my TyTnII and my Jabra manually, this must be done though the phone."
--------------------------------------------------------------------------
"hm...its pair'd....here is the situation
even though it is pair'd, when i goto the bluetooth connects scree (device tab) there are no options to connect. the only options that come up are "edit, delete, set as hands-free, set as wireless stereo". theres no connect option. so i cannot tell it to connect....
sometime sit connects automatically, sometimes it simply doesnt, no matter how many times i restart it or the headset. sometimes even when i RE-PAIR it, it still does not connect."
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?
I am having a problem getting bluetooth to work with calls. When I pair with a BT device, it will often only connect for audio but not calls. I can go into the bt device settings and tap the Calls switch to turn it on but it will immediately turn right back off. This is happening on two devices that previously had no trouble connecting for calls. If I unpair the bt device then pair again, calls will work for a little while but then the calls option turns off and I have to unpair the device to get it to work again. Very very annoying.
Any idea why this is happening?
uscpsycho said:
I am having a problem getting bluetooth to work with calls. When I pair with a BT device, it will often only connect for audio but not calls. I can go into the bt device settings and tap the Calls switch to turn it on but it will immediately turn right back off. This is happening on two devices that previously had no trouble connecting for calls. If I unpair the bt device then pair again, calls will work for a little while but then the calls option turns off and I have to unpair the device to get it to work again. Very very annoying.
Any idea why this is happening?
Click to expand...
Click to collapse
i had that same problem on my A8 for a while and out of the blue one day it just stopped doing that and it worked properly ever since that day. I didnt do anything to remedy it, it just stopped effing up on its own somehow. No OTA update or anything like that either. The exact same bt headphones (Tozo 10L's) have worked seamlessly on my S9 since the day i got it. Matter of fact, i never even had to pair them as the info carried over from my A8