Database Users

Questions about standby mode

I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?

chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.

All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..

Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!

Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.

Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.

OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.

cool, thanks. I'll try this today.

chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.

Anyone having these strange random kernel issues in KLA4?

I'm using CF's rooted kernel and nothing else on my KLA4 Note. No other alternative kernels, just the stock one. And yet I keep seeing strange issues with the kernel. Is anyone getting any of these two?
1) gps causing a wakelock in betterbatterystats in kernel section
2) fuelgauge also causing a wakelock in betterybattery states in kernel section
It doesn't happen often, but it has happened out of the blue. And before you ask, no, GPS was never enabled, no apps I have in my phone are using GPS too. Happened over the weekend with no other activity on the phone other than some calls. A reboot fixed it.
As for the fuelgauge thing, I have no idea either. It happened after removing my phone from a charger, and noticed that the battery was draining fast. Sure enough looking at BBS, I see fuelgauge wakelocking in kernel, whatever that is. A reboot fixed it.
Anyone else facing these strange issues?

If it helps to know, I have it too. I seem to be able to trigger the GPS wakelock issue when the Browser attempts to fix my location but is somehow unable to. But not always.
Fuel gauge. Seems random, but it might be related to the battery being too stressed and the level "rising" a bit when relaxed.
I've tried the stock android kernel and now am CFRoot kernel with Checkrom v5. If anything the gps issue has increased.

I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now. No wakelocks except those for sync. Phone has deep sleep now and the battery life is outstanding.

Blue1k said:
I had a high Android OS usage with CF kernel and LA4. I switched to Abyss Kernel and the OS usage is next to none now
Click to expand...
Click to collapse
I had the same with stock kernel. On low-use days my kernel was using 40% of the battery!
It finally forced me to flash a kernel, and I chose Abyss. Kernel is now less than 5% pretty much all the time. Deep sleep is also most of the time, although I did not check well before that.

My phone randomly reboots. This happened over a few weeks ago, I wiped cache and monitored it, it fixed it.
Today, it just rebooted.
I think its more a software problem rather than hardware.
Any suggestions.
P.S. Not to threadjack, but I am also on LA4 CF Root with CheckROM

There's a separate thread in the Q&A section about the GPS Wakelock problem.
http://forum.xda-developers.com/showthread.php?t=1419087
Some ideas to try and avoid it, but unfortunately nothing definitive yet.
Just as an aside, personally I've been using the 'wake up lag' characteristic of the exynos when coming out of Deep Sleep as a clue to these wakelocks. If the screen comes on immediately, I suspect a wakelock of some sort and check BetterBatteryStats and CPUSpy.

[issue] Need some feedback from GB users

hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.

ellokomen said:
hello, I would like to know if I'm alone on this issue, right now I'm running stock 2.3.6 on my i9100 and I have found an issue.
When Power saving mode is activated (the default one), if I open the camera app and turn off the screen for 1 minute, the phone dies and I have to reset it to make it work again.
Some friends told me that on ICS it doesn't happen so I was wondering if I got a faulty unit or this OS has this bug.
I would like some feedback from you guys with gingerbread onboard, thanks.
Click to expand...
Click to collapse
This has never happened to me, but maybe try to turn off the device and take the battery out, leave it for a minute and reinsert the battery and restart. Then try to reproduce the problem.

Never happened to me or even heard of it
Sent from my GT-I9100

have you tried to see if this bug would occur without power saver mode on?,i never had this issue before nor heard of it

thanks everyone for your answers and concerns, the problem has been isolated:
It was a bug caused by a underclock that I did have that so far only occurs on the circumstances that I had on my phone.
When your phone turns off the screen, it will go to sleep mode or deep sleep mode depending on the running apps you have in that moment, these modes allow the CPU to low the frequencies (CPU Clock) in order to preserve battery life.
Comes to public interest that when using the camera app, the phone uses a high frequency clock to process photos and videos taken with the camera.
As because I did have a custom kernel that tweaks the CPU in order to gain more battery life, when battery saver option (which slow the max freq. clock of the CPU) was ON in my phone, the phone couldn't jump directly from sleep mode to max freq mode to keep camera app running and the CPU kept "slept"
If serves as interest of anyone, the kernel I was using was Siyah Kernel (don't remember which version, just check out the date this thread was posted and compare it with siyah kernel log to know by that date which was).

Phone freezing in deep sleep; should I request an RMA?

I've been having a recurring problem where my phone will lock up in a deep sleep, leaving the phone completely off. In order to restart the phone, I have to hold Power and Vol Down which takes me to a charging logo, and then hit power again. This generally happens overnight when the phone is charging, but I've also had it happen once while making a VoIP call. I thought I resolved the issue by wiping the phone and flashing the stock 4.2 ROM. However, the issue just occurred last night after 4 days of bug-free usage.
My question is whether this is some sort of weird software bug or a hardware issue. I haven't seen others report identical behavior but I've seen lots of complaints about freezing and random reboots that seem to be due to software. Should I request an RMA?

+ 1 . I am having the same issue. I would say hang tight. Call the support team and let them know you are having issues. If atfer a few weeks the problem persists perhaps go through an rma. I suspect it is software related. Lets say you did RMA still had the issue then had a dead pixel or other problem? It would suck and you would have to go through the whole process again. rinse and repeat. Only if you want to return the device for a full refund, then I would say hurry up and make that call. My .02 Good luck.

NexUsandThem said:
+ 1 . I am having the same issue.
Click to expand...
Click to collapse
+1
Having the same issue. Although no clear pattern is visible. Sometimes I find the phone dead-locked after putting it aside for 10 minutes and sometimes it seems to run for a day or even two without issue. Running _motley kernel right now without any change on this front.
I rather think it's a software issue than hardware. So I am not going to RMA it.
Strangely when I power off the phone on such a lock-up and then reboot it I will see a substantial drop in battery after the reboot. So the phone seems to be in some state where it still drawns more battery than in normal operation. E.g. with _motley kernel and limited clocks I typically see 3-5% battery drop over night only. When it locks up during the night and I reset it in the morning then battery usually drops much more (e.g. 30-50% is gone). Maybe it's caused by some hanging/deadlocked driver.

If you full factory reset and flashed then i'd say some app of yours is causing the issue.

shotta35 said:
If you full factory reset and flashed then i'd say some app of yours is causing the issue.
Click to expand...
Click to collapse
In fact I got the device in dec 2012. Started to set it up and then decided to root it (including full factory reset). I only have a very minor amount of system-level applications installed. Actually the main reason to root was to use Voltage Control as I intended to limit clock rates and (if possible) voltages the same way I was used to do it on my Galaxy Tab 7 (P1000) where I was very pleased with 6-days battery lifetime.
Initially I found the minimum clock rate was set to 1GHz and I have reduced it to 304MHz (minimum with stock kernel). When I discovered first freezes/lock-ups then I reverted to default settings and found it still locking up occasionally. Meanwhile I am using _motley kernel which seems to include some voltage mod as well. Although Voltage Control does not show options to modify voltages. Then I found Trickster MOD which shows some voltage control but it seems to have no effect (at least I was used my galaxy tab to crash when undervolting too much and it's pretty "strange" to be able to set all clock voltages to 0.6V while still running stable; so I guess the settings won't have any effect right now).
I have also tried to remove all modifications and applications and/or profiles which could cause the issue without any difference. Even when run stock settings it occasionally completely locks-up the device.
Edit: I was wrong regarding voltages. In fact I found my device happily works at 1134MHz using 600mV. Since I am used to limit max clock rates to 810MHz I could simply put all voltages to 600mV without seeing a crash/reboot.
CAUTION: This does not necessarily have to apply to all devices. My one is "faster" binned Rev. 11 device. Some voltages of different users are collected here: https://docs.google.com/spreadsheet/ccc?key=0AnlqtEwFJwR6dE55WkZYSThEM3U4SGtKMVl2V1VqMmc#gid=0

[Q] [SOLVED, kinda] Weird battery drain for no apparent reason

Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa

gilboa said:
Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
Click to expand...
Click to collapse
Buy a new battery, maybe this will solve the problem...

gilboa said:
Hello all,
I own an international N9005.
Up until recently, I used the stock Samsung ROM with good battery life.
A couple of weeks ago, with no apparent reason, I started getting horrid battery life - in access of 10% drop -per hour- in idle (as opposed to 1-3%).
I removed more-or-less everything, disabled more-or-less everything but nothing seems to work.
Got root (there goes the warranty) tried looking for Wake-locks and nothing. The Note3 is 97% (!!!) awake even with everything disabled, and in the wake looks screen both user and kernel I only see 1-2 minutes (!).
Tried resetting the ROM, tried installing other custom ROMs (X-Note, Omega, etc). Nothing seems to work.
Currently I'm running Omera v20, with *zero* applications installed (including all the Google and Samsung applications beyond Google Playstore) and all external services (location, WIFI, et-al) disabled, my note 3 is still 95-99% awake, and the list of wake lockers is, errr, empty.
FWIW I'm ~100m from the nearest cell tower.
EDIT: According to battery meter, Android OS is keeping the phone up.
Any ideas?
- Gilboa
Click to expand...
Click to collapse
Indexing your external SD maybe?
You could try the link in my sig and try again for your custom ROM.

First, thanks all for taking the time to answer.
I'm thinking about getting a new battery, but my gut feeling is that its not the source of amazing battery drain - ~20%/h while completely [!] idle (auto-sync/location/etc completely off).
I've attaching /d/wakeup_source in excel format sorted by count and total time - in-case someone has any idea what's completely broken.
As far as I can see, qpnp-vadc-ebd30a00, sec-battery-monitor, mmc0:0001:2 are the main culprits.
nicholaschum,
Before I attempt a complete wipe (as opposed to the normal wipe data / cache), how can I detect if someone is indexing my sdcard? (which may account for the mmc0:0001:2 in the wake lock dump).
- Gilboa

I know this is a long shot but try turning off developer options if you have it turned on(especially force gpu rendering). Somehow I found out that when I turned it on and the screen is idle. I get a battery drain. Not as big as yours. But not really sure because if I use the phone, the battery is actually pretty great(an hour of screen time is about 10% even more with internet apps like facebook youtube chrome etc.).
Clear cache. I know this is too common but it actually works for a lot of people.
Lastly, try airplane mode overnight and see if it doesn't drain. It might be your network that is causing the drain.

gilboa said:
First, thanks all for taking the time to answer.
I'm thinking about getting a new battery, but my gut feeling is that its not the source of amazing battery drain - ~20%/h while completely [!] idle (auto-sync/location/etc completely off).
I've attaching /d/wakeup_source in excel format sorted by count and total time - in-case someone has any idea what's completely broken.
As far as I can see, qpnp-vadc-ebd30a00, sec-battery-monitor, mmc0:0001:2 are the main culprits.
nicholaschum,
Before I attempt a complete wipe (as opposed to the normal wipe data / cache), how can I detect if someone is indexing my sdcard? (which may account for the mmc0:0001:2 in the wake lock dump).
- Gilboa
Click to expand...
Click to collapse
Hi, basically just check your phone using BBS (BetterBatteryStats), and see which individual process is eating up your battery.

Graffiti Exploit said:
I know this is a long shot but try turning off developer options if you have it turned on(especially force gpu rendering). Somehow I found out that when I turned it on and the screen is idle. I get a battery drain. Not as big as yours. But not really sure because if I use the phone, the battery is actually pretty great(an hour of screen time is about 10% even more with internet apps like facebook youtube chrome etc.).
Click to expand...
Click to collapse
I had the developer options off and on. Didn't seem to help.
Clear cache. I know this is too common but it actually works for a lot of people.
Lastly, try airplane mode overnight and see if it doesn't drain. It might be your network that is causing the drain.
Click to expand...
Click to collapse
If the current state doesn't hold (see below), I'll give it a try. Good thinking
nicholaschum said:
Hi, basically just check your phone using BBS (BetterBatteryStats), and see which individual process is eating up your battery.
Click to expand...
Click to collapse
Already installed - together with WakeLockDetector.
Short update, out of pure desperation I completely wiped the phone (including sdcard), tried installing stock ROM and, err, Odin failed. Managed to get CWM running again and installed the latest CM nightly.
...
As weird as it sounds, going from NF4 based ROMs (including stock) to CM nightly dropped to idle battery usage to ~2-6%/h, a huge drop from ~20%/h.
I'll update and mark resolved if this situation holds (crosses fingers).
- Gilboa

gilboa said:
I had the developer options off and on. Didn't seem to help.
If the current state doesn't hold (see below), I'll give it a try. Good thinking
Already installed - together with WakeLockDetector.
Short update, out of pure desperation I completely wiped the phone (including sdcard), tried installing stock ROM and, err, Odin failed. Managed to get CWM running again and installed the latest CM nightly.
...
As weird as it sounds, going from NF4 based ROMs (including stock) to CM nightly dropped to idle battery usage to ~2-6%/h, a huge drop from ~20%/h.
I'll update and mark resolved if this situation holds (crosses fingers).
- Gilboa
Click to expand...
Click to collapse
I heard there were problems with NF4 battery. But I haven't been on TW since ND4. No matter what on Note 3 TW the battery sucks. AOSP is great. But actually S5 port has the best battery.

Solved, at least for now.
nicholaschum said:
I heard there were problems with NF4 battery. But I haven't been on TW since ND4. No matter what on Note 3 TW the battery sucks. AOSP is great. But actually S5 port has the best battery.
Click to expand...
Click to collapse
I use Nova (and not TW)
Either way, latest nightly seems to solve the battery drain problem completely - using the same Nova and system configuration (widgets, active syncs, etc). Currently I'm at ~1.5-0.8%/h when idle with no issues going into deep sleep.
Seems that my specific model really dislikes NF4.
Thanks again for trying to help.

This thread has been quite helpful as I was suffering with a Battery Drain after the NF4 Upgrade.
Planning to go back to ND5, which was the last stable version.

JazonX said:
This thread has been quite helpful as I was suffering with a Battery Drain after the NF4 Upgrade.
Planning to go back to ND5, which was the last stable version.
Click to expand...
Click to collapse
I was thinking about doing the same, but in the CM 11 runs circles around both NF4 (duh!) and my previous ROM (not sure which revision it was) - plus I can actually get 2 days of standby time, even with the old batteries, so I'll stick with CM 11 for now.
- Gilboa

gilboa said:
I was thinking about doing the same, but in the CM 11 runs circles around both NF4 (duh!) and my previous ROM (not sure which revision it was) - plus I can actually get 2 days of standby time, even with the old batteries, so I'll stick with CM 11 for now.
- Gilboa
Click to expand...
Click to collapse
CM11 is not an option for me. No 4k Video Recording, Worse Camera than TW, S-Pen Functions Removed... Nope. Cant survive with CM11.

JazonX said:
CM11 is not an option for me. No 4k Video Recording, Worse Camera than TW, S-Pen Functions Removed... Nope. Cant survive with CM11.
Click to expand...
Click to collapse
I can relate.
Good luck, and post if you find a solution (in-case I decide to switch back to Samsung based).