yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Imoseyon:
I believe that. Interactive is tuned a bit more for performance, so if you use your phone a lot you might be better off with ondemand or smartass, but if you use your phone less often then i think interactive is best.
[Thunderbolt Android Development] Richpopski123:
Your statement is correct.

Nothing wrong with trying to improve the improved! Thanks again!
[Thunderbolt Android Development] lilpeezy23:
Ok cool. That's what I've been doing and definitely seeing better battery. Should probably put my phone down more though :)
[Thunderbolt Android Development] corenojoe:
Quick question: I see the new v1.0 has a new governor and a few other tweaks. However I have been getting amazing battery life with v.92 extreme. So, do you think its worth while to go to v1.0 or should I stick with what's working? Just wanted a little advice.
[Thunderbolt Android Development] Imoseyon:
I'd try v1.0 and see if you get even more amazing battery life. :) If not you can always flash back to v0.92.
[Thunderbolt Android Development] pinhead875:
1. Make a backup

2. Try out 1.0

3. If you like 1.0, profit

3a. If you like .92, flash back

4. ???

5. Profit more
[Thunderbolt Android Development] Imoseyon:
I approve these steps! :D
[Thunderbolt Android Development] Imoseyon:
a quick poll for advanced users

Would you guys prefer if the governors:

1) lock at lowest clock speed, or

2) have a bit of breathing room and lock at 369Mhz and below

when screen is off?
[Thunderbolt Android Development] 4dfl4:
I would prefer lock at lowest speed since its been working for me fine and for battery life
[Thunderbolt Android Development] dickenam:
What would the advantages of letting it breathe and lock in at a slightly higher freq?
[Thunderbolt Android Development] hyatari:
I'd prefer to have a higher lock speed but ill test this out and see how it goes with music streaming while screen off etc. Also, I can't get swap enabled with.plainjane rom by jcase. I've flashed the zip a few times but no go. Worked previously on liquids rom. Looking at info in setcpu and not seeing any swap available.
[Thunderbolt Android Development] JonKyu:
I prefer maximum battery saving lol
[Thunderbolt Android Development] patdroid1:


agreed i stream music every day and might need just a little breathing room...shouldn't kill battery savings.
[Thunderbolt Android Development] corenojoe:
It would depend on if three any lag when waking.
[Thunderbolt Android Development] mbh87:
My vote.

10 char.
[Thunderbolt Android Development] Richpopski123:
My advice... Try them all! Doesn't take much and you can always go back.
[Thunderbolt Android Development] Richpopski123:
agreed i stream music every day and might need just a little breathing room...shouldn't kill battery savings.[/QUOTE]

My vote!
[Thunderbolt Android Development] Imoseyon:
Thanks for your votes guys. What I'm going to do is keep interactiveX and smartass locking at the lowest frequency, and then have ondemandX lock at 2nd lowest and give it the ability drop or raise at or below 2nd lowest.
[Thunderbolt Android Development] patdroid1:
more options....love it!!! of course now i have to make a decision on which governor to use?????
[Thunderbolt Android Development] mbh87:
Would it be possible for someone like me make the governor default to smartass without the need of setcpu?
[Thunderbolt Android Development] Imoseyon:
Yep. Impossible to type the command on the phone so I'll post instructions later today. I'll also make three zip files that you guys can flash to choose your own default governor.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] ANDROID 3G:
When flashing these kernels do I just let them be or do I have to use them in conjunction with SetCPU and if so what settings are recommended?
[Thunderbolt Android Development] mbh87:
Awesome, thanks.
[Thunderbolt Android Development] Nikolai2.1:
Loving the smartass governor so far! Have yet to see battery life, but do like it locking at the lowest speed to save battery. Performance is great and no lag so far!
[Thunderbolt Android Development] ANDROID 3G:
Anyone?
[Thunderbolt Android Development] Nikolai2.1:
default they will boot at 1ghz i think with the ondemand governor. Thats really all you need but if you want setcpu then i would use smartass and keep the frequencies the same. overclocking in my opinion is a waste on the bolt, itll just ruin your phone faster
[Thunderbolt Android Development] Imoseyon:
Default for v1.0 is interactiveX which I believe is the best of both worlds in terms of speed and power efficiency. It's certainly faster than Smartass.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] pinhead875:
I love how these are also updated in Kernel Manager. Nice job, and thanks.
[Thunderbolt Android Development] Nikolai2.1:
doesnt it use more power though?
[Thunderbolt Android Development] Imoseyon:
Maybe. Wouldn't surprise me. ;)

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] jlevy73:
This is my output from dmesg, not sure exactly what it means:

#dmesg | grep imosey

<6>[11356.904937] [imoseyon] interactive awake at 1408000

<6>[11453.813751] [imoseyon] interactive suspended at 460800

<6>[11456.868164] [imoseyon] interactive awake at 1408000

<6>[11464.054229] [imoseyon] interactive suspended at 460800

<6>[11482.498535] [imoseyon] interactive awake at 1408000

#
[Thunderbolt Android Development] azturbomini:
OP:

I have never seen a developer that was so attentive to the feed back they get as you are. Your passion for perfection show in the kernels your developing and I really appreciate what your doing. The bottom line is, my phone operates much better than stock.

Thank you!
[Thunderbolt Android Development] patdroid1:
ha ha seriously it's pretty awesome...it's like we have our own personal dev. helps feed my addiction for crackflashing too!!!
[Thunderbolt Android Development] Veridor:
Rocking the battery life with v1.0 battsaver on smartass and Perfect Storm ROM. Awesome work. Been off charger about 3 hours with 4G left on and still have 78% on stock battery.

Sent from my HTC Thunderbolt using Perfect Storm themed XDA App
[Thunderbolt Android Development] Nikolai2.1:
Lol well I switched to interactivex because smartass started giving me hiccups. Liking it so far!
[Thunderbolt Android Development] jlevy73:
The interactiveX has rockin performance although seeing a hit on battery life. That's a compromise I'm willing to live with :)
[Thunderbolt Android Development] jlevy73:
Where is your donate link kind sir? I think there is more than one of us who would like to thank you for all you're hard work
[Thunderbolt Android Development] Imoseyon:
azturbomini: thanks.

jlevy: yeah that's pretty much the output you should expect. All it really tells you is the clock speed when you sleep and when you wake. Nothing earth shattering. :)

If you guys really want, you can donate to your favorite charity, or me via paypal: imoseyon@gmail.com
[Thunderbolt Android Development] jlevy73:
Sounds good, thanks
[Thunderbolt Android Development] corenojoe:
Early indications are I'm getting slightly worse battery life with v1.0 than I was with v.92, but we will see. I'll keep testing it out.
[Thunderbolt Android Development] jlevy73:
What governer are you using?
[Thunderbolt Android Development] JonKyu:
Hmm 5hrs 44min and 80% pretty awesome for moderate usage! I switch between smartass and interactivex on the extreme kernel.
[Thunderbolt Android Development] tu3218:
which kernel are you using? Wow my bad, just saw you mentioned it at the end lol. I'm about to flash the extreme an hoping for similar results.
[Thunderbolt Android Development] corenojoe:
Smartass clocked at 1200
[Thunderbolt Android Development] Imoseyon:
Make smartass default!

Here it is guys. Flash this zip and smartass will be your new default governor. I'll have two more zips for the other two governors posted on the first post along with v1.1 this weekend.
[Thunderbolt Android Development] pinhead875:
Quick request: When you guys state your battery life, please mention whether you are on 3G, 4G, or wifi. If you're on a mix, how long for each?

I have 4G coverage everywhere here in Denver, but wifi at work and home. I just flashed 1.0 battsaver, we'll see how this goes.
[Thunderbolt Android Development] Imoseyon:
A quick note on battery life testing

hey guys,

So battery life testing is highly subjective and also highly unreliable in general. I would try the following first:

1) wipe battery stats

2) fully charge battery

3) make sure that the conditions are exactly the same on all tests

4) try the test several times (once of twice will not give you an accurate indication).

Battery life depends on so many different factors, testing for it is really hard. For instance, your weather conditions could affect the cellular radio signal to drain battery faster, especially 4G. So i think it usually takes a few days of testing to get a decent reading. IMHO anyway. :)
[Thunderbolt Android Development] jlevy73:
I have a question for you. In the Nexus S kernel the ratio between bus speed and gpu performance is 1:1. With the Nexus S, say 250mhz would gives you 60+FPS on benchmarks like nenamark, where on the bolt 47fps is the highest I have seen. Does the Adreno 205 allow for alteration to the bus speed? If so, this might be a way to push GPU performance, especially FPS higher. I'm always looking for ways to push the envelope a little further but I am not that familiar with Adreno code to make a knowledgable assessment. Curious to know your thoughts. Thanks
[Thunderbolt Android Development] tu3218:
hey lmoseyon, besides clock speed whats the difference between extreme and battsaver. Extreme states that its super-undervolted and battsaver is ultra low volt. I typically don't really care about overclocking as I think 1ghz is fast enough. I'm looking for best battery life, will these two kernels offer similar results? Not sure between the super-undervolted and ultra low volt and what difference they'll make.
[Thunderbolt Android Development] Imoseyon:
I haven't actually looked at the GPU code at all. Let me take a look at it and see if I can find a way to tweak/optimize it before the next release.
[Thunderbolt Android Development] jlevy73:
Thanks.....
[Thunderbolt Android Development] Imoseyon:
Battsaver is undervolted a little bit more than extreme, but the biggest save will be that it is capped at 1Ghz. With extreme you will be running frequently at 1.41Ghz (unless you manually cap it using setcpu or something). In the next version I will attempt to close the gap between battsaver and other undervolt versions at least below 1Ghz but messing with undervolting is tough since one little tweak could benefit one group while harming the other.
[Thunderbolt Android Development] tu3218:
Okay cool, thanks for the info.
[Thunderbolt Android Development] asenduk:
running v1.0 - 1.92X @ 1408 max 245 min, with interactiveX gov

i like :D

donation sent!
[Thunderbolt Android Development] LeoD:
Thanks again imoseyon, I'm at 11 1/2 hours with light/mod usage today and currently at 50% battery with your extreme ondemand kernel with np.
[Thunderbolt Android Development] Imoseyon:
holy crap thanks!
[Thunderbolt Android Development] BSDADON:
I'm running 1.0 battsaver with on demand and screen off 245. I'm losing like 12% an hour when I'm not using the phone. I'm wondering if I should wipe my phone and start from scratch because seeing all these people reporting such great battery life while I can barely use my phone is frustrating. Do you recommend I do that or try a different kernel?
[Thunderbolt Android Development] Imoseyon:
need help testing new overclock code

those of you that are running v1.0 1.92X successfully, could you help test this version?

http://cl.ly/62bO

Let me know if it hangs or reboots more often than the version you've been running. I can't run 1.92Ghz reliably on my phone so it's hard for me to test.

thanks!
[Thunderbolt Android Development] azturbomini:
I can but I run mine at 1280mhz using on demand not wide open... Whatcha think?!
[Thunderbolt Android Development] JonKyu:
I got one reboot on the extreme kernel after 14hrs, %40 battery left, on smartass (moderate usage, mostly wifi a little 3g). Just wondering if the governors could cause a reboot? Like how quickly it ramps up or something? If it reboots once in a while I think I could live with it lol.
[Thunderbolt Android Development] kman100:
I'm running your v1.0 1.92x, I can have it clocked at Max for like 1 or 2 quadrant tests before it freezes out.
[Thunderbolt Android Development] jlevy73:
Be happy to. Will let you know how it runs.
[Thunderbolt Android Development] mcseufer:
I've been running 1.41GHz Extreme v1.0 and I've gotten 3 different re-boots. Once was after I disconnected from my car dock and twice just swapping from screen to screen. I've been running your kernels for awhile now.

I did turn SetCPU off (well, at least I unchecked "start at boot"). Not sure if that caused the instability.

m.
[Thunderbolt Android Development] jlevy73:
By far your fastest kernel yet. So far everything is running quite smoothly. Got a 3225 on Quadrant and a 64 on Linpack. I like the additional clock slots you added.
[Thunderbolt Android Development] ikon8:
Your phone can't handle the extreme version's undervolt, try the normal kernel.
[Thunderbolt Android Development] azturbomini:
I am freezing and or rebooting at 1766mhz and above while running Quadrant on ondemand.
[Thunderbolt Android Development] corenojoe:
I know battery life is subjective and all and consider the fact that about 5 hours of this was while I was sleeping, but I thoughtit was still cool enough to show you guys. This is with perfect storm v1.3 running v1.0 extreme kernel capped at 1280mhz in a 4g area for about 15hrs and 3g for the rest with moderate to frequent use:
[Thunderbolt Android Development] Imoseyon:
Same here. Now the big question is, were you able to run the previous version at 1.92ghz reliably? Just wanted to see if the 1.1test version is less reliable at top speed or not. thanks!
[Thunderbolt Android Development] r1tony:
How much can we squeeze without worrying about freezes and reboots?
[Thunderbolt Android Development] Imoseyon:
That depends on your phone. Some phones are more tolerant to overclocking/undervolting than the others... My phone does not run reliably above 1.8Ghz no matter how much juice i give it.
[Thunderbolt Android Development] asenduk:
had 1 lockup/reset while trying to adjust speeds in setcpu with v1.1 after install but its working great since then.. this happened before with a previous version too, but forgot which one
[Thunderbolt Android Development] azturbomini:
I think our phones are pretty much the same. I froze at higher speeds with the previous version too while running quadrant.
[Thunderbolt Android Development] Imoseyon:
You and I have to come up with a plan to get jlevy and asenduk to trade with us!
[Thunderbolt Android Development] patdroid1:
i have 10 friends and family (literally 10) all with the thunderbolt and i would love to get cracking on all of them and see how they all respond to different voltages and overclocks but none of are down for it...so frustrating!!!! still i'm happy mine at least runs at 1.92 but really only stable to about 1.8.

i could be your full time alpha tester with 10 phones to sample from!!!
[Thunderbolt Android Development] azturbomini:
No kidding. Its pretty wild how phones differ so much. I can understand how a car for instance might run a little better than the next being they are mechanical but I can not get my arms around electronics and why some TB,s can handel the faster clock speeds. I set my TB above 1800 and it's instant lock... Oh well lol.
[Thunderbolt Android Development] mbh87:
Gave you as many thanks as I could, battsaver kernel has been running great. I was skeptical to try them and now I'm too skeptical to try another.
[Thunderbolt Android Development] Richpopski123:
I was not, set it a slot lower.
[Thunderbolt Android Development] asenduk:
my phone runs 1.92 just fine but it does lock up and resets when I play around with the min and max frequency in setcpu.. it seems like certain combinations just wont play along nicely
[Thunderbolt Android Development] cmo220:
I just wanted to let you know how much I'm loving this new kernel. I'm using extreme with it overclocked around 1.2. Using the interactivex governor. Seems very fast and great on battery. I'm not using it too much but I'm at 15h 58m off charger and have 70% left. Only 2 hours of awake time but that's still really good. I've been on wifi the whole time but still don't usually last this long.
[Thunderbolt Android Development] Imoseyon:
Just a quick update. My nature is getting to me and i'm redoing my overclock code again. This is taking a long while to perfect since i have 5 different versions. ;)

Jlevy, I'm getting about 47 fps - that's what you're getting as well right? I took a cursory look at kgsl_adreno205 gpu code, and unfortunately driver code looked pretty greek to me, but I will take a deeper look soon.
[Thunderbolt Android Development] Imoseyon:
I think i figured out why that happens. Hopefully v1.1 release will fix that.
[Thunderbolt Android Development] Forgetfull:
Imoseyon-

Did you make any similar kernels for the Incredible? My thunderbolt is rocking on your extreme (battery life) and I'd like my gfs inc to do the same.
[Thunderbolt Android Development] Imoseyon:
Nah my android kernel career began with the tbolt. :)
[Thunderbolt Android Development] cmo220:
This is very nice. I hope you make these for AOSP once that's running!

v1.0 Extreme

Overclocked 1.2

InteractiveX

Wifi whole time
[Thunderbolt Android Development] Forgetfull:
Display on time? Extended battery?
[Thunderbolt Android Development] Veridor:
This. That's insane battery life for a stock battery.

Sent from my HTC Thunderbolt using Perfect Storm themed XDA App
[Thunderbolt Android Development] pinhead875:
Yeah, show this screen from Spare Parts app.

This is me at 7 hours, wifi at home.
[Thunderbolt Android Development] cmo220:
I restarted to flash the radio settings. I can tell you I wasn't using it too much. My awake time was only between four and five hours. Still much better than I'm used to though. But it is stock battery.
[Thunderbolt Android Development] Imoseyon:
Spent the entire day trying to make 1.92Ghz run reliably on my phone. I'm not giving up yet!
[Thunderbolt Android Development] WormDoes:
I'm in your boat, man. I'm losing waaaay too much battery for the settings and setup I use. For instance, did a fresh wipe and install of BAMF and .9 normal, set the phone down at 33%, took a shower and when I got out 20 minutes later I was at 14%. This was on WiFi. No rogue app(s) gnawing at my battery, only thing syncing is gmail and FB (every 4 hours). When I had my Eris and Inc I would lose maybe 2% over 3-4 hours on the same network. I'm starting to think my TB is bunk :(

I'm going to test it for a few more days and if it's still this bad I'm going to try and get a replacement (my first replacement ever and this is my 3rd Android phone :eek:)
[Thunderbolt Android Development] y2ktibltd:
Imoseyon, I was able to run your 7.2 1.92x kernel with no problems but every revision since then has caused random lockups and reboots for me, even the 1.92 no extreme. Any chance you could repost your older versions or maybe make a version with the same voltage settings from earlier. Oh, and not that I don't appreciate your hard work already but drod2169's 1.8 kernel runs smartass perfectly. I'm two hours in and my battery has barely dropped 1%. Any chance you two could get together and work on the smartass for your kernel? Thank you again for all of your hard work!
[Thunderbolt Android Development] BSDADON:
Wow your battery loss was more drastic than mine. I actually wiped everything and started over this morning. I went a little over 10 hours with 3 hours of games, texts, and some web browsing. Sadly I had to shut off 4G to get that battery life. I also switched to smartass instead of on demand.
[Thunderbolt Android Development] Cadillac Johnson:
If it's any consolation, yours was the only kernel I could run that high without any issues..

I tried 1.92 Extreme just for the hell of it, expecting to have issues, but didn't have a single force close, freeze, nothing.. Even tried to make it freeze and couldn't. Ran Quadrant 8-9 times in a row, opening and closing random apps as fast as I could, even ran a stability testing app and just gave up after the battery got a little too warm for my liking..

Granted, IMO, I don't think anything above 1.2-1.3 makes any noticeable difference besides a temporary increase in Quadrant and Linpack scores.
[Thunderbolt Android Development] WormDoes:
What really made me wipe and reflash everything was this morning took off charger at 8:30, used the phone for about 30 minutes (FB, cpls texts, light browsing), shut WiFi/Sync off around 9:30 with 92%. Left my phone alone, literally did not touch it. Then I finally picked it back up at 3pm and I was down to 40% with nothing syncing, 30% display, no WiFi or mobile data. This is unacceptable, IMO. I got such good life from my Eris and Inc that this happening with such an awesome phone makes me want to put my head through a wall.

Oh, yea, if that wasn't bad enough, this and my other post's stats were both while using the 1700mAh battery. I'm convinced my phone is faulty, especially after seeing some of the life people are getting in here.
[Thunderbolt Android Development] Imoseyon:
wormdoes, are you doing any reboots? There's apparently some sort of bug in the firmware that messes with the battery stats. When you reboot, sometimes it drops anywhere from 5 to 25%. And sometimes your battery meter drops like 1% after 1 hour of usage. :\

BTW, my phone runs perfectly right up until 1.8Ghz and then gets a bit wobbly higher than that. I'm going to try to cheat a little by tuning the governors a bit.
[Thunderbolt Android Development] WormDoes:
Not an unusual amount. I mean after reflashing today I did have to do about 5 or so to get everything I wanted, but my last post, before I wiped and reflashed, I hadn't rebooted in a day or two.
[Thunderbolt Android Development] Imoseyon:
I looked at my code check-in history and the only difference between 0.72 and 1.0 in terms of overclocking/undervolting was the addition of another slot (1.79ghz). I think I might have undervolted that slot too much - hopefully 1.1 will fix that.
[Thunderbolt Android Development] PerCompLLC:
Where did you get a 1700mAH battery? The stock battery is 1400mAH, The Seidio Slim Extended battery is 1600mAH (although reviews indicate that it is probably really only 1400mAH), and the HTC Extended battery is 2750mAH.
[Thunderbolt Android Development] JonKyu:
I was reading that there was 1700mAH Chinese batteries, maybe that's what they're using.
[Thunderbolt Android Development] PerCompLLC:
Ahh. Personally I think I'd stay away from those...
[Thunderbolt Android Development] WormDoes:
1700mAh battery from HTCExpress
[Thunderbolt Android Development] v4npro:
got a reboot with 1.0 extreme version while web browsing with your govener. trying smartass now.
[Thunderbolt Android Development] jacobk:
been running the newest battsaver for a few days now and im finally getting some good battery life.
[Thunderbolt Android Development] caramanis:
Oddly enough, the problem resolved upon flashing another kernel.

Edit : Just reflashed your kernal and had the same SD card issue. Back to bamf kernal and all is well. Maybe it's ROM related (bamf 1.3.2)

Edit2: This problem is resolved in v0.3! Thanks.
[Thunderbolt Android Development] B3L13V3:
Imoseyon reporting back from testing...everything went smooth no reboots, quick and responsive but like two other gentlemen stated my apps on sd card were missing and I could not install apps as well, and when I flashed a different kernel those problems went away. Thank you sir and its definitely something to look into. I will also test further versions.