Related
Just one simple question. When phone is in deep sleep, the cpu's running speed is the min frequency I choose from the cpu settings or a default lower one?
I use smart ass 2 with min at 768 and max at 1516 . So in deep sleep my phone is running at 768?
Thanks in advance...
Sent from my Huawei u8800 using XDA Premium App
spirosbond said:
Just one simple question. When phone is in deep sleep, the cpu's running speed is the min frequency I choose from the cpu settings or a default lower one?
I use smart ass 2 with min at 768 and max at 1516 . So in deep sleep my phone is running at 768?
Thanks in advance...
Sent from my Huawei u8800 using XDA Premium App
Click to expand...
Click to collapse
Not 100% sure but freq is minimum as it can be. And if cpu is not used no metter is freq 10000MHZ or 300Mhz it uses almost the same power. But when cpu is in use freq is important to power usage. Freq management is good not because it lowers freq but because it lets use lower freq on things that is not require hi freq. so it saves LITTLE LITTLE BIT of power. In idle mode (deep sleep) no meter what freq is.
But i still don't understand the need of governor. It's good only in cases where you overclock cpu but if don't - i don't see why it should be used.
PS Use app called CPU SPY it shows on what freq your cpu is being used and how much of the time.
Thanks! I use CPU SPY and it says tha about 60% or more is in deep sleep, 15%-25% is at 768 and the rest higher, which seems to be a good thing. But my phone still lasts for about 10-15 hours with normal use.
So i thought that maybe my min 768 frequency drain a lot of battery.
To clear things up a bit I use latest oxigen rom+latest franco kernel+zram+Juwe ram script...
Actually deep-sleep state is a special state supported by your phone MCU. In this state, a lot of functionality (therefore a lot of logical gates) are disabled thus MCU consumes very low power compared to normal functioning states. The thing about a CPU/MCU is when it is running even if there are no work to do no code to process, it has to run some command. While idle it must run NOOP (no-operand / no operation) command or do something equally unnecessary like counting a not required number. But in deep sleep mode, MCU actually stops working except for core functions to keep your phone going on.
Think about it this way, in a normal working state, CPUs most basic functionality is to read a command from memory, execute it and proceed to the next command to continue. Thus, in an operating system or a single purpose embedded software, CPU/MCU has to execute a "do nothing" command when you have no job to give it. But even a "do nothing" command need all of the MCU/CPU resources to be kept readily available. If you're sure that you have absolutely no job for your MCU/CPU to do, what you can do is to tell it to go and sleep fr a while until you wake it up again. In sleep, MCU/CPU can shut down a lot of its support systems like math processing, external memory access, graphics related functions (if any), even IO outputs. Depending on your CPU/MCU, this means until an interrupt occurs or a special sub system wakes it up, most of the sub-systems within your MCU/CPU thus may be millions of transistors will not be working so, your CPU/MCU will not consume as much power.
In layman's terms, deep-sleep state is a special state that shut down most of your MCU in your phone, thus while crippling it by removing its ability to function, making sure that it doesn't consumes much power. So OS (Android) (with the help of some additional hardware) controls when your MCU will sleep and under what circumstances it will wake. So it shuts down the engine -so to speak- when you're not using it for long terms and saving fuel rather than leaving your car on idle.
Hope this helps..
Thanks t_d_z. That is also how I imagined things...
But what is wrong with my battery which today, for example, went 33% down in 5 hours with 68% (from cpu spy) in deep sleep, without wi-fi on.
As i said above, I use latest oxigen rom+latest franco kernel+zram+Juwe ram script+smarass2 governor...
I also calibrated my battery by wiping battery stats, like i read in a post.
I have read in an other forum that if you use smartass (I use smartass2) or ondemand (I think...) governors, the governor is learning your habits and after a week you see the difference. Is that true?
Finally, can you guys who have "good" battery life, post your settings? (By settings I mean: rom, kernel, governor with cpu parameters, how you use the phone and everything else you think is important).
Thanks again...
I get about two days of battery life. I use Oxygen without any modifications. CPU is min. 245 (or something like that with 200, I dunno now) and max. is 800. Wifi is always on when I am home.
Try installing Oxygen-r1 and use it with a full battery, do not change anything and do not install too many apps. There will be apps that just won't stop running (like BBC or CNN app), I do not install those. Then you will see how long your battery lasts. If you just write some messages throughout the day and call somebody for 1-3 hours you should get about 2 days.
Then install your apps and test it again - maybe your apps are the problem.
spirosbond said:
Thanks t_d_z. That is also how I imagined things...
But what is wrong with my battery which today, for example, went 33% down in 5 hours with 68% (from cpu spy) in deep sleep, without wi-fi on.
As i said above, I use latest oxigen rom+latest franco kernel+zram+Juwe ram script+smarass2 governor...
I also calibrated my battery by wiping battery stats, like i read in a post.
I have read in an other forum that if you use smartass (I use smartass2) or ondemand (I think...) governors, the governor is learning your habits and after a week you see the difference. Is that true?
Finally, can you guys who have "good" battery life, post your settings? (By settings I mean: rom, kernel, governor with cpu parameters, how you use the phone and everything else you think is important).
Thanks again...
Click to expand...
Click to collapse
Look not at cpu spy but in battery usage to find out what drains your battery. And i can tell All roms are kinda lame in terms of battery, except CM7. In deep sleep it takes about 7% of battery in 10hours. I tried all roms but non of them was so efficient. But latest franco kernel (which i think even more improves cm7 rom) does not support cm7 right now, so i've attached older version if you would like to test cm7+franco kernel.
With normal usage of 50 sms and 30minutes of calls and sometimes wi-fi to download few apps and 20minutes on easy games my battery lats about 18hours. Whan only sms it lasts 30hours. depends how long lcd is on
Well, I'm not an expert on smart phone OSes but I'm an expert on embedded systems and micro controllers. If the designers are not really stupid (which I'm sure they are not) all the peripherals gets suspended when the main CPU goes to deep sleep mode. So, it is almost impossible for the phone to consume much power in deep sleep state. Most likely your phone consumes that power the rest of the time when it is not in sleep mode. I agree with Tommixoft, you should use battery usage info rather than CPU spy to find what drains your battery. Also, here is a quick check list about what consumes power :
1. Screen, especially when it is brightly lit
2. GSM network (Even when you're not talking to phone, GPRS/Edge/3G network communications drains almost as much power)
3. Wireless network
4. GPS
As an additional note, if your phone is not going to sleep mode regularly try to uninstall applications that have "prevent phone from sleeping" security setting.
Hope this helps, and of course there are a lot of more experienced people in the forum that knows about the details of the kernel so they might provide additional info.
Regards,
---------- Post added at 05:15 PM ---------- Previous post was at 05:10 PM ----------
Oh I forgot to tell the MOST important thing, 768MHz is way too high a value to set as minimal frequency. Try to set it 245. I use 122 MHz and it work pretty well. Don't forget, when you need the CPU power, the governor will provide it for you.
Hi guys.
Edit : I am running fully stock, non-rooted and OTA updated Kit Kat 4.4.2
I noticed that a high Android OS usage and wake lock (in my case) comes from the cpu Governor locking all cores to 2.0-2.3 GHz despite nothing happening on the phone. I checked this using the system monitor tool. I have screenshots added.
The problem is that I can't see what apps are causing the governor to never make the other 3 cores go offline. When I check "Top apps" everything is at 0% cpu usage. What is causing the cores to never go offline and stay locked at 2.0GHz+ and drain battery?? It is only when this happens that I get high Android OS usage. A reboot fixes it, but it happens randomly. When I feel that my battery is draining badly, I check my cpu in system monitor and see all cores online even when idle. I just don't get it.
I'm thinking it may have something to do with dashclock/BBS or some combination, as every time this happens, the BBS add on in dashclock shows 0% drain (so it seems broken when it happens).
Please help!
Sent from my SM-N9005 using xda app-developers app
EddieN said:
I noticed that a high Android OS usage and wake lock (in my case) comes from the cpu Governor locking all cores to 2.0-2.3 GHz despite nothing happening on the phone. I checked this using the system monitor tool. I have screenshots added.
Click to expand...
Click to collapse
Hello. Have you found a solution to this problem? I thing I have something silmilar, although in my case the IDLE cores stay at 300MHz and they do not enter offline as they should. I have a rooted phone with original 4.4.2 firmware and Xposed framework installed, but it doesn't seem to be a problem (the cores get stuck after some time).
this is caused by samsungs dvfs (google it for more information). just download and enable the dvfs disabler module from xposed framework
I have xposed enabled, dvfs disabler its enabled.
My minimum 300mhz became 1.19-2ghz, so cpu is stuck.. Onlu one core usually. I find out one app that does that, camera. I enter camera app then exit, cpu minimum core is 1.95ghz and stay there always, till restart.
What rom do you have? I'm on xxuend3
And on what governor? I'm on interactive.
And usually if you move cpu minimum /maximum sliders, cpu became unstuck.
So you have few cores stuck, move sliders up and down and stuck became unstuck
Regarding the top apps not showing, I've found the usage reporting on the device to be entirely broken.
I've had it report, in 6 seperate apps, that Android was using 25%... whilst I'd been playing Oh Edo! Towns for 6 hours straight. It listed that game, which is quite heavy, as 2%.
No way in hell that's accurate.
25% in deep sleep, yes. There's nothing else running, so 25% of 1% per hour for idle processes makes sense. But not during gaming.
Sent from my SM-N9005 using Tapatalk 2
Hello! About 1 day works well for me on the phone, then the middle two seeds get stuck 1,9MHz. Only a restart helps ...
Kernel bugs??
Im on skyhigh kernel. On this one cpu wont stuck.
I found that Camera app makes cpu stuck at maximum clock, like 2.2 or more. The fix, restart phone or use cpu sliders and move them a bit, then cpu became unstuck. Use android tuner, faux, etc for moving cpu clock sliding
Note 3 rooted knox 1, my last Samsuck crap. I want freedom. Stay away from Samsuck!
I found an small annoyance. When i wake up the phone i see an lag... Sometimes its about 5sec,sometimes lower or more. How can i fix this? Tried to raise cpu clock on touch... The same
Note 3 rooted knox 1, my last Samsuck crap. I want freedom. Stay away from Samsuck!
So I have been noticing that i have a high kernel usage on my D800, it's over 7%, my question is, what processes should be there and what shouldn't be on?
I really have no clue, but it appears that there are too many processes working, at least more than I saw on my previous G2
I'm having some issues with my phone being awake when it is charging. I've checked the most obvious causes such as daydream, and the keep awake setting, but neither were active.
I'm not sure what actually keeps it awake as battery stats end up being erased at 100%. I have Wakelock Detector installed but that doesn't give me any conclusive evidence either since again, the stats are gone once the phone is fully charged. This is mostly an inconvenience as after disconnecting the charger, the battery use is about normal and I can control the wakelocks through Greenify, Amplify and the Privacy Guard's keep awake function.
Has anyone else experienced/solved this issue before and what did you do?
My current setup is:
Android 6.0.1
Resurrection Remix ROM
Nevermore Kernel
I have noticed that most ROMs above 4.4 seem to have an adverse effect on battery life on my S4 and my Galaxy Tab 2. 6.0 seems to be giving me the same standby time of 4.4 however on my tab, so I was hoping that it'd do the same for my S4 as I want to move away from using the Davlik runtime.
Always awake on charging is normal habit, you don't need to worry such thing.
Sent from my HUAWEI SCL-U31 using XDA Labs
Not for Samsung it's not .....at least not on the 4 Samsung devices I own (the AMOLED screens on them would get horrendous burn in if the screen remained on for long periods of time).
There is an option in
Settings>>developer options
that will prevent the screen from sleeping while the charger is plugged in, but the default setting for this option is disabled. Just double check to see if it has been enabled......
It wasn't normal in 4.4 nor 5.1, so either this was changed in 6.0 or my kernel is forcing this behavior, I may try switching kernels. As I mentioned previously, the dev options don't have anything enabled that would cause it to keep awake.
so guys after a long search in the forums i didnt find an answer my cpu usage is flactuating cpu-z shows around 60% usage while im in the cpu-z window
but cpu monitor shows 3% but flactuating alot when i update apps or download them it goes to about 80-90% usage watchdog says its the "base system" process that goes to +-70% cpu usage i tried factory reset didnt help
i cant add images because im a new user