yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] thegregbradley:
Same thing for me, I used to ALWAYS run BFS with sense roms cuz it ran amazingly, but BFS with CM7 and my phone just makes it run like bull****. Been running CFS for about a month now with various versions of SZ and it's like buttah.
[EVO 4G Android Development] BlueHarford:
Your bfs revert is on the mirrors as 1.0.1 ;)
[EVO 4G Android Development] locozildjiangodx:
i used the new mirror for 1.0.1 from yesterday and it works MUCH better. soooove like buttah
[EVO 4G Android Development] twiz0r:
My phone is running Extremelyyyyy slow on 1.0.1. Was great on 1.0.0. ANy ideas?

So slow I cant even swype properly

swyped from my cyanogenized and gingerbreaded EVO
[EVO 4G Android Development] jpmaniac87:
If you run bfs, check 2 posts above yours
[EVO 4G Android Development] twiz0r:
I run cfs, my phone hates bfs

edit: my phone is so slow right now i had to log on the computer to do these posts. I'm at work so I don't really need to use my phone. Leaving 1.0.1 on it for now so I can see if you guys have any ideas for me to try
[EVO 4G Android Development] Sprintdaddy:
Is your phone plugged in? Seems that when the phone reaches 100% and plugged in the CPU goes to 100% and gets really really laggy.
[EVO 4G Android Development] wase4711:
I apologize if this has been covered, but I have been away from this kernel for a few weeks

will the newest 1.01 cfs kernel allow hdmwin to work with cm7 RC4?

thank you very much!
[EVO 4G Android Development] twiz0r:
I do not have it plugged in
[EVO 4G Android Development] twiz0r:
Yes it will
[EVO 4G Android Development] wase4711:
thanks, twiz! :D
[EVO 4G Android Development] twiz0r:
Anything I can do to help. I wish that I had more knowledge to that I could be more helpful to all my fellow XDAers.

BTW: When I was running 1.0.0 I was having AMAZING battery life. 17 hours off the charger yesterday and I had 49% left. Albeit with light to medium usage, but still about 3 hours better than I was getting. I was having issues with SBC, though
[EVO 4G Android Development] LifeInTheGrey:
I saw your comment about 1.0.1 struggling ... did you downloading right when it came out, or within the last day? They updated it yesterday morning because they realized some commits were missing, I personally was having a quirky experience with the original, but the remix works very nicely. :)
[EVO 4G Android Development] cheflarry:
The non havs is working great. No random reboots and I can over clock and underclock and the SBC charged straight through the night. Ty
[EVO 4G Android Development] twiz0r:
I downloaded it this morning. I also double checked to make sure I didn't accidentally d/l the bfs version
[EVO 4G Android Development] rebosxl:
that non havs kernel he posted was sbc?
[EVO 4G Android Development] LifeInTheGrey:
Hmm ... and you're a pretty savvy user, I'm sure you wiped both caches when flashing and fixed permissions again. Are you using SetCPU? The only thing I can think of is if the CM internal CPU settings were conflicting with some profile you set in SetCPU, it could go haywire. I experienced that, its the reason I stopped using SetCPU and went straight CM.
[EVO 4G Android Development] twiz0r:
I wiped cache/dalvik 2x with amon and fixed permissions upon reboot (took foreverrrr). I am using setcpu, but i have the CM settings turned off. I tried multiple governors (performance, conservative, ondemond, interactive)
[EVO 4G Android Development] LifeInTheGrey:
Out of curiosity, you may consider just temporarily turning off SetCPU and using CM settings. It may be a problem in the coding, that it turns on whether you activate or not.

If that doesn't work out ... I dunno. I say if 1.0.0 was working for ya, flash back to that guy and try 1.0.2 when it comes out. These devs are pretty solid when it comes to expeditious updates. :)
[EVO 4G Android Development] twiz0r:
I'm trying another reboot and if that doesn't do anything I will try turning setcpu off, then I will revert back to 1.0.0. Just wish the sbc didn't act so spotty for me on it.

EDIT: I flashed the bfs version of 1.0.1 and so far everything is great. Possibility they were labeled wrong? Just asking because my phone usually hates bfs
[EVO 4G Android Development] androidEVOlution:
I'm using native CM settings to OC, but in also using 1.0.1 SBC/HAVS.

Are you guys saying that HAVS is preventing me from truly being OC'd?
[EVO 4G Android Development] LifeInTheGrey:
Um ... I don't recall ever actually typing HAVS at any point haha.

But no, HAVS is one of those things that it either works for you or doesn't, there is no in-between. If you are OCing with HAVS and everything is running smoothly, then you are right as rain. :)
[EVO 4G Android Development] androidEVOlution:
No you didn't mention HAVS, but someone (it nay not have even been in this thread to be honest) said that scaling voltages basically nullified OCing.
[EVO 4G Android Development] rockenrooster:
I redownloaded from the mirror yesterday and I still get the 100% CPU usage with android system when I am at 100% battery AND plugged in AC power. I dont like knowing my phone is at 100% cpu while charging overnight for 8 hours. Haven't tried usb charging yet. I tried the bfs kernel and same thing. Other than that it is an awesome kernel.

cm7 rc4

SZ 1.0.1 Cfs GB
[EVO 4G Android Development] BlueHarford:
Android System at 100% is rom related not kernel
[EVO 4G Android Development] asqwrd:
How are u guys getting 30 hours battery life? Can u tell me wat ur setup is like what governor ur using cuz I.never get those hours even wit light use I might be lucky to get 15-20?
[EVO 4G Android Development] datajosh:
I get this too with 1.0.1 (CFS or BFS) on CM7 RC4 (RC3 too) but reverting to 1.0.0 solves it instantly. It only happens while connected to the charger and I believe only after the phone reaches 100%. I've seen a couple of other mentions of it in the thread as well.
[EVO 4G Android Development] bbedward:
100% charger issues must have something to do with the SBC changes I made, i'll look into it. Same with the charger lag :\
[EVO 4G Android Development] Marth05:
I think this is the right place to ask this: can someone tell me how to get the ridiculous battery life everyone seems to keep going on about with this kernel? I'm on CM7 RC3 with the CFS HAVS WIMAX 1.0.0 kernel and I'm not getting anything close to the figures I've seen people claim.

I swear it seems like I used to get better battery life before going to AOSP roms, but I'm at 19% after just under 11 hours on the battery, and I'm a pretty light user. A good amount of texting but few calls and not a lot of browsing.

I just want to be able to get through the day without having to charge my phone at some point, or trying to squeeze that last bit of juice. I've tried the different governors and it seems like I actually got better life with the stock ondemand one than with the savaged zen one. Please help or point me in the right direction. Thanks.
[EVO 4G Android Development] dkdude36:
what governer? i'm getting really good life on savagezen governer.

also, check about phone, battery and all the spare parts, battery history things. if anything is abnormally high, that's ur problem.
[EVO 4G Android Development] dkdude36:
double post my bad.
[EVO 4G Android Development] LifeInTheGrey:
Indeed, examine spare parts for Partial Wake and Sensor Usage, as well as Settings=>Applications=>Battery Use to see if anything is eating away at it. And of course, heed my mantra ... always fix permissions.

Report back and we'll see if we can assist further.
[EVO 4G Android Development] Marth05:
I cleared the battery history with my last flash hoping that would help. I'm looking at spare parts and nothing seems (to me) unusually high. The other usage stats have my running percentage at about 15%, phone on at less than 1%, wifi on 1%, screen on at 7.6%.

Although, in partial wake and sensor I do have TIKL using up 20 min, android system using an hour and a half and dialer using 42 min. Is that a lot?

In the Cyanogenmod settings there are performance options to change the governors. The stock setting is "ondemand." I used that most of the day then switched to savage toward the end of the night and savage SEEMED to be even worse.

Thanks for the quick responses and attempt at help. You guys are the best.
[EVO 4G Android Development] dkdude36:
yea the sensor usage is probably what is doing it. i dont know anything to do except maybe force closing them. for the governer, try savagezen. it is based of smartass, so it needs to 'learn'. after it is given time, it is very good.
[EVO 4G Android Development] s2kdriver:
Other things that you may want to verify/do that helped me:

Prevent logging into Latitude and Talk on reboot. Hugh battery hogs.

Use Wifi as much as possible for data. Requires less power to talk to a close by access point than a far away 3g/4g cell tower.

Use 4g only when necessary. It does take more batt than 3G.

Hope this help.
[EVO 4G Android Development] wrich73:
*edit*

sensor use back at 100...sigh
[EVO 4G Android Development] Dozenboy0012:
These are great kernals jus I had to return to 1.0.0 from 1.0.1 it jus wasnt running as smoothly as the prior no complaining jus sayin but they really stay on top of things around here
[EVO 4G Android Development] thegregbradley:
I do a lot of "management," i.e. turning off wifi the second I leave my house, checking battery stats to make sure some rogue app isn't going haywire. Other than that I use either the interactive or SavagedZen governors, minimum mhz set at 245, max 998. I was having crappy battery life upon switching to CM7 until I did a battery stats wipe, the proper way. I can't remember my exact method, but it was something like this:

1. charge phone fully to 100%

2. unplug, let drain like 5 percent, charge again to 100% (just to make sure you truly have 100% battery)

3. Reboot to recovery, wipe battery stats

4. Run phone down to 0%, i.e. let the phone die from lack of power on it's own

5. When phone is dead, plug in for like 10 mins, then reboot

6. Let charge to 100% with the phone on

Hopefully that fixes any battery issues. Odds are you ARE getting great battery life, but your battery stats are lying to you so you think you're out of battery.
[EVO 4G Android Development] italy7:
Any of you go from .2.1 to 1.0, can you describe differences please? I'm on .2.1 cfs havs sbc n it works great for me n don't want to mess up a good thing
[EVO 4G Android Development] JBabey:
then dont... lol, its not like you cant flash back if your unhappy ><
[EVO 4G Android Development] LifeInTheGrey:
Haha okay I had to post this ...

I looked at my phone just to see how battery life was doing, and if sensor usage had gone down (it has, marginally, but still). Little did I know, my phone had been at 100% for the whole day! Google Services had a massive Partial Wake, which appears to be fixed, after fixing permissions and rebooting, but ... check out the pics. It was running the whole day, and after over 9 hours of being used like this, it was only at 66%.

This kernel is friggin sick.
[EVO 4G Android Development] twiz0r:
Do you use google voice?

swyped from my cyanogenized and gingerbreaded EVO
[EVO 4G Android Development] LifeInTheGrey:
Yup, have for a long time. Never posed this problem before.

I have spoken.
[EVO 4G Android Development] twiz0r:
Thats most likely what's causing it. I had it happen to me after I received 2 voicemails this morning. Caused 9hr wakelock

swyped from my cyanogenized and gingerbreaded EVO
[EVO 4G Android Development] thegregbradley:
I have that problem here and there. I did a fix permissions and it seemed to clear things up... sorta... sometimes.... haha. Also using the interactive governor definitely fixed it, but the SZ governor gives better battery. I figured it was the kernel dropping voltage/mhz and having a hard time getting going again. I bet if you put your minimum mhz setting to 384, it'd help too.

EDIT: Also, I'm noticing a definite bug in the SZ governor. When you go to unlock the screen, you get a blip of the previous screen you used before unlocking, then the lockscreen. It just makes things feel choppy and unfinished. Doesn't happen with any other governor that I've used (performance, interactive, ondemand, and conservative). I'm gonna go back to interactive till a new version of SZ comes out and see if it's fixed. Just letting y'all know, been loving everything else about the kernel :)
[EVO 4G Android Development] smw6180:
Any idea of when a fix for this is coming? I had to switch kernels because the phone is unusable on the charger at 100% charge.
[EVO 4G Android Development] Sp0gg:
Words cannot express my amazement at the speed and battery life of this kernel combined with cm7. I just watched a 2 minute YouTube video with 0 drain. I've been using your kernel since the first version and I've seen its ups and downs, and I can say that this is the best performance i've seen. Thank you for what you've done.

Statswise I could probably go 3 days without charging with very light use. Heavy use gets me around 12 hours and normal/moderate gets me 1.5 to 2 days.

I have literally restarted my phone several times because I thought the battery gauge was stuck. (It wasn't.)
[EVO 4G Android Development] vanessaem:
Is anyone overclocking and underclocking with this kernel? If so, what are your settings? Do I need to do any of that?
[EVO 4G Android Development] xhazyx:
i usually OC to 1.13, or 1.07 - Interactive gov.

but overclocking will most likely drain your battery faster, so just try it out with the normal settings, 998max 245min, interactive, smartass, or sz governors.
[EVO 4G Android Development] Brian Rubin:
Good question. Only time I'm underclocking is with the screen off, but I'm wondering if I need to do that.
[EVO 4G Android Development] snxxxxx:
What the perfect kernel for cm 6.1.2? I use 0.2.1 bfs and cfs still drain my battery and my data being slow.

no need to try cm7 until gps and touch to focus works.. ;-)
[EVO 4G Android Development] bbedward:
You can revert to 1.0.0, that version does not have the issue
[EVO 4G Android Development] smw6180:
Gotcha. Will do. Thanks!
[EVO 4G Android Development] luisdelv:
cifs is not working on 1.0.0 or 1.0.1 kernels, had to revert back to 0.2.1 hopefully they fix that quick.
[EVO 4G Android Development] vanessaem:
Currently on SetCPU, my settings are 998max~245min Interactive with no profiles. These settings seem to be working well for me batterywise. However, the only problem I'm having now is that the screen takes quite a bit more time to come on after wake than normal. What should I do to alleviate this problem? Thanks!
[EVO 4G Android Development] stricklerjosh:
Bump up your min
[EVO 4G Android Development] -viperboy-:
Or you can just set a profile for screen off with ondemand. Might work a little better.
[EVO 4G Android Development] dirkyd3rk:
Make sure you're using the froyo kernel and not the GB one. Also you can try adjusting the frequencies and changing the governors. Maybe ondemand or conservative.
[EVO 4G Android Development] nrap:
i flashed cfs 1.0.1 earlier today.

and i can't download apps from the market. it seems like it cannot connect or something.

and the battery died in about 2 hours.

what am i doing wrong?
[EVO 4G Android Development] stricklerjosh:
Well cfs 1.01 is working great for me with decks rc7. Thanks!
[EVO 4G Android Development] nrap:
im on CM7 RC4

i can't figure it out.

if i flash something like CM6 will it replace the savage-zen kernel?
[EVO 4G Android Development] twiz0r:
Just reflash cm7...it will replace the kernel

swyped from my cyanogenized and gingerbreaded EVO
[EVO 4G Android Development] dkdude36:
does the wimax scan fix that was implemented in the newest nightly work for this kernel? if its a change in the kernel, then probably not. if it's a chagne in the rom, then maybe. i'm testing it now to see.

edit: can confirm fix doesnt work for this kernel. still need to run the kill dhcpcd command and then toggle 4g. i haven't tested stock kernel yet either so maybe it just plain old doesnt work. flashing back to stock to test...
[EVO 4G Android Development] mwielgosz:
It is a change in the ROM code, not kernel code. Specifically, the code for libhardware_legacy

http://review.cyanogenmod.com/#change,4370
[EVO 4G Android Development] dkdude36:
ok. thanks for the reply. that's pretty wired though, because when i disconnected 4g (by putting it under as many metal things as possible, wow 4g seems to work even better than sense!) then held it up again, and even hit scan a bunch of times, it didnt connect until i killed dhcp and toggled 4g. now i'm confused. testing again.

edit: yea man same problem. and it connects right away after killing dhcp and toggling.
[EVO 4G Android Development] drdrewdown:
whats it do on the cm7 kernel? same thing?
[EVO 4G Android Development] rockenrooster:
Is there a way to change the shutdown voltage of a kernel. I know li-ion batteries can be discharged to 3.0v without damage. My evo dies around 3.6v although the battery can go down all the way to 3.0v. If we could change the shutdown voltage to something like 3.2v I think we could gain a considerable amount of battery life. any help would be appreciated.
[EVO 4G Android Development] aimbdd:
I posted a thread about this a while back. It would be nice... the only "danger" really is a bricked battery. So I would see no harm in trying it. The nexus crew have it for their phones.
[EVO 4G Android Development] xhazyx:
+1 on the lowering of the phone's shutdown voltage... any extra juice we can get is very much appreciated
[EVO 4G Android Development] xjackofall:
Anyone else having Google Services wakelock on 1.0.1? It's killing my battery.

TeamWin's innovation replaced my laptop with this EVO
[EVO 4G Android Development] drdrewdown:
& what would this have to do with the kernel? check your settings...
[EVO 4G Android Development] algirnavi451:
Yeah I have the same issue. I dont know if its kernel related. Tried to go through all my settings possible, no dice.
[EVO 4G Android Development] xjackofall:
Doesn't really seem kernel-related, does it? But switching back to 1.0.0 solves the problem.

TeamWin's innovation replaced my laptop with this EVO
[EVO 4G Android Development] LifeInTheGrey:
I experienced this problem as well. I fixed permissions and wiped dalvik and cache, have not experienced the problem since.

I have spoken.
[EVO 4G Android Development] thegregbradley:
I did the same, no dice. Only thing that has fixed it is a downgrade to 0.2.1, my phone is running great again.
[EVO 4G Android Development] aimbdd:
i had the same problem as well. I restarted and it went away though. Hasn't happened on sz rom though.
[EVO 4G Android Development] empiire:
Which kernel version has the least issues/is the most advisable to flash? 1.0.1, 1.0.0, 0.1.2...? Any ideas?
[EVO 4G Android Development] J4mm1nJ03:
1.0.0 is pretty solid. 1.0.1 has a few issues while charging for some people as well as some above-average reported wakelocks, so I'd advise against that one.
[EVO 4G Android Development] bbedward:
1.0.1 has charging issues with SBC -> not with charging itself, but people said it lagged when plugged in which i havent experienced but others have. Charging and SBC work as expected regardless.

Wake lock issues -> i have no idea where these came from, barely any changes happened that could possibly cause this from 1.0 to 1.0.1

The changelog from 1.0 to 1.0.1 if i didnt post it already:

- Re-done SBC

- Incredible board files added to src tree

- 2.6.38.2

- 925 havs starting voltage

- As low as 800mV possible when using havs sysfs

- Updated BFQ
[EVO 4G Android Development] J4mm1nJ03:
I had some of the lag issues while charging that people had mentioned in the past while on 1.0.1, which isn't present for me on 1.0.0.

As far as the wakelock goes, I know that the kernel usually doesn't play a big part in it but I've seen several people mention it, so I figured it was worth noting. Personally I've had some issues recently with wakelock and my battery draining a bit faster than I'd expect it to, so I'm hoping that CM7 final releases soon so I'll have an excuse to do a full wipe and start fresh.
[EVO 4G Android Development] JBabey:
I can +1 the full charge/on charger = not useable

Oh well, im sure it will be fixed shortly so no complaints, i rarely use the phone while its on a charger anyways.
[EVO 4G Android Development] cLOUDFAn:
have been having 100% awake problem (some google service) since RC4 (to n35) with 1.0.0 or 1.0.1

the nightly build right b4 rc4 dropped was fine with 1.0.0

stock kernel has no problem

weird
[EVO 4G Android Development] grungbuk:
I use my phone constantly when charging and have not experienced this.........*shrug*

Device- EVO

ROM- CM7 latest nightlies

KERNEL- Savagedzen latest

THEME- Sculpted 2.0
[EVO 4G Android Development] brokentoaster24:
I've been using tiamat for a while, tried sz again on a whim. I'm getting pretty amazing battery life. near non stop use/texting/music/wifi for 4 hours and I still have 75% :D
[EVO 4G Android Development] NewZJ:
/sniffs

do I smell a kernel update cooking?
[EVO 4G Android Development] sag7392:
I dropped back to 0.2.1, due to governor issues (SZ & SA not hitting max setting only around 768) in 1.0.1. But with that said, 0.2.1 gives me some awesome battery life and is smooth as butter...oc'd at 1075. I believe the dev's are working on fixing the issues...and when they do, I'll jump on it!
[EVO 4G Android Development] thegregbradley:
Do what myself and a few others have done and drop back to 0.2.1, it's basically bug free. I had the 100% awake thing with 1.0.1 as well. Was ASSURED by some know-it-all that it wasn't kernel related. It was. No changes to anything other than the kernel and my 100% awake is eliminated, battery life is back to dope. I love me some 0.2.1, baby! No random reboots, dope battery life, no weirdness.
[EVO 4G Android Development] Redneck Trash:
No issues here with 1.0.1 BFS.
[EVO 4G Android Development] MikeOD:
0.2.1 isn't bug free if you stream bluetooth audio...the newer builds are perfect for that though...and I do a lot of that in the car.
[EVO 4G Android Development] thegregbradley:
Ah... never use bluetooth myself. I'll upgrade when cm7 final comes out so i can do a full wipe and see what's up with that freakin' wakelock.
[EVO 4G Android Development] larry12345:
How come the cfs kernel won't overclock to 1228 on the new hardware like the sense roms do? Thx
[EVO 4G Android Development] empiire:
I'm trying 1.0.0, hopefully good battery life, if not I'll give 0.2.1 a go. :)

Edit: no crapped out batteries/exploding batteries on this, right? I would read all 268 pages but... it's 268 pages, so if anyone knows, any info at all would be appreciated. :)
[EVO 4G Android Development] aimbdd:
Nope.. not here, so far.
[EVO 4G Android Development] sag7392:
You know that YMMV may vary, because I use BT in my car all the time without issues on the 0.2.1 kernel.
[EVO 4G Android Development] drdrewdown:
i find it amazing how much misinformation is spread around by people who shouldn't be posting in the dev section..

#maybeitsjustme

cheers
[EVO 4G Android Development] luisrcastillo:
We limit overclocking to 1.19 because anything beyond that is unstable for most evos
[EVO 4G Android Development] JBabey:
Last night I decided to go ahead and throw 1.01 on my phone. I had terrible, terrible "Hotspot" issues with cyanogen. Dropped connections, bad packets, basicly unusable even for surfing the web. Also, the GPS wouldnt shut off after i used google maps for directions.

Reverted to the stock cyanogen kernel and the hotspot was working like a champ.

I dont recall having this issue on 021, but 1 and 1.01 have given me weird hotspot issues.

Im really looking forward to 1.02, keep up the good work guys.
[EVO 4G Android Development] luisrcastillo:
Please provide a logcat if this happens again. I have not had any issues with hotspot.

In regards to the GPS icon, I've seen that happen in all GB ROMs even with the stock CM kernel. The workaround I've had is to open the maps app again and press the back button so it closes and then the GPS icon disappears