Related
Hello all!
Just upgraded my wife from the MyTouch 3G Slide to the G2 as she has to have a keyboard and we were on our 5th replacement Slide. So, as she is not the geek that I am, she will not be constantly flashing new ROMs and such. However, I am going to at least install the latest CM and I am looking for kernel suggestions. I already have root, s-off, new hboot, and all that, I'm just waiting for CM7 to finish downloading.
I started using Android with the G1 and constantly updating Radios, as well as ROMs and I currently use a Samsung Vibrant running a TeamWhiskey ROM. It's stable as anything, I like the theme, and CM7 still has some broken stuff on the Vibrant. I'm glad to see that Eugene recently picked up a G2 as he made some bad ass kernels and ROMs for the Vibrant.
So, let's here those kernel recommendations and why you recommend them.
Thanks!
Well am currently using mexdroidmod and their kernel is pretty awesome because its fast and stable. My best advice is to test the diffrent kernel and read through the tread, see what people say about it. All the kernels I have tried are all awesome so you should try them
Sent from my HTC Vision using XDA Premium App
pershoot's kernel. great batt life and OCing
Umaro's kernel has been rock solid for me and has tons of features as well. You can OC all the way to 1.9 Ghz if you so please and it has smartass.
well considering your wife isn't much of a techie.. i say you should go with pershoots kernel because he's always releasing updates and i've never had a problem with any of them. the battery life is excellent if you use the right radio (.17 and .30 have been good to me), but you need to experiment with this though. the phone runs beautifully, just make sure you use superwipe+ to format/wipe so you don't end up with gps issues like many people have had, good luck!
I've run umaro, eugene, pershoot, flippy, pyro, etc etc... aaand I've decided that the provided kernel is pretty much good to go. yeah, there are some little trinkety things with a few of the above kernels that the standard CM7 kernel doesn't support... but honestly, they're worthless to a user who just wants to turn the phone on and have it work.
set her up with the stock kernel @ 245-1017 (I haven't found a reason yet to ditch the ondemand governor, it seems to work best with CM7) and a vanilla gingerbread launcher and she'll be blown away.. that's my $.02
Like said above, CM kernel is great. I've tried most or even all available kernels for CM and finaly decided to stick with original one. It's stable and supports OC (up to 1.5GHz) "out of box", so really, I see no single reason to use the other ones.
Sent from my HTC Vision using XDA App
AllWin said:
Like said above, CM kernel is great. I've tried most or even all available kernels for CM and finaly decided to stick with original one. It's stable and supports OC (up to 1.5GHz) "out of box", so really, I see no single reason to use the other ones.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I'm also thinking about changing the kernal, but only for smartass. Does smartass offer that much of an increase on battery life or anything else? Also, when you OC, do you use SetCPU or just CyanogenMod Settings?
slapshot30 said:
I'm also thinking about changing the kernal, but only for smartass. Does smartass offer that much of an increase on battery life or anything else? Also, when you OC, do you use SetCPU or just CyanogenMod Settings?
Click to expand...
Click to collapse
not at all pooping on any of the guys who swear by smartass/other governors, but the change in battery life is almost unnoticable for me.. the change in performance however can be pretty apparent.
here's my problem with "battery saving" governors:
in order to save battery, these governors are supposed to be more intelligent about which frequencies they select once a task is called... well, that's all well and dandy, but the problem is that the majority of battery-hogging apps (ie streaming music/video, gaming, browsing for a long time, being on the phone, etc) are still going to be battery hogs with or without a fancy governor. the governor isn't capable of making an app that needs a lot of processing power run well at a lower frequency, it can only try to be more selective about which frequencies it uses in order to attempt to save battery life.
additionally, most people use their phones like this: phone is idle (ie screen off), and a call arrives. call ends, phone is back to idle. texting a few people, back to idle. playing a game for 15 minutes, back to idle.
is it really logical to assume that these short bursts of activity are going to benefit at all from a fancy shmancy governor? I doubt it.
I still swear by ondemand or interactive (both work well for me) thru built-in settings if possible (ie cyanogen performance settings). second choice would be setcpu with no profiles (unless you're overclocking heavily, then you should at least have a temp warning profile). at this point, screen-off profiles don't do a damn bit of good, because pretty much every kernel we have for the vision is going to scale down during inactivity.
hello xda
this is one of my first posts, and beacuse of that, i am not permitted to post in the development section af the G2/desire z forum.
i have a little problem on my desire z running virtuous unity 2.35.
i use setcpu to overclock my phone to 1.7 Ghz, but after a while it automatically underclocks to 1.2 Ghz.. does anyone know why?
Thanks in advance
nicolaibaun said:
hello xda
this is one of my first posts, and beacuse of that, i am not permitted to post in the development section af the G2/desire z forum.
i have a little problem on my desire z running virtuous unity 2.35.
i use setcpu to overclock my phone to 1.7 Ghz, but after a while it automatically underclocks to 1.2 Ghz.. does anyone know why?
Thanks in advance
Click to expand...
Click to collapse
set cpu only overclocks to 1.7ghz when you actually need it, like when you are running graphics heavy apps or you are multitasking alot. it underclocks to 1.2ghz at times because you dont need 1.7ghz and only need 1.2ghz, this also saves battery life. if you want it to run at 1.7ghz all the time you need to set your governer to preformance. hope this helps
You shouldn't be using SetCPU if you are on Unity. There is already an OC interface built-in to the ROM, and it works better than SetCPU.
From the Virtuous website:
Virtuous. overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
But as evilcuber already mentioned, CPU clocking down when not needed is normal. The OC you are setting is a MAXIMUM, not a MINIMUM. You set how high it can go, but that doesn't affect how the CPU can clock up and down below that upper limit. If you want, you can set the minimum clock speed higher (or as evilcuber mentions, use a different governor), so its running at 1.7 GHz all the time . But you are just wasting battery life when its not needed. You might see some slight performance increase by running at max clock speed all the time, as it avoids any delays in CPU speed stepping. But the battery trade-off is probably not worth it.
Think of it as your car's engine revving at maximum RPM all the time, regardless of what speed you are actually moving at, or even when your car is parked. It makes more sense to just rev the engine up or down when the speed is needed. Not a perfect analogy, I know. But you see what I'm getting at?
also if u want a gui, u can download the virtuous overclock app
ohh i may not have expressed my self good enough.. i know about how the governors works (at least some of them), and the problem is that, i choose 1.7 Ghz, and quit the app, and then when i get back, the clock is adjusted back to 1.2 Ghz. maybe i should just uninstall setcpu, and let the daemon do the work?
evilcuber said:
also if u want a gui, u can download the virtuous overclock app
Click to expand...
Click to collapse
Ah, I just upgraded to Unity 2.35 today, and noticed the OC GUI is no longer packed in. Just find the file by using the search function in the Unity thread, to install the GUI.
nicolaibaun said:
hello xda
this is one of my first posts, and beacuse of that, i am not permitted to post in the development section af the G2/desire z
Click to expand...
Click to collapse
FYI you don't post questions in the dev section, you post them in Q&A which means questions and answers
Sent from my HTC Vision using XDA Premium App
nicolaibaun said:
ohh i may not have expressed my self good enough.. i know about how the governors works (at least some of them), and the problem is that, i choose 1.7 Ghz, and quit the app, and then when i get back, the clock is adjusted back to 1.2 Ghz. maybe i should just uninstall setcpu, and let the daemon do the work?
Click to expand...
Click to collapse
But which governor?
I would uninstall SetCPU. As I already said, the Virtuous team does not recommend it. It doesn't perform nearly as quickly as the built in daemon. Install the GUI app, if you want to tweak the daemon settings. If the dev of a ROM is as clear about recommended something as they are with the daemon (vs. SetCPU), its a good idea to follow their advice.
Got the same problem with setcpu.
You should try what they say above.
I run unity 2.37 : use virtuous OC gui(virtuous overclock controller) with temp+CPU widget to monitor your speed, temps, mem, etc.
With the new unity kernel you can OC up to 2.0 ghz
solid advice
redpoint73 said:
You shouldn't be using SetCPU if you are on Unity. There is already an OC interface built-in to the ROM, and it works better than SetCPU.
From the Virtuous website:
Virtuous. overclocking daemon will automatically be disabled if an overclocking tools (such as SetCPU or CPU Tuner) is installed. Installing these tools is not advised, as the virtuous_oc daemon responds far more rapidly to screen state changes than any Android (Java) application.
But as evilcuber already mentioned, CPU clocking down when not needed is normal. The OC you are setting is a MAXIMUM, not a MINIMUM. You set how high it can go, but that doesn't affect how the CPU can clock up and down below that upper limit. If you want, you can set the minimum clock speed higher (or as evilcuber mentions, use a different governor), so its running at 1.7 GHz all the time . But you are just wasting battery life when its not needed. You might see some slight performance increase by running at max clock speed all the time, as it avoids any delays in CPU speed stepping. But the battery trade-off is probably not worth it.
Think of it as your car's engine revving at maximum RPM all the time, regardless of what speed you are actually moving at, or even when your car is parked. It makes more sense to just rev the engine up or down when the speed is needed. Not a perfect analogy, I know. But you see what I'm getting at?
Click to expand...
Click to collapse
wow thank you for this enlightening advice, you have answered all my questions i had in my mind about overclocking my android
I have the virtuous rom version 2.39.0 just 2 days ago on my mytouch 4g, i'm new to rooting & roms & still happy that i took this risk and rooted successfully i was contemplating on pushing my luck a bit further by overclocking it with setcpu but thanks to you and other experienced members in this thread i now understand a lot that i didnt know
jamgirl said:
wow thank you for this enlightening advice, you have answered all my questions i had in my mind about overclocking my android
I have the virtuous rom version 2.39.0 just 2 days ago on my mytouch 4g, i'm new to rooting & roms & still happy that i took this risk and rooted successfully i was contemplating on pushing my luck a bit further by overclocking it with setcpu but thanks to you and other experienced members in this thread i now understand a lot that i didnt know
Click to expand...
Click to collapse
You're very welcome. Be sure to click the "Thanks" button, if my post helped you!
Also, on Sept. 12, the Virtuous team recommended OC/UV Beater as a interface for overclocking the Virtuous OC Daemon. I've been using this recently, and it works great.
http://forum.xda-developers.com/showthread.php?t=1207546
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
I've done a bit of reading and don't seem to be able to identify a kernel that works fully with webtops.
There are 2 current issues:
1. Status bar on webtops do not work with popular kernels
2. CPU speed locks at 1ghz when in webtop
I know for a fact this is an issue with Faux's kernels and it is typically there on Clemsyn's kernels. Are there any kernels out right now that may provide some of the performance and battery life tweaks of Faux's codes w/ a working webtop?
I recently purchased the $50 lapdock and am interested in trying to get everything working. I may even give up Faux kernels to go back to stock =(
I have a stock ROM with Clemsyn's timing tweaked kernel. I have tried webtop with the multimedia dock (not the lapdock...backordered like most others), and I've noticed that both cores peg at the 1.4 GHz max and the phone could heat a small room. Like others have reported, after I quit webtop, the processors are still pegged at 1.4GHz, and almost 100% utilization. I get poor performance after that until I reboot the phone. Not very nice.
The main reason I wanted to go with an alternate kernel is more for UC and UV. Right now I have Battery Saver set to the max, which seems to UC me to 608 MHz most of the time and I don't really see any performance issues. I know stock doesn't give OC and I don't even think it does UV. Don't know about UC.
I haven't paid attention to the status bar issue...I've only used webtop so far just to check it out...but with the lapdock I plan to use it more (coupled with the full Ubuntu mod).
clenynsns uv better than any other lkernal
Sent from my MB860 using xda premium
You can use kholk's kernel, and i think it works perfectly with webtop
Sent from my MB860 using xda premium
Edit - Nevermind
Sent from my MB860 using Tapatalk
On my lapdock/webtop now and can confirm that everything appears to be working well with Kholk's kernel.
After seeing the suggestion here, I tried it and am both speedy and stable using the 1.5 GHz version with everything undervolted -75. Got some freezes in Webtop if I opened more than a few Firefox tabs when I UVed -100
Glad this kernel is webtop compatible. It helps a pretty good bit. Definitely makes being without MIUI/CM7 more tolerable.
never mind. I am dumb.
The latest faux kernel also works with webtop now.
After the release of Clemsyn's 1.6 GHz Kernel for CM7 based ROMs last night, I immediately switched to it just to see.
But before that I was running Faux123 1.3 GHz.
I'm keeping the Clemsyn kernel for now, simply because I can. My phone can run it with little difficulty thus far and I have a profile to lower the max freq when the CPU gets to a certain temperature. I think I went with about 65 Celsisus.
Before I switched back to CM7 (or rather Neutrino) I was using Wet Dream. I OCed to 1.45 then in attempt to compensate for only half decent webtop performance.
But now I really only do it because I can. Whenever possible, my phone is on the lapdock since I like to HDMI mirror. Battery is not a concern since the lapdock charges the phone and I pretty much always keep the lapdock charger on hand in my bag.
I just thought it would be an interesting subject for the community to discuss as I'm sure it's something that a number of us haven't even thought of and I bet a good number of us fall into the because I can or bragging rights category.
Specific instances of problems OCing helped with in x app or y app might make someone else want to OC whereas someone who doesn't OC might persuade a user like myself to drop it for amazing battery ETC.
Sent from my MB860 using Tapatalk
Why I DO OC.
Right now I have my Atrix OC'ed at 1.45. I'm currently running Alien ROM Build #4.
The CPU has never gotten past ~55ยบ C.
I also have 2 profiles set
1 for Screen off - 800 MHz max.
1 for Battery< 10% -216 MHz max.
This paired with Alien ROM and LP has left me with a buttery smooth experience.
Is the 1.6 OC kernel worth giving a shot? Or does it make the CPU run excessively hot?
EDIT: I didn't really address battery life. I don't notice a huge decrease in battery life, I'm a pretty heavy user- SMS, Web, Video streaming, Facebook, Twitter. Over all OC'ing is definitely worth it to me.
I like to keep mine overclocked because it seems snapier. I use faux 1.45 and its great. Ive noticed clem's likes to make my phone very hot when running video or games and has actually shut my phone down due to heat. If I run clems I like to drop the overclock with setcpu to around 1.3 so it doesnt shut down but seems to get way hotter than faux's. Anything over 1.5 is just going to cause damage to peoples phones and IMO it should not be used so lightly.
I'm OC'd to 1.45ghz I do it for performance and those random times I need to benchmark I want to try 1.5-6 but I can't seem to get them to boot with the ICS mod2 cm7 so till cm9 or neutrino ill just float about with what I have
Sent from my Atrix-4G, stock 2.3.4 (rooted)
No need for 1.6 IMO.
1.3 is plenty for the Atrix. Even Faux 1.0 is fine. Its a phone, not a PC.
Sent from my HTC Inspire 4G using XDA App
I dunno...my webtop configuration may want to take exception to that statement
troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
+ 1
Sent from my Atrix 4G using Tapatalk
i honestly haven't been able to really tell a difference between 1.0 and 1.3GHz in most of my applications. it definitely doesn't help with system slowdown due to live wallpapers, which is a disappointment.
troycarpenter said:
I dunno...my webtop configuration may want to take exception to that statement
Click to expand...
Click to collapse
Haha, I was in that boat before I switched to HDMI mirroring coupled with VNC or Splashtop (when applicable) from experience, I can tell why Webtop users want OC. You can turn your phone into such a useful computer, and then it falls flat on its face because the inner-workings aren't streamlined. The extra power DOES help in that situation.
But in my actual experience, I haven't seen many realworld benefits past 1.2.
Especially since 1.6 kept eventually shutting down on me after about an hour (assuming there is the same issue as in Clemsyn 1.5, setting your max to a lower frequency than 1.6 won't stick so my temperature profile wouldn't actually work)
My "because I can" mindset is going to leave me stuck on 1.45 though most likely. I keep it maxed at 1.2(or is it 1.1? I'm not using the kernel right now) and then have a profile to ramp it up to 1.45 when it's on the charger (aka my lapdock)
I don't think it is quite the same for Blur based ROMs, but on CM7 1.0 seems perfectly adequate for the Atrix. Even at it's stock speed, it is snappy.
Sent from my MB860 using Tapatalk
I dont overclock. I used to be at 1.3ghz, but I didnt see a big enough difference to keep it. At least on CM7, the Atrix is plenty fast on stock speed.
I overclock, but I wait for thoroughly tested kernels before doing so. Right now I'm with faux's v023r @ 1.3 Ghz. I'll try Clemsyn's after its second or third "redesign" or bugfix.
I stick to optimal battery life kernels rather than performance (faux 123 0.2.3 being the one I'm currently on and most likely will be for the foreseeable future)
Also I can't imagine performance possibly getting any quicker or running programs any faster than they already are on the atrix.
Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.
Atrix_Owner said:
Honestly, I never understood why people oc their phone, especially the Atrix. I mean the phone is already fast being that it is 1Ghz dual core. Plus from what I have seen, the Atrix overheats like crazy with the stock frequency so why would you want to increase that even more, so it explodes? I use my phone to mostly play 3D games and I have never encountered any lag or low fps whenever I play games.
Click to expand...
Click to collapse
Quote for truth
The Atrix is plenty fast already. I can understand if you OC a HTC Magic, or a Hero; but there's no real need to do so on the Atrix.
Idk I see a difference on any launcher when I flip through pages and through apps. 1.3 or 1.45. But I def notice the difference in snappyness.
Sent from my MB860 using xda premium
95% of the time I overclock I do it for getting awesome benchmark scores that I can admire. 5% of the time I do it when playing 3D games like Fruit Ninja, It seems a lot smoother to me. But I hardly ever do it because it sucks the battery down so fast, so usually I'm at 1ghz. Also it's just kind of cool to see the the potential the phone has when overclocking.
i used faux's kernel to overclock to 1.3 for a few months but i didnt really see any difference except when i run quadrant or how my phone got hotter than stock when under load. another thing that annoyed me with faux's kernel was constantly losing widgets on reboot. i use two batteries so i reboot pretty often.
I used faux 23r 1.4GHz with setCPU profiles.
Profiles clamped speed to 1ghz at cpu temp of 50degc and 800mhz at 60degc.
Most noticeable difference was in k9 mail, indexing and searching were slightly improved.
I ran it so I would get a short boost if the cpu was cold.
Matthew
Sent from my MB860 using XDA App
Hey
On my old and feeble Hero I had to OC, if I wanted it to run fine, however I never felt the need to OC my Atrix. it has so much juice in it without OC, making it useless to squeeze the battery for the extra 0.2-0.5 GHz. Moreover, since we have no real ICS, our CPU runs freely and waste energy for nothing, so OC it will just make it run ever faster for nothing (In Hebrew there is a saying- running full throttle on neutral ).
I used to run Faux123 1.0Ghz kernel just to UV the device, but since I flashed weekly 6 I use the stock kernel, and it runs great, no overheating, and extremely stable (What cannot be said on UV kernels...)
The only time i oc is when using webtop, that extra speed makes a difference. The rest of the its running at 1ghz and seems plenty
Sent from my MB860 using xda premium