yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] T41NT204:
hah, yes i am in the wrong thread. damn oxys got me reading wrong n posting wrong all week bahh sorry lolz. i liked ur 1.9 and such but they didnt feel that stable for my device or me. idk
[Thunderbolt Android Development] Imoseyon:
v0.7

- Added 123mhz at 550 VDD for extended battery life. Removed 245mhz & 460mhz, and added 370mhz. Went back to my own overclock code (for the most part) without losing speed.
[Thunderbolt Android Development] giobotta:
bootloop Help!!

well i saw the rave about this kernel and was turned onto it by a close work friend but now my phone is in a bootloop and i dont know how to get into clockwork recovery manualy please help!! i gotta restore the backup i made.
[Thunderbolt Android Development] giobotta:
my phone wasnt able to handle the 1.9 ghz i dunno why what should i use? i rly wanted 1.9ghz
[Thunderbolt Android Development] Imoseyon:
Try this one: http://cl.ly/1H3H3x3r2C0x2r3r4002
[Thunderbolt Android Development] Imoseyon:
plug it into pc via usb, pull battery, replace battery, and then power up - you should get clockwork.
[Thunderbolt Android Development] thechopster:
I'm using 2.4.4 sp and I'm seeing that CPU is always at max. I also tried using Setup but same result. Btw- I wiped data from setup also. I have tried rooting and also wiping cache and cache but same results. I flashed adrynylyn's kernel and it is able to settle back down but I really want to give these new ones a shot. Any suggestions?
[Thunderbolt Android Development] thechopster:
That should say Setcpu and not setup
[Thunderbolt Android Development] BennyJr:
Hmm thats weird. Mine was doing that too. Did u choose a governor?

I just caught my cpu running at 1.7 when i set the speedtweak to 1.4...maybe thats why i got a random reboot
[Thunderbolt Android Development] biglipps66:
Funny you mentioned that I noticed it as well. Im back on the old kernel now with bamf 161 and problem is gone. Might have been a slight glitch. Ill try his new release when its out again shortly
[Thunderbolt Android Development] thechopster:
I've tried a bunch of things including setting a governor in terminal and also separately in Setcpu. I think I got it working by deleting Setcpu and restoring after wiping both caches. I think there is a conflict with the kernel's governor and setcpu's. I actually prefer to control the governor and the clock speed via setcpu while using terminal to switch the type of kernel.
[Thunderbolt Android Development] jlevy73:
Wow, this kernel has grown into a monster of it's own.

What's difference between lean vs special for Sense kernels? Didn't see it mentioned in the OP.
[Thunderbolt Android Development] Nikolai2.1:
Taken from the OP:

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

2) special edition: slightly less lean. Supports in-call recording, and TUN. "speedtweak.sh" script also available.
[Thunderbolt Android Development] jlevy73:
Doh, don't know how I missed that. Thanks :o
[Thunderbolt Android Development] Nikolai2.1:
lol its cool
[Thunderbolt Android Development] staveandor:
Just wanted to drop an update:

Wifi on 2.2 connected to my access point, but made it completely unreachable to all other wifi devices. Connectivity wouldn't restore until I disabled wifi on my phone and manually reset the router.

Haven't had a chance to try it on 2.4.

Either way, I love this kernel. Thanks for all the hard work!
[Thunderbolt Android Development] Nikolai2.1:
Did you flash from kernel manager? Don't do that. it breaks wifi
[Thunderbolt Android Development] BennyJr:
Ok I caught the CPU going higher then what i set it at in the script. So I'm trying out the das bamf CPU settings.
[Thunderbolt Android Development] bokechukwu1:
I noticed this in the last version as well
[Thunderbolt Android Development] thechopster:
I tried the das bamf toolkit CPU setting tool and the CPU was still maxed regardless of governor or frequency setting used. I flashed back to adrynylyn's kernel and it went back to normal. I really want to check out this kernel but I just can't get it to settle.
[Thunderbolt Android Development] 52brandon:
odd, and you set das BAMF CPU and setCPU to the same settings?
[Thunderbolt Android Development] 52brandon:
I got consistent 59s on linpack at 184-1408 on smartass with lower voltages. Then I went to interactive and 1408-1408 and it went down to consistent 50s. Confusing...
[Thunderbolt Android Development] infinite_loop:
Once we use the speedtweak.sh script, do we need to use the cpu settings from bamf toolkit? Or once you script, you're done?
[Thunderbolt Android Development] JonKyu:
Awesome mine seems to run pretty good with your voltages and patdroids voltages for 1.2ghz+ question is is there any point in using 184MHZ and 245mhz if 368mhz is already at the lowest voltage?
[Thunderbolt Android Development] Nikolai2.1:
Honestly i dont know. and i stopped doing this because i was having spontaneous reboots and lag all day long. Although UV should not affect performance, it does... and i think 184 and 245 might save a tad bit of power lol
[Thunderbolt Android Development] JonKyu:
Oh really? Damn. I'll run this voltage a bit long and see how my phone fares, it *seems* like it's stable though.
[Thunderbolt Android Development] Imoseyon:
So the only reason your phone will go above or below the clock frequencies set by speedtweak.sh is if something is overriding it. Setcpu will do that.

Say you ran the script and chose "extreme" which sets a soft upper limit at 1.4Ghz. And then for whatever reason you ran setcpu. That could have easily reset the upper limit to 1.92Ghz. Does this make sense? I'm going to try to see if there's a way I can shield the speedtweak settings from setcpu but that's not going to be trivial..
[Thunderbolt Android Development] Nikolai2.1:
Which ones are you using for 1.2 and up again? I want some for 1.5-1.92 to try
[Thunderbolt Android Development] Imoseyon:
How did you catch this? Bet you ran setcpu. ;)
[Thunderbolt Android Development] JonKyu:
I'm using patdroids stable voltages 1075 and 1125 for 1.2ghz and 1.4ghz respectively. I left 1.5ghz and up the stock voltages.
[Thunderbolt Android Development] Nikolai2.1:
i wanna lower those but im scared im gonna break it again lol, and i might try it again. The reboots were still happening even after i set the stock voltages and reflashed the kernel. i reflashed liquid and it seems fine now
[Thunderbolt Android Development] Imoseyon:
You're now the third person to report this problem and I guess I can't ignore it any more. :p

Can you reproduce the issue consistently? Would you like to try CM7 and one of my CM7 kernels? The reason I'm asking is because my CM7 kernels have a completely different wifi driver. I can also try reverting the wifi driver on my sense kernels but then we lose the low power mode. I will do a test build anyway.
[Thunderbolt Android Development] JonKyu:
Hmm weird, I'm running bamf and haven't had those issues yet.
[Thunderbolt Android Development] Nikolai2.1:
I think it was a bad flash or something.. guess ill try UV again... do you or anyone else have any suggestions for 1.5-1.9?
[Thunderbolt Android Development] thechopster:
The way I can tell the cpu is maxing is by using SystemPanel- it lets me know the freq. and also the % of cpu used. I was wondering if there could be a way to allow setcpu to overide the kernel's governor?
[Thunderbolt Android Development] JonKyu:
Not yet lol I don't really run at that high usually lol, I think the higher you overclock the more finicky it gets with right voltages.
[Thunderbolt Android Development] Nikolai2.1:
yeah me too, but there has to be something:p

Imoseyon what do you think?
[Thunderbolt Android Development] DroidTh3ory:
Anybody up for pulling the files needed from BAMF to take advantage of the call recording support in this kernel. I am running extreme with the "Special" and Tesla Coil. Never been so happy, straight up bad ass.

I vote for kernel king to be titled. :)

___

Sent from my HTC ThunderBolt 4G LTE.
[Thunderbolt Android Development] staveandor:
Nope. I manually flash everything in CWR.
[Thunderbolt Android Development] Imoseyon:
Oh most definiltey
[Thunderbolt Android Development] Nikolai2.1:
lol i meant like what voltages do you think i should do for 1.5-1.92? i know its the lowest your phone can handle but i wanna try some if i can... unless its 25-50 like you said, then theres no point lol
[Thunderbolt Android Development] JonKyu:
Try lowering by 200 lol

Edit I meant 100 lol :-P
[Thunderbolt Android Development] Nikolai2.1:
i tried that once and it froze.. :(
[Thunderbolt Android Development] Imoseyon:
1.92X uses the following:

1593600: 1300

1766400: 1350

1920000: 1450

I don't think you can go much lower than those even with some super lucky phone. 25-50 at most. My phone will crash with anything lower than the above.
[Thunderbolt Android Development] BennyJr:
Actually i have this temp+cpu widget. I disabled setcpu. It didnt do it for a while, then it started doing it.
[Thunderbolt Android Development] Nikolai2.1:
me too, even if its just 25 lower... so i guess im SOL, but those are really low to begin with..

hey if we put 184, 246, and 368 to 750, is there any point in using the first two?
[Thunderbolt Android Development] Imoseyon:
Do me a favor. When this happens can you run the speedtweak script immediately, and look at the current settings? Pay attention to what it says about min and max and post them here?

Nope, if you can run 368 at 750 without crashing or overheating, you should use setcpu to set min at 368.
[Thunderbolt Android Development] 52brandon:
I think the apk is in the themes and apps section
[Thunderbolt Android Development] Nikolai2.1:
alright awesomeness, ill start doing that :) i can do

184 750

246 750

368 750

768 850

1017 950

1.2 1050

and i wanna do 1100 for 1.4 but it keeps freezing lol
[Thunderbolt Android Development] Nikolai2.1:
Weird... as soon as i started using 368 as the min it started rebooting...

Im just gonna go back to your extreme voltages. batt life already great lol
[Thunderbolt Android Development] Imoseyon:
v2.4.6 Sense (5/12/11) - reverted to EXT3, EXT4 was killing quandrant scores. Will bring back EXT4 after more testing.

Ok took me the whole day to figure out why quadrant scores were so low. Did I miss any questions? Any other issues aside from min/max being overridden?
[Thunderbolt Android Development] Nikolai2.1:
If we dont care about quad can we just keep 2.4.4? or was there something else?
[Thunderbolt Android Development] Imoseyon:
Totally. There was a very tiny cosmetic change in the speedtweak script as well, but only upgrade from 2.4.4 if you care about quandrant scores.
[Thunderbolt Android Development] Nikolai2.1:
Im good then :p
[Thunderbolt Android Development] PineTre3:
^^ agreed the 246 kernel is sick, super fast and my battery is a million times better with no more over heating! i pulled my phone off charger at 9:30am with mild use all day and i'm still at 83% right now (with extended battery)
[Thunderbolt Android Development] 52brandon:
so far I'm at:

and it's been stable so far
[Thunderbolt Android Development] Nikolai2.1:
you sir are lucky... i can actually pull 768 and 1017 down a little more... but 1.2 and 1.4 lock up on me there
[Thunderbolt Android Development] 52brandon:
I'll play with those values some more. Right now I'm streaming a video and will screw with it after. I do know that when I lowered all of those values by 25 it froze, so I need to be more specific. Thanks for the tip
[Thunderbolt Android Development] Nikolai2.1:
let me know what happens :)
[Thunderbolt Android Development] 52brandon:
no bueno. I got bored and decided to give your values a shot on the 1 and 1.2ghz. Froze and went down. Put it back on mine and its back up and ok, guess I dont have as much room as you on some slots, and then the opposite is true on others... weird
[Thunderbolt Android Development] Nikolai2.1:
it might be how the voltages on each slot correlate with each other.. but every phone is different
[Thunderbolt Android Development] JonKyu:
This is what I'm on right now:

368 750

768 825

1017 900

1.2 1000

1.4 1075

I could go to 1050 for 1.4 but it was a little finicky so I upped it to 1075. I think these are just about as low as I can go.

EDIT: I'm gonna have to tweak this a little, it boots and works fine, but as soon as it sleeps it doesn't wake up hahaha
[Thunderbolt Android Development] thechopster:
Imoseyon- any chance of allowing setup to override the script governor for us who are having the CPU max out? I loved you earlier kernels but I just can't get the new ones the settle.
[Thunderbolt Android Development] 52brandon:
could be. Now mine's acting retarded (lebron is a ***** for apologizing to the folks that got their panties in a bunch over him saying that). I think I'm gonna reinstall the kernel and start over from scratch
[Thunderbolt Android Development] Nikolai2.1:
man you got you 1ghz lower than mine! envy:mad:
[Thunderbolt Android Development] Imoseyon:
Sorry i think i missed this earlier. What exactly is happening and how do you tell if the CPU is being maxed out?
[Thunderbolt Android Development] Imoseyon:
So this means that your lowest clock speed is not handling the undervolting too well. Bump it up by 25/50.
[Thunderbolt Android Development] JonKyu:
Thanks I'll try that, I dunno what happened though I reflashed the kernel to recover from a frozen sleep and I got a weird UID mismatch error message and everything was all screwy I'm gonna try restoring from a backup. Do you know what could have caused it? All Ive been doing is editing the 01vdd_levels file. :confused:
[Thunderbolt Android Development] JonKyu:
Lmao do'nt be envious quite yet I've run into some weird UID mismatch thing x.x
[Thunderbolt Android Development] Nikolai2.1:
so i see :cool:

just re download the kernel and try again
[Thunderbolt Android Development] JonKyu:
Lmao Ok I concede

heres my most stable

368 750

768 850

1.0 950

1.2 1050

1.4 1125

I think the 1.4 spot was killing me haha, I think I'm happy with this I don't think going any lower would really do anything. :cool: I might try going down 25 for 768-1.2 though.
[Thunderbolt Android Development] Nikolai2.1:
i might give these a shot.. im just tired of failing with voltages
[Thunderbolt Android Development] JonKyu:
OMG tell me about it x.x; I've been testing voltages since 5:30pm and it's 10:23pm.
[Thunderbolt Android Development] Nikolai2.1:
ive been trying for like two days :p
[Thunderbolt Android Development] BennyJr:
Lol that's why I leave the developers to do the voltages :)
[Thunderbolt Android Development] Nikolai2.1:
yes but some times other phones can go lower than theirs
[Thunderbolt Android Development] thechopster:
Imoseyon- I can see that the cpu is maxed out from an app called SystemPanel. Basically I can't get the frequency to settle. The CPU is basically maxed out from the get go and doens't throttle down at all. I asked regarding allowing SetCPU to override the script governor because it allows for additional control of the frequency and might be the way I can get my fussy TB to settle with your new kernels.
[Thunderbolt Android Development] BennyJr:
Are u wiping the dalvik before u flash? Im running the new kernal just fine and so are others. It may be something besides the kernal. Try a re download. and wipe the dalvik cache
[Thunderbolt Android Development] thechopster:
Yes, I always wipe cache and dalvik cache before I flash a new kernel. I also, when using SetCPU, clear data and reboot again as Adrynylyn suggests. I don't think I am the only one having this issue as there are others who have posted a few pages back. BTW- how are others checking to see how the CPU is doing?
[Thunderbolt Android Development] BennyJr:
Oh hmmm idk then buddy, im using a cpu widget that shows it in real time.
[Thunderbolt Android Development] Imoseyon:
The only risk of running setcpu is that it can inadvertently override the min and the max that was set by the speedtweak script. (oh it can also override the governor setting but that's not as bad).

Go ahead and run setcpu and do your thing. But also use it to see if the cpu is truly maxed out constantly. I like going to the Info tab looking at "Time in State".

Which ROM are you running?
[Thunderbolt Android Development] Nikolai2.1:
wow running these EXACT same voltages and it works great!!!!
[Thunderbolt Android Development] thechopster:
I have been running LTS 1.45. I just restored to the stock rooted ROM and I'm testing it now.
[Thunderbolt Android Development] BennyJr:
A good app also for time in state is cpu spy
[Thunderbolt Android Development] smashtheguitar:
Running these voltages with no problems so far:

368 750

768 850

1.0 950

1.2 1050

1.4 1150

I tried sticking with 1125 for 1.4Ghz, but it kept rebooting during quadrant tests. 1125 seemed stable otherwise, but I think any heavy lifting will cause reboots for the average TB.

I also tried dropping the 768mhz to 825, but that just brought more reboots.

I don't think anyone will be getting much lower than these settings.
[Thunderbolt Android Development] Nikolai2.1:
who cares about quad? im running 1.4 1125 and did a stress test and nothing happened
[Thunderbolt Android Development] smashtheguitar:
Several folks say they are running just fine at 1125. Depends on the phone. I don't care about the quad score, just the possibility of lockups. I'm not sure a 25vdd difference will even be noticed anyway, so ill stick will the stable settings in my phone rather than risk reboot at a bad time.
[Thunderbolt Android Development] 52brandon:
everybody, duuuuuhhhhhh. It doesn't matter if your phone is the fastest, smoothest, make you coffee in the morning most awesome thing ever if your quadrant is under 2000
[Thunderbolt Android Development] Nikolai2.1:
Yeah that means over clocking to 1.4 all the time for no reason ;)
[Thunderbolt Android Development] JS0724:
I personally use SystemPanel. However, I would not trust its CPU information. I often find that it is displaying incorrect values. Also, the app itself is CPU intensive so the clockspeed is high just because the app is open. I bet it clocks down as soon as you exit.

As mentioned previously, time in state readings are what you should look at. SetCPU and CPU Spy are both good apps to check them with.
[Thunderbolt Android Development] JonKyu:
Thats good to hear! Mine has been pretty solid so far.

Edit: Just did and quadrant and the nothing bad happened, only bad thing that came up was my quadrant score lmao but I still running the ext4 kernel so its expected.
[Thunderbolt Android Development] bmerrill63:
+1

I have been using CPU spy for a few weeks now. It gives you a list of the frequencies you are running and a percent that the CPU spends in each slot. It seems to be very accurate but, what do I know.
[Thunderbolt Android Development] JonKyu:
Anyone flash the tweaks.zip and enable swap.zip with the current kernels? My phone went wacko when i tried flashing them lol
[Thunderbolt Android Development] biglipps66:
Im debating on trying these voltages myself... hmmm.. just another darn thing to mess with on this phone :p
[Thunderbolt Android Development] digitalscars:
been running these kernels since i've installed BAMF. I have a question though, currently im running 1.6.3 with kernel 2.4.6 set to extreme with 184 unlocked. When my screen is off at idle my phone gets great battery life. but when i use it for looking on xda app or browser it is losing 1% every minute give or take. is this normal? does this even when browsing market also.
[Thunderbolt Android Development] Imoseyon:
Lock 184, reboot and try again? I know it seems counter intuitive but that slot can mess you up in many different ways.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] MadBrad11:
I have been using the v2.0.5AOSPbeta and noticed that the audio much lower than it used to be, especially on speakerphone. Looking through the source for both AOSP and sense kernels I see that the audio tweaks have been removed and are no longer there. Was there a reason these were removed and could they be possibly added back?

I also have been having a problem with speakerphone while in the car dock with this kernel. If speakerphone is on I cannot hear the caller and the caller cannot hear me while in the dock. I'm not sure if this is a kernel problem or a CM7 problem though.
[Thunderbolt Android Development] distortedloop:
We all like to see a high quadrant score every now and then, but it's so easy to trick it's meaningless in many ways.

What I care about with the post you replied to is that running Quadrant causes a reboot with his settings. Obviously an issue if any app that normally wouldn't cause a reboot suddenly does, regardless of the results of any other particular stress test. ;)
[Thunderbolt Android Development] biglipps66:
I definitely use it for personally knowing the changes Ive made dont have a negative effect on my phone performance. Just 1 benchmark tool for testing! Its like tweaking and overclocking a PC, you dont run with it unless you know that shiz is stable right :D
[Thunderbolt Android Development] mzimand:
What is the best way to make the Voltage changes that everyone it talking about?

Does the app Voltage Control work for the Thunderbolt, I use it for my Galaxy Tab.

Thanks in advance for someones help
[Thunderbolt Android Development] Nikolai2.1:
Yeah true, it started happening with me with the market..so i raised a couple of slots by 25
[Thunderbolt Android Development] Nikolai2.1:
no.. read the OP
[Thunderbolt Android Development] mzimand:
I read the OP.

I am referring to post where people are modifying the slot frequencies and lowering the voltage. I do not see where in the OP it says how to do this. I am able to use the scripts but those are preset. People are talking that they are further modifying each slot and lowering the frequencies.
[Thunderbolt Android Development] Nikolai2.1:
Root Explorer

/etc/init.d/01vdd_levels

modify that file and reboot
[Thunderbolt Android Development] BennyJr:
Ok i wanna try this. No one has posted like a step by step for us noobs.

open root explorer

then....?
[Thunderbolt Android Development] mzimand:
That is exactly what I was looking for, thanks
[Thunderbolt Android Development] BennyJr:
Wait i found it. thanks
[Thunderbolt Android Development] ridobe:
I downloaded the latest 2.4.6 version (lean) and locked the 184 slot. I enabled the ondemandX governor, and the battsaver mode and that is all I have changed. It has been extremely stable.

Why is my battery draining like it has a hole in the bottom? Funny thing is that the exact same thing happened with Adryns' 2.0 CF kernel. I don't get it. This doesn't happen on undervolted kernels, at least not extreme UV kernels.

Does undervolting have this effect on some phones? That is the only thing that is different. I have really enjoyed modifying my own kernel but I will have to go back to something that I know doesn't kill my battery.

Any insight?
[Thunderbolt Android Development] LexusBrian400:
Anyone else lose WiFi after flashing the new Lean?
[Thunderbolt Android Development] BennyJr:
did u flash through kernal manager?

I found that the ondemand governor is broken. It just keeps the cpu maxed out.
[Thunderbolt Android Development] WormDoes:
Just getting around to trying this new sense kernel. Before I flash it, dumb question, how do you go in and manually change the voltages?
[Thunderbolt Android Development] LexusBrian400:
No, I flashed through recovery. Wiped Dalvik also

:confused:

Edit: I cant even turn wifi off now. it just keeps looping. bummer cuz the kernel rocks speedwise
[Thunderbolt Android Development] BennyJr:
Hmmm thats weird. Try and download it again.
[Thunderbolt Android Development] BennyJr:
If u have root explorer go to this file

/etc/init.d/01vdd_levels

So

open root explorer

Scroll down till u see /etc

Open then scroll down till u see /init.d

Open and the vdd level file should be there, open it and edit the voltages.
[Thunderbolt Android Development] WormDoes:
Good stuff, thanks for the quick response.