[SOLVED] Slim ICS 4.2 sleep problem - Galaxy S I9000 Q&A, Help & Troubleshooting

[SOLVED]
Just re-flash
Running Slim ICS 4.2 and Semaphore ICS 1.2.6s which is oc'ed to 1.2Ghz with smartassv2.
Only app installed from market is Apex launcher, which isn't being used anyway.
Whenever the screen goes off and the system reaches 'sleep', the phone ALWAYS reboots into recovery... and it's really annoying :laugh:
Any ideas anyone?

mod2max said:
Running Slim ICS 4.2 and Semaphore ICS 1.2.6s which is oc'ed to 1.2Ghz with smartassv2.
Only app installed from market is Apex launcher, which isn't being used anyway.
Whenever the screen goes off and the system reaches 'sleep', the phone ALWAYS reboots into recovery... and it's really annoying :laugh:
Any ideas anyone?
Click to expand...
Click to collapse
too much over clock
Sent from my GT-I9300 using xda premium

Hey
Try re-flashing the rom again...
Sent from my GT-I9000 using xda app-developers app

Sorry guys, been busy so haven't been able to update this (phone was actually fixed the same evening). All I did was re-flash, along with the obvious other things like cleaning.
@slaphead20
OC was my first point of call, so I turned it back. I was left with the same issue, but interestingly with the clocks and gov set back to default it took alot longer for the phone to reboot into recovery after screen off and then sleep.
@tchindalia
That's what I did in the end, it's always my last option though (as it should always be).

Related

[Kernel] Dragon TEST... SetCPU profiles support...

http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.3-T1.zip
Dragon 3.2 w/ a fix that seems to work for setCPU screen off profiles setting the CPU to low values. Please note: The max freq in setCPU for that profile is what will be used, no scaling. I set it to 200Mhz and it's working fine every time I fire it back up.
The original patch is from here: https://review.source.android.com//#change,20804
Created by coolbho3k for the Nexus S, I backported it to Froyo. If we get good test reports from others, I'll push the changes to github tomorrow so other devs can use it.
When testing, please either use known good OC/UV settings, or don't OC/UV at all. Phantom OC/UV crashes won't help us know if this is working well for others. I've tested it with and without, turning my phone on/off like a madman... working fine so far.
Hmmm... early reports aren't looking good. Perhaps something isn't quite right. lol... Be warned if you try it, read all the comments. Might have to declare this one a fail. Too bad the NS cpu-freq driver is so different.. maybe I'll try pulling the whole thing over..
Downloading now report back tomorrow! This sounds promising.
Sent from my SGH-T959 using XDA App
Will test as soon as i get mine back to stock! Its just what I felt like doing today.
I did have a question..
Do we need to adjust it to say.. performance,on demand powersave? or will it just default?
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
coolkid893 said:
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
Click to expand...
Click to collapse
wow that can't be good. Sounds like the phone is overheating..
PaiPiePia said:
wow that can't be good. Sounds like the phone is overheating..
Click to expand...
Click to collapse
ya i know an its not even o/c its set to only max at 800mhz lol i think im gonna reflash to 3.2 to be safe but its a step in the right direction good try
Ok Im gunna have to try and install setcpu first.. otherwise my phone loads and restarts a few minutes into being on the desktop.
Testing now, Just UV'ed my clocks, and now setting profiles.
Observation so far:
SetCPU, and Uvolting seems to lock up my phone, and cause a reboot, and phone is pretty warm/hot.
Confirmed I can not run this either.
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
junxracr said:
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Im having better luck using profiles with 3.2 than with this one. I've been using set cpu since 3.2 came out with no problems @1.4 and on powersave when screen is off. I have made no changes to the UV settings.
yikes ! i smell quadrant score in few min lemme install it
Has anyone got a "kernel panic" on this before? I'm not sure what I could have done wrong.. had to Odin back to stock. Forgot to back up before I flashed, shame on me. lol.
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
bartek25 said:
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
Click to expand...
Click to collapse
Nah, it didn't wipe my data. I had to Odin back to stock because I couldn't go into Clockwork Mod Recovery Mode. It would go into Kernel Panic and it reset all my launcher settings....
Was running hot for me also. Back to stock and then to bionix .
I think that when you get things fine tuned you will have a great Kernal.

[Q] Pandora streaming is choppy on my HTC hero CDMA (CM7 flashed)

I recently flashed the aospCMod-20110123 (gingerbread) on my sprint HTC hero. The upgrade has been awesome so far except for one really annoying issue. My pandora app hasn't been playing properly (I uninstalled and reinstalled the app). The music becomes choppy when the screen turns off. Reactivating the screen fixes the sound most of the time but it's really annoying. I haven't had this issue before with CM6.1 (froyo). Did anyone else see this issue ? I would greatly appreciate for any possible solution to this problem.
Thanks.
prashm said:
I recently flashed the aospCMod-20110123 (gingerbread) on my sprint HTC hero. The upgrade has been awesome so far except for one really annoying issue. My pandora app hasn't been playing properly (I uninstalled and reinstalled the app). The music becomes choppy when the screen turns off. Reactivating the screen fixes the sound most of the time but it's really annoying. I haven't had this issue before with CM6.1 (froyo). Did anyone else see this issue ? I would greatly appreciate for any possible solution to this problem.
Thanks.
Click to expand...
Click to collapse
If you are using the kernel that comes with the ROM:
Go into CM Settings and then performance.
Within CPU Settings, change the governor to ONDEMAND.
You'll have to reboot. If that alone doesn't fix your problem then bump you MIN CPU setting to 256.
What is your min set to? Probably needs to be bumped up to 264 or whatever.
poashll said:
If you are using the kernel that comes with the ROM:
Go into CM Settings and then performance.
Within CPU Settings, change the governor to ONDEMAND.
You'll have to reboot. If that alone doesn't fix your problem then bump you MIN CPU setting to 256.
Click to expand...
Click to collapse
Thanks for quick reply. However, I don't find the CPU settings option under Settings->CyanogenMod settings -> Performance. Is that enabled by a separate app that I may be missing ?
prashm said:
Thanks for quick reply. However, I don't find the CPU settings option under Settings->CyanogenMod settings -> Performance. Is that enabled by a separate app that I may be missing ?
Click to expand...
Click to collapse
If you flashed a different kernel, you will not see the option. If that is the case, you will need to use Setcpu or Deca's battery tweak.
Sent from my HTC Hero CDMA using XDA App
poashll said:
If you flashed a different kernel, you will not see the option. If that is the case, you will need to use Setcpu or Deca's battery tweak.
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
Thanks poashll. I installed cputuner free app and restarted ph. That completely jacked my ph. I kept on getting "The process com.android.phone has stopped unexpectedly.." error. Nothing seemed to fix it. So I restored my cm6 backed up rom. Thank God that I had backed up my prev ROM. Then I downloaded and flashed the latest CM7 nightly build. This one had the CPU Settings option. Before I mess with it, I backed up my current configurations (it's a real pain in the butt to re-install all the lost apps and configurations). And then changed the governor to ONDEMAND. Now my pandora works great and battery life is still good!
Thanks a ton for all the help! I appreciate that.
hmmmm... I have been having the same problem since I installed ASOP gingerbread. and still have it with CM 7. adjusting the cpu settings work fine for me as long as I don't let the phone's screen go to sleep. but if the screen stays awake it's fine....
any other setting you suggest? kind of a waste of battery to be running pandora AND have the screen awake all the time.
noriyori said:
hmmmm... I have been having the same problem since I installed ASOP gingerbread. and still have it with CM 7. adjusting the cpu settings work fine for me as long as I don't let the phone's screen go to sleep. but if the screen stays awake it's fine....
any other setting you suggest? kind of a waste of battery to be running pandora AND have the screen awake all the time.
Click to expand...
Click to collapse
What settings are you using?
Sent from my HTC Hero CDMA using XDA App
poashll said:
What settings are you using?
Sent from my HTC Hero CDMA using XDA App
Click to expand...
Click to collapse
I set the governor to ONDEMAND and the MIN to 264. But like a dummy, I didn't set the 'Set on boot' option so my settings reverted when I rebooted...
How is the ondemand governor different than the standard interactive governor?
Mine is still on interactive, but the min is on 352. Anything lower than that for my phone, and it will skip when the screen turns off.

[Q] Phone won't wake up from lock screen

I'm running on stock jvq ROM. Before this, I have no problems waking up from lockscreen. After several weeks, my phone starts to delay when waking up from lock screen. I don't get any respond after pressing my home screen.
I tried factory reset.,yet the issue still occurs. What should I do?
Sent from my GT-I9000 using XDA App
Try another rom, if it persists then try a different battery.
EDIT: also keep the UV and OC at default values.
Battery would cause such issues? May i know what is OC and UV?
Sent from my GT-I9000 using XDA App
OC is overclocked and UV is undervolt
have u tried flashing different Kernel?
cheers

CM7 Nook freezing issues

My nook is booting up fine, but once it gets to the android interface after a couple seconds or minutes, it just freezes and I can't do anything until I reboot. Has anyone else had any similar issues like this?
If this is a repost, I'm sorry just point me in the right direction as I could not find anything.
Edit: This may be linked to beautiful widgets? I have reflashed CM7 twice now, seems to be linked to that.
Yep, BW will do exactly that. Fancy Widgets is a decent alternative for a large clock widget
I've been having a similar problem after I rerooted and installed phiremod. I can rarely even boot up and have a functional tablet. It almost instantly freezes and must be reboot only to do it again.
reeeaaally pissing me off.
---------- Post added at 05:24 PM ---------- Previous post was at 05:10 PM ----------
after about 10 reboots I was able get it running long enough to uninstall beautiful widgets and after another reboot it seems to have solved the problem. Its a bummer though cause it a good app.
I had the same problems with Beautiful Widgets and the BeWeather widgets. I've read Fancy Widgets work and I'm currently using HD Widgets since it has a 4x4 widget and hasn't given me any problems.
Sent from my PG86100 using xda premium
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
mondegreen said:
I'm having a freezing problem, with pure, clean CM7. I can use the Nook for 1-10 minutes, browsing the web, and then it hard freezes. Then if I reboot it, it typically gets stuck in a CM7 bootloop the next 1-2 times I reboot it. Then eventually it will boot successfully again.
I tried switching to running CM7 from the SD card, didn't seem to change anything.
(I definitely do not have Beautiful Widgets, or anything else, installed. I even checked in Manage Applications--none found.)
Click to expand...
Click to collapse
Are you overclocked? And I assume since you mention SD card, you normally run from the internal storage? And is this a hard freeze while you're using it, or some time later while the screen is off?
1. Not overclocked. Completely pure, just-installed, CM7 with no changes to default settings. No GApps even.
2. I had the same problem when running from internal. Switched to the SD card to see if that would change anything--it didn't'.
3. Hard freeze occurs while using it.
Thanks!
I also had major freezing w/7.1. I flashed the last nightly (11/16/11) and gaaps.
http://download.cyanogenmod.com/?device=encore
Although freezing might happen once in awhile, it's rare now. I only use one widget (wifi signal). Everything else is pretty much default. No overclocking, live wallpaper, themes, etc.
I've downloaded about 20 apps so far.
Yep, it is caused by beautiful Widgets. I had the same thing happen and I posted on their development forums. I was able to get the startup logs and send them to the developer. Then the response was he could not figure out the bug. The logs clear showed a problem when trying to load the bw, but the bug may have been down deeper the operation system.
Not sure. But bummed none the less.....
Sent from my NookColor using Xparent Green Tapatalk
I was having a similar issue. However I didn't have Beautiful Widgets installed. I solved this by going to the Cyanogen CPU settings. I set minimum to 800mhz, max to 1200mhz and the profile to performance. I also checked the SET ON BOOT (can't recall the exact wording.) After a reboot, I haven't experienced any freezing. Hope this helps you guys.
Thanks.
I will give that a try with a beautiful widget on my home screen. then I will report back on my findings.
Update: nope that did not fix the problem for beautiful Widgets. I made your changes, rebooted, added a super clock widget to my home screen, rebooted, it froze. Thanks for the idea, though.
Sent from my DROID2 using Xparent Green Tapatalk
I've been following this thread as I have been experiencing the same thing, I ridded the nook of BW and it hasn't helped the freezing upon boot issue, even knocked up the min setting to 800. I've reflashed a million times. This came out of no where.
Edit: its getting really annoying. This thing isn't even useful. Never occurs with the ics preview. Only with any cm rom.
Sent from my PG06100 using xda premium
Sorry to hear that. The only time I have really experienced freezing, it was always because of some application. Is there some application that you always install that could be causing the issue. I know at one point it seemed like a certain version of flash would freeze mine, even if it was just installed not being used. Are you using the most recent stable build of cm7?
for now I have switched to ics on my nook, just for fun, I wanted to be able to make my own nightlies so I set that up . Will have to try a beautiful widget on there once I make a backup.
Sent from my DROID2 using Xparent Green Tapatalk
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
---------- Post added at 04:10 PM ---------- Previous post was at 03:30 PM ----------
carlosraf20 said:
same issue here , mine freezes after an hour of use, ... i have nightly 10252011 with the oc kernel . i just change the cpu setting and will report back if this solves the problem , if not then i guess i will try the stable cm7.
Click to expand...
Click to collapse
reporting back still freezes , i will install cm-7.1.0-encore-signed.zip stable tonight and see what happens, what oc kernel to go with stable cm?
So for what it's worth currently beautiful Widgets seem to work on nook color ICS without freezing it up. But ICS is still in it's infancy.
By the way are you running off an sd card or Emmc? Running off an sd card is not nearly as good and that can cause a lot of freezing. Just throwing that out there.
Sent from my NookColor CM9 pre-alpha using Xparent Green Tapatalk
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
peanjr said:
Thanks for all the replies guys, I found out it was nook tweaks causing the issue. Removed it, and it's been running fine ever since. I'm on Kang cm7
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
how do u find out it was nook tweaks that was causing this?
Because it always ran just fine, until I installed nook tweaks checked "set on boot" for the cpu settings. I didn't change them, just ticked it. After that, anytime i rebooted, it was a fight to keep it on. So i removed the last thing i put on there, nook tweaks. Its not froze one time and I've rebooted it a whole since then. I reinstalled it but never opened the cpu settings, just edit the audio stuff, no freezes. Kinda wierd.
Sent from my PG06100 using xda premium
I just install cm 7.1 stable and change the kernel to daligrin 603011 and still having freezing issues . I don't want to do it ,but i guess i will have to do a complete wipe and then install cm 7.1 fresh.
Nook Color freezing issues
I too have having freezing issues.
Symptoms: I'll be using my Nook Color with no issues when it suddenly just locks up. No error of any sort on the screen. Screen does not black out. It just locks up. I think everytime it has happened has been after I've transferred several MB (over 5 at least) of data over Wi-Fi.
I'm running CM7.2.0 RC0 KANG build from 11/30/2011 from eMMC.
I'm overclocking to 1200 with the Min CPU set to 800 and the governor set to Performance. I also tried Max CPU at 1100 but that didn't make a difference. I'd had Min CPU at 300 but moved to 800 based on a suggestion found here. Setting the Governor to Ondemand didn't make a difference either.
I do have Nook Tweaks installed but have changed nothing from the defaults and nothing is set to start up at boot time. (I use it to get to USB Host Mode.)
With this build I haven't had any screens of death like I was getting on CM7.1. Just the freeze-ups.
Anyone else seeing a pattern with Wi-Fi?
I've never installed Beautiful Widgets.

[Q] Phone freeze

Hi, I have a problem with my O2x. Every night when my phone is charging, it freeze and the alarm don't work.. And every day I late at high school. Last night my phone was fully charged so I don't need to charge it, but yet my phone freeze and the alarm don't work again..
Why this happen?
My rom is Wiui 2.1.0.7 and i use the symbi0sis kernel. It is happen because I use the ramhack?
Thank you and sorry for my bad english.
I have the same problem too, i think it is a bug in the kernel. I have guestes2x 3.8 on my phone with the same kernel.
Sent from my Optimus 2X using xda app-developers app
Try to use other rom with same kernel, symbiosis works me perfectly together with temasek 135.3 final, no bsod
Sent from my Optimus 2X using xda premium
I like miui and i don't want to change it.. I'll try with another kernel to see if the problem persist.
Alecsexu said:
I like miui and i don't want to change it.. I'll try with another kernel to see if the problem persist.
Click to expand...
Click to collapse
You can try to set the phone to "Always active while charging" (not sure how the exact English translation is as I am using a German menu). You can find it in "Development options" in settings. I read in some other thread that this should help. Let me know if it works
I tried this but did not work.. now the only solution is to change the kernel.
Alecsexu said:
I tried this but did not work.. now the only solution is to change the kernel.
Click to expand...
Click to collapse
You could also try setting the screen-off frequency a bit higher. I've heard that some phones have problems with the 216mhz frequency (if that's what you're using)
Or it's due to the ROM. I had issues with WIUI too, been on Temasek's CM7 build for ages now and haven't had a problem since then.
If you shut down your wifi, the problem is solved.
What i do is :
Add a alarm on 11 pm with a profile included.
In the profile you should set wifi off.
So your wifi is automatic shut down.
And by the alarm you must include a profile with wifi on, so you can get your mail etc.
It is very simple
Sent from my LG-P990 using xda app-developers app
I changed the kernel and now the problem was solved. thank you guys for help.

Categories

Resources