My phone was on standby for quite a lot of time, yet I see the CPU being kept awake for more than a day.
it says that it have been awake for this period, but its counting together all periods of cpu activity.....
Oh my bad then. Thanks
Sent from my Xperia S using xda app
Related
I have my vibrant running perfect on nightly 15 and I was just wondering why I'm getting such high standby drain. About 24% for some reason even with 3g/wifi/GPS/bt off. I have it on stock kernell and updated to kb5 radio. Should I just keep trying new radios?
Sent from my SGH-T959 using XDA App
Download cpuspy from the market. It keeps track of the time spent in different states (ie deep sleep, 100mhz, 200mhz, etc). Check to see if your phone enters deep sleep and for how long. If it isn't, your governor might be set to performance, which means it stays out.of deep sleep and elevates on speed unnecessarily for regular use, or you have an app that is running rogue and keeps scaling up your CPU.
Sent from my SGH-T959 using XDA App
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.
Hello,
Place base don't shoot me if I am asking the same question again. I am using CM10 jelly bean Epinter. My battery used to last two days on fully charge but after rooting and installing jelly bean, its hardly last 1 day after average use.
Phone idle state is consuming 33% of battery. Here is the screenshot attached.
I would really appreciate your help to decrease phone idle state battery consumption.
Sent from my MB860 using xda app-developers app
I apologize for misspellings.
Sent from my MB860 using xda app-developers app
Likewise it's killing me too.
In my case the drain is closer to 50 %. This appears to be a recent development. How can I track down the source of the problem?
marathamola said:
I apologize for misspellings.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
both should install cpuspy to see if the phone is entering in deep-sleep...
it might be the bluesleep bug thah is discussed on development forum, you could try that
marathamola said:
Hello,
Place base don't shoot me if I am asking the same question again. I am using CM10 jelly bean Epinter. My battery used to last two days on fully charge but after rooting and installing jelly bean, its hardly last 1 day after average use.
Phone idle state is consuming 33% of battery. Here is the screenshot attached.
I would really appreciate your help to decrease phone idle state battery consumption.
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I believe is normal to see the phone idle so high if you are not using your phone that much. It just says how many time your phone has been on without doing anything, i see "phone idle" in every rom
cpuspy shows 36% deep sleep.
What is the significance of deep sleep? And what do all those frequencies tell me?
Thanks
andresrivas said:
both should install cpuspy to see if the phone is entering in deep-sleep...
it might be the bluesleep bug thah is discussed on development forum, you could try that
Click to expand...
Click to collapse
pbmax626 said:
What is the significance of deep sleep? And what do all those frequencies tell me?
Thanks
Click to expand...
Click to collapse
Deep sleep is the ideal state of the phone, in that mode your phone is almost turn off, the battery consumption is so low.
And the frequencies, higher means more battery consumption, so everybody try to keep the phone in low frequencies
pbmax626 said:
What is the significance of deep sleep? And what do all those frequencies tell me?
Thanks
Click to expand...
Click to collapse
Those are the speed steps of the processor, depending on the task, it sets itself to the lowest possible.
Deep sleep is a state of very low power, is like the processor almost shut itself down to save battery... thah is the most desirable state when the phone is idle as is the mos battery saver
Is there a way to stop this or is my phone defective?
Sent from my HTCEVOV4G using xda app-developers app
Is your phone rooted? If it is try lowering the cpu. Turn screen brightness down. See if that helps
Sent from my PG86100 using Tapatalk 2
By always, you mean all the time? Or just when doing a certain thing (playing game, watching video, etc)?
The phone should NEVER get hot. It will get warm after watching a video or playing a game for an extended amount of time, but never hot. Also, take off the back cover and see if the battery is hot. If it is the battery, remove it IMMEDIATELY, there is a chance it could explode.
AW: Phone always getting hot,
If you oc the phone to >=1,5 GHz/ 320 MHz you could also call it hot if you play 3d games ^^ "hot" is a little bit subjective, imo its warm not hot, but other might see it different...
But if its always hot, something is wrong with your phone....
If you have root you can check the CPU and battery temps with kernel tuner (if supported by kernel) or similar apps
Cpu should stay at <30° at idle and <50 while using it a long time; battery is throttling itself @ 36° afaik, but should stay under 33° if your not benchmarking and charging at the same time....
Hey guys, so the title says it all, my first charge from this device was just over 4 hours which is pretty good and it went all the way to nearly 6 hours screen on time and now its at 40% with stamina mode on, and screen on auto brightness with 2hours and 44 mins
So it might get to 3.5 hours before it dies which isnt great at all -.-
I use my phone pretty much the same every day, bit of Facebook twitter instagram etc
Do you guys have these problems? Battery life isn't bad, its just not consistent. Hopefully KitKat brings even better battery life ?
J
Sent from my C6833 using xda app-developers app
how you use the phone might not seen to differ to you, but may to the CPU/GPS/etc..
also 3/4g reception will have an affect on the battery life
JackHanAnLG said:
Hey guys, so the title says it all, my first charge from this device was just over 4 hours which is pretty good and it went all the way to nearly 6 hours screen on time and now its at 40% with stamina mode on, and screen on auto brightness with 2hours and 44 mins
So it might get to 3.5 hours before it dies which isnt great at all -.-
I use my phone pretty much the same every day, bit of Facebook twitter instagram etc
Do you guys have these problems? Battery life isn't bad, its just not consistent. Hopefully KitKat brings even better battery life ?
J
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
social media apps are really bad! Don't use them.. no seriously dont!! they constantly use CPU and connectivity hardware every minute, so your device probably isn't using deep sleeping during this time. I'm betting thats whats doing it