Related
Thats right, just loaded it up after rooting this bad boy and it is working just fine!
I am not responsible if you brick your device in the process.
UPDATE!
Ok so here is what is needed to run this badboy without problems.
Use only the conservative option (least problematic and no sleep comas)
I dont use the widget, i already know the speeds i set it at.
The settings stick even after a reboot, but when you click on the setcpu icon they revert back and you lose your settings. If that happens just go back and click on detect auto speeds and set up your speeds again.
Happy clocking!
what version? 2.0.1?
Were you able to overclock it past the 1ghz?
I rooted mine today and installed setCPU which worked flawlessly but I am not able to move the slider past 1ghz.
I loaded it on mine and while it *appears* to work, it doesn't seem to effect the clocks any.
heck just underclock your phones to save battery lol
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
jroid said:
I can only seem to clock mines to 800? hmm. I noticed when i first opened setcpu it was clocked to 384/245!! wow so low
edit: setting it to nexus one/snapdragon Qsd it clocks to 1ghz exact. not really sure it's working though
Click to expand...
Click to collapse
To see if it's working set it to underclock and then get into an adb shell and run the command: cat /proc/cpuinfo
It should display cpu data that includes the current clock speed.
I don't know if this helps but when I was in the Quadrant Standard app it has the system info. I hit it, scrolled down to cpu and it said
Current: 400 mhz, Max: 1000 mhz, Min: 100 mhz,
and I just checked it now and it said my current clock was 800 mhz, so i guess the cpu scales dynamically based on what the load is and what we are doing, thats a pretty great power saving feature.
Select 'Auto Detect'.
I believe you need an oc'd kernal to be able to move the slider past 1ghz.
Also, the dev has stated that it should be set to 'conservative', not 'ondemand'. 'Ondemand' was causing random shutdowns on the Galaxy S.
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Koblek said:
I installed SetCPU on my Vibrant too but removed it because it appears that it caused the phone to power off.
Does there need to be device specific support for a processor/device or does the auto-detect work on any processor?
Click to expand...
Click to collapse
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Has anyone noticed any significant battery conservation with this?
MINUS Stl said:
Look at the post before yours.......from me.
SetCPU needs to be set to 'conservative' on the Vibrant, not 'ondemand'. Also, per the dev in the "Random shutdowns?" thread: "You can "simulate" ondemand by changing freq step in Advanced to 100%"
Click to expand...
Click to collapse
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
i am still having problems with setcpu even on conservative mode. i have stopped using setcpu completely for now.
wbexpress said:
Hey, sorry if this sounds like a stupid question, but why does it max out at 800,000?
Click to expand...
Click to collapse
Auto detect...
Sent from my SGH-T959 using XDA App
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
mygti02 said:
i have this on my rooted vibrant. Max is 1000 and Min is 100. My battery life has doubled. I have not experienced any force closes, no slowness and no freezing. the phone is running super fast and smooth. Love it. After looking at the stats, it seems like the CPU uses 400 and 800 a lot.....thats probably where the extra battery life comes into play. 1000 is used when on full load.
Click to expand...
Click to collapse
What are your exact settings in profiles, advanced and overview?
any one running their phone at 1Ghz all the time?
+1, hah2110 please post your settings if they're working for you so a noob like me can learn some things!
Hey what would cause my java scores to drop using cf bench..I'm not sure what its measuring but it seems to have cut in half for no reason ..I think its at 1800 when it was like 4k before ..this isower than stock
Btw I'm on viper and helicopters #1 kernel ..with this same combo I was getting an overall score of 8k so I'm not sure what has happened ..and its not just the score I can feel it using the phone.
You got an app that is a cpu hog maybe, it could be a number of things. Reboot your phone and then clear out all your tasks using an app like Fast Reboot, then run a quadrant. Also an app like system monitor can show you what apps are eating up cpu and battery. Hope this helps.
I just noticed I got the same set up as you as far as kernel and ROM, its got to be an app in the background cause I get no lag whatsoever and im only over clocked at 1.5 with the screen on.
Edit again: maybe your over clocked too much, I read that pushing it too high can create lag also and be counter productive. With me 1.5/on demand seems to be the "sweet spot" for battery/performance.
phatmanxxl said:
You got an app that is a cpu hog maybe, it could be a number of things. Reboot your phone and then clear out all your tasks using an app like Fast Reboot, then run a quadrant. Also an app like system monitor can show you what apps are eating up cpu and battery. Hope this helps.
I just noticed I got the same set up as you as far as kernel and ROM, its got to be an app in the background cause I get no lag whatsoever and im only over clocked at 1.5 with the screen on.
Edit again: maybe your over clocked too much, I read that pushing it too high can create lag also and be counter productive. With me 1.5/on demand seems to be the "sweet spot" for battery/performance.
Click to expand...
Click to collapse
Thanks for the reply..let me explain exactly what happened.. I had the setup I told you for a few days and I was using setcpu to Oc..at that time I.was getting about 8 k cf bench score and the phone was fast besides the fact that setcpu was acting funny..then I set up the Oc daemon and set it to 1.8 just like I had it for setcpu. I really liked the daemon bc the phone was super fast..I then flashed an icon pack..at this point i was still getting high scores..I then tried flashing a theme and after that is.when my scores dropped significantly and i felt a little slowdown..so I.flashed back to just the ROM and kernel with no theme thinking that the theme was the issue. Unfortunately I'm getting the same low scores. The java score is very very low. I dont have many apps and i didn't even re install any apps besides the cf bench when I re benched it
Try viruses superwipe, that might help.
Will do
..should you wipe when flashing another kernel
If its just the kernel just wipe the cache and dalvik cache.
I did superwipe and my java score went up 1000 points..I'm at around
6500 ..right on par with the gs2..so its better but not as good as before..but I'm happy bc everything feels good..since your running same setup as me if u can do a cf bench and let me know what you score is appreciate it ..thanks for your help
I installed the webtop over hdmi mod on my Atrix and while testing it out, it got very warm in my hand. I opened the setcpu app and noticed that while overclocked to 1.3GHz, the CPU was running at 75C! I lowered it back down to the stock 1GHz and the temp slowly went down and settled at 63C.
It seems that while in webtop mode, the CPU is taxed at 100% all the time so I'm wondering if it's safe to stay overclocked when using webtop.
Everyone has different opinions of what is too hot around here.
IMO the cooler the better. IMI No Atrix should have a temp above 60c and I'm not even comfortable with above 50c either...
Sent from my MB860 using xda premium
I have experienced the same problem and worried that something may fry.... I have had mine overclocked at 1.45 using debian linux and all of a suddent he phone freezes and restarts.... Since it did it to me the second time I have kept my phone at 1Ghz... I am new at this so please don't beat me up too bad for being a noob... Just want to see if maybe undervolting it a little might help or hurt it?
Thanks in advance
Here are some tips I can offer
1.Try re-flashing your custom kernel and see if that fixes the web-top thing and over heating
Whenever the phone is plugged to the web-top it will naturally overheat so it's kinda expected remember now it's gotta work harder since its displaying on lap-dock or TV,but if you can cook an egg on it it might be too hot...lol
2.Set profile for temperature on setcpu so this way once you reach for example 100F your phone will clock down a little and so it might help the heat issue.You can set even more than one temp profile so this way when it reaches 96 it goes down a little then when it reaches 100 it will clock down a little more and such.
3.If that doesn't help,which in my situation it did.Flash a different kernel mayb it's just the one you're using that is causing funny stuff to happen.
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
I tried reflashing the kernel but it didn't change anything. I'm using Faux's 1.3GHz overclock kernel for Gingerbread (2.6.32.9). Is there something else I should be using?
sk8trix said:
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
Click to expand...
Click to collapse
Do what sktrix said in rest of his post.
I use the stopgap 1.0GHz kernel, and UV does lower temperatures. I would definitely try UV'ing a wee bit. You don't need to go crazy. I am using the following with great results for both temp and battery life:
-50
-50
-75
-75
-75
-100
-100
My setcpu profile clocks it back if I reach 60C, (I idle in the low to mid 30's). Under heavy load I reach around 52C max which is quite acceptable.
Now, granted I am not using Webtop, but the end result for UV should be the same. Lower temps and better battery life. You may also want to try just using 1.0GHz when on Webtop. The phone has more than enough power at this clock speed.
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
I know I'm straying from my correct forums here, however I have an LG Optimus 2X which like the Atrix, is a Tegra 2 CPU.
Our phones get VERY hot, I have had my CPU up to 86C before I decided to back off the stress test. CPUs are very good at handling high temperatures, and IMO you will see no ill effects from doing so, I am unsure of whether or not the Tegra 2 has thermal throttling/shut down, but in my experience they should be fine to around 80C.
The only issue I can forsee is the battery, batteries HATE high temperatures and it is awful for their life span, this is why your laptop batteries turn to crap after 1-2 years, even if low charge cycles, because they are always hot.
I would not be concerned about anything in the 70C realm, at all.
Alcapone263 said:
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
g2tegg said:
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
Click to expand...
Click to collapse
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
ericemir said:
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
Click to expand...
Click to collapse
It will still hang at 1.3ghz, though it's a known bug. I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick. Right now, the software that's out there is optimized to run on existing hardware w/o overclocks. I've run Shadowgun at 1.45ghz and didn't see any difference over the 1.0 enhanced.
Now, if we were trying to run games that were coded specifically or faster-paced chipsets then we'd need overclocking to catch up much like you would in the PC arena. That, however, is not happening in the cell phone market just yet.
treehumper said:
I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick.
Click to expand...
Click to collapse
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
cjrhoades said:
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
Bump.
Anyone?
cjrhoades said:
Bump.
Anyone?
Click to expand...
Click to collapse
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
CaelanT said:
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
Click to expand...
Click to collapse
I see... guess that explains why the phone doesn't really feel any faster when it's overclocked. I'll flash the 1GHz kernel then.
Thanks for the info.
Not sure if this is the same with phones but normally a CPU should stay at 40C idle and 50C load. Maximum would be 60C while benching or something.
If it goes above that I would definitely underclock/undervolt.
cjrhoades said:
what's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
also has other fixes besides overclocking you can go read them in the kernel threads
now hat we're unlocked lets overclock and undervolt and see if we can get 10k quadrant and a week out of the battery..lol
no but seriously how much do you guys think we can turn this thing up (overclock) and it be stable? (like its really needed..i cant get it to lag now as it is) once we get a kernel that is
blackbass595 said:
now hat we're unlocked lets overclock and undervolt and see if we can get 10k quadrant and a week out of the battery..lol
no but seriously how much do you guys think we can turn this thing up (overclock) and it be stable? (like its really needed..i cant get it to lag now as it is) once we get a kernel that is
Click to expand...
Click to collapse
1800 is a VERY good starting point.... I ran a kernel when I had the International variant and it was FAST!! I think it was called "Bullet" kernel...?
blackbass595 said:
now hat we're unlocked lets overclock and undervolt and see if we can get 10k quadrant and a week out of the battery..lol
no but seriously how much do you guys think we can turn this thing up (overclock) and it be stable? (like its really needed..i cant get it to lag now as it is) once we get a kernel that is
Click to expand...
Click to collapse
I was looking stuff up on that today. The highest I could find documented was 1900 on the cpu and 800 on the gpu.
For everyday usage, overclocking is useless, even for gaming. Undervolting can be beneficial, but from what I've seen, the latest processors get approximately the same battery life on stock voltage as they do undervolted.
imnuts said:
For everyday usage, overclocking is useless, even for gaming. Undervolting can be beneficial, but from what I've seen, the latest processors get approximately the same battery life on stock voltage as they do undervolted.
Click to expand...
Click to collapse
hey thats good to know...like i stated though. if there ever was a phone that needed over clock this one IS NOT it. i cant bog it down right now and believe me ive tried. someone out there might can but i cant.
imnuts said:
For everyday usage, overclocking is useless, even for gaming. Undervolting can be beneficial, but from what I've seen, the latest processors get approximately the same battery life on stock voltage as they do undervolted.
Click to expand...
Click to collapse
I just like to play around with different kernels but the kernel I was using def made the device snappier and I had some killer benchmarks! But you are right though! Custom kernels on this device is not really necessary...
I plan on building a custom kernel then, hopefully tomorrow night or possibly Saturday. I do have some plans to improve it, but nothing related to the CPU or GPU going faster, just having other stuff operate better and getting rid of anything not needed.
shojus said:
1800 is a VERY good starting point.... I ran a kernel when I had the International variant and it was FAST!! I think it was called "Bullet" kernel...?
Click to expand...
Click to collapse
I hope I don't get another lemon CPU... my TBolt's would only overclock to 1.4G, anything above and it locked up.
DaWolf850 said:
I hope I don't get another lemon CPU... my TBolt's would only overclock to 1.4G, anything above and it locked up.
Click to expand...
Click to collapse
That's better than me. I could run 1200 for weeks but at 1400 about every other day it would restart randomly.
IvanNCase said:
That's better than me. I could run 1200 for weeks but at 1400 about every other day it would restart randomly.
Click to expand...
Click to collapse
HA. My TBolt stayed stable at 1200, but ANYTHING higher than that and it would crap out on me.
I could run my bolt stable at 1700 all day. Kept it at 14 for a month no issues. Stayed at 13 the rest of the time. Course at 17 it was like it was running on a watch battery with the amount of time it would last. Lol
Eh I ran 1.6Ghz on my Thunderbolt 24/7 and with the 2750mah battery it lasted me days.
On a phone like that there was a significant improvement to the end user that justified the overclock. Now on the Note 2 I'd expect there to be very few who would want an overclock at all. I am part of the very few however. I play a lot of emulators on my phone and for N64 and Playstation I need all the raw CPU power I can get. Yep, even on this beast of a phone I still get some lag and stuttering on those emulators. The reason being is the same as PC gaming. AMD thinks that by adding more and more cores to their processors they can win the performance arena. Unfortunately they are wrong. Intel has the right idea, 4 cores is plenty now let's improve the efficiency and performance of those specific cores.
Same goes for our phones. Quad core is the most I'd ever want in my computers, anymore is just a waste. Now let's get better architecture for the processor to maximize clock-for-clock performance. And overclocking those cores helps it in apps that don't support more than one or two cores, because the baseline performance for each core is boosted.
So yeah, can't wait for a 1.8Ghz kernel
hello guys im new here and i want to ask how far... the CPU can Overclock without Risk... and i know that a safe O.C is 1.7GHz but use 1.89GHz is good? and how far the Phone is goiing to handle this and the life of the Phone? as i know overlock a Video CArd,CPU can make more short the life of the Device... so is the same with this phone? i know the The Qualcom CPU is 1.5GHz but the normal Speed is 1.7GHz... i dont know why HTC DOWN CLOCK THE CPU... if the CPU can Handle 1.72GHz
darkhelio said:
hello guys im new here and i want to ask how far... the CPU can Overclock without Risk... and i know that a safe O.C is 1.7GHz but use 1.89GHz is good? and how far the Phone is goiing to handle this and the life of the Phone? as i know overlock a Video CArd,CPU can make more short the life of the Device... so is the same with this phone? i know the The Qualcom CPU is 1.5GHz but the normal Speed is 1.7GHz... i dont know why HTC DOWN CLOCK THE CPU... if the CPU can Handle 1.72GHz
Click to expand...
Click to collapse
I'm not sure how far you can OC this device, but the reason they usually underclock slightly is twofold, heat and battery life. The higher the CPU clock speed, the more heat generated, and the lower the battery life.
codeprimate said:
I'm not sure how far you can OC this device, but the reason they usually underclock slightly is twofold, heat and battery life. The higher the CPU clock speed, the more heat generated, and the lower the battery life.
Click to expand...
Click to collapse
ok thanks bro
It is completely device dependent. Some people could be unstable at 1.7 while others could be fine at 1.89.
Sent from my HTC6435LVW using xda app-developers app
Ok veo thanks
Sent from my HTC Droid DNA using xda premium
What are you guys using to OC? Any app on the market or is there an HTC prefered app?
SetCPU is probably the most popular and to be 100% honest Overclocking is harmful to these devices there is a reason why HTC decided to place the clock speed at 1.5GHz... there isnt enough cooling provided to really push it past the limits but to each thier own I guess... Ive done it before and I really havent found it to increase the overall usage to my device... I had my old phone OC'd to 1890MHz and the only thing that changed was the benchmark numbers the normal day to day stuff still stayed the same like switching between apps and what not...
.torrented said:
SetCPU is probably the most popular and to be 100% honest Overclocking is harmful to these devices there is a reason why HTC decided to place the clock speed at 1.5GHz... there isnt enough cooling provided to really push it past the limits but to each thier own I guess... Ive done it before and I really havent found it to increase the overall usage to my device... I had my old phone OC'd to 1890MHz and the only thing that changed was the benchmark numbers the normal day to day stuff still stayed the same like switching between apps and what not...
Click to expand...
Click to collapse
I agree with that. I'm mostly interested in lowering the CPU speed for better battery life. Was curious of what everyone was using. I currently have the NoFrills CPU Control app. Although it is very basic, it does the trick. I've been running 1ghz max and battery life has greatly increased. If I feel the need for speed, I just set it back to 1.5ghz. As you said, I haven't found a need to go beyond that.
Same here, OCing increased benchmark scores but no noticeable difference when using it. And when it got hot (really fast when OCing and benchmarking) the thermal protection pulled the reins in and scores plummeted.
You just need to get rid of the bloat and unused services, or install a slimmed down rom.
Kernal to use for OC?
Im running [ROM] DNA Super Stock 2.06.605.1_710R v1.0 4/24/13
is there a kernal I can flash to OC my DNA? i tried to change my cpu Mhz but it wont budge
I want to use this rom: [17.01][DNA/X920D/E][ROM][GSM][GLOBAL] Virtuous DNA+ v.2.0.0 [Sense 4+ / OC / Stable]
--but it doesnt support VZW
thanks
Chenzo57 said:
Im running [ROM] DNA Super Stock 2.06.605.1_710R v1.0 4/24/13
is there a kernal I can flash to OC my DNA? i tried to change my cpu Mhz but it wont budge
I want to use this rom: [17.01][DNA/X920D/E][ROM][GSM][GLOBAL] Virtuous DNA+ v.2.0.0 [Sense 4+ / OC / Stable]
--but it doesnt support VZW
thanks
Click to expand...
Click to collapse
Beastmode Kernel
http://forum.xda-developers.com/showthread.php?t=2021714