yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Imoseyon:
Interesting this feels like init.d support is broken in the ROM, or there's a conflict that prevents /etc/init.d/01vdd_levels from running at boot. Jeremy, anything special going on with init.d on BAMF stripped?
[Thunderbolt Android Development] Imoseyon:
Awesome, you must be on wifi most of the time right? My sense kernels wifi driver consumes 1/2 power of stock wifi driver at idle. :)

Doh stock TB probably doesn't have busybox installed properly. Let me know if installing from market doesn't work. I will probably make a zip for installing busybox properly for stock TB.

I also have a couple of zips you can flash on op instead of using the script.
[Thunderbolt Android Development] PineTre3:
yea i seen that thank you! but what about the voltage thing if i use the max/min in cpu will that matter or is there an upside to using terminal?
[Thunderbolt Android Development] 52brandon:
Oddly no, I usually am when home, but I stayed at my girls last night, so it was 4G the whole yime
[Thunderbolt Android Development] m1mgd00:
Sorry, forgot to mention that I'm running Das BAMF Stripped.
[Thunderbolt Android Development] bokechukwu1:
Which kernel version are you using voltage, smart ass or interactive x, etc? Wanna try your setting out also what Rom and are you on extended batt
[Thunderbolt Android Development] BennyJr:
Been running all day atleast 12hrs and I have 57 percent left. Stayed cool all day and ran better with the kernal update. I'm also not running setcpu. Love this kernal!
[Thunderbolt Android Development] RjsShadows:
Why should we not run SetCPU? I like to use it to have profiles for my battery life to last longer.
[Thunderbolt Android Development] ScottIsMyName:
We should be able to make an app to run the script right? This would probably help those with problems using terminal emulator.

I can try to put something together tomorrow but I am still a novice with android programming.

Sent from my Thunderbolt
[Thunderbolt Android Development] 52brandon:
BAMF remix 1.6.3. Smartass governor on 1.92x set to 1.408-184. I can't remember if any of the vdd files I edited actually took though. They were very minute changes though anyways
[Thunderbolt Android Development] 52brandon:
I think it's kinda overkill. Typing:

su

speedtweak.sh

in terminal is extremely simple, and IMO everybody that wants to edit files on their phone should learn ADB/Terminal. It just looks scarier than it is
[Thunderbolt Android Development] patdroid1:
yeah it's really not that hard...learned it overnight...besides it makes you feel like you know what you're doing when you type funny looking commands in a command prompt...i enjoy it lol

i got my stable voltages locked down...now i just need to figure out which governor to use!!!!! i still default to interactive x but haven't given smartass enough time
[Thunderbolt Android Development] Nikolai2.1:
Could you post your voltages please? Are they lower than the extreme voltages?
[Thunderbolt Android Development] patdroid1:
give me a minute...i'll compile a quick table

they are lower than extreme...i got luck with this phone
[Thunderbolt Android Development] patdroid1:
After stress testing and benchmarking at each voltage and frequency increments i finally came to these stable settings. However (except for the 750 settings) going .25 lower would cause instability or a complete crash. So to be safe i bumped up a little bit at each frequency until i felt completely confident. i killed off 184 because when you lock down that frequency the phone is soooooooo slow...at 245 it can at least move along and since we can't undervolt below 750ma...i figured the risk of lagging was not worth the battery saving reward. haven't figured my voltages above 1408 yet as i only go above that when playing around...which i'm about to do....right now lol ;-)

Stable

184320 @ 750

245760 @ 750

368640 @ 750

768000 @ 875

1017600 @ 975

1222400 @ 1075

1408000 @ 1125

Final Settings

184320 @ Delete

245760 @ 750

368640 @ 800

768000 @ 900

1017600 @ 1000

1222400 @ 1100

1408000 @ 1150
[Thunderbolt Android Development] JonKyu:
Awesome! Thanks for sharing, i might just try these out.
[Thunderbolt Android Development] Nikolai2.1:
You're stable ones work for me...they're just not sticking on reboot. But I can confirm they they work via the terminal
[Thunderbolt Android Development] patdroid1:
to get them to stick i just edit through root explorer then reboot. i do my testing in adb and once i finalize setting just edit the init.d
[Thunderbolt Android Development] Nikolai2.1:
Bug report. Voltages don't stick on reboot period. I've been getting great battery life nonetheless, but if I set a custom voltage or even switch it to say, battsaver mode. When I reboot and check, the voltages go back go "normal" mode, but it still clocks to 1ghz and says I'm on battsaver.
[Thunderbolt Android Development] Nikolai2.1:
At this points it seems like I can't even get the predefined battsaver voltages to stick
[Thunderbolt Android Development] patdroid1:
how are you editing them?
[Thunderbolt Android Development] Nikolai2.1:
Root explorer. Then ill run

sh /etc/init.d/01vdd_levels

When I check the script it shows the custom voltages.

when I reboot and check it again, even If I wait like 10 minutes, they're back up to like 184/900 and so on.
[Thunderbolt Android Development] FoxRacR17:
Same for me. Have tried mounting system as r/w in root explorer and bamf toolkit, and using root explorer to edit the voltages to what i know works for my phone, and upon reboot i check using the script option #11 and it shows the default voltages. But if I check both 01vvd_levels under /etc/init.d and /system/etc/init.d/ both still show the custom voltages that I set. It just seems the kernel isnt reading from the 01vdd_levels files. However if i flash back to 2.4 and do everything EXACTLY the same to set my custom voltages everything sticks after a reboot. So something must be broke in 2.4.1 and 2.4.2
[Thunderbolt Android Development] Nikolai2.1:
Exactly what I'm thinking
[Thunderbolt Android Development] Imoseyon:
K i'm looking into this now.
[Thunderbolt Android Development] patdroid1:
well this is where my knowledge runs thin lol...that's a bummer man. you might wanna try adrynalyne's 2.0 kernel...same concept and if you read the op he posted up some scripts...worth a shot if you haven't tried...i'm running now and is perfect (until imosoyen releases his next update lol)
[Thunderbolt Android Development] Nikolai2.1:
Thanks alot man, and hey the new .13 seems to have better battery life. Or that could be the battmode lol

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Nikolai2.1:
Yeah I was actually just about to, at least until the bugs in this one are worked out.

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Imoseyon:
Yikes, found a nasty bug in my script. Fix coming in like 5min!
[Thunderbolt Android Development] PineTre3:
i'm running the 246 version and i changed it to be "extreme" mode and when i go into setcpu it says i have the option to go up to 1.92? is this a bug in setcpu or did the extreme voltages change?
[Thunderbolt Android Development] Nikolai2.1:
Haha then I think ill wait for this! :)

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Nikolai2.1:
You can change it to whatever you want, it's just gonna lock it at 1.4 but u can use set CPU to change it

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] 52brandon:
If you run sh /etc/init.d/01vdd_levels after boot it reapplies the script and runs your changed values. If that script could run automatically on boot, or possibly better if it were delayed, it would be golden
[Thunderbolt Android Development] patdroid1:
lol now you know you're not going crazy...it makes me wonder what's wrong with me....gonna have to download update and give a go!!!!!
[Thunderbolt Android Development] Nikolai2.1:
It used to. I think thats what he's trying to fix

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] PineTre3:
ohhhh so even if i set it to 1.9 in setcpu it's still gonna run at 1.4?
[Thunderbolt Android Development] Nikolai2.1:
Lol yeah first I thought I was a permissions thing but I fixed that last night

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Nikolai2.1:
No, set CPU will over ride

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] PineTre3:
okay now i'm lost haha i thought in the op it says that "extreme" will only overclock to 1.4? sorry i'm new to all this script stuff i just got the hang of everything else haha
[Thunderbolt Android Development] Imoseyon:
here's the fix. sorry about the bug guys - that was a nasty one.

http://www.androiddoes.net/~imoseyon/imoseyon_leanKernel_v2.4.3.zip

http://www.androiddoes.net/~imoseyon/imoseyon_leanKernel_246Mhz_v2.4.3.zip

http://www.androiddoes.net/~imoseyon/imoseyon_leanKernel_sp_v2.4.3.zip

will update OP in a bit.
[Thunderbolt Android Development] Nikolai2.1:
Its alright lol. Okay so the kernel has all the kernels combined, and you choose which one you want using the script. However, if you feel the need to over clock some more, you can always use set CPU instead of running the script again.

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Nikolai2.1:
Appreciate it man :) so the settings will stick to reboot?

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] patdroid1:
we're gonna find out!!!! here we go...intalled and rebooting
[Thunderbolt Android Development] Imoseyon:
Yup that's the fix. I also made the script loop so it doesn't exit until you tell it to but that part needs some work still in terms of aesthetics.
[Thunderbolt Android Development] Nikolai2.1:
Yeah I know what you mean. But it's fine and I'm satisfied. Thanks for the quick update!

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] JonKyu:
Thank You! That's exactly what I needed!
[Thunderbolt Android Development] PineTre3:
okay so even though I'm running "extreme" which is a 1.4 max I still have the option to go to 1.9 with "extreme" in setcpu because all the kernels are combined? do I got it? haha

Sent from my Thunderbolt
[Thunderbolt Android Development] Nikolai2.1:
Lol yep! Just make sure that you are.in fact on extreme and not normal if u want it more under volted of course

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Imoseyon:
Yeah basically all the speed slots are available but speedtweak.sh sets soft limits on min and max speeds so your phone never goes above max or below min.

The method my script uses is the same method that setcpu uses so once you launch setcpu you can easily (and accidentally) override the settings set by my script.
[Thunderbolt Android Development] patdroid1:
hmmm....all the values didn't show up in the 01vdd_levels file at first ... i went back to the speedtweak.sh and ran script for extreme...went back to 01vdd_levels and everything was there...edited voltages...reboot and boom...perfection.

is that normal????
[Thunderbolt Android Development] Nikolai2.1:
Okay so I'm running the first five slots on battsaver mode at,

184320 @ 750

245760 @ 750

368640 @ 750

768000 @ 850

1017600 @ 950

Seems to work well, and I'm good here but if I'm feel adventurous someday I might go lower ;)

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Nikolai2.1:
With the new update yes lol

Sent my HTC Thunderbolt 2 5G.
[Thunderbolt Android Development] Imoseyon:
Yes when you first flash the kernel it's using its default values which is same as "normal".
[Thunderbolt Android Development] FoxRacR17:
Thanks for the quick update! 2.4.3 fixed the issues and now my custom voltages are sticking
[Thunderbolt Android Development] PineTre3:
i'm too afraid of the script lol not advanced enough, all i used it for was switching from "normal" to "extreme" and then i used setcpu to switch govenor to interactiveX and max to 1.4, would that mess with your script even though i didn't change voltages in your script to begin with?
[Thunderbolt Android Development] patdroid1:
are you serious???? you want to go lower huh???? lol good luck!!!! after seeing the stock voltages i'm happy i can get as low as i can! let me know if you get there ;-)
[Thunderbolt Android Development] Imoseyon:
Oh setcpu can't mess with the voltages, only min, max and governor.
[Thunderbolt Android Development] Imoseyon:
Shhhh, i made a silent update to 2.4.4 (sense). All it does is make you hit enter before the screen loops back in the speedtweak script - no change in kernel code. If you're already on 2.4.3, only flash if you're bored.
[Thunderbolt Android Development] JonKyu:
Lmao im going to give those a try too!
[Thunderbolt Android Development] patdroid1:
lol tricky tricky....well played
[Thunderbolt Android Development] PineTre3:
alright sweet thanks!

Sent from my Thunderbolt
[Thunderbolt Android Development] Nikolai2.1:
On another note, eHRPD is back up :D
[Thunderbolt Android Development] bmerrill63:
Thanks for the fast update! loading 2.4.4 this morning. Great work man.

Update-

Reboot/script seems to be fixed!

Plus you don't have to re-enter speedtweak.sh everytime.....oh thank you thank you!!
[Thunderbolt Android Development] shock2sys:
i figured that busybox wasn't installed in the stock rom, but i installed it within titanium backup.

anyway, i'm installing the one from the market now.

Do i still need to mount the system as r/w as someone else had mentioned or will the script (together with busybox) take care of that?

edit:

woohoo!!! after installing busybox from the market and installing the 2.44 kernel, i was able to successfully run the speedtweak.sh script and set the options.
[Thunderbolt Android Development] biglipps66:
From running extreme 2.2.0 to this new 2.4.4 normal, my quadrants dropped over 400 points. Doesnt seem normal?

EDIT make that 600 points actually.. same speeds.. same gov.

Wow even at 1.9ghz clock Im STILL less than my 1.4 clock on the old 2.2.0! eek

Flashing back to 2.2.0 no other changes and Im back to normal. I guess mine just likes this one better or something. Was there a flaw in 220? Is it suppose to have 2200 average quadrants at 1.4gz? I do notice a little batt drain difference for sure after I changed from bamf 1.6.1 to 1.6.3 with this 2.2.0 kernel. I may go back to 1.6.1 and try kernels on that release again
[Thunderbolt Android Development] sgtguthrie:
I don't put much stock in quadrant scores. When you can run it 3 different times and get 3 very different results, how accurate could it be? Now I do think smartbench is a little more accurate, but still isn't gospel...

sent via rooted THUNDERBOLT with Tapatalk
[Thunderbolt Android Development] tipsofme:
I know I am doing something wrong here. Every time I flash w/Rom manager to 1.92x or Extreme Kernal, I go into boot loop and have to restore. What am I missing?
[Thunderbolt Android Development] dajogejr:
Use Clockwork Recovery and not ROM manager.
[Thunderbolt Android Development] trikotret:
I get boot loops when I tried flashing 1.92x. No clue why
[Thunderbolt Android Development] lect1984:
voltages are too low. reflash a normal kernel.
[Thunderbolt Android Development] tipsofme:
I know this is super newb of me but isn't clockwork recover in Rom Manager?
[Thunderbolt Android Development] tipsofme:
How do I change the voltage before I flash?
[Thunderbolt Android Development] sgtguthrie:
Are you wiping dalvik-cache? if not that could be your problem. If that doesn't do it you probably need to try one with higher voltage or lower clock speed. 1.92x is excessive! Why not just download the 2.4.4 one then tweak it from the terminal? It boots at normal voltage until you change it.
[Thunderbolt Android Development] NetworkPIMP:
Rom Manager is a pretty post-boot interface that can direct Recovery to do things - which it does after rebooting.

What you're being asked/told to do is to skip using Rom Manager - for the moment anyway.

D/L the zip for the kernel you want to your sdcard, then boot the phone into recovery: hold down volume-down while pressing/holding power button - this will put you into hboot, from there you can boot into Recovery.

From there, follow the menu's to install a .zip and navigate to the kernel you d/l'd.

-J
[Thunderbolt Android Development] biglipps66:
I dont have supreme faith in quadrant scores either.. BUT.. a score of 600 points in 1 direction or another is quite the difference, especially in same clocks or 500mhz more! Its noticeable for sure
[Thunderbolt Android Development] lect1984:
sound's like you adrynalyne's uber quadrant script was enabled. it adds another 500 or so to your quadrant scores.
[Thunderbolt Android Development] biglipps66:
Never clicked it. Its literally the difference in flashing 2 different kernals though. Dunno.

With it ENABLED I get 2500 scores.. only 300 higher. So thats definitely not it.
[Thunderbolt Android Development] lect1984:
which governor are you using? i get 2300 @ 1.41 using ondemand. high 2700s with uber quad enabled.
[Thunderbolt Android Development] Imoseyon:
Let me look into this. I only check linpack and nemamark regularly. It's possible one of my recent changes is affecting quadrant scores. I wouldn't worry about it for now though. Both linpack and nema scores are still strong.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] Imoseyon:
Looks like its the changes between 2.3 (never released) and 2.4. Most likely the kernel code upgrade to .13.

I will fiiiiiix.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] MisterDonut:
Just downloaded the Newest Kernel. I was wondering do I need SpeedCpu in order to use the overclock kernels. or will speed tweak automatically boost it for me.
[Thunderbolt Android Development] BennyJr:
U can just use speedtweak. thats what im doing and its running great.
[Thunderbolt Android Development] mzimand:
I can confirm the lower Quadrant Scores. But the new Kernel is running great with super cool temperatures and the best Linpack Scores thus far. I am running 1.92x and my phone runs coolest at 1.59 for some reason.
[Thunderbolt Android Development] Bullhead00:
If I flash the latest kernel, enable the extreme setting, and my phone locks up or reboots, will I have to reflash the kernel to get the default setting back, or will it automatically revert back to default? Didn't know how else to phrase that question lol. Would I be correct in assuming that flashing make_battsaver or make_extreme zip files in CWM takes care of that?
[Thunderbolt Android Development] BennyJr:
Reflash it
[Thunderbolt Android Development] want a droid:
Nothing but good results from imoseyon's kernels!

Sent from my ADR6400L using das bamf 1.6.3 remix with imoseyon's lean extreme 2.4.2 kernel
[Thunderbolt Android Development] biglipps66:
Gotcha Mr Imoseyon ...

So we did confirm there was a slight coding error then correct. I see that others had the same quadrant reflections. Ill check linpack on the old kernel and the new and see what I get as well.
[Thunderbolt Android Development] Cubs2008:
Do we have an expectation for linpack scores? I'm getting around 60 mflops with 1.92x (special 2.4.4) on Liquid ThunderSense 1.45 and it runs pretty cool.
[Thunderbolt Android Development] Imoseyon:
1Ghz: ~40mflops

1.4Ghz: ~50mflops

1.9Ghz: ~60mflops

+/- 2-3 mflops
[Thunderbolt Android Development] Cubs2008:
Thanks Imo! I'm right on point with these expectations. :)
[Thunderbolt Android Development] taypotts:
So I was using the extreme kernel and its AMAZING for battery, but I want to have the latest one, so which of the three gives best battery life? Lean, special, or the 264??
[Thunderbolt Android Development] biglipps66:
Old 2.2.0

1.4ghz

Interactive

46flippyflopps
[Thunderbolt Android Development] BennyJr:
lean with the 184mhz enabled. my phone loves it and it stays cool
[Thunderbolt Android Development] PerCompLLC:
Now THAT is funny! :D
[Thunderbolt Android Development] Imoseyon:
I could bake it into ramdisk but somehow it didn't feel right. The zip will create a 200mb swap file and enable it on every boot. Completely optional.

leanKernel + Tesla coil
[Thunderbolt Android Development] Imoseyon:
It's up to you if you want to use it. Not necessary. If you're using the 1.92 kernel id probably recommend it to limit the top speed and save battery.

leanKernel + Tesla coil
[Thunderbolt Android Development] Imoseyon:
Can't help myself.

leanKernel + Tesla coil
[Thunderbolt Android Development] Imoseyon:
A quick clarification. Backporting means I took the code from the newest linux source and integrated it into our tbolt kernel code. So as far as leanKernel's ondemand governor is concerned its got the latest and the greatest.

leanKernel + Tesla coil
[Thunderbolt Android Development] jlevy73:
It was late when I posted my comment, didn't catch at the time it was just a port for the on-demand codes. But that being said, I bet .39 is a better kernel altogether since the governor is greatly improved.
[Thunderbolt Android Development] PerCompLLC:
@Imoseyon - I've read your write up on swap files, and I understand how they work on a linux system. Question though... In your opinion (or your experience), what advantages will your swap implementation bring to the TBolt?
[Thunderbolt Android Development] NetworkPIMP:
So, ROM Manager and/or CWR both allow me to repartition the SD can that creates a swap partition if I remember correct (in addition to sd-ext).

can that be utilized?

where does the 200mb swap file get put? SD?

Thx!
[Thunderbolt Android Development] Imoseyon:
I think if used correctly, it will 1) allow more apps to stay in memory, thus making switching between apps faster, 2) keep more RAM free for apps that use a lot of memory otherwise minfree is going to be working hard killing procs while the app is trying allocate free memory, and 3) leave more RAM for buffers and cache, which help speed up the phone.

There are also some risks associated with using swap too such as potential app performance and power efficiency hit, so i'd say the jury is still out.
[Thunderbolt Android Development] Imoseyon:
I have not tried to mount a swap partition but i don't see why it wouldn't work if the kernel has full swap support enabled.

As for the swap file, it gets put on /data/swap. My blog post has some details about the performance test i ran to compare I/O speed between internal flash and sdcard, but that was before increasing the readahead buffer so perhaps I should run another test.
[Thunderbolt Android Development] shelooga:
ive been streaming a lot of video the past two days.. i think .5 may have had better battery life for me. i went from 85 to 15 and its only the 4th inning! go phils!

but yesterday i streamed the par 3 contest for 2 hours (4g only), in addition to my normal routine and got a solid 24 hours from my charge. also today i spent the first inning using a wifi signal (supposed battery saver opposed to 3/4g) at the bar and 4g for the past 3.

both times using the standard 1.41 clocked down to 1.2

if i use swap correctly(which i dont know how to or understand the mechanics after reading about it too) can this help battery life?
[Thunderbolt Android Development] Imoseyon:
Yeah as far as the ondemand governor change is concerned, newer code doesn't necessarily mean better in all aspects. But based on what I've seen in the code changes, if the old code had better battery life it's due to pure luck.

I did notice that thunderbolt battery life is very fickle. May depend on exactly where you were and how strong the signal was in terms of 4g, which is clearly the battery drain culprit. So comparing battery life can really never be an exact science unfortunately.

As for swap, give it a try and see if it makes any difference for you. Just flash the zip and reboot.
[Thunderbolt Android Development] T41NT204:
im just shy of hitting 2000 on quadrant with the Bversion kernal, on the virus 3.0 rom. very nice, but what are the attached files at the bottom of your main post?
[Thunderbolt Android Development] Imoseyon:
Hmm I don't have a b version. I think you might be in the wrong thread. I could build a 'b' kernel but it might be entirely different than what you are thinking of. ;)

leanKernel + Tesla coil