Related
SetCPU. In my personal opinion, one of the best Android apps out there. It lets you overclock/underclock your phone. Here I will describe how to set it up for the Vibrant so you do not brick/crash your phone.
1. Uncheck/DO NOT Check Set on Boot (this will cause crashes in most phones if checked)
2. Set the CPU Governor type to "Conservative"
3. If you're using a kernel such as JAC's OC/UV(/VOODOO) set the MAX Clock speed at 1.2Ghz, also set the MINIMUM clock speed at 200MHz (not doing this could cause random crashes/reboots/freezes)
4. Don't underclock too low (as this could cause crashes), I recommend nothing below 750MHz (although it could *probably* run at 400MHz, no lower though!)
5. Don't blame the dev of your kernel or SetCPU's dev if you break your Vibrant, you shouldn't do something you know nothing about.
6. Set a warning up so if your Vibrant gets hotter than 115° Fahrenheit SetCPU will alert you. (125° Fahrenheit is when your Vibrant will start to get damaged.)
7. Always ask if this works on the ROM you have flashed before you try to use it on the ROM.
8. SetCPU is free for XDA members only.
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
That is all.
A couple of things:
1. It's been found that setting the minimum to 200 MHz is too low on some ROMs and can cause problems with some applications, like Pandora. Users have reported that setting the minimum to 400 MHz alleviates those problems.
2. SetCPU is and has been free for some time to XDA members. However, if you like the application, you should throw the dev some coins and buy it in the market or make a donation.
NikolaiT said:
SetCPU. In my personal opinion, one of the best Android apps out there. It lets you overclock/underclock your phone. Here I will describe how to set it up for the Vibrant so you do not brick/crash your phone.
1. Uncheck/DO NOT Check Set on Boot (this will casue crashes in most phones if checked)
2. Set the CPU Governor type to "Conservative"
3. If you're using a kernel such as JAC's OC/UV(/VOODOO) set the MAX Clock speed at 1.2Ghz, also set the MINIMUM clock speed at 200MHz (not doing this could cause random crashes/reboots/freezes)
4. Don't underclock too low (as this could cause crashes), I recommend nothing below 750MHz
5. Don't blame the dev of your kernel or SetCPU's dev if you break your Vibrant, you shouldn't do something you know nothing about.
6. Set a warning up so if your Vibrant gets hotter than 115° Fahrenheit SetCPU will alert you. (125° Fahrenheit is when your Vibrant will start to get damaged.)
7. Always ask if this works on the ROM you have flashed before you try to use it on the ROM.
8. SetCPU is not (and probably never will be) free, so DO NOT bug the dev for a free copy.
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
That is all.
Click to expand...
Click to collapse
I am interested in how you have determined this.
How legit are these instructions, im interested in this app. Since im running bionix 1.9.1 jacs oc/uv rom.
Sent from my SGH-T959 using XDA App
I agree with most of what the OP is saying, I've been using setcpu since my G1. I'm currently running Fusion 1.0 with JAC kernel. I have 200 min with 1200 max. No set on boot and no profiles. I'm not sure about the damage temp, I've ran the gps for an hour with the phone in direct sunlight and it hasnt gotten that high.
This is what works for me, as well as many other users, and the issues posted here have been reported by many users. Also to the person with JAC's OC/UV Kernel, this app is required. If it isn't used, you can experience random freezes/crashes/reboots.
opiomorph said:
A couple of things:
1. It's been found that setting the minimum to 200 MHz is too low on some ROMs and can cause problems with some applications, like Pandora. Users have reported that setting the minimum to 400 MHz alleviates those problems.
2. SetCPU is and has been free for some time to XDA members. However, if you like the application, you should throw the dev some coins and buy it in the market or make a donation.
Click to expand...
Click to collapse
Yes, this is true, but the only time time the vibrant will reach 200MHz (100MHz if SetCPU isn't used) is when the phone is idle.
Double post, apologies.
i have set on boot checked on bionix 1.9.1 with no problems. 200min,1200max, conservative.
Im running the bionix 1.9.1 with jacs oc/uv. I havent installed the set cpu app yet and my phone is running great. Im working on getting up the nerve to try it.
Sent from my SGH-T959 using XDA App
GreggoryD502 said:
Im running the bionix 1.9.1 with jacs oc/uv. I havent installed the set cpu app yet and my phone is running great. Im working on getting up the nerve to try it.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Do eet! The worst that will happen is that your CPU can't handle an overclock and you'll be stuck at 200/1000. Cross your fingers!
It is worth the money for the developer, for sure.
Also, can you post your source for the temperatures you listed? Seems kind of low for Fahrenheit. Especially since where I live those temps are just above room temperature sometimes
Ok. Just installed and set 1200.max 400 min. Will post latet let everyone know.if I notice a differnce. Phone does seem snappier, or could be.my imagination. Lol
Sent from my SGH-T959 using XDA App
Quick, possibly dumb question. Do I have to reset the settings if I turn my phone off and turn back on?
Sent from my SGH-T959 using XDA App
GreggoryD502 said:
Quick, possibly dumb question. Do I have to reset the settings if I turn my phone off and turn back on?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
not if you have 'set on boot' checked. but some people claim that setting can cause problems. however i've been running bionix 1.9.1 with set on boot checked since 1.9.1 came out with 0 problems. otherwise, yes, you have to reset it every time you reboot.
Thanks. Ill check set on boot and see what happens.
Sent from my SGH-T959 using XDA App
Be careful about "Set on Boot", it someone resets SetCPU and underclocks your phone to the point of crashing shortly after it boots. This is a pretty common issue but it doesn't happen to all users.
funeralthirst said:
not if you have 'set on boot' checked. but some people claim that setting can cause problems. however i've been running bionix 1.9.1 with set on boot checked since 1.9.1 came out with 0 problems. otherwise, yes, you have to reset it every time you reboot.
Click to expand...
Click to collapse
i dont have set on boot checked, and my settings are preserved on reboot
Ive been using set on boot for several days now, and no issues so far. To be honest I cant really tell any difference in the phones performance. But im not really pushing it either.
Sent from my SGH-T959 using XDA App
NikolaiT said:
9. This will NOT work on the Vibrant's Stock kernel, a new one must be flashed (such as JAC's OC/UV(/VOODOO) kernel or Kingklick's OC/UV Kernel)
.
Click to expand...
Click to collapse
This does work on stock vibrant kernel. I have it on JI6 stock except for Root and mods. The OP is correct that you cannot over clock on stock.
As a battery saver for JI6 possibly. Also I am currently using it as an attemped fix for my Gallery freeze, lockup/CPU hog issue.
Sent from my SGH-T959 Gallery freezing Vibrant using XDA App
hi all been a member for a long while from HTC 8525 days, just wanna say i love this site, saw that the app was free for members, but i love supporting you guys i bought the app anyway! thanks for all the hard work all of you put in... im sure we all appreciate it!
Hello there XDA I just switched to the Aria from the Captivate. I am new to Android modding, so please bear with me.
I like the phone, It doesnt bother me losing screen space. However it is a bit slow with the 600 MHZ processor.
So if there are some people kind enough to guide me to/through the following it would be appreciated.
1. I would like to overclock it a bit, maybe to 800.
2. General performance tweaks
3. Get rid of Att bloatware
4. Root ( z4root is not in the market anymore and ATT disables side loading.)
Sent from my HTC Liberty using XDA App
Everything u need is in the android Dev. Section for the aria its really simple. To find and to follow..I use cm6 rc2. It overclocks very nicely
Sent from my Liberty using XDA App
Hey Joshua, being new to the Aria as well (less than a month), I haven't looked into overclocking it... but I am running CM 6.1 RC 2, what do I need to do to start overclocking?
Install SetCPU to overclock. I wouldn't go over 825mhz as it starts getting unstable.
As for rooting, search for posts by user asiancuta. He did a really good write up that included a key point I didn't see anywhere else. It's titled NOOBZ: easy guide to rooting your aria.... Read all instructions, and make sure you understand it first.
To install cyanogenmod 6.1 rc2 do a search for That aria - she's so racy!
Sent from my Liberty using XDA App
Mike's Aria said:
Install SetCPU to overclock. I wouldn't go over 825mhz as it starts getting unstable.
Click to expand...
Click to collapse
In the other overclocking thread (or overcloking as the OP spelled it ) several people posted that they were running at 864... what type of instability is likely? Also, doesn't overclocking HAVE to have some sort of adverse effect? Like reduced reliability or an increased likelihood of hardware failure? If there are no adverse effects, why would HTC not set the CPU higher from the factory?
I want to try it, but I feel like I pushed the limits of my comfort zone just by rooting and installing CM...
911jason said:
In the other overclocking thread (or overcloking as the OP spelled it ) several people posted that they were running at 864... what type of instability is likely? Also, doesn't overclocking HAVE to have some sort of adverse effect? Like reduced reliability or an increased likelihood of hardware failure? If there are no adverse effects, why would HTC not set the CPU higher from the factory?
I want to try it, but I feel like I pushed the limits of my comfort zone just by rooting and installing CM...
Click to expand...
Click to collapse
I always lean on the side of caution when it comes to overclocking a phone. I don't want to fry the processor since I can't replace it as easily as one on a computer.
Processors are never set from the factory to run at their fastest.
Sent from my Liberty using XDA App
While it might seem odd since all these phones have the same hardware they don't all respond the same to overclocking. Some people can do 864. I can't even get my phone to do anything over 825 and even 825 gives me issues. I like to keep mine between 768-787. Over doing it can cause damage and shorten the life of the processor but keeping it around 800 is probably safe as long as you moniter temps. Heat is the real enemy here. Manufacturers are trying to balance cost, reliability, battery life. Our little phone use a smaller battery and so a lower clock speed keeps the phone running longer. And the aria is a mid range phone, they don't want it to be faster than the more expensive phones. Also Higher clock speeds will drain your battery faster. At 768 the phone is noticeably snappier and the battery drain over stock isn't even noticeable.
Huh. That's good to know, Callmearia. However I don't even know where to start on any of this. I've never 'flashed' a phone or anything like that before.
Sent from my HTC Liberty using XDA App
This is a really good guide explaining how to root your phone and install a custom recovery, Clockwork, with which you can flash ROMs, make backups, and a bunch of other stuff:
http://forum.xda-developers.com/showthread.php?t=788737
You will still not be able to sideload apps just by rooting though. You will need to flash a ROM in order to do that. Check out the Android Development section, it is all there.
L551 said:
Huh. That's good to know, Callmearia. However I don't even know where to start on any of this. I've never 'flashed' a phone or anything like that before.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
I think most people can hit 864 now using CM6.1 RC2. I think some tweaks were made to allow it. Before I was only hitting 825mhz or 844mhz when I ran in to stability problems... but now I have none. Or, it could be due to the fact it's colder here now.
Alright, so after some adb troubles with Ubuntu 10.10, I am now rooted, woo!
So now, where to go from here?
This worked flawlessly and easy. Less than 5 minutes
http://forum.xda-developers.com/showpost.php?p=7449486&postcount=1
EDIT : I see that you already got rooted.
You have two choices for Attn1's custom ROMS
Liberated or Cyanogenmod
http://forum.xda-developers.com/showthread.php?t=819715
http://forum.xda-developers.com/showthread.php?t=821642
Take in mind that CM has more customizable features, INCLUDING OVERCLOCKING. Liberated doesn't.
Place the .zip on your SD card. Enter clockworkmod recovery by holding down the volume down button after restarting phone. Wipe Data, Cache, Dalvik Cache. Go to install zip from Sdcard. Pick the file. It should install. wait, and reboot and continue.
Customize it to your liking. Download apps/widgets
Turn off unnecessary background items. (Auto Sync)
Decrease Brightness
Only use GSM networks
(these are battery saving tips....lots more)
http://forum.xda-developers.com/showthread.php?t=505419
That is the SetCPU for XDA members.
To install, go through ADB in the command line, or download FASTAPP Install from the Market and place the .apk on your sd card and install it from there.
kaschenberg said:
I think most people can hit 864 now using CM6.1 RC2. I think some tweaks were made to allow it. Before I was only hitting 825mhz or 844mhz when I ran in to stability problems... but now I have none. Or, it could be due to the fact it's colder here now.
Click to expand...
Click to collapse
That's probably true. I haven't tried going over 825 since way back with dumfuqs kernel.
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
L551 said:
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Make sure you install the google apps package.
Also, Not too sure.
I use windows. Works perfectly on there. try that
Yup I made sure to install that. Need my market.
I'll see if it works on windows later.
Sent from my Liberty using XDA App
L551 said:
Alrighty... did all that, now running cyanogenmod on my Aria! \o/
No more ATT bloatware.
I made sure to do a nandroid backup just in case.
Also overclocked to 768MHz. Phone seems a bit quicker.
Thanks guys
Any other tips?
Oh also adb stopped working again on Ubuntu >.< Anyone know how to fix that?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Try leaving the OC alone after the reflash.. It's defaulted to 864mhz and it works flawlessly for me.
It was default 600MHz for me.
EDIT: Holding down 1 to access voicemail no longer works, as there is no voicemail number in the options. What is it?
Sent from my Liberty using XDA App
L551 said:
It was default 600MHz for me.
EDIT: Holding down 1 to access voicemail no longer works, as there is no voicemail number in the options. What is it?
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Its different for every one. My VM is a local number. You can always just use your phone number.
I recently set my VM to go thru my Google Voice number now.
Sent from my Liberty using XDA App
Using my own number worked.
However, now my phone is freezing randomly, and causing the launcher to hang. (ADW and LauncherPro both do this)
It seems android.process.acore always takes alot of CPU time when it does this.
Hey guys whats the max overclock that the Aria can be set to? I had CM6 on mine and had the overclock widget from the market and the max that the sliders went to was 600... But I have Liberty FR008 on it now and i still have the overclock widget but the max that the sliders goes to now is 864... I tried overclocking to 864 but it froze and something went wrong so i had to flash a backup i made. My overclock options right now are 245, 400, 480, 600, 768, 787, 806, 825, 844, & 864... Has anyone tried to over clock the Aria past 600? and did you have any problems with it? Thanks for any help.
-Cpl. T. King
I dont think the cm6 kernal allows for over clocking. I have the latest liberated rom and overclocked to 806 which is the recomended max setting by the dev.
Sent from my HTC Liberty using XDA App
Use the search button. The safe zone is 806.
Sent from my HTC Liberty using XDA App
andrew.cambridge said:
I dont think the cm6 kernal allows for over clocking. I have the latest liberated rom and overclocked to 806 which is the recomended max setting by the dev.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
The CM 6.1 kernel most certainly does support over-clocking. The CM 6.1 kernel was used as the basis for the Liberated FR008 kernel.
Maybe I was thinking about 6.0. Whatever one I had, I could only over clock to 600.
Sent from my HTC Liberty using XDA App
6.0 didn't allow overclocking, 6.1.1 does though. I overclock my Aria to 806mHz and underclock it to the lowest setting when the phone's screen is off so I don't tire out the processor. 806mHz is really good, it puts the phone at the level of the G2 or the Shift 4G...and because I usually run Edge w/3G when downloading, WiFi if available, my battery is really good. Probably about 14 hours of normal (good) usage.
I wouldn't overclock it higher, you risk burning the processor out.
I'm OCd to 825 on-demand and the phone runs very nicely. 245 when screen off
825 is not recommended I don't think. 806 seems to be the sweet spot.
brswattt said:
825 is not recommended I don't think. 806 seems to be the sweet spot.
Click to expand...
Click to collapse
Says who? It's dependent on the quality of the processor. Some can do it, some can't.
kaschenberg said:
Says who? It's dependent on the quality of the processor. Some can do it, some can't.
Click to expand...
Click to collapse
Attn1 said he doesn't recommend overclocking over 806, because you might fry the cpu
Sent from my HTC Liberty using XDA App
I forgot attn1 was a engineer for HTC. 806mHz is the sweet spot, I've been running it for weeks OD with Screen off at 206 and it doesn't overheat & good battery life.
tribestros said:
I forgot attn1 was a engineer for HTC. 806mHz is the sweet spot, I've been running it for weeks OD with Screen off at 206 and it doesn't overheat & good battery life.
Click to expand...
Click to collapse
Suit yourself. Just saying 806 is the sweet spot for most people around here. I've gotten force closes and reboots at 825. We don't need your attitude
Then it seems like your particular phone can't handle 825. I suggest people try it on both. every phone is different. Just don't be stupid about it. When using the phone as a gps, under clock it. under clock when screen off. and over clock on demand and I'm fine on 825. never seen any issue.
"Suit yourself." I think that was the point of his post. His phone and usage of it OCd at 825 is good for him. He was just stating an answer to the OP. No reason to go around telling him he's wrong..
Anyways, not trying to start a OC war... because that would be ridiculous (-ly funny I might add).
As for myself, when I did OC my processor, 825 didn't effect my phone's performance, but it did make it extremely hot after a bit of use. So it's up to your phone and how you want to handle your phone. I don't really need the OC anymore though; I just stick with 600 (;
Sorry for the nooby question, but whats this even do? Besides making it faster I assume?
vicmora5 said:
Sorry for the nooby question, but whats this even do? Besides making it faster I assume?
Click to expand...
Click to collapse
That's basically all it's for. d:
You get more processing power.
brswattt said:
That's basically all it's for. d:
You get more processing power.
Click to expand...
Click to collapse
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Downsides are less battery life (may be a lot or not) and not going as fast as it would be if you were OCd. It may also heat up more.
vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Overclocking is not necessary at all. We just recently became able to overclock. If you are satisfied with the speed/fluidity of your phone, then there is no need to overclock. The downsides would be less battery life (cpu running faster), and if you push your phone too hard (overclock stupidly), you run the risk of burning out your cpu. your phone should not be getting hot.
vicmora5 said:
Thanks. Is it really necessary? What are the downsides of doing this. Sorry I'm just trying to learn /:
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
It's not necessary. It's pretty damn cool to make the little Aria have a processor as fast as the one in the G2 though.
I'm still more or less a noob to the whole android customization, even though I tried out a lot of different roms on my saphire (MT3G). I recently upgraded to th MyTouch 4G, and immediately found a root method to install a custom rom. I tried several different roms for this device as well over the, last few weeks, and found that the ICE GLACIER 1.1.6 runs the most stable, and closest to the original. So my question is this: I have also been looking into overclock kernels as of late only to find that all the ones I try with my rom are either incompatible or cause frequent freezes, crashes, or restarts. Is there a kernel out here I have missed that will run smoothly with my rom? I have already looked trough some of the forums here and tried both versions of the faux kernel, and all the rest I have seen that aren't CM specific. Anyone can point me in the right direction would be greatly appreciated.
Sent from Iced out Glacier (MT4G) v. 1.1.6
Gorilla's OC kernel that TeamSilence put in Ice-Glacier is a very strong and stable OC kernel. if I remember correctly that kernel will go up to 1708 or 1709 if you have SetCPU.
I am using set cpu, but even the kernel that comes with the rom freezes my phone up, or causes force closes and restarts out of the blue.
Sent from Iced out Glacier (MT4G) v. 1.1.6
powduh09 said:
I am using set cpu, but even the kernel that comes with the rom freezes my phone up, or causes force closes and restarts out of the blue.
Sent from Iced out Glacier (MT4G) v. 1.1.6
Click to expand...
Click to collapse
If you're OCing to 1.7GHz, that may not be the kernel's fault. Every CPU is different, some can't overclock as high as others. Here's a nifty thread on the subject.
Very true, just like the MT3G-Slide mine could go well into the 900's before it would lockup but my wife's can only hit 844 any higher and it locks
jdkoren said:
If you're OCing to 1.7GHz, that may not be the kernel's fault. Every CPU is different, some can't overclock as high as others. Here's a nifty thread on the subject.
Click to expand...
Click to collapse
Thanks for the info. I love my MT4G as is, so overclocking isn't really a big issue, after reading this article, I am begining to wander if it is even a good idea. I was only curious to find out the problem because I never had such troubles overclocking my saphire (MT3G)
Edit: have reduced settings to 1497600mhz. Going to play around a little bit and see what my best settings are. As of now, this settings have outlasted all others. Thanks to those who responded. And HAIL to the devs who spend their time creating all these roms, so noobs like myself can easily make their devices unique!¡!¡!¡!¡!
Sent from my HTC Glacier using XDA App
Try Faux's kernel with smartass gov. Set at default to 1.1ghz. He makes great kernels and is very active updating and making them better.
I've been flashing his kernels like crazy. As the famous tiger says......there grrrrrreat!
Sent from my HTC Glacier using XDA App
Vinsane said:
Try Faux's kernel with smartass gov. Set at default to 1.1ghz. He makes great kernels and is very active updating and making them better.
I've been flashing his kernels like crazy. As the famous tiger says......there grrrrrreat!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Does the kernel affect battery life given the same clock speed? What I mean is if I am using CM7 RC1 with whatever Kernel it came with... and I change to the Faux kernel and keep the same clock speed will I see diff. battery life?
Are there any kernels that are tuned for better battery life?
Thanks,
RA
Vinsane said:
Try Faux's kernel with smartass gov. Set at default to 1.1ghz. He makes great kernels and is very active updating and making them better.
I've been flashing his kernels like crazy. As the famous tiger says......there grrrrrreat!
Click to expand...
Click to collapse
I'm running on the kernel that came with Ice Glacier now, thanks to a hard crash around midnight last night. I've been set at 1497mhz since I restored. No freezes, acceptable battery temps, and blazing response time. Now I only wander if one of the kernels allow a little better fine tuning, because if I try to change this one it only has two more setting, one in the 1600s and then max, both of which cause my phone to go crazy...
Sent from my HTC Glacier using XDA App
radamo said:
Are there any kernels that are tuned for better battery life?
Click to expand...
Click to collapse
I don't know for certain, but I would think it matters more if the kernel is undervolted or not. Assuming the same usage patterns and CPU clock settings/profiles, the kernel that utilizes less voltage would preserve more battery, would it not? (Anyone with experience on the subject wanna chime in?)
jdkoren said:
If you're OCing to 1.7GHz, that may not be the kernel's fault. Every CPU is different, some can't overclock as high as others. Here's a nifty thread on the subject.
Click to expand...
Click to collapse
I would like to say thanks for your help on this, been set to 1497mhz for almost 24hrs now with no force closes freezes or out of the blue restarts
Sent from my HTC Glacier using XDA App
I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks
Try a different kernel.
Sent from my CM860
ishamm said:
I have moved from CM7 to Hombase 5.4, and found that setcpu no longer seems to do anything. on CM7 it worked as i had hoped, underclocking the phone when i was doing low intensity stuff like texting, and pushing it up to full power for videos etc. now it does nothing but tell me core temps, which are always high as its always running at 1Ghz.
Can anyone explain how to get it back to underclocking?
Many Thanks
Click to expand...
Click to collapse
This is a known issue with the OC faux kernel. I was running into the same problem with his enhanced stock kernel after using webtop. After reflashing the enhanced stock 0.2.0 it would still get stuck at max 1Ghz after using webtop, but a reboot would get the underclocking working again.
I only tried the webtop hack to see if I could get it working. I haven't gone back into it at all so I don't know if this is something that will reoccur. Although I will say that with my day to day use I have not run into any clocking issues since.
Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium
ishamm said:
Thanks, is there a page somewhere which details which kernels do what and which would work with my rom?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
This is the page for faux's kernels. As far as details, start reading and searching through that thread as well as the threads for any ROMS you are using. 99% of the time people will either have the same problem (and possible fix), the other 1% of the time they will identify a bug (i.e. maxed out CPU).
Keep in mind faux does have different kernels for Froyo, GB, and CM7.
For some reason even if I move the slider from 1300my to 1000, when I touch the screen with at least 3 fingers for a few seconds it pegs out at 1300. I read our cpu's are daisy chained so to speak
so the 2nd core kicks in when needed. I tried cpu tuner and it gives the option to powersave and only use one core or if you choose performance it will allow Both cores. Just might be setcpu isn't designed fully for our dual core setup.
thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks
ishamm said:
thanks for the link to kernels, but i cant find one for HomBase, or a Kernel only download on the homebase thread. i have the Version2, which has some blur, but only the 1.0Ghz clock kernel. where could i get the 1.3GHz download by itself, to see if that might help, as its the one CM7 had iirc
Thanks
Click to expand...
Click to collapse
Get the 1.3 from the faux thread that I linked to. They're in the very first post...
CM7 is the only ROM that has its own custom faux kernel. For all other ROMS just match the kernel to the build the ROM is based off of (Froyo or GB). If you're using V.2 of Homebase then use the GB one.
Update: Also, there are other kernels out there. I was only using faux's as an example since you were using CM7 and Homebase.
thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again
ishamm said:
thanks, ive now got the 1.3Ghz kernel installed successfuly, but it still seems like setcpu will not underclock. i dont know if its normal, but the "Scaling" option is greyed out, and i cant get access to the Advanced tab. is there something im doing wrong in setcpu itself?
thanks again
Click to expand...
Click to collapse
Lack of underclocking is a known issue with the latest OC kernel. I'm unclear whether it's actually a bug with the kernel or with setCPU not supporting dual core devices. But yeah, there's a problem with it right now. I'm on the stock enhanced, and other than the webtop issue I mentioned above, it works fine.
Scaling/advanced are not available, this is something that is determined by the kernel you are using not the app.
ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?
ishamm said:
ok so if i understand you right i would be best off using the stock enhanced kernel (for now), as it will underclock fine?
Click to expand...
Click to collapse
It's working perfectly for me, except after webtop use (which I don't normally use).
I'm still having the same issues regardless of weather I choose power save or performance it will not underclock, and those are the only governors I get the option of :s
Sent from my MB860 using xda premium