yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] patdroid1:
in fact adrynalyne has borrowed Imosoyen's code a few times. i am interested however in his latest tweaks with ext4 support...wonder if that is what Rjs shadows is referring to?
[Thunderbolt Android Development] RjsShadows:
Yeah that is what i'm referring to thank you. :D
[Thunderbolt Android Development] adrynalyne:
Yep, we have shared a couple times, both ways. Open source is win win for all.

My tweaks are on gh.
[Thunderbolt Android Development] patdroid1:
lol yeah i'm not complaining...i bounce back and forth between you two pretty much on a daily basis...was running 4.4.5 earlier today...now on Imosoyen 2.01...doing some benchmarking right now.....soooooooo close!!!!!
[Thunderbolt Android Development] RjsShadows:
I love both kernels, I wish you two would work together on one superior kernel.
[Thunderbolt Android Development] Imoseyon:
Ah yes EXT4. I'd have to enable it on my kernel first. ;) And that's coming in v2.1. As for additional EXT4 tweaks I'll take a look. It will probably not be trivial since 2.6.35 EXT4 code is very different than the 2.6.32 code.
[Thunderbolt Android Development] patdroid1:
awesome...just got a new replacement t-bolt from verizon today so still setting things up...down for some beta testing if you need it
[Thunderbolt Android Development] JonKyu:
+1 really interested in the filesystem tweaks.

And as an update on the test version of the kernel I'm back to awesome battery life. Been 2hrs and after some moderate usage (youtube, games, forum browsing, and twitter) I'm at 89% :-D
[Thunderbolt Android Development] BennyJr:
The test kernal is running much better at 185.
[Thunderbolt Android Development] RjsShadows:
Awesome :) Well i'm excited to see how it will turn out. My battery was at 88 percent after little to know use in a 8 hour period which is amazing to me, using your last kernel. Before I would go down to 70 or less.
[Thunderbolt Android Development] Imoseyon:
v2.1.0 for sense (5/6/11)

- 184Mhz battery draining fixed, flashlight brightness fixed, EXT4 enabled

EXT4 support is enabled in kernel but there will likely be further work required to make it work with ROMs (ie. BAMF). I will look into that this weekend. Kernel version will still show as 2.0 because I forgot to change it. ;)

http://xdaforums.com/showpost.php?p=12633597&postcount=1
[Thunderbolt Android Development] patdroid1:
just flashed, testing under way...system info shows kernel as 2.0 still???
[Thunderbolt Android Development] Imoseyon:
Oops forgot to modify the version info! thanks for the report - I will update the first post.
[Thunderbolt Android Development] patdroid1:
k cool... so far so good...my new t-bolt actually benchmarks higher than my first and so far the xtreme version working good so looks like it can handle undervolt...lol i was worried about that
[Thunderbolt Android Development] patdroid1:
k i think you nailed it...temp is much much cooler and battery drain so far is almsost non-existent
[Thunderbolt Android Development] raziel36:
Hi, my name is Jason... and I... have an addiction.

I just happened to open my downloads.. and realized how little of a life I have outside of my phone. No wonder I'm going through my second divorce lol
[Thunderbolt Android Development] patdroid1:
it's all about balance and technique...i've learned the ways....pretend you are listening...nod your head...when she goes to the bathroom that is your moment...quickly flash and get out!!!!!!!
[Thunderbolt Android Development] KGBxxx:
That is exactly how you do it. Also, she asks me why I poop so long. I say it's a guy thing.
[Thunderbolt Android Development] raziel36:
Haha, if anything, my phone hobby actually kept the marriage alive alot longer than it should have. It gave me an out, to forget about her pain pill addiction for a while. Fun times. Now it's just me and the phone... oddly and sadly, the best times I've had in years. I do have *friends w/benefits* though, so I'm not a lost cause yet.. otherwise, I'd be lobbying for the right to marry electronic devices.
[Thunderbolt Android Development] 52brandon:
nice, I thought I was going crazy with how bad my battery was draining
[Thunderbolt Android Development] smashtheguitar:
Did you end up deciding to set the 184mhz to 750VDD?

Edit: Actually, it looks like you left it at 650? So the "can't go below 750VDD" was actually just a bug, or are we still testing how stable 650VDD is? If this works on most phones it's an incredible accomplishment, I think.
[Thunderbolt Android Development] mmtoman:
Can you give me a kernel version for sense 2.1.0. I flash so much **** that I cant keep it all straight. Running great. I use batt saver fyi.

Is there only three or for steps in this kernel? In setcpu I only see it jump through a few frequencies.
[Thunderbolt Android Development] smashtheguitar:
the battsaver version appears to have 5 steps.
[Thunderbolt Android Development] Imoseyon:
Actually I changed it to 750. I'm going to see if I can force it to go lower when i get a chance. Turns out the bitbucket link doesn't update automatically to the lastest code - sigh. Here's the new link: https://bitbucket.org/imoseyon/lean...373/arch/arm/mach-msm/acpuclock-7x30.c#cl-134
[Thunderbolt Android Development] Imoseyon:
battsaver = 5, normal = 6, extreme = 7, 1.92 = 9, 1.92X = 10.
[Thunderbolt Android Development] corenojoe:
My battery is still dropping from 100 to 95 in like 5 or 6 minutes with v 2.1 never did that with previous versions.
[Thunderbolt Android Development] smashtheguitar:
The dropping around 5% from 100% shortly after unplugging is common, especially with HTC devices (apparently). It's my understanding that it has to do with something about protecting your battery (from overcharging?).

The proposed solution has you charging to 100%, clearing the battery stats and then letting it die before recharging to full. Not really sure if that solves the issue, but this is a common problem after changing roms/kernals.

That's probably the case. I'd wait and watch it a bit to see if you're really seeing a consistent drop or not, as the 100-95 isn't really that telling of a kernal problem.
[Thunderbolt Android Development] ncwildcat:
I still had bad battery drop with 2.1 extreme..
[Thunderbolt Android Development] BennyJr:
What is 'bad'?
[Thunderbolt Android Development] corenojoe:
Now down to 87% after a half hour and I didn't even touch the thing, screen was off. That's definitely not right.
[Thunderbolt Android Development] Imoseyon:
Hmm set the min to 246mhz using setcpu and see if it gets better? I wonder if the low slot is still problematic.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] Forgetfull:
I think 2.whatever is still having growing pains. Of course it could have been something network related but once I flashed back to 1.2.3 (or whatever it was) battery while the screen is on went back to normal.
[Thunderbolt Android Development] BennyJr:
Mine is running good like your other previous ones...hmmm
[Thunderbolt Android Development] Richpopski123:
I would agree that on the high end it drops quickly, but once at around 50% it slows greatly. After 2 charges its starting to even out so I say give it a few days.
[Thunderbolt Android Development] smashtheguitar:
I'm using the latest extreme version. I'm currently at 88% with 4 1/2 hours since unplugged. Up time of 5:54 (hours) and and awake time of 1:25 (hours). Using interactiveX with 184-1222. Moderate use with display -> voice calls -> cell standby with most usage.
[Thunderbolt Android Development] BennyJr:
Yeah it use to be better then that..
[Thunderbolt Android Development] sublimaze:
I was running v2.0.1 at 1ghz/184mhz/interactiveX with no problems whatsoever, phone never ran hot, no freezes. I flashed v2.1.0 about 3 hours ago using same cpu settings and just experienced my first hangup. Phone wasn't hot but screen timed out/turned off and later would not respond to the power button. I had to pull battery & reboot
[Thunderbolt Android Development] smashtheguitar:
I have not any lockups since you made the latest revision. Battery life might be a bit worse, but not sure its dramatically so.

Edit: After a little more time with it, I think I'm getting better battery life if I bump up the lowest slot to 245 mhz. No empirical evidence to share here, but maybe there is still a problem with that slot.
[Thunderbolt Android Development] Imoseyon:
Those of you having issues with v2.1 please set min to 246mhz and report back here? Thx.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] jasonbiggs:
Flashed 1.92x w/o problem. Question is what to set setcpu to for maximum battery/speed combo? Thanks for input.
[Thunderbolt Android Development] Imoseyon:
i think some of the phones (including mine) still can't handle 184Mhz properly. What i'm going to try to do is lock out that slot and make a flashable zip that unlocks it for those of you who really want it. 2.1.1 should be coming this weekend.
[Thunderbolt Android Development] 52brandon:
works great for me. 4 hours on standby and I lost 2% of my battery. It's amazing
[Thunderbolt Android Development] 52brandon:
I use 1.408 and 184 on mine and it runs beautifully. Any higher is kinda a waste of battery life
[Thunderbolt Android Development] sublimaze:
Update: I was on v2.1.0 (1ghz/184mhz/interactiveX) for 9 hours and twice my phone wouldn't wake up from sleep. I never had this issue with v2.0.1 and same cpu settings, so I rolled back
[Thunderbolt Android Development] corenojoe:
Wiped battery stats, now 2.1.0 seems to be OK but no noticeable difference from v 2.0
[Thunderbolt Android Development] Imoseyon:
Yup that almost certainly means your phone can't handle 184Mhz/750VDD. I'll have 2.1.1 to lock out 184mhz soon.
[Thunderbolt Android Development] sublimaze:
Yeah, I figured that. But I was able to use 184mhz on v2.0.1 and got incredible battery life with it
[Thunderbolt Android Development] 52brandon:
which kernel? Is it an extreme one or a normal one? If extreme, you may wanna try a normal one just in hopes that it works
[Thunderbolt Android Development] sublimaze:
Battsaver each time. I've been really pleased with battsaver, I haven't tried the others
[Thunderbolt Android Development] Imoseyon:
If you're interested in saving battery I'd suggest conservative but you'd get a slight performance hit, but undervolting alone will help you save battery regardless of the governor you choose. In terms of scheduler, it's using Autogroup scheduler which is a variation of CFS. BTW, a quick note on BFS: http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler#cite_note-9
[Thunderbolt Android Development] Nikolai2.1:
Thanks for the information man, youre very helpful! Ill stick with ondemand tomorrow and test, and thanks for the the info on BFS, i really enjoy learning about this stuff

EDIT: After more testing, the kernel locks up on me spontaneously, and reboots into clockwork. Not sure if this the speed, or what, I doubt its the speed though
[Thunderbolt Android Development] Imoseyon:
Are you running the 1.92ghz version? I think it's very possible that the phone cannot handle that much speed....
[Thunderbolt Android Development] Nikolai2.1:
yeah, well i mean it was running it for quite a while and then it locked... i remember using some 1.8 kernels that lock at wake or not even let my phone boot for one thing.. i went back to using adrenalynes 1.4 kernel for now, but great work man! who knows, maybe we can get these high speed kernels to run flawlessly:cool:
[Thunderbolt Android Development] Imoseyon:
Woohoo I'm a senior member! I may stop responding to every post now. ;)
[Thunderbolt Android Development] Nikolai2.1:
ahh hey man not cool lol
[Thunderbolt Android Development] inline6power:
Fastest kernel I have tested yet and I have tried all of them. At 1.9 I am getting 3250 quads and 64 mflops. Smaetbench is at 3100.this thing flies. Will test for a full day of use. Thanks you

Sent from my rooted Thunderbolt
[Thunderbolt Android Development] jlevy73:
1.92 runs nice and stable on my device. 3210 on Quadrant and Linpack = 64

Now where's the 2.04 kernel :p j/k

Thanks for the awesome kernel, much appreciated.
[Thunderbolt Android Development] Diversion:
Weirdest thing..

Performance mode at 1.92ghz is benching slower than using On Demand governor..

Slower in any type of benchmark.
[Thunderbolt Android Development] adrynalyne:
You are overheating.
[Thunderbolt Android Development] Spaniard85:
My Linpack is close at 63.5, but my Quadrant is no where near that. Maxed at 2600ish so far. Have had a couple of reboots, though, so I'll let it break in and test it again later today.
[Thunderbolt Android Development] mini_monsta:
Got a 3283 quadrant score on the 1.92 kernel. O o wow!
[Thunderbolt Android Development] Imoseyon:
Those of you with stability issues with 1.92Ghz, try this version with higher VDD. If this one's unstable as well, it's very possible that your phone is not suitable for overlocking that high.

EDIT: oops fixed. please redownload.
[Thunderbolt Android Development] asenduk:
1.92GHz works greatfor me, although i wont ever set my phone at that speed.. only thing that would be nice is a smart-ass gov since using the on-demand gov, the phone constantly switches back from 245MHz to 1.92GHz(or what max ever is set) constantly even when idling.. other than that, 1.92GHz is screaming fast!!!
[Thunderbolt Android Development] jlevy73:
For benchmarking I set it to 1.92/1.92 using performance then run my benches.
[Thunderbolt Android Development] Imoseyon:
I'm actually trying to remove code not add. ;) Let me go through the on-demand governor code to see if there's anything I can do first. (i might be overestimating my coding skills here).
[Thunderbolt Android Development] Diversion:
Lol, awesome.
[Thunderbolt Android Development] Spaniard85:
Sweet, will definitely give this a try. So is a "higher VDD" a higher voltage then for the top end?
[Thunderbolt Android Development] Mistar Muffin:
This is been my experience with the ondemand governor on all of the kernels I have tried, and I have tried them all :D

I can sit there in setCPU and watch it bounce between min and max with no user interaction. I have also tried it after killing as many unnecessary services and background apps as I can with no change in the result.

On the kernels that support it, smartass scales down to the min and will rest there until I interact with the OS. Even then, however, it doesn't necessarily spike right up to the max frequency. Additionally, ondemand seems to only have two modes and usually just runs @ the max setting when the device is being used at all. This is an additional criticism on top of the fact that it doesn't seem to idle properly as reported by asenduk.

Smartass:

+1 for idling at min freq

+1 for actually stepping between min and max frequencies like less of a spaz

Pretty please! :D
[Thunderbolt Android Development] azturbomini:
Running great at 1408.
[Thunderbolt Android Development] Richpopski123:
Yeah... My phone died in 7 hours. No real usage. Will bump up a slot
[Thunderbolt Android Development] WormDoes:
Have been running 2.1 extreme for about 5 hours now at 185|1.4 and have lost 1%. Phone seems just as smooth as it did when I had it at 245. I've run a lot of kernels from a lot of developers and I have to say yours are by far my favorite and best I've come across.
[Thunderbolt Android Development] NetworkPIMP:
Question

So, I've become smitten with the idea of call-recording support in Adryn's new kernel's - and it seems to work quite well in his latest iteration. It's saved my butt once or twice in the 36 hours I've had it ;)

That said, I find myself back on his kernels - but I feel you've a) had more/better focus on power-consumption and b) the 1.92 options with InteractiveX work "extreme"ly well for me.

Is there a way that call recording can be added to this kernel? I know your focus, aside from power and speed, is to keep it as light as possible - so, can it be added after-the-fact? i.e. as a script or cwr .zip that adds it in? or does it have to be baked in?...

Thx!
[Thunderbolt Android Development] RjsShadows:
I completely agree with the call recording suggestion! I also love 1.92x! Its amazing to my phone
[Thunderbolt Android Development] want a droid:
Anyone use extreme and the 1.92? I've always stuck with the extreme, but I'm curious of 1.92. Is there noticeable battery difference between the two kernals?
[Thunderbolt Android Development] smashtheguitar:
There's no difference other than one goes to 1.92.
[Thunderbolt Android Development] smashtheguitar:
A higher clock means more juice
[Thunderbolt Android Development] Imoseyon:
this is a minor update. I'd say you don't really have to update unless you're having problems.

v2.1.1 Sense (5/8/11)

- 184Mhz slot disabled by default (use the enable_lowslot.zip in first post to re-enable it),

- filesystem speedup in ramdisk,

- full kernel version names.
[Thunderbolt Android Development] soundengineer:
Whatever the Default Kernel is for Liquid Smooth Roms...Thundersense... Doesnt work on my phone...

I had to flash the "Safe" version for my phone to get past the Boot Screen Thunderbolt logo.

I've literally spent 6 hours trying to get the rom to work only to finally figure out that its a kernel issue..

I would love to run the undervolted 1.41 "Normal" Kernel...but it always hangs at the Thunderbolt Logo screen no matter what I do with that kernel.
[Thunderbolt Android Development] 4dfl4:
I flashed your updated kernel but i still have 184Mhz slot, software info on my phone shows new kernel #42 Sun May 8
[Thunderbolt Android Development] BennyJr:
yeah me too. 185 is still enabled by default
[Thunderbolt Android Development] Imoseyon:
Yup you can see it but it won't go down there. Unless you tell it to via setcpu or flashing the zip.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] Imoseyon:
How does the call recording work from user's perspective? Is there an app that you launch?
[Thunderbolt Android Development] CJNYC:
Last night...

Last night on battsaver 2.1 I set the phone down on my desk at midnight with 68% charge. When I picked it up at 10:00 AM it immediately shutdown due to a dead battery. That's ridiculous. I didn't even breathe on the phone during that 10-hour period. I live in NYC, so I was on 4G but had full bars and I know the signal is rock-solid where I was.

Sorry, I'm not blaming the kernel, it's just my frustration with what is an otherwise brilliant phone is coming through in all my posts. The Droid Charge might be in my future, as I might be getting to the point that less polished software might be worth better battery life.

I will try 2.1.1 today. I truly appreciate all your hard work. Again, I'm not venting frustration at this excellent set of kernels, but rather at HTC for including a very small battery by modern smartphone standards.

Thanks again!
[Thunderbolt Android Development] Imoseyon:
hmm did you have wifi on at all? If not, as long as you had mobile data turned on what you experienced is very possible - i've seen it happen myself. v2.1.1 could help if your phone was having issues with the low slot.
[Thunderbolt Android Development] BennyJr:
I feel this kernal could be better..idk i went to see fast5 last week and i went in the movie with 78 percent..saw the 2:15hr movie then came out drove home and made a call and a couple of text's and it was still at 78. this one i havent touched really since 821 and its 11:12 and im down 6 percent already.
[Thunderbolt Android Development] corenojoe:
I gotta say I'm pretty happy with 2.1 extreme once I wiped battery stats and switched to smartsss governor. Take into account I was asleep and didn't touch it for about 6hrs, but still. Not too shabby. I got it set at 184 min and 1.222 max
[Thunderbolt Android Development] CJNYC:
No WiFi. Wireless data ALWAYS on. We'll see. Downloaded 2.1.1. Fingers crossed. Thanks again!
[Thunderbolt Android Development] TheImmortal68:
The call recording is done by an app CallRecorder which is included in the BAMF ROM. It loads at bootup and then automatically starts as soon as an incoming or outgoing call is initiated.
[Thunderbolt Android Development] NetworkPIMP:
There is an app that was included in BAMF 1.6 ... but, it seems that without kernel support, it doesn't work. It doesn't error (that I've seen), just does nothing.

That said, I fired up the app, auth'd it for root (SU pop-up), and now, it records all incoming and outgoing calls to the SDcard, and I can browse the recordings in the app.

And, I don't have to actually do anything, the recording just happens - all I see is the SU toast about the CallRecorder app at the start/end of every call.
[Thunderbolt Android Development] Imoseyon:
Haha yeah I told Ryan (Liquid) that 1.92X wasn't going to work for everyone. My normal version doesn't work for you? Contact me off line via twitter? I will build you a custom kernel.

To others who asked for call recording, I looked at the code and it's not a lot of additional code so either 1) i will add it to a future version, or 2) I will build a special version with it enabled.

EDIT: I did some battery testing this morning. 184Mhz does help with battery life as long as you're on wifi (or not on 4g/3g). Mine dropped like 1% in 2 hours of mostly standby and one quick phone call. So i think either 4g/3g just suck as we all know and/or 184Mhz doesn't do as well as 246Mhz on 4g/3g.
[Thunderbolt Android Development] WormDoes:
I'd love to try it on extreme. Would there be a way to add an enable/disable zip(s) that could be flashed on its own? Also, I'm kind of intrigued to see how low undervolted a phone can handle. Could it go below the 185?
[Thunderbolt Android Development] want a droid:
Would rather see a special version with it instead of it included in every version.
[Thunderbolt Android Development] Imoseyon:
I tried 123Mhz a long while ago but boy was it unstable. Doesn't matter though, 750VDD is as low as the phone will go and 184Mhz seems to be ok with it for the most part. As for the special zip, doesn't look like it can be turned into a module so it needs to be baked into kernel.

Agreed!
[Thunderbolt Android Development] BennyJr:
Yeah i have been running the 185 slot for about an hour or a lil more and it hasnt dropped at all.
[Thunderbolt Android Development] WormDoes:
Ok, I was just curious because 185 runs really well on my phone so I didn't know if we could try pushing it even further :) Would you make an enabled for every version? I was just speaking with adrynalyne about this feature so I'm really excited you're going to add it to your kernel (didn't want to switch to his...ssshhh, don't tell him ;))
[Thunderbolt Android Development] adrynalyne:
I love you too.
[Thunderbolt Android Development] Imoseyon:
Something else I've been thinking about while waiting for the movie to start is whether suspending at max 250mhz (interactive) is a good idea for mobile data. I wonder if the phone needs a bit more headroom when it needs to talk 4g/3g. When I get home I will experiment by allowing interactivex to go up to 360mhz to see how often that slot is used while screen is off.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] azturbomini:
Busted! That was funny...
[Thunderbolt Android Development] want a droid:
As always I can help test. Just PM me.
[Thunderbolt Android Development] imneveral0ne:
What theme are you using?
[Thunderbolt Android Development] WormDoes:
Don't get it twisted, bro I have mad love for you (no homo)
[Thunderbolt Android Development] Jaxidian:
Like others, mine is rock solid at 185 but after many hours will randomly refuse to wake from sleep and I have to do a battery pull.
[Thunderbolt Android Development] KGBxxx:
No homo!!! Classic
[Thunderbolt Android Development] cypherx82:
Is there any way to set it to 184 max while on Wifi and 245 max when on 3G/4G?
[Thunderbolt Android Development] ScottIsMyName:
I would love if you would include the call recorder in your kernel from now on

Sent from my Thunderbolt