yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] :
So are people liking 2/15-C better or 2/18-B better?
[AT&T Samsung Galaxy S II SGH-I777] ryude:
In my opinion, 2/15-C was better all around. 2/18-B seemed a little jittery and battery life wasn't as good.

Neither can touch 12/8/11 though, so I'm back on that.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
2/15C hands down for me!

This is what I got with 2/18B, lot of snvet dormancy wakeups at night! My phone drained about 26-30% in about 7 hours.

This was yesterday night with 2/15C. 7% discharge in 9 hours. It shows that even though the phone is awake most of the time overnight, there is very little discharge, not sure what that is. It will be great if someone could throw some light on that.

BBS dump of that: http://db.tt/0bGvqRZc

Sent from myphone.
[AT&T Samsung Galaxy S II SGH-I777] :
Even though you got more time with 2/15-C it looks like from your pictures that your phone was awake w/o the screen on a lot more than with 2/15-B.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
As a binary, no - However I have been considering doing I9100 builds. In fact I posted one as testing in the VillainROM thread - I did not receive any feedback on it though. I wanted some limited testing before releasing it in a more obvious venue.

http://xdaforums.com/showthread.php?p=22598211#post22598211

You won't screw up an I9100 much - it's almost identical. It's also, at least in theory, VERY easy to build for the I9100 target from the same source base, which is what he was asking for.

Not correct, I did update my changelog - see 12/8.

The change was not due to any personal desire of CFQ over BFQ, it was due to wanting to keep my initramfs clean. The tweak script belongs in init.d, not the initramfs, simple as that.

svnet-dormancy wakelocks wouldn't be affected by anything I changed from 15C to 18B - you simply didn't evaluate the two kernels against each other for long enough, since svnet-dormancy wakeups are NOT under the control of the kernel - svnet-dormancy wakeups are due to incoming cellular data.

Both the 18A and 18B patch should improve power management. One patch allows a peripheral to be shut off in deep sleep, the other one fixes a documented cpuidle bug.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Yes, but what's weird is that while it looks from the screencap that the phone was awake about 7 out of 9 hours, in the BBS log of those 9 hrs shows wake time of 19 minutes. If someone knows the reason for this, it will be great. I'll also post this in the BBS thread.

---------- Post added at 02:38 PM ---------- Previous post was at 02:35 PM ----------

Thanks for making that clear to me Entropy. I will give 18B another go today. What's surprising is that for both nights, I had mobile data and Wi-Fi turned off on the phone and still I saw those intermittent wakeups on 18B with heavy battery drain. 15C shows a strange long continuous wakeup but that has hardly any battery drain.

This is the CPU Spy screencap for those 9 hrs overnight while using 15C. Battery graph shows phone is awake but CPY Spy shows it had a good long night sleep :)
[AT&T Samsung Galaxy S II SGH-I777] ryude:
I wonder if disabling background data will help with some of the wakelocks? Of course you can't use the market, but can always just turn it on when you need it.
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
Band-aid solution. While it'd be harder to pinpoint the source of data activity, finding out what's causing it is the better course of action to take.

Sent from my Galaxy SII
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
I assume you were referring to my posts.

I have just Google contacts/cal/mail sync enabled. But that shouldn't matter if I disable mobile data and WiFi at night.

On that topic.. a related question:

Say, that Google mail sync is going on, and the mobile data/Wi-Fi turns off in-between. Does that wakelock stay held in that case?

I am sorry for cluttering this kernel thread but had to pose this question here because of related posts above.
[AT&T Samsung Galaxy S II SGH-I777] DeXel55:
Hi, Entropy. Sorry for taking so long to update the crashing problem.

So, I am getting crashes starting from 1/2/12 (this is around when I started to experience the problem in the first place) and they definitely also happen with 1/30/12, 2/7/12, 2/15A and 2/15C but what is weird they happen only with unnamed 1.3.2 with my apps restored with MyBackup Root. I didn't manage to get crashes on fresh installed ROM. With the same setup but different kernels (DD 12/8/11 and 12/12/11 and Siyah v2.6.12) crashes don't happen.

Another weird part is that crashes don't happen with hellrased LilRom and ShishirROM with the same apps restored with MyBackup Root and kernels that caused crashes on unnamed.

To me it seems some weird ROM+kernel+apps crashing combo.

Anyway, I will be running ShishirROM in the next few days, with your five last kernels and same apps, and they return to unnamed and see if it crashes again.

So far 18B and 1/2/12 have been rock stable.

Thanks for help, Entropy. Since this problem seems to be some very setup specific (at least in my case), I guess you can mark it as stable enough and continue the further development. I will keep this updated though.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I have seen that in some cases, with multiple kernels (and multiple devices) the Android battery stats screen will sometimes falsely report awake time that wasn't actually spent awake.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
I didn't quite get that. By 'multiple kernels', you mean that if I had kernel A on a day to begin with and halfway through the day if I flashed kernel B, the battery stats can show false awake times?

I had 2/18B kernel till yest morning 8am and then I flashed back to 2/15C (when I freaked out looking at that overnight battery drain). So yesterday night I had that false awake time shown in battery stats but did not get an equivalent battery drain.

So I will still stick with 2/15C for one more day to get more dependable Android battery stats. Tomorrow I will switch to 2/18B and again do the overnight drain test.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
No, I'm saying I've seen it often across various kernels for devices other than the GS2 even.

This is why I trust CPUSpy and the kernel wakelocks list far more than the Android battery stats screen - the Android battery stats screen is kind of notorious for not quite working right.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
About those intermittent svnet dormancies I saw when using 2/18B I have to use Microcell at home. Could any intermittent power suppy/WiFi cause those abnormal svnet activities? Even with mobile data/Wi-Fi turned off?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Maybe... My experience with microcells is that they're buggy as ****. This wouldn't be the first time I've seen people report weird behavior (including battery drain I think) on microcells.
[AT&T Samsung Galaxy S II SGH-I777] :
I can't even use my Microcell because it murders my battery. On both my Captivate and my GSII on several rooms and kernels, its always killed my batter so I dont even use it anymore.
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
This. I've seen numerous accounts of battery drain issues.

Sent from my Galaxy SII
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Thanks guys. Then the battery life of over 1 day which I get is excellent for a weekend when I am at home the most and use the Microcell the most.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
All of the microcell horror stories are why if I have coverage issues when I buy a house - I'm going with Wilson.

I have one of Wilson's vehicle products installed in my car and it's amazing.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
+1000 on Wilson products.
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
Are you referring to something like this?.....http://www.amazon.com/Wilson-Electronics-801213-Booster-Vehicle/dp/B0011GI950

I'm considering this because some areas around my location kill my signal/battery sometimes.

Edit: Sorry for hijacking and taking thread off topic ;)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Yup - I have this one in my Subaru - http://www.amazon.com/gp/product/B0011GI94Q/ref=oh_o01_s00_i00_details - Appears identical to your link except with a different inner antenna. In my case, I have the inner antenna on my dash and the official Samsung car dock hangs the phone 1-2 inches above it. The one thing with the vehicle Wilson units is that the phone has to be very close to the inner antenna to work well. In a cradle like that, it should perform extremely well. Watch out if you have a sunroof - this could permit too much inner/outer antenna coupling. Also, it will almost surely not work well if the antenna is on the trunk of a sedan - the inner antenna will be right in its pattern with no shielding. In my case, the outer antenna is at the rear of the roof of my Outback.

Home systems should give better coverage from the inner antenna, especially if the outer antenna is a directional one pointed at the tower.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Uploaded 2/26 - Another only-one-patch change.

I slowed down hoping to get more feedback from those who indicated stability issues, but they're silent now. I believe the majority of the issues in 2/7 were due to arighi's smooth scaling patch combined with leftover cruft that needed fixing post-overclock. Those stability issues should be resolved now.

The few people who reported SoDs on 1/30 have not reported any followups. That leaves only DeXel's report.

Oh, here's a fun one: At this point, between I9100 update3 and the cpuidle backport, power drain when a wakelock is held is only 1.5%/hour or so. Yes, that's right - 1.5%/hour when being hit by a wakelock. (See attached.) Last time I tested this (I777 source base), this was 4-5%/hour.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Weird. See what happens if you restore apps one at a time.

Were these crash-to-LPM, or crashes that happen when unplugged too? If they happen when unplugged, it would be useful to see a last_kmsg.
[AT&T Samsung Galaxy S II SGH-I777] DeXel55:
That happens only during charging. I will flash unnamed back on Tuesday (or maybe tomorrow since ShishirROM with 2/18B seems very stable) and try to restore group of 10 apps (starting with those that require root) at the time on 2/7 kernel. Bad side is that I lost my nandroid backup of "crashing" setup, but it wasn't a problem to get unnamed crashing anyway and I have backup of 2.2.1 which was also crashing if I remember correctly.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Thanks for the update man :-)

Sent from my mobile phone and delivered to your face.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Attached is what happens with the same wakelock running 12/08 - About 4-5%/hour.

People weren't lying when they said Update3 was a major improvement in terms of power management.
[AT&T Samsung Galaxy S II SGH-I777] shahulvm:
Clarification pls

Hi Entrophy,

Can you please suggest if the below param value in build.prop should be 0 or 1. As I have searched the net and in XDA, most of the information are contradicting. (some suggest to use 0, while others suggest to use 1).

ro.ril.disable.power.collapse=1 or 0

I get mixed results with them and hence decided to ask you for suggestion.

Thanks much..
[AT&T Samsung Galaxy S II SGH-I777] AntwanL:
Just installed the latest update on LilRom 1.3.1 and it's running very smooth so far.

Big thanks for the update!
[AT&T Samsung Galaxy S II SGH-I777] nyamoV2:
3 hrs mostly idle with your newest updates and I've loss 6%.. Great job and keep up the work.. I think it's time for another donation come Fri
[AT&T Samsung Galaxy S II SGH-I777] omgabunny:
5 hours of idle and I've lost 3% with 2/26. Thanks for the continued awesome work!
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Hi Entropy,

I installed the DD2/26 yesterday and the overnight drain behavior was similar to what I saw for DD2/18B.

I again compared the BBS reports for the overnight drains while on DD2/15C and on DD2/26.

During both times I was connected to Microcell and for a 6 hour duration, the mobile data and Wi-Fi are turned off.

I noticed that there's a huge difference in duration and count of deleted wakelocks.

When using DD2/15C:

BBS log duration: 9 hrs overnight

"deleted_wake_locks" () : 26 s (26 s) Cnt:(c/wc/ec)922/0/47 0.1%

BBS log: http://db.tt/6FOf8ZPL

When using DD2/26:

BBS log duration: 7.5 hrs overnight

"deleted_wake_locks" () : 13 m 36 s (816 s) Cnt:(c/wc/ec) 73530/0/1424 2.5%

BBS log: http://db.tt/TmrjtK9a

In the above comparison, there is absolutely no difference in the phone config (ROM/apps installed/..) other than the kernel.

Any hints to what could be causing higher deleted wake locks?

Thanks

UPDATE: Adding more info to help debug this issue I am facing.

- I use Voltage Control to set scheduler to cfq, governor to OnLoad, set freq range to 200-1000MHz and do undervolting. Does this somehow cause contention with the kernel?

- Few major background apps: widget locker, cerberus anti theft, llama, green power, swype, go launcher, minimalistic text

NOTE: The Voltage Control settings and background apps were the same when I had 2/15C kernel too.

Sent from myphone.
[AT&T Samsung Galaxy S II SGH-I777] Karashta:
Slept for eight hours and only lost 1% of my battery. That is crazy
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
That's sweet! I am interested in knowing how you set up your phone. If you get a chance, it will be great if you can fill out the battery life study poll.
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
I know the feeling. :D

Running my rom and got these results as well, though I slept longer not sure why it only said 5 hours.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I need to check, but I believe that's a Qualcommism that doesn't apply to Samsung CPUs. I'm fairly certain it does nothing on our device - in fact I'd check reputable firmwares (such as stock and ones like VillainROM) to see if they even change this setting.

In theory, "power collapse" is a Qualcommism for "deep sleep" - disabling it would be bad! But I think on earlier Qualcomms, deep sleep didn't always work so well.

See post 3 or 4 for info on enabling deleted_wake_locks debugging. The most common source I've seen for deleted_wake_locks is that all wifi related wakelocks (wlan_rx, wlan_rx_wake, etc) get converted to deleted_wake_locks when you turn off wifi.

What I do see is something is definitely waking up your phone frequently... WAY too frequently. I can't review the BBS logs until tonight.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Last night on 12/8/11

Wifi on and all my sync stuff on. 7hrs and lost 6%.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
If you don't have any data on then it looks like the microcell is your culprit.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Thanks, I have changed that parameter to 35

I guess that the next step is to post the dmesg and logcat soon after I wakeup tomm morning.

---------- Post added at 11:10 AM ---------- Previous post was at 11:06 AM ----------

But I *WAS* on microcell when I had version 2/15-C of the kernel.. and that night, the battery drain was just 7% in 9 hrs.

The only difference that made the battery graph look like the one I posted above was changing the kernel from DD 2/15-C to DD 2/26.

As Entropy suggested, I have changed the wakelock debug parameter to 35 (from 3) and learn what's going on there.
[AT&T Samsung Galaxy S II SGH-I777] :
Weird, I installed 2/26 and my phone seemed sluggish, so I performed a few reboots and it was still sluggish, so I redownloaded and reflashed thinking maybe something didnt go quite right. Still sluggish (and by sluggish I mean it takes 2-3 seconds to turn the screen back on if it went to sleep, and 3-5 seconds if waking up from a deep sleep, scrolling lagged bad and was choppy in both the app drawer and any app that scrolled)

So I flashed back to 2/15-C and my phone is back to being snappy and my screen instantly turns on when hitting the power button... plus battery drain is very minimal too so Im still happy... just weird that my phone/setup didnt like the 2/26 version.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Weird... Go from 15C to 18A to 18B to 26 to see where it started.

This is the best time to try and debug stuff like that, as I right now am keeping it to only one patch per release until I'm back at the 2/7 level.
[AT&T Samsung Galaxy S II SGH-I777] IVIadness:
Weird I am not having any issues, running serendipity on s2 of course!
[AT&T Samsung Galaxy S II SGH-I777] :
Im probably the only person having that weird issue... but I will go through all those kernels and see when it happens for me... but if its just me, then it probably just my phone/setup being picky.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
I second that. I too notice that it's taking close to 3 seconds for the screen to turn on.

I froze Widget Locker and tried turning on the screen, still I see that 2-3 second lag... don't recall having to wait for the screen to lit up on 2/15-C.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
You said in your post that both times wifi and mobile data were off. :confused:
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Sorry, corrected the typo.

But I *WAS* on microcell when I had version 2/15-C of the kernel.. and that night, the battery drain was just 7% in 9 hrs.

The only difference that made the battery graph look like the one I posted above was changing the kernel from DD 2/15-C to DD 2/26.
​
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Back to the topic at hand. :mad:

Have you flashed the different kernels as entropy explained?

I'm gonna test 15c since I haven't yet.
[AT&T Samsung Galaxy S II SGH-I777] JmPTaz09:
Using 2/26, reduced sampling rate of conservative to 25k, noop, running great, snappy and good battery performance, deep sleeping nicely. Oh, also undervolted by about 75-100. 4.5 hours on, 48 mins screen on and some music, at 86%. Seems good so far.

Edit: no wake-up lag, just the normal second or so.
[AT&T Samsung Galaxy S II SGH-I777] :
OK, I went from 2/15-C to 2/18-A, 2/18-B and then back to 2/26. 2/18-A and 2/18-B runs just fine on my phone. Its when I get to 2/26 is when my phone starts to act like an 80 year old man. Defiantly something in the 2/26 release that does not play well with my phone. Im back on 2/15-C though because it seems to be more snappy.

Again, this may just be a 1 person deal because several others have said they liked it, so at least I know for me that my phone dosent like 2/26. Ill just sit back and wait until the next release comes out and see if anyone else has any issues with 2/26.
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Can you explain what reducing the sampling rate of conservative to 25k does?
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
CPU load is checked more frequently, and as a result, the governor ramps up the frequency more often.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
With the config in my Sig I'm pulling 10hrs and I'm down to 78% with 1hr screen on. This is also on stock battery. nothing beats Entropy's Kernel and UnNamed.
[AT&T Samsung Galaxy S II SGH-I777] EVIIIL:
I dont know how you do it but the 2/26 seems to be working very well for me. Usually at this time of day I am in the low 60% range with your previous kernel, and so far I am at 75% with the 2/26. I am running the ICScrewD 2.0.1 Rom with stock settings with 8 hours from unplugged.
[AT&T Samsung Galaxy S II SGH-I777] jneilliii:
Decreased Overall Volume

Just wanted to check in with everyone, after upgrading my UnNamed 2.2.1 ROM to Entropy's Daily Driver 2/26/12 kernel I've had a dramastic decrease in overall sound volume across the board. The previous version of the kernel I installed was 2/7/12 and didn't seem to have the issue. I've verified that all volume levels are set to max and I can barely hear my notification tones at all. Any help would be greatly appreciated.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Well, the patch in 2/26 is memory management related, so something may be "interesting" with memory on your phone. Do you have anything in init.d, especially lowmemkiller tweaks?

The problem with this is that the patch in question solves crashes for another user (Nizda1)...

Doesn't make sense - I haven't touched the sound driver at all. Slowly roll back one release at a time to see where the problem begins.
[AT&T Samsung Galaxy S II SGH-I777] :
Nope, I dont have anything in unit.d or any special tweaks... just running unnamed and your kernel.

On another note, 2/15-C has been absolutely incredible for both responsiveness and battery... I've never had battery life (both idle and in use with calls/texts/tapatalk). Absolutely awesome speed fluidity and battery, I'm completely happy with 2/15-C.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Hi Entropy,

These are the logs I got after I kept my phone running on battery for about an hour at home.

logcat, dmesg log (after setting debug_mask = 35 ): http://db.tt/zZVL7NNn

BBS log: http://db.tt/8HJk20yv

About 28k wakelocks in an hour!

I looked for wake_lock_destroyed in dmesg but didn't find it heavily populated with those. What else should I look for in it?

I did not get that many wakelocks at work, but still heavier than usual battery drain.

logcat, dmesg log (with debug_mask = 35): http://db.tt/LwMkZVEb

BBS log: http://db.tt/w9iS8XRX

1698 wakelocks in 38 mins.

At home, I have D-Link DIR-655 router and Microcell.

I will be testing 02/26 overnight. Tomorrow, I will switch back to 02/15-C and post similar logs.
[AT&T Samsung Galaxy S II SGH-I777] Haloruler64:
Hey Entropy. I used to run your kernels all the time. I just rooted my replacement SII (so no old scripts, everything clean), and flashed SHOstock and your 2/26 kernel over it. Crazy laggy. Nothing is smooth. Reflashed SHOstock and it works perfect with Siyah kernel. And I know the kernel before 2/26 didn't have any lag whatsoever. I posted this in the SHOstock thread and someone told me to write this here because Red5 was having the same issue.
[AT&T Samsung Galaxy S II SGH-I777] NJGSII:
I haven't noticed any lag whatsoever with the latest release.
[AT&T Samsung Galaxy S II SGH-I777] :
Going back to 2/15-C fixed my issue. 2/18-A,B also ran fine on my phone, but 2/15-C is just awesome.

2/26 made my phone super laggy and it took about 4 seconds for my screen to come on. Apps and the app drawer was choppy for me.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
I'm testing 2/15-c right now. We'll see what tomorrow brings. I haven't tried 2/26 since I didn't like what 2/18-b did overall for my phone.
[AT&T Samsung Galaxy S II SGH-I777] :
It seems these patch-a-day kernels aren't friendly with everyone.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Just like the roms
[AT&T Samsung Galaxy S II SGH-I777] msgfromside3:
Same here. I unscientifically feel better battery life as well.
[AT&T Samsung Galaxy S II SGH-I777] stalked_r/t:
I need to play with my device some.

Late last night, I used the one touch to return my phone to stock, wiped it using the input code in the dialer, Rooted the phone using the one touch. I then flashed 2/26 via mobile odin, applied UnNamed 2.2.1 and went to bed. Got up at 6:30 this morning. In the last two hours, I've dropped 21% battery life. Only thing I have installed or on is WiFi. I have a feeling this is an anomaly, so I'm going to redo that entire process again and see what happens. I'll let you know if I see the same type of results after a full charge.
[G2 and Desire Z General] philbagg:
Hi, I'm having a few issues with the CoreDroid 6.7 rom i have installed on my phone. I was wondering if there was a way I could go back to using the stock HTC Sense rom (that I was using before), while keeping root access? I've got a few apps that use it.

If so, where can I get the stock rom?

Thanks.
[G2 and Desire Z General] Nipqer:
Search the development forum for pre-rooted stock roms.

I know rmk has some for the DZ, and there are some for the G2.

-Nipqer
[G2 and Desire Z General] philbagg:
Cheers man!