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

Root [Kernel][GB] H426 - BDTweaks now on Google Play (06/24/13)

Maybe I missed it but where in "follow the instructions in the file to enable it" are the instructions in relation to the Permagov. I've unzipped the file and see no instructions ---- is there a place within the phone to locate the instructions?

Thanks!
 
Maybe I missed it but where in "follow the instructions in the file to enable it" are the instructions in relation to the Permagov. I've unzipped the file and see no instructions ---- is there a place within the phone to locate the instructions?

Thanks!

Use a root explorer and go to /system/etc/init.d and open S07HK with a text editor.
 
I am a novice at working with android but I do know alot about networking and open source router firmware and I believe that 70-84 mW is the recommended Transmit Power setting in DD-WRT and for good reason. Depending upon your brand of router and version of DD-WRT. I hope your not cooking your router. I have the Asus RT-N16 running Tomato Toastman Build and a setting of 60 mW works great.

Yeah, I'm pretty sure this ones OK with 90 its an older version 2 hardware linksys wrt54g and the error rate is OK. I've had it there for about two years without issues. Cranked it up to overpower those 8-10 signals I was talking about lol


No problems with battery life or CPU sticking since I rebooted yesterday.

Edit: I take that back it just stuck on 1200 with the charger plugged in. it was fine until I used google maps then it stuck on 1200 until i unplugged it and turned the screen off/ on.
 
Yeah, I'm pretty sure this ones OK with 90 its an older version 2 hardware linksys wrt54g and the error rate is OK. I've had it there for about two years without issues. Cranked it up to overpower those 8-10 signals I was talking about lol


No problems with battery life or CPU sticking since I rebooted yesterday.

Edit: I take that back it just stuck on 1200 with the charger plugged in. it was fine until I used google maps then it stuck on 1200 until i unplugged it and turned the screen off/ on.

some app on your phone is probably keeping a constant load on the cpu which keeps it set at the max freq.

in other news: its been like 50ish hours and my marquee just froze while typing this lol.
 
the only time it ever does it is when its plugged in. seems fine until I open any app at all really (while plugged in). i just had a bunch of force closes on different things im going to try fixing permissions i never did that. I flashed the kernel twice and went beck to stock rooted before flashing 3.75 this time. I really only have a few apps installed, pandora, nofrills cpu, youtube, gas buddy, goodle maps, gmail and a few other common ones.
 
all my beta builds will be for GB rom's only, once we get something final I'll do one for JB too.

while testing beta builds:

DO NOT add anything to init.d and DO NOT use any apps that change or tweak anything other than the frequency/governor/scheduler.

also, please keep your phone on for at least 3 full days after flashing and if your phone locks up and requires a battery pull, post here with what governor and frequencies you were using.

beta build 5: H4Beta5.zip

disabled zram
added cleancache
added frontswap
added zcache (currently disabled)
set cpu to never go past 1ghz during boot
 
The test begins... now.

Error, only boots into CWM recovery.

Reinstalled CTMod 3.75, reinstalled HK b5.

Everything is running, lost all my apps but I backed up my contacts.

Whoops, rebooted on accident. It didn't feel as snappy. I probably just need to clear the caches.
 
Again, very good battery life at night ;)
 

Attachments

  • screenshot-1360413665785-1.png
    screenshot-1360413665785-1.png
    59.2 KB · Views: 133
could you guys do me a favor? I want to know if its my phone i swear this thing is possessed by demons lol.

Plug into the charger, start up the camera and take a picture or two. Now go look at your current cpu frequency and see if its stuck at your max setting.

I swear if i do anything while its charging my cpu maxes out and wont go down until i unplug it. its fine on the charger though as long as i just let it sit there.
 
could you guys do me a favor? I want to know if its my phone i swear this thing is possessed by demons lol.

Plug into the charger, start up the camera and take a picture or two. Now go look at your current cpu frequency and see if its stuck at your max setting.

I swear if i do anything while its charging my cpu maxes out and wont go down until i unplug it. its fine on the charger though as long as i just let it sit there.

I just took 3 pictures while it was plugged in and it's still scaling like it always does.
 
I hate to jinx things but this version looks like a winner Blood. Really snappy performance and very battery friendly. I have checked out all the apps and devices on the phone all working great. Using smartass2 and bfq.
 
could you guys do me a favor? I want to know if its my phone i swear this thing is possessed by demons lol.

Plug into the charger, start up the camera and take a picture or two. Now go look at your current cpu frequency and see if its stuck at your max setting.

I swear if i do anything while its charging my cpu maxes out and wont go down until i unplug it. its fine on the charger though as long as i just let it sit there.

Well first you need a young dev and an old dev. I tried it twice and it did not get stuck so I have no idea.
 
I hate to jinx things but this version looks like a winner Blood. Really snappy performance and very battery friendly. I have checked out all the apps and devices on the phone all working great. Using smartass2 and bfq.

I'm glad its working well for you so far, hopefully it stays that way lol.
 
Same as inkrypted, so far so good. I'm running CTMod 3.75. I cleared cache and dalvik before flashing H4Beta5 and it booted fine afterwords. Running same settings as inkrypted smartass2 and bfq.

Seems really snappy so far. Crossing my fingers that this brings back some much needed life to my little Marquee.

Thanks Blood!
 
No complaints here. Odd thing happened though.... had scheduler set to bfq. Used "juice for roku" app. Checked voltage control after and scheduler went to "on demand". Again, no complaints. Everything else running smoothly.
 
No complaints here. Odd thing happened though.... had scheduler set to bfq. Used "juice for roku" app. Checked voltage control after and scheduler went to "on demand". Again, no complaints. Everything else running smoothly.

bfq is an scheduler and ondemand is an governor bro.
 
Hmm, maybe I should try giving the rom and kernel another flash. IDK its weird. Running good for me other than that though!
 
Back
Top Bottom