• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [KERNEL]SpeedDemon V5.6 (Performance & Battery Improvements) - MIUI Kernel

I'll look into being able to boot into Ubuntu as feature for V6.0, but as for right now, no.
~~~
Read the whole first post it tells you how to.


I have a question, basically everytime I restart my phone I have to constantly keep going to setcpu to change the governor and Max to 1.4ghz. I have the set to boot option checked on but it never goes to that during a restart. Is there a specific setting in the phone to do this as opposed to using a seperate app to change the governor and OC speed?
 
Unfortunately only CM7 has a settings menu for clock speed and governor, MIUI don't. Reinstall setcpu and see if it works then or try Nofrills.
 
May i ask, whats the absolute best overclock? how to i add voltages, i have no frills and incredicontrol aswell. i would like 2ghz but it becomes laggy and unresponsive at times. thanks.
 
Well if you can't deep sleep, you can tell with the app cpu spy, check to see if there's any apps that's keeping your phone awake. You can also try recalibrating your battery if you haven't already.
~~~
There isn't really any overall best overclock, there's just higher frequencies, as they get higher, in terms, they get more "powerful"; but, the higher the frequency the more unstable(random reboots) your phone gets. Most users say that they have more frequent reboots at 1.6Ghz and up, but everyone's phone is different so others might be able to handle 1.6Ghz and up; also, the higher the frequency, the more power/battery it uses. If you really want to overclock, you can start at 1.1Ghz, 1.2Ghz, and 1.3Ghz, then get higher(or lower) if you want; the ultimate goal you will try to achieve is to have a somewhat equal balance of performance and battery life. You can even try underclocking, going lower than 1.0Ghz as your as maximum; going lower will take away from performance, but also gaining battery life, picking a good governor helps a lot with performance and battery life. I had explained voltages(incredicontrol) to a different user, on page 7.
 
I followed a lot of your recommendations, and set undervolting, and even set max cpu to 650 (or whatever the exact amount is).

I set min to 61 mhz, and the phone functions well enough. I just know that before I could deep sleep, now with this kernel I can't, and battery life doesn't appear to be as good as miui stock kernel. I'm willing to test out any other settings though. I use smartassv2 and sio.
 
Wow, you've made a lot of fixes and updates since the last version. I can't wait to try out the new one! How's performance compared to the last version?
 
FroyoShark, performance should be better now, more that before.
~~~
Just to let you know, you cant deep sleep when charging or when data is running, or when WiFi, GPS, or Bluetooth is on. You can try using the built in app killer, it kills all those unnecessary apps that keep your phone awake. Task killers is not good to use, since it is a app itself and plus it sometimes kill the wrong apps, but the built in one for MIUI is perfect. You probably have apps keeping your phone awake. You can also try a different governor to see if it works, though I tested smartassV2 and it is able to Deep Sleep. If your going to underclock that low, with a low min, I would recommend using smoothass, smartassV2 does lag when waking up, and does lag in general when it comes to underclocking that low; because smartassV2 will go to your lowest min, while smoothass does go to the frequency four steps ahead of your min frequency.

I Just tested deep sleep; I reseted timers for cpu spy, went back to launcer screen, use app killer(hold home button and then click the app killer button); I then turned off my phone right away, gave it about 45 seconds with screen off, turned it back on, checked cpu spy, and cpu spy tells me I have 20 seconds at 576Mhz, 10 seconds at 245Mhz, and 32 seconds in Deep Sleep. The 20 seconds at 576Mhz is the time I took to go launcher and then used app killer, basically the time before I turned off the screen. 245Mhz is the governors ramping down the clock speed as the phone goes idle; then Deep Sleep kicked in.
 
What's the governor that has the best battery life without sacrificing performance? I always went with smartassv2 but there are so many more in this version so I thought I'd ask.
 
FroyoShark, performance should be better now, more that before.
~~~
Just to let you know, you cant deep sleep when charging or when data is running, or when WiFi, GPS, or Bluetooth is on. You can try using the built in app killer, it kills all those unnecessary apps that keep your phone awake. Task killers is not good to use, since it is a app itself and plus it sometimes kill the wrong apps, but the built in one for MIUI is perfect. You probably have apps keeping your phone awake. You can also try a different governor to see if it works, though I tested smartassV2 and it is able to Deep Sleep. If your going to underclock that low, with a low min, I would recommend using smoothass, smartassV2 does lag when waking up, and does lag in general when it comes to underclocking that low; because smartassV2 will go to your lowest min, while smoothass does go to the frequency four steps ahead of your min frequency.

I Just tested deep sleep; I reseted timers for cpu spy, went back to launcer screen, use app killer(hold home button and then click the app killer button); I then turned off my phone right away, gave it about 45 seconds with screen off, turned it back on, checked cpu spy, and cpu spy tells me I have 20 seconds at 576Mhz, 10 seconds at 245Mhz, and 32 seconds in Deep Sleep. The 20 seconds at 576Mhz is the time I took to go launcher and then used app killer, basically the time before I turned off the screen. 245Mhz is the governors ramping down the clock speed as the phone goes idle; then Deep Sleep kicked in.

Thanks, I went ahead and removed maps and reinstalled as it looks like it was contributing to the problem. Once I changed to smartassv2, I had better results (I was using smoothass per another recommendation). I do not appear to have any lag issues. I think the main cause (besides maps) is that the wifi is still wonky; the phone never properly sleeps whenever wifi is on, unlike when 3g is active. GPS can be on, but not in use... I have it on and the phone goes into deep sleep now properly. I will test for a few more days and report back with results. I mainly look at what % drop I get per hour with little to no use as a sign of how good battery savings are. This is with sync enabled, gps on (but not in use), 3g, auto brightness (with very low custom settings) and no animations. I do use haptic feedback, but to a very little extent. I do use the built in app killer occasionally, but when troubleshooting deep sleep issues, I go to manage programs and then see what is currently running (services). Thanks for your support.
 
I Just tested deep sleep; I reseted timers for cpu spy, went back to launcer screen, use app killer(hold home button and then click the app killer button); I then turned off my phone right away, gave it about 45 seconds with screen off, turned it back on, checked cpu spy, and cpu spy tells me I have 20 seconds at 576Mhz, 10 seconds at 245Mhz, and 32 seconds in Deep Sleep. The 20 seconds at 576Mhz is the time I took to go launcher and then used app killer, basically the time before I turned off the screen. 245Mhz is the governors ramping down the clock speed as the phone goes idle; then Deep Sleep kicked in.

What's the governor that has the best battery life without sacrificing performance? I always went with smartassv2 but there are so many more in this version so I thought I'd ask.

I like interactive governor the best, it's tried and simply efficient and ramps up very fast when needed, and then back down when idle. Most of the time the screen is on like when you're reading should be at the min frequency (a static screen shouldn't take CPU cycles), and screen is off, it should be at deep sleep. The highest freq is 3rd place when it's actually doing processing, like opening & closing apps, live wallpapers, etc.
 
I like interactive governor the best, it's tried and simply efficient and ramps up very fast when needed, and then back down when idle. Most of the time the screen is on like when you're reading should be at the min frequency (a static screen shouldn't take CPU cycles), and screen is off, it should be at deep sleep. The highest freq is 3rd place when it's actually doing processing, like opening & closing apps, live wallpapers, etc.

ive tried interactive x and loved it expect for when I recived a phone call, seems like when the phone was ringing I could not get the screen to come on, like it wasnt ramping up to allow the call and screen on command.

Has any one else had a problem like this on interactivex governor?
 
ive tried interactive x and loved it expect for when I recived a phone call, seems like when the phone was ringing I could not get the screen to come on, like it wasnt ramping up to allow the call and screen on command.

Has any one else had a problem like this on interactivex governor?

I just tried this and found that it did the same thing. I tried it again, and it worked fine.

Going to play around a bit with interactive, interactive X, smartass, and smoothass.

EDIT: Research suggests that smartass = a better interactive, and smoothass = smartass + More agressive wakeup config.

One of many sources explaining them: http://www.acsyndicate.net/which-cpu-governor-should-you-go-with/
 
I also noticed that smartassv2 will only allow me to clock from 61 mhz to 652. When I lower 652 to anything else, it will only stay at 61 mhz. I think this is due to some set values of 'steps'.

smoothass will do the same, but has a min of 184.
 
ive tried interactive x and loved it expect for when I recived a phone call, seems like when the phone was ringing I could not get the screen to come on, like it wasnt ramping up to allow the call and screen on command.

Has any one else had a problem like this on interactivex governor?

I said Interactive, not InteractiveX, the X version locks the CPU to the lowest freq when screen is off, which explains it being slow at waking back up. Also just because a dev says theirs is based on interactive or improvement on it, doesn't necessarily mean it's true, devs make mistakes & miscalculations...etc. Take it with a grain of salt. Very few people have done any unbiased actual testing of the governors and the differences in how they perform vs battery life.
 
I'd have to say Smoothass is my favorite. I get about the same battery life as Smartass but it's a bit snappier.
 
I just tried out interactive and it has AMAZING battery life compared to smartass. Also, performance is not affected and even seems a little better. Thanks for those changes you made to interactive cause it seems to help a lot!
 
Austrie, can you push your changes to your github repo? (or provide a link to what those changes are) I'm interested in the 720p video encoding enhancements for CM7. Seems the default video camera only does 10 fps no matter what resolution (the hardware is capable of more I'm sure).
 
Sure, when I release V6.0, or when I'm done with my side project with Mobstergunz, I will. Though I already have my github with my V1.0 on it, so you'll have to tell the difference between V1.0 and V5.0/V6.0
 
Sure, when I release V6.0, or when I'm done with my side project with Mobstergunz, I will. Though I already have my github with my V1.0 on it, so you'll have to tell the difference between V1.0 and V5.0/V6.0

I know this is probably not possible as it most likely isn't a kernel issue. But is there a way to increase gaming environment on your kennels.I love miui but I can't play some of my games cause they lock up and I have to wait for it to become responsive again. Again I don't know if that's some thing that you can do our if it's specific to miui build.thanks Austrie love you're work and can't wait to see what else have for us
 
Back
Top Bottom