yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Finally got a good hint as to where to look/how to reproduce the problem.

I've been an idiot and always "digging deeper" into wakelocks and BBS and deep sleep percentages when the answer is more clear on the battery history details screen.

See attachment - note the tiny blip of "GPS On" when the drain starts. There's a bunch of awake time later in the evening that didn't seem to impact drain - I think when GPS turns on, some peripheral gets forced to stay on and starts draining in a manner hidden from everything else in the system.
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
I repeated the same test last night with "Battery Monitor" on through test window of roughly 8 hours and the battery drain was a little more (+2%) than that of last test ( as the this app was on), but this time I got some stats out of Battery Monitor.

Any idea What the "suspend" and "event/0" are ? I guess these are related to email/facebook/store sync!
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
Interesting......I always leave GPS off, unless I use Maps for navigation(maybe once weekly).

I've reverted back to 12/8 kernel(for comparison purposes) to see if idle wifi drain improves. For me, the difference was minimal with regard to idle(standby) wifi drain between 12/8 and 1/2 but 12/8 seemed a bit better. Over the next few days I'll be able to make a better judgment on the latter. ;)

Entropy, we all appreciate your steadfast interest in making your kernel the best it can be. Thanks!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Those are classic "other symptoms" of the infamous Android OS "bug". It indicates the phone is spending a lot of time resuming from sleep/going back to sleep. In fact, when you see high Android OS usage on a GSII, it's almost always because of the CPU usage of those two processes.

The reason 2.6.35.12 and above don't show high AOS usage is because time spent in interrupt handlers is no longer blamed on the active task at the time (which happens to be these two during suspend/resume) but accounted for "elsewhere". (Where "elsewhere" is I haven't figured out yet.)

High AOS usage is caused by:

1) Apps driving network data to the phone

2) Broadcast WLAN traffic waking the phone

3) The infamous UCKK6 wifi drain bug (BT-AMP misbehaving and firing a 1 Hz wakeup interrupt)
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
As always, I appreciate your help and admire your knowledge! Basic reason behind all my posts out tests is to give some feedback that may be useful for you and other users of this kernel, no complaints at all ;)
[AT&T Samsung Galaxy S II SGH-I777] pupochek:
FWIW, noticed another difference between DD 12/08/11 and 1/2/2012 (running ShoStock ROM). Latest Swype includes Dragon Naturally Speaking voice input. Running with 1/2/2012 kernel, it does not work, running with 12/08/11 it works. Looks like some problem with microphone interaction in the kernel, but what do I know...
[AT&T Samsung Galaxy S II SGH-I777] :
Hmm, I always turn off Wifi when I dont use it... I dont see a reason to leave it on over night if Im not going to use it. Perhaps thats why 1/2/12 has been rock solid for me, wifi dosent drain my battery because I dont give it a chance to.

I also dont use GPS. I think Ive used it three times since the beginning of October. Interesting to see all the chunks of awake time after GPS was initiated.
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
I haven't noticed this at all...running 1/2 and using dragon dictation is flawless.
[AT&T Samsung Galaxy S II SGH-I777] pupochek:
My bad. Just flashed 1/2 and dragon dictation does work provided there is some kind of data connection, wifi or cell I guess...:rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] gr8hairy1:
Took a bit of searching but found a post of mine from awhile back:

http://xdaforums.com/showthread.php?p=20078311#post20078311

While gps didn't show up on mine, I always keep gps on and wifi is always left on through the night.

I never did find out what caused mine, and I don't know if it has been repeating. I liked the beep when the phone was done being charged. It'd wake me up and I'd unplug it so it's not charging unnecessarily though the night, thus I noticed the drain and posted the pic. But when I switched over to turkbey rom the full charge notification was disabled. I just switched to the latest villain rom to check out battery life. I'll see if I'm still getting the drain though the night.

Sent from my páhhōniē
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
In a properly working system, wifi drain is so low that leaving wifi on when in range of a wifi AP should consume LESS power overall than turning it off - no 6-second svnet-dormancy wakelock or cell radio power usage for background data. Wifi is more efficient.

However, when things are NOT operating properly, wifi can trigger some nasty drain situations.

A properly working system should have negligible penalties for leaving GPS enabled, and should actually get better battery life with background data going over wifi.
[AT&T Samsung Galaxy S II SGH-I777] NJGSII:
Which is why I always enable both wifi and sync at home and turn both off when I'm not.
[AT&T Samsung Galaxy S II SGH-I777] :
On paper (or text) this makes since... but when did we ever have a properly working system to actually drain less power overall? I dont think Ive ever seen it, which is why Im used to shutting off my Wifi when not in use (thanks to my handy Beautiful Widgets Wifi Widget).
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
For me - since late October. Until this recent regression, leaving the device sitting overnight on wifi would always drain less battery than turning wifi off.

Obviously if you're on UCKK6 it's a different story.
[AT&T Samsung Galaxy S II SGH-I777] :
I was on KK6 for about a week. I reverted back to KH7.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
I see no difference. For me I always turn off wifi and Bluetooth when I'm not using them. Home wifi is always on and is set to never sleep. When I'm not using my Bluetooth I usually turn it off. I leave GPS on for location stuff. I don't see any differences that stand out between Kh7 and Kk6 as far as battery life is concerned.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
No issues at all on the KK6 Modem with ShoStock.
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
My tests did not show any difference between kh7 and kk6 on wifi.

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] hlb3:
I had no issues with KK6 other than horrible data speeds, so had to revert back to KH7.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Modem does not affect wifi at all, I was talking about firmware base. UCKK6 base has a clearly documented wifi drain bug. It's intermittent and seems less likely on unnamed, but unnamed is not immune.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Why is it less likely on unnamed?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
No clue honestly - but that just seems to be the case.

It might just be that there are more KK6 stock users in the world and they only come here when it's broken.

Had the PM regression happen this time without any GPS usage (GPS was turned off) - dammit. At least popping GPS when on wifi seems to guarantee that it happens. Going to see what happens if I revert one release back - My usage patterns were so screwy the last week of the year that I don't fully trust things. But I think it was the final I9100 update3 push that broke things.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Well I asked because Mine is KK6 also. I haven't seen to many complain about it. Just a few here and there and they have mostly been app related.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
It seems less likely on modified ROMs, no clue why... Again, either that or because there are far more stock users out there, and you see the ones that complain.

I know a few people have had it happen on Unnamed. Also, drain problems are rarely diagnosed properly.
[AT&T Samsung Galaxy S II SGH-I777] sshimomichi:
Hello entropy.

It has been a while now that I have used your DD kernel (1.2.2012) and I have encountered a bug. I do not know if this is due to the rom I'm using (UnNamed) or not, but I never had this problem running stock kernel. I will try to do this on Siyah kernel later on.

Situation: I was curious about how fast my MicroSD card is so I downloaded an app named "SD Tools". Once the performance test is done, the phone completely freezes up. None of the capacitive buttons respond. To reboot I must force the phone to go to recovery and resume booting up from there on. To be sure, I performed the same test again and the same thing happened. I figured I should logcat so provided is the logcat. I don't know if this is helpful or not but I enjoy the stability of this kernel and intend on using it for a long time. :)

pastebin(dot)com/D7SrSBqN
[AT&T Samsung Galaxy S II SGH-I777] electroau:
Try reinstalling the tool.

I use the sane tool with the sane setup (kernel and ROM) and don't have a problem
[AT&T Samsung Galaxy S II SGH-I777] electroau:
My class 4 card
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Logcat is useless - I need /proc/last_kmsg after a crash (which is documented in the first post of this thread...). Make sure to reset using long-power-press as a battery pull will wipe the ramconsole buffer.

Will attempt to reproduce tonight.
[AT&T Samsung Galaxy S II SGH-I777] Nizda1:
Entropy,

As I was speaking to you the other day regarding my dl throughput issues after reverting back to Uckh7. I found the cause I think which is for some reason my tcp buffer size's have somehow reverted back to stock allocations. This is on unnnamed 1.3.3 with your 12/8 dd. Another thing odd is after further inspection I've noticed a persistent reoccurring timestamp in all /sys/kernel dated 01.12.69 heh. Anyway im at work right now so when I get home ill re download all your dd,s again to test for a bad flash and let you know from there. I only noticed the tcp max buffer size reverting back and timestamp issues on 12/8 however the throughput issue was a problem on every dd I tried but I had not checked into the other issues. Ill write up something like jivys kernel cleaner just to make sure nothing is overlapping/overwritten.

Thx and I'll follow up when I get back home.

All else aside my battery life is phenomenal compared to what I thought was good on Uckk6

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
TCP buffer sizes can be overridden by setprop or build.prop - maybe a tweak script mangled them.

This is why I don't run major all-encompassing tweak scripts (I make a point of having each and every script I post in my init.d scripts thread independent and documented as to exactly what it does), and also why I removed anything from my initramfs that would make permanent changes.
[AT&T Samsung Galaxy S II SGH-I777] jaysix79:
is there a way to check what kernel my ROM currently have?...

I flashed the 0102 kernel but the kernel version on my phone still the same
[AT&T Samsung Galaxy S II SGH-I777] cfaberlle:
cpuspy app
[AT&T Samsung Galaxy S II SGH-I777] naturallyfrozen:
Just reverted back to this kernel from siyah. Had issues with wifi. With Entropy? No problemo. Thank you for all your hard work.

NoSig
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Posted 1/23/2012 standard - experimental probably won't get posted until 1/24 as I want to run it for a bit longer before posting.

This consists mostly of upstream bugfixes, and a feature to help those encountering deleted_wake_locks problems diagnose the issue. See post #4 for details (especially if you are shoman94 - this feature is for you per our IRC chat tonight!)

The minor power management regression I've been chasing for weeks is still there - go figure, just when I thought I could reproduce it at will, I can't reproduce it. See "known issues" for details. This one seems pretty rare, I hate going forward with it there but I've held things back a bit too long.

I'm going to look into the reports of touchkey lights staying off now - there's a slight chance the missing I9100 updates (one to the I2C bus driver) might have fixed this but it's not likely. I'm finally going to take a look at the posted dmesgs this week. Can those who had this issue confirm - it ONLY persisted until turning the screen off and back on?
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Thanks for the update!!! :)

But grrr, I have been on 1/2/12 and today I was like hmm let me try Siyah since its been a while you did an update, and poof you go and surprise me. >.<
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Hi Entropy...Glad you finally got the time to look into the touch key lights....I am still having the issue... and yes it ONLY happens until toggling the screen off and back on...then it disappears.
[AT&T Samsung Galaxy S II SGH-I777] tboooe:
I too am having the touchkey light issue. Hopefully this can be resolved soon.
[AT&T Samsung Galaxy S II SGH-I777] AntwanL:
Just flashed with jivys kernel cleansing scrip and works great so far with UnNamed 1.3.2
[AT&T Samsung Galaxy S II SGH-I777] kytrauma:
Any chance of getting voodoo louder support any time soon? I really miss the stability of your dd over siyah..

Sent from my unf#cked att sgs2
[AT&T Samsung Galaxy S II SGH-I777] kennonk:
Can someone confirm if tun support was built in or not on the 1/23 please?
[AT&T Samsung Galaxy S II SGH-I777] evostevo1:
Its supported now. Not by choice. Lol (voodoo louder)
[AT&T Samsung Galaxy S II SGH-I777] AntwanL:
My capacitive button light seems to stay on when watching Netflix, I don't think I've noticed it on others. Anyone else having that?

It's only when the video is playing. If I pause the video they shut off as they should.
[AT&T Samsung Galaxy S II SGH-I777] nyamoV2:
While I don't have Netflix. When I watch a movie in stock or mx player my lights shut off
[AT&T Samsung Galaxy S II SGH-I777] dandrumheller:
I think I remember someone else posting about this some time ago, and it was reported as normal netflix behavior. Can't find the post ATM.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Thanks I'll get it installed tonight on the wife's phone.
[AT&T Samsung Galaxy S II SGH-I777] AntwanL:
It doesn't really bother me much, I've read the capacitive buttons don't really take up a significant amount of power anyway. I'm just curious. A normal video doesn't do that so I didn't know if it's just Netflix and if anyone else noticed it.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
GAH. CRAP. I keep forgetting! Sorry!

1/23 Experimental won't get posted - I'll do a rerelease tonight with tun.ko compiled for both releases.

Normal Netflix behavior unfortunately, not specific to GS2 either - happens on my Galaxy Player. Freaking annoying as hell.
[AT&T Samsung Galaxy S II SGH-I777] Gutterball:
LOL **** off :D

By the way anyone having problems with this kernel when you first flash try running jivys kernel cleaning script before hand because I cleared the caches then flashed this kernel and received a battery overheat warning. I then ran the kernel cleaning script and then reflashed entropys new kernel and everything is fine now. Battery life seems amazing so far!
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Thanks Entropy for new release!

Request:

Guys, those who report "touch key" issues, can you please give "Step by Step" instructions to reproduce the issue including your setting for "Touch key light duration", Apps, Firmware version, that cause touch key to stay on,etc. I have vanilla/plain UnNamed v2.2.1 ( Vanilla/Plan - Just UnNamed, no other third party tweaks or scripts, no VC/OC/UC, etc..etc) and never experienced touch key issues either on DD 12/08/11 or 01/02/12.Your input will help others to reproduce the issue and report it here,thanks!
[AT&T Samsung Galaxy S II SGH-I777] tboooe:
Good idea. Unfortunately, I cant replicate the issue. It seems to happen randomly but here is my relevant phone setup:

Unnamed 2.2.1

Entropy 1/2/12

No OC/UV

No scripts, tweaks, etc

I never had this problem before Entropy 1/2/12. I know not a lot to go by.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Thanks for the update :-D
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
While I don't have a way to reproduce the problem, I at least do have dmesgs from those who had touchkey issues. I'll be reviewing them tonight or tomorrow night.
[AT&T Samsung Galaxy S II SGH-I777] chocodough:
Anything special we need to do to install the new Kernel like wiping cache or the Dalvik cache before applying with Mobile Odin?

Or is just flash and go?
[AT&T Samsung Galaxy S II SGH-I777] evostevo1:
Why don't you use cwm if your already running custom kernel? Yes wipe cache and dalvik. Please read the op before you jump ahead of yourself.
[AT&T Samsung Galaxy S II SGH-I777] chocodough:
I'm still a noob at this, so it's a work in progress for me.

When I rooted the other day, I used Mobile Odin to install the first custom kernel, I guess I just assumed to use it again to install a newer kernel.

I just wasn't sure you should wipe the two cache's before installing a different kernel. But should I wipe them before or after flashing the new Kernel?

There's is so much reading to do on all this stuff, and just when you though you read enough to kinda know what you're doing there ends up being even more to read. :)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
There should almost never bee a need to wipe cache/dalvik when installing a new kernel. Don't bother unless the kernel developer specifically states that a change requires it. (Usually, this would be an initramfs change - but in the entire history of this kernel, I have NEVER done anything that would merit wiping cache/dalvik, except for possibly the root autoinjection scripts I no longer have.)

Sometimes when changing kernels you need to clean out /system/etc/init.d - I no longer place ANYTHING in here automatically, so if you need to remove anything from there, it's not something I placed in there.

Edit: Oh yeah, I did include a .tar release for 1/23 - I will not normally include .tar releases when I update, but from now on I'll make sure there's always at least one known-working-CWM one so people can do an initial install.
[AT&T Samsung Galaxy S II SGH-I777] VFO:
First off, excellent work. This kernel was just what I was looking for. I have been on the GS2 since Sunday but was starting to miss the Roms and kernels I was running on my cappy. Since flashing this beast named Doom2 I really see what's this phone is capable of.

I am however experiencing the same issue with SU as others have reported. Not a big deal although maybe something can be done about it.

On a.other note, what is everyone using.g to OC/UV? I been using setCPU but wonder what other Apps there are. I have always used voltage control and Tegrak but those don't seem to work.
[AT&T Samsung Galaxy S II SGH-I777] dayv:
Voltage control does work
[AT&T Samsung Galaxy S II SGH-I777] wonner:
The VC I had backed up with TiBu didn't work (v.4.0 maybe?) but the VC from the market worked fine.
[AT&T Samsung Galaxy S II SGH-I777] dayv:
Yea, it needs the /system/etc/init.d folder to work, so if you restored it you need to create that folder, if you install it from the market it will create it itself.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
OK, I'll take a look at these in a bit. I think I know what's wrong - the root injection script checks the date of the su binary to see if it's older. However the problem may be that the data of the su binary in the initramfs is the build date of the kernel - which is newer than the updated su binary.

So the autoroot script overwrites the updated binary.

BTW, on my device, when I try to update the binary, it just says "checking for updates" and then does nothing. So I haven't experienced this problem because it just won't update to begin with. (Edit: Market link was broken on my device. I updated the app, then the binary, and I have a temp fix committed to git that'll work until the binary changes again.)

I'll look into a more robust autoroot script. In the meantime:

Short-term user fix - try running the following command in an ADB shell after you update the su binary but before rebooting:

adb remount
adb shell touch /system/xbin/su

If using Android Terminal Emulator on the phone, you'll need to remount /system read/write some other way.

Mid-term initramfs fix:

I'll include updated su binaries. This shouldn't take me long, however I'm reluctant to do a kernel release tonight - I've patched a lot of stuff and don't feel it has enough testing to be ready for release yet.

Longer-term initramfs fix:

Fancier root injection script

Even the doom kernel should've been stable if you did not use SetCPU or Voltage Control to change voltages

General update: Since I was home sick from work, I was able to get a LOT more done this past week than I normally would have in a week. However, for the past few days I've been feeling like crap and have barely left my apartment in days. Now that I'm mostly feeling better I'm probably going to be out of the apartment quite a bit for a few days. I need a break! :)

I've pulled in a bunch of miscellaneous bugfixes from codworkx, and I also have an experiment running - using arighi's commit set to bring the Linux base kernel revision up to 2.6.35.14. As a result my next release will likely have two or three builds - .7 with OC, .14 with OC, and .7 without OC. (.7 no-OC should be the most stable. However .14 OC has been solid for me, although as I've stated before, I never enabled the OC frequencies on my own device.)

In addition, arighi seems to be doing some pretty impressive power management work. I'm probably going to start pulling in his tweaks as a separate branch soon.
[AT&T Samsung Galaxy S II SGH-I777] VFO:
Thanks for the heads up. I just went and updated it in the market and it works now.
[AT&T Samsung Galaxy S II SGH-I777] LamboDroid19:
Thanks that worked.

Edit: Nevermind still says su binary is outdated. :(
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
As to fps uncap - http://xdaforums.com/showpost.php?p=18267464&postcount=125

On this issue, I'm going to go with DG's judgement. FPS uncapping is usually only good for benchmark epeen anyway.

As to GPU clock/voltage tweaks... I'm not sure... It should be easy to pull in netarchy's patches, but on past devices, GPU OC/voltage control was MUCH more likely to cause hardware damage. So I'm nervous about this. I'm going to wait and see if people actually read the big red text regarding CPU overclocking for a while.

(Seriously - over in the Infuse community, people wouldn't completely read the first posts of ROM/kernel threads, even stuff that was big red text.)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Damn. OK I think I'm going to post some updates then...

Warning - one is untested (but should be OK), the other is highly experimental.

OK, I've posted 10/09 and 10/09 Experimental. I haven't actually booted 10/09 but it should be OK. 10/09 Experimental has a highly experimental feature (Updating the kernel base to 2.6.35.14) - it's been running on my device for a few hours but I haven't really pushed it.

designgears, let me know if you want a no-OC build and I'll work on it tomorrow evening.
[AT&T Samsung Galaxy S II SGH-I777] jsmith8858:
Well, even though there's still an issue to work out, I think this is definitely great news, sounds like a stable BLN is a definite possibility! Thank you for all the hard work you are putting into all of this.
[AT&T Samsung Galaxy S II SGH-I777] LamboDroid19:
OK thanks that really fixed it that time. I went with the experimental release. Will let you know if I come across any other problems. Thanks again. :)
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
+1 Same here. Continuous updating of su binary script fixed :) Also running 10/9 Experimental. I'll let you know how it plays.
[AT&T Samsung Galaxy S II SGH-I777] VFO:
Worked for me as well. Thanks for the update!
[AT&T Samsung Galaxy S II SGH-I777] sentinel79:
I was sick too ... tis the season :)

Glad you're on the mend