Bsod with Idle or DeepIdle enabled - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi all,
I'm currently running AOKP milestones 6 with the Devil Kernel, and everytime I activate the DeepIdle option with NSTools or with the Devil Kernel manager app I get Bsods.
It's not specific to AOKP rom because I had the same problem when I was running CyanogenMod 7. I tried to use Glitch Kernel or Semaphore Kernel but it's everytime the same thing : I get one Bsod after a few hours, and after they come every 10min or so. If I pull off the battery or keep pressing the power button the phone reboots normally but until I deactivate the Idle option I have always this same problem.
I tried using smartass V2 governor or modifying the voltages, doing fresh installs but I can't solve this problem. I also used the BT killer script to see if it changes anything but it didn't solve my problem.
Could it be my phone or am I doing something wrong?

I'd say its probably just the DeepIdle. I do remember reading that DeepIdle support is kinda... weird. In my own experience I've had trouble getting it to work. Had SoD's only a couple of times but actual DeepIdle state won't be used much. It has improved a lot from the Cyanogenmod7 days though.
Is the phone very hot on such an event?
I'd say just don't use DeepIdle if you've had such a long history of problems with it.

I put devil Idle option permanent and I didn't have Sods since this morning, maybe you're right and the Deep idle doesn't work. It's quite sad because it seemed awesome on the paper
And about your question the phone doesn't get hot when this happens, it just stop responding but I have no memories that this happened when I was using the phone only when the screen was off. I'm not sure if it's important but it happened when the phone wasn't used for some minutes or if quickly press power button multiple times.
How did you managed to get it working?

Related

Recent sleep deaths.

Hello xda!
Lately my phone has been acting real crazy. I've been on Cognition rom for about a month and I never experienced any issue. However, after flashing SpeedMod k12t, my phone kept freezing while on sleep after 1-2 hours of use. I decided to reflash firebird 2 to make sure it wasn't the new kernel, but my phone recently froze in screen off. I am now sure this has nothing to do with a specific kernel. I have been trying to figure out what's wrong with my phone. I am pretty sure it has nothing to do with my modem either, since I have been using jk4 for about a week or three and this issue never came up until now.
All I'm really thinking of would be my setcpu settings. I recently started to use profiles with the following settings :
Screen off : 200-200 performance (now 400)
Charging : 1000
Battery < 101% : 800 - 1000 conservative
Battery < 39% : 400 - 800
I am thinking the screen off settings are causing all of this trouble. I only started using these a day or two before all of this started. Back then I was testing out a couple different kernel (suckerpunch, gb's kernel, firebird, speedmod). I had a rather poor uptime with suckerpunch because it took a while for me to find the correct settings, and when I did, I remember getting a sleep death that I blamed on the kernel because of the history of charge death it had back then.
Also, my original kernel was firebird and my phone was quite stable during the 3 weeks I've used it. I'm leaving the possibility of a bad kernel away because of this.
So here's my question, xda : What's up with my phone? Is reflashing back to stock and back to Cognition the only possible fix for this? Could me flashing kernels without disabling voodoo be the cause of all of this? Could disabling voodoo and reflashing the kernel fix this? Can set cpu be the cause of all of my trouble (i disabled it for now).
Thanks,
I have the same exact problem and it drives me insane. I have no solution for it except if your last 4 IMEI numbers (under your battery) are below 6000. Mine is 8355 so i dont know.
The last four numbers under my battery are 6, 5, 5, and 9. 6559. This only started a day or two ago. I've only had this phone for a month. So far the problem seems gone, but I've noticed my battery went from 67% to 80 after rebooting my phone to check the numbers under my battery. I recently wiped my battery stats though.
I've only had my phone for about a month too, so i don't know any more than you do. The only thing different for me is the shutdowns were already happening, and the the ROM I flashed just increased it.
Yeah, my phone also seems to freeze when alseep but only if its charging. Sometimes if i disconnect it, it will freeze or if i get a phone call while its charging.
My Captivate had sleep death (randomly) and charge death on some ROMs. After flashing several combinations of ROM/kernel/modem, it seems ok now. I think I will keep on finding a better combination.
SetCPU has some issue with OC/UV kernel on my Captivate, so if you have the same problem try to disable SetCPU first and see if the problem goes away.

[Q] Sleep/Charge of Death

I been wondering if the phone never had sleep/charge of death before can a kernel and/or ROM be the culprit to it? I been trying to look more into it and haven't found a definite answer to it so I ask you guys what is causing it. I've tried different kernels and ROMs and some do it other don't is there anyway to just know? Or a good way to narrow it down?
I was able to track mine down to a kernel that supported Overclocking. Once I switched to a ROM that had a kernel that wasn't OC supported (older version of same ROM) my charging death went away. I think it has to do with the OC settings, the idle clock speed is too slow, but no matter what settings I used I got sleeping death every other night until I swapped for the other version.
Sent from my Captivate running GR-12
Only time I have encountered the Sleep/Charge of death was when I was OCing the phone and UVing it also. Having too much of a variance in the UV was my problem. Wants I started to UV the same amount across the board or close to it my problems were solved. For instance the most I UV is 75 and the least is 25. if you had a gap like 150 to 0 that could be what is causing your problem. At least that is what I noticed for myself. Now I am perfectly fine for over a month.
The phone boots up to 1/2 way through the kernel when charging in off mode... IBL, PBL, SBL, Params, Kernel... If it hangs, then it's likely hung at a custom kernel.
If the ROM craps out it soft reboots and/or goes into a boot loop. I don't think that a ROM can cause your phone to randomly shut down.

[Q] Horrible Battery Life on my Captivate

hey guys, having troubles with my cappy here. running CyanogenMod RC1 rom. i needed to use my GPS this morning, used it for navigation for about 15 minutes and turned it off. from 7:30 AM this morning when i woke up and unplugged my phone, it's already down to 7% battery left. when i turned off my GPS it was at 56%, that was 9:30ish. so from 9:30 - 12:15ish, it's down from 56% to 7%
that is without any apps running, wallpaper disable, it's been sitting in my pocket sleeping
is there a way i can undervolt it? i know you need a compatible kernel, is there a compatible kernel for CM7 RC1 than i can load so i can UV?
any help appreciated, thanks
Bad battery is one of the known bugs in CM/MIUI. Right now, it's a fact of life every CM/MIUI user deals with.
hm that's a bummer, i'm loving CM7, but now i've got to resort the old fashioned way to find my way back, as my phone is now dead, rofl
gonna have to stop and ask for directions lol
so, is there a kernel i could load that would allow me to undervolt my cappy with CM7?
You know, nothing about CM7 is a batt hog IMO. Only weird thing I can find is that my voice calls use about 27 percent of my battery per hour. I've tried flashing different modems and all, but it could also be that I have a year old battery.
I've been reading on this as well and followed this thread.
http://forum.xda-developers.com/showthread.php?t=806211
Was a great help doing the jump charge as I was flashing many ROM/kernels. Hope it helps you too.
What's eating up the battery? If its the OS at like 40% I'd do the following
1. Shutoff GPS
2. Wifi sleep policy to when screen turns off
3. Determine which apps are keeping the phone awake(use spare parts)
4. I've been using jk4 modem, as far as I know because the developers don't have the Samsung source code there is a problem with the modem that will keep the phone waking
5. Run the battery down to 20%, plug phone in, power off, because of the source code it'll reboot immediately and you'll have around 46%, let charge to 100% unplug, that always eliminates my wake problem so I repeat the process every time my phone stays awake and let it chrage overnight afterwards and I've been getting between 1 and 2% battery drain/hour
Sent from my I897 using XDA App
Just manually force close battery eating apps. In manage apps. ( not running apps) cm7 doesn't have the closed sauce needed to improve its batt Life just yet. Only use data or wifi when needed. GPS when needed. Turn off auto sync. Turn off location. Anything that runs constant that you don't need. You can get an app autostarts, people have suggested it working for them.
For kernels there are three awesome ones: escapist, tkglitch or platypus neo10
Please read through their OP before playing with them. good luck
Sent from SGS Captivate CM7 or MIUI with Escapist orTKGlitch using XDA premium app.

Sleep of Death - Workarounds

I’m creating this thread to help anyone who’s been affected with SOD (Sleep of Death). Here’s a brief history of what I’ve tried so far:
- I was running stock 2.2 for about a year, had lag, choppiness, etc.. but never a SOD
- Flashed CM7.1 2 weeks ago (stock kernel), phone is not amazingly fast but experiencing SODs every few days.
- Created a Tasker profile to wake the phone every 1 hour, (wait 5 seconds command), no SOD for a week
- This morning, got a SOD again.. missed my alarm and was late for work 
- All SODs happen at night while charging.
- Today I downloaded ‘Wake my Android Pro’, supposedly it send a wakelock every 29 minutes and prevents the phone from entering deep sleep.
My next step if this fails and I get another SOD:
- Set CPU min clock to 350 (read that this doesn't help but will try anyway)
- Activate SoftLocker to prevent the phone from ever going to sleep, this is the last resort since it will affect my battery life (wish there was a Tasker plugin to toggle the settings so I can enable it only when charging)
Does anyone know how long after turning off the screen does the phone go into deep sleep (versus regular sleep)?
gabster21 said:
I’m creating this thread to help anyone who’s been affected with SOD (Sleep of Death). Here’s a brief history of what I’ve tried so far:
- I was running stock 2.2 for about a year, had lag, choppiness, etc.. but never a SOD
- Flashed CM7.1 2 weeks ago (stock kernel), phone is not amazingly fast but experiencing SODs every few days.
- Created a Tasker profile to wake the phone every 1 hour, (wait 5 seconds command), no SOD for a week
- This morning, got a SOD again.. missed my alarm and was late for work 
- All SODs happen at night while charging.
- Today I downloaded ‘Wake my Android Pro’, supposedly it send a wakelock every 29 minutes and prevents the phone from entering deep sleep.
My next step if this fails and I get another SOD:
- Set CPU min clock to 350 (read that this doesn't help but will try anyway)
- Activate SoftLocker to prevent the phone from ever going to sleep, this is the last resort since it will affect my battery life (wish there was a Tasker plugin to toggle the settings so I can enable it only when charging)
Does anyone know how long after turning off the screen does the phone go into deep sleep (versus regular sleep)?
Click to expand...
Click to collapse
I'm also using CM7 (nightly #146) with neo kernel..I only have had SOD once (while using stock kernel IIRC). Now I'm booting every evening before going to bed and haven't noticed any problems (knocking the wood..).
Btw, as you came from froyo did you flash GB before going to CM7? Or at least GB bootloaders prior flashing?
Can't really say any solution to your problems since these sods are quite hard to catch..logcat, dmesg, etc are our friends with these kinds of problems
Sent from my GT-I9000 using xda premium
Kurre said:
I'm also using CM7 (nightly #146) with neo kernel..I only have had SOD once (while using stock kernel IIRC). Now I'm booting every evening before going to bed and haven't noticed any problems (knocking the wood..).
Btw, as you came from froyo did you flash GB before going to CM7? Or at least GB bootloaders prior flashing?
Can't really say any solution to your problems since these sods are quite hard to catch..logcat, dmesg, etc are our friends with these kinds of problems
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
No, I didn't flash GB, I installed CWM bootloader and flashed CM7 from recovery (had to find a workaround to get past the e3 protection).
So far with "Wake my Android Pro" I see the screen go on and off quickly (about 1/2 a second) every 29 minutes.. too early to tell if this is helping with SODs, I'll report back regularly to update the results
Woke up today to my alarm, wohoo! Phone doesn't seem to go to sleep and battery life is fine.
charging on a PC.
Hello
Thank you for the informative thread.
I have a Galaxy S i9000 running 2.3.6, XXJW4 and CF-root, and find it frustrating not to be able to fully trust my phone to respond whenever needed, be it listening to Internet radio, using sat nav, getting Facebook notifications (yes I got them back after reinstalling Facebook and clearing Dalvik cache but I should talk about that in another thread) and of course making and receiving calls now and then.
I was wondering whether the fact that I have been hooking it up to a PC to charge it through the day (and of course plug and unplug it a few times during the day) actually made the situation worse.
So far I have been getting an SOD every two days. The 'serious' SOD would come on after a 'less serious' SOD had already happened ie the phone went into coma and then came out of it and lasted for 6 to 8 hours longer before actually falling into the SOD coma.
I stopped using the PC as a charger (using a cheapo replacement micro USB charger) and so far 3 days have gone by without a hint of an SOD. Fingers crossed. Will keep investigating.
Cheers

Huge battery drain by rild/phone

Hello All,
My Problem is a high battery drain, not caused by baseband_xmm_power wakelock, but by the processes "Phone", "Messaging Storage" and "SIM Toolkit". My device gets very hot although I do not even use it and the CPU runs constantly at 475 MHz. I got this issues on every custom ROM / Kernel combination. This Problem appears at random time intervals. Sometimes after 2 days, sometimes 5 times a day and sometimes it disappears after rebooting.
I also have tried to freeze that 3 processes with greenify, but no success
Right now I am running SlimBeam 7.8 with iodak Kernel (because with this combination I dont get these baseband wakelocks)
Is there anybody with the same issue or with some tips for me?
I have found the solution, switch off your phone for maybe 10 minutes. The RILD problem will persist across phone reboots (hard reboot and even xposed soft reboot).
I had the same problem on S3 and just couldn't figure out why and how to fix until I got the clue from the forum link below
https://forums.motorola.com/posts/c56958d919?commentId=660328#660328

Categories

Resources