yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Screen off to powersave is a guaranteed SoD, because powersave blocks the SoD fix patch from working properly - I think Jank4au's issues were not related to the issues others have had.

As a result I've removed powersave, since conservative with min=max=200 MHz will achieve the same results. Personally, I set my max to 500, better to bump up a notch to hit deepsleep faster. Since 500 and 200 have the same voltage by default, they should be almost identical in power consumption for a given load. (Other than some small differences in internal/peripheral clocks which are also higher for 500.)

Uploaded 3/03 - with this release, Patch-A-Day is nearly complete, with the following results:

Code cleanups of problems caused by overclock code

Removed arighi's smooth scaling patch - doesn't behave well with non-stock min/max frequency settings

Removed the ashmem patch - caused performance problems for a few people, and the one person whom it seemed to fix problems for isn't experiencing them now anyway

Removed the cpuidle loadavg patch - questionable benefit, Google removed it too, I may revisit it or make it tunable though

Remaining patches:

https://github.com/Entropy512/linux_kernel_sgh-i777/commit/9d9903dee0cc5d3fd13503c1c9d104b8d09f16f1

and

https://github.com/Entropy512/linux_kernel_sgh-i777/commit/07917f0724a985819955b1f97df4f889eaaa3cb4
[AT&T Samsung Galaxy S II SGH-I777] DeXel55:
I spend a whole week trying to figure out what was causing those crashes! Then, I read here that SetCPU caused SODs for some people, I turned it and added to boot on and next time on charge it crashed. I wasn't able to get my phone crash even after restoring nandroid backup until I launched SetCPU. I am just going to try to validate this behavior by installing fresh unnamed 1.3.2 with "crashing kernels" with just SetCPU installed. I will report tomorrow.

Note: I didn't undervolt or anything else, except adding checkmark to "Set on Boot" and leaving governor on conservative. And yes I have to press power button 2-3 seconds to turn my phone on.
[AT&T Samsung Galaxy S II SGH-I777] gadget069:
I have a quick question, can a kernel effect sending mms. For some reason cannot run any other kernel other than the DD12/8/11, otherwise I have issues. I flashed the DD3/3/12 today and could not send an mms.

sent from my SGH-I777 w/Tapatalk
[AT&T Samsung Galaxy S II SGH-I777] Jank4AU:
What ROM are you on, out of curiosity? I remember having a similar issue some time ago.
[AT&T Samsung Galaxy S II SGH-I777] IVIadness:
Never had any issues myself. And have you ever ran any other kernel on your phone besides entropys I have heard of strange things happening if you don't clean out and old kernel before flashing a new one.
[AT&T Samsung Galaxy S II SGH-I777] alacrify:
Interesting - I'm getting just the opposite. 3/2 isn't quite as good as 2/15-C, but it's better for me than 2/28. Going to 3/3 now to see what that does.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Thanks for the update. Gonna flash it now ;-)

Sent from my iNsAn3 AnDr0iD Galaxy S II
[AT&T Samsung Galaxy S II SGH-I777] gadget069:
I had brought my phone back to stock root then installed unnamed 1.3.2 running DD12/8/11. I no issues sending mms. I ran the cleaner script then installed siyah 2.6.11. I like using CWM to name my nandroid backups. Starting having issues sensing mms, they wouldn't go through or take 10-15mn to send. So I reflashed back to DD12/8/11, I could send mms again. So I thought I would try a different rom, Shostock. I believe the kerenl flashed with that rom is DD2/18a. Once again I had issues sending mms. So I flashed DD12/8/11, using the cleaning script between kernel flashes, and I could send mms.

sent from my SGH-I777 w/Tapatalk
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
SetCPU screen-off profiles with limits below 800 MHz pretty much guarantee an SoD on stock kernels, which is why SetCPU has this bad reputation on Samsungs - sysfs is sysfs, but SetCPU is the only one with profiles that change governor based on device state.

There are patches for this, such as the one I use (thank netarchy for this one) - https://github.com/Entropy512/linux_kernel_sgh-i777/commit/cfa24134d112dac54037ad601e165ba0553f723e

You know what is ****ing annoying? Samsung KNOWS about this issue and has submitted kernel patches to mainline for it - http://comments.gmane.org/gmane.linux.kernel.cpufreq/7423 - yet the problem STILL exists in ICS kernels. (In some ways, this could be because it normally doesn't matter - only people who root can potentially hit this bug.)

The problem with powersave is that it forces 200 MHz regardless of what the cpufreq policy settings are - so when the SoD patch saves the current settings and forces min=max=800, it does nothing with powersave.

Any other governor should be safe. Now that powersave is removed, SetCPU should be safe too - as I've mentioned, that's what I use! :)

As to the MMS issues... weird, get logcat and dmesg. I can't think of any way this would affect MMS, except some odd bonkers thing like a timing bug in Samsung's MMS code that chokes with alternative I/O schedulers. (The reason I always kept BFQ in an init script was because on the Infuse, using it on boot would cause the device to freeze at the bootanim due to some weird race condition.) Or it might be some weird permissions issue - but no one else seems to have trouble. However, you're on a different carrier - but that shouldn't matter.
[AT&T Samsung Galaxy S II SGH-I777] smknutson:
Entropy, updated to 3/3 kernel version. Had another SoD. The common denominator seems to be having Tapatalk open when the screen turns off and sleeps. The kicker is, I never used to have this problem on older kernel versions. (Prior to around beginning of Feb)

Settings in SetCPU are: Ondemand, 1600max, 200min, all voltages are detected kernel defaults, sampling rate 90000, Up Threshold 85, Ignore Nice Load 1. The only running programs were SetCPU and Tapatalk. Screen off time 30s, connected to home wifi, battery level around 65-75% (not sure, its reporting 60% now, it could have dropped due to the restart bug).

Is there a kernel date you'd recommend me to test? I'm going to flash back over to your SH!Trom tonight, and see if it couldnt be a firmware issue (I had just gone back to UnNamed 2.2.1).
[AT&T Samsung Galaxy S II SGH-I777] IVIadness:
Entropy what settings do you use on you GS2 in SetCPU? I am new to playing with that app it has a ton of options so a baseline of the profile you rock would be awesome! Thanks man.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
I just tested this on my phone and it does not happen. :confused:
[AT&T Samsung Galaxy S II SGH-I777] smknutson:
:confused:

I dont know, it's all I can figure that I'm doing in all my SoDs to be the same
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
smknutson - Since it seems to happen relatively often for you, you seem to be a good test case. (Assuming that you are not using a screen-off profile with the powersave governor...) It's another case where it looks like the device entered suspend and then just died, but with a shload of log corruption for some reason.

Try 1/29 - That has been the largest architectural change lately, and myfluxi said he got SoD reports after implementing cpuidle (but I didn't seem to see any negative reports except for the MFC issues with Siyah even though GM put in the cpuidle backport with Siyah 2.6.12...)

I started seeing people claiming SoD problems with 1/30 (but supposedly stable with 1/29) - but maybe those people skipped 1/29 too fast. Those reports are why I didn't initially consider the cpuidle backport in 1/29.

If 1/29 still has problems, try the release before that.

If there's a clear difference between 1/29 and the release before it, then try 3/3B (not uploaded yet) - Has a small change that MIGHT fix things IF the problem is cpuidle. If not - I think I may need to rip it out and redo it, despite the fact that on my device it hasn't caused any problems and it has improved standby drain significantly. (It also has, I believe, reduced the battery penalty of suspend/resume cycles - I ran pingdrain against my phone recently and was VERY surprised by how well it worked.)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
3/3-B uploaded - might help some of the SoD issues, might do nothing. It's a shot in the dark.
[AT&T Samsung Galaxy S II SGH-I777] smknutson:
Alright. Flashed 1/29, I'll start playing with it.

Nope. No powersave, no screen off profile.
[AT&T Samsung Galaxy S II SGH-I777] Jank4AU:
Flawless Victory on 3/3

Having no issues and incredible battery life so far. I never went back and regressed kernels yesterday since we (meaning you) figured out it was my combination of Powersave 800Mhz and my screen off profile in SetCPU.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Nope as in not stable, or nope as in it's not crashing/SoDing when it happened often before?

If it's unstable, try 1/24. If that's stable, then see if 3/3B is stable.

And Jank4Au - correct, in your case since you were using the Powersave governor and that was the cause of your issues, no need to play with kernel swapping.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
I think he meant nope, He's not running powersave or a screen off profile.
[AT&T Samsung Galaxy S II SGH-I777] ryude:
3/3-B is EXTREMELY snappy! What are some recommended battery life profiles for setcpu?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
My current settings:

In all cases, conservative with up_threshold 90, sample_rate 40000 (decreasing this more will improve responsiveness but MAY negatively impact ability to enter LPA idle state, which is bad for battery. I'm not sure about this, I need to do some more research). I'm still fiddling with down_threshold - a high

down_threshold makes sense at higher frequencies like 1 GHz, but if it's too high it'll cause the governor to "bounce" at lower frequencies like 500 vs 200. I'm considering eventually doing some governor hackery to deal with this one.

Default: Min 500 max 1200

Screen off: Max 500 min 200 (highest priority)

Charger: Min 200 max 800 (lower priority than screen off)
[AT&T Samsung Galaxy S II SGH-I777] IVIadness:
Thanks man!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Uploaded 3/4 - This is the last release in PatchADay, as I've returned to the 2/7 baseline minus patches that were either suspect or definitively bad.

Coming next: GPU voltage control, and after that 3-step GPU clock/voltage control
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
going from 2/28 to 3/4.....installing now...thanks entropy!

[EDIT] - just have one problem...not with the kernel...

But In Setcpu in the advanced tab...setting ignore nice load to 1...wont last a reboot.. EVEN with the 'Set on Boot' checked.

Does anybody else have this problem?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
GPU voltage control added to existing clock control in 3/4-B

This is not the 3-step control in Siyah - that's coming soon.

http://xdaforums.com/showpost.php?p=23260574&postcount=64 for more info
[AT&T Samsung Galaxy S II SGH-I777] gadget069:
I installed binnacle this morning, same issue, had to revert to DD12/8/11 for mms to function. Ive never used logcat or dmesg, I should have some spare time tomorrow to figure out how to get the log files.

sent from my SGH-I777 w/Tapatalk
[AT&T Samsung Galaxy S II SGH-I777] joeybear23:
So, the disabling of the second core while the screen is off sounds like it would make a serious dent in power usage when you are not actively using it... Since I travel a lot, I often need to go many hours without access to a power outlet, and not all planes have hot outlets.
[AT&T Samsung Galaxy S II SGH-I777] csetera:
I've been running rooted stock with 3e recovery for a while now and I'm considering installing Entropy's kernel to get CWM and the battery savings. I don't do a ton of tweaking with SetCPU or anything else. What do people consider the current best build? Also, is it safe to install the kernel from heimdall without incrementing the flash counter or do I need to do something with Mobile ODIN?

Thanks!

Craig
[AT&T Samsung Galaxy S II SGH-I777] alacrify:
Just loaded 3/4-B - kernel cleaner, then install. On reboot, went to swipe the lock (Widgetlocker) - screen froze, had to hit back button to get to home screen, and it went black. 15 second press required to get it to reboot. Seems fine now, but last_kmsg attached in case it offers any info. I run setcpu, but on the defaults it sets - no u/c, overvolt, or anything else. UnNamed 2.2.1.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Well ideally it shouldn't get turned on in low load anyway - this just makes sure that something doesn't trigger it when it's wrong.

After support for Xan's new configurator app and Mali 3-step, improving the hotplug logic is my next goal. Unless ICS pops out first. ;)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Hmm... That one just seems to have crashed with no warning, and the log is fairly corrupted. How often does this sort of thing happen?
[AT&T Samsung Galaxy S II SGH-I777] alacrify:
Sorry, meant to put that in the first post - it's the first time it has ever happened. The only thing I've been changing the last week was loading your kernel updates (2/28 was draining battery on me, which could be because I didn't let it "settle", the others have been fine to great). I always run jivy's script before loading.

It's been fine since, so I'm not too worried about it. And I'm on the edge of going to ktoonsez's CM9 - or Fenny's AOKP - or PG's Binnacle (that's just today's WANT list :)). I'd ask your opinion, but I know what the answer would be :)

Just hoping to give you some data in case it comes up for others.
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
Running 3/4-B....no problems so far...also used the kernel cleaning script....question...entropy after you incorporate the 3 step mali thing....does that mean that xans new ExTweaks app will be compatible with your kernel?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
They're two completely independent things - other than that GM's example configuration scripts highlight Mali 3-step quite a bit - I was going to do config first then mali, but decided the app would be pretty barren without the mali stuff.

Edit: 3-step and ExTweaks support are in testing. Going to give this one a day or two before release.
[AT&T Samsung Galaxy S II SGH-I777] ryude:
Just got a freeze on 03/04-B, using exact same settings I use for every other kernel. I went to open the mms app and it just froze. First time I've seen that happen with uv: 950@200, 1000@500, 1050@800, 1100@1000, and 1200@1200. I know it's probably the uv, but I still want to let you know about it.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Probably... interestingly I think your voltage setting for 500 is above stock... 1200 is undervolted a bit though.

There's a possibility the new cpuidle patch in 1/29 may require people to back off their undervolts - If the core power is switched on and off more rapidly, that will make the regulator's job harder. But it's better to juice the voltage a little so you can depower the core than to leave it running at reduced voltage.

Got a last_kmsg in case it's not undervolt?
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
I just love how avidly you monitor what goes on in here Entropy. Keep up the great work.
[AT&T Samsung Galaxy S II SGH-I777] :
Im still on 2/26 (2/28 didnt hold up as well for me) and now there are like 3 more releases. Good Lord, how do I get enough time to test all these?

I might just stay on 2/26 for now. :D
[AT&T Samsung Galaxy S II SGH-I777] DeXel55:
SetCPU alone by itself does not cause crashes, nor with all apps restored from backup that was made from ROM that was crashing. However, crashes do happen after restoring nandroid backup and launching SetCPU.

Thats said I just flashed different ROM (trying Shi1tRom now with packed kernel) and restored my apps including setcpu and everything seems perfectly stable. At least, this is the reason behind my crashes (garbage filled ROM?).

Thanks, Entropy!
[AT&T Samsung Galaxy S II SGH-I777] Simba501:
Entropy,

Couple of questions.

What's your impression of load balancing? I don't see anything in the changelogs related to its support. Is tweaking it a general capability? Or does the ability to configure it have to be enabled?

i.e.

echo 1 > /sys/devices/system/cpu/sched_mc_power_savings

In testing (wake idle), the CPU seems to ramp up to 500 mhz more frequently as a result of the second core not activating as it typically would. I suspect that under normal usage, this pattern would continue (generally spending more time in a higher frequency than it would with two cores). My question is if the extra clock cycles are worth not having both cores active.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
2/26? I thought that was the one that was utter **** for you?

Up to around 800 MHz, I believe it's better to ramp up the clock than to activate the second core. Having the second core active blocks deep idle states (LPA and AFTR), which makes sched_mc_power_savings=1 worthless. (BTW that parameter has zero effect on hotplug, only scheduling when both cores are active.)

More at http://xdaforums.com/showpost.php?p=23193259&postcount=100
[AT&T Samsung Galaxy S II SGH-I777] tboooe:
Any update on the soft keys light up issue? I am on 2/15C and am still having this issue.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
You mean the touchkeys shutting off?

Whatever ROM you're running, revert liblights back to stock. If it still happens, attach a dmesg.

Basically, right now all of the evidence says that liblights is misbehaving.

If people REALLY want a kernel fix, the fix will be to rip out BLN completely.
[AT&T Samsung Galaxy S II SGH-I777] smknutson:
Ok, I'm on 1/29 running UnNamed 2.2.1, just had another SoD. I can trace it back to the program Tapatalk. Specifically, if I am typing a longer post, and the screen times out due to inactivity, it gives me a SoD. Keep in mind this does not happen every time, but This has been happening across kernel versions, the same situation. Is it possible that a program could cause SoDs, and not the kernel?? Would you want another last_kmsg?
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Now it's time for you to try 1/24.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Yes, even though so far they seem to be uninformative - you may get lucky.

Some programs can bring out bugs in the kernel though - sometimes directly, in other cases indirectly. (Just by altering the timing of how everything works in the system.)

So I assume, in this case, you're taking a break from the post if the screen times out? What is your timeout set to?

Yup. If he can get a last_kmsg with 1/29 that's good, but then it's time to try and repeat with 1/24.

Tonight I'll try to reproduce with tapatalk to see if I can reproduce myself - If I can, this gets MUCH easier!
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Weird cuz I use Tapatalk all the time.... But it rarely times out on me since I have a 10 min timeout. :D
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Timing out whileposting would be pretty rare in general, since usually in that case you're, well... writing... :)

I need to figure out if XDA has some sort of sandbox area for stuff like this... Although I guess I could just cancel the post.

Edited the OP title - I realized with 3/4-B I altered the changelog and uploaded, but didn't change the title.

Edit 2: smknutson, do you use crt-off animations?
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Thanks Entropy! DD-3/4-B looks like the best cure for phone-insomnia till date :)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
3/5 uploaded

Mali 3-step

Extended hotplug tuning

ExTweaks support - https://market.android.com/details?id=com.darekxan.extweaks.app
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Thanks for the great update :)
[AT&T Samsung Galaxy S II SGH-I777] pikachu01:
Hey Entropy512, with recent experimentations, I've roughly found that limiting frequency to 500MHz (or so) on screen off gives a lot of battery savings in return. I've used lulzactive and Siyah's ondemand(that's actually ondemandX in the hood), both with significant battery savings (4-5 hours screen time with uptime of 1 1/2 days to 2 days). No gaming though, gaming drains the GPU + display + high frequency usages.

Whereas, using the plain ondemand or even conservative and smartassV2 didn't amount to the savings that I've tried. This is an experiment that I've done for the past month. No logs though, you have to take my word for it.

What do you think of this? Let me know of your comments :)
[AT&T Samsung Galaxy S II SGH-I777] desiromeo719:
I like the new Entropy...Lol..Thank!
[AT&T Samsung Galaxy S II SGH-I777] manny05:
Might be a stupid question but can I use this kernel with aosp ICS? I doubt it has the tweaks or hacks to make the audio work for phone Calls..but I thought I'd asked. I'm a huge fan of this kernel
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
That's why we have SetCPU. :)

(I think a few pages back I mentioned that I have a screen-off profile in SetCPU with a 500 MHz limit - and also 500 MHz min when screen is on.)
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
When will you break XDA? :p

Testing this out now, liking the idea of 1 core off. (I am 1 day late to the patch)
[AT&T Samsung Galaxy S II SGH-I777] howtomen:
Kmsg

heres the file from the SOD
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I had to yank all the exp releases to make room. Going to move old stuff into a separate post when I have time.

Attached is a test kernel for those having SoD issues - Rather than go back and forth between various releases, this will hopefully provide more informative last_kmsg dumps.

This hasn't been pushed to github - instead I've attached the patch for this. It does some ugly hackery (thank garyd9 for the inspiration here) to enable the no_console_suspend commandline option in the kernel.

This may possibly negatively affect battery life, I'm not sure - but without it, the crash doesn't get logged.
[AT&T Samsung Galaxy S II SGH-I777] smknutson:
No crt off here. It has been rare, but always when I was typing into Tapatalk, stopped mid post, and let the 30s screen time out take effect.

I'll try 1/24?
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
I believe that was the intent. Then move to his latest after...
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Actually try that new test kernel from a few posts above now...

Hopefully it will provide a more informative last_kmsg.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Hi Entropy,

Yesterday, the deep sleep during the day was excellent on DD 03/04-B, but it was worse overnight.

(I have links to BBS, logcat and dmesg logs at the bottom of this post)

Reason: The screen turned on automatically every 15 minutes automatically! That's weird, that has never happened.

The only new thing on the phone yesterday was the kernel and the TED app (but I have disabled background sync in TED).

I was able able to see in Llama log that WiFi was turning on every 15 minutes because the screen was turning on every 15 minutes.

BBS log

log cat + dmesg

BBS only tells that a lot of partial wakes were caused by AlarmManager, nothing else looks out of normal.

Can you please have a look at above 2 files?

Thanks

Sent from myphone.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
You know - our country wouldn't have to worry about secrets getting leaked if they just put them in the first posts of XDA threads. Best way on the planet to keep a secret!

I'll look when I have the time, but deep sleep is rarely kernel related. Try reverting to your last kernel to see if it continues.

Odd... Random screen wakeups are an ICS problem too.