Does anyone else experience random delay when turning on (waking up) phone using either power or home button? Sometimes it takes almost 1.5 seconds before screen is lit up and sometimes only 200-400 ms.
If yes, is it a hardware problem or software and there are solutions to fix it?
criosray said:
Does anyone else experience random delay when turning on (waking up) phone using either power or home button? Sometimes it takes almost 1.5 seconds before screen is lit up and sometimes only 200-400 ms.
If yes, is it a hardware problem or software and there are solutions to fix it?
Click to expand...
Click to collapse
When the phone go into deep sleep i think 1.5 seconds should be normal
because cpu running 200khz,So 200-400ms it can turning on.
leamoor said:
When the phone go into deep sleep i think 1.5 seconds should be normal
because cpu running 200khz,So 200-400ms it can turning on.
Click to expand...
Click to collapse
Thanks...
Is there a way to prevent it from doing so? Previous generations of SGS didn't have this "feature" seemingly... At least the screen was turning on instantly, as far as I recall.
I daresay you can prevent it from deep sleeping somehow, expect battery drain though!
slaphead20 said:
I daresay you can prevent it from deep sleeping somehow, expect battery drain though!
Click to expand...
Click to collapse
Something must be wrong with SGS3... Tried HTC One X today - the screen goes on like instantly. This is really upsetting.
Found app in the market that prevents from entering deep sleep "Wake My Android Pro".
Right now device seem to wake within bearable 0.5 seconds. Will see how much battery life it will lose...
I came from HTC one s and got sgs 3 from work recently. It is true that the delay when turning on the phone is well noticeable compared to HTC phones.
As OP said, sometimes longer other times shorter. But I don't think 1.5 seconds is normal.
The reason I am saying this is because I had experienced very long delay about 1 to 2 sec starting mid last week. Then after recalling what application had I installed last week, I found one which caused the problem also drained battery. Uninstall straightaway. Since then, things are back to normal, it's not instant turning on, but definitely less than half second.
So maybe checking any suspicious app?
Sent from my GT-I9300 using xda app-developers app
criosray said:
Thanks...
Is there a way to prevent it from doing so? Previous generations of SGS didn't have this "feature" seemingly... At least the screen was turning on instantly, as far as I recall.
Click to expand...
Click to collapse
If you prevent that from happening, your battery will last only a couple hours, if that much.
You can prevent that from happening, but most tools I know requires root. changing the CPU governor and powersave features will make your phone "snappier", at the expense of battery life.
that feature is present in dozens of Android phones (where CPU supports the feature, which is the vast majority of them)
Simonetti2011 said:
If you prevent that from happening, your battery will last only a couple hours, if that much.
You can prevent that from happening, but most tools I know requires root. changing the CPU governor and powersave features will make your phone "snappier", at the expense of battery life.
that feature is present in dozens of Android phones (where CPU supports the feature, which is the vast majority of them)
Click to expand...
Click to collapse
No,without deep sleep battery already lasted 18 hours with some use. Cannot see any difference yet.
Also it doesn't make much sense - why previous generations were lasting as long as SGS3 but screen was turning on instantly?
the same problem exists in the galaxy Note 2
ricardoassaad said:
the same problem exists in the galaxy Note 2
Click to expand...
Click to collapse
I think it could be related to the technology used for the amoled screen of SGS3 and Galaxy Note 2...
Small update: without deep sleep over night battery went down by only 4%.
One more observation: when phone is charging the delay is almost not existent.
criosray said:
One more observation: when phone is charging the delay is almost not existent.
Click to expand...
Click to collapse
Because the device cpu running minimum200mhz when charging
I think its the Exynos processor. Every one i had that had that processor had the delay. Had galaxy s2 sprint had the delay switched to the skyrocket on at&t no delay. Had the galaxy s3 at&t model no delay switched to the exynos international and delay again. I use the no lock app and doesnt seem to hurt battery.
Sent from my GT-I9300 using xda app-developers app
leamoor said:
Because the device cpu running minimum200mhz when charging
Click to expand...
Click to collapse
Hmm, that doesn't make much sense to me... Did you mean at maximum CPU? Otherwise I'd assume waking it up would be slower or as slow...
u921333 said:
I think its the Exynos processor. Every one i had that had that processor had the delay. Had galaxy s2 sprint had the delay switched to the skyrocket on at&t no delay. Had the galaxy s3 at&t model no delay switched to the exynos international and delay again. I use the no lock app and doesnt seem to hurt battery.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thanks. That could explain it.
Related
Hello,
Im experiencing some lockscreen delay when i try to wake up the phone. I have rooted and flashed the original kernel back. When phone is connected to PC or charging its very responsive. Is there anyway to fix this? How do you do a factory reset?
Would be interested in an answer for this as well. I have the same situation, fast response to lock-button press when charging, few (2 +-1) seconds delay when not charging. I haven't rooted yet and have 2 pages of homescreen which have 5 widgets and 10 shortcuts/apps.
Is this normal behaviour, because the phone wakes up from a deep sleep state?
I think this is because of the phone being in sleep mode. It takes a second to wake up and increase the CPU speed and such... If you were to disable this, your phone would probably consume a LOT more battery. =/ But, heck, if it's only one second, it's worth waiting for, given that it's the most awesome phone you'll see until SGS3!
This used to happen all the time on JVK on SGS1.
This also happens to me and I just can not figure out what causes this? When the phone is on the charger it mostly doesn't happen. When I switch from Wifi to 3G, for a few seconds it doesn't happen... I cant figure it out what it is!
Same here, doesn't bother me that much though. What does bother me is, I first see the normal screen for just a moment and then the lockscreen. Anyone else got this to?
Sent from my GT-I9100 using XDA Premium App
It's because when the phone is uplugged and has been locked for awhile, the CPU downclocks to conserve energy. And when you wake the device up, it takes awhile to get the display going and bump the CPU speed back up.
This happened with my old HTC Desire with battery optimizations. When the custom roms start rolling in for the G S2, I guarentee there will be a 'fix' for this at the expense of battery life.
FYI, the delay isn't there when the phone is on charge/plugged in as the CPU doesn't downclock as drastically.
*EDIT*
TheGhost1233 said:
Same here, doesn't bother me that much though. What does bother me is, I first see the normal screen for just a moment and then the lockscreen. Anyone else got this to?
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
Yep, I've got that, as does the other 4 Galaxy S2's that have passed through my ownership due to replacements. It's completely normal don't worry.
drm111 said:
It's because when the phone is uplugged and has been locked for awhile, the CPU downclocks to conserve energy. And when you wake the device up, it takes awhile to get the display going and bump the CPU speed back up.
This happened with my old HTC Desire with battery optimizations. When the custom roms start rolling in for the G S2, I guarentee there will be a 'fix' for this at the expense of battery life.
FYI, the delay isn't there when the phone is on charge/plugged in as the CPU doesn't downclock as drastically.
*EDIT*
Yep, I've got that, as does the other 4 Galaxy S2's that have passed through my ownership due to replacements. It's completely normal don't worry.
Click to expand...
Click to collapse
I use Widgetlocker great lockscreen mod and the normal screen does not come up first.
I understand your explanation but this did not happen to my desire and it doesn't happen all the time (switch from wifi to 3g and stuff). I can get used to it but it would be nice if it would be instant!
DHel01 said:
I use Widgetlocker great lockscreen mod and the normal screen does not come up first.
I understand your explanation but this did not happen to my desire and it doesn't happen all the time (switch from wifi to 3g and stuff). I can get used to it but it would be nice if it would be instant!
Click to expand...
Click to collapse
It happens rarely, but I've used both widget locker and the stock lockscreen on this phone and it happens on both.
And no, it didn't happen on the stock desire, it only happened on my desire with the battery optimizations which downclocked the CPU to 133mhz i believe, so the G SII must be downclocking to around that speed when not plugged in.
drm111 said:
It happens rarely, but I've used both widget locker and the stock lockscreen on this phone and it happens on both.
And no, it didn't happen on the stock desire, it only happened on my desire with the battery optimizations which downclocked the CPU to 133mhz i believe, so the G SII must be downclocking to around that speed when not plugged in.
Click to expand...
Click to collapse
I think you are right about the downclocking because when I wake my SGSII RIGHT after a whatsapp message or something it works instantly. That means that the CPU is also awake to for a moment. Strangely, Setcpu doesnt affect this when I set 1200mhz on sleep. Oh well, lets await the custom roms!
How can I make my battery last longer? I am using set cpu and various profiles to give me the best optimization I can, however my phone barely makes it 10 hours with light use *1hr web browsing, avid txting, light music listening via music on phone ~ 1 hr as well.* I'm not faulting the phone. I just want to know what can be done to get the most out of the stock battery as I see people getting results twice as good as mine and just done get what I'm doing wrong here.
Thanks for the help in advanced.
I have the exact same problem as you. Are you using unnamed with Enthropy's experience kernal as well? I'm about to flash cm7 to see if I can get better results.
Sent from my SAMSUNG-SGH-I777 using xda premium
xAnimal5 said:
I have the exact same problem as you. Are you using unnamed with Enthropy's experience kernal as well? I'm about to flash cm7 to see if I can get better results.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I used cm7 for a while now using UnNamed and cm gave marginally better battey life but
Just use the dang phone . You dont need to do anything special for great battery life. Try a factory reset if theres a problem though. Im rooted on cog beta 4 getting amazing battery life. I talked my mom imto getting this phone over the new iphone and hers is completely stock and she knows nothing and doesnt close any apps and gets the same amazing battery life as i do.
Reset and use it. If you cant get through a day of heavy use the phone is defective.
Sent from my SAMSUNG-SGH-I777 using xda premium
roadrash7 said:
If you cant get through a day of heavy use the phone is defective.
Click to expand...
Click to collapse
+1....or you have wakelocks. Find BetterBatteryStats and CPUSpy. BetterBatteryStats will tell you if something is preventing the device from going into deep sleep. I like to use "wakelocks since unplugged." CPUSpy will tell you the amount of time your device spends in each frequency, including deep sleep. For this, you'll need to reset the timers each time you unplug the phone.
Its add easy as flashing cm.... I went 15 hours and still had 60% left. with OC. Nothing else special (aka no juice defender our set CPU). The only trick is deleting everything in the dcim folder (known medias bug ) you'll see 1% battery loss per hour, with fb and GV sync
Sent from my SGH-I777 using XDA App
Simba501 said:
+1....or you have wakelocks. Find BetterBatteryStats and CPUSpy. BetterBatteryStats will tell you if something is preventing the device from going into deep sleep. I like to use "wakelocks since unplugged." CPUSpy will tell you the amount of time your device spends in each frequency, including deep sleep. For this, you'll need to reset the timers each time you unplug the phone.
Click to expand...
Click to collapse
BBS sometimes misses wakelocks, for even more info, grab the contents of /proc/wakelocks and post them here.
my solution: keep a charger with you anywhere you go
I have a car charger, home charger and work charger (as do most people)
Thanks for all the replies. I'm sure there's go to be a work around for this
Not sure about a workaround. From everything I've seen, the max battery life is around six hours when the screen is on. Basically, if your screen has been on for 4-5 hours, it's time for a recharge.
Sent from my Galaxy S II using Tapatalk
arctia said:
Not sure about a workaround. From everything I've seen, the max battery life is around six hours when the screen is on. Basically, if your screen has been on for 4-5 hours, it's time for a recharge.
Sent from my Galaxy S II using Tapatalk
Click to expand...
Click to collapse
Well based on all I've read it seems like the battery is a mixed bag depending on the OC profiles, roms and kernels being used with the device.
Is it true that setting a screen off profile in set cpu will cause the device to not be able to enter a deep sleep mode and thus will kill the battery faster?
Sent from my SAMSUNG-SGH-I777 using xda premium
Alucardis666 said:
Well based on all I've read it seems like the battery is a mixed bag depending on the OC profiles, roms and kernels being used with the device.
Is it true that setting a screen off profile in set cpu will cause the device to not be able to enter a deep sleep mode and thus will kill the battery faster?
Click to expand...
Click to collapse
Not true. It is true, however, that on stock kernels and ones without the "sleep of death" fix, setting a screen off profile with a clock limit lower than 800 MHz can cause "sleep of death" issues. Right now I think only my kernel and the Cyanogenmod kernel have the SoD fix.
Entropy512 said:
Not true. It is true, however, that on stock kernels and ones without the "sleep of death" fix, setting a screen off profile with a clock limit lower than 800 MHz can cause "sleep of death" issues. Right now I think only my kernel and the Cyanogenmod kernel have the SoD fix.
Click to expand...
Click to collapse
Thanks for clearing that up
I'll post here as I don't have enough posts for the development forum yet.
I'm running Entropy's 16th exp kernal, and Cog4 and I noticed my battery draining far too fast, CPUSpy then showed that the phone simply isn't entering deep sleep. I had previously been undervolting with Voltage Control but I uninstalled the program just to be safe, still not deep sleeping. I also uninstalled Widgetlocker, and I don't think I have any apps that would cause infinite wakelock. What are some possible causes of this issue? Just so I have an idea where I should be changing things.
UPDATE: Reflashing the kernal fixed the problem for a while but then I reinstalled voltage control and now I seem to have it again. Uninstalling and reflashing again however, did not fix the problem. I am utterly confused
On another subject, has anyone actually noticed better battery life after undervolting?
Freaking SWEET! My battery lasted 33 hours and 13 minutes! I've only owned the phone for 3 days now and this is off of teh very 1st FULL charge! Usage was between light & moderate. Data sync on, Wifi On, GPS OFF, BT OFF, FB Data Sync OFF, Capacitative buttons set to light up only in the dark & NO haptic touchback...mmm, can't remember what else I tweaked at the moment but I think that's fantastic battery life! I'm upgrading from a G1 that couldn't last more than 17 hours when it was on standby ONLY with maybe 2 phonecalls and less than 20 text messages. I usually only averaged 6-8 hours and with SIMILAR usage in the last couple of days, I've been able to get 33+ HOURS? ^_^ <-- I'm very, very happy so far! This is on a stock root - NO custom ROM for me at the moment...I'm actually digging TouchWiz 4.0 which I thought I was going to hate when I played with the previous version of TW on the T-Mo Vibrant. (yes, my G1 was running CM 7.1 and battery life still sucked and I went through 2 different aftermarket batteries w/o any luck!)
Don't know what the voodoo in the programming is with this bad boy, but I think Sammy did a nice job this time!
The best thing you can do is having "Autostart" to prevent App to start automatically. I saved 25-30% on my SGS 1 and the same on my SGS 2 (i777). My son on the I9000 SGS 2 saved also 30%.
poker_rick said:
The best thing you can do is having "Autostart" to prevent App to start automatically. I saved 25-30% on my SGS 1 and the same on my SGS 2 (i777). My son on the I9000 SGS 2 saved also 30%.
Click to expand...
Click to collapse
Thanks for the tip
selfassembled said:
I'll post here as I don't have enough posts for the development forum yet.
I'm running Entropy's 16th exp kernal, and Cog4 and I noticed my battery draining far too fast, CPUSpy then showed that the phone simply isn't entering deep sleep. I had previously been undervolting with Voltage Control but I uninstalled the program just to be safe, still not deep sleeping. I also uninstalled Widgetlocker, and I don't think I have any apps that would cause infinite wakelock. What are some possible causes of this issue? Just so I have an idea where I should be changing things.
UPDATE: Reflashing the kernal fixed the problem for a while but then I reinstalled voltage control and now I seem to have it again. Uninstalling and reflashing again however, did not fix the problem. I am utterly confused
On another subject, has anyone actually noticed better battery life after undervolting?
Click to expand...
Click to collapse
Check for wakelocks in BetterBatteryStats, and if that doesn't find anything, do the following in an Android Terminal Emulator shell:
Code:
cat /proc/wakelocks > /sdcard/wakelocks.txt
or better, using ADB (Google it and if you're on Windows, Droid Explorer)
Code:
adb shell cat /proc/wakelocks > wakelocks.txt
Then post wakelocks.txt here
All the apps,camera n everything works on that rom? ??? I installed cm7 bt now stock it cuz some apps and camera app didn't work.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
I have recently realized that my phone had a lag/delay when turning of the screen to the lockscreen. When I press the power button, it would take about 1-1.5 seconds after I press the button for the screen to actually turn on. This does not happen while charging for me, only on battery. After screen on, the UI runs fine. This also never happened to me when I was on Gingerbread roms.
I am currently running Serendipity 9.2 with Cherrypicker kernal because I like the UI, but I still get the screen-on lag
I have tried ShoStock 2, Foxhound, AOKP, Serendipity 9, Mystic and ShirShirRomICS
and comboed those with all of the different kernals: Siyah, Fluxxi, Cherrypicker and NEAK. All this to no avail
I was wondering if this is only happening to me, because it slightly annoys me that I need to wait, since it makes the phone feel like its not as speedy as it should be.
If somebody can help me solve this I will be SOO GRATEFUL!
Thank you so much!
I forget which thread but entropy said screen delay is about that long now. Its a Samsung thing that can't be worked around
Sent from my SGH-I777 using Tapatalk 2
awww, Hopefully entropy will find a way
Maybe its because its not based on the Official i777 one?
but was it just me or did GB roms not have the delay?
Takes mine an avg of .5 seconds. Sometimes it's almost instant, other times it's near 1 second, but the avg would be close to .5 - I wonder if that will change the longer I've got this phone?
Clay
Sent from my SGH-I777 using XDA
Mine turns on basically instantly
Sent from my SGH-I777 using Tapatalk 2
Nick281051 said:
Mine turns on basically instantly
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
What rom and kernal are you using?
george.z.he said:
What rom and kernal are you using?
Click to expand...
Click to collapse
Fluxii 6/2 and Task's aokp 6/3
Sent from my SGH-I777 using Tapatalk 2
george.z.he said:
awww, Hopefully entropy will find a way
Maybe its because its not based on the Official i777 one?
but was it just me or did GB roms not have the delay?
Click to expand...
Click to collapse
GB had about .5 sec delay. Ics is close to 1 sec
Sent from my SGH-I777 using Tapatalk 2
Mine used to do the same. After a new aokp build 36 Install the lag went away- maybe a coincidence?
Sent from my SGH-I777 using XDA
Try upping your lowest frequency step if you have your min set to 100/200mhz on your governor, change it to 500mhz and see if it stops happening. (Works for me, only happens on certain I/O schedulers and governors however.)
Sent from my SGH-I777 using xda premium
cepsbow said:
Try upping your lowest frequency step if you have your min set to 100/200mhz on your governor, change it to 500mhz and see if it stops happening. (Works for me, only happens on certain I/O schedulers and governors however.)
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Which I/O scheduler and governed do u use?
Sent from my SGH-I777 using xda premium
On demand and noop were the most stable for me. However it varies by device, not all sgs2 are created equal. I would suggest trying a few and see which runs most stable for your phone as the kernels governors vary (I was experiencing this issue with siyah and Neak on various aokp builds (35-37). Conservative/noop & vr with Neak and powersaver & performance / cfq & vr for both on siyah)
Currently on stock aokp 6-3 with tasks kernel, he truly overhauled the kernel, works better than any alternate kernel I've run so far with no issues on any oc/uc/uv settings.
Sent from my SGH-I777 using xda premium
If I recall correctly from the discussion many months ago (I think it was in Entropy's DD kernel thread for GB) there is basically a .65 second delay from power button press to screen on when waking from deep sleep on the SGS2 - and this is a hardware limitation, not software.
When you are seeing quicker screen wakes it is because the device was not in deep sleep at the time of the press of the power button. In the case of waking from a non-deep-sleep condition, probably the lowest idle clock speed or current clock speed (set by whatever background process has the phone awake) will be the controlling factor in how fast the screen wakes up.
I could be completely wrong here...someone please correct me if so...
dandrumheller said:
If I recall correctly from the discussion many months ago (I think it was in Entropy's DD kernel thread for GB) there is basically a .65 second delay from power button press to screen on when waking from deep sleep on the SGS2 - and this is a hardware limitation, not software.
When you are seeing quicker screen wakes it is because the device was not in deep sleep at the time of the press of the power button. In the case of waking from a non-deep-sleep condition, probably the lowest idle clock speed or current clock speed (set by whatever background process has the phone awake) will be the controlling factor in how fast the screen wakes up.
I could be completely wrong here...someone please correct me if so...
Click to expand...
Click to collapse
Then is it possible to turn off deep sleep? And does it drain a lot of battery if it is not in deep sleep?
I realized when playing music or when the BLN notification is on it wakes instantly.
george.z.he said:
Then is it possible to turn off deep sleep? And does it drain a lot of battery if it is not in deep sleep?
I realized when playing music or when the BLN notification is on it wakes instantly.
Click to expand...
Click to collapse
Yes it is possible to turn off deep sleep. There is an app in the market called "wakelocker" or something similar. You can find references to it in the very early ICS ROMs for the i777, as it was used to avoid the random screen-ons we were having. It can be set up to hold a permanent wakelock.
However, you should expect to drain between 5 and 10% battery per hour idle if you are wakelocked all the time. In other words, your battery life will completely tank if you do this. Most people around here do anything and everything they possibly can to prevent wakelocks, as this is the best way to improve device-idle battery life. As someone mentioned in the AOKP thread, screen on delay is a sign of good sleepiness (or something like that - I'm paraphrasing cause I don't want to bother to go look)... If I were you, I'd leave it be...
My SGS2 has a 5-6 seconds delay before waking up from deep sleep. I noticed that after I take the phone away from my ear after a call the screen takes very long to turn back on, as if the proximity sensor is sleeping away.
This is definitely not because of my last firmware update because it simply didn't happen after I installed it. It was just impressively fast. This new behavior started about 3-4 weeks ago, I can't figure out right now whether I installed something that could produce such behavior.
Build number: IML74K.XWLP7
Kernel version: 3.0.15-I9100XWLP7-CL340913 [email protected] #3 (rooted)
Baseband: I9100XXLPS
LE: I have the european version.
pcamlin said:
Mine used to do the same. After a new aokp build 36 Install the lag went away- maybe a coincidence?
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Yeah,mine as well and have no idea if it's a coincidence,seems like an old radio will get back to work after some beats...
Yeah as said above, it is a hardware thing combined with the state of the processor. The reason some people's turn on very rapidly is because their processor is already doing something, aka not sleeping. You should have at minimum probably a half second to maximum 2 second delay from pressing the button to your screen coming on. Otherwise your battery would be terrible.
Sent from my new and improved SGH-I777 with AOKP!
dogfax said:
Yeah as said above, it is a hardware thing combined with the state of the processor. The reason some people's turn on very rapidly is because their processor is already doing something, aka not sleeping. You should have at minimum probably a half second to maximum 2 second delay from pressing the button to your screen coming on. Otherwise your battery would be terrible.
Click to expand...
Click to collapse
How does HTC do it then? My wife's stock Inspire wakes literally instantly, and its idle battery drain is even better than my S2 running AOKP/Fluxi. This is proof to me that Samsung could be designing things a little better...
mattdm said:
How does HTC do it then? My wife's stock Inspire wakes literally instantly, and its idle battery drain is even better than my S2 running AOKP/Fluxi. This is proof to me that Samsung could be designing things a little better...
Click to expand...
Click to collapse
I was just thinking the other day why did I get rid of my Inspire...
Oh yeah... cuz I have a thing for phones
refer to post #6 and onwards.
Theshawty said:
So, it seems Samsung phones in general have a 1 to 2 second wake-up lag and mostly it doesn't seem to matter if you run on the stock firmware or on a custom firmware based on AOSP.
Why do most/all Samsung devices have this and does it haunt them in general? Galaxy Nexus didn't have it, yet it's made by Samsung? (though with Google's standards)
Click to expand...
Click to collapse
It's waking up from deep sleep and that takes 1-2 sec. Widgetlocker seems to be little quicker than the original stock locker.
Casanoaa said:
It's waking up from deep sleep and that takes 1-2 sec. Widgetlocker seems to be little quicker than the original stock locker.
Click to expand...
Click to collapse
Why is this only plaguing Samsung devices but not Samsung-Google devices and all other android devices?
Are you saying a different CPU governor and a slightly higher minimum frequency could help it?
Are you saying a different CPU governor and a slightly higher minimum frequency could help it?
Click to expand...
Click to collapse
Actually he's saying that another lockscreen than the default one should be faster since less extravagant.
All Android devices have a lag when waking up from deep sleep, exactly as do other devices such as computers.
Deep sleep means the system is actually in a sort of standby, the kernel and all processes have to resume normal operation and the CPU being clocked up before you can use it again.
You could prevent deep-sleep but that would drain your battery since at least one cpu-core needs to be online 24/7 in that case.
d4fseeker said:
Actually he's saying that another lockscreen than the default one should be faster since less extravagant.
All Android devices have a lag when waking up from deep sleep, exactly as do other devices such as computers.
Deep sleep means the system is actually in a sort of standby, the kernel and all processes have to resume normal operation and the CPU being clocked up before you can use it again.
You could prevent deep-sleep but that would drain your battery since at least one cpu-core needs to be online 24/7 in that case.
Click to expand...
Click to collapse
Would it have anything to do with idle+lpa (deep idle)? I don't think that the nexuses have deep idle activated in the kernel.
Sent from my GT-I9300 using xda premium
Let's say if one with normal to less use get's around 2 days of battery time, and with heavier use around 1 day 15 hours both with deep idle activated. How much less would this be with deep idle (IDLE+LPA) completely off?
I mean, the Galaxy Nexus has a lower battery mAh than the S3, so theoretically the battery should still last a lot longer than 1 day with medium-heavy usage? Plus, I don't mind charging every night.
I am currently running CM10.
Theshawty said:
Let's say if one with normal to less use get's around 2 days of battery time, and with heavier use around 1 day 15 hours both with deep idle activated. How much less would this be with deep idle (IDLE+LPA) completely off?
I mean, the Galaxy Nexus has a lower battery mAh than the S3, so theoretically the battery should still last a lot longer than 1 day with medium-heavy usage? Plus, I don't mind charging every night.
I am currently running CM10.
Click to expand...
Click to collapse
Even underclocked and undervolted and tweaked getting a full 24 hours of actual medium to heavy use (not idle, since most of the uptime on a device is idle) is pushing it. If you set deep sleep/idle off your phone would die in a day~ without even touching it, would be like your using your phone with light use I suppose. The google phones do this also, every android does.
Just a guesstimate, those features are there for a reason. Not only will the device drain battery faster but its will also cause more wear and tear on the hardware.
Cdjones187 said:
Even underclocked and undervolted and tweaked getting a full 24 hours of actual medium to heavy use (not idle, since most of the uptime on a device is idle) is pushing it. If you set deep sleep/idle off your phone would die in less than a day without even touching it. The google phones do this also, every android does.
Click to expand...
Click to collapse
First of all that's not true.
It wouldn't die in less than a day without touching it.
I can leave my galaxy nexus and not touch it and it will stay on for over 3 days, and they don't have deep idle.
He isn't trying to remove deep sleep, he wants to disable deep idle.
Different thing completely.
Sent from my GT-I9300 using xda premium
nodstuff said:
First of all that's not true.
It wouldn't die in less than a day without touching it.
I can leave my galaxy nexus and not touch it and it will stay on for over 3 days, and they don't have deep idle.
He isn't trying to remove deep sleep, he wants to disable deep idle.
Different thing completely.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Exactly! None of the Google devices as far as I know have deep idle enabled (but deep sleep), and the battery life was more than decent. I could get over a day of medium use, and approx 18h of heavy usage but I don't mind charging every night. I've been charging my phones every night since many years back, so it's a habit of mine. I'm just happy if it gets me 8h.
I had an LG G Pro and when i went to sleep every night the phone was at 100% and it would be like that for 8 hours of sleep, now with my Galaxy S5 the phone will consume 1% in 8 hours. I know that's nothing but why is it doing that if i'm not using the phone.
TikyPR said:
I had an LG G Pro and when i went to sleep every night the phone was at 100% and it would be like that for 8 hours of sleep, now with my Galaxy S5 the phone will consume 1% in 8 hours. I know that's nothing but why is it doing that if i'm not using the phone.
Click to expand...
Click to collapse
It all really depends on what your phone is doing or what is running in the background.
If you want to get to the root of the problem ( stand by for pun ) you should root your device (eyyyy ) but seriously root it and install wake lock detector. See what is using your phone and waking it up out of sleep. It could be that it randomly looses signal and starts searching for it during the night or it could be something like Facebook waking up and checking for updates.
The lg g pro has a stronger battery thats y
Sent from my SM-G900T using Tapatalk
You make is sound like you lost 1% of battery in 8 hours... umm that is actually quite good, amazing actually. Whats the problem?
Gerr1985 said:
You make is sound like you lost 1% of battery in 8 hours... umm that is actually quite good, amazing actually. Whats the problem?
Click to expand...
Click to collapse
It's not a problem, is just that if the phone screen is off and i'm not using it at all. It's not suppose to lose 1% of battery. I'm going to try what
Sparatan117
Click to expand...
Click to collapse
Said.
TikyPR said:
It's not a problem, is just that if the phone screen is off and i'm not using it at all. It's not suppose to lose 1% of battery. I'm going to try what Said.
Click to expand...
Click to collapse
1% in idle is still amazing. Unless the phone is powered down, I'm not sure how you can really get much better than that.
"Samsung’s press materials say that the phone offers about 390 hours of standby time with LTE on." - Still insanely impressive and you probably have to have Ultra Power Saving mode on, which puts your phone's appearance and operations in crap mode.
If you lost 1% every 8 hours, then you will be getting roughly 800 hours of standby, which is double what Samsung claims you can achieve.
If you are going by what the other poster said, then he/she is likely referring to having the phone rooted and applying the "Greenify" app. This will hibernate anything, including system apps. I do hope you have luck with that... for some reason, when I use Greenify on this phone, I get worse battery life than with it off. I"m too lazy to tinker with it...
you do know that the phone is still on consuming power / electricity during idle/sleep mode, right...? I get about 3 days idle if I rarely use the phone and have like 11 things syncing stuff, which I find good.
Gerr1985 said:
1% in idle is still amazing. Unless the phone is powered down, I'm not sure how you can really get much better than that.
"Samsung’s press materials say that the phone offers about 390 hours of standby time with LTE on." - Still insanely impressive and you probably have to have Ultra Power Saving mode on, which puts your phone's appearance and operations in crap mode.
If you lost 1% every 8 hours, then you will be getting roughly 800 hours of standby, which is double what Samsung claims you can achieve.
If you are going by what the other poster said, then he/she is likely referring to having the phone rooted and applying the "Greenify" app. This will hibernate anything, including system apps. I do hope you have luck with that... for some reason, when I use Greenify on this phone, I get worse battery life than with it off. I"m too lazy to tinker with it...
Click to expand...
Click to collapse
Thanks for The Fast Replys And Overall everything
TikyPR said:
It's not a problem, is just that if the phone screen is off and i'm not using it at all. It's not suppose to lose 1% of battery.
Click to expand...
Click to collapse
How can you expect any electronic device that is ON to not have any battery consumption over 8 hours? obviously it needs to consume power to stay powered on...cpu is still running..cellphone still needs to maintain communication to the cell towers...syncing is still happening...running apps or system apps are still updating their status....
devoidx said:
How can you expect any electronic device that is ON to not have any battery consumption over 8 hours? obviously it needs to consume power to stay powered on...cpu is still running..cellphone still needs to maintain communication to the cell towers...syncing is still happening...running apps or system apps are still updating their status....
Click to expand...
Click to collapse
Exactly.
Sent from my SM-G900T using XDA Free mobile app
Could be s5 battery is smaller than your old phone or u have more stuff syncing
Sent from my SM-G900T using Tapatalk
raw2000j said:
Could be s5 battery is smaller than your old phone or u have more stuff syncing
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Could also be because the S5 just uses more power than the G Pro when on standby. I highly doubt it used less than 1% power in 8 hours though...
Just found out something, not sure if it helps, but I did notice a significant increase when you turn off location services for Google apps... namely the ability for Google maps to access your surrounding area and probe it for updated information. I saw an immediate increase after 19 hours I was at 62% having used the phone for regular use... so I think this might be the main culprit, although I'm not sure what LG is doing. I suspect that there is some sort of background killer in there working behind the scenes though.