Im getting the dreaded SOD when i enable deep idle and was wondering if anyone else experiences this.
Kernel: 3.0.35 Semaphore
Rom: Slim 4.2.1 RC 1
Band: KB5
Thanks,
Chris
Update,
I upgraded the kernel to 2.9.8sv but it still does not want to wake up from deep sleep when I enable deep idle.
Mines been toggled on for months including power down Bluetooth option and no sod. Some phones can't handle it if updating to an different android os. Why not disable it and have a usable phone?
Sent from my Vibrator running 4.2.1 Neobuddy Pass%$n Alpha 14.1 RC
Was hoping it might just be a setting I was missing that would cause the sod. Its disabled now, too bad though would have been useful at work, love slim ROM otherwise.
Related
Ive been using Glitch V12 (20110720-HL) for a while now with CM7. I stuck with this version because BLN (without app) and sensors work. I tried going to the newer releases but when using GrooveIP, I temporarily lose sound when the screen goes off while im in a call and doesnt come back until I turn the screen back on. Is this the screen state scaling? If so, any recommendations of what governor to use to that I wont get cut off but is also good on battery?
Thanks
If it is something that happens a lot, try either ondemand or disabling screenstate scaling completely.
Sent from my MIUI SCH-i500
Thanks for the quick response. Wasnt expecting to have an answer 'til I woke up. I will reflash back to the latest CM7 and Glitch tomorrow and report back.
Well, I flashed the latest Glitch kernel (9-23) along with CM7 (nightly 59) and its not doing it at all. When it did it before was on kernel 9-06. Did that build have a different default screen off governor or maybe it had something to do with the proximity sensors not working and the auto off screen kicking in after about 30 seconds, which is when the sound would stop before?
Hi folks, I've been doing a bit of scouting and haven't been able to find a solution as of yet so hoping somebody here can help me. I upgraded to ICS a couple of days ago from 2.3 and since then my battery has been going a bit odd.
My phone wouldn't come out of sleep and i kept having to do battery pulls to bring it back to life. I figured this was probably to do with my SetCPU setting being too low (200-500MHz for screen off) so i disabled the profiles and it still was happening. Have deleted SetCPU altogether and it has improved a tad bit. But now my phone does occasionally go into sleep mode and won't wake until i do a battery pull. But when i bring it back to life my battery is 15-30% lower than from before I did the pull.
I'm running 4.0.3
Sensation Rom 3.5
Siyah Kernal v3.3.2
PDA version XWLPG
Baseband DXLP9
I've attached two screenshots to show properly what I mean. Scrolling through ExTweaks shows me that siyah kernel itself also can change clock speed but there's too many options there for me to know safely what I'm doing. I've done battery recalibration twice with no luck so far.
Thanks in advance for any help!
flash stock rom and root and reflash sensation rom by doing a full wipe
do a full wipe, and reflash the rom.
Then see if you still have problems.
Then install your apps again, if you then ahve problems, you know your apps are causing it
You can also install betterbatterystats (free on xda), that app will tell you which app is causing wakelocks
Hello
I appreciate both the CM and AOKP roms built on 4.1.2 are no longer being supported but is anyone running these roms as daily drivers and can confirm their stability?
Over the last month I have tried both roms and found them great roms with no audio (speaker) issues which keeps me from using the 4.2 builds of these roms.
Unfortunately I am finding my phone occasionally will not turn back on when the phone has gone into sleep. When this happens the capacitive buttons at the bottom are illuminated in red but the phone will not turn on at all. I am forced to hold down the power button so that the phone reboots.
Just wondering if anyone else has experienced this?
For both CM and AOKP I just use the kernel within the rom zip. Perhaps I should use the latest Maxwen kernel?
So this is a bit of a pot shot but the I9300 is the 3rd device I have owned with the slow wake issue. On my previous device (huawei g300) i used this kernel mod after being told that vsync was partly to blame.
github.com/KonstaT/zte-kernel-msm7x27/commit/368448b773f6917c213f37f7dd1a882ba588b120
It worked a treat and was soon inclueded by our resident CM ROM dev at the time. My questions are:
Could we benefit from this or something similar on the i9300? Has the cause of the slow wake been identified?
Thanks
In Ultima Rom there is an option to fix this wake delay
And it is mentioned there that I9300 goes in deep sleep mode and thus a delay occurs in order to wake the cpu
when the Fix is applied then the delay is gone. I have personally not checked the fix because i am ok with it, but i can try and let you know but too lazy for that
Also so much on my plate going on.. but this i just shared with you is what i read.
Hello XDA,
I've come across a really annoying issue for me.
I've downloaded android revolution 40.0 and was advised to run boeffla kernel with it as the stock kernel drained the battery too much.
I installed boeffla kernel and it was working fine, all the tweaks worked!
Now there's only 1 issue that needs to be fixed with this kernel/rom. The home button is very unresponsive when the phone is in sleep/standby mode. Things I've tried:
Using different governors
flashing boeffla kernel obviously
changing CPU speeds
Different options within the boeffla app.
Does anyone have any idea why the button reacts so slow as it does? Is it rom related or kernel related?
Any advice on a possible fix would be very welcome.
Don't be shy :silly:
Stefan0vic said:
Hello XDA,
I've come across a really annoying issue for me.
I've downloaded android revolution 40.0 and was advised to run boeffla kernel with it as the stock kernel drained the battery too much.
I installed boeffla kernel and it was working fine, all the tweaks worked!
Now there's only 1 issue that needs to be fixed with this kernel/rom. The home button is very unresponsive when the phone is in sleep/standby mode. Things I've tried:
Using different governors
flashing boeffla kernel obviously
changing CPU speeds
Different options within the boeffla app.
Does anyone have any idea why the button reacts so slow as it does? Is it rom related or kernel related?
Any advice on a possible fix would be very welcome.
Click to expand...
Click to collapse
Define ur term 'slow' how slow is it. 5 seconds?