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

Root v1.1 up for testing ***Umph Kernelv1 Now With Oddball***

got v1 kernel working great with setcpu. no lock/unlock problems and i havent done any reboots or set on reboot option and everything is working perfectly. will test for a couple days to make sure i don't get any random reboots or anything like such, but got all my profiles setup and im running 1.7ghz while not charging and 1.9ghz while charging through usb and it seems to be doing amazing. pulled a 3963 with AnTuTu benchmark and a 2600 with Quadrant. God I Love This Device!!!!

hahaha forgot i got all my minimums set to 122 and they are also working properly and efficiently.

Hmmm...sorry, but I doubt you have everything working. I'm assuming you are using SetCPU because of the profiles. So do this:
1) Set min 122, max 1900.
2) Put on any governor besides ondemand, try Scary.
3) While SetCPU open, press power button to lock, and then again to unlock.
4) Read the values on top.

Does it say "scaling Scary" then under that "1900 max 122 min"

OR

Does it say "scaling ondemand" then under that "1900 max 245 min"?
 
Upvote 0
I've used nothing but set cpu and had no issues whatsoever. Has anyone tried to recreate what I did to see if that would help?

I already tried installing over doomlord's v01 and v02 kernels. I will try clearing dalvik cache since that will be re-created on next boot. I'm not gonna do nandroid backup because I don't feel like messing my phone up :p

EDIT:
Nope. Cleared Dalvik Cache then reinstalled test 14. Didn't work.
 
Upvote 0
I already tried installing over doomlord's v01 and v02 kernels. I will try clearing dalvik cache since that will be re-created on next boot. I'm not gonna do nandroid backup because I don't feel like messing my phone up :p

EDIT:
Nope. Cleared Dalvik Cache then reinstalled test 14. Didn't work.

Remember though i also did an accidental factory reset.
 
Upvote 0
I already tried installing over doomlord's v01 and v02 kernels. I will try clearing dalvik cache since that will be re-created on next boot. I'm not gonna do nandroid backup because I don't feel like messing my phone up :p

EDIT:
Nope. Cleared Dalvik Cache then reinstalled test 14. Didn't work.
people here (dont remember exactly who) said that doomlords was doing the same thing
 
Upvote 0
@cubmoney..... just to let you know yes i have looked at consistently over the past few hours and all i have to say is you have a point but no..... it only scales back to 245 when i enter setcpu otherwise it is perfectly set at 122 and when i unlock my phone afterwards (i have it set to interactive gov), and who would set their gov to scary when it's just pointless, i had mine set to smartass for a couple of the profiles but noticed they werent working so well and had to set them back to ondemand, but everything is great on my phone and is working amazingly.....
 
Upvote 0
Hey guys I hate to tell you but nno fills doesn't solve the problem and here is the reason why:
set CPU shows you real time what the current and min Max freq is. It also shows what the current selected government. Is.
No frills simply provides you a list if available frequencies and govenors and allows you to choose values to set at boot. It never shows you what government and frequencies are actually applied. If you go into the sys directory and look at were the values for govt and freq are it will show on demand gov and the min freq set to 245 regardless of what CPU control apparently you use.
So it is something in the kernel making it default back to on demand and 245 min drew whenever it sleeps(I.e. turning the screen off)


Sorry to be the bearer of bad news but its a fact! Still a very nice kernel though it just needs some work!
 
Upvote 0
Remember though i also did an accidental factory reset.

Yea, but I'm not willing to do that! If someone is willing to set back to complete stock, go ahead...

people here (dont remember exactly who) said that doomlords was doing the same thing

I tested on v01 and v02 of doomlord's kernel and reported same behavior.

@cubmoney..... just to let you know yes i have looked at consistently over the past few hours and all i have to say is you have a point but no..... it only scales back to 245 when i enter setcpu otherwise it is perfectly set at 122 and when i unlock my phone afterwards (i have it set to interactive gov), and who would set their gov to scary when it's just pointless, i had mine set to smartass for a couple of the profiles but noticed they werent working so well and had to set them back to ondemand, but everything is great on my phone and is working amazingly.....

How can you tell that the min is set and stays at 122MHz without checking? Also same for governor...I've checked with nofrills (SetCPU uninstalled) and with SetCPU (nofrills uninstalled) on fresh boots. Anytime I try and then lock-unlock, it'll reset back governor to ondemand min 245MHz. So if you can provide proof of some sort against all the people on here saying it's doing the same thing I'm describing, I have a hard time believing you.


Hey guys I hate to tell you but nno fills doesn't solve the problem and here is the reason why:
set CPU shows you real time what the current and min Max freq is. It also shows what the current selected government. Is.
No frills simply provides you a list if available frequencies and govenors and allows you to choose values to set at boot. It never shows you what government and frequencies are actually applied. If you go into the sys directory and look at were the values for govt and freq are it will show on demand gov and the min freq set to 245 regardless of what CPU control apparently you use.
So it is something in the kernel making it default back to on demand and 245 min drew whenever it sleeps(I.e. turning the screen off)


Sorry to be the bearer of bad news but its a fact! Still a very nice kernel though it just needs some work!

OMG! Someone who actually knows what he/she is talking about, lol. This is a problem in the OC tables since pwnyourace used doomlord's OC tables. As such, as I have tested, Doomlord's kernel(s) will report the same behavior (which it does). Is that so hard for everyone to understand?
 
Upvote 0
Well I tried using terminal to manually set governor and min:

echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "122880" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

Result is resets back to 245 and ondemand...I'm out of ideas of what I could do :(

EDIT:

Mine wifi isn't working do i need to do a full wipe then install the rom?
What version of the kernel and describe what you mean. Does it show "Error" when trying to apply it within settings?
 
Upvote 0
Well I tried using terminal to manually set governor and min:

echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "122880" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

Result is resets back to 245 and ondemand...I'm out of ideas of what I could do :(

EDIT:


What version of the kernel and describe what you mean. Does it show "Error" when trying to apply it within settings?

I'm on version 1.2 and it keeps saying Error and i did a fresh wipe.
 
Upvote 0
Does that one has wifi and if i do nandroid restore will ti restore it?

No need to do nandroid restore! Kernels are flashable over each other. And yes it has wifi. Just do the following:
1) Download here: Download Umph Kernelv1 zip
2) Put file on SD card
3) Shutoff phone
4) Enter recovery, and select flash from zip.
5) Select Umph-Kernelv1.zip and YES.
6) Reboot

Some people report that this one doesn't work on some phones. So hopefully you are lucky.
 
Upvote 0
No need to do nandroid restore! Kernels are flashable over each other. And yes it has wifi. Just do the following:
1) Download here: Download Umph Kernelv1 zip
2) Put file on SD card
3) Shutoff phone
4) Enter recovery, and select flash from zip.
5) Select Umph-Kernelv1.zip and YES.
6) Reboot

Some people report that this one doesn't work on some phones. So hopefully you are lucky.

Nope it doesn't work on mine i got version 1010_2_39
 
Upvote 0
My triumph is the 39 one and i was able to install and boot with umph kernel.

Update: Running at 1900 max 245 min ondemand. Before i installed setcpu i was doing a titanium backup it rebooted once but after I installed setcpu i did stress test for about 5 mins no error found. Right now my battery temp is at 36 C I will probably do more stress test using different program. Anyone know a good stress test app for the cpu? Is there a prime 95 for android :)
 
Upvote 0
Okay great news everybody I solved the sleep gov/freq problem!
There is a file in /system/etc called init.qcom.post_boot.sh.
what this file does is checks to see if the CPU status changes from sleep to awake and if so it changes the gov to ondemand and the min drew to 245 along with some other CPU parameters.
what I did is with a root file explorer open this file as text and out a # symbol, which comments out the comands where it makes it change those values which makes them be ignored! After doin this reboot and use either setcou or no frills to set desired values and your setting g will stay! Thank you and goodnight lol!

Hey pawn is the init.qcom.post_boot.sh a file that your kernel writes to /system/etc cause if so you need to either remove or change it like I described! Also how do you run init.d scripts with this kernel. The only way I have is with install-recovery.sh but even the stock kernel will do that!
 
Upvote 0
Okay great news everybody I solved the sleep gov/freq problem!
There is a file in /system/etc called init.qcom.post_boot.sh.
what this file does is checks to see if the CPU status changes from sleep to awake and if so it changes the gov to ondemand and the min drew to 245 along with some other CPU parameters.
what I did is with a root file explorer open this file as text and out a # symbol, which comments out the comands where it makes it change those values which makes them be ignored! After doin this reboot and use either setcou or no frills to set desired values and your setting g will stay! Thank you and goodnight lol!

Hey pawn is the init.qcom.post_boot.sh a file that your kernel writes to /system/etc cause if so you need to either remove or change it like I described! Also how do you run init.d scripts with this kernel. The only way I have is with install-recovery.sh but even the stock kernel will do that!

Wouldn't it make sense to just delete that file? All I see in it is everything that we don't want, lol. I'm gonna delete it and see...

EDIT:
Deleting file fixed problems after lock-unlock :)
 
Upvote 0
Wouldn't it make sense to just delete that file? All I see in it is everything that we don't want, lol. I'm gonna delete it and see...

EDIT:
Deleting file fixed problems after lock-unlock :)

So far, so good here, although I just renamed the file to .bak

Not that that would do me any good if it borked something, but whatever :)

Edit: I say that, but I did reboot and it hung, so I just reflashed the kernel and it booted fine. Checked the file and it's not there, just the .bak
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones