Hey guys,
Sorry if this has been asked before, I did a search and didn't see anything.
A few weeks ago I noticed that my 2013 Flo was randomly powering down. I have noticed that this only occurs when the screen is shut down and it is allowed to go into deepsleep or hibernation as it will only occur after the screen has been off a few minutes. There is sometimes a series of four beeps after which the device powers down. If I turn on the screen after the beeps it comes up with the shutting down dialog as if I manually shut it down. I have tired to use various log recorders but all of them keep the system in wakelock and thus prevent this from happening.
I was wondering if anyone else has been having this issue, or know of any methods to debug this, and if it is a hardware issue thus meaning I should return my device or not.
Also: I am running PA 3.98 rather then stock but do not believe it to be caused by the rom.
There are some threads where people mention this happening because the "keep wi-fi on during sleep" setting not being checked as the root cause.
What's yours set to?
cowabunga said:
There are some threads where people mention this happening because the "keep wi-fi on during sleep" setting not being checked as the root cause.
What's yours set to?
Click to expand...
Click to collapse
It was set to never. Just put it on always. I'll see if that fixes it. Thanks
This just happened again so I dont think that fixed it.
Sorry for bumping this but it still is happening and I think I have tried everything. Does anyone know a way to fix this or should I try and swap my device for a new one and hope that works?
Swap it IMO
Sent from my HTC Sensation using xda app-developers app
Related
I know there might be a dozen threads about this, but its all gobbledygook and nobody seems to have a straight answer.
I just want to ask: What can we possibly do about Froyo draining our battery? Task manager auto-killers aren't working right now it seems.
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Task Managers??? Are you kidding me? My battery life has doubled since Froyo because I dont use task managers or auto killers. Use Fresh Rom, with set cpu with perflock off, change the screen off to 245/245. Most important part is condition your battery...Trust me, i thought it was stupid as well, but it works.
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
haha thats funny and true so i like it. i am running froyo official and have noticed an increase in battery. but hey when you get near your computer plug your phone in when you get in your car plug your phone in.
Froyo Killed Your Parents??
Sorry To Hear About Your Parents
R.I.P.
theres not much else u can do..just wait for a fix
I have ota and its the worst batterie ever with out doing nothing not even a phone call it died under an hour i only have gps enable had 3g off 4g to app all close no auto killer
Htc Evil Phone
I have the same problem. I read reports that Facebook 1.3 will not release the partial wake lock. I took FB 1.3 off and the problem persisted.
Here is how to check if you have a problem with your partial wake lock:
goto settings > about phone > battery and compare the uptime and awake time. If they are the same or very very close you have a wake lock problem. A wake lock allows an app to prevent your phone from going to sleep, even if the screen is off. If these times match then an app is creating a wake lock and not releasing it, and therefore your phone never sleeps.
As I said removing FB 1.3 did not solve the problem, but I was able to prove it is a wake lock as using Advanced Task Killer to kill 21 tasks allowed my phone to actually sleep, as indicated by a corresponding difference in the two times. So now that I know this is an app doing it, I will try to narrow it down and figure out which and report back.
OK I just found it. It appears the LED Light widget also causes a partial wake lock. To alleviate you don't need to uninstall it, just remove the widget.
Which led light? From market or the one with 2.2?
Borg1982 said:
Which led light? From market or the one with 2.2?
Click to expand...
Click to collapse
The new "flashlight" app is not a widget...It's actually called LED Light, by picolyl.
I don't have a problem, for me is little better!!!! just buy a new battery that solve your problem
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
Problem NOT solved. Or maybe 15 extra minutes.
Or don't use it at all, you'll save plenty of battery
Check to make sure that your Google Talk app is not automatically signing in. Go to apps - talk - settings. This is a typical battery drainer
totally forgot about google talk. have flashed a few ROMs back and forth, and now running a stock rooted ROM, I forgot to shut this one off...
use a custom rom, something without sense and try not to have a f***ton of widgets. im running cyanogen nightly and i get about 10 hours before i hit 20%-30% thats when i quit doing stuff and start trying to make the battery last. screen eats most of the battery so turn the brightness down.
my average 10 hours is 75-125 txts 30 + or - min of talk time and 3+ hours of internet (facebook)
oh, and about your parents... they are gone, there isnt an app or a rom that can fix that.
Indeed, the title of this thread is goofy. Froyo has literally killed my parents....... and has done a bad job for my battery life on my phone. Haha!
I guess an apostrophe would not have hurt after the word "parents" eh?
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
opie2l said:
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm having similar issues with my OMJ 2.2 froyo rom. poor battery life, plus it seems laggy and unresponsive. i was much happier with OMJ's 2.1 rom
Hello,
I recently noticed an issue with my wifi (stock 2.3.3), where an app that needs to update regularly didn't seem to be doing it when the screen was off. As the phone always sits on its dock when I'm at home, I "solved" the issue by making the screen never turn off.
However, today I decided to give SIPdroid another go, as I tested it when I first got my phone and it wasn't working properly. I found out why, the second I put the phone to my ear, the screen turns off and the sound cuts. If I take the phone away, I suddenly get all the audio high speed as it catches back up.
A bit of googling showed this to be a known issue, the wifi goes into power saving mode when the screen turns off - on SIPdroid there's an option to keep the screen off and it seems to work well, it just dims the screen instead. But that's still an unnecessary battery drain.
I had trouble finding any recent info on the issue (within the past 6 months), maybe I was just using the wrong keywords. So I thought I'd ask here. Does anyone know anything about this issue? Is it likely to be fixed in the next version of android if it ever comes to the desire HD? Maybe there's a fix out there already (preferably without rooting and/or installing custom rom, my phone is just right as it is now...).
Settings>Wireless & Networks>Wifi settings>Hit 'Menu'>Advanced>Wifi sleep policy>Never
That'll prevent the wifi turning off when the screen turns off.
Sent from my Desire HD using xda premium
I tried that before posting, it makes no difference whatsoever (besides, the sleep policy is either never or 15 minutes, this problem occurs the second the screen goes off).
If u re root: change radio... try anyone.
stock: mmm default reset to try. (i think)
No:
http://code.google.com/p/sipdroid/issues/detail?id=268
http://code.google.com/p/sipdroid/i...Status Priority Milestone Owner Summary Stars
Reading through the comments, it seems a more general android problem. A reset wouldn't fix it.
Also:
http://code.google.com/p/android/issues/detail?id=9781
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
The question is as short as the title. I've a Samsung Galaxy Note 3 & it has started showing issues where the CPU remains in lowest possible frequency (250Mhz) and it doesn't go to deep sleep.
I tried uninstalling all the apps that I installed in last 2 days but I can still see the issues.
Searching on google isn't helping either. Most of the posts that get in search results are the posts where people paste the betterbatterstats output. On the official wiki, https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/wlan_wake , it's mentioned that a sniffer should be used to debug.
I saw that most of the sniffers actually require root. So, how do I debug this wakelock without rooting my phone?
Thing to note is, I was not seeing this wakelock since a few days back and I started seeing it just today. I don't want to switch off the wlan while the screen is off & I actually want to fix this.
PS: Please help as I've actually very religiously searched on the internet and I'm unable to find the solution.
wakelock detector
Sent from my SM-N9005 using Tapatalk
Chenglu said:
wakelock detector
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
That's how I came to know about it (using BetterBatteryStats though). It's a kernel wakelock, not a partial one. So, it's not what's triggered by the apps and hence it isn't easy to find the app that's causing it.
At various places, people are suggesting that some app is constantly using the wlan0 and hence the wakelock but I'm not sure which one.
So, anyone knows?
Bump
shadyabhi said:
The question is as short as the title. I've a Samsung Galaxy Note 3 & it has started showing issues where the CPU remains in lowest possible frequency (250Mhz) and it doesn't go to deep sleep.
I tried uninstalling all the apps that I installed in last 2 days but I can still see the issues.
Searching on google isn't helping either. Most of the posts that get in search results are the posts where people paste the betterbatterstats output. On the official wiki, https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/wlan_wake , it's mentioned that a sniffer should be used to debug.
I saw that most of the sniffers actually require root. So, how do I debug this wakelock without rooting my phone?
Thing to note is, I was not seeing this wakelock since a few days back and I started seeing it just today. I don't want to switch off the wlan while the screen is off & I actually want to fix this.
PS: Please help as I've actually very religiously searched on the internet and I'm unable to find the solution.
Click to expand...
Click to collapse
Have you tried disabling automatic time zone in settings?
My note used to have this wlan_wakelock ,but after I disabled automatic time zone its' seems to be fine.
That's weird
tyrand3 said:
Have you tried disabling automatic time zone in settings?
My note used to have this wlan_wakelock ,but after I disabled automatic time zone its' seems to be fine.
Click to expand...
Click to collapse
How'll that even remotely effect wlan_wake?
Guys, I was really hoping if someone could help... Thanks
N900 Wakelock
Hi
I had the same problem
Sometimes it's happened when I change WIFI state (On/Of)
Follow this:
0)I use Cpu Spy app to determine wakelock & Deep Sleep Problems
1) go to Wifi settings & turn on Wifi
2) go to Advanced
3)Set "Keep Wi-Fi on during sleep" to "Never"
4)Wait some seconds (I used to turn off screen, wait for some seconds)
5) turn off wifi
if you want to use wifi, turn on wifi and set "keep Wi-Fi..." to "Always" or not.
Notice that befor turning of Wifi, set it to "Never"
notice that when your phone is connected to charger T before disconnecting charger, unlock phone and wait for a few seconds while screen is on, then disconnect charger,
4.3
N900
XXUCMK1
XXUCMK2
Few possible causes:
- Do you have Wifi Scanning set to enabled? (Wifi settings)
- Do you have Use Wifi Networks enabled in Location settings in both Settings and Googe Settings?
So for the last couple of days my HTC One M7 would recieve a notification and the screen would just stay on the entire time for no apparent reason. Im on latest OmniROM and its starting to bug me. Like for instance I get new mail on Gmail in the middle of the night. The screen turns on, it show the notification, and it doesnt turn off until I turn it off. If I restart, its fine for a few hours, but as soon as I get a notification, the problem reappears.
Nobody, seriously?
Sinistersky said:
Nobody, seriously?
Click to expand...
Click to collapse
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Entropy512 said:
Dude, you took less than 24 hours before bumping. Not everyone checks the forums regularly.
Also, per the FAQ, bug reports belong on jira.omnirom.org
However the behavior you describe is a feature in Omni. Let me guess - you turned on Active Display and forgot about it? (Since it's off by default, and the behavior you describe is not something I've ever seen on any device when AD was disabled.)
Click to expand...
Click to collapse
Nope.
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
VFO said:
Just to note, I am seeing the same thing on my nexus 5 running the 10/13 nightly. AD is disabled and I have never enabled it. I was wondering why sometimes I would pull my phone out of my pocket and the display would be on. Since reading this I have verified that this happens when I get a notification. I will submit a bug report on jira.omnirom.org.
eta: oops, I just realized you need an account for jira.omnirom.org.
Click to expand...
Click to collapse
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Entropy512 said:
This doesn't occur on any of my devices, including a Nexus 5.
Are you running some sort of notification customization app of some sort?
Define "screen on" - Lockscreen? Blank with backlight on?
Click to expand...
Click to collapse
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
VFO said:
I am not running any notification customization apps just straight Omni nightlies. It happens with any notification that I receive. It goes to the lock screen and stays on until I unlock it. I am going to wipe and reinstall the ROM and try and determine if it's an app issue.
Click to expand...
Click to collapse
Do you have "screen stays on while charging" enabled? Even then, it shouldn't be turning on for a notification in the first place.
None of my devices turn on for a notification in any situation, and the screen always shuts off quickly (faster than the screen timeout setting) when it's at the lock screen unless "screen stays on when charging" is set in Developer Options.