So I just switched to a Nexus 5 from a Galaxy S4.... loved the phone until I connected it to my Tundra OEM bluetooth system. Hard to pinpoint an exact problem, it just doesn't work right. Randomly disconnects, etc. I had zero issues with bluetooth with my GS4. Is there some fix I should be aware of? i should mention that I rooted the phone right off the bat and am running Cyanogenmod Nightly.
Try it on stock to see if you have issues. It's most likely a rom issue
Sent from my Nexus 5
I've had a similar problem on stock rom with stock, chaos, franco and arkenstone kernels so I don't think the rom or kernel is the root of the problem. It will arbitrarily not connect, it will connect but when a call comes in won't automatically go to bluetooth but go to the handset etc.
I had hoped it was fixed somehow but happened again today out of the blue. It also comes with excessive bluesleep wakelocks that impact my battery life significantly (goes from draining at .7%/hr to ~3%/hr).
Related
Hey everyone, I need some help here.
A friend of mine bought a Galaxy S II about 5 days ago.
Her problem is that her battery lasts for like half a day. The only thing she has turned on is mobile network (3g). No wifi, no bluetooth or anything else. She has installed several applications, but nothing too extreme.
What could be the reason? And how is this solvable?
I was thinking of calibrating the battery, and if the problem persists, take it to replace.
The main problem is that it is not sure whether they are going to replace it, since when she was looking to buy it, she could barely find it, and the one shop that had it said that it was the last one they had on stock. They all said that Samsung had stopped producing models and, thus, they had none left.
Roflwat said:
Hey everyone, I need some help here.
A friend of mine bought a Galaxy S II about 5 days ago.
Her problem is that her battery lasts for like half a day. The only thing she has turned on is mobile network (3g). No wifi, no bluetooth or anything else. She has installed several applications, but nothing too extreme.
What could be the reason? And how is this solvable?
I was thinking of calibrating the battery, and if the problem persists, take it to replace.
The main problem is that it is not sure whether they are going to replace it, since when she was looking to buy it, she could barely find it, and the one shop that had it said that it was the last one they had on stock. They all said that Samsung had stopped producing models and, thus, they had none left.
Click to expand...
Click to collapse
this may not be a problem of faulty battery in the first place. try changing few things (lowering the brightness, switching off all the radios when not in use etc) and see if that improves the battery life. if it doesn't, then approach the service center, they will get it replaced. hope it helps
If it is actually a hardware problem, will it be a battery problem? Or a problem with the device itself?
Could be some rogue apps. GO Launcher and GO Locker can cause this if not set up properly. Coupled with with poor internet coverage if your 3g is poor, can cause the phone to continuously fail at synching and not preventing it to sleep well.
Uninstall programs you suspect are causing your phone to turn on periodically or check the battery power usage in settings to see which apps are draining the battery the most.
If still troublesome install Better Battery Stats from the forum which can give you more detail as to the cause of battery drain.
JelliBeaned SGSII
Dorimanx 7.17
Modem BVLP7
RootBox 10/11 Nightly
JusTunBean 4.1 Apps
Roflwat said:
If it is actually a hardware problem, will it be a battery problem? Or a problem with the device itself?
Click to expand...
Click to collapse
We're you able to solve the problem and did my advice help? Thanks for giving me my first thanks.
JelliBeaned SGSII
Dorimanx 7.17
Modem BVLP7
RootBox 10/11 Nightly
JusTunBean 4.1 Apps
Has anyone else for a kernel wake lock of bluesleep quite dominant?
Is there a fix for this?
tangcla said:
Has anyone else for a kernel wake lock of bluesleep quite dominant?
Is there a fix for this?
Click to expand...
Click to collapse
I noticed it today when I had been listening to audio over my bluetooth headphones. Had you been doing similar?
I notice it happens as a result of my Pebble being connected. Do you have any "smart" devices connected to it?
Sent from my D820
Shamingo said:
I notice it happens as a result of my Pebble being connected. Do you have any "smart" devices connected to it?
Sent from my D820
Click to expand...
Click to collapse
Yep I have a Pebble too.
Same here, I have been running it alongside my Nexus 4 (alternating days, same apps, settings, etc.). Nexus 4 is still on Jellybean, Nexus 5 is obviously on KitKat.
The issue might just be with KitKat because I don't have the issue at all with the Nexus 4. My next step will be to flash KitKat on my N4 and see if the issue starts happening there as well.
Obviously there is going to be some sort of battery drain when Bluetooth is enabled but there is a HUGE difference between the drain and wakelocks on N4 & Jellybean and N5 & KitKat. Hopefully it's software only.
Anybody figured anything out with this? I am getting bluesleep and msm_serial_hs_dma wakelocks. I use a Pebble also.
Edit: Saw there was a thread for this on the Pebble forum and they apparently deleted it because I had to view a cached version.
Unfortunately, my Nexus 4 is out of commission for the time being but I did get some (not very conclusive) data that showed the issue is not preset with the N4 & Jellybean.
However, I found more information regarding the subject. I found this post on the pebble message boards that seems to confirm the issue lies mostly with the Pebble watch. I tested this by disconnecting my watch but leaving bluetooth on (both with it connected to nothing and on a half an hour drive with my N5 connected to my car). The wakelock is nowhere near as crazy as it is with the Pebble.
Doing more research on the bluesleep wakelock in general yielded a couple of results here in XDA ranging from missing binaries to kernel bugs. The fact that it's only happening to the Pebble is interesting however.
I wonder how other Bluetooth "smart" devices do with the Nexus 5. I don't own any other ones but if someone else does that would prove an interesting test.
Seeing the same thing. Got a Pebble yesterday and seeing the Bluesleep wake lock in BBS.
edit: wrong thread!
Has anyone been able to test this with another Bluetooth data device (ie: not a headset)?
Same Blue sleep issue
I'm having the same issue.
Running 4.4.1 with ART runtime.
Using Sony bluetooth headphones.
Over 2.5 hours of wakelocks today.
Wasn't an issue on 4.4 so must be software glitch in 4.4.1
Will need to post it to Android code database so it can be locked into.
almightywhacko said:
Has anyone been able to test this with another Bluetooth data device (ie: not a headset)?
Click to expand...
Click to collapse
Ketzal said:
I'm having the same issue.
Running 4.4.1 with ART runtime.
Using Sony bluetooth headphones.
Over 2.5 hours of wakelocks today.
Wasn't an issue on 4.4 so must be software glitch in 4.4.1
Will need to post it to Android code database so it can be locked into.
Click to expand...
Click to collapse
I have the same with Android 4.4.2 using ART: Pebble app has 4h 8m of keep awake on 6h 36m total. I found a fix for bluesleep wakelock for Motorola Atrix, probably someone could build one for N5.
I think that the wakelocks issue is related to ART; I switched back to Dalvik and now it seems working fine as before.
almightywhacko said:
Has anyone been able to test this with another Bluetooth data device (ie: not a headset)?
Click to expand...
Click to collapse
I have the same thing with my samsung gear smartwatch , a search for the issue brought me here
bluesleep
msm_serial_hs_dma
msm_otg
msm_serial_hs_rx
are the main problem wakelocks
dece27 said:
I think that the wakelocks issue is related to ART; I switched back to Dalvik and now it seems working fine as before.
Click to expand...
Click to collapse
I have same issue with dalvik runtime and pebble smart watch.
nexus_ix said:
I have same issue with dalvik runtime and pebble smart watch.
Click to expand...
Click to collapse
Same issue for me now, Galaxy s4 running GPE ROM on 4.4.4 with Pebble Smartwatch. Almost 100% awake due to BT. If I turn off BT thongs go back to normal ...
Any fixes yet?
Same problem with jawbone up24.
I have the same problem. Started when I installed the beta XY findit app for BLE tags.
I have uninstalled that now, but whenever I have bt open, the battery drains blazingly fast. no BT headsets or anything. I mostly use the bt to interact with iBeacons.
i have been having this issue a lot to. seems to be caused by my pioneer nav in my car. bluetooth does disconnect however bluesleep wake lock stays going until i turn off bluetooth. hasnt always been a problem. started maybe a month ago. very strange. running slim rom. happens with stock slim and elementalx kernels.
I have had this issue a few times with certain versions of Franco kernel. I have a Fitbit Flex that syncs with my phone.
Hi, i did not find any related to my problem, that's why i am opening this thread.
I did a brick on my tf700 at last September and the cheapest solution it was to buy a new board on ebay.
i did the replacement that it was easier than i supposed and it started to work like new, like the first time the system ever boot.
After some days i did again unlock and install cromix and during several weeks it was perfect until yesterday when I detected that it was not good WiFi.
It is like half of intensity compared with htc one. Just works up to 8m from router.
I open it again to verify contacts, board. Everything is normal.
Do anyone know about antenna problem on tf700 (on my last prime it was a lot)? or hardware problem that in a moment reduced the intensity, if it was no WiFi at all i understood as a hardware problem, but half is strange.
Another thing is sound. When i started tf700 no sound, just on phones. After some hours (from night to morning) tablet working, sound appear.... i don't understand.
I tried different firmwares, now i am on cmb 4.3, and it is the same.
Any help?
antonio3073 said:
Hi, i did not find any related to my problem, that's why i am opening this thread.
I did a brick on my tf700 at last September and the cheapest solution it was to buy a new board on ebay.
i did the replacement that it was easier than i supposed and it started to work like new, like the first time the system ever boot.
After some days i did again unlock and install cromix and during several weeks it was perfect until yesterday when I detected that it was not good WiFi.
It is like half of intensity compared with htc one. Just works up to 8m from router.
I open it again to verify contacts, board. Everything is normal.
Do anyone know about antenna problem on tf700 (on my last prime it was a lot)? or hardware problem that in a moment reduced the intensity, if it was no WiFi at all i understood as a hardware problem, but half is strange.
Another thing is sound. When i started tf700 no sound, just on phones. After some hours (from night to morning) tablet working, sound appear.... i don't understand.
I tried different firmwares, now i am on cmb 4.3, and it is the same.
Any help?
Click to expand...
Click to collapse
If you use a different rom and you still have the same problems, then you may have a defect motherboard..
You can try to install a stock rom to verify the issues that you have. If you still have the problems, then you can confirm that you have a bad board.. Good luck..:fingers-crossed:
LetMeKnow said:
If you use a different rom and you still have the same problems, then you may have a defect motherboard..
You can try to install a stock rom to verify the issues that you have. If you still have the problems, then you can confirm that you have a bad board.. Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I already ordered another board from other guy.
My doubt is if the problem is at the ROM level, or kernel level.
Is not possible to take a log to see what Android reports at startup for sound and WiFi?
antonio3073 said:
I already ordered another board from other guy.
My doubt is if the problem is at the ROM level, or kernel level.
Is not possible to take a log to see what Android reports at startup for sound and WiFi?
Click to expand...
Click to collapse
Did you do a clean installation of your rom? If you flashed different kernels, you may have messed up the wifi modules.
Or it is another bug that has been discussed lately in the CROMi-X forum. If you turn wifi off and then on again: Does that change anything?
Some people had bad download speed when waking from sleep, whereas it was fine on a fresh boot or after toggling WiFi on/off.
If that is your problem, try turning off WiFi Optimization in the WiFi settings.
Absolutely loving this rom, but does anyone know if there are bluetooth issues with the current Cyanogenmod builds? Got a wear device for christmas, and it's battery life is about half what it should be. I've seen it reported on other devices running CM because of a problem with the Bluetooth drivers. Really trying to avoid switching back. Thoughts?
Can you please specify which device and what Wear Device are you referring to ?
Okay so I was on the M8 for about a year being a crack flasher and never having my phone set up quite the way I like it. I then switched to this phone and am loving it except the bluetooth. When I got it, I updated to 05Q before trying to connect to my car's bluetooth. I then had a lot of problems with bluetooth connecting, It would take forever to auto connect, music would skip and my phone would randomly disconnect. I did some reading and discovered it may be an issue with the update so I used the tool kit to downgrade to 44S. While less often, the issues are still very much present. I've been tempted to try CM12 but need something relatively stable. That being said, the 11s doesn't seem to be very stable itself, and I'm curious is bluetooth is better in the cm12 nightlies. I've done some research and I see references here to issues and then fixes and I'm not sure where things have landed at this point. Looking for some input on whether things would improve if I switched to the nightlies. Forgot to mention on my M8 bluetooth in my car worked flawlessly.