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.
I'm running Bionix V 1.3.2 with the Immortality 2.1 kernel.
What I'm curious about is everyone's preferred overclocking app?
From what it looks like, it comes down to SetCPU, No-frills, Tegrak, or CPU tuner.
No frills advertises doing the overclocking without running in the background- which is appealing.
What are your thoughts?
Im not familiar with anything other then set cpu. I like it because I set up profiles for charging, screen off and temp. Ive used it for a while even when not overclocking, just for the screen off profile.
go with set CPU that's great the profiles really help save battery
Sent from my SGH-T959 using XDA Premium App
You can use Voltage Control to OC too...
Sent from my XDA app cuz I'm stalking your mom....
So it looks like there are a couple of categories the overclocking apps can be divided in to- those with profile management and without, and those for the SGS only.
Profile Management: SetCPU ($1.95), Tegrak ($1.95), CPU Tuner (Free)
Without: No Frills (Free), Voltage Control (Free/$3.84)
Both Tegrak and Voltage Control are specific to the SGS family- why would I want to buy a program that only works with specific phones when I can get a solution that will work with all my future phones?
I know SetCPU is the most commonly used solution, but I keep reading so many complaints in the forums. Does anyone have any experience with CPU tuner in comparison to the others? I'll at least tinker with it when I have time since I'll have more than 15 minutes to see if I like it.
Set cpu is horrible, atleast from my experience.
Constant screen of death, meaning after I lock phone,it won't turn on until reboot.
Instability. Lagged my phone even with oc only up to 1.2
Voltage control is what I prefer.
xriderx66 said:
Set cpu is horrible, atleast from my experience.
Constant screen of death, meaning after I lock phone,it won't turn on until reboot.
Instability. Lagged my phone even with oc only up to 1.2
Voltage control is what I prefer.
Click to expand...
Click to collapse
Sounds like your kernel is not compatible with setcpu =]
Some are not and votage control is preferred.
I'm on MIUI revamped Xx-2 with glitch 11 anf haven't had a problem with setcpu.
Vibrant+MIUI
Setcpu because in the "About? " it has says "Its over 9000! " plus its simple to use.
Sent from my SGS-t959 using XDA App
Well I'm using voltage control right now because its tailored to the hummingbird and I like the undervolt settings. Once you find the right voltages, your battery will be (more) amazing.
However, I've used setcpu since I've had my htc hero and it works wonders...at first when the galaxy s came out, there were conflicts and setcpu couldn't tune the hummingbird(atleast for the Epic 4g, the Galaxy S for Sprint), but that's since been worked on.
Setcpu is very straightforward. When you start it up, just tap autodetect speeds and it'll have a slider for min/max and yyou just slide it to the appropriate speeds. Then you use "governors" that dictate how the processor clocks...for example, on "conservative" the cpu scales up to the speed it needs to process what you're doing and slows down really fast when not in use. "Ondemand" is basically the same thing, but it scales high up and then lowers itself to the needed speed. "Performance" keeps your cpu clocked at its highest speed and keeps it there. Its good to run performance when you need to run benchmarks or do a lot of stuff on your phone at once, because it kills the battery faster (obviously)
Just try em out...setcpu is free on xda, just look for it in the apps section on android general I think or the g1 boards
Voltage control, be wary about, because if you mess with the ettings and don't know what you're doing, it'll corrupt your phone.
Sent from my SPH-D700 using XDA Premium App
I like voltage control too and pimp my CPU mainly because SetCpu hardly ever supports the kernels I use and when it does it gives me reboots
Thank you, I'll give Voltage Control a try. Do you have any 'safe' recommended voltage settings when using smartass, and then I'll see the limits of my phone from there?
No sorry idk about the vibrant, but it sould be able to handle the uv since we're both hummingbird
When you use VC, do it one clock speed at a time. The voltage slider moves in -25mV increments. Each processor is different. For example, my phone can handle 1.4ghz unervolted by -50mV but if I put it down one more notch, my phone freezes and its FC galore. So its good to have a backup.
If you're not turned away by the amount of time it takes to tune VC, then it'll be worth it. You just have to thoroughly test the phone each time you undervolt to make sure its stable before you set it as Boot. To test just scroll around and run acouple of benchmarks.
For example, when I started my UV, I started with 1.4ghz and worked my way down to 1.3, 1.2, 1.1, 1.0, .8 and .6 ghz. Slide it to 1400MHz and then slide the voltage bar one notch to the left to uv it by 25mV. Hit apply and then run smartbench, quadrant, neocore, linpack, w/e just to make sure your phone can handle it. If it can, move it one more notch and test it out. Rinse repeat for the rest
Setcpu is way more user friendly and does what its supposed to, but vc is for power users I guess
Sent from my SPH-D700 using XDA Premium App
If I do recall you could also change the voltages in setcpu. Ya know if your kernel supports it.
Sent from my SGS-t959 using XDA App
So I just wanted to see how normal this is, didn't see anybody else really mention anything about this. But my phone only really seems to want to use the 1566 MHz frequency range. It almost never uses any other frequency. Any body ever really notice this or is it not really that big of a deal?
https://www.dropbox.com/s/moqxq1agsriin54/2013-07-14 14.38.13.png
Edit: And for what its worth, I'm stock rooted. Left the governor on ondemand, had the I/O scheduler set to deadline for a while but set it back to CFQ with no changes(as expected). And my max frequency is set to 1890MHz, so it should go all the way up there, but there is almost no usage of those other frequencies, especially the higher ones which was weird since there was a while when I was trying to load it up to get to the higher frequencies.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Awizzle said:
So I just wanted to see how normal this is, didn't see anybody else really mention anything about this. But my phone only really seems to want to use the 1566 MHz frequency range. It almost never uses any other frequency. Any body ever really notice this or is it not really that big of a deal?
https://www.dropbox.com/s/moqxq1agsriin54/2013-07-14 14.38.13.png
Edit: And for what its worth, I'm stock rooted. Left the governor on ondemand, had the I/O scheduler set to deadline for a while but set it back to CFQ with no changes(as expected). And my max frequency is set to 1890MHz, so it should go all the way up there, but there is almost no usage of those other frequencies, especially the higher ones which was weird since there was a while when I was trying to load it up to get to the higher frequencies.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'm new to android, so my answer may not worth be much.. but what i've noticed in between switching roms and kernels and cpu apps, clean /dirty/whatever.. is that if you have been messing with cpu settings or voltages in any way then they will always have a small possibility of sticking even after you've deactivated or changed them back to default. the only way to get rid of these little bugs, at least for me, was to restore a stock/rooted/cwm nandroid backup or full wipe and full format under Mounts and Storage in recovery.. then flash back to the same rom i'm currently using.
basically.. the cpu can stick and you may need to reformat the system. seems to bethe case to me anyways.. hope it helps. if you can find a way to clear this issue without wiping data, please post the fix.
I just got my s7e yesterday. Found the guide on here how to root it. I did and it started having overheating issues so I downloaded kernel adiutor and put it on "on demand" as I saw posted somewhere else. This seems to work BETTER but my phone still keeps overheating frequently.
rkrajnov said:
I just got my s7e yesterday. Found the guide on here how to root it. I did and it started having overheating issues so I downloaded kernel adiutor and put it on "on demand" as I saw posted somewhere else. This seems to work BETTER but my phone still keeps overheating frequently.
Click to expand...
Click to collapse
My AT&T one was, too. I went back to stock. Faster and cooler (temp). Just gonna wait for a fix.
Yeah it doesn't matter what you set it too, it will overheat more then the stock.
my phone doesn't overheat at all. stock kernel uses interactive governor not ondemand. and you need to use an app that supports big.little CPU cores like kernel toolkit or ex kernel manager. set your big CPU cores to 2.1GHz and your little cores to 1.6k GHz. if you don't know about all this you guys probably shouldn't be rooting in the first place.
I was overheating also on pb6 firmware. Flashed pb8 and re-rooted, used kernel toolkit to set interactive and cpu cores to there min 300 something and 1500 for small and 2100 for large. Then flashed tekx. All is good now. Battery life is nowhere close to stock still.
xVermicide said:
my phone doesn't overheat at all. stock kernel uses interactive governor not ondemand. and you need to use an app that supports big.little CPU cores like kernel toolkit or ex kernel manager. set your big CPU cores to 2.1GHz and your little cores to 1.6k GHz. if you don't know about all this you guys probably shouldn't be rooting in the first place.
Click to expand...
Click to collapse
MegaNoob said:
I was overheating also on pb6 firmware. Flashed pb8 and re-rooted, used kernel toolkit to set interactive and cpu cores to there min 300 something and 1500 for small and 2100 for large. Then flashed tekx. All is good now. Battery life is nowhere close to stock still.
Click to expand...
Click to collapse
This is with using EX Kernel and big.little set to interactive. There is a problem with WiFi and some gaming that will heat this phone up hotter than hell itself.
CaptainMorgan said:
This is with using EX Kernel and big.little set to interactive. There is a problem with WiFi and some gaming that will heat this phone up hotter than hell itself.
Click to expand...
Click to collapse
And what firmware are you on? Did you also try flashing tekx? My phone doesn't heat up at all and WiFi is fine. Using pd8 and tekx. I had overheating but it's gone after a full wipe and flashing pd8 prior too rooting. It sounds like you just need to try again. I had problems also, it took a few tries.
If you use your phone for gaming you will see how much the phone heats up. If your using it from normal non heavy things it will be fine.
Well after switching to ex kernel, using TekX ROM, greenify, and L Speed, my phone is running almost perfect with great battery life.
rkrajnov said:
Well after switching to ex kernel, using TekX ROM, greenify, and L Speed, my phone is running almost perfect with great battery life.
Click to expand...
Click to collapse
Hello,
What do you mean by ex kernel?
umaro said:
Hello,
What do you mean by ex kernel?
Click to expand...
Click to collapse
He means the app, EX kernel manager.
umaro said:
Hello,
What do you mean by ex kernel?
Click to expand...
Click to collapse
Ex Kernel is an app that you can get from the play store.
https://play.google.com/store/apps/details?id=flar2.exkernelmanager&hl=en
xVermicide said:
my phone doesn't overheat at all. stock kernel uses interactive governor not ondemand. and you need to use an app that supports big.little CPU cores like kernel toolkit or ex kernel manager. set your big CPU cores to 2.1GHz and your little cores to 1.6k GHz. if you don't know about all this you guys probably shouldn't be rooting in the first place.
Click to expand...
Click to collapse
That's a ****ty response........remember when you were a noob? There was a lot you didn't know....don't bash people on the forum for trying or questioning what to do. You're a senior member. You probably should act like it and give the proper advice rather than saying one "shouldn't be rooting in the first place" I need to wear a condom just reading your post because of you being a **** on the thread.
...and there is slight heating, and major overheating when playing heavy games like dead effect 2 when you root. Even after the scripts and kernel tweaks. It's the engboot. Likes to be warm I guess
It's the trade off for now if we want root..
Sent from my SM-G935T using Tapatalk