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.
I have just updated to LeeDroid V2.2.2 and all is good.
Reading his post there is mention on using a I/O performance file and Setcpu.
What effect does setting the cpu to say 1.8ghz have on battery life?
I have downloaded Setcpu and had a look in the post but can't seem to find the best settings. Is there such a thing or not?
bluebirds said:
I have just updated to LeeDroid V2.2.2 and all is good.
Reading his post there is mention on using a I/O performance file and Setcpu.
What effect does setting the cpu to say 1.8ghz have on battery life?
I have downloaded Setcpu and had a look in the post but can't seem to find the best settings. Is there such a thing or not?
Click to expand...
Click to collapse
At 1.8ghz it will eat battery like a fat kid in a candy shop lol
Sent from my Desire HD using Tapatalk
just us it 245-1200(max) in smartass dude!the phone is already speed-up...only if u want benchmark results to impress yourself or some friends o/c it...
what will the i/o performance file do?
and how do you install it?
anheuer said:
what will the i/o performance file do?
and how do you install it?
Click to expand...
Click to collapse
I just installed leedroid yesterday, my first ever rom. I am also wondering if the IO patch will be of any use to me in every day use. I know lee says in his thread that its not fully tested so not sure whether to even experiment iwth it.
I think in Lees thead there are instructions for installing it.
Hello, to start yes I'm really stupid! I did watch the video in the start to try and find the answer to the following questions but it just confuses me and I would really like to get this done, thanks and on to the question!
So minutes ago I got my CM7 working for the first time! And right away I wanted to increase the clock of my CPU but it won't go higher then 768 on setcpu. From what I managed to understand its because of the kernel... So is it possible to increase the max clock with another kernel, if so whitch one and how much is safe to clock?
Thanks!
HTC Buzz (Wildfire)
Android version 2.3.7
Kernel version 2.6.35.14
Mod: Cyanogen 7.1.0.1 build GWK74
Yes its the kernel that controls CPU speed, test it for a while at 768mhz as not many wildfires can even cope with that, if you have problems random reboots, freezing etc then turn it down a little.
Kieranftw made a kernel called infinity ice or play I think? which made it possible to oc at 788 or 800mhz, mine was fine at 788 but very unstable at 800 so now I just settle for 768 as I didn't really notice a difference between the two, any higher than that is asking for trouble imo.
ok thanks for the answer, ive had no errors with the current settings, maybe ill keep it like this for the moment
This post might be in wrong section but I couldn't post in Omega thread due to insufficient posts
I used to use Omega 3.0 and Perseus kernel, everything works perfect, CPU freq jumps fairly between 200-1800. However when upgraded to Omega 4.1 my clock always ticks at 1800 and the device getting hot and battery drains quickly.
Not sure what I did wrong, has anyone encountered this issue?
Try change governor/scaling - you may use any cpu overclock app for that. Default for SGN2 is pegasusq.
This release is good, I tried many others but none is as stable as this one.
I've downloaded the KOSP ROM 2.7(unofficial version) switching from Evolution X's latest version just for the sake of seeing it's Performance since I've heard it's very optimized for gaming Smartphones, so far ever since I've downloaded that ROM, my Performance and Prime cores have been showing a really strange behavior.
They never go above 1478 MHZ for the performance and 1862 MHZ for the prime core when 865 has the potential to ramp up to 2.4 and 2.8 MHZ, and the strange thing is that it doesn't respond to dynamic Frequency Change if I want to change it in FKM.
Then, sometimes they would strangely ramp up to 2246MHZ and 2457 for the prime core, just to go back down to 1478MHZ and 1862 and unlike before, switching no governor does change that, almost as if there's some sort of magnet attracting it.
I've already tried switching multiple ROMs and Kernels even the ones that would grant be full frequency throttle that I've already installed before, but so far no matter the ROM and Kernel, result is the same.
Please guys, help, I'm seeing extremely bad browsing and gaming performance like this!
Edit: yes, it's running in performance mode and Governor.
Edit 2: as I'm talking to you, the performance cores randomly switched to 1.7 GHZ and not only I can't set them to 2.4, I can't even set them below 1.7, it's like my phone deciding for it's own, WTF going on!
THREAD LOCKED
As per the Forum Rules:
5. Create a thread topic or post a message only once, this includes external links & streaming media.
-snip-
-snip-
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
-snip-
Click to expand...
Click to collapse
For continuing discussion, kindly use the existing thread that you created earlier: https://forum.xda-developers.com/t/mi10t-running-below-full-throttle-cpu-frequency-help.4451737/
Regards,
shadowstep
Forum Moderator