Seems like a lot of people are facing problem waking up the phone resulting in getting black screen and nothing else.
I faced the same problem too that is why I decided to create a new thread specifically on this.
Let's share what caused our phone to go into coma based on our observations so that in time, the root of the problem can be traced.
Based on my observation, when my phone is left idle for some time, say 1-2hrs, it tends to become sluggish and setcpu will stuck at max or min value (Yes! sluggish even when stuck at max value!). Given long enough idle time, it will fail to wake up (e.g. every morning when i wake up after 7-8hrs of idle time).
I was using OpenDesire v4.0.10 and just changed to v4.0.15 to see if it still exist. I have setcpu set on 1075max 245min (ondemand) and 245max 245min (ondemand) when screen off. Also, using task manager.
Please share your observations and phone settings (ROM, versions, setcpu, task manager and others)
have you tried removing setcpu?
cgrec92 said:
have you tried removing setcpu?
Click to expand...
Click to collapse
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?
I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App
Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.
shai.bosse said:
I noticed using setcpu does make the phone sluggish. when uninstalled problem was solved.
Installed undervolt & got better batt life.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
what is this undervolt you talking about? mind elaborating a little?
@ngel said:
Perhaps, a more tailored topic title will help all readers understand what you're talking about.
However, HAVS kernels is the only common factor and SetCPU is not the cause.
And, my two cents, I don't think this issue deserves a dedicated thread since is specific to a single kernel flavor.
Click to expand...
Click to collapse
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly
webber2109 said:
what is this undervolt you talking about? mind elaborating a little?
Click to expand...
Click to collapse
Undervolt is a kernel mod that you install and it lowers the cpu drain by setting it to use lower volt values on each cpu freq. This cause it to stay cooler too.
Look for it in this forum. [Kernel] undervolt
Sent from my HTC Desire using XDA App
I am suffering from this once per day on Defrost and OD so I suspect its kernal related. I am running the default HAVS kernel at the stock 998 frequency. I uninstalled SetCPU yesterday and had a lock this morning ( Defrost 4.1 ). The notification LED was flashing orange. So SetCPU is not causeing the problem. I have swapped over to SVS so I will report back on how that goes.
webber2109 said:
Nope, but in OpenDesire thread, people without setcpu experienced the same thing. Do you have such problem?
Click to expand...
Click to collapse
I use OpenDesire 4.0.10, then 4.0.15, then 4.0.16, each release for at least 3 days, and not for once have I encountered such "black death"....no setCPU of course.
Care to elaborate what apps you have there ?
webber2109 said:
I created a specific thread on this topic because there are many people out there experiencing this bug and there is no dedicate thread to discuss it. I assume you are not facing this problem because otherwise you would understand the pain and frustration of encountering this problem repeatedly
Click to expand...
Click to collapse
That issue is relative to OpenDesire and DeFroST ROMs only, and when they use a particular kernel version (HAVS) on selected CPUs, so I continue to think that it'll be eventually sorted out by the respective developers and/or Kali- and the kernel team; those guys do monitor the ROMs threads so they're already aware of the issue.
And yes, I suffered the issue twice, as I wrote more times in the DeFroST thread. "Pain" (panic?) and "frustration" sound a bit strange to me, when dealing with overclocked, custom, highly tweaked cooked ROMs. If a reboot scares you, head for a stock HTC ROM and you'll be fine.
I was worried I was the only one who had this. Thread title isn't that helpful for people seeking advice on it though. Get this after every reboot for about a minute until everything is back to normal.
Had the sluggish issue when using YouTube after about 20/30 mins, other than that I've had no lags.
Using 4.0.16
Sent from my HTC Desire
Double post
I got this on a svs kernal, so its not just restricted to havs. I had 1300 svs installed. With setcpu. Done the same with 1267 svs.
I've also had this issue on SVS kernels, was also having a series of hard resets last night - have rolled back to an earlier version of my favourite ROM flavour for now.
Never experienced anything like that...Although there are times that my Desire's performance would remind me of the bad old Diamond days,where patience was a virtue(well,not a virtue,but a money saving method!throwing your phone to the wall with your full strength after it frustrates you with being slow is known to be a costly process! ).Seems to be some apps running in the background...Maybe if your phone recovers after it without a reboot you can check if any apps use a larger than normal amount of ram.Other than that...Well,god is almighty and people experiencing epiphanies are known to work wonders through the ages!
And something completely off-topic(sorry about that).When using an undervolted rom/kernel you are not able to overclock to values as high as when using a normal-volted(is the word right?I dunno...) rom/kernel,right?I mean,what would happen if someone tried to overclock to 1382MHz(I know,I like the limits) using an undervolted kernel?And finally,how does this all apply to the hardware?Does UV affect the CPU's health like overclocking or something like that?
Thanks a lot!
I've had it on OpenDesire 4.0.10 and 4.0.15 a few times. Stopped happening when I stopped using profiles and defaulted back to to 998/ondemand.
Will try running it on 998/interactive for a while and see what happens.
No lockups after SetCPU to ondemand. OD 4.0.15.
Sent from my HTC Desire using XDA App
Separate thread IS useful, otherwise replies get lost in ROM threads where the focus is not specifically on this problem.
I too had this issue three times. DeFroST on all occasions, versions 3.x iirc. Never tried the HAVS kernels, just plain default what is shipped with the ROM (SVS @ 12xx Mhz?). Also SetCPU'd it, have not yet bothered to try and turn that off yet. SetCPU keeps it at 995 Mhz max, interactive governor, while switching to powersave while asleep.
Issue happened twice while browsing (possibly with Flash ads on the page by accident) and the power state switching (i.e. turn the device off quickly while running for train, afterwards reading for 2 minutes again, etc). Third time it happened while tethering my internet connection to my laptop.
Hth
I had this problem few times a day when I upgraded OD to .10 and the new ADW on the same day.
Then I restore back the old OD with old ADW, then no problem.
Related
Does anyone know how to over clock you're DI to say 1.2? Thanks for any help.
You first need to root your phone, then install a kernel that is compatible with whatever rom you are using, then you need to install an OCing app like SetCPU and adjust accordingly.
I'm rooted running the 2.2 RUU and I have set cpu. So do I just need a kernal? Which one?
i reccomend King Kernel bfs #4, best freaken kernel ever... its located... here
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
makos101 said:
so when i install this kernal is it ok to just bump the cpu speed up to 1.2? are there any guides to do this?
Click to expand...
Click to collapse
A lot of factors come into play when you start overclocking, every rom will respond differently.
The first thing to do before anything is to do a complete nandroid back up.
When overclocking keep in mind that the more you overclock the more chances you have of making your system unstable.
I have experimented a quite a bit and I have found that the King Kernal #4 seems to work well for me and at 1.2 it seems to be pretty stable. Any higher than that and my phone will sometimes re-boot itself for no apparent reason.
Again, your rom may handle things different so experiment and see what works best for you.
And remember - Do a complete backup first!
I'm using the number 4 kernal and it only goes to 1.19 is this what you mean by 1.2? I have to keep mine at 1.1 ghz at 1.19 my di gets unstable
Ya that's as high as they can oc these chips. I can only get to 115 safely 119 just crashes. But the charging experience will be better than stock with the BFS #4.
Sent from my ADR6300 using XDA App
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
makos101 said:
Could you guys please tell me what your settings for setcpu are?
I want better battery life and a faster cpu but im noticing that my phone almost needs a wake up time when i come out of screen off.
Thanks so much
Click to expand...
Click to collapse
If you are experiencing slow wake up, try increasing the min cpu speed to something around 460. Better batt life and increased speed takes a lot of experimenting. Your OC speed might differ from others due to differences in the phones cpu. For example, I have never been able to oc to 1.19 without the phone freezing or rebooting. My phone can handle 1152 but 1113 is perfect. In my opinion, ROMs have something to due with best batt-speed combo. I am running Ruby 1.1.1 with a setcpu profile of Screen off=245 without any wake lag. Other ROMs I have tried had wake up lag at that speed profile.
My set up:
(ROM-ASOP) Ruby 1.1.1
King's #1 ASOP "I told you so"- only works with ASOP
With the ROM's "Gem" performance scaling setting off, I use setcpu to OC to 1113, min is 245. I have a profile set to SCREEN OFF = 384 max/245 min.
I haven't worried about battery life since I started using King's kernals (I've tried them all with every compatible ROM on xda). I have several posts elsewhere on XDA showing 12 plus hours on a single bump charge and heavy phone use. Good enough for me. Stock cpu speed plus Sense ROM seems slow to me now.....to each his own though.
I hope to get some help because i value the opinions of those on this forum. Currently i am running virtuous 2.7 with virt. kernal v2. I am rooted, s-off, 2.15.xx radio. I want performance without draining my battery. What are the best settings to use in setcpu?
I did try king's kernal #4, but it was rebooting. switched kernals this morning.
One other app I use in conjunction with SetCPU is MinFreeManager. This will readjust your free ram to a higher standard. But with SetCPU I have it at 1113/Ondemand with no custom profiles. One other thing I really don't set is the Set on Boot option. I don't know why but I do. So with SkyRaider Vanilla 3.0 RC3/ KingX Kernel #4/ and MinFreeManager my phone fly's. I can't say for certain what settings you need for your phone but 1113-1115 is preferred by "most" phones and keep the set on boot option off. I keep a Galaxy S live wallpaper running and pandora while browsing the web and no lag what-so-ever.
CyanogenMod 6.0.2 and KingX kernel #1 with the same setup runs almost as smooth.
Hope this helps you out.
I have been bouncing back in and forth from rom to rom. Most are great. Warm 2.2, DamageControl, and Virus (currently running). The issue I'm having is no matter witch rom or kernal I run on my Evo froyo, every time I install Setcpu within a couple of hours my launcher (no matter witch one) stops working. I have gone into root to reinstall, install and uninstall and nothing works. All Rome are affected by what I can tell. I'm finding the problem to be with setcpu. I'm surprised if can't find much information on this. Does anyone have ideas?
Sent from my Evo using Tapatalk
Yea, setcpu can improve things but also causes issues elsewhere. I was using launcher pro for a while, and using that in conjunction with setcpu gave me nothing but poor battery life and terrible freezing. I have since then stopped using setcpu and my phone works fine. Besides the difference between 1ghz and 1.1-1.2 is negligible on the Evo unless your benchmarking imo
sent from my DAMN Evo!!
Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.
drmacinyasha said:
Stop putting your phone's minimum frequency at 128 or 245MHz. Also, tweak your launcher's memory settings properly.
Click to expand...
Click to collapse
I did all that already. I had my screen off set to 384mhz, im no novice, setcpu has great benefits but has some negatives also.
OP, try ziggys 10/26 kernel. It has scripts that handle oc'ing up to 1.13ghz using interactive governer WITHOUT using setcpu
sent from my DAMN Evo!!
I use SetCPU and Launcher Pro Plus and have used these 2 on every ROM I have used...which is a LOT!! My screen off is set to 245 and I OC to around 1228. I have NEVER had any issues on amy ROM. I dont know what is causing your issue but it isnt SetCPU and Launcher Pro....
This is stock ROM.
Every time I flash bacon bits to overclock my phone I always noticed that my screen flickers when I turn off the phone's screen or press the button to wake up.
Sometimes it just gets stuck and it stats flickering like crazy and I can't unlock my phone because of it.
This only happens when I OC my phone. When I wipe the phone it works fine but no OC which is what I want.
Any way to fix this issue?
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
dustrho said:
I don't use Bacon Bits, but I have experienced the flickering you speak of. It seems that happen when you go too far with the OC process. What happens if you were to lower your clockspeed a bit? Does it continue to happen for you?
Click to expand...
Click to collapse
Actually I OC my phone, but it's still set on 806MHz so even at lower clockspeed it still flickers. It's bugging the hell out of me.
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
captainreynolds said:
EDIT:
Switched over to pershoot's kernel: http://forum.xda-developers.com/showthread.php?t=847672 I can now overclock to 1.5 gHz with no problems anywhere. Aweseome.
I have this same problem and am bumping this thread.
I'm running stock rom with bacon bits v 0.3 - and my screen flickers when turning off so much that it won't turn off fully and opens the lock screen. I have to just try and try repeatedly to get it to work.
Any suggestions?
Click to expand...
Click to collapse
Yeah, I have flashed all the kernels even pershoot's and it still flickers. I'm using the original ROM that came with the phone not the original one posted on the forums. Maybe if I use the one posted on the forums that will work?
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
captainreynolds said:
I have the stock rom as well - I first flashed baconbits kernel, but when that flickered, I flashed pershoots most recent kernel in recovery. No flickering anymore - sorry to say I don't know what's wrong. Try posting in the thread of the kernel you are currently running!
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
Well you know what I flashed an older version of pershoot mayeb I should try the newer one. I'll let you know what happens...
I had trouble flashing it with ROM Manager. Clockworkmod it. Here's the link to pershoots blog with the latest update links: http://droidbasement.com/db-blog/
Good luck!
Sent from my T-Mobile G2 using XDA Premium App
Just tried it and nope... it's still doing it maybe it's just my phone.
Bring it up in this thread:
http://forum.xda-developers.com/showthread.php?t=847672&page=103
Pershoot is always monitoring it along with a bunch of other smart devs. Maybe they'll have a better idea - don't give up hope!
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
pmcqueen said:
what app are you guys using to manage your OC?
if it's setCPU, set your scaling to Interactive on the main screen and in any profiles you're using.
also, if you are using any screen on/off animations, disable them (just to see, for troubleshooting purposes, if that might be the culprit)
Click to expand...
Click to collapse
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
jjuice525 said:
Yeah, it's set on Interactive and so are the profiles. As for the screen on and off animation I believe that's in the CM7 RC1 ROM. I'm using the stock ROM so there's no option for that.
Click to expand...
Click to collapse
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
pmcqueen said:
hehe, didn't even read what rom you were using. my bad.
kernels aside, it is very possible, as you mentioned earlier, that you guys got the chips in the stash that don't take to overclocking very well. even on a device like the G2/DZ that seems to take to higher clock speeds relatively easily, there are bound to be some that aren't as happy with the increased workload.
if I think of any other bright ideas, I'll let you know. I haven't played with baconbits a lot.
Click to expand...
Click to collapse
Actually, after installing Pershoot's most recent kernel, I have no problems. Maybe I just got lucky here.
Hi. I'm using BlackICE ROM and I came across one, major for me, issue. I mean, sound skipping during unlocking device, turning on the screen, opening maps. It happens randomly. Other roms are fine.
I'm using PowerAmp Beta3. But it happens also with MusicMod, GoogleMusic and many others.
Any sollutions yet? I really want to stick with this rom, cause it's the best so far for me.
The only time I have ever experienced similar issues is when I had the screen-off CPU frequency set too low. Increasing it a little stopped the skipping and made the device fast and snappy on wake / unlocking again.
What kernel and governor do you use, and do you use any scripts like Killersloth etc?
I used LordModUE V8 kernel and interactiveX governor. I used setCPU and set CPU to 1.5 ghz
Too bad, that music skipping was happening with screen-on, during normal use. I mean, reading text msgs, browsing. And it happened randomly. On hydrogenmod i haven't experienced anything like this. only on blackice.
Oops, I just hit thanks instead of quote so make sure you do something nice for someone today
Back to your issue... in that case I'm not sure. It shouldn't be happening with screen on that's for sure. Sometimes a full wipe and reflash of the ROM can fix any problems, so that would be my first suggestion. If that doesn't fix it then maybe try some different kernels... like older versions of LordMod or whatever other kernels are popular for CM7 based ROMs (I'm not really familiar myself as I use Sense based ROMs).
Edit to say you could also try Ondemand governor, I find that has best results
Tried many different governors. But the problem was swill there. But the problem is over since i started using unity rom thanx for help! and for thanks ;p
No problem! Glad you got it sorted
Hi guys,
I'm a bit of a noob so please bear with me. I recently rooted my phone (SGH-I747M Telus), I have CWM recovery installed. I was interested in overclocking so I installed this kernel on my stock rooted rom (I installed the "sammy" one). I also cleared the delvik cache, cache, and fixed permissions before rebooting. Now I'm having a weird problem with video playback. I get these bleep like sounds, like you might hear on a spaceship, lol. The normal audio plays in addition to these sounds. Yet, regular audio plays fine (mp3s), same with youtube. So, my question is, why? Is there any way of fixing this? I'd rather not play around the stock ROM. I made a backup before doing anything and recently tried to restore the boot, but I got an invalid md5 check.
-JC
Okay, I was able to fix my problem by flashing the stock at&t kernel... but I would still like to be able to overclock... is there another kernel that I can try or a way to fix the problem with the kernel I already tried? Thanks.
If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.
ghost77 said:
If you still want to try previous kernel your problem might be because of heavy undervolting , kernel creator posted this voltage chart.
You can experiment by increasing voltage and see if that helps.
Or you can just try this faux kernel , its pretty good also, we don't have many kernel choices for Samsung based roms at this early development cycle.
Click to expand...
Click to collapse
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.
JustChillin1414 said:
Thanks for the reply... but I was able to fix the problem. It was something wrong with the settings of SetCPU which I installed earlier. I changed it from on demand to performance and now all is well. Now I have a question about battery life. Will overclocking drain battery a lot faster? I imagine it would only make a difference if I was doing CPU intensive things.
Click to expand...
Click to collapse
Well.. performance setting makes it so that your CPU runs 100% all the time. I don't think that will be battery friendly . Overclock generally uses more power and battery longevity will depend on your usage.
You can try messing with setcpu settings. Try Conservative, then limit minimum speed to 384 and max to your preference. Try your movie again.
Current kernels and setcpu are a bit quirky.
I had the same issues on ktoonsez Sammy. Ended up back at stock AT&T. I've heard it's an issue with many of the kernels but a fix is on the way. Couldn't find a way to get rid of it, but that's not to say it can't be done. Don't have much time to tinker right now.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Its a known issue on ktoonsez kernel. Flash faux's kernel, it has the same features (as well as GPU OC) and doesn't have the audio issue.