I wanted to explain black screen issue many folks are encountering with overclocked kernels. The root cause is that voltages at higher clock speeds are not high enough to get the screen to turn on. In other words, if your screen is off and your phone scales beyond 800Mhz, the phone does not have enough power to turn the screen on. You'll almost always scale to the max the moment you hit that power button.
There are a few ways to prevent this from happening (from best to worst):
Create a "screen off" profile in SetCPU to restrict the clock to 800Mhz or below when the screen is off. I think it's obvious why this works. At the same time, a lot of people already do this, which explains why everyone hasn't been having the problem.
Use the conservative governor. Because it scales more gradually, it won't immediately jump past 800Mhz when you attempt to power the screen. There is still a chance of encountering the issue if you attempt to turn on the screen if the device has been busy for a while.
Increase voltages in the kernel. I started experimenting with this before I decided to come here and recommend the first two options. To get the screen to reliably turn on at higher clock speeds, we'd have to raise the voltages substantially. So we'd end up with more risk of damaging components, degraded battery performance and so on. Once the screen is on, the cpu does not actually need more power than it's being given in today's frequency tables. Thus, we'd effectively be increasing power consumption all the time to deal with a need for more power at screen on. Clearly a bad idea.
Unless you're using SetCPU profiles (or equivalent) or the conservative frequency governor, you're going to get black screens. Cyanogen, Pershoot, Evil's and my kernels all use roughly the same voltages, so you're going to need to apply this solution regardless.
There you have it.
*Applauds*
I bow down to your wisdom, sir!
Can you explain why this doesn't happen to me when I'm on CM 6.1.1 ROM?
With setcpu settings at 1209/368 (ondemand scaling, no profiles) I have black screens on Virtuous but neveron Cyanogen's mods.
rgl12miami said:
Can you explain why this doesn't happens to me when I'm on CM 6.1.1 ROM?
With setcpu settings at 1200/300 I have black screens on Virtuous but never
on Cyanogen's mods.
Click to expand...
Click to collapse
I'd have to do more testing to confirm but I would guess more load is generated (events triggered) with Sense ROMs at the time of wake, causing the ondemand governor to scale up to nearly max more rapidly than CM.
There's a simple way to see if it'll ever happen on CM. Set your governor to "performance", with clock speed above 1Ghz. Turn off the screen and see if it fails to turn after a few attempts at toggling it on and off.
I did what you suggested about 30 times and no one has failed. It's a shame,
because I do really love your ROM: speed is incredible. But what bothers me
the most is when the alarm sounds or I receive a call and the screen refuse to
lighten up. I will keep an eye on your rom and for sure I will be back on it soon.
Great job! The best sense rom i've ever seen.
Thanks for this. Works perfectly on my Stock SenseUI ROM with virtuous kernel
Thanks! That explains why the issue hasn't been happening since I set my profile to conservative. That was probably the most annoying issue since I got my G2.
I bet the fact that every cpu is different would also explain why it happens to some and not others.
Again every cpu is different, but here is my settings for screen off. Min 245 max 245. I started min 245 max 368, dropped max down and no adverse effects and great bat life. I have no blackscreen/wakeup issuses. I've been using setcpu to save battery since before the first oc module/kernel.
Would def test kernel that drops below 245 and/or uv it greatly.
fastludeh22 said:
I bet the fact that every cpu is different would also explain why it happens to some and not others.
Again every cpu is different, but here is my settings for screen off. Min 245 max 245. I started min 245 max 368, dropped max down and no adverse effects and great bat life. I have no blackscreen/wakeup issuses. I've been using setcpu to save battery since before the first oc module/kernel.
Would def test kernel that drops below 245 and/or uv it greatly.
Click to expand...
Click to collapse
What do you mean that every CPU is different? At the hardware, firmware, software level?
gee one said:
What do you mean that every CPU is different? At the hardware, firmware, software level?
Click to expand...
Click to collapse
I think he means every cpu handle overclocking differently, for example ive been very unlucky and my cpu cant handle anything above 1.1 Ghz and it crashes if i set it up any higher but lots of people running theirs at 1.8 and they are stable
its just like overclocking PCs every cpu handle overclocking differently even if they have the exact same spec.
I'm bumping this due to how useful this information is and how often the issue still comes up.
Sent from my HTC Vision using XDA App
rmk40 said:
I wanted to explain black screen issue many folks are encountering with overclocked kernels. The root cause is that voltages at higher clock speeds are not high enough to get the screen to turn on. In other words, if your screen is off and your phone scales beyond 800Mhz, the phone does not have enough power to turn the screen on. You'll almost always scale to the max the moment you hit that power button.
Click to expand...
Click to collapse
I don't understand why I don't encounter this issue at all with AOSP ROMs. Is there an obvious reason I'm missing?
poochie2 said:
I don't understand why I don't encounter this issue at all with AOSP ROMs. Is there an obvious reason I'm missing?
Click to expand...
Click to collapse
This was the first question asked (see the fourth post). Here's the OP's theory...
rmk40 said:
I'd have to do more testing to confirm but I would guess more load is generated (events triggered) with Sense ROMs at the time of wake, causing the ondemand governor to scale up to nearly max more rapidly than CM.
Click to expand...
Click to collapse
I haven't seen this issue before either.
ianmcquinn said:
This was the first question asked (see the fourth post).
Click to expand...
Click to collapse
My bad, I missed that.
Related
As per the title, I have started experiencing random system lockups since yesterday. I have had to perform two battery pulls and I'm starting to worry that my ext partition won't be so lucky next time...
I have no idea what is causing the lockups, though both have occurred while using Swype. Coincidence?
For now I'm going to set my system clock back to 600Mhz and use the default input method for a while and see if I still get lockups, at which point I will probably flash another ROM unless I can find a solution, which is where you guys (hopefully) come in. Is there anything else I can do to diagnose and/or solve the problem?
- Typed from my rooted HTC Legend -
It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version
Try interactive governor or flash latest kernel from the other thread.
TheGrammarFreak said:
It's most likely the OC that's causing the problem, Swpye shouldn't affect the stability. Unless it's a cracked version
Click to expand...
Click to collapse
That's peculiar, as I've had the processor on 768Mhz for a while now and I've had no problems at all before now.
As for Swype... it could be. ;P
BlaY0 said:
Try interactive governor or flash latest kernel from the other thread.
Click to expand...
Click to collapse
I'll try that, but what exactly does each governor do?
segphault said:
I'll try that, but what exactly does each governor do?
Click to expand...
Click to collapse
It manages when the processor speeds up. It doesn;t run at 768MHz all the time, that's just the highest you allow. Ondemand scales the frequency up when it's needed, and lowers it again afterward. It seems to be a little bugged in our kernels though, and causes crashes.
Interactive does a similar thing, but without polling the CPU. It also ramps the frequency up a little more quickly. I use it, it makes the phone more responsive (IMO), and also eliminates the need for profiles in setCPU (to a degree)
Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.
segphault said:
Just checked my kernel version - I already have the latest version (2.6.32.17). I've also set the governor to interactive as suggested, but I have pushed the max clock back to 768Mhz and the min clock to 122Mhz.
While we're here, is there any way to push the min clock down even lower, or would that require fiddling with the kernel? In which case, I have two questions:
1. blay0, I've heard people who can push their min clock down to something ridiculous like 19Mhz if I recall correctly, which makes battery life last a crazy amount of time. Could you include that as the minimum clock in the next kernel for b 0.8?
2. If not, how do I go about changing it myself?
I want to learn.
Click to expand...
Click to collapse
You'd have to mess around with kernel source code. I wouldn't know where to begin, sorry
Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App
MaBlo said:
Wouldn't 19 MHz min also make the phone painfully slow to wake up? Just curious.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
That did cross my mind but other users have reported success with it, so I figured I might as well give it some investigation.
I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows
TheGrammarFreak said:
I had mine go to 19 min with screen off once, it did my head in. Maybe interactive with a reasonable upper limit with screen off (like 400) would work, who knows
Click to expand...
Click to collapse
Maybe not quite 19Mhz, then.
Perhaps we should do some testing to see how much processing power is needed to wake the phone quickly? Is there any way to test that?
Back on topic, I just had another lockup while using the interactive governor. This time I froze up while loading Fruit Ninja.
Now I'm at a total loss for what could be causing the lockups.
- Swyped from my rooted HTC Legend -
Seeing as nobody can seem to pin-point the problem, I'm moving to CM7 permanently as soon as it's released as stable.
For those of you on CM7 (preferably RC2 or later nightlies), are you using SetCPU or the built in CMSettings CPU manager? Which is giving you better performance/battery life?
I can't help but think that the built in CM Settings CPU tuner is going to be conflicting with my SetCPU profiles.
Been using nightlies since #30 or so, and I currently run SetCPU with a normal profile, a screen off profile, and a profile for <10% battery and haven't touched CMSettings' CPU manager.
I'm contemplating just uninstalling SetCPU for a day or two and seeing what a 1017max / 245min Ondemand or Powersave governor via CMSettings ends up doing to my battery life considering there will be no screen off profile.
Any thoughts?
I dumped setCPU after a lot of testing (and even bought it on market)
I'm finding I'm much happier using inbuilt CPU settings. I think battery life is the same but performance is better due to the fact that SetCPU would sometimes get stuck in my screen-off profile when turned on causing the phone to be really slow.
I recomend uninstalling setCPU, set your ONDEMAND governor with ~1Ghz and run it... You'll find your battery about the same but much less hassle.
I have yet to try that, I somewhat feel obligated to use SetCPU since I purchased it lol. But it probably won't be the last time I waste money at the market.
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Utorrent76 said:
Neither. CPU tuner works best for me.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
its the same thing :facepalm:
Try the inbuilt one... I think its way easier
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
DJAeroX26 said:
I say setCPU cuz as battery gets lower... I have my CPU speed lower also. Basically, 15% battery lasts me forever :] lol
Sent from my T-Mobile G2
Click to expand...
Click to collapse
Definitely. This is the one thing I like about SetCPU is having the 10% and 5% profiles so that I can get the last few % to last forever if I need it. Although in normal day-to-day use I'm never pushing it below 20%.
ScooterG said:
Whatever you tell SetCPU to do, you'll see the same settings mirrored in the CM settings.
Click to expand...
Click to collapse
Yea I see this, as far as the governor changing etc.. This is why I'm wondering if it would be easier on my phone to just run only the CM Settings one.
I notice that every 5th or so time I unlock the phone, there is an obvious lag switching from the screen off profile, and my unlock sliders jitter around and it takes 4-5 tries to unlock the phone. I think this is probably partially due to both settings switching over trying to change.
I think I might try backing up and uninstalling SetCPU for tomorrow to see how it goes.
colonelcack said:
I've been wondering about this too. I don't quite understand how it works. Can I just set the frequency higher till a certain point without changing the voltage and get the same battery life?
What's the best way of doing this? Just change the clock speed or do I need to change something else or update the kernel?
Click to expand...
Click to collapse
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
redpoint73 said:
I've read on here that overclocking the Vision's CPU up to 1 GHz requires no over-volting, and in theory should not affect battery life (but not sure exactly where that information originates from). But there has been lots of debate on these forums on whether the SetCPU app helps or hurts battery life depending on screen-off profiles (underclocking to save battery) or its constant polling of the CPU clock (possibly killing the battery faster).
A kernel that supports overclocking is already part of the CM ROM. If you are on CM, you can just adjust the clock speed under Settings>CM Settings>Performance>CPU settings. Or set the CPU clock using an app like SetCPU. Choosing one method over the other is what is being asked/debated here. If you are on the stock ROM, you need to be rooted, flash a custom kernel that supports overclocking, then install an app such as SetCPU or CPU Tuner to set the CPU clock to your liking.
Click to expand...
Click to collapse
I'm not sure about CM's kernel with the over-volting but I do know that Pershoots kernel can be overclocked to 979mhz without over-volting (Pershoot told me himself).
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Daughain said:
At 1.8Ghz, I find the temp settings in SetCPU very useful.
Vision rooted, booted and scooted
Click to expand...
Click to collapse
Well obviously.... But why the hell would you ever need to be running at 1.8ghz? The fact that you are always using a temp-specific profile method should show you that consistent 1.8ghz isn't good for the phone...
Okay so I uninstalled SetCPU last night and I'm going to run just the CM Settings CPU manager all day to see how it goes. Running like this:
ONDEMAND governor
Min CPU: 245 mhz
Max CPU: 1017 mhz
On nightly #19 also.
Okay so its midnight almost, and I'm at 13hrs unplugged and 52% battery still. Pretty general/light use, phone is just as snappy and the lack of a screen off profile doesn't seem to effect battery at all. Liking it so far! very interesting to see the screen off profile not mattering much.
SetCPU for me. I like to have a temperature and charging profile, to prevent the phone from overheating. Even at 1ghz the possibility exists, nice to have a backup incase.
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
tackleberry said:
I'm thinking set cpu conflicting with the cm built in caused my ****ty running problems. I have not used setcpu since and been good so far
Sent from prison
Click to expand...
Click to collapse
With multiple tries... If you change the settings on one, it cancels the settings on the other... Maybe it's because you had set on boot enabled on both?
im going to run the CM tuner and uninstall Setcpu and see how it runs. i never thought about this but i do get that lag when i turn my screen on sometimes. im gonna miss having the profiles but ill see how it runs over the coarse of a couple days.
Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!
http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.
063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.
Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...
Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.
I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.
dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.
After reading through the Thread for the Pre Release of FuguMod Ultra in the development section of this forum I thought I would post some info up for people who are wondering why it doesn't work with their phone, and just some general info on overclocking.
- First off, not all phones will be able to run at 1366MHz. Every CPU made has a range of freuqencies it will work at, and it is different for every single one. So some may be able to handle 1366MHz and above, others may max out at 900MHz. If you are getting black screens, freezes, or random behaviour, then your CPU doesn't like the frequency you have it at, try a lower frequency.
- Always keep an eye on the temp of the CPU when testing overclocking, if the CPU gets too hot, and fail safes don't work, there is a chance you could fry your CPU.
- With the FuguMod Ultra kernel, you must also be aware that gpu bus frequencies have been changed, so if your phone is not happy with that it will black screen. (as bus speeds are like cpu speeds, every different device can handle different clock speeds)
- plls values have been changed, and these may cause problems on your phone.
So if you want to have a go at overclocking your phone, back it up, and then give it a go. Select a frequency, and test with something pretty cpu intensive (3d game, multiple quadrant passes) and see if there are any bugs/overheating during a 15min time period. If you notice any problems/too much heat, try a lower frequency, and try again. And if for some reason your phone doesn't like the kernel, you can reflash with your previous kernel or a new ROM as you have already backed up your data.
If you have any other questions about overclocking, feel free to post here and I will try my best to answer them.
--- Samsung G3, InDroid 4.3, FuguMod 2.4 B3 800MHz ---
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
dilzo said:
How can you check the CPU temperature? I thought it was only battery temperature.
Sent from my GT-I5800 using XDA App
Click to expand...
Click to collapse
The battery temp is a good representation of how hot the processor is getting as it is right next to the battery (only a thin sheet of metal seperating it) If the battery rises in temperature by a few degrees, then you can summize that the cpu is probably getting a few degrees hotter than that. I really wouldn't recommend letting the battery get above 55degrees (celcius) as this means the CPU may be getting up close to 65degrees (celcius) which is a very bad thing.
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
marcellusbe said:
Good post.
Note that if you want to make some stress-tests, you have to put "PERFORMANCE" governor and set the max freq you want to test.
Click to expand...
Click to collapse
Yes, Very true!!
Must also say, Your kernels are pretty legendary! Waiting patiently for the offical release of your FuguMod Ultra
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Piyush Rawal said:
m not able to see time in state with both setcpu and cpuspy and it seems deep sleep is also not working.
Click to expand...
Click to collapse
How have you got your phone set up? i.e. what ROM are you using etc.
I am using stock jpq with app2sd, swap, zipalign, ramhack and stuff. Setcpu is installed with default min/max freakquency, No profiles in use and undervolt a bit.
Ok,
This may be an issue caused by XXJPQ, as it is a new release there may be some sort of conflict. Have you tried asking if anyone else has this issue in this thread? http://forum.xda-developers.com/showthread.php?t=1132697
I haven't played around with JPQ yet so don't know what the bugs are yet.
Also, are you running a stock kernel? Have you confirmed that the phone has been rooted properly as well?
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Piyush Rawal said:
It's definitely a bug in Kernel. I tried three different roms and i wasn't able to check time in state in any of them (I am talking about fugumod ultra prerelease kernel here).
With previous versions of fugumad kernel everything is fine. So definatly a bug in kernel.
Click to expand...
Click to collapse
Ok cool, I'll report the bug to the developer so that he can have a look into it. Thanks for testing and proving to the kernel.
Little bit of info some might find helpful. After some recent testing, I have found that some people might experience a black screen freeze when phone is in standby for a while with 83MHz min setting and on demand governor. I am not sure of the exact reason for this, whether it is a bug, or that the processor just doesn't like going that low for extended periods of time. If you experience this type of error, just hard reset the phone then open setcpu after phone has loaded and change the "standby" profile minimum to at least the next step up on the slider. Personally I use 223 setting as it provides a smoother lock screen animation, and no significant difference in battery drain.
Sent from my super smooth GT-I5800 using XDA App
Lately I've been noticing when I go to grab my phone, it will be magically turned off. I know it wasn't turned off because it will just sit on my desk, full battery, no loose battery connection (NEVER has the phone turned off while use or moving around, but still an assumption), no crazy setcpu scaling (min: 245MHz max: 806MHz), and no water damage. I haven't had this problem in the past with CM7 nightlies, or CM7 final release. I also know that its not just that problem I have every once in a while where the screen won't turn on but the 4 touch buttons will. But I'm 99% sure that's just a result of my min: 245MHz max: 245MHz screen off setcpu profile. Anyone have this issue or have any ideas why its doing this?
Sent from my HTC Vision using XDA Premium App
You're not the only one who has experienced this problem. Check out this thread from the T-mobile forums where users have discusses the problem and a possible fix. Take a look at the pictures on the 4th post on page 4 by user vlado4 and see if your battery is the same. Apparently there is an issue with the battery shorting out or something of that nature. http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4 Hope this helps!
carquote said:
You're not the only one who has experienced this problem. Check out this thread from the T-mobile forums where users have discusses the problem and a possible fix. Take a look at the pictures on the 4th post on page 4 by user vlado4 and see if your battery is the same. Apparently there is an issue with the battery shorting out or something of that nature. http://forums.t-mobile.com/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4 Hope this helps!
Click to expand...
Click to collapse
I checked my battery and my battery does not have the metal strips, should i still attempt his fix even though i dont have that metal on metal contact? My battery looks like the guys GF's battery a little bit down on the 4th page, 4th post.
I would ditch setCPU to be honest. since CM settings now has overclocking built in, it just seems loony to call on another app to manage cpu frequencies.
there is a lot of misunderstanding regarding profiles with setCPU as well...
unless you are running the performance governor (which pegs the CPU frequency at its highest selection), "profiles" are already built in to your kernel.
it is the kernel's job to manage frequencies according to load... which is exactly what you are attempting to do with your screen off profile. if you're on ondemand, interactive, scary, smartass, or any other governor aside from performance, the governor will do the "screen off" profile for you automatically by scaling down frequency based on load.
setCPU is a good tool for roms without built-in CPU management, but for CM7, it's officially obsolete (unless you're overclocking heavily and need a temperature profile... your governor won't do that for you )
Thanks for all the info, i knew CM7 had the built in one but didnt know the kernel handled as much as it did... thanks! (and i pressed "thanks" by the way to everyone who replied ) Since you seem to have some kernel knowledge, whats the smartass and userspace governor?
Kevin001111 said:
Thanks for all the info, i knew CM7 had the built in one but didnt know the kernel handled as much as it did... thanks! (and i pressed "thanks" by the way to everyone who replied ) Since you seem to have some kernel knowledge, whats the smartass and userspace governor?
Click to expand...
Click to collapse
here's a quote from erasmux on smartass (the sleeping frequencies may differ depending on whose smartass you're using):
smartass governor – is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Of course, the frequencies are different than what he used, since we have better processors than the Hero.
Z
Click to expand...
Click to collapse
userspace is problematic in my experience. would not recommend using it. here is a good article explaining what it does (and why it's not the best idea for most of us): http://publib.boulder.ibm.com/infoc...topic=/liaai/cpufreq/TheUserspaceGovernor.htm
G2 randomly turns off
I have been having a similar issue with the phone just randomly turning off, I am not sure if this has to do with the handoff between wifi and network calling but this is a hunch. I do have a logcat with a few shutdowns.
carquote said:
You're not the only one who has experienced this problem. Check out this thread from the T-mobile forums where users have discusses the problem and a possible fix. Take a look at the pictures on the 4th post on page 4 by user vlado4 and see if your battery is the same. Apparently there is an issue with the battery shorting out or something of that nature. [cant post outside links] Hope this helps!
Click to expand...
Click to collapse
You think you could summarize what the fix is? The link doesn't work anymore. Thanks
j0lte0n said:
You think you could summarize what the fix is? The link doesn't work anymore. Thanks
Click to expand...
Click to collapse
Try this link instead: http://208.74.204.85/t5/T-Mobile-G2/G2-Turning-off-by-itself/td-p/513575/page/4
T-Mobile, in their infinite wisdom, completely trashed the old forums in favor of some new community/social neworking-esque BS. Everything that people had worked on, figured out, and shared was lost for good. After an uproar from the community they temporarily restored a read-only version.
That link should work for now, but T-Mobile stated that the archives would only be brought back for about a week. Tools.
I had this issue. Only with the leaked 2.3.3. I haven't had the issue with the new official 2.3.4. I had to remove the battery and reinsert it. rather annoying especially if I was driving.