yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
For me, it was reporting above Cell Standby but without actual additional drain - which is impossible.

Battery usage stats reporting is clearly broken on our phones... .14 improves it a bit but doesn't completely fix it, as the Android System false report shows.

Edit: As to V6 SuperCharger, as far as I can tell it changes OOM killer kill thresholds - strangely enough claiming to do so universally, despite the fact that our device has twice as much RAM as, say, a Captivate, and even more than the device it was originally written for. A lot of these tweak scripts seem to do nothing of real value, or in some case enable dangerous options that can lead to data loss in order to obtain performance. I also tend to shy away from anything written by anyone who makes claims as extreme as that developer.
[AT&T Samsung Galaxy S II SGH-I777] nyydynasty:
i had the same thing. AOS reporting over 50% but normal battery life.
[AT&T Samsung Galaxy S II SGH-I777] SNadler:
Hello Entropy,

Using this method I had no problem installing the exp kernel and if I adb recovery it goes to blue recovery but all of the options do not work. I can select them but I just get the circle with the hat? What am I doing wrong?:confused:
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
Buttons have changed. Home button to select back button to go back.
[AT&T Samsung Galaxy S II SGH-I777] SNadler:
Duh! Face Smack!

Thank You! :)
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
Running smooth with Unnamed. Suggestion... I remember from OCing on Cappy and Infuse that 6 or fewer frequency levels was most efficient (may not be the case with dual core). If possible can the next release include the ability to disable some frequencies. I can't do it with VC so I"m assuming the kernel doesn't allow it yet. I'm thinking 1400 and either 1200 or 1000 could be disabled for more efficiency...

Thanks

Confirmation number: 4FT23308M8789142C
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I never had disabling in my Infuse Daily Driver series, and as far as I can tell it's less easy to do in Gingerbread kernels - note that bedwa's kernel doesn't properly support disabling either. Nearly all OC implementations for Exynos devices are straight ports of netarchy's OC code, which doesn't do disabling.

I do have netarchy's conservative tuning governor tweaks in here which makes the kernel step through frequencies MUCH faster in conservative.

I'm really nervous about mucking around too much in the clocking code - the only reason I even have OC in here is because it was a very well tested and mature patch that originated with netarchy and was cleaned up/merged by codeworkx.

I'm also planning on pulling in some code from arighi that locks out the lower frequencies when the screen is on and higher ones when it's off - kind of like SetCPU's screen-off profiles but with much lower latency.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
10/13/2011 maintenance releases uploaded - This only affects people who are still having issues with su and Superuser.apk getting overwritten. (Since su is currently latest, this really only affects ROM developers right now, as everyone else has updated Superuser.apk in /data)

That's the only change between 10/9 and this release - As such both 10/9 releases have been removed since these have no kernel code changes, just an initramfs script tweak in the autorooter.

No need to flash the update unless you're having issues with su or Superuser.apk getting overwritten on every boot.
[AT&T Samsung Galaxy S II SGH-I777] dirtbagg:
What should it read under kernal version in about phone...just flashed kernal

Sent from my phone
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
Which one did you flash? Experimental or Non-Experimental. If it was Exp it should read 2.6.35.14. Otherwise it should read 2.6.35.7
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Was Android OS percentage very high along with lots of wlan_rx wakelocks in the kernel wakelock list? If so - this is one of two widely documented bugs with the UCKK6 base.
[AT&T Samsung Galaxy S II SGH-I777] stalked_r/t:
I didn't have BBS on it, so I can't say. That's why I'm going to redo everything, give it a full charge, then start logging things like I did before.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Even normal battery stats would've caught abnormally high AOS percentage, which would have happened if it were one of the UCKK6 bugs. Also /proc/wakelocks can be pulled via ADB - that's how it was done for a while before BBS added that feature. :)
[AT&T Samsung Galaxy S II SGH-I777] Tenkie:
Less than 1% per hour, running entropy 2/26 kernel and sh1trom xwkl1 w/ 38 minutes display. No problems w/ power on and off. Will report if otherwise.

Thanks again for the release!
[AT&T Samsung Galaxy S II SGH-I777] stalked_r/t:
lol I'm too new to this and was more focused on getting my phone setup back to where it was. It's charging right now. Only thing i have on it is Enhanced Email, BBS, and the Amazon Appstore (to download EE). WiFi is off, GPS is off, BT is off. I'll see what happens this time as soon as it's done charging. When I put it on the charger, it was down to 65%. That's nearly a 20% drain per hour, so I'm thinking something wasn't right with my setup.
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Hi Entropy get on this... :)

I9100XXKP4

http://hotfile.com/dl/139221321/6c05...XAKP4.rar.html

pass: samfirmware.com

I9100XXKP8

http://hotfile.com/dl/139221144/1bdf...XAKP8.rar.html

pass: samfirmware.com

Got this from the checkrom site forum...should be released on the 1st but they have stable versions...think the files include the kernel...
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Um, those are ancient (Note the third letter is K designating 2011). LPH (the base for Baby Pacifier) is MUCH newer.

The ICS prereleases seem to be missing month code, using P (prelease?) instead.

And they are not relevant to this thread - this is for my Gingerbread kernel. ICS kernel work will have a new thread, and kernel work won't start until I9100 ICS becomes official and source code is released.

I doubt the March 1st release date for I9100 ICS at this point - LPH isn't ready to go in my opinion and there hasn't been any leak since then. I'm 90% certain there will be a leak before official release.
[AT&T Samsung Galaxy S II SGH-I777] shinji257:
Just to let you know I was running the 2/18 builds (the one actually dated 2/18) and had the weird shutdown issue. Upon turning on the button leds flash real quick then a normal boot. An attempt to get a /proc/last_kmsg failed as it didn't exist. Ideas?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Was this when connected to a charger?

Which 2/18 build? A or B? Were you on 15C before?

crash-to-LPM is pissing me off - it's damn near impossible to get a log. :(

I'm going to look into maybe putting something in the initramfs to dump last_kmsg in LPM.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
I want to say that 2/15c is awesome on my rom so far. 2/18b was a step backwards. I know the changes aren't great and I don't understand why the big difference but it is. Finally something better then 12/8/11.

Take it for what it is.....
[AT&T Samsung Galaxy S II SGH-I777] :
Another thumbs up for 2/15-C, awesome!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
PLEASE compare 18A to 18B!!!!!! The ability to do so is the whole point of releasing kernels with one patch per release. Also provide more details as to the circumstances where it performs more poorly power-wise.

I'm much more inclined to investigate/rework/revert the patch in 18A than 18B. The 18B patch is from Linux mainline, which means - it's gonna be in ICS whether you like it or not.

Red: Can you confirm again that 26 was the one problematic for you? I've already decided to revert that patch for now and investigate other solutions for Nizda1's issue (if he even has it again, ashmem may have been a red herring) because unlike shoman94, you narrowed it down exactly to a specific patch and you were able to see a night-and-day significant difference. (I don't think I've seen any feedback on 18A from shoman.)
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Entropy,

We can add even XWKL1 base to bug list; in idle state, XWKL1 base drains 10%/ hour on my work wifi with AOS topping >67% with lots of wlan_rx wake locks.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Bump!

Probably this post was missed. It shows that 02/26 was a problem for me.

BBS log of 02/26 overnight with Wi-Fi on.

Staying on 02/26 overnight was a disaster too. Weird.. if I turn off Wi-Fi, I get deleted wake locks and if I keep Wi-Fi on during night, I get wlan_rx wake locks (because of the bug in 2.3.6). Then what's the point of turning off Wi-Fi? Above logs are for 2/26 on SHOstock 1.9.2.

Now I am testing a different ROM on 2/15-C
[AT&T Samsung Galaxy S II SGH-I777] shinji257:
I believe it was 2/18b (confirm definitely 2/18b) since the kernel was actually dated 2/18. It was charging via PC USB rather than the standalone adapter. I had skipped 2/15c coming from build 1/30/12.
[AT&T Samsung Galaxy S II SGH-I777] :
Ya let me go back through both 2/18's and then 26. Give me some time though as I want my phone to use then for a bit to be double sure.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
You haven't seen any feedback on 18a yet because I haven't used it. I can only run one kernel at a time and I need a full day so I can test it. I was planning on flashing 18a tonight.

So again I will be flashing 18a tonight and report at the end of the day tomorrow.

Between 15c and 18b I haven't had any problems but 15c just performed a touch better and was quite a bit better on battery life.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Running the latest release and things seem super stable and battery is much improved. Thanks again.
[AT&T Samsung Galaxy S II SGH-I777] buickgnx:
Is there a way to change the recovery to the touch version? tired flashing it in the cwm that came with this kernel but it dosnt change anything. im guessing the .img file would need to b decompliled?
[AT&T Samsung Galaxy S II SGH-I777] :
Yup, both 2/18's ran fine (although not at great as 2/15-C) then jumped over to 2/26 and my phone felt like it was only operating at 400MHz and only had 128MB of RAM total installed (slow, laggy, choppy in apps, games and in the app drawer... power button took 3-5 seconds to turn on and wake up). Just flashed back to 2/15-C and my phone is running awesomely smooth again.

Whatever it is, my phone just flat out does not like the 2/26 version.
[AT&T Samsung Galaxy S II SGH-I777] Karashta:
I find it so weird that you have such big problems with it when I haven't had any symptom remotely like yours. I know to a certain extent all our phones are their own monster but still... way weird to me
[AT&T Samsung Galaxy S II SGH-I777] ryude:
I had no issues with 2/26, perhaps just a corrupted download or a bad flash.
[AT&T Samsung Galaxy S II SGH-I777] Nizda1:
Entropy,

I just got back from a cruise, I've read for the last hour still have some catching up to do, lots going on. As far as the Ashmem issue I'f its affecting other users negatively, take it out or whatever you'd like to do. I just put 2/15 on and will work my way up. Before I left I did a full wipe and put back on 1/30 with uckh7, had no issues at all while away.

Thanks for all your hardwork, I'll be sure.to document if I have any issues.

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] nyamoV2:
Im with red5 on this. No major issues with 2-20 but 2-15c runs smoother. Even with my 2d only games were noticeably laggy. Will run with 2-15c for a few days to compare
[AT&T Samsung Galaxy S II SGH-I777] AndAllThingsWillEnd:
I guess I'm one of the lucky ones, I haven't had any issues with any of entropy's kernels.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Well, to confirm it's the base - please perform the diagnostics (skip right to Shark captures) in the known battery drainers thread.

I saw BT-AMP happen once on XWKL1, but it was when I was janking around with some experimental settings in the wifi driver and never again.

I'm 90% certain I ran the arpdrain test against KL1 and it was immune. Will try again later this week.

Hmm, if charging via PC USB, and it happens again, try to ADB in and pull /proc/last_kmsg

On other topics:

I'm going to revert that ashmem patch. I have no idea why red5 is having performance issues with it, but since it's clear that things go badly when switching between 18B and 26 that there is a delta, I'm going to go with it.

For the patches in 18A and B - I need more info because too many people skipped A.

I'll be uploading shortly.

It also contains a bunch of small recovery fixes INCLUDING swapping internal/external SD to be consistent with Android standards (and with CWM labeling)

Touch recovery is not planned at this time - It is too prone to user error.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
That sucks. Maybe red pill then?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I'll look into it - I think the main improvement there was removing a bunch of the "nos" in the confirmation screen, which does make sense - there are a few too many...
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Going to give 2/28 a try for the week. :)

At first I wasn't up for change but when I started testing and flashing builds before releasing, I deeply felt so much hate for the layout of CWM. :(

I really wish for a organized recovery if at all possible.

Yea that is also a pain, I honestly felt like I was going to break my volume buttons.

I compared it to my gf's phone and mine made so much noise when I touched them. Lol
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Thanks for the update :-)
[AT&T Samsung Galaxy S II SGH-I777] Karashta:
I have some beef with red pill recovery. More than one of the nandroid back ups I made with it were corrupt. Totally not cool in my book. I had to reflash my miui and cm7 so I could have them when I wanted them again. Not sure if others had that problem on siyah but it sure pissed me off
[AT&T Samsung Galaxy S II SGH-I777] :
Again, if its just me having issues with 2/26 then dont feel like you have to add this or remove that, I'm perfectly happy with 2/15-C and will just wait for your next update to see if my phone like that one.

I do appriciate your hard work and effort though, changing things around for other users... most people wouldn't do that, so thank you.
[AT&T Samsung Galaxy S II SGH-I777] Haloruler64:
Same issue though man. SHOstock 1.9.2 for me. JUST changing the kernel to 2/26 creates unbearable lag in doing everything. Flashing 2/15-C and it's flawless. Flashing Siyah back and flawless. Only difference was the kernel. I think 3 people have reported it already.

Also yes, thanks Entropy for your hard work!
[AT&T Samsung Galaxy S II SGH-I777] jneilliii:
You're right, for whatever reason after rebooting a couple of times it sorted itself out.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Maybe I missed it, but it was mainly you and Red5.

When two people have definitive immediate night-and-day regressions, and the patch only helped one person and doesn't seem to be helping them after they have wiped, the patch goes away for now - Maybe I'll revisit it again later, but I really want to get rid of as many of the reported issues with 1/30 and 2/7 as I can. I think I got the worst of the 2/7 issues, but still some people are hitting crash-to-LPM. This is frustrating as hell because you can't dump logs in LPM. I'm going to see if there's a way to mount /sdcard and dump last_kmsg in lpm.rc
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
You forgot me :P
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Running 2/18a and idle is great so far. 5hrs and 1% drop. Which is 1% better the 2/15c.

We'll see how it goes as the day goes on. So far performance is on par.
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Okay, I will post Shark dump before noon.
[AT&T Samsung Galaxy S II SGH-I777] stalked_r/t:
An update from me running the 2/26. This morning I removed from charger, down 10% in 1 hour 53 minutes. Display on for 12 min (I made a phone call that lasted under 2 minutes).

Looking at BBS I found something interesting. When looking at the kernel wakelock stats, it says "No referrence since charging". Looking online, I didn't find anything specific that I could put my finger on to say what that means or if something is fubar'd.

When looking at Partial Wakelocks, I see

Enhanced email: 4 min

*sync*: 3 min

Google Services: 2 min

*wifi*: 2 min

I'll run a shark if you want me to.
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Shark dump attached.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I've seen that sometimes on fresh installs, BBS doesn't properly get superuser privileges - you see a message that root was denied even though you never got a prompt. This will make things janky with respect to displaying kernel wakelocks.
[AT&T Samsung Galaxy S II SGH-I777] stalked_r/t:
That appears to be it. I have Super User premium but can't for the life of me figure out how to add an app to the approved list and can't get BBS to prompt for permissions. I've uninstalled and reinstalled BBS.
[AT&T Samsung Galaxy S II SGH-I777] lbohn:
Select the Alarms stat in BBS and you will be prompted for SU permission.

--L.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I had to play around with unplugging/replugging the charger a few times. Also, it was weird - it would not ask for permissions until 20-30 seconds or so after unplugging.
[AT&T Samsung Galaxy S II SGH-I777] tedkunich:
Entropy,

Is the kernel responsible for switching audio to and from the BT stream? Have noticed that BT audio streaming always breaks after going out of range with the BT device (car HF) and then returning within range. The phone show that it is re-connected, and I can make and receive calls via the BT, but music streaming is silent until I either make/take a call, or use the dialer to play back key presses. Turning BT on/off with the toggles does not appear to clear this up, but airplane mode does.

This has occurred on multiple bases (Sh1tRom, ICScrewD 2.0.1, Binnacle), but I do not recall this happening with older kernels and ICScrewD. If this could be kernel related, I can flash some of the older ones and see where things go wonky.

T
[AT&T Samsung Galaxy S II SGH-I777] NJGSII:
Initial thoughts on 2/28

- Device seems to be snappier than from using 2/26

- Could be placebo, but battery life might be slightly better as well.

- No issues, so far.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Hmm... That's something that would be affected by a multitude of things - kernel and system. I'd think it was primarily system but there could be kernel involvement.
[AT&T Samsung Galaxy S II SGH-I777] geomax45:
Shoman, is that idle with wifi on?
[AT&T Samsung Galaxy S II SGH-I777] shinji257:
I'll try but no promises. I tried to do it last time right after boot but it wasn't there. Almost positive the phone actually shuts down. What I might do is make an adb connection and try to cat kmsg and pull logcat while charging.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Yes wifi on set to never and my normal sync stuff active.
[AT&T Samsung Galaxy S II SGH-I777] Dungeon47:
Latest DD is running very stable, and seems to get slightly better battery performance on CheckRom 6.

I'll try to get a logcat of my power off which charging problem, but it might take a while because it doesn't always happen.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Unfortunately, since logs get blown away during the shutdown/reboot, it's next to impossible to get a logcat or /proc/last_kmsg.

I've got some ideas to try... One is to have people set up a continuous logcat to the SD card so that it's already running when the shutdown happens, but for a rare problem this is annoying as hell (it will affect phone performance.)

Another is to hack up lpm.rc to dump last_kmsg when LPM is entered.
[AT&T Samsung Galaxy S II SGH-I777] Dungeon47:
If the logcat to SD is something that can be turned off with script manager or something, I could test it over the weekend.

In my experience it seems to be most likely to happen when the phone is charging from less than 50% and is left along until it hits 70%. At about 70% it shuts down and charges the rest of the way to full. I know (for me) that it's near or at 70% because I've happened to see it do it twice.

If I remember correctly, its not a crash, it actually shuts down properly with animations and everything. Like the phone suddenly thinks it's at 0% for a moment.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Hmmm... That's interesting. It's also a hint how I might be able to reproduce. I rarely get below 75-80%! Also, it's REALLY beneficial to know that it's a triggered shutdown, even though that makes it a ***** to debug in some ways.

I'll have to drain the **** out of my battery with StabilityTest after a phone call tonight, then see if it dies when I recharge overnight. I use my Tab 10.1 as my alarm so it's no big deal if the thing shuts down.

By the way - this is the most informative report on the issue I've seen in the entire time people have been reporting this.

I forget - did you say this started with 1/2 for you?
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
There are some options to dump or capture the state/logs of modem etc. by doing *#9900# can that be turned on based on some events for this purpose?

Sent from my GT-I9100
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Entropy, if you could spare some minutes for this, that would be great.

Sent from my GT-I9100
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
My findings so far between 2/15c and 2/18a .... I'm not sure if this makes sense but idle time with screen off uses less battery on 2/18a but screen on uses less battery on 2/15c.

Performance by feel and antutu feel the same.

Does the change between the 2 coincide with my thoughts?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Screen off should improve battery. Screen on shouldn't be affected.

The difference is that some hardware is controlled more aggressively when the phone enters deep sleep:

https://github.com/Entropy512/linux_kernel_sgh-i777/commit/4d8a7e7834e29cee232d6634454c0c38e9903d49

It (in theory, I should probably instrument the code and test it...) powers down some of the internal storage when the phone enters deep sleep.

When the screen is on, it has zero effect.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Ive been trying to use the phone the exact way I did with 2/15c. What I did forget was 30 minutes of Pandora with the screen on and it has now put me back even with screen on. I will be taking this to 1 percent so I will do final tally then.
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Scrolling for me is muchhh smoother on 2/28....reporting just after updating...will test further.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Compared to ???
[AT&T Samsung Galaxy S II SGH-I777] joeybear23:
I just installed 2/28 (I have been vascillating between siyah and earlier DD builds) and this time around I decided to use the kernel's default cpu settings. So I uninstalled SetCPU and then installed 2/28... and battery life has been awesome now. I am actually getting high deep sleep numbers now. Without any change in normal use, I am getting 80%+ in deep sleep. Granted, i need to run a few days to be absolutely sure, but so far it is looking very promising.
[AT&T Samsung Galaxy S II SGH-I777] Haloruler64:
Are you saying SetCPU had some effect on battery?
[AT&T Samsung Galaxy S II SGH-I777] stalked_r/t:
I'm testing /28 since mid afternoon yesterday. I'm starting slow to try to narrow possible differences in apps that I regularly use. Currently what I did was

flash back to stock

Flash rootkit

Install /28 kernel

Install UnNamed 2.2.1

Install 10tonhammer's Dark Fire Blue theme

Install BBS

Install Amazon App Store

Install Enhanced Email

Turn off WiFi and GPS

Turn on BT

Been up since 6:30 AM EST and battery is currently at 98%, so right around 1% loss per hour at the moment.