Develop Bugs

XDA IIs Spontaneous turn on & HBH-660 issues

I have had my XDA IIs for 24 hours and found two problems.
1. Blue Tooth Headset
Despite reporting a successful pairing, the only way to get my Sony Ericsson HBH-660 to connect is to soft reset the XDA. If the headset is turned off a reset is again necessary in order to reconnect.
2. Spontaneous turn on
Despite having Key Lock activated (and tested) the XDA seams to turn itself on at sporadic intervals whilst in the carry case. This is evidenced by the rapid discharge of the battery 100% to less than 20% in 10 hours most of which the unit was unused, and finding the screen already on about 80% of the time when removing it from its case. Great care has been taken to ensure that there is no accidental activation of the power button when putting the unit in and out of its case. The Bluetooth headset was connected at the time, could this be related to problem 1 or is it a hardware fault?
Query
Is it possible to use the Fonix voice dial from the BT headset? If so, how?

1. Have you applied the bluetooth patch from O2??? This should fix your HBH-660 problems
2. You aren't pressing the button on the HBH-660 by any chance?? Activesync is not running in the back ground?? No other applications running??
3. Not quite sure about fonix but i have been trying to find the software to try it out.

BT patch I am not sure, I have run the active update aplication on the phone (found one package) but I havent seen a patch on the O2 web site.
No buttons were being pushed on the phone or the headset (I checked) and no other applications were running.
I think Fonix have trial versions available for download, if not drop me a mail as it is a freebie on the O2 installation disk.

Is your XdaIIs an asia version of UK version?? Here is the link for the bluetooth patch upgrade ftp://xda:[email protected]/BlueAngel/O2XdaIIsBT3500Patch.exe
(url corrected by M4io)

It is the UK version, unfortunatly the link you provided did not work from here.

Thanks the BT patch worked great can connect at will now. I wonder if it will fix the other problem?

Gone the whole day with BT turned on (and working fine) made some longish calls and still have 68% of battery with no sign of rogue turn ons. Looks like it was a BT issue all the way.
Thanks again.
All I need now is a nice case.....................

[Q] Anyone else getting frequent disconnects (3-4 times per day)

I haven't been able to get through one day without having to do a complete reset of my 360. It will disconnect from my phone about 3 or 4 times per day and the solution is some random combination of massaging the watch and Nexus 5 through restarting the phone/watch, connecting/disconnecting in the Android Wear app, or ultimately resetting the watch and going through the whole setup again. I am using a Nexus 5 with CM11 on it. Is anyone else having this issue?

Using an ancient GS2 with CM11 and get an issue where my bluetooth turns off and can't be turned on so I have to restart, but I think my bluetooth module is damaged, your phone bluetooth doesn't turn off does it?

v3ngence said:
Using an ancient GS2 with CM11 and get an issue where my bluetooth turns off and can't be turned on so I have to restart, but I think my bluetooth module is damaged, your phone bluetooth doesn't turn off does it?
Click to expand...
Click to collapse
No, I don't have that problem.

mzimmer88 said:
I haven't been able to get through one day without having to do a complete reset of my 360. It will disconnect from my phone about 3 or 4 times per day and the solution is some random combination of massaging the watch and Nexus 5 through restarting the phone/watch, connecting/disconnecting in the Android Wear app, or ultimately resetting the watch and going through the whole setup again. I am using a Nexus 5 with CM11 on it. Is anyone else having this issue?
Click to expand...
Click to collapse
I am having a few maybe 3 or 4 disconnects but the watch reconnects for me.

I get about 1-2 disconnects a day but it reconnects immediately afterwards.

Nexus 5 CM 11 user with the same problem, well, erm, had a problem...-ish.
I've made a couple posts on the is problem and created a Log of my first day here.
I made this post here telling an XDA member how to remedy their disconnects:
When you lose connection with your 360, if you open the Wear app on your phone, does it still say connected? If so, try and reconnect with Android Wear to your 360, does it not reconnect? (This is happening to me)
Try reconnecting on Wear, your 360 may say that you've lost connection (Cloud with a slash icon). Try reconnecting again from the Wear app, if that doesn't work, try repairing your 360, that should work. (4/5 times it works for me)
Resetting does seem to work as well, I did it yesterday and went 16 hours without a disconnect, previous day was 7 in 6 hours. But this morning I walked away from my 360 with my phone and lost connection and it started disconnecting again.
Click to expand...
Click to collapse
When I did a reset of my 360, it got my through the day without any disconnects the count not reconnect. But I think I had one or two minor ones where all I needed to do was wake my phone and it reconnected.
Now, the final solution? Yesterday CM11 M10 came out and if you have upgraded, I highly suggest making a backup and doing so. It seems to of fixed the issues on my N5. I made a post here preCM10 (Before it came out) and decided it was probably a BT problem with CM, not the 360 and I think I was right.
The BT fix apparently made it into CM11 M10 and I seem to be doing alright. But Battery life kind of sucks still, I only made it 7 hours yesterday with moderate usage, so I'm starting to suspect that I'm still getting some kind of disconnect, but it's reconnecting instead of hanging, thus decimating my battery life.
My Nexus is also seeing pretty bad battery life since I started using my 360. Granted, it's never been the best at making it through the day, but it definitely seems to drain about 20% faster.

what about stock Nexus 5?
B3RL1N said:
Nexus 5 CM 11 user with the same problem, well, erm, had a problem...-ish.
[...]
.
Click to expand...
Click to collapse
I use a N5 stock Android 4.4.4
Will I have the same problem or is it linked to the CM thing?
Thanks in advance and, by the way, great graphic analysis, dude!

Galaxy S4 here
CM11 had constant connection problems. Always showed "Connected, running sync loop" in the Wear notification.
I switched to a GPE ROM and haven't had one disconnect.

I experienced 5-6 disconnects a day, at least, before the update. Afterwards, it has disconnected once, but I was in a very crowded area, and it could have simply had a lot of electronic interference. Otherwise, the update has definitely made a difference. Wear Aware is actually useful now!

[Q] Loss of BT and WiFi every day

I received a brand new Galaxy Note 4 from Sprint a few months ago to replace a problematic LG G2, but didn't activate it until last week (it sat in it's box prior to that and wasn't even turned on). At first, it worked great, but recently it has been losing Bluetooth and 2.4 GHz (I think) WiFi connectivity every day or so (usually when I wake up in the morning), and the only way to get it back is to restart the phone.
Has anyone heard of this? Or have any suggestions on troubleshooting or resolutions?
Thanks very much!
Three things to mention:
1) I did the tap & go to transfer my data from my old LG G2 (running some version of Android 4.x - I can't remember which one specifically) to my Note 4, but that was a week or so ago and the problems only started in the last few days.
2) The Note 4 came with a version of Android 4.x, but I updated it to Android Lollipop - again, this was done a week or so ago and the device seemed to work with no issues after doing it.
3) I am using the Samsung Gear 2 watch with the phone via Bluetooth but it seems all BT connectivity dies when the above issue happens (such as no ability to connect it to my car BT, etc.)
Thanks for any assistance!

Have you changed the visibility timeout to never? Then keep Wi-Fi on during sleep? For the Bluetooth problem, which I had also,I did a factory reset and haven't had as many problems since.

w7excursion said:
Have you changed the visibility timeout to never? Then keep Wi-Fi on during sleep? For the Bluetooth problem, which I had also,I did a factory reset and haven't had as many problems since.
Click to expand...
Click to collapse
Thanks for the info. I haven't ever made any of those setting changes previously, which is what leads me to believe something is wrong. For Bluetooth visibility, it is set to "2 minutes", but wouldn't this just be when a device is initially connecting to my phone, and not when a device is already connected? And for WiFi, it is set to "Always" for "Keep Wi-Fi on during sleep", so this is already set per your suggestion. Basically, things used to work fine, and now every night it seems to lose BT and 2.4 GHz WiFi. Per suggestions on another forum, I did a cache partition wipe, but this doesn't seem to have helped. This morning I woke up, and the device had lost it's connection with my 2.4 GHz WiFi network (wasn't even seeing it), and had connected to my 5 GHz WiFi network, and while it still showed connected to my Samsung Gear 2 watch, I don't think BT was working since I tried to connect it to another BT device and it failed. I then restarted, and it worked fine (until tomorrow morning presumably). I'd prefer not to hard reset, especially since there's no guarantee doing so will fix the issue and it won't just re-occur, and because it'll take me a lot of time to back everything up, hard reset, and then restore data, settings, and customizations to my device.
Any other suggestions or thoughts? Thanks!

I just wanted to say that my connectivity timeout is set to two minutes as well. I use my BT everyday for my headset and my head unit in my big truck and have had no issues.
From my Alliance powered Note4

schlepprock said:
I just wanted to say that my connectivity timeout is set to two minutes as well. I use my BT everyday for my headset and my head unit in my big truck and have had no issues.
From my Alliance powered Note4
Click to expand...
Click to collapse
Thanks for the info! This is so frustrating - just started using this device, and already it's broken...lol! Anyone have any other good thoughts or suggestions on what I might be able to do to resolve without a hard reset? Thanks!

Any other thoughts/suggestions? I'm open to Anything at this point!!

I spoke with someone at Sprint Tech Support, and they had me turn off WiFi Power Save Mode using *#0011# (and then choosing WiFi from the three dots menu) to see if this would help resolve the above issues. It didn't, and now even after re-enabling the power save mode, things have gotten worse. Now, every time I leave a location where I'm on WiFi (such as my home), my device's WiFi never refreshes to auto reconnect to other WiFi SSID's elsewhere. So even if I leave my home and arrive at an office where I've previously saved a WiFi connection, the phone stays on 4G/LTE until I manually turn off WiFi and then turn it back on a minute or so later. And I still think the 2.4 GHz issue (above) is happening as well.
WiFi is basically useless on my phone now - anyone have any ideas at all?
Thanks!

Bluetooth turning off since NMF26U

Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.

I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.

nighcore said:
I've had the same persistent issue also as of recently. Only things that use on Bluetooth is my Hauwei Watch and State Farm Drive Safe beacon. I haven't figured out what is causing the issue.
Click to expand...
Click to collapse
I also use a Huawei watch and the drive safe app. I'm gonna install an older version of the state farm app as it recently was updated now that I think of it.
Sent from my Pixel XL using Tapatalk

thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
FWIW: I've had no Bluetooth issues. Only things I use it for are connecting to my two cars for phone, and Android Auto (which uses USB and Bluetooth connection).

I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.

millerd79 said:
I am also experience this same issue. Seems when I get in my car I have to toggle my BT back on. I am using a Samsung Gear S3 with my Pixel XL.
Click to expand...
Click to collapse
Ever since I got the Gear S3, my Bluetooth will restart every single time I disconnect my Bluetooth headphones. It also never routes calls through my headsets unless I go into Bluetooth settings and uncheck and then recheck the phone audio option of those headphones every time I reconnect them. I've tried maybe 6 different BT headsets and it's the same case with all of them.

I have been having this issue since NMF26U as well. NOF26V actually seems even worse. It doesn't go off immediately upon connection or disconnecting from my car, but then randomly wile the BT lite will disappear while it is disconnected from any devices. Toggling it back on works as does a reboot that comes back on with BT activated even though it was off when rebooting. Hard to believe after this many updates that BT issues continue to be an issue with this phone.

Probably background tasks are getting killed aggressively. Despite being "not battery optimized", my VPN app gets killed too, if I don't touch my phone for too long. E.g. at night. And yes, I'm facing Bluetooth issue too.

Strange, Bluetooth hasn't turned off since my first post. ?
Sent from my Pixel XL using Tapatalk

I've had this issue and I'm not on the latest firmware. It's happened twice now. Very random, a week between. Maybe it was an update with the Google app, I've noticed a bunch of updates recently

I am having the same issue. The only thing I use my bluetooth for is my car. I have to turn it back on everyday when I start my commute.

I think I found a work around....
thecarp1975 said:
Has anyone been experiencing their bluetooth turning off on its own since the MNF26U update? I've tried re-flashing the factory image and doing a factory reset, but the problem still exists.
Click to expand...
Click to collapse
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!

Kokopelligod75 said:
This suddenly started happening to me as well and at first I thought it was my Moto 360 watch going bad since it kept displaying "Bluetooth Services has Stopped". After looking I noticed my Bluetooth was off on my pixel and here is what I did after learning a similar experience from my Camera shutting down on my old Nexus 6.
I went under Settings/Battery/Click the 3 dots in top right corner and select "Battery Optimization"/Then select the little drop down arrow next to "Not Optimized" and select "All Apps"/ Scroll down to "Bluetooth MDI Services" and Bluetooth Share". I selected both of them to "Not be Optimized" but you can play around and select one or the other to see if it works for you. Since I selected both my watch has stayed connected now for about 2 days straight and my Bluetooth stays connected and connects automatically like I've set up to my car and other devices. It also works and stays on when my phone goes into "do not disturb mode" also....
I'm not saying this is the "fix" for it but it seems to be working for me....
I hope this will work for you guys and helps!
Click to expand...
Click to collapse
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!

t3chfaith said:
This suddenly started happening to me as well... SIGH... I've tried what you just listed to do, stay tuned I hope it works. Thanks!
Click to expand...
Click to collapse
Yeah I would be very curious if it works for you as well and hopefully it does. I was getting very frustrated with it but since I changed those settings it seems to be working fine now and I haven't really noticed any difference in battery performance either.... If you don't mind, keep me posted as I'm curious. Thanks!

Had the Bluetooth turn off on my XL before even entering my car (but I didn't see it happen except when I was about to get in the car and noticed no BT indicator). This was approximately an hour after a reboot and no BT devices had been paired though the indicator was on for some period after the reboot. Pretty hard to believe it was an optimization issue since I had run no apps after the reboot. While typing this, the BT icon disappeared again. Add this to getting a Verizon "Server Unreachable" error on my wife's Pixel yesterday and my XL this morning that both needed reboots to remedy. My frustration with this phone is pretty bad today. Both are unlocked BL, rooted with newest SU, running newest TWRP and newest Google version but otherwise stock. P.S. When you see about 4 Google play updates a day for about 2 weeks (with not very many apps installed other than the base) it is hard to guess what my be causing the issue. OK, rant over.

BT has definitely been a PITA since the latest security update. It's completely ruining the music experience on a car I bought days before the update came out. Since the update I constantly have to toggle bluetooth on then off again to get the phone to connect to the car. Then I have to open Google Play Music and start playback manually. This happens several times a day and is very annoying. Had not a single issue before the update.

I am having issues with Bluetooth disconnecting as well. Was bad on previous build but this most recent update, NOF26V build, is worse. I connect to my truck, watch, and speaker system in home and office. Happens randomly without notice. I have tried to test the "do not distrub" theory, after reboot, etc., so far I have not figured out a root cause or time.

Trying the optimized thing for the heck of it. I noticed that only share was listed and not MDI services. I wonder if that is only available on Google phones and not Verizon somehow or only shows if the BT is connected to the device, but I'm not in the car to check.

I too have a gear 3 frontier and since then I have to reconnect my pixels bluetooth, pretty much once everyday. very frustrating lol

Same BT problem
I have been having the same issue with BT switching itself off for about a week now. Never had any BT issues prior to that. Mine is a Verizon Pixel XL. I noticed it when it wouldn't connect to my car, but I quickly discovered that was because BT was off on the phone. I always leave BT on, so I knew something was funky and paid close attention after that. Once I turn it back on it connects to everything just fine and it stays on for the duration of me using it at that time. But when I go to use it the next time, it is off again. It can be a variable length of time in between when I use it, so I don't know how soon it turns off, but it has to be within just a few hours. This pattern suggests to me that something is turning it off, perhaps to save battery, if it goes without being used for a certain time period. I did not knowingly turn on any setting that does that, so it makes sense that an update changed something. I have not tried the workaround/fix mentioned above; I will do it and report back.

Bluetooth disconnections and unpairing driving me to distraction

My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?

gadgetgaz said:
My issue seems to be different from others' as mine isn't just bluetooth losing its connection - it actually unpairs.
In my car (it has an Android Auto compatible infotainment system) it works fine for ages then fails to connect all of a sudden. Then after a while a message pops up on the car's screen saying "bluetooth pairing successful". The phone then asks me for contact sharing permissions. Of course it screws up the smart unlock feature as a result forcing me to set it up again.
On my Huawei watch 2 sport it loses connection and so the wear os app says the watch is disconnected. Bluetooth settings show the watch to be invisible and, as a result, smart unlock gets unconfigured and I have to set it up again. The watch battery discharges very quickly - probably constantly searching for the phone.
I reboot of both devices seems to fix it, for a while.
This is all since the Pie official update.
Does anyone have any fixes please?
Click to expand...
Click to collapse
No fixes but same problems here

I'm having the same issue also very frequently with WiFi dropping all the time. These two reasons are linked from what I been told. Google telling me to RMA. The pain of that

Mine has done this with my Gear S3 watch since I first got the phone a few months ago, it had me seriously considering returning it for a while. Sometimes it would just disconnect from the bluetooth, but often it would unpair causing me to have to go through the whole set up process again. It did this on Android O, various DP builds of P but so far (touch wood) has been good with the latest version of the Samsung software and Android P.

I'm having the same issues as well and currently searching for answers.