yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Imoseyon:
Sorry guys, fixed the sdcard issue. v0.3 is up on OP!

v0.3

- added MD back in (needed for a2sd) - slightly less lean now. :(

- undervolted the crap out of it especially lowest frequency which is where your phone spends most of its time. Let me know if phone starts rebooting or freezing often - that will tell me that i've gone too far. ;)

- added /tmp tmpfs support,

- disabled install-recovery so init.d scripts don't run twice by the ROM

BTW, if any dev wants compcache module let me know. I compiled it but won't use it for my kernel.
[Thunderbolt Android Development] Jaxidian:
I TOTALLY disagree on this. If you run with the Conservative governor, then you see a lot of time in the notches above minimum, which results in even more battery savings. On the other hand, I think the 20 various frequencies that some kernels have might be a bit on the high end, so I do appreciate some of them being pulled out.

Just my $0.02 worth. I run Conservative governor most of the time specifically for this reason - gives me extra hours.

That said, I've not flashed this kernel yet, so I'm speaking out of my ass to an extent.
[Thunderbolt Android Development] cmo220:
I've been running this kernel all day. The only problem I'm having is it usually doesn't unlock on the first swipe. I've tried conservative and ondemand. I'm not sure but maybe having another speed like 384 might fix that. Just a suggestion. Great work anyway.

Oh yeah, forgot to mention, same problem with the new update.
[Thunderbolt Android Development] Imoseyon:
That's interesting. I should test conservative a bit more. Do me a favor and post the content of this file: "/sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state" after running your phone for a few hours?

thanks,
[Thunderbolt Android Development] jlevy73:
Still observing battery life on v0.2, will wait until my battery dies to flash 0.3. Thanks for the continued updates :)
[Thunderbolt Android Development] Picao:
Tried to install apps and could not get any to install. Also apps that I had like Angry birds do not show up in the apps drawer. When I tried to install again I would get the message that it was trying to overwrite the app. I went back to another kernel and the apps showed back up. Strange that a kernel could remove apps.
[Thunderbolt Android Development] Imoseyon:
Did you try v0.3 yet?

leanKernel + Tesla coil
[Thunderbolt Android Development] houseboatwayne:
Running every test I can think of no problems found. File system showing. Charging battery to charge then I'll wipe bat stats and just run battery tomorrow :)
[Thunderbolt Android Development] jlevy73:
On v0.2 I got about 9 hours with moderate usage. Still have about 10% left but going to try out v0.3 and see how that fairs.
[Thunderbolt Android Development] jlevy73:
v0.3 has fixed the non-installing apps issue. I can tell you way UV 245mhz. I'm getting a little bit of a lag waking the device up. Might be a good idea to add another step up before the jump to 768mhz. Just a thought.
[Thunderbolt Android Development] Imoseyon:
alright, coming in v0.4!
[Thunderbolt Android Development] Exeodus:
This is the first kernal I have tried, running a stock rom right now. Definite speed difference, will report back on battery life. :D
[Thunderbolt Android Development] hyatari:
Running pretty sweet so far on liquids Rom. No wake issue for me as discussed previously. Will see in time how the battery life is. Nice to see you making a kernel now man. Keep up the good work.
[Thunderbolt Android Development] Exeodus:
Quick question, is the 1280 speed unvolted? , like less than 1024 on the stock kernel?
[Thunderbolt Android Development] two_cents:
wiped dalvik, flahsed then it hung on the boot screen for 3 min... looped to splash screen rebooted and hung again for 8 minutes... pulled the battery and reinstalled adryn 2.0... not sure why it would do this but it did... perfect storm 1.1
[Thunderbolt Android Development] Exeodus:
Don't wipe anything. Just flash the zip via CWM. That is what I did per the instructions in the OP.

Sent from my rooted Thunderbolt
[Thunderbolt Android Development] hyatari:
The battery temp doesn't appear to be displaying properly. Always reads 25.2 degrees at all times in set CPU. Anyone else seeing this? Not positive if its kernel related since I just got a new battery before flashing this kernel.
[Thunderbolt Android Development] adrynalyne:
Do you have this on github somewhere?
[Thunderbolt Android Development] tu3218:
Were you not getting good battery life at first? I flashed it Saturday night an I haven't been too impressed yet. Maybe it takes a couple days for results to show.
[Thunderbolt Android Development] Trevlo:
The 1.0 test kernel seems to be working for me at 1.92... but if I mess with setcpu too much it freezes and restarts. Also froze a couple times when playin games. Other than that keep up the great work!
[Thunderbolt Android Development] swimminsurfer256:
1.92X working great :) everything's so smooth and I've lost 8% battery in 2 hours of moderate use! *knock on wood*
[Thunderbolt Android Development] seang:
the normal kernel is giving me much improved battery life. usually this time of day i would be at 50%, now i am at 75%
[Thunderbolt Android Development] grynn15:
Just noticed this morning while using interactiveX governor (extreme 1.4ghz v1.0) that I was unplugged for more than two hours with no phone usage at all and my battery was still at 100%. Has anyone else seen this? I didn't bump charge or anything, just a normal day...

Not that I'm complaining. This kernel is awesome, I just didn't expect it to get awesomer a day or so after I flashed this version.
[Thunderbolt Android Development] WormDoes:
Ok, I don't want to jink myself, but I've been home all day on WiFi, I've been off the charger for 8 hours, light use, and I'm still at 91% :eek: I'm not sure what happened, but it's a pleasant surprise nonetheless. Running .9 normal, 1.24|245 conservative no profiles. I think my TB sensed, no pun intended, I was ready to kick it to the curb and finally decided to act right, lol
[Thunderbolt Android Development] cmo220:
Hahah. I told you all this kernel is great on battery life and sorta light usage.
[Thunderbolt Android Development] JonKyu:
Wow I flashed the 1.9ghzX kernel for fun and surprised to see my phone ran stable at 1.79ghz! it ran on 1.92ghz but rebooted when I started browsing.
[Thunderbolt Android Development] WormDoes:
I'm not sure if you're being sincere or sarcastic, but if you read my two previous posts I was losing insane amounts of battery with no use. IE: 50% in 6 hours with everything shut off and no use, 20% in 20 minutes last night on WiFi, so this is pretty outstanding as far as I'm concerned
[Thunderbolt Android Development] StephenMilone:
same here.. was watching a flash video via dolphin. Im going to switch governors too if thats all that would fix it.

plus every now and then my data just stops working unless i reboot or turn off/on mobile data...no idea if that could be kernel related?
[Thunderbolt Android Development] cmo220:
I was being completely serious. I had 40% battery yesterday after almost 21 hours off the charger. It was on light usage but much better than I'm used to. I'm a big fan of this kernel.
[Thunderbolt Android Development] cmo220:
The only time I lost a lot of battery without use was when I had deleted weather and news and things like that that sync in the background. For some reason on this phone it kept it in "accounts & sync" in the settings menu and I never unchecked them. Once I did it got better. Anyone having that problem should check that.
[Thunderbolt Android Development] pinhead875:
3G vs 4G is huge on battery performance, but nobody ever notes their data speeds when they state their battery performance.

3G/4G/Wifi?? Which are you on mostly?
[Thunderbolt Android Development] rune-san:
Combined with the Lightening ROM and this kernel (1.4 extreme) I'm getting sooo much better battery life compared to the stock ROM. So glad I rooted!
[Thunderbolt Android Development] cmo220:
I mentioned in all my posts yesterday about the new kernel that it was all wifi. But even today when I'm at work with mainly no service, until I leave the basement switches to 4g, then back to no service, the battery seemed to last better than it ever has before. I've used tons of kernels on a few different phones and never really noticed any difference between any of them on battery with data usage. I'm much more concerned with how it does when I'm doing things that don't involve data.
[Thunderbolt Android Development] WormDoes:
I mentioned in all my posts that I was on WiFi. I generally always use WiFi because I have access to it almost everywhere I go.
[Thunderbolt Android Development] Imoseyon:
4G is definitely the worst offender by A FREAKING MILE when it comes to power consumption. You could run your phone at 500mhz max undervolted the entire time but if you're on 4G you're going to drain the battery in hours - there isn't anything the kernel can do...
[Thunderbolt Android Development] pinhead875:
EXACTLY! Most people seem to not understand this. Or they think they have a super phone and their 4G only sips their battery. We can only wish...

BTW, love your work, Imoseyon.
[Thunderbolt Android Development] jlevy73:
Huge as in 2X for me. Was at a birthday just outside of LA and only had 3G coverage. My battery only drained about 10% in 8 hours.
[Thunderbolt Android Development] Veridor:
As a dev, do you think an updated radio firmware or other OTA might improve 4G power efficiency, or is it the LTE hardware to blame and thus we're SOL?

Loving how battsaver has improved my battery life, but you're dead-on: 4G KILLS battery.

Sent from my HTC Thunderbolt using Perfect Storm themed XDA App
[Thunderbolt Android Development] jlevy73:
Yes definitely. When the Evo came out battery life was horrid. With subsequent updates battery life was much improved so hopefully we'll see the same here
[Thunderbolt Android Development] Imoseyon:
Yup hopefully HTC will come through!
[Thunderbolt Android Development] patdroid1:
Imoseyon...i'm ready to do some testing...been playing around with kernels for past couple weeks and keep coming back to yours.

my phone doesn't mind the overclocking (been to 2.06) but can be sensitive to the undervolting...hope this can help you with your development...let me know i'm ready to test beta!!!!

keep up the good work
[Thunderbolt Android Development] Imoseyon:
Check your PM. :)
[Thunderbolt Android Development] patdroid1:
on it now...report back
[Thunderbolt Android Development] jlevy73:
Nice, curious to see how your phone handles 2.04. If it's stable, run a quadrant if you don't mind.
[Thunderbolt Android Development] azbryan3:
Was there someplace I could read about these governors? I'm really confused by all this smartass/on demand/interactive stuff. Thx:)

-Mobile via XDA Premium-
[Thunderbolt Android Development] patdroid1:
ok so some preliminary tests....

100% stable on all tests, no overheating, no lag

i used CPU Benchmark and Linpack for first tests to get a baseline... interactive X as governor...here's what i got so far...

1024mhz=665ms/32.5 (CPU benchmark/Linpack)

1222mhz=563ms/44.5

1408mhz=505ms/50.5

1593mhz=445ms/54

1766mhz-402ms/58.5

1920mhz=398ms/56.5

more testing to do....just a sample!!!

oh yeah...those are averages across 5 tests each
[Thunderbolt Android Development] Imoseyon:
Cool, thanks for testing. Wanted to see how stable the 1.92 builds were. v1.1 should be out shortly....
[Thunderbolt Android Development] patdroid1:
sure thing let me know...i do regular testing on my own anyway so might as well contribute...let me know what you need...i can be more comprehensive lol
[Thunderbolt Android Development] jlevy73:
Did the kernel you are testing include 2.04 or only up to 1.92?
[Thunderbolt Android Development] JonKyu:
Hmm interesting, there not much of a difference between 1.7 and 1.9 scores.
[Thunderbolt Android Development] jlevy73:
Were you able to get the radio working with more recent kernel you mentioned last week?
[Thunderbolt Android Development] jlevy73:
If you look at 1.7 vs 1.9 linpack scores actually go down. Interesting...
[Thunderbolt Android Development] Imoseyon:
Here's my take on the governors. A few of these are pretty easy:

performance - max speed all the time

powersave - lowest speed all the time

conservative - slow ramp-up

The next few get a bit more complex. ondemand, interactive, and smartass all try to pretty much do the same thing. Perform well and power efficient. But the way they approach their goals are very different (ie. their algorithms are very different).

1) ondemand - been in linux for a long time and we got really smart linux kernel developers working on it and the code gets reviewed by really smart people. At the same time this governor is really designed to work on desktops, servers, phones, etc - a universal solution.

2) interactive - developed by CM (I think), tuned for performance. Instead of sampling at every interval like ondemand, it determines how to scale up when cpu comes out of idle.

3) smartass - developed by erasmux for his android kernel. Famous for its ability to use android's onboard suspend mechanism to keep the phone below a certain clock speed when screen is turned off. Also does slow ramp-up like the conservative governor.
[Thunderbolt Android Development] patdroid1:
i know...i've seen this several times on several kernels...looks like my phone flattens out around 1.8 and starts to die after 1.4
[Thunderbolt Android Development] Imoseyon:
haha never got around to it. v1.1 is all about governors and making 1.92ghz more stable. v1.2 is probably going to be gpu optimization and a few other features. v1.3 and onwards is probably going to be either get the incredibleS kernel to work fully on the tbolt or backport a lot of the newer from from the incredibleS kernel to the tbolt.
[Thunderbolt Android Development] patdroid1:
and Imoseyon...phone run's beautifully on both stock interactive x and on demand governors...when i play around with smartass i get some serious lag...on text...email...homescreen...etc...????
[Thunderbolt Android Development] jlevy73:
Great, look forward to it.
[Thunderbolt Android Development] JonKyu:
I think that has to do with the slow ramp up. I get some finicky results with smartass too, its really bad on some of the other kernels I tried.

@imoseyon maybe you should post your governer explanation in the first post I think its really helpful.
[Thunderbolt Android Development] jlevy73:
This is taken verbatim from coolbho3000 (creator of setcpu and kernel guru) site: http://www.setcpu.com/#7

ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.

conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.

performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.

powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.

userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.

smartass (Best explanation i've found paraphrases to: based on interactive, but better.)

cpufreq: interactive: New 'interactive' governor courtesy of Cyanogen's github

New interactive governor.

This governor is designed for latency sensitive workloads, UI interaction for

example.

Advantages:

+ significantly more responsive to ramp cpu up when required (UI interaction)

+ more consistent ramping, existing governors do their cpu load sampling in a

workqueue context, the 'interactive' governor does this in a timer context, which

gives more consistent cpu load sampling.

+ higher priority for cpu frequency increase, rt_workqueue is used for scaling

up, giving the remaining tasks the cpu performance benefit, unlike existing

governors which schedule rampup work to occur after your performance starved

tasks have completed.

Existing governors sample cpu load at a particular rate, typically

every X ms. Which can lead to under powering UI threads when the user has

interacted with an idle system until the next sample period happns.

The 'interactive' governor has a different approach. Instead of sampling the cpu

at a specified rate, the governor will scale the cpu frequency up when coming

out of idle. When the cpu comes out of idle, a timer is configured to fire

within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer

fires then we assume the cpu is underpowered and ramp to MAX speed.

If the cpu was not 100% busy, then the governor evaluates the cpu load over the

last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down

to.

There is only one tuneable for this governor:

/sys/devices/system/cpu/cpufreq/interactive/min_sample_rate:

The minimum ammount of time to spend at the current frequency before

ramping down. This is to ensure that the governor has seen enough

historic cpu load data to determine the appropriate workload.

Default is 5000 uS.
[Thunderbolt Android Development] JonKyu:
@jlevy73

Thanks for that very interesting read. Hopefully that will minimize my "stupid question" output lol. I lol'd at the simple smartass explanation too. Haha
[Thunderbolt Android Development] Imoseyon:
v1.1

v1.1 (4/18/11)

significant changes were made to the OC/UV code. If v1.1 is *less stable* than v1.0 for you, go back to v1.0 and either PM me directly or report here.

If you had issues running my 1.92 builds in the past due to random reboots/lockups, give it a shot again?

ondemandX governor (ondemand + my own suspend code to keep phone under 369Mhz when screen is off). It will suspend at 245Mhz but can ramp to 369Mhz if necessary while screen is turned off.

modified interactiveX and smartass governors to prevent unnecessary spikes over 1.8Ghz to stabilize my 1.92 builds and extend battery life. If you don't like this behavior, use ondemandX. N/A if you're not running 1.92 builds.

extreme/1.92X/battsaver now all share the same VDDs at and below 1024Mhz (undervolted even more for extreme and 1.92X!)

OC/UV code re-written again to smooth out transitions and reduce random reboots,

added one more slot to 1.92 builds.
[Thunderbolt Android Development] Forgetfull:
I had no issue running v.92. I cant run 1.0, I'm trying 1.1
[Thunderbolt Android Development] Forgetfull:
Now that the new RUU is advailable will that change your kernels or merit some heavy changes to be seen in the next version?
[Thunderbolt Android Development] Imoseyon:
There will be changes for Tesla Coil but nothing on the kernel until there's new version of kernel source code. I haven't downloaded the RUU yet but there's a good chance it's using the same kernel as before.
[Thunderbolt Android Development] patdroid1:
wow that was pretty sudden...downloading now...k imoseyon...get ready to do your thing lol...as i said earlier...i'm down for beta testing!!!!
[Thunderbolt Android Development] Forgetfull:
Extreme 1.1 is running great.
[Thunderbolt Android Development] patdroid1:
k on new RUU...just getting things rollin..so far so good....

Kernel Version:

2.6.32.21-gb05544a

htc-kernel@and18-2#1
[Thunderbolt Android Development] Richpopski123:
This^^^. No locks, just eating batt at 1.92!
[Thunderbolt Android Development] jlevy73:
1.92X runs very well with the new Bamf 1.5 Rom. Got a couple of Linpack scores that were above 63 :)
[Thunderbolt Android Development] azbryan3:
Is anyone having a force close issue with the front facing camera? Thought it would be with the ROM but no one there is having the issue. Only other part is the kernel. I'm running the normal 1.0 ... Thanks!

-Mobile via XDA Premium-
[Thunderbolt Android Development] azbryan3:
Yes! And thank you!!

-Mobile via XDA Premium-
[Thunderbolt Android Development] JonKyu:
So far so good, am finally able to run at 1.92ghz! Lol

Edit:

I got a reboot when I tried to do a quadrant at 1.92 on 1.92X kernel with the on demand governor, it fine with smartass and interactive though. Seems like 1.79 is my sweet spot my scores don't seem to go up with 1.92
[Thunderbolt Android Development] Forgetfull:
So on extreme 1.1 (on demand gov) set at 1400MHz my MFLOP was 46 and Quadrant was 2150. Is this Good?
[Thunderbolt Android Development] swimminsurfer256:
That's odd. I'm getting constant ~61s on linpack at 1.92!
[Thunderbolt Android Development] Imoseyon:
thanks for the info. Looks like the new RUU is on the same kernel version. Should be safe to flash my kernel on top of it.
[Thunderbolt Android Development] Imoseyon:
found a bug in the smartass code. Sometimes it doesn't limit the speed while sleeping. Fix coming later today...
[Thunderbolt Android Development] Imoseyon:
close enough i think. You can usually get around 50.
[Thunderbolt Android Development] Imoseyon:
You should be able to keep the max at 1.92 as long as you use my interactiveX or smartass. Those two governors will minimize unnecessary ramp spikes above 1.8Ghz. It will only allow you to go above 1.8Ghz when you sustain load above 95% and a few other factors.
[Thunderbolt Android Development] patdroid1:
Running leaked software on 1.1 normal....so far so good....will report back later with full update
[Thunderbolt Android Development] Imoseyon:
v1.11

ONLY UPDATE IF YOU'RE USING SMARTASS

- smartass wasn't suspending properly - fixed.
[Thunderbolt Android Development] bokechukwu1:
I'm on 1.0 normal now running the smoothest for me but I have a question is smartass not fixed in this version?
[Thunderbolt Android Development] Imoseyon:
haha i was hoping no one would ask this question. I was actually wondering the exact same thing. I gotta head to work now but when i get there i'll flash 1.0 to check it out. In the meantime i don't think you'll be disappointed with v1.11.
[Thunderbolt Android Development] patton21:
Does interactiveX or smartass provide better battery life with phone off and/or using the phone? Thanks a lot! Great work!
[Thunderbolt Android Development] jlevy73:
In theory, smartass is a better implementation of interactive.
[Thunderbolt Android Development] Imoseyon:
Interactivex, imo, is superior to unmodded Smartass. :)

In my kernel all three should provide the same power efficiency when screen is off.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] jlevy73:
If your scores are not going up that's a sign of instability or overheating at play. Some chips just can't handle that much voltage and as a results scores begin to decline. Try just the normal 1.92, it's a bit more gentle than 1.92x is.
[Thunderbolt Android Development] jlevy73:
I agree however is you Smartass unmodded?
[Thunderbolt Android Development] Imoseyon:
It's heavily modded but for some reason I still prefer Interactivex's performance. I also like the elegance in cm's code. :)

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] jlevy73:
Just had a reboot while on a call running v1.1 1.92 (1.92/245 interactiveX) :(
[Thunderbolt Android Development] Imoseyon:
:( let me know if it reoccurs.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] asenduk:
v1.11 been running great so far @ 1.92/.245 using interactiveX

im actually waiting for it to lock up, lol

:P
[Thunderbolt Android Development] mbh87:
Maybe I'm crazy but it seems like v1. 11 battsaver is running a little warmer than usual.
[Thunderbolt Android Development] Imoseyon:
LOCO!!!

:p
[Thunderbolt Android Development] Imoseyon:
hmmm looks like it's in v1.0 as well. I wonder if it's a bug in original smartass code... anyway it's fixed in v1.11.