yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] lgldrgdlr:
I've been running the BFS at 1.8 for nearly a full day so far and I have had zero problems. Haven't had any lockups, issues with the screen waking, etc. Must say, Ziggy, I'm glad you got a Tbolt. Thanks for all of your hard work.
[Thunderbolt Android Development] Hellzya:
Ran ziggy's on my dinc glad to see you over here. Bfs at 1.5 is great thus far

sent from somewhere
[Thunderbolt Android Development] asenduk:
wow Ziggy!

running the BFS kernel with Bamf 1.32

constantly checking setcpu for the frequency and smart ass actually works!

battery life is CRAZY! and not to mention, this thing is blazing!

and stilll in beta?

WOW!!
[Thunderbolt Android Development] htowngator:
What are you getting for battery life with LTE on?

My average is about 10%/hr drain with moderate use. (I am not rooted nor using a ROM)
[Thunderbolt Android Development] asenduk:
When idling this thing is a beast...

Left my phone uncharged last night around 12:15am before bed at 65%, woke up this morning at 7:15am and the battery was at 62%.. WHAT???

Charged it up at 100% before leaving work at 9am.. Pandora all the way up until now, did some web browsing, no phones calls, did about 15 text messages and its now 11:15am and im at 91%

im using smart-ass governor @ 1.5GHz

1.8HGz was actually stable for me with no lock-ops or reboots, but i dont want to push my baby too hard lol

This thing with Bamf 1.3.2 ROCKS!!!
[Thunderbolt Android Development] egeorgia:
Where are guys finding the bfs kernel? I only see the cfs.

Never mind. Clicked on the comments link and found it.
[Thunderbolt Android Development] Bimmer323:
On Ziggy's download page, it's on top of the CFS kernel download link.

One for BFS and one for CFS.

!!! We've got Tardis power !!!
[Thunderbolt Android Development] Mistar Muffin:
I get lockups requiring a battery pull. Lockups can occur when I try to wake and unlock or when running Quadrant. It has happened at 1.8ghz and 1.5ghz. I can run other kernels @ 1.8ghz with no problems. I want to try Ziggy's kernel to see if the battery life is improved over the other kernels I have tried. These symptoms were on the BFS version so I am trying CFS now.
[Thunderbolt Android Development] Nikolai2.1:
CFS did the same for me
[Thunderbolt Android Development] eschelon:
He's still working on smoothing out the proper voltages to prevent this from happening on occasion

Kernel development is always a work in progress as there are always little quirks, bugs fixes, and other improvements to be made. So keep checking back on his site as he updates and releases new kernels
[Thunderbolt Android Development] khanam:
i am stable at 1.8 but i do not want it that high because of battery life concerns. either way, i get to 1.8 in steps, i first throttle min and max to 1.5ish (throttle means min and max are at same freq and governor is performance). then i slowly increase max 1 step, then min to same level, then max 1 step higher and so on. that works for me.

i hv been a faithful ziggy kernel tester and user since the incdoes days on the inc. imho, his kernels are the best both for battery life and ridiculous performance. he stays close to the mainline linux tree which makes it easy for him to upgrade, patch and tweak. as a result, at least on the inc (no data for the bolt yet since no bolt aosp rom exists), his kernels were universal i.e. they worked both on sense and aosp roms.

kernels can make good roms really shine. i am running his bfs on storm 1.2 and the combo is incredibly (pun intended) good. try them out together.
[Thunderbolt Android Development] Nikolai2.1:
I know, I like these.kernels so I'm not giving up on him
[Thunderbolt Android Development] Gunthermic:
First try at a Kernel? Just ROM Manager and flash it? I heard that Ziggy is the best..
[Thunderbolt Android Development] jlevy73:
Yep, that's it
[Thunderbolt Android Development] xyojimbox:
Im using this with bamf 1.3.2 and its sweet! I dont know.if this is a prob with the rom or kernel but phone screens stays off when take away from face in call and have to push the wake button to get it back on
[Thunderbolt Android Development] :
Sorry for this newb question. I'm running andrenyline 2.0 kernel. Can i flash over?

or do I always have to do wipe data and cache after every flash
[Thunderbolt Android Development] Mistar Muffin:
As you said, CFS offered no improvement in the lockups over the BFS kernel. I will go back to droid's 1.8ghz and wait for an update.

Thanks for your work, Ziggy.

-Muffin
[Thunderbolt Android Development] Gunthermic:
Thank you for answering...
[Thunderbolt Android Development] sincerity:
just flash over...BUT make sure you have a current backup before flashing ANY kernels in case your phone won't boot for whatevr reason
[Thunderbolt Android Development] SubliminalME:
Seems to work great.

I'm running VirusRom. Stock Kernal was around 1700 Quadrant, 1.2 was ~2000 and this at 1.5 is about 2300.

Good enough for this kid! :)
[Thunderbolt Android Development] houseboatwayne:
Just back kernel down to 1.6 from 1.8 and resets will disappear. Worked on BFS and CFS for me. Quadrant scores are still crazy high even on smartass gov.
[Thunderbolt Android Development] CorporateGoth:
That's interesting - since my phone seems solid @ 1.8 right now.
[Thunderbolt Android Development] Nikolai2.1:
which kernel are you using and how did you do this?
[Thunderbolt Android Development] CorporateGoth:
I'm just using Ziggy's beta kernel.

I only clock my phone @ 1.8 while on power, and I use SetCPU to make it use the performance governer, with min/max @ 1.8.

When on battery I have the max clock down to 1.2 using smartass (and even down to 0.3 when the screen is off), to make the battery last longer.

But I've used it fairly heavily both on power and off and not had any crashes.
[Thunderbolt Android Development] MYxdaUSERNAME:
this is a beast of a kernel...for what it's worth, at 1.8/1.8 performance gov, it got a score that is 282 out of 5500+ scores on An3DBenchXL...

but as i was typing this I switched back to ondemand gov and it froze up and rebooted..gonna try it out on 1.4ish and see how it does..
[Thunderbolt Android Development] sm0k3y-TB:
sent via r00t3d TB - thx jcase!
[Thunderbolt Android Development] ziggy471:
I'm glad you all like it so much. I originally started compiling and modding Linux kernels back in the pre 1.0 days. I started doing kernels for my INC, only mine, but my friends convinced me to build the kernels for them too. Then my EVO buds said they needed one too, so I made an Evo one. Then when the Bravo source came out, I dropped everything to build a kernel for Mr. X and Mighty Mike, if it weren't for those 2, you guys might not even know who I am. I then decided that keeping 3 trees at the same level SUCKED, so in came Frankenstine, that's INC/EVO/BRAVO combined tree. I then decided to get the TBolt early because of the data cap that was coming, so I had to start working on that one too. The Mecha code has yet to be integrated into Frankenstine, but eventually it will be.

Now as for why some can overclock more than others. Not every processor can overclock to the same limit. Also, as I've discovered on the INC, the ROM also has an effect on how high you can go. My INC could do 1.15 on an new sense ROM, but on the older ones, it'd lock up. The only reason for the 1.8G cap was due to one of my testers who had 2.03G stable, but the others couldn't. I think that maybe adjusting the voltage some would help some, while with others, it won't help at all.

Just my 2 cents, now back to the discussion.

Z
[Thunderbolt Android Development] jlevy73:
I am rock solid @ 1.8ghz, I think my phone could handle 2.03 :)
[Thunderbolt Android Development] asenduk:
2GHz?

Thats insane!! but i want!!! lol
[Thunderbolt Android Development] khanam:
I am rock solid at 1.8 and during testing I did get to 2.03 for a short period of time. Please do read my earlier post about incrementally hiking up cpu speed and not in a jerky manner. It helps with stability. I shocked somebody at htc with the scores so that was fun. I am currently running it at stock 245/1228 smartass and its fast enough for me there.

Sent from my thunderbolt
[Thunderbolt Android Development] mbh87:
Noticed my phone gets a little warmer that usual while charging, other than that the BFS kernel runs amazing. I have it clocked to stock speed.
[Thunderbolt Android Development] Cmotion:
So I know that when devs release Kernels on the site they usually say whether or not you should wipe cache/dalvik cache after flashing the kernel, but since this wasn't started by the dev himself, is it common practice to wipe those two when flashing a new kernel?
[Thunderbolt Android Development] khanam:
Yes. I always wipe dalvik and cache. It's always a good idea.

Sent from my thunderbolt
[Thunderbolt Android Development] Cmotion:
One final newb question, does the order matter? Flash kernel first then wipe caches or wipe caches then flash kernel? Or totally inconsequential?
[Thunderbolt Android Development] khanam:
doesnt matter. i hv done it both ways.
[Thunderbolt Android Development] gemitero:
i know quad scores don't mean much but it is nice to look at lol

ziggy bfs kernel @1.459

perfect storm rom 1.1
[Thunderbolt Android Development] corenojoe:
I'm solid at 1.8 also, but I don't run it cranked all the way up much because of battery life. Still, nice to know it can handle it.
[Thunderbolt Android Development] blaine07:
This kernel(BFS) as is is to kill for. By far best battery life of any of tgr kernels I've messed with && BONUS the best performance. Not messing with kernels until this onw is drastically changed. Very stable, no reboots on smartass @ 1036. I'm not sure you could improve this much...

Anyway, thanks a ton!
[Thunderbolt Android Development] Gunthermic:
what is the aceptable temp we should allow. We can go up to 1.8 right now, but mien seems to be gettign warmer..
[Thunderbolt Android Development] 52brandon:
Been on the cfs kernel at 1.53ghz with no problems at all. Loving it so far

Just set it at 1.8 and performance on setcpu...

Gotta say, I love having a phone that performs really well. After my Droid couldn't get past 1.1 and sometimes struggled there
[Thunderbolt Android Development] Bimmer323:
Loaded up the CFS kernel last night, went to bed with 71% battery remaining.....(wifi and data turned off, I don't need notifications while I sleep)......woke up this morning to 71% battery remaining. :)

Played around for about an hour last night with the new kernel and everything was great, not much time today to test, but so far....awesome work!!

!!Tardis Power!!
[Thunderbolt Android Development] andrew53517:
Bfs or cfs kernel do you guys recommend? Which is better? I want to test this kernel out too :D

Thunderbolt Rooted!
[Thunderbolt Android Development] khanam:
Cfs is smoother and better at multitasking but bfs is faster. I use bfs.

Sent from my thunderbolt
[Thunderbolt Android Development] SteveDusa:
Wow this kernel is making a HUGE difference on battery life! I am getting almost extended battery-like time on standard with LTE on!

Using CFS build on DAS BMAF 1.3.2, SetCPU with smartass governor.
[Thunderbolt Android Development] BeeDubs:
What do you guys mean when you say this? Just speed or battery or what?
[Thunderbolt Android Development] andrew53517:
How is the overall speed of the ROM? does it feel really smooth and quick?
[Thunderbolt Android Development] SteveDusa:
Oh yeah! I haven't tired many kernels but this is like a God-send kernel! I am start to think time to return my extended battery (which is still in the box) now lol.
[Thunderbolt Android Development] Cmotion:
I am in agreement with everyone else, battery life has been amazing. It actually idles on the lowest frequency using smartass governor, and even while using the phone the battery is so much better. When I first flashed the kernel last night, I was on LTE, browsing the internet, periodically checking the battery % using Quick Settings, and it stayed at 99% for a good couple of minutes while doing things on the phone... to the point where I thought there was something wrong with the battery reading! Finally a few minutes later it dropped to 98. I'm so glad the Verizon store I went to yesterday was out of stock of the extended battery. Amazing kernel!
[Thunderbolt Android Development] detox246:
Bfs kernel is blazing. Running 1.19ghz on tesla coil with 2300's quads and 46's linpack. One lock up at 1.8 but I'm not gonna run it there anyway. Have to wait till tomorrow to report on battery but so far this kernel is amazing. Nice work Ziggy!
[Thunderbolt Android Development] itzjonjon69:
hmm i loaded the BFS kernel and went into setCPU and set the max at 1.8 and put it on smartass and my phone kept freezing, am i doing something wrong?
[Thunderbolt Android Development] andrew53517:
Nope, your phone can't handle it. Scale down to 1.6...if still freezing try 1.5 (if there is a slot) or 1.4. That should fix it. Some phones cant handle that speed.
[Thunderbolt Android Development] khanam:
If you want to be stable at higher frequencies, you have to be in performance mode and throttled all the way.

Sent from my thunderbolt
[Thunderbolt Android Development] khanam:
Kernel update coming tonight solving proximity sensor issue. I just tested it and I do not have to press the power button to wake the phone.

Also, battery life is good already but havs work has not even started yet. There should be dramatic improvements in battery life when that happens. Anybody who was using ziggy's bfs havs kernel on the inc knows what I mean.

Sent from my thunderbolt
[Thunderbolt Android Development] andrew53517:
I can't wait till we get these kernels on AOSP ROMs! They'll be even better than they are now!

Thunderbolt Rooted!
[Thunderbolt Android Development] PlankLongBeard:
I Come from Those Times! It's Was Evil D's Warm Z and Ziggy... Full Charge Lasted Nearly Two Days! Now that I Brought Up Evil, I Miss Evil's Work :(
[Thunderbolt Android Development] Breakthecycle2:
I thought it was just my phone being buggy with the whole proximity sensor.
[Thunderbolt Android Development] blaine07:
Updated kernel with proximity sensor fix was just posted on jhis website ...
[Thunderbolt Android Development] hogowner:
One question...I want to try his kernal...but which one??

the cfs or the bfs...how do you know which one to use for your particular phone?

how do you know which md5sums you have??

Thanks

EDIT:::::SORRY GUYS ME BAD! I googled it and found out...sorry for posting this!!!! :(
[Thunderbolt Android Development] Nikolai2.1:
Yes:)

10 chars
[Thunderbolt Android Development] Nikolai2.1:
Anyone interested in trying this kernel should. Im using BFS UNDERclocked to 806 and i can already see a difference.. a good one! 806 and 2ghz honestly felt the same to me. I was able to acheive 2ghz without lockups by throttling on performance mode (props to khanam). However i didnt try to turn off the screen in fear of it not turning on...

All in all its pretty smooth and fast for me, even at 806 (i got 1628 quadrant on this and 1630 on 2Ghz) i know that doesnt make sense but thats the facts... at least for my phone. OH, and it charges FAST!
[Thunderbolt Android Development] aostl:
Thanks for posting. This is already like my old inc with the community making my battery life way better. Thanx ziggy
[Thunderbolt Android Development] 52brandon:
:eek:

sweet, flashing the new CFS now. Cant wait to give this one a run after how well the last one did
[Thunderbolt Android Development] aostl:
Cfs @ 2ghz finished the quadrant but said it couldn't make the call to report score. Doh!
[Thunderbolt Android Development] 52brandon:
mine just completed at 2583 :confused: when the old kernel at 1.8ghz hit 3332. Odd... maybe my phone needs a bit more time to run the kernel before testing...
[Thunderbolt Android Development] jlevy73:
I miss Evil D too :( When I had the Nexus One he did some really good work both with kernels and Roms.
[Thunderbolt Android Development] Nikolai2.1:
diminishing returns my friend.. i hit 1630 on 2ghz, and that was running the slightly faster BFS kernel
[Thunderbolt Android Development] 52brandon:
strange, guess 2ghz is just going too far for the time being

my phone slipped into a coma when it went to sleep at 2ghz too... had to pull the battery
[Thunderbolt Android Development] Cg006:
I can assume you guys are using setcpu in conjunction with the kernel?
[Thunderbolt Android Development] 52brandon:
yes, I am at least
[Thunderbolt Android Development] jlevy73:
No diminishing returns here. 2ghz, Quad = 3610, Linpack 71
[Thunderbolt Android Development] 52brandon:
:eek:wow, nice. I do have to say though, that I am running very stable at 1.61ghz set on smartass. Hopefully it keeps up and I can keep turning it up to see where I max out while being stable
[Thunderbolt Android Development] jlevy73:
Amazing that this kernel can be OC'd by 100%, pretty cool. Of course I'll never run the kernel that high for more than a couple minutes to benchmark. I still find adrynalyne's 1.4ghz kernel to run the smoothest/best battery life but it's great to see all the development going on here.
[Thunderbolt Android Development] CorporateGoth:
Quad is very unreliable. I've had 3 consecutive runs of 1600, 1200, and 1900 (ish) obviously). Nothing different, all on power, etc. It's crap for a benchmarking tool. I mean if they were similar, I would say 'OK', but that's some serious variability.
[Thunderbolt Android Development] jlevy73:
Yeah Quadrant is not the best because it relies way too heavily on I/O. However, that being said, Quadrant has been around the longest so people use this as a barometer because you can see the differences fairly well across multiple devices.

As far as running Quadrant, I find that you need to run it at least 3 times. Typically after 3 runs, variablility thereafter decreases.
[Thunderbolt Android Development] 52brandon:
3311 now on 1.61 smartass... I dunno :confused:
[Thunderbolt Android Development] jlevy73:
Which Rom are you using?
[Thunderbolt Android Development] 52brandon:
das BAMF 1.3.2
[Thunderbolt Android Development] ktrinidad:
Running CFS (latest), clocked at 998. What did you mean about proximity sensor issue? Thank you!
[Thunderbolt Android Development] 52brandon:
That post was made before the kernel was released today. There's an issue with it not turning the screen back on when youre on the phone and move it away from your face
[Thunderbolt Android Development] ktrinidad:
Thank you for the quick reply. I thought so. It still happens though. The first time, yes it wakes. The second time you pull it away, the screen remains off until you press the power button. Just thought I'd report that. Otherwise, all is good!

Best!

EDIT: The developer (ziggy) did mention on his site that he was still working on it some more.
[Thunderbolt Android Development] khanam:
Holy crap. 3610???? 71????

Anyways, I think some of the phones are just able to handle higher frequencies better than others so do not be surprised if you can't get to 2ghz. It is what it is. Also, kernel panic or freeze is a distinct possibility at those speeds. Hell, you are going at twice the speed limit!!! And to be honest the instability caused by higher frequencies outweighs the benefits of the higher processor speed. I'm at 245/998 smartass unless I need to show off the phone to somebody. Then I slowly ramp up to 1.8. I did get to 2 but I don't like the thought of doubling processor speed.

Also, somebody asked how battery life might be improved. Ziggy believes there is still significant room for undervolting at lower frequencies. That is what will give you most battery savings. However, if you run this fully overclocked, obviously you won't see any improvement.

With regard to why you should overclock only using performance governor at significantly higher frequencies, its because of the changes in voltage if you go from a high frequency suddenly to a lower one (watch what happens in setcpu). That causes the phone to freeze up and reboot. Think of it as a built in safety mechanism.

Sent from my thunderbolt
[Thunderbolt Android Development] adrynalyne:
Running performance is the way to go?

Guess we will have to agree to disagree.
[Thunderbolt Android Development] jlevy73:
Not sure I follow the logic. If you run setcpu with "performance" it will pin your frequency to the maximum value. Say for example, I chose 2.04ghz/245mhz, with performance set it would clock at 2.04 only. That's why the only time I ever use performance is when benchmarking so the clock speed is at a max for the whole run.

I run my device overclocked but I only use on-demand or smartass depending on whose kernel it is. This way the phone only ramps up when needed drawing less battery over the long-run.
[Thunderbolt Android Development] khanam:
I guess I did not word it correctly. What I meant to say was that if you are going to ready higher frequencies, throttle the min to the same level as the max so that you do not get voltage changes abruptly.

Sent from my thunderbolt
[Thunderbolt Android Development] khanam:
I mean that if you are pegging the max to a very high number such as 2 ghz, then the governor should only be performance otherwise voltage fluctuations will cause problems. This is especially true in havs kernels. If you are overclocked only in the safe territory such as to 1.4 or 1.6, its safer to use smartass or on demand but not if you are in the 1.8+ range.

Sent from my thunderbolt
[Thunderbolt Android Development] 52brandon:
Setting it to performance runs on max always. So you're essentially doing the same thing
[Thunderbolt Android Development] khanam:
Yup. Either throttle min to max or run it on performance. I choose to leave nothing to chance and do both. Works for me. No reboots etc. Same reason I wipe cache and dalvik any time I flash a zip, even if not required. Just born that way.

Sent from my thunderbolt
[Thunderbolt Android Development] adrynalyne:
I think you stand a bigger chance of instability from thermal changes than voltage ramping up and down. This isn't a car where stop and go traffic is bad for it.
[Thunderbolt Android Development] PlankLongBeard:
This Is the Reason Why The Nazi's (Big Red) Should Have Released the Thunderbolt Back in Feb:

Genius' Like Ziggy Who Take the Smallest Battery that Powers One of the Largest Scales of a Beasts in the Signal and Process Power Margin to More Efficient Heights than Those with 1500+ Batteries!
[Thunderbolt Android Development] fillyo:
Is there any consensus of whether bfs or cfs is better on the thunderbolt?
[Thunderbolt Android Development] khanam:
That's true too but thermal changes are not instantaneous. Voltage changes are.

Sent from my thunderbolt
[Thunderbolt Android Development] jlevy73:
Not too mention that if you peg the kernel to a higher frequency say 1.4ghz which draws 1.2V (just using out of my ass numbers) over time that will be a larger draw on the battery than running smartass or on-demand which will fluctuate between 1.2V and say 1.0V giving an average of 1.1V. Less voltage equals less battery.
[Thunderbolt Android Development] khanam:
My point is to overclock for short periods of time in a stable manner, long term overclocking is obviously not good for battery life or battery temperature

Sent from my thunderbolt
[Thunderbolt Android Development] jlevy73:
I see what you mean :)
[Thunderbolt Android Development] sznaps:
If i even try to put setcpu to 2ghz without smartass governor on, my phone instantly freezes.
[Thunderbolt Android Development] jlevy73:
Yeah 2ghz is way up there. Most phones will not be able to handle that frequency.
[Thunderbolt Android Development] sznaps:
weird thing is it works fine if i have it on performance governor.
[Thunderbolt Android Development] khanam:
That's what I have been saying. To be stable at higher frequencies, you must have other factors constant (voltage, temperature, etc)

Sent from my thunderbolt