Can anyone tell me anything about bluesleep? From the research I've done, it's apparently something that started showing up with ICS. I haven't found many reporting it with Kit Kat though. The closest I came was a few experiencing it with Pebble.
I did a factory reset on my N5 and tried to connect to my car's bluetooth. It wouldn't auto connect so I found a fix where I could rename my N5 and that fixed it. Now I've noticed bluesleep and a couple of other bluetooth related wakelocks showing up after I connect and use it. They seem to stop after I stop using it. Is this normal? Has anyone else noticed bluesleep?
Sounds normal.... You're basically saying when it's in use it causes battery drain. And when i turn it off all is normal. Aren't you?
Sent from my Nexus 5 using Tapatalk
Yeah. I just wanted to make sure that was normal. If you had an android watch connected wouldn't that always keep it awake and destroy your battery?
wakelocks are how the phone works. wakelocks arent bad, its the wakelocks that get "stuck" that are bad. if your phone didnt produce wakelocks, you wouldnt be able to do most anything with your phone.
Related
I picked up a Captivate and used SuperRooter, got Clockwork on there, and put on some apps. What's odd is that if the phone sits for a while and I try to wake it up, the screen doesn't turn on - even after waiting like 3 minutes. Besides flashing back to stock, is there anything I can do to see what might be causing this? Would a logcat via ADB help? When I set it down and use it every few mins, it's fine. It's just doing the weird not waking up thing when it sits for a while.
I've had mine since aug. 2nd....this just started happening to mine over the past few days, where it'll shut off while sleeping. Its only done it 2 or 3 times tho. Mine isn't rooted.
Seems this is happening to a bunch of people, some have had to remove the battery to get it back on....i haven't had to do this yet. (knock on wood)
Is there a way to disable a long press of the Power button while the phone is locked? I'm wondering if that is part of the problem.
Are you using SetCPU? The ondemand CPU governor is known to cause this problem.
Sent from my SAMSUNG-SGH-I897 using XDA App
Setcpu was causing my vibrant to do the same thing, deleted it and everything is fine
If SetCPU is an app, i haven't installed that one....
Removed it and it is still doing it. If the phone is plugged into anything (weither stay awake is on or not) it seems fine but when it is unplugged, it shuts off every few mins. My girl has this phone for the week and I won't see her til the weekend but I was reading on Android Forums and it seems alot of people are having this issue. I will flash back to stock and see if it helps, but I have a feeling it won't help.
i think its the root i mean i it did taht after i rooted i just got my replacement seeing if itll act up if not ill keep it if it does im jumping ship to buy a international galaxy s
Does your phone smoke a lot of pot?
I'm actually wondering if it doesn't have something to do with power handling with a full battery. I had to swap mine out because any time it was charged 100%, if it slept it turned off. After a few restarts or me playing with it enough to drop it below a completely full charge it was fine. I don't know, but if this new one does it I will just return it and look for something else :_(
well ricparr and anyone else i would just return your model saying its defective and get a replacement tahts what i did
Good day friends,
Thanks for such a great forum. I bought a second hand LG G2X. It was rooted but still running stock Gingerbread 2.3.3. The phone runs very well except for two defects.
1. GPS turns on but does not find my location at all.
2. The battery charges to 100% and when it gets to 75% it reports low battery and turns off.
I have no idea why the GPS is not working. I assumed the battery was bad and bought a new one. However the fault persisted. The curious part is that even when the phone reports low battery and turns off, the battery is not actually empty at all !! I download an app called "My battery info and drain". I waited until the battery reached 75% or so and got the 'Low Bat' message. I restarted and immediately was told 'Low Bat'. But this time I immediately turned on the 'Battery Drain' app and the phone didn't shut down as it usually those. In fact right now as I am typing it is draining. I wonder if this is some issue which has been encountered before and someone knows how to deal with it.
My Primary Request
1. Obviously the battery issue is non-reconcilable. I really have to find a way to keep the phone on for its designated time on battery. It seems a phone message since the battery still has some juice.
Peripheral Request
Obviously having a GPS is a plus. I really wonder if there is some driver issue wrong with the phone. I tired using Cyanogen 7 Rom and thought that might make it work but no success. Is there something such as a kernel which has GPS drivers that I can install.
I would imagine your best bet would be to upgrade to 2.3.4 stock. Search for methods if you can't do it OTA.
Sent from my HTC Ruby using xda app-developers app
I've heard horror stories about 2.3.3....glad I never had any experience with it!
I got a moto G it was charge to 100% played with it a little then completely shut down the device. Next day when i tryed to turn the device on, the battery was completely dead. Had to connect the charger for like 10 min before it powered on. Any ideas what can be the cause? Maybe the device does not shut down properly and freeze into the shutdown process with the screen turned off? Anyone else experienced the same?
vick33 said:
I got a moto G it was charge to 100% played with it a little then completely shut down the device. Next day when i tryed to turn the device on, the battery was completely dead. Had to connect the charger for like 10 min before it powered on. Any ideas what can be the cause? Maybe the device does not shut down properly and freeze into the shutdown process with the screen turned off? Anyone else experienced the same?
Click to expand...
Click to collapse
I'm pretty sure there are other posts with the same issue. Did you search Google or XDA before posting.
scott_doyland said:
I'm pretty sure there are other posts with the same issue. Did you search Google or XDA before posting.
Click to expand...
Click to collapse
I did but i did not found anything closely related to this. If you found or seen anything and can link it i would be realy glad
vick33 said:
I did but i did not found anything closely related to this. If you found or seen anything and can link it i would be realy glad
Click to expand...
Click to collapse
See here
http://forum.xda-developers.com/showthread.php?t=2599421
Not exactly your issue but the best place to post I think as its all about battery issues. There may be something in there that helps.
It is similar to your issue but I realise you had switched off the phone and it still dropped battery to zero, but I would think the above post is related.
If the issue is hardware related I guess the battery could probably 'drop' its charge, or at least report the charge was dropped, even if the phone was off, ie battery goes 'wrong' while phone is off so phone can't power on properly.
It is similar yes, but yet diffetent will keep an eye on the thread and see if the problem happens again
So I've had a lot of issues with my nexus 5 randomly rebooting and decided it was time to do a complete factory reset on it. Since I had been running stock, unrooted, locked bootloader since launch, I also decided it was time to unlock, root, and switch to Franco to see if it would improve things.
Now before, when I was charging my phone in my car, on my dashboard mount, while running Waze and driving in sunlight without AC (mine's dead), my phone would sometimes overheat. I'd know because it was hot to the touch, my battery widget would show overheat status, and it would stop charging. It would still FUNCTION, though.
Since my wipe/root/Franco change, though, it no longer reacts the same way. Now it simply gets so hot that it begins to freeze or fail to respond to normal functions and then eventually reboots itself, one time putting itself into a boot loop from the heat until I stepped in, forced it to the bootloader and powered it off until it cooled down.
Any idea why this change to Franco (I'm assuming it's the difference and not merely rooting, since that shouldn't change anything) would cause this, and what sort of settings I should adjust? I changed CPU temp threshold from 60 down to 52 in FKU, but that's done either nothing, or simply avoided the boot loop issue I had before. Do I need to lower that further? It's not even clear what that setting does. Anything else I can do?
Strongly considering going back to stock kernel to test further, but I know it's a slight pain to remove Franco due to all the roots, plus I wanted its improvements.
TurboFool said:
So I've had a lot of issues with my nexus 5 randomly rebooting and decided it was time to do a complete factory reset on it. Since I had been running stock, unrooted, locked bootloader since launch, I also decided it was time to unlock, root, and switch to Franco to see if it would improve things.
Now before, when I was charging my phone in my car, on my dashboard mount, while running Waze and driving in sunlight without AC (mine's dead), my phone would sometimes overheat. I'd know because it was hot to the touch, my battery widget would show overheat status, and it would stop charging. It would still FUNCTION, though.
Since my wipe/root/Franco change, though, it no longer reacts the same way. Now it simply gets so hot that it begins to freeze or fail to respond to normal functions and then eventually reboots itself, one time putting itself into a boot loop from the heat until I stepped in, forced it to the bootloader and powered it off until it cooled down.
Any idea why this change to Franco (I'm assuming it's the difference and not merely rooting, since that shouldn't change anything) would cause this, and what sort of settings I should adjust? I changed CPU temp threshold from 60 down to 52 in FKU, but that's done either nothing, or simply avoided the boot loop issue I had before. Do I need to lower that further? It's not even clear what that setting does. Anything else I can do?
Strongly considering going back to stock kernel to test further, but I know it's a slight pain to remove Franco due to all the roots, plus I wanted its improvements.
Click to expand...
Click to collapse
your phone overheating isnt cpu heating related, so changing that setting in fku will do nothing for you. its your battery thats overheating, not your cpu. its your own bahavior thats the issue actually. the battery and cpu have differing throttle/shutdown/overheating temps. the problem is that you are charging while plugged in, in the sun/heat, while using it. the battery gets warm just from a normal charging, gets hot while using and charging, but you also have it in the heat, lol.
simms22 said:
your phone overheating isnt cpu heating related, so changing that setting in fku will do nothing for you. its your battery thats overheating, not your cpu. its your own bahavior thats the issue actually. the battery and cpu have differing throttle/shutdown/overheating temps. the problem is that you are charging while plugged in, in the sun/heat, while using it. the battery gets warm just from a normal charging, gets hot while using and charging, but you also have it in the heat, lol.
Click to expand...
Click to collapse
Right... I'm not contesting that, and I basically stated most of that already. But my thread is about how this behavior has CHANGED since going Franco, and I'm looking for how to fix it. As I said, BEFORE Franco, in the same situation, my phone would get hot, stop charging, and continue functioning while it stopped charging. Now, instead of functioning and not charging, it appears to continue to get hotter and hotter until it freezes, crashes, and reboots. It didn't do that when I was stock, unrooted, locked. Now that I'm Franco, rooted, unlocked, it can't withstand this situation the way it did before. So I'm looking to improve upon that.
I'm perfectly fine with the old behavior because, as you note, this is my own "fault" by putting it in this situation (not that I have much of a choice), so I recognize I'm pushing the phone beyond what it should do. But the phone was smart enough to account for the problem and do what it needed to to stay functional, so I wouldn't lose my GPS or phone call in the middle just because I wasn't actively watching the battery meter every second, WHILE DRIVING, to see if it was overheating. It would notice on its own, stop charging, and get around the problem without crashing. I just want that behavior back, and I'm hoping a Franco setting can help me restore that since the issue seems to tie to my switch to Franco.
Then put the stock kernel back on. Get the factory image and extract the boot.img and flash it with fastboot
TurboFool said:
Right... I'm not contesting that, and I basically stated most of that already. But my thread is about how this behavior has CHANGED since going Franco, and I'm looking for how to fix it. As I said, BEFORE Franco, in the same situation, my phone would get hot, stop charging, and continue functioning while it stopped charging. Now, instead of functioning and not charging, it appears to continue to get hotter and hotter until it freezes, crashes, and reboots. It didn't do that when I was stock, unrooted, locked. Now that I'm Franco, rooted, unlocked, it can't withstand this situation the way it did before. So I'm looking to improve upon that.
I'm perfectly fine with the old behavior because, as you note, this is my own "fault" by putting it in this situation (not that I have much of a choice), so I recognize I'm pushing the phone beyond what it should do. But the phone was smart enough to account for the problem and do what it needed to to stay functional, so I wouldn't lose my GPS or phone call in the middle just because I wasn't actively watching the battery meter every second, WHILE DRIVING, to see if it was overheating. It would notice on its own, stop charging, and get around the problem without crashing. I just want that behavior back, and I'm hoping a Franco setting can help me restore that since the issue seems to tie to my switch to Franco.
Click to expand...
Click to collapse
the dynamics of the two kernels are completely different. they are so different that one or more of many many changes could be possible culprit(s).
jd1639 said:
Then put the stock kernel back on. Get the factory image and extract the boot.img and flash it with fastboot
Click to expand...
Click to collapse
...if I'm here asking for assistance on how to adjust Franco to resolve this problem, isn't it obvious I'm trying to avoid doing that? I'm here looking to see how to fix Franco so I can still use it. I know I can go back to stock, but that's not a fix, it's throwing my hands up in defeat. I'll certainly do that if nobody can offer me good advice, but I'd rather not.
simms22 said:
the dynamics of the two kernels are completely different. they are so different that one or more of many many changes could be possible culprit(s).
Click to expand...
Click to collapse
I understand, of course. I just hoped someone here had a similar experience that might help us track this down. I imagine people with more technical knowledge have put this kernel through it paces and might have an idea. PR better yet, know of a setting in FKU I can adjust to counter this.
Hi,
I've experienced the overheating issues with Franco kernel.. Have been using ElementalX kernel until i chose to try out Franco r69 kernel. Woke up in the middle of the night while phone was charging to a vibration sound that continued every 1 minute or so. Vibration was from when device is rebooting all the time. I checked the phone and it was really I mean really hot was uncomfortable to keep it in my hand. I immediately thought this could be something that a kernel might do. So I flashed ElementalX 2.05 back and tried to start it again. After the "Android is updating" window it started doing that again, heating up and rebooting. So I left it to cool home and started using my backup phone. Not sure what caused this but will research more when I come home. Hopefully phone is still good and I dont need to get it repaired.
Have been using the original charger, experienced some problems with other chargers.
Hello, I am using galaxy S3 stock rom and my phone keeps shutting down/rebooting when I am using it. Sometimes I let it charge and 20 minutes later it turns off and I have to try many times to boot it. Many times I let my phone on airplane mode at night at 53% battery and It drains completely. I tried other batteries but still the same thing. Did anyone ever experience this?
Thanks
spiritblastt said:
Hello, I am using galaxy S3 stock rom and my phone keeps shutting down/rebooting when I am using it. Sometimes I let it charge and 20 minutes later it turns off and I have to try many times to boot it. Many times I let my phone on airplane mode at night at 53% battery and It drains completely. I tried other batteries but still the same thing. Did anyone ever experience this?
Thanks
Click to expand...
Click to collapse
looked here? http://forum.xda-developers.com/galaxy-s3
Sent from my KFFOWI using Tapatalk
If you're sure it's not a battery problem, and you've run a battery calibration after backup, factory reset, and restore, just to be completely positive, you might want to see if it is a power button issue. The internals of the button get stuck every so often, and I found that when it was usable, I still got huge battery drain, and sometimes turning off and on by itself. There was a place near me that fixed the button on my S4 mini for $15, worked just like new.
I found that the phone was losing battery when when turned off, try leaving it off overnight and if it drains, it's probably an issue with the button.
If it's just a software problem, then that won't help. What does the OS say is using the battery? Maybe check for wakelocks with a battery saving app, I'm sure someone could recommend something
Cortmarshall said:
If you're sure it's not a battery problem, and you've run a battery calibration after backup, factory reset, and restore, just to be completely positive, you might want to see if it is a power button issue. The internals of the button get stuck every so often, and I found that when it was usable, I still got huge battery drain, and sometimes turning off and on by itself. There was a place near me that fixed the button on my S4 mini for $15, worked just like new.
I found that the phone was losing battery when when turned off, try leaving it off overnight and if it drains, it's probably an issue with the button.
If it's just a software problem, then that won't help. What does the OS say is using the battery? Maybe check for wakelocks with a battery saving app, I'm sure someone could recommend something
Click to expand...
Click to collapse
I Just played around with the power button because there was some dust and removed the battery and tried cleaning the metal things. I tried it today and it did not shut down once, i will see how it goes.. :good:
spiritblastt said:
Hello, I am using galaxy S3 stock rom and my phone keeps shutting down/rebooting when I am using it. Sometimes I let it charge and 20 minutes later it turns off and I have to try many times to boot it. Many times I let my phone on airplane mode at night at 53% battery and It drains completely. I tried other batteries but still the same thing. Did anyone ever experience this?
Thanks
Click to expand...
Click to collapse
I had a problem which was similar to this but the phone I got is LYF Flame 7.
My phone was automatically shutting down a few minutes after the device is locked, I investigated every setting to check whether anything like auto shutting down or sleep or something was enabled , but every settings were okay but the problem continued.
When I bought this phone, I was disabled a lot of useless stock apps . I re-enabled all these apps to their default and then the problem is solved.
So you just try reverting your apps to their default,if you have tried to disabled it.
Clear its Cache and Misc
Also try a factory reset and try to boot the phone without any SIM cards and SD card.
In my knowledge , I think , the problem of your phone is software related and hardware is okay.
And keep investigating in S3 threads.