yashsingh1/xdaforums huggingface dataset:
[EVO 4G Android Development] neilkarunatilaka:
here are my settings that i used to fix that issue when the power button won't bring up the lockscreen after sleep and you either have to double press or hold it down.. now it works fine :) On CM Nightly # 57, SZ 2.0.2 CFS. I had the issue originally, but just made these changes and its gone. Multiple reboots, battery pulls tested, and the problem hasn't come back. Hopefully this helps someone. Idk lol. :)

Cyanogenmod Settings:

Display -> Automatic Backlight.

-Enabled

-Allow Light Decrease

-Decrease Hysteresis 50%

-Everything else in this menu is default.

Interface -> Render effect

-No render effect

Performance

-Use JIT

-Enable surface dithering

-Allow purging of assets

-VM 32

Performance -> CPU Settings

SMARTASS 245/768 (Prob will work with SavagedZen)

Set on Boot.

Spareparts:

Window Animations - Normal

Transitions Speed - Fast

Compatibilty mode

Rest default settings.
[EVO 4G Android Development] EVO-lution of Man:
This is great. Running this for over a day with viperboys undervolt script and decent usage. Right on par with 1.6 and miui from the froyo days.
[EVO 4G Android Development] bbedward:
I'm waiting for someone to report the results of the test kernel on the last page to see if screen wake delay is fixed :D then i can release 2.0.3

Also some nice new governor tweaks, I made interactive scale a bit harder for performance, lowered the min sampling rate on conservative, and adjusted most values in the SZ gov which will also fix the 768Mhz issue (the test build doesnt have these tweaks, but it has the fixes for screen wake)
[EVO 4G Android Development] gpz1100:
Bbedward, I'm still doing some final testing with tiamat. Should be done in a few days, will test your kernel then.

Please advise, which governor parameters does your sz governor support, and is there a list of other supported governors?

edit reference

Edit2: N/m, will try it for the weekend. I'm not too thrilled with smartass scaling in the tiamatt 3.3.7 kernel. Even with a super high threshold setting of 99%, the cpu is still spending too much time at the top frequency.
[EVO 4G Android Development] gpz1100:
Something not right with that test kernel. It wiped out my launcher and reverted everything to default. In fact, all my apps are missing that are on the ext3.
[EVO 4G Android Development] drdrewdown:
sz 2.02 killed my ext3 partition as well. just got my new card, never done ext3 on the old one, so i cant compare previous versions
[EVO 4G Android Development] gpz1100:
Did you install the 2.02 or the test kernel attached on the previous page (see one of my posts above for a direct link). I haven't touched 2.02, only the test kernel.

@Bbedward, I can't test your test kernel as it removes access from the ext3 and all my apps are on there. However, during testing, the screen turned on each and every time from a sleep state.
[EVO 4G Android Development] zuzonline:
Glad Im not the only one with this issue. Im really tempted to keep trying but I have flashed my phone so much the past couple of weeks that I decided to just sit back and enjoy cm7.0.2.1 with SZ 1.1.0 SBC

The issues I get with what I have right now are minimal.
[EVO 4G Android Development] drdrewdown:
my comment was regarding v2.0.2, i just moved everything back to internal so i could use the kernel. i'm cool with built in a2sd in cm7, but it would be nice to use my ext3...

i wont revert back to any older version, i'm quite anal when it comes to staying up to date with commits by the cyanogenmod team.
[EVO 4G Android Development] gpz1100:
I suppose I could of moved the apps back to internal, but ultimately, I need that functionality. Strangely enough, i've been running cm7latest stock kernel, and the screen has been turning on each and every time. Other than updating several apps, no major changes have been made. The apps include things like qrdroid, quickpic, and a few others that really shouldn't have any association with this issue. We'll see how this trend continues in the next few days.

PS. Your motored cycle performs much better when both wheels are on the ground ;)
[EVO 4G Android Development] bbedward:
I can fix the ext3 no problem, I was just worried about the screen wake issue
[EVO 4G Android Development] THunDA:
My wake delay wake wasnt all that bad but was definitely there. Just flashed this and it seems to wake up fine now...

Using CM7 7021..
[EVO 4G Android Development] drdrewdown:
appreciate the effort

the wake delay is def a lot less in this test build. it turns on pretty quick now. even at 128mhz minimum.
[EVO 4G Android Development] mrufino1:
I just flashed deck 1.0 last night along with sz 2.02 and I also list the apps I moved to SD. Back on tiamat for right now but is that indicative of the described ext3 problem? I like the sz kernel a lot so hopefully its an easy fix. The other stuff was solid.
[EVO 4G Android Development] 12MaNy:
I jump back and forth between CM7 & MIUI.
[EVO 4G Android Development] bbedward:
Once i finish this programming project today I'll be able to get it fixed and get 2.0.3 out
[EVO 4G Android Development] 12MaNy:
Nice! I'll donate when I get a chance to add some $ to my paypal account. :)

Any chance you guys will start releasing non-SBC versions again? I know alot of people don't care for SBC.
[EVO 4G Android Development] JBabey:
You cant be serious? You are serious arent you....

TRY LOOKING AT POST 1

-uh..... explitive
[EVO 4G Android Development] 12MaNy:
Latest non-SBC version is 1.01 and the SBC-off .zip doesnt work for me (SBC turns back on). You should TRY LOOKING AT POST 1 there big guy....and YES I am serious. Thanks for your input though hero stud boy. :)
[EVO 4G Android Development] drdrewdown:
its best not to respond to that guy. he knows everything & is gods gift to trolling
[EVO 4G Android Development] 12MaNy:
Who, me? Or, him?
[EVO 4G Android Development] empiire:
Him, I think. He seems like a prick.
[EVO 4G Android Development] 12MaNy:
Yeah...his comment was a little negative/useless/un-called for.

Anyway, can't wait to get some 2.0.2 on my Evo. SD write speeds are killing me right now.
[EVO 4G Android Development] algirnavi451:
he had a point...if you read the first post you would have seen that you can enable/disable SBC with a script posted...therefore all kernels are SBC or nonSBC...
[EVO 4G Android Development] 12MaNy:
...and like I said before...SBC always turns back on on my device. I explained this fully a while back. ;)

http://xdaforums.com/showpost.php?p=13250488&postcount=3180
[EVO 4G Android Development] dkdude36:
he's saying that zip doesnt work for him. i can confirm the init.d file stays after reboot, but i'm not sure it's working. edit: what he said ^^^^^

can't wait for 2.0.3.

got 1 freeze up today, while playing pool. probably me undervolting -60 that did it. i'd go further but screen takes a while to turn on any lower. hopefully 2.0.3 with it's screen fix will allow me to go lower.
[EVO 4G Android Development] -viperboy-:
What is the voltage floor of this kernel? I want to make sure all my UV mods are working perfectly for this kernel. Thanks!
[EVO 4G Android Development] VisedMonk:
Hey viper,

I was wondering if it is possible to do a script that undervolts the higher cpu frequencies more than the lower ones, like -75 or -100 for 574 and above and -50 for the lower frequencies? My phone can't handle the lower voltages as your scripts are written right now, but I wondered if it might be more stable with a hybrid more/less uV script...

Imported from Detroit using XDA premium app
[EVO 4G Android Development] -viperboy-:
I will take that into consideration. I know what you're saying, I just don't want to have to make like 30 scripts haha
[EVO 4G Android Development] VisedMonk:
Oh, but why not? ;-)

Imported from Detroit using XDA premium app
[EVO 4G Android Development] oOflyeyesOo:
Is toasts new kernel code going to be implemented into the new version? And when do you think it will be released? Im itching for a new flash, hopefully CM7.1 and SZ 2.0.3 comes out in the same day, ill be a happy camper.
[EVO 4G Android Development] -viperboy-:
I mean, I could make them in stages, but they have to be in 25mv increments. If someone wants to come up with an idea to do this, that would be good.
[EVO 4G Android Development] aph:
The test kernel fixed it for the most part but not fully. The most consistently I was able to reproduce was to reboot, wait 10 min and try to turn the screen on.

Also it destroyed my battery life overnight (-60% where it's usually -2-3%) no usage

- Posted from Evo, please forgive typos.
[EVO 4G Android Development] Shinzul:
Great news everyone!

I pinpointed the issue with the .38 kernAlz and flashing using Kernel Manager! You should now be able to flash to and from a Savage-Zen kernel using KM Pro v1.2.2 :). (I haven't updated KM Lite yet, just Pro so far.) It's kind of a big change, and it'll take some time for me to merge it into the lite version.
[EVO 4G Android Development] Lento10:
So it was a KM issue and not the kernel?... Interesting
[EVO 4G Android Development] Shinzul:
Well, not really to be honest. It was an issue with koush's AnyKernel binaries that are included with the kernel zip file.

I had been extracting the mkbootimg, unpackbootimg, etc from each kernel zip and using those, but they didn't work with the new page sizes of the .38 kernels.

So it's really koush's fault :p
[EVO 4G Android Development] -viperboy-:
#blamekoush
[EVO 4G Android Development] Lento10:
Just wondering, interesting info.
[EVO 4G Android Development] evo5150:
^ LOL

GOOD JOB to all the developers for the hard work and outstanding kernel you guys produce. I only been reading this since thread 321 or something. Im currently running 2.02 CFS and the only issue I have is after my phone sleeps for awhile I would unlock the screen and my animations wont show. Then when I try calling someone or texting it becomes "unresponsive" and I will have to reboot my phone. I'm not sure if that issue has been addressed yet but this is my issue only. Other than that battery life is amazing I just want to know for some of you guys who are claiming to have 30+ hours battery life on a single charge with stock battery are doing? I get a good amount on stock but I like my phone snappy and fast are you guys sacrificing that?? btw im still on CM 7 STABLE
[EVO 4G Android Development] snandlal:
Im still getting the screen wake with the test kernel, tho not as much it seems. Good luck!
[EVO 4G Android Development] Lento10:
I am using 2.0.2 cfs and the lock screen wake issue stop a couple of days ago.
[EVO 4G Android Development] gpz1100:
Why not just edit the script yourself? Pull the respective file using adb from the /etc/init.d folder, make that changes, then push back. You can define your own custom map that way, unique to your device.
[EVO 4G Android Development] bbedward:
I don't quite get people these days...

The screen wake was mostly an oversight in a patch that increased battery life by lowering the power collapse frequency.

It caused wake issues for some, but a lot of people didnt have the issue (such as my self)

Anyway, i'll still release 2.0.3 despite all the people that dog on our work.
[EVO 4G Android Development] drdrewdown:
trolls will be trolls bro. most of us appreciate the work you are doing. looking forward to the next update
[EVO 4G Android Development] Lento10:
This kernel gives excellent battery life, and the only people who dog your work are haters. Keep up the great work!!

Looking forward to your next rev,
[EVO 4G Android Development] algirnavi451:
So does that mean that this will decrease battery life?

Also I was only getting the screen wake issues in CFS, BFS didnt cause me any problems, but CFS ran smoother....I'm getting the same issues in GoDmode kernel every once in a while as well

Thanks for all the work you guys put in. I love this kernel and will go back when 2.0.3 is released...and what is the Androidian.apk in your mirrors?
[EVO 4G Android Development] bbedward:
It will barely affect battery life. There is an outstanding bug in CM6 that continues in CM7 which is for screen wake delay when answering the phone.

Anyway, i'm building a new test build that's all updated and it should fix the ext issues too
[EVO 4G Android Development] bbedward:
http://downloads.zen-kernel.org/zendroid/SZ-2.1-test.zip

I'm about to push a new build to the mirrors, test it for screen wake and ext3 issues.

Also the governors are a bit tweaked in that guy.
[EVO 4G Android Development] -viperboy-:
Hey bbedward, voltage floor is 800mV in this kernel?
[EVO 4G Android Development] snandlal:
Ya what this guy says. Cant wait!
[EVO 4G Android Development] snandlal:
Interesting. I did not know this was done intentionally. Maybe a nice balance can be made for the people that use this kernel
[EVO 4G Android Development] aph:
Nevermind flashed back to 2.0.2 and still seeing massive battery drain, must be something else

- Posted from Evo, please forgive typos.
[EVO 4G Android Development] bbedward:
Yea that's correct ;)
[EVO 4G Android Development] halorin:
Trying out 2.1 bfs right now with CM7. Some of the most responsive a bfs kernel has ever been for me. Will update as I go.

Great work. Screw the haters. I respect anybody that takes personal time to better my ohone experience. I hate that people have this mean spirited attitude over a common goal of making our phones. Keep going.
[EVO 4G Android Development] algirnavi451:
Why cant i download the 2.1.0 Kernel...I get getting forbidden messages

Edit: Nvm all good now
[EVO 4G Android Development] bbedward:
You can now get SZ 2.1 in kernel manager too
[EVO 4G Android Development] raphenucleus:
I'm still getting the forbidden error ("You don't have permission to access /files/SavagedZen-2.1.0-CFS-HAVS-signed.zip on this server") when I click on the link for 2.1.0 CFS, but I right clicked on it and selected "Save Link As..." and it downloaded fine. Tried the old CFS links and the new BFS one and those all worked fine.
[EVO 4G Android Development] lamboh:
Just flashed 2.1 test on miui. 29 and UV 75 no problems so far and smooth like butter
[EVO 4G Android Development] algirnavi451:
I am still getting wakelock issues, actually worse than before. Now I have to longpress the power button for my screen to wake up. Gonna try BFS.

Using 2.1.0 CFS, HW 0003, SavagedZen scaling 998-245 MHz, CM 7.0.2.1
[EVO 4G Android Development] Redneck Trash:
On mirror.savaged-zen.com the file sizes for 2.1.0 are 0.00KB.
[EVO 4G Android Development] bbedward:
There's some sort of bug in the buildbot replication or something idk, it's fine though they should be about 2.3Mb
[EVO 4G Android Development] Apo11on:
I keep watching the changelog in the OP for HDMI related fixes - there has been nothing mentioned in the past few builds, so I gotta ask. Has any of the latest teamwin's HDMI code been merged into S-Z? Specifically, the tiger blood thing which is supposed to fix EDID (although judging by its effectiveness on my phone it's more like a tomato juice :cool:) and if not - any plans to merge latest HDMI fixes?
[EVO 4G Android Development] Redneck Trash:
I couldn't get it to download. I assumed that was the reason.
[EVO 4G Android Development] algirnavi451:
Right click and do save as. That worked for some people. Or kernel manager.

My problem with screen not turning on (or sleep lock as gpz1100 puts it) definably has to do with CFS. I had this problem with 2.0.2 CFS and Godmode (which runs CFS). Now that I'm running BFS I don't have any issues with my screen not waking up.

Edit: there I changed it. Happy?
[EVO 4G Android Development] gpz1100:
algirnavi451, I think you're confusing your terms. Wakelock is when the phone fails to go to sleep, staying awake when it should be asleep. The issue with the screen not turning on from sleep is probably better termed as sleep lock :), but definitely not wakelock.
[EVO 4G Android Development] bbedward:
I havent merged it, mostly because a lot of people seem to have issues with HDMI after the patches
[EVO 4G Android Development] Redneck Trash:
It's downloading now. Don't know why but screw it it's working.
[EVO 4G Android Development] xhaui:
I've flashed it and the screen wake is definitely fixed, but I notice now that rather than being slow to wake, the phone is unresponsive for a few seconds after I unlock the screen. I'll give it sometime through. Seems to be smooth as butter other than that, but if none else reports this, I'll just try to reflash the kernel.
[EVO 4G Android Development] evo5150:
Yeah thats all Im saying.. the kernel is great but I just have that tad small issue.. the devs hard work is very much appreciated.. Im just saying thats all I have. I tried wiping cache and doing everything.. I may just have to try a full wipe and it might get better.. Will report back..

*UPDATE didnt even see 2.1 is up going to flash that now* :D
[EVO 4G Android Development] raphenucleus:
The "sleep lock" issue seems to be fixed for me using 2.1.0, except when the phone is on the charger, which is weird but it doesn't really bother me. I'm also seeing the frequency hit 998 MHz again, which is nice. Everything's running really smooth so far and battery seems to be stellar as always. Thanks for all the hard work!
[EVO 4G Android Development] evo5150:
which governer are you using? BTW 2.1 BFS is smooth as butter.. my quadrant benchmarks are a lot higher now!! loving this version of the kernel!! MIN 384 max 998 GV: SZ GOVERNER gj!
[EVO 4G Android Development] snandlal:
Yes i still get this when i flashed to see if it was fixed. Also hardware 0003. Oh well. Thanks for trying
[EVO 4G Android Development] bbedward:
I'm getting tired of your trolling tendencies, the screen lock is fixed, if not use the bfs kernel. the stock cm kernel has screen lock issues once in awhile too
[EVO 4G Android Development] halorin:
I haven't had any screen lock issues so far with BFS. Using 2.1.0 and CM7. 248-998 Interactive.

I'll try SZ governor for a while to compare.
[EVO 4G Android Development] Lento10:
2.1.0 BFS working great :)
[EVO 4G Android Development] tiato:
CFS version is working great on mine, no screen lock issues. BTW, I can concur with the dev. that even CM stock kernel had that screen lock problem.

All your hard works are greatly appreciated. Please ignore the trolls for they have no better things to do.
[EVO 4G Android Development] thegregbradley:
Confirming that Tiamat, SZ, and stock CM kernels all have intermittent wakelock issues. HOWEVER... I found that SZ gave more issues, but I haven't tested 2.1 at this time. Tiamat gives me the fewest. DOUBLE HOWEVER... SZ had slightly battery life. Probably some more aggresive HAVS and down-mhz-ing going on in SZ.

Basically haters, if you don't like it, DON'T USE IT. The devs owe you NOTHING, so be nice when you have bugs and criticisms. You don't HAVE to run SZ and CM7 just because they're the most popular options, give other **** a try. Have fun flashing, and chill out.
[EVO 4G Android Development] halorin:
While I didn't have any screen lock issues with the SZ governor , I liked the performance of Interactive better. :)

edit: Whoops. Meant governor.
[EVO 4G Android Development] snandlal:
My experience has been somewhat different. The only aosp kernel that has the "screen wake with the power button" is this kernel. Yes we know about the other wake issue while answering the phone, two different issues. The issue im talking about is the one with the delay while waking the phone with the power button, which is not fixed completely. Some people are still having problems. Not to say this kernel isnt a good one. It is.
[EVO 4G Android Development] thegregbradley:
Possible your phone doesn't like undervolting? And you haven't put your CPU minimum mhz below 245, right? And finally, I never used the SZ governor, it's too aggressive for my phone. Interactive all day.
[EVO 4G Android Development] eyeamfresh:
Tried to flash three times today. All three were a no go did full wipes everytime twice with clockwork and once with amon ra. Any advice?

PS - I have flashed many Roms and this has never happened.
[EVO 4G Android Development] thegregbradley:
What do you mean by full wipe? You only need to wipe cache and dalvik cache, nothing else, if you're wiping more, you're deleting system files and your rom won't boot due to the fact that the files aren't there :D
[EVO 4G Android Development] evo5150:
So far so good with this kernel Ive been playing with my phone for the past 3 and a half hours and I have had no issues with SZ 2.1 BFS. Battery life has been great for me on heavy use, the Quadrant bench marks are a lot higher than the previous versions, its super smooth with ADW Launcher EX (which btw is an outstanding launcher). I have no issues with any screen lock issues. My animations show just fine on wake and the 4g icon issue has been gone so its good to go.

If any of you are having other issues I suggest doing a full data wipe before flashing your rom and kernel. I greatly appreciate the hard work for the SZ team in making it compatible with CM7 the best they can. I will be looking forward to future SZ kernels and mods!
[EVO 4G Android Development] eyeamfresh:
I wiped cache dalvic and system reset. I always wipe all three when flashing something with different framework.
[EVO 4G Android Development] M4ver1ck:
I agree, sz has been working thier butts off and making amazing kernels (and now an amazing rom). The only issue I'm having is on the bfs kernel ever since 2.0.2 my sd card would randomly unmount. But cfs is working great.
[EVO 4G Android Development] bbedward:
You can't do a system reset unless you flash a rom too, just making sure that isnt your issue :eek:

You could flash it with kernel manager too
[EVO 4G Android Development] dkdude36:
kernel manager pro works. lite fails.
[EVO 4G Android Development] dirkyd3rk:
The newest savagezen kernel is the best kernel they've ever released. 2.1.0 CFS is the bees knees!
[EVO 4G Android Development] androidEVOlution:
Would the level of OC I'm stable at be affected by a new kernel?

On 1.0.1 I'm fine at 1190, but ever since 2.0.0 I get a frozen phone after boot or sometimes it boots then gets major FC trouble then starts lagging then freezes.
[EVO 4G Android Development] bbedward:
It's probably because the voltages are different. You can change them in the VDD interface but I'll put it on my to-do list to increase the voltages for OC'd frequencies
[EVO 4G Android Development] mrufino1:
2.1 BFS working great so far on 0004 hardware, running deck 1.0.
[EVO 4G Android Development] dkdude36:
Hate to say it, but having horrible sleep lock On newest cfs no sbc uv to -50. Have to hold power for like 3 seconds before the screen comes on.

Sent from my PC36100
[EVO 4G Android Development] Macropoutsis:
Anyone running MikG with this kernal? If so, can you report your results? Thanks.
[EVO 4G Android Development] Redneck Trash:
If min is 128 try 245. Only other thing I can think of is trying the -25 script but try the min setting first. The Evo can be picky as hell sometimes.
[EVO 4G Android Development] androidEVOlution:
I flashed 2.1.0 and then the +50mV script and got the same issue. Dunno if that's enough of a voltage bump to matter though.
[EVO 4G Android Development] housry23:
This kernel won't work with MikG because MikG is Sense and this kernel is for AOSP.
[EVO 4G Android Development] sheeksta:
So far so good.. running 2.1.0 Cfs and its fast... super duper fast... on the interactive governor. I've tested everything I can think of and its stable, fast, and has not stuttered even once. I'm so impressed I might not update for a while :) all running on hw 003 on cm 7.0.2.1 with more than 70 apps installed.
[EVO 4G Android Development] snandlal:
This is running excellent. When i press the power button to wake the screen, the bottom soft key lights come on and then after a second or so the screen comes on. Any way to correct this delay?

Hardware 0003, deck 1.0, any governor does it. Trying to find the culprit