Hi,
I have recently installed GLaDOS kernel on my Nexus S, and activated the DEEP IDLE, however, under idle stats both DEEP IDLE (TOP=ON) and (TOP=OFF) are shown as 0ms (checked in NStools).
What could be causing this, how can I fix it?
Thanks.
Jujo12 said:
Hi,
I have recently installed GLaDOS kernel on my Nexus S, and activated the DEEP IDLE, however, under idle stats both DEEP IDLE (TOP=ON) and (TOP=OFF) are shown as 0ms (checked in NStools).
What could be causing this, how can I fix it?
Thanks.
Click to expand...
Click to collapse
Well, does your rom have deep idle activated?
Sent from a sandwich using my Nexus S
Well, I have turned it on in NStools
Jujo12 said:
Well, I have turned it on in NStools
Click to expand...
Click to collapse
Ok, in some roms you can turn it on but it don't work. What rom are you using?
MIUI 2.6.1
OK, we have progress. I don't know what I did, but now my Nexus enters DEEP IDLE, however only with TOP=ON. TOP=OFF is still at 0ms. What could be causing it?
Bluetooth fast switch. Needs a framework fix. May not work in miui.
Haha, I have been thinking about moving to CM9 for some time, and decided to install it. Deep idle works without any problems.
Thanks a lot
I'm searching for a stock Jellybean kernel with ezekeels deep idle mod and propably with the BLN mod.
Is out there something like that what I didnt find so far?
Kernel source hasn't even been released yet.
Ah, sorry I should habe learned that over the last werk :beer:.
And I saw with CPU Spy that deep idle seems to work with the Stock kernel.
Why the hell did I start this thread :banghead:
Deep sleep and deep idle are not the same.
I had the stock GB rom on my ATRIX 2 MB865. Flashed the ICS leak 18. On checking i noticed that my phone doesnt go to the deep sleep mode at all....using CPU Spy app. I had lost the mot_hotplug CPU governor. Changed the CPU governor to hotplug and got the deep sleep back. However, the battery tend to die out faster. After that i flashed the ICSupercharged v7 rom. I installed the 1125Mhz overclock and then the 1200Mhz overclock. My cpu wouldnt clock down below 750 Mhz on idle. However it would hit 1200 easily. Deep sleep too was lost. I have tried out all the governors including the hotplug, interactive and the smartass v2.. Still no deep sleep and still nothing less than 750mhz
Is there anything that I have missed out, cos i really loved the ICSupercharged ROM. But not having Deep sleep is a deal breaker.
Now i am back on the stock GB rom using RSD lite ..
spunxhoe said:
I had the stock GB rom on my ATRIX 2 MB865. Flashed the ICS leak 18. On checking i noticed that my phone doesnt go to the deep sleep mode at all....using CPU Spy app. I had lost the mot_hotplug CPU governor. Changed the CPU governor to hotplug and got the deep sleep back. However, the battery tend to die out faster. After that i flashed the ICSupercharged v7 rom. I installed the 1125Mhz overclock and then the 1200Mhz overclock. My cpu wouldnt clock down below 750 Mhz on idle. However it would hit 1200 easily. Deep sleep too was lost. I have tried out all the governors including the hotplug, interactive and the smartass v2.. Still no deep sleep and still nothing less than 750mhz
Is there anything that I have missed out, cos i really loved the ICSupercharged ROM. But not having Deep sleep is a deal breaker.
Now i am back on the stock GB rom using RSD lite ..
Click to expand...
Click to collapse
Check your build.prop using Root Explorer (best file manager, in my opinion) and see if this shows:
"ro.mot.deep.sleep.supported=true" There are other build.prop edits such as:
For Battery:
ro.ril.disable.power.collapse=0 - This setting puts your phone into a deeper sleep when on standby. This may improve battery life.
pm.sleep_mode=1 - This sets the phone to use power collapse when in standby.
0 - Power Collapse Suspend
1 - Power Collapse
2 - Apps Sleep
3 - Slow Clock and Wait for Interrupt (default)
4 - Wait for Interrupt
WiFi.supplicant_scan_interval=180 - This sets your WIFI to scan less frequently. This conserves battery life, however may come with side effects such as WIFI points not showing up as fast.
There's others, but you really need to get deep sleep back. Just search around for build.prop and deep sleep, you'll find a load of threads I'm sure...
Apex_Strider said:
Check your build.prop using Root Explorer (best file manager, in my opinion) and see if this shows:
"ro.mot.deep.sleep.supported=true" There are other build.prop edits such as:
For Battery:
ro.ril.disable.power.collapse=0 - This setting puts your phone into a deeper sleep when on standby. This may improve battery life.
pm.sleep_mode=1 - This sets the phone to use power collapse when in standby.
0 - Power Collapse Suspend
1 - Power Collapse
2 - Apps Sleep
3 - Slow Clock and Wait for Interrupt (default)
4 - Wait for Interrupt
WiFi.supplicant_scan_interval=180 - This sets your WIFI to scan less frequently. This conserves battery life, however may come with side effects such as WIFI points not showing up as fast.
There's others, but you really need to get deep sleep back. Just search around for build.prop and deep sleep, you'll find a load of threads I'm sure...
Click to expand...
Click to collapse
Good Info. But SCV7 has it exactly like that. The problem is that the media server on ICS causes wake locks. I don't know any fix for this my self. Apex might tho.
Sent from my locked MB865 on Ice Cream Sandwich.
DemosZevasa said:
Good Info. But SCV7 has it exactly like that. The problem is that the media server on ICS causes wake locks. I don't know any fix for this my self. Apex might tho.
Sent from my locked MB865 on Ice Cream Sandwich.
Click to expand...
Click to collapse
Which media server are you talking about? My apologies, I'm not familiar with what SCv7 offers, perhaps I should flash it and get on par, eh? Anyhow, I can try and help you guys track down this issue, just let me get on the ROM and see what I can come I with.
We can look at the wake locks cause by the media server, not sure why or how this would be causing such grief, but I'm also not saying it's not a plausible excuse. l will report back after my flash...
Apex_Strider said:
Which media server are you talking about? My apologies, I'm not familiar with what SCv7 offers, perhaps I should flash it and get on par, eh? Anyhow, I can try and help you guys track down this issue, just let me get on the ROM and see what I can come I with.
We can look at the wake locks cause by the media server, not sure why or how this would be causing such grief, but I'm also not saying it's not a plausible excuse. l will report back after my flash...
Click to expand...
Click to collapse
Sorry if Tapatalk doesn't show but here.
Sent from my locked MB865 on Ice Cream Sandwich.
It doesn't show wakelock cause I was hooked up to pc. But that is what causes it.
Sent from my locked MB865 on Ice Cream Sandwich.
DemosZevasa said:
It doesn't show wakelock cause I was hooked up to pc. But that is what causes it.
Sent from my locked MB865 on Ice Cream Sandwich.
Click to expand...
Click to collapse
Wake locks are always traceable, some are a little more tricky to hunt down, but if something is causing a wake lock, there is a way to determine what's causing it, where it stems from, and how to alleviate it...
Apex_Strider said:
Wake locks are always traceable, some are a little more tricky to hunt down, but if something is causing a wake lock, there is a way to determine what's causing it, where it stems from, and how to alleviate it...
Click to expand...
Click to collapse
When I'm using the phone normally. It says that is causing most of battery drain and it says *wakelock * next to it. Normally my phone goes hours on standby cause of school.
Sent from my locked MB865 on Ice Cream Sandwich.
Whoohoo
Thank you apex strider for pointing me in the direction of the build.prop tweaks.. While i am still on the stock rooted GB (i might flash back to the SCv7 or the ICS over the weekend), the build.prop tweaks really helped me in getting the battery usage under check. 10% battery drain over 10 hours aint too bad afterall with some amount of wifi and calls..(used to lose about 20% over the 6hours sleep)..I ecstatic!!
http://forum.xda-developers.com/showthread.php?t=1697040
Now to check out all these tweaks on the ICS.. Will get back to you over the weekend..
Thanks again..
Okay, so my jump from ICS to SCv7 has been put on hold, due to some unmentioned experimentation. I haven't forgotten, just have forbearance with me...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Apex_Strider said:
Okay, so my jump from ICS to SCv7 has been put on hold, due to some unmentioned experimentation. I haven't forgotten, just have forbearance with me...
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Click to expand...
Click to collapse
"experimentation" huh Apex?
Fall of Enosis said:
"experimentation" huh Apex?
Click to expand...
Click to collapse
Yeah... (wink, wink)
Sent from my SAMSUNG-SGH-I747 Anti-Motorola Ballistic Missile
Hey guys,
I do have deep sleep and I'm on SCV7:
Hi guys! I have a problem with SetCPU on CM10 nightly 0904
I created a profile Screen OFF with freq min/max 100 governor ondemand and scheduler cfq (i have matr1x kernel v23)
When i want to unlock screen, nothing appens. The screen doesn't unlock
I have to remove battery and then the phone start...why?
Is SetCPU is still incompatible with JB??
sorry for my bad english
sossio18 said:
Hi guys! I have a problem with SetCPU on CM10 nightly 0904
I created a profile Screen OFF with freq min/max 100 governor ondemand and scheduler cfq (i have matr1x kernel v23)
When i want to unlock screen, nothing appens. The screen doesn't unlock
I have to remove battery and then the phone start...why?
Is SetCPU is still incompatible with JB??
sorry for my bad english
Click to expand...
Click to collapse
Using screen off profile is a very bad idea. Setting the maximum frequency to 100MHz is an even worse idea. Don't do that. Stop using SetCPU.
polobunny said:
Using screen off profile is a very bad idea. Setting the maximum frequency to 100MHz is an even worse idea. Don't do that. Stop using SetCPU.
Click to expand...
Click to collapse
When i was on ICS itbwork very well and i save a lot of battery
Inviato da un terminale non identificato
sossio18 said:
When i was on ICS itbwork very well and i save a lot of battery
Inviato da un terminale non identificato
Click to expand...
Click to collapse
On a properly configured system you do not need a screen off profile. What you need to make sure is that your phone is actually idle with the screen off. You can use software such as BetterBatteryStats for this.
Besides, Jelly Bean has some little issues with current programs used to set minimum frequencies. It will often default to 200MHz.
polobunny said:
On a properly configured system you do not need a screen off profile. What you need to make sure is that your phone is actually idle with the screen off. You can use software such as BetterBatteryStats for this.
Besides, Jelly Bean has some little issues with current programs used to set minimum frequencies. It will often default to 200MHz.
Click to expand...
Click to collapse
The phone goes in deep sleep, not in deep idle. Is the same?
If it isn't the same, how i active deep idle? I have matr1x kernel v23
Inviato da un terminale non identificato
JB CPU
Try Paranoid Crespo JB
I've been trying to check cpu states on my BBS and CPU Spy. But BBS would return with nothing and CPU would say no states found?
Why is this?
How can I resolve this?
Once I turn on SetCPU though and go back to BBS and CPU Spy, I can get my states.
Is there something wrong with my path/directory?
If you are talking about cpu times you can check that with setcpu too.
x714x said:
If you are talking about cpu times you can check that with setcpu too.
Click to expand...
Click to collapse
hey thanks for the reply.
I'm not so much concerned with the data, since i can check it with BBS as well.
But im concerned with the issue of not being able to read any cpu states until setcpu is used.......
Does anyone know what causes this?