yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Cubs2008:
I'm willing to guinea pig JD on my Bolt. I just got great battery life from the 1.92x/Liquid ThunderSense ROM combo (min 245/max 1.92 InteractiveX with no profiles) and I'm going to try it now with battsaver by itself to see what I get. I'll try JD in aggressive mode after that with battsaver (currently don't run JD at all.)

I usually run in LTE only mode since I have 4G at home and at work. I also push Exchange and run Facebook (both Sense and Android), Google and Weather on auto sync.
[Thunderbolt Android Development] Taykiin:
This didn't work for me...? Running Bamf 1.6.3. Wiped cache/dalvik to no avail...:(

**Edit** Some calls record, but most don't....? Is a rather weird thing... it's hit and miss
[Thunderbolt Android Development] Taykiin:
How did you get this to work patdroid1? Would you mind sharing please?
[Thunderbolt Android Development] BennyJr:
What app are u using to monitor this?
[Thunderbolt Android Development] JonKyu:
I think he's talking about JuiceDefender.
[Thunderbolt Android Development] Auronis1:
Temp+CPU Pro widget.

Since flashing 2.2 battsaver I can see it underclock often and it seems to run cooler temperatures :)

Not sure why the extreme didn't act the same way, maybe I'll try it again...
[Thunderbolt Android Development] Imoseyon:
that is weird. Go back to extreme and run it for an hour or so. And then send me the output of /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state ?
[Thunderbolt Android Development] want a droid:
Tried running 1.92X, but got a reboot. I'm going back to extreme for now.
[Thunderbolt Android Development] infinite_loop:
What's the recommended governor for best battery life?

Currently using smartass with 184/1.018.
[Thunderbolt Android Development] IvanNCase:
I've noticed that sometimes the first time I boot my phone after flashing a new version of the kernel it doesn't seem to sleep at the lowest slot but once I reboot once it seems to fix it.
[Thunderbolt Android Development] Imoseyon:
I bet that's what happened! Can you guys let me know which ROM you're on when this happens?
[Thunderbolt Android Development] want a droid:
You all are in for a treat with 2.3!
[Thunderbolt Android Development] IvanNCase:
I'm running the leaked update but I flashed my radio back too the one that shipped because of reboots.
[Thunderbolt Android Development] hyatari:
Can you add a aosp kernel that doesn't lock the CPU to lowest speed? I'm not sure but I think its causing issues with subsonic while downloading music when the screen goes off. The download tends to stall until I turn the screen back on and would like to see if this is the issue.

Edit: nvm ill try drods kernel and see if it works first.
[Thunderbolt Android Development] JonKyu:
Because of his tweaks all governors give about the same battery savings. I'd stick to interactivex personally but if you don't like that one smartass should be good.
[Thunderbolt Android Development] cmo220:
I've almost always used interactivex too. Just curious though imoseyon. What are the exact settings you prefer? Gov, speeds, version?
[Thunderbolt Android Development] infinite_loop:
Yeah...would be interesting to know what imoseyon himself likes :)
[Thunderbolt Android Development] infinite_loop:
Haha..maybe we should have read the OP :P:

interactiveX - it's the interactive governor from CM, but I added suspend/wake logic so when the phone screen is off it runs at 246Mhz. Also, I modified its code some more to minimize unnecessary cpu spikes above 1.8Ghz if you happen to be running one of my 1.92 kernels. Most tbolts are unstable above 1.8Ghz, and it's the quick jump above 1.8Ghz that usually locks up the phone. It will hit 1.92Ghz only when it makes sense (ie. sustained high load). This is my favorite governor - perfect combination of speed and power efficiency.
[Thunderbolt Android Development] WillTheGreat:
Just installed the extreme, so far so good.
[Thunderbolt Android Development] staveandor:
Anyone else not able to connect to WPA2 using the newest 1.92X?
[Thunderbolt Android Development] NetworkPIMP:
yup... in fact, it killed my access point repeatedly.

I only noticed because I just got new AP's today for the house, and whenever I'd bring my phone onto the new AP, within a minute the AP'd reset itself.

I changed over to Adryn's BAMF 4.4.7 and all is right with the world.

So... your complaint, plus my experience = 1.92X v2.2.0 DoS'd my AP...

will wonders never cease!?

(I offer you no definitive proof other than the deduction that when I switched kernels, the resetting stopped... I have not put 1.92X back to see if I can kill it again - I may do that later tonite after the wife wraps up her work email and Facebook-whoring... I value breathing.)
[Thunderbolt Android Development] Imoseyon:
Hmm this is the 2nd time i've heard this problem. What make/model is your AP?
[Thunderbolt Android Development] xCHPx:
on v2.20 extreme with Tesla. My phone is now flying and saving battery. Amazing work.
[Thunderbolt Android Development] LexusBrian400:
Imoseyon, Do you plan on updating your kernels in Kernel manager please?

Greatly appreciated.

Thank you
[Thunderbolt Android Development] NetworkPIMP:
It's a DLink DAP-2553 ...
[Thunderbolt Android Development] staveandor:
I can confirm that enabling wifi on the 1.92X kernel killed my access point/router as well.

My router is a Linksys WRT54GS v7.
[Thunderbolt Android Development] PineTre3:
okay dumb question, when it says "may not work for everyone" how do we know it worked?
[Thunderbolt Android Development] BennyJr:
U get pass the bootanimation

Im at 20% and my estimated life is 7hrs...this kernal rocks. I was at 65% earlier and it said i had 1day left
[Thunderbolt Android Development] staveandor:
If your phone boots, it worked. Or at least, partially. Watch for reboots/FC's/lock ups.

If it doesn't boot, flash another kernel or restore a backup.
[Thunderbolt Android Development] Imoseyon:
You guys running stock firmware or dd-wrt (or something else)?
[Thunderbolt Android Development] Pithism:
for new sense roms, whats the difference between lean and special?
[Thunderbolt Android Development] Pithism:
whoops nm didnt read the op well enough
[Thunderbolt Android Development] BennyJr:
Voltage. Thats the main difference between all of them but also clock speed.
[Thunderbolt Android Development] Imoseyon:
v2.4 SENSE (5/10/11)

- combined all my kernel flavors into one, speed/voltage can be controlled by speedtweak.sh script,

- added vdd_levels support (code from snq- via adrenalyn's git),

- kernel upgraded to 2.6.35.13. BOOYAH

http://xdaforums.com/showpost.php?p=12633597&postcount=1

TWO VERSIONS (SENSE)

1) lean: stripped down and minimalistic. undervolt/overclock/slots are now controlled by the "speedtweak.sh" script (more info below)

2) special edition: slightly less lean. Supports in-call recording, TUN, and EXT4. "speedtweak.sh" script also available.

speedtweak.sh (sense only for now)

This script will allow you to "transform" your kernel into normal, extreme, 1.92, 1.92X and battsaver versions (ie. it allows you to control speed, voltage, and slots to a certain degree). Once you run the script, everything will be self-explanatory. To run the script:

1) Open Terminal Emulator (install it from market if you don't have it).

2) Type "su" (without quotes) and hit enter.

3) Type "speedtweak.sh" (without quotes) and hit enter.

Again, if you have issues with 2.4 go back to previous and report here.

(Sorry if you prefer having separate flashable versions - i believe learning how to use the script should be trivial for most of you, and maintaining 2 instead of 5 will allow me to work faster.)

I'm going back to CM7 tomorrow!
[Thunderbolt Android Development] staveandor:
Running stock firmware. I have too many non-techies in this house to deal with the router being down long enough to flash DD-WRT... lol.

I'll update the kernel and try this script when loaded to see if I get different results using different "flavors". I do have to say 2.2 1.92X was the coolest my phone has run and seemingly the best battery life I've had so far.
[Thunderbolt Android Development] raziel36:
I pulled the call recorder from dasbamf, and would like to test on CM7. I know you won't officially work on AOSP during certain times, so any way for you to add the code to the existing AOSP kernel and let me blind-test it? I'm crazy like that lol
[Thunderbolt Android Development] Auronis1:
I use perfect storm 1.3, I've been running 2.2.0 battsaver all evening here's the file. I noticed my cpu usage at 90%+ a lot when the phone was idling, and averaging 90 F with just some texts.

Also tried a reboot, sometimes after a reboot it will underclock and after an hour or so it will stop underclocking and start running up usage and temp again, not sure if there's some app or widget I have that's causing the problem but 1.2.3 runs cool and underclocks as much as possible.

I'll switch extreme back on and send you that too.

Having trouble copying that file onto my sd card in root explorer, couldn't upload either. Stats are:

184320 0

245760 40831

368640 31980

768000 7409

1017600 105597
[Thunderbolt Android Development] staveandor:
Flashed the 2.4 lean kernel, modified to 1.92X, wifi works properly.

Now if I could just get 4G to not drop connection randomly...
[Thunderbolt Android Development] Nikolai2.1:
I cant figure out how to set the voltages. And when i select battery saver. going to setcpu just shows it at extreme
[Thunderbolt Android Development] infinite_loop:
Does v2.4 support 184MHz slot on any of the settings?

Noticed the enable low .zip was removed...
[Thunderbolt Android Development] BennyJr:
Ok i ran the script and set it to extreme but in setcpu i can still clock to 1.92...
[Thunderbolt Android Development] NetworkPIMP:
Latest stock...

--

via XDA Premium on my TBolt.
[Thunderbolt Android Development] Imoseyon:
When you run setcpu you can still see all the speed slots, and manually set min and max slot. speedtweak.sh will alter the voltages for each slot, and then put a "soft limit" on the max and min. The only way you can change the min and max again is by moving the slider on setcpu or by running the script again.

In other words, you can see all the speeds but the phone will not use the slots unless you tell it to using setcpu. Use "8) View current settings" to verify. I hope this makes sense...

That is built into the script now. Check options #6 and #7 on the bottom?
[Thunderbolt Android Development] BennyJr:
Oh ok in that case its working here well. I like the script man! good job
[Thunderbolt Android Development] Nikolai2.1:
I like it... but is there still no way to set custom voltages? Like the ones i showed you
[Thunderbolt Android Development] Imoseyon:
Ah yes, you set it exactly the same way. :) The file is /etc/init.d/01vdd_levels.
[Thunderbolt Android Development] FoxRacR17:
Would like to know this also, as my phone can handle slightly less voltage then your extreme version of the kernel. I love your kernel and the interactiveX but i like super low voltages more :)
[Thunderbolt Android Development] FoxRacR17:
perfect! Thank you so much!
[Thunderbolt Android Development] THATTON:
Imoseyon your servers are ssllooowwwww right now? 30 minutes to download a 3.0 mb file? IDK man. I like the new features though.

Also, without running the script at all will we run at stock voltages or will it be undervolted still?
[Thunderbolt Android Development] Nikolai2.1:
i like it! thanks man im gonna go do that right now ;)
[Thunderbolt Android Development] Kroaker:
If you don't tweak it, what is the default setting?
[Thunderbolt Android Development] Imoseyon:
Oh really? Damn. Need to find another service for next release. Thanks for letting me know. I'll set up a mirror right now. EDIT: mirror is set up!

It's "normal".
[Thunderbolt Android Development] raziel36:
Pushed the call recorder to system/app/ and set permissions accordingly. Upon reboot, it immediately force closes, so I'm thinking the app either works with certain Sense elements or the kernel not being written for it's use causes it to force close. I'm hoping it's the latter, and you adding the code will resolve the FC. Also tried fixing permissions in CWM, to no avail.
[Thunderbolt Android Development] BennyJr:
How do u get into the voltage tweak part? Im curious.
[Thunderbolt Android Development] FoxRacR17:
have you tried this: extract the contents of the callrecorder.apk file, inside there should be a folder with two files, one called liblame.so and the other called libvoix.so, adb push both of those files to the /system/lib. Then reboot your phone and hopefully that will work for you like it worked for me :)
[Thunderbolt Android Development] JonKyu:
You have to manually modify the file in the directory above in imoseyon's post. It's a post with etc/init.d/ beginning.

@imoseyon

I'm guessing that ext4 support and tweak is similar to adrynalynes kernels? Lol awesome job to both you guys with your kernels.
[Thunderbolt Android Development] Imoseyon:
You did use the sp version right?

You need to mount system rw and modify the /etc/init.d/01vdd_levels file manually.... I'd only recommend doing this if you're super comfortable.
[Thunderbolt Android Development] 52brandon:
easiest way is in root explorer, mount and use their text editor

and by the way, love the new kernel/script etc. Cant wait to tweak and play with it
[Thunderbolt Android Development] Nikolai2.1:
Imoseyon, when i change the voltages and reboot, the 01vdd file shows the modified ones, however the command line when choosing option 8 shows your voltages. is this normal? im assuming you have them predefined to show your voltages in the command line.

I know it works though, because i had a lock up once :p

Ill have a final voltage table out soon so show you guys :D
[Thunderbolt Android Development] Auronis1:
2.2.0 extreme, did an extra reboot and ran for an hour or so, I used no frills to enable 184, just texting

http://www25.zippyshare.com/v/31893287/file.html
[Thunderbolt Android Development] PineTre3:
is the "lean" kernel ext4 as well?
[Thunderbolt Android Development] JonKyu:
Please do! I'd like to try your voltage settings to see if mine can handle it. One question is if my phone bootloops because of it how would I revert changes?
[Thunderbolt Android Development] Nikolai2.1:
put it into recovery, then pull the file and modify it with a text editor on your computer. Then push it back. Im testing some extremely extreme low voltages right now, looks promising:)
[Thunderbolt Android Development] FoxRacR17:
It shows my changes after a reboot and i do option 8 :cool:
[Thunderbolt Android Development] raziel36:
This worked.. thanks.

@Imoseyon, I'm on CM7.. care to shoot me a modded kernel to test?(even if untested by you)
[Thunderbolt Android Development] Nikolai2.1:
Hmmm what exactly did you do? Did you modify both the /etc/init.d/01vdd_levels, and /system/etc/init.d/01vdd_levels?

Now im beginning to think that lock up was a coincidence...
[Thunderbolt Android Development] FoxRacR17:
Just edited the /etc/init.d/01vdd_levels using the text editor in root explorer, saved & exited, then rebooted the phone. Then when it started back up i went into the terminal emulator in the bamf toolkit and ran speedtweak.sh and chose option 8 and it showed the voltages i set
[Thunderbolt Android Development] NetworkPIMP:
I'm assuming market/open Wireless Tether app doesn't work with this kernel because TUN is left out - but does the stock Hotspot app still function?

EDIT: Yup - it does... I'm on it right now.
[Thunderbolt Android Development] schwab16:
What about interactive, how does it compare to the other governors?
[Thunderbolt Android Development] NetworkPIMP:
REQ: different versions w/ different gov's / and maybe a slightly chubbier version?

I don't even know if this is possible, BUT...

in the interests of keeping it lean, what about different versions with different govs'?

so like, a version that just has ondemand & performance, or one that has just performance and interactive, or (my personal pref - if tweaked correctly) a version with just performance and smartass

not sure if this is even possible...

ALSO, what about a not quite as "lean" one, but - a "slim" that has TUN in it so WiFi tether works - hotspot works now, but on 5/15... well... you know...

Past that, I'm VERY impressed... I'm running the 1.92ghz version, and my phone is fast and cool... tho, it's ALL over the place on freq's... never settles. hence the request for some options with respect to gov's...

Thanks for all you guys do!
[Thunderbolt Android Development] adrynalyne:
Tun has nothing to do with tethering. It has to do with vpn.
[Thunderbolt Android Development] NetworkPIMP:
I stand corrected... my brain = broken.

Would still like to see maybe a "slim" version too ;)
[Thunderbolt Android Development] inline6power:
tether works just fine
[Thunderbolt Android Development] Imoseyon:
It's definitely possible but it's a pain to maintain a lot of different versions.

I am working on completely overhauling ondemand governor code, so expect something soon.

leanKernel + Tesla coil
[Thunderbolt Android Development] Imoseyon:
Yup

leanKernel + Tesla coil
[Thunderbolt Android Development] Spaniard85:
Thanks. I'm on the updated version, but I've still gotten a hang. Every time I get a call while my phone is asleep it'll hang. I've been trying to run at 1.92 on demand. Should I try reflashing the kernel and wiping dalvik or clearing data and cash?
[Thunderbolt Android Development] azturbomini:
Your phone may not handle 1:92GHz. I would try turning the speed down a bit. (That's what I had to do...)
[Thunderbolt Android Development] Spaniard85:
Quite aware of this, so I've been running at 1.4 most of the day. Just looking to see if I've really reached the limit of my device. :p
[Thunderbolt Android Development] Imoseyon:
Try to reproduce the hang by stress testing? One way to do it is lock the phone at 1.92 using setcpu and then run its stress test for at least 5-10min. If it hangs during testing you know that your phone is having issues with 1.92Ghz.
[Thunderbolt Android Development] crashdogy:
my phones stable but cant get higher than 1800 on smartbeach and 2500 quadrant what rom are you using ?
[Thunderbolt Android Development] jlevy73:
I'm using Das Bamf. When running quadrant set your min/max to 1.92 then governor to performance. Run quadrant at least 3 times.
[Thunderbolt Android Development] Imoseyon:
v0.6

*NEW* on-demand governor, backported from linux-2.6.39-rc2, which includes massive amount of improvements and fixes. When I compared the code from the latest linux source, i could not believe how poorly on-demand governor code was written in 2.6.32.

If you're an observant/perceptive type, you may notice some differences...
[Thunderbolt Android Development] jlevy73:
Thanks, look forward to trying it out.
[Thunderbolt Android Development] jlevy73:
v0.6 1.92ghz kernel still showing that it's 2.6.32.21.
[Thunderbolt Android Development] Imoseyon:
Oh the kernel version is the same. The only thing that's new is the governor.

leanKernel + Tesla coil
[Thunderbolt Android Development] NetworkPIMP:
so do I need to do the enable-swap.zip? or is it already baked into the kernel?
[Thunderbolt Android Development] v4npro:
Just to clarify again, might of missed it, but I don't need setcpu right?
[Thunderbolt Android Development] JonKyu:
Sweet thanks! Looking forward to your results.
[Thunderbolt Android Development] Nikolai2.1:
Interesting...I can't replicate, but it shows my voltages in both of the files even when I edit the one (normal), so I know it's working. What is everyone else getting? Imoseyon?
[Thunderbolt Android Development] Nikolai2.1:
REALLY Low Voltages(Not for the faint of heart)

Okay guys something is wrong. I set all the voltages to 750 for every slot.. and the damn thing still booted.... obviously theyre not sticking, and the terminal is telling me the truth
[Thunderbolt Android Development] Imoseyon:
Hmmm paste the content of the /etc/init.d/01vdd_levels file? Make sure the permissions are correct, otherwise it won't be executed at boot.

After reboot, speedtweak.sh option #8 will show the new settings.
[Thunderbolt Android Development] JonKyu:
Can you double check the script in that file? My guess something might be missing causing it not to write to the actual voltage file.
[Thunderbolt Android Development] Nikolai2.1:
This is what i used to test the phone to see if it would boot, and it did. The file stays like this after reboot, but doesnt show in the command line (shows your voltages) should i fix permissions with rom manager or is there something specific? im on windows so chmod probably wont work

#!/system/bin/sh
sysfile="/sys/devices/system/cpu/cpu0/cpufreq/vdd_levels"
echo "184320 750" > $sysfile
echo "245760 750" > $sysfile
echo "368640 750" > $sysfile
echo "768000 750" > $sysfile
echo "1017600 750" > $sysfile
echo "1222400 750" > $sysfile
echo "1408000 750" > $sysfile
echo "1593600 750" > $sysfile
echo "1766400 750" > $sysfile
echo "1920000 750" > $sysfile
echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1920000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Thunderbolt Android Development] Imoseyon:
That tells me that the speed steps are working fine. You were probably using the phone moderately right?
[Thunderbolt Android Development] Imoseyon:
Paste the output of:

ls -l /etc/init.d

Also, you can execute the file manually without having to reboot by doing "sh /etc/init.d/01vdd_levels".
[Thunderbolt Android Development] Nikolai2.1:
Before i do that, you were right, the permissions were different because i had been pushing the file from my computer to the phone. Ill edit them in the phone this time after i fix it and see what happens. and thanks ill try that after this :)

edit: im just gonna reflash the kernel and start over
[Thunderbolt Android Development] JonKyu:
Is there an easier way to revert changes if you bootloop?
[Thunderbolt Android Development] 52brandon:
lol, I was gonna say. I tried going down 10 on the 1408 slot and it would freeze up on me. If you got down 100, that would be a step past amazing
[Thunderbolt Android Development] 52brandon:
make a backup and advance restore in recovery and only restore boot...
[Thunderbolt Android Development] Nikolai2.1:
or reflash the kernel
[Thunderbolt Android Development] 52brandon:
I figured sometimes files can get left behind when just flashing. But thinking about it, this kernel should replace all of the files
[Thunderbolt Android Development] tats_06:
Imoseyon,

Am I ok to leave the current kernel? I don't want to mess with scripts and if there are no significant changes/tweaks, I think I am good. :confused:
[Thunderbolt Android Development] Imoseyon:
You can stay at the current version, but I'd suggest flashing 2.4 and not run the script - you will be running the "normal" flavor and can also take advantage of the newer code.
[Thunderbolt Android Development] Nikolai2.1:
you have to down and up in increments of 25
[Thunderbolt Android Development] tats_06:
Oh, perfect! That's the one I am running (the previous version). I will do as you said. Did you mean the lean or special one? Thank you. :)
[Thunderbolt Android Development] TsaiKimon:
Imoseyon, you are the man. thanks a lot for your hard work and the anal retentive organizing side of me thanks you for combining all the kernels and working off a script. Again, thanks you.

On a total side note, I've been wondering what the significance of your username is. I think of goku with eye-shadow every time i read it. EMO-Saiyan! LOL
[Thunderbolt Android Development] Nikolai2.1:
Guys i give up on trying this voltages. I could get some serious low volts with 245 being the starting point, but it seems like 184 is killing me, but im trying to use it.

Lemme know what you guys come up with and ill try myself, until then ill be using battsaver.
[Thunderbolt Android Development] JonKyu:
LMAO! I was wondering too, I thought of saiyan too. For some reason though Imoseyon seems like a Korean word to me. Haha