yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Imoseyon:
I thought about that too, because otherwise everyone else would be doing it too right? ;) in the end I decided to give it a shot anyway because 123mhz isn't too slow and it's fun.

leanKernel + Tesla coil
[Thunderbolt Android Development] BurnOne77:
Hmm, changed from lame 0.6 kernel to lame 0.7 and the problem while surfing on stock browser persists.

It just hard locks and reboot. Funny cuz I can bench anything at 1.4 but when idle surfing the web hardlock within minutes unless I set to 1024mhz.

Made me think it was an idle step in the CPU speed when at 245mhz being too undervolted but then why not when I set max at 1024mhz...

I have tested up to 1.5 perfectly stable on other kernels... Kinda bummed cuz this and tesla coil are one of my fav combos.
[Thunderbolt Android Development] PerCompLLC:
LOL - gotta give you credit for that answer!
[Thunderbolt Android Development] adrynalyne:
I kanged your ondemand backport :D

https://github.com/adrynalyne/kernel_htc-mecha/commit/c3712974918d1163fdb68d9ee05ad9c51bf2be13
[Thunderbolt Android Development] RjsShadows:
I'm sorry if this is a noob question to ask, but what exactly is TUN?

I know it has something to do with VPN, Virtual Private Network, but I'm honestly not sure how that is used. Just curious.
[Thunderbolt Android Development] mbh87:
if you run speedtweak.sh and it says the lowest is 245 or whatever it is, id imagine you are fine. it is probably a preset script with all slots in it.
[Thunderbolt Android Development] Imoseyon:
hmmmm i just realized that my script will override what you set in setcpu every time you reboot. I'm going to have to add an option in the script to remedy this. In the meantime, there wouldn't be any real harm to set the limit on setcpu.

yup, if you'd like you can re-download. :)
[Thunderbolt Android Development] Imoseyon:
For VPN.

yup it's normal and perfectly harmless. Next version of script I'll remove it.
[Thunderbolt Android Development] WormDoes:
I figured it was fine, just wanted to double check
[Thunderbolt Android Development] RjsShadows:
I'm curious is there anyway we could adjust cpu frequencies?

I'd like one in between the 1017 and 1222, and between 1222 and 1408. :/

In ziggy's newest 5/3 kernel he allows you to pick and choose which frequencies you'd like to have on.

Is there maybe a downside when having to many frequencies?
[Thunderbolt Android Development] dc iz 2 legit:
Yayy I can finally post in here
[Thunderbolt Android Development] TsaiKimon:
Oh no, and that's what u posted, lol, that's exactly why you weren't allowed to post in here previously! I'm just amused not being a ****, its just funny in an ironic sort of way. Anyhow, welcome :)

Imoseyon, thanks again. I love watching your kernel progress, and feeling my phone improve all the while! Cheers!

DC, I real was just playing.
[Thunderbolt Android Development] dc iz 2 legit:
Lol...you saw that I was trying to get my 10 post....I have so many questions that I can't think off right now.

Nevermind what I just said..... in a defferent thread I posted....lol....and I thought u saw that
[Thunderbolt Android Development] staveandor:
Has anyone tested 2.5 sense lean on Wifi?

I ask because 2.4.2 -2.4.6 kicked everyone else off my router when I connected, and wouldn't allow anyone to connect until I disabled wifi and restarted the router.
[Thunderbolt Android Development] Smok3d:
At home I am always on WIFI and there is never a problem and it works.
[Thunderbolt Android Development] BennyJr:
Wanted to add u should increase the 3rd slot too
[Thunderbolt Android Development] BennyJr:
Got my first hang up when unlocking the phone....
[Thunderbolt Android Development] PineTre3:
thanks buddy, i'm gonna mess with it tomorrow i haven't had a full day to dedicate to voltages yet so i was just using someone's previous work but of course my luck isn't good and it didn't work lol

edit: by the way new interactiveX governor=awesomeness so far!
[Thunderbolt Android Development] BennyJr:
Bad news. I've gotten about 5 lockups on the sane voltages as the last kernal. Looks like I'm gonna have to raise em. I even tried the new governor and smartass and I still get lockups :-\
[Thunderbolt Android Development] PineTre3:
let me know what voltages end up working for you please!

Sent from my Thunderbolt
[Thunderbolt Android Development] BennyJr:
Yeah I'm testing some now
[Thunderbolt Android Development] PineTre3:
you're a good man

Sent from my Thunderbolt
[Thunderbolt Android Development] BennyJr:
haha well idk but i tweaked the voltages and still got a lockup, so i flashed back to 2.4.6 for tonight. im gonna have to mess with it more tomorrow, but something doesnt seem right. It shouldnt hang like that...
[Thunderbolt Android Development] Richpopski123:
184 @ 750

245 @ 775

368 @ 775

786 @ 850

1017 @ 950

1222 @ 1025

1408 @ 1125

As of now this is working for me. The 750 slots would not work on my phone. I tested these for about 4 hours, also have the top slots almost done for anyone that wants those...
[Thunderbolt Android Development] DieselvRR:
I installed the battsaver kernal from Kernal Manager on the latest Stock RUU. Experiencing major battery drain. 4 hours into the day and had 30% battery left. Is it the Kernal, latest update or combination of both? Ideas?
[Thunderbolt Android Development] mmtoman:
This post truly emphasizes what is so great about Android. Your kernel makes my phone so much smoother, less hot, and have WAY better battery life. The speedtweak script alone is just an amazing idea and is perfectly executed.

I am donating $20 to you as I type this and just wanted to let you know how great of a job your doing.
[Thunderbolt Android Development] ridobe:
Hahahaha. If you look through the thread, I've had the exact same problem. I can't figure out why I can flash a kernel that uses less voltage and cause more drain. I'm still trying to figure it out because sometimes the battery life is great and other times, not. Make sure your init.d file doesn't contain too many code lines setting the governor. For some reason, if you change it using Imos' script it will add the new line without deleting the old one. I've cleaned this up and it has helped.

It does seem to settle after a while. I also notice that ondemandx killed my battery while smartass didn't. That actually makes no sense at all. I also reverted all of my UV adjustments back to stock and that has seemed to help. Again, makes no sense. I think I'm going to download the latest version and give it another shot.

Also, if you use Setcpu I suggest freezing it in TB and only using the script in the init.d folder as to make sure there is no conflict. Hope this helps.
[Thunderbolt Android Development] BennyJr:
Well ive got a full battery so im gonna try it again

Well i left the voltages at the way imoseyon has em and its not locking up.
[Thunderbolt Android Development] keith.mcintyre26:
If you're experiencing drain issues I recommend wiping dalvik cache prior to installing.
[Thunderbolt Android Development] DieselvRR:
I havent touched the init.d file nor am I using smartass. Pretty much just loaded straight from kernal manager and getting battery drain. its been 1 hr off a bump charge. 2 phone calls and I am at 80% battery now. Using kernal manager clears all the cache needed.
[Thunderbolt Android Development] smashtheguitar:
For one, I'd avoid using kernal manager. Probably not the issue here, but too many problems crop up for people using it.

Also, are you using the 184mhz slot? It's possible that your phone doesn't like that and that is causing the drain. Otherwise, I'd reflash your kernal again and see if that helps.
[Thunderbolt Android Development] TMYINC:
Had a weird sleep to death issue last night. Well, sort of. Got up today and tried to turn my phone on and got the lights but no screen. Battery pull and rebooted. Was running the special kernel at min 245 and max 1408, interactiveX governor. I know you said you re-worked that governor so I was wondering if anything you changed might have cause that? Havent messed with the voltages at all yet and running LTS 1.45.

Oh and i had the 1.92 non-extreme set through the script, and using setcpu to clock down at the time. I dont think it was because of setcpu because I have been doing that for a while now. Didnt know if that info would help or not.
[Thunderbolt Android Development] BSDADON:
Was just about to post this. My phone absolutely hates that slot.My phone gets very hot and the battery life is horrendous. 246 works perfectly for me and my battery life is amazing.
[Thunderbolt Android Development] DieselvRR:
not using the 184mhz slot, locked by default on this kernal.....Ill let today run its course and try reflashing without kernal manager.
[Thunderbolt Android Development] BennyJr:
Ive been getting this too
[Thunderbolt Android Development] TMYINC:
Just with the newest update?
[Thunderbolt Android Development] Imoseyon:
One of the changes in 2.5 iX governor is that it wakes at 1Ghz instead of max speed. There may be a slight problem with that if your phone can't handle the undervolting too well at that speed. In fact the new iX governor uses a few other slots a bit more than the older version, so it may help you discover a few other undervolting issues.
[Thunderbolt Android Development] BSDADON:
Do you use setcpu? Because I think that can override the settings from the speedtweaks script. Someone correct me if I'm wrong.
[Thunderbolt Android Development] DieselvRR:
Nope...dont use setcpu...

thanks
[Thunderbolt Android Development] smashtheguitar:
This is probably the issue. Several folks have been able to drop their voltages to very low levels, only to find their phones locking up during normal/heavy use. Certainly until the latest gov. changes, you usually only had to really get the low and high slots set at a comfortable voltage, as the in-between slots rarely got used. If the gov. is now hitting on the middle slots more often (and waking at 1Ghz), that could absolutely be where the problem is if you seemed to be stable pre-2.5.
[Thunderbolt Android Development] sparkysshocker:
Just flashed 2.5 kernel update from 2.0 and now on boot Ive been stuck at the clouds for 10mins now any ideas?
[Thunderbolt Android Development] ridobe:
Battery pull. Re-flash using CW instead of kernel mgr. Wipe cache/dalvic.
[Thunderbolt Android Development] sparkysshocker:
Tried to no avail. and I deleted my 2.0 kernel zip off the sd card already :(
[Thunderbolt Android Development] DieselvRR:
I just went ahead and updated to 2.5 using CW. Used speedtweak to check settings and set to battsaver. Will let you guys know how it goes.
[Thunderbolt Android Development] ridobe:
I'd just reflash it again. Otherwise use a backup. You did make a backup, right?:o
[Thunderbolt Android Development] sparkysshocker:
It just gets worse getting an error while formating /system during restore.
[Thunderbolt Android Development] hijackerjack:
If you're at the clouds, it probably means you're still booting up. Happened to me before. If you get that far, your phone will probably turn on fully.
[Thunderbolt Android Development] TMYINC:
Makes sense. Just confuses me because I hadn't had any issues with the battsaver which I thought would be more undervolted the the "normal" 1.92. Does the battsaver kernel wake up at max speed? Just wondering if technically the 1.92 and the battsaver both wake up at 1ghz.
[Thunderbolt Android Development] ridobe:
I'm going to have to step aside for someone else to help you. That's not your sd card. Maybe you renamed your backup after you made it?
[Thunderbolt Android Development] TMYINC:
Did you try wiping data and cache/dalvik cache before restoring your backup? I like to do that before restoring a backup just to be safe. It may be an unneeded step but it makes me feel better ;)
[Thunderbolt Android Development] DieselvRR:
After reflashing to 2.5 on battsaver, I went from 66% battery life to 49% in 1 Hour on wifi with phone locked/idle.
[Thunderbolt Android Development] ridobe:
Ya know, I don't know if it's all kernels or just the few that have the ability to change the voltages, but I wouldn't trust the battery right away. They seem to be WAY off right off the bat. Bump charge and then reset batt stats first. Actually, I've noticed that it takes two good bump cycles to settle in.
[Thunderbolt Android Development] Imoseyon:
Yup. Give it some time. Also keep in mind that every time you reboot you could lose anywhere between 5 and 15 percent which is annoying I know.

sent from my phone running leanKernel + Tesla coil
[Thunderbolt Android Development] PineTre3:
very annoying, i don't believe this is because of your kernel though my girlfriend's phone was stock up untill yesterday but her's did the same thing on reboots stock
[Thunderbolt Android Development] IvanNCase:
Hey Imoseyon I saw your comment about interactiveX waking at 1Ghz and was curious what would see what would happen if i set the max below that and I found that if you do the phone drops to the lowest speed you have set and stays there. Only on iX weather you use SetCPU or edit 01vdd_levels.
[Thunderbolt Android Development] Auronis1:
Running these now, works so far thanks
[Thunderbolt Android Development] sublimaze:
I never delete old kernels. One day you will flash a kernel that has issues, and you'll need to revert to a previous build
[Thunderbolt Android Development] BennyJr:
This. very useful. thanks.
[Thunderbolt Android Development] RjsShadows:
Am I the only person experiencing proximity sensor problems?

I've made many phone calls and my screen won't turn off when I'm not looking at it.
[Thunderbolt Android Development] BennyJr:
Looks like my magic wake up voltage is 1000.
[Thunderbolt Android Development] TMYINC:
Im still trying to figure out what is going on with mine. Had the issue before so I reflashed and set up the battsaver which has the same vdd as the 1.92 for the 1ghz slot and no issues there. That is considering that battsaver option wakes at max frequency. Im befuttled :/
[Thunderbolt Android Development] BennyJr:
What governor u on?
[Thunderbolt Android Development] TMYINC:
iX governor at the moment.
[Thunderbolt Android Development] BennyJr:
So whats it doing? bad battery life?
[Thunderbolt Android Development] TMYINC:
Had a somewhat sleep to death problem. Lights would come on but screen wouldn't. Thought maybe it was the vdd levels like Imoseyon suggested but Im not having that issue with the battsaver option that wakes up with the same frequency at the same vdd level as the 1.92 I was running. Random reboots I have been getting are probably radio related but not sure if they add to the issue also.
[Thunderbolt Android Development] BennyJr:
Ahh i was having that problem alll last night lol ok whats ur voltage at for the 1ghz slot.
[Thunderbolt Android Development] TMYINC:
Its still at 1100. Haven't changed any of the vdd's yet. Still have the preset ones. Its strange because running another kernel the vdd was down to 975 at 1ghz and I didn't have any issues. I dont have the 186mhz slot enabled either cause I never liked it. Didn't have issues with it, just preferred not to go that low. This is why I am stumped lol. Restoring a backup of a different rom to see if it was rom related. Doubtful though since I have ran LTS for quite a while now. Stumps me even more lol. :confused:
[Thunderbolt Android Development] BennyJr:
Oh man, try running smartass governor
[Thunderbolt Android Development] TMYINC:
Yeah gonna try that next. I cant figure it out for the life of me. I dont want to increase the vdd levels at all either. Kind of defeats the purpose I guess. Im hoping it was just a freek occurrence and it doesn't happen anymore. I dont know what else to think.
[Thunderbolt Android Development] Richpopski123:
Is anyone having issues with 2.5? I thought it was my voltage changes but I reloaded the base kernel and it's still rebooting but only on wake. I'm going to go back to an older kernel to see if I have an issues.
[Thunderbolt Android Development] sublimaze:
I would reflash 2.5 first. I don't recall anyone else seeing that. If you still encounter that after reflashing, go back to an earlier build
[Thunderbolt Android Development] Richpopski123:
Reloaded, reflashed... My poor use of words. I already reflashed 2.5 once already. :)
[Thunderbolt Android Development] Imoseyon:
Did you use any custom voltages? Make sure your 1Ghz has enough juice...

I'm back home now - anyone else still have issues with v2.5?
[Thunderbolt Android Development] bokechukwu1:
Yeah my kernel is draining my batt fast as well on 2.5 batt saver mode
[Thunderbolt Android Development] DieselvRR:
Still battery issues on v2.5 in battsave mode...
[Thunderbolt Android Development] Imoseyon:
Which kernel did you flash? normal lean or 184Mhz?
[Thunderbolt Android Development] DieselvRR:
I flashed lean v2.5 and used speedtweak to set to battsave mode. didnt mess with voltages or governors.
[Thunderbolt Android Development] Imoseyon:
Interesting, do me a favor and try Extreme to see if you see the same battery drain? Make sure you're not running the 184Mhz version. Also try a different governor.
[Thunderbolt Android Development] DieselvRR:
did you want me to try a different governor with the lean or with the extreme after i flash?

Thanks
[Thunderbolt Android Development] Imoseyon:
Lean kernel in battsaver mode with a different governor first, if that doesn't help Try enabling the extreme mode.
[Thunderbolt Android Development] DieselvRR:
sweet..will do and let you know whats up.

thanks
[Thunderbolt Android Development] bokechukwu1:
Along with poor battery life 2.5 is sluggish upon wake up and while you're using the phone it gets sluggish as well
[Thunderbolt Android Development] ridobe:
Imoseyon, I flashed 2.5 extreme/interactiveX this morning with minor changes to UV. I bump charged and have been using the phone pretty hard all day. I've been on wifi mostly but was on 4G for 2 hours earlier. I'm still over 50% at the 7 hour mark. I will bump charge once more tomorrow at work. I will be on 4G the entire day until dinner time for a good test.

Everything feels much better on 2.5. It is snappy as hell @1.4 and so far the battery has been excellent. I hope this sticks because I am really enjoying the features you have put into this kernel.
[Thunderbolt Android Development] DieselvRR:
Sounds promising...maybe I should just change to extreme and run with overclocked. I was trying to avoid overclocking, just wanted the best battery life. But if lean\battsaver mode wont work with my phone for some reason, I'll try the extreme as you and Imoseyon suggested.

I just switched to smartass governor on lean\battsaver. We'll see how that goes.

Thanks
[Thunderbolt Android Development] ridobe:
I had horrible luck on battsaver and/or smartass/ondemand. Give your new setup a chance but don't give up. Try what I posted afterwards. I have come to the realization that you DO need two battery cycles to smooth things out. I even undervolted a bit and all seems well. Check out my voltages in the "post your voltages" thread.
[Thunderbolt Android Development] Nikolai2.1:
Since I flashed this kernel... i cant reboot or power off the phone.. It does a hot restart and powering it off just locks the screen
[Thunderbolt Android Development] Richpopski123:
Originally Posted by Richpopski123

Reloaded, reflashed... My poor use of words. I already reflashed 2.5 once already.

Did you use any custom voltages? Make sure your 1Ghz has enough juice...

I'm back home now - anyone else still have issues with v2.5?

I did not. I had been using custom voltages but as I found what I thought was stable you posted 2.5. I then applied my custom to 2.5 and started getting lock ups. I then reflashed 2.5 to see if that was the problem, but again had a few lock ups. Went back to 2.4.6? ( I think that was the one) and its been working great.

I will reflash a little later to make sure it was just a fluke.
[Thunderbolt Android Development] Nikolai2.1:
Never mind, turned out it was the rom
[Thunderbolt Android Development] Imoseyon:
whew dodged one! Anyone else?
[Thunderbolt Android Development] bokechukwu1:
Im on extreme clicked to 1.4 and my battery life isn't the biz right now on 2.2 my battery life was Gold went through a full day of work and phone had 85% left extended battery of course also it might be in my head but on version 1.0 normal the in call volume and over all volume was louder one last thing on this new version it gets extremely sluggish after a while
[Thunderbolt Android Development] :
Is there a specific way I'm supposed to get SWAP to work?

I flash the file in CWR and then reboot and then reboot again. It becomes super laggy and I can't do anything, being forced to battery pull into recovery and flash the disable SWAP. Ideas?
[Thunderbolt Android Development] tekhna:
After a few days of playing around, I've found smartass to be pretty frustrating. It's slow to unlock, scrolling through my app drawer it stutters and hangs, and opening apps often takes a very long time. Ondemand seems to work pretty well, both in terms of battery and performance. Using extreme, min 246. Anyone experiencing the same?
[Thunderbolt Android Development] bokechukwu1:
I'm experiencing this with all governors unfortunately you aren't the only one
[Thunderbolt Android Development] lect1984:
set your min to 346.
[Thunderbolt Android Development] BennyJr:
Guys remember it unlocks at 1ghz, so make sure u give it enough juice or else its gonna be laggy. 1012 @ 1000 seems to work well for me
[Thunderbolt Android Development] NetworkPIMP:
those of us w/ WiFi issues...

Regarding the rare few of us who are seeing our WiFi AP's/routers having troubles with your kernel:

Imoseyon, I haven't had an opportunity to flash CM7 as you asked on Twitter - and while I still intend to make time to do this, I wanted to make a quick comment to your point about WiFi drivers and how you use a different one w/ CM7 vs Sense kernels...

As I've mentioned, I don't have this issue when I use Adryn's kernels. In his kernel thread OP (http://goo.gl/7BB5f), he mentions "Changes to wifi power management (4.2+)" but doesn't indicate a change in the wifi driver.

In the OP here, you mention that you "backported 2.6.35 wifi driver" because of it's low-power mode.

Furthermore, your request that I try things out under CM7, implies yet a 3rd flavor (tho, this may not be accurate).

I'm wondering if the cause of this issue is buried somewhere in the differences in the various drivers (assuming that I'm correctly inferring that the drivers are, in fact, different - not just tweaks on the same one).

I've noticed that things go awry both with WPA2/AES and when wide open.

In my case, the AP resets itself... repeatedly. Others have reported that users can't access anything until the phone is disassociated from the AP.

In addition, I've noticed that some AP's are more resilient to the issue than others - for example, our enterprise-grade high-end bookoo expensive Cisco Wireless infrastructure where I work seems unphased - but my cheap "small business class" AP's by DLink at home, as well as my old Linksys WRT54GSv4 can't seem to manage it.

So, the issue seems manifested on 2 fronts, both within the kernel or driver, and on certain AP's that can't deal with whatever is going on.

While this certainly speaks to a potential weakness of certain AP's out there, I think if we can identify where the issue is in the kernel/driver, it's easier to attack that than for you to say "my kernel is awesome [which it is] but you can't use WiFi with certain AP's [that may be fairly common]."

This clearly isn't a wide-spread issue - not a lot of reports - but your insight is appreciated none the less.

Thanks again for all your effort, Imoseyon... I'll make time this week to get CM7 on there and see if the issue recurs.

-J