• 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***

I tried adding renaming init.qcom.post_boot.sh by adding .bak and the min 122 and governor still revert back to 245 and ondemand. Did i do it wrong? I was trying to figure out also how to add # by going opening the init as text editor but dont know where to put it. Still a noob with all of this terms:eek:
 
mcvanta said:
I tried adding renaming init.qcom.post_boot.sh by adding .bak and the min 122 and governor still revert back to 245 and ondemand. Did i do it wrong? I was trying to figure out also how to add # by going opening the init as text editor but dont know where to put it. Still a noob with all of this terms:eek:
Click to expand...

delete the file, reboot, then change your frequencies....
 
pwnyourace said:
if 7 wont boot 8 and so on shouldnt..hmm this is the part where i scratch my head..do u know what i changed in 7? i changed the default panic timeout from 10 to 5 and enabled swap support..both of which were done in 1.1 and 1.2..going to make a test with just OC and default config and see if that even boots cuz if it doesnt its the OC table on the oddball devices..but they booted with it on 1.1 and 1.2..ugh very confused..so if this does boot then that means it has to be either the swap or the panic timeout..i have no clue why either of those would make it not boot tho
http://dev-host.org/16kvm127v7pm/Umph-Oddball_test11.zip
Click to expand...


Just tried it and still nothing.
 
AtticTRON said:
Just got a quadrant score of 2190 at 1.3ghz.
Click to expand...
that was all stock with the oc and that setting in the config, compiling one now that has everything v1 has but with that setting and if it works then yay! and also if this gets confirmed that it boots on the oddball devices then can someone that can boot v1 try this and if it works all good it wont have any performance differences and id like to just have one version for all devices
 
AtticTRON said:
It works! I'm gonna test it for a few minutes.
Click to expand...


I leave for a little bit and you make one that boots on the oddballs ;-) I see how it is.. lol

Edit: Heck yeah that is more like it. even as is the performance is working much better and seems stable! Not having the freezes and odd behavior I was having with umph 1.1 and 1.2
 
pwnyourace said:
o yea op update time! gunna switch the link over to my mediafire account, the one u downloaded from will still work but the one in the op will be mediafire, just cuz ive got all my triumph stuff in a folder
Click to expand...


Thanks man, I really appreciate all your hard work.
 
AtticTRON said:
Thanks man, I really appreciate all your hard work.
Click to expand...
your welcome im really glad its working out for you guys and we fixed the issue! cant believe it was something so stupid like setting the min/max cpu frequencies which is disabled on the stock kernel that was making it not boot on only certain devices. ill probably talk to doomlord within the next few days about how exactly to implement the undervolting hes got going on cuz im used to just changing the acpuclock but for now i think we got a pretty good release :D
 
hey i have a quick question.... pwn, how did you deodex the stock rom? did you use an htc kitchen? if you have the link to it i would like to try it.
 
ziggy46 said:
yea thats the one i used.... i dont know how to do it manually or i would. do you have any ideas of why it breaks wifi?
Click to expand...
no clue, whatsoever, wifi is done in the kernel, and the modules, both of which are left untouched..
if u wanna try manually doing it (very time consuming) heres a nice guide How to deodex a ROM - SDX-Developers
theres also 2 other programs u can use to autodeodex at the bottom in notable links
 
Interesting... Hey Attic does your speed revert to 1056 max and 245 min?... I`ve deleted the one file and it sticks for a while then jumps back to those at random?
 
Guys I have been folowing the thread and finally decided to flash this Kernal because everything looked stable. Guess wrong. This thing done messed my phone up! Its just resetting over and over I dont even get a chance to put it into recovery to flash the stock!!
 
bigvandal said:
Guys I have been folowing the thread and finally decided to flash this Kernal because everything looked stable. Guess wrong. This thing done messed my phone up! Its just resetting over and over I dont even get a chance to put it into recovery to flash the stock!!
Click to expand...

dont blame the op! you did the damage.... try pulling the battery and then going straight into recovery.

EDIT: i accidentally put do LOL
 
streetpounder said:
Interesting... Hey Attic does your speed revert to 1056 max and 245 min?... I`ve deleted the one file and it sticks for a while then jumps back to those at random?
Click to expand...

Nope I got mine at 1516 max and 245 min but it does switch back to on demand whenever I change it to scary or smartass.
 
bigvandal said:
Guys I have been folowing the thread and finally decided to flash this Kernal because everything looked stable. Guess wrong. This thing done messed my phone up! Its just resetting over and over I dont even get a chance to put it into recovery to flash the stock!!
Click to expand...

Like the other poster said... pull the battery and go into recovery. Hopefully you loaded the stock kernel file to the card before testing (always make sure you have a way to back out). The behavior you are experiencing is not typical as per the rest of us that have tested it thus far. You may also try resetting the dalvik cache under the cwm advanced menu in recovery and then flashing it again. Maybe something is just hitched up

Always remember this is the nature of the beast. If you want assurances then stock is where it is at. Plan ahead. Keep good backups. If you get stuck somewhere then ask for help in a positive manner, but remeber it is each of us who is making the decision to step off the cliff. Each phone is different as we`ve shown with this kernel. The Umph version worked great for most but some of us had oddballs and had to go back to stock or otherwise whiile Pwm put in some hard work to get us working. Heck there were a few times early on when the triumph first came out that I was poking around and lost all write access to my main partitions !!! It took me a while to figure it out but I got back. Just part of riding on the developmental edge. That being said hopefully we can put our heads together and get you back rolling.
 
You must log in or register to reply here.
Back
Top Bottom