yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Note that it's still a quick "workaround" fix - it'll break next time the su binary updates. I'm hoping to have a more robust solution for the installer script by then.

I can't figure out why no one reported this as an issue on the Infuse forums - it's the same script ALL of the Infuse kernels use with tiny modifications that wouldn't affect this issue.
[AT&T Samsung Galaxy S II SGH-I777] ArtificialMusik:
Not to harass you but how can I flash bootanimation.zip? I keep getting error in CWM.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
You don't flash it, unless it's part of a CWM-flashable package. Most of the time, it's a straight bootanimation.zip that you must manually place at /system/media/bootanimation.zip

The following works for me, it requires ADB to be installed and working. If you don't have ADB installed and working, Google is your friend.

adb remount
adb push bootanimation.zip /system/media/bootanimation.zip
adb shell chmod 644 /system/media/bootanimation.zip
[AT&T Samsung Galaxy S II SGH-I777] ArtificialMusik:
Thanks a ton! I got it to work. I was just so confused on where the location was of it. Now I got ICS 720P instead of lame old AT&T! :D Next step is to change the i9100 triangle !!

Thanks a ton for your help man.
[AT&T Samsung Galaxy S II SGH-I777] wonner:
Can you post the file?
[AT&T Samsung Galaxy S II SGH-I777] ArtificialMusik:
http://briefmobile.com/download-nexus-prime-boot-animation
[AT&T Samsung Galaxy S II SGH-I777] othermark:
Installed 01.23.2012. Seems to work. Love the ATT TCP initial window patch. Seems hilarious, but they must have had a reason, I'm just not sure what it is.
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
Why wipe the dalvik cache for a kernel change? The two have nothing to do with each other.
[AT&T Samsung Galaxy S II SGH-I777] AntwanL:
Lol my bad, not sure why autocorrect feels **** has a higher priority than shut.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Maybe you tell too many people when you're taking a dump? :P
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
When you got to go... you got to go... and it just takes a higher priority.

(Now, if I could only get my 6 year old son to realize that it takes a higher priority than angry birds...)
[AT&T Samsung Galaxy S II SGH-I777] austinsnyc:
Got boot loops with this release. Unnamed 2.2.1 and OC but a stable overclock. Wasn't even able to get past boot logo.
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Can you please mention the steps you followed to flash this release?

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] Gutterball:
Heres what I did I was on siyahs newest kernel running illusion. I flashed jivys kernel cleaning script then flashed entropys kernel and then charged to a 100 percent and callibrated. My battery has been phenomenal today its only dropped 22% since 7 am this morning. it is now a little after 2:30 pm and I'm now at 77%. Haven't even thought of charging all day. I've been texting and made a few phone calls as well and played a little zombies omg. So its gotten use too. I'm impressed! Awesome work! Entropy Thanks!:D
[AT&T Samsung Galaxy S II SGH-I777] AntwanL:
+1
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
How were you OCing? Were you on a different kernel (such as Siyah) previously?

I know that using Voltage Control and changing kernels is BAD. Unlike SetCPU, VC has no methods to detect that the kernel clock/voltage control interfaces are different, so can REALLY hose you up when changing kernels.

Can you enter recovery?

Yup, did you CWM-flash it or use the .tar?

No need to calibrate battery on any Samsung Android device currently in existence. Well at least not their phones - Tab 10.1s have a valid reason to fullcharge. Also wiping batterystats.bin does nothing in terms of the fuel gauge.
[AT&T Samsung Galaxy S II SGH-I777] Gutterball:
Good to know. theres another useless app to dump now.:D
[AT&T Samsung Galaxy S II SGH-I777] austinsnyc:
I use setCPU for over clock. I was using 2.6.9 from the other kernal dev before trying your 1/23/12 kernal. Flashed 2.6.9 again and phone was good to go. Love you your kernals for battery life its amazing! Just deleted everything in the int.d folder going to try and flash yours again. Oh and voltage control has never touched my phone.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Probably you got nailed by some cruft siyah left in init.d

Booting siyah again might return it there - if you bootloop again, enter CWM (this should still work) and clear out init.d from recovery (might need ADB for this)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
1/24 up - adds tun.ko, nothing else. Working on getting experimental up

Removed 1/23 download since this is such a tiny change.
[AT&T Samsung Galaxy S II SGH-I777] Alucardis666:
Thank you for the update. :-)
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
Entrophy, I think my mobile ap disconnecting after 15-20 min. is kernal related. I used stock kk6 kernal today and was uninterrupted. Is it possible that there is something in the kernal tweaks?

Thanks again for your work.

SHOstock

DD1/2/12 exp

Onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
guys, it's kernEl, not kernAl... :)
[AT&T Samsung Galaxy S II SGH-I777] Afterain:
Thank you for your kernel, I'm using now:D
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Hmm... Interesting. I've never had tethering problems in the entire time I've used this, other than the config perms problems (ROM problem) with newer international bases, and the initial I9100 Hellraiser tethering issue.

Does this happen on older/newer releases? Especially if you go to a release before the Broadcom DHD update patch? (unfortunately that's the same one with the UCKK6 wifi incompatibility fix... hmm...)

I've nearly given up on fixing anything wifi-related with UCKK6 base though - UCKK6 is clearly broken in horrific ways when it comes to the BCM4330...
[AT&T Samsung Galaxy S II SGH-I777] austinsnyc:
Ya still stuck on 2.6.9 some app must have set something while using 2.6.9. Tried cleaning scripts and deleting everything in the int.d folder and still no love. Looks like in I'm going to have to do a freash instal and start over.
[AT&T Samsung Galaxy S II SGH-I777] mjgspr95:
I have been updating as you roll out new ones. Not sure when the issue started. I'll try an older version an test. How far back do you recommend?

Edit: 12/8 stayed connected, but reverted to Edge (2g) even after reboot. I remember that from back when too. Trying the lates DD then I may have to stick with stock ... Mobile AP is my internet source for work.

SHOstock

DD1/2/12 exp

Onepointsixingit
[AT&T Samsung Galaxy S II SGH-I777] Nizda1:
Entropy,

I have been having some serious crashes followed resulting in hard reboot or straight kernel panic since 1/23/12. I have too many theories on whats going on to list in a post, so I put a .tar of 3 last_kmsg's from 1/23 & 1/24 as well as debug info, lastly 2 screenshot of certain pertinent areas within the file system that I would like you to take a look at. Whats odd is the most prevalent problem I've seen taking a couple quick glances at the last_kmsg's is "[TouchKey] system calling LED Notification control". Which is so far where everything starts going downhill. It wouldn't be odd except for the fact that I have never used bln or installed any type of bln control app etc.. to allow its usage. The only thing related to bln on my phone or ever has been is the shared object files that most dev's include in ROM's nowadays. Lastly, for awhile now I have consistently seen problems with ashmem its abilities with virtual memory allocation within this OS. Some of these problems could be just my isolated problems.

Thanks,
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Hmm... One of them, a crash seems to happen due to a softlockup in "comm", with a modem wakeup or sleep activity 30s beforehand.

In the other two - there's clearly some wacky vmalloc stuff going on.

1) Are you using any tweaks that enable swapping or anything? (odd... I'm seeing your softlockup timer trip at 30 seconds, I was fairly certain the default was 60...)

2) Not sure where you got ashmem from, but you MIGHT be on to something there, I sort of recall seeing some patches regarding ashmem issues, I'll have to look for them again. Not sure why you'd suddenly have problems now...
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Finally uploaded experimental, forgot to do so last night. Too busy tearing apart a fraud.
[AT&T Samsung Galaxy S II SGH-I777] dominuce00:
I appreciate all the work that you have put into making your Kernel a great one. Let's hope the fraud learned a valuable lesson.
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
a fraud? :confused:
[AT&T Samsung Galaxy S II SGH-I777] Nizda1:
Entropy,

Ya Im not running any tweaks or mods, I agree I have never had this happen before a couple days ago, why I find it so odd. The ashmem issue however I have noticed for quite awhile but only via some logcats and it never lead to any critical issues so I let it be. Then looking at some of the kmsg I noticed the bit about vmallocation throwing out errors before the kernel panic. Ill get you a logcat and dmesg of the ashmem issue bc it seems to be a continuous error, from what I can tell so far its starting from a touch input event then unpinning and correcting itself consistently. Ill also include a writeup in the tar for you so I can give a better explanation with examples. Personally I think theres some definite problems with Samsungs code.

Thanks for taking a look.

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Over in the I9100 forums, one dev (knzo) was making outrageous claims that his kernel had features no one else did.

I exposed the truth - other kernels had the same features, some of them for longer than his existed.

If you see the hype about the "lionheart" governor in the I9100 forums:

Lionheart consists of a total of one patch that has any performance benefit.

What's funny is the devel managed to get everything deleted... (Edit: Nope, search is just slow, will add linkes later today)
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Good Job, Entropy512!:)
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
Whats the big deal with governors anyway? I've been involved with linux for a long, long time, but it seems that the android community has spawned more variations of different governors than any other branch.

Why? I don't see what any of these provide that can't already be done with the mainline governors as-is. If you browse through the various forums, I think I've seen 6-7 variations of conservative, and at least as many variations of ondemand. The actual impact of these variations is so tiny that, given user-space tweaks in the /proc filesystem, the amount of performance change or power savings would be well within a margin of error of any measuring technique.

Strangely, everyone seems to be ignoring the very tool provided in the linux kernel for all these exotic governors: the 'userspace' governor was developed to provide a way to allow any crazy scheme people wanted. In many ways, that (along with a userspace deamon) would be better than some of these far-flung things I'm seeing. 'userspace' also has the benifit of protecting the kernel from idiotic coding. It's (in theory) impossible for a userspace deamon to soft lock the kernel. (What many of us do with 'setcpu' and changing the governor parameters on various events is very similar to how userspace works.)

Yes, I have tweaked the governor in the kernel I'm working on for the 7+, but only to allow a wider range of parameters - not to change how it works or to add new governors (and I was even very hesitant to make that change.) I've flatly rejected all requests from people to add new governors. Unless someone can PROVE to me that it would provide an actual value, is 100% stable, and can't be done with a userspace deamon, it doesn't belong in the kernel.

So... what is it I'm missing?

Gary
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Marketing and placebo effect... I agree with you. Reducing the minimum polling interval of conservative gives it a MAJOR advantage, to the point where, if you add a bit of placebo-effect hype to get away from the artificial stigma against conservative, it comes out on top.

http://xdaforums.com/showpost.php?p=21761755&postcount=1037 - knzo's fraudulent claims against Lionheart

http://xdaforums.com/showpost.php?p=21781230&postcount=1105 - My initial analysis of his patch. He's up to some shady **** there, deleting all comments.

http://xdaforums.com/showpost.php?p=21820112&postcount=1261 - He later put a list of "patches" that were supposedly part of "lionheart" and made it the "unique and amazing" governor it is. 3 of those patches were 100% impossible to apply to any I9100/I777 kernel (already applied). 1 was not a patch against the Conservative governor. Many of the rest were not performance patches but code/maintainability cleanups - the improvements of which he threw out the door when he deleted all comments in the code to hide his origins. In the end, he has only one significant performance patch, and that's the conservative polling rate tuning patch from netarchy which I committed to this kernel back on October 6!

As to userspace - there's a possibility that the overhead of many of those will offset the benefits of the governor, so there's a possible valid point there. That's the one main justification for "smartass" and relatives - performing a screen-on limits change before dalvik wakes up and sends SetCPU a wakeup intent. I believe most of the benefits of this are eroded on faster CPUs anyway - they made sense on underpowered CPUs, but not on a CPU which is fairly fast even at 500 MHz and on a system design which takes 650 msec just to complete resume no matter what...
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I found one possible cause for the issues I've been seeing - in some source trees, there are flags in the serial port driver to tell the cpuidle driver when the GPS is in use. These aren't in the I9100 base (or even the I777 base... so that is why I'm leaning towards "probably something else). Funny thing is, Samsung did include MACH_C1 (SGS2) specific code in their Tab 7 plus source tree.

I'm testing an improved cpuidle driver now, that has MUCH better AFTR support.

Also on the list to look at when I have time

nizda's crash issues (weird that no one else is having them...)

The touchkey lights issue

shoman94 says autobacklight is far less useful since the update3 completed. If this bothers you, for now use manual brightness + the notification bar swipe trick
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
Also take a look at the 7.7 source tree... It's a bit later than the 7+ tree and contains some mainline patches (such as the one I PM'd you a day or two ago for cpu.c)

(different video and touchscreen, but same processor)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
That patch you sent me seems to depend on 2.6.36 - it won't apply to .35.x and it seems like things are architectured somewhat differently.

Know of anyone with a github repo of 7.7 sources? I'm lazy and would rather git clone than pull a tarball. :P (Guess I could hop over to the 7.7 forums...)

I'm expecting not much will be easily backportable - I am actually shocked the cpuidle code backported as easily as it did. (Of course, if I beat on it for a while it could blow up... That's why I'm not releasing it until it's been stable on my device until at least late Saturday.)
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
you tell me the reason for this code fragment (just the left shift of 0), and I'll tell you where a 7.7 repo is sitting:

#define AUTOSTOP_SHIFT 5

call_a_func(0 << AUTOSTOP_SHIFT) ;

(not my repo)

https://github.com/bedwa/P6800-Kernel
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
any observation so far on the improved battery life because of that?
[AT&T Samsung Galaxy S II SGH-I777] :
I'm so glad that we have Entropy because he's so knowledgeable and is actually doing this for us... and lately we have Gary here to help figure out the latest issues and is truley helping also.

Thank you both!
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
Sure, you say that now, but when I harass and abuse you, I get slapped with infractions. ;) Oh, and where is my "sarcastic diva" title?

I'm actually annoyed at Entropy right now. I really didn't want to do charger current changes on the 7+, but he managed to somehow make me curious enough to look at the code, and now I'm stuck with it. (Of course, I have to admit that playing in the kernel relieves stress for me...)
[AT&T Samsung Galaxy S II SGH-I777] JmPTaz09:
1/24 exp running nice and smooth, no issues, paired with Hyperdroid 6.0.8. Running at default settings, will see how battery goes.
[AT&T Samsung Galaxy S II SGH-I777] vladm7:
I'm pretty sure he does that cause it interests him and for fun... not for "us".

who are "we" for him after all? a bunch of virtual nicknames....

either way thanks for sharing your "fun" with us, Entropy :)
[AT&T Samsung Galaxy S II SGH-I777] :
Because he could just do it for him and dosent have to post it for US, that's why.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
No clue, I wouldn't expect it to be TOO huge - it mainly means we get to hit an intermediate idle state (AFTR) more often.

Before, we had two primary states, just plain "idle" and "LPA" where most of the CPU powers down. AFTR was an "alternate" mode that would get hit if the timing criteria for LPA was hit but not other criteria (basically whether or not certain peripherals were on). So AFTR would only get hit if LPA were blocked but the timing criteria for LPA were hit.

AFTR now gets hit when the target idle time is 1/4 that of LPA - meaning it gets hit more.

Unfortunately I got hit again with that stupid "drain from nowhere" regression that went in either 1/2/12 or 12/21/11. (Still trying to narrow it down) - Go figure I didn't get hit with it for a few days which is why I finally went ahead and released an update, then the bastard comes back to taunt me.

Hahah. I have major mixed feelings on charge detection override - One of your users stated a legit use case for it, but too many will abuse it and damage things.

Making iPad chargers detect as a valid charger - that should be almost 100% safe unless some 500 mA charger reports identically to an iPad - but an iPad would misdetect in that same situation.

As to left-shifting zero - Most likely someone's trying to fill in a bitmask or subfield in a register, even though left-shifting zero does nothing, reading "put zero in this offset" is easier than not having the code.
[AT&T Samsung Galaxy S II SGH-I777] lbohn:
Yep. Cycling the screen always restores the touchkey backlight for me.

Per your suggestion, I disabled auto-brightness. The backlight for my touchkeys dropped out today. My brightness is currently set to lowest level. I've attached a dmesg from the latest incident.

I am running UnNamed v2.2.1 with true connection mod. Currently I'm on Entropy's DD 1/24 standard kernel. No OC, UV. No BLN apps have ever been installed or used. My touchkey duration is set for "Always on".

The only reproducible step is turning on the phone using the power button. Sometimes the issue occurs after the screen has been off for the duration of the night; sometimes the issue occurs after the screen has been off for only a moment.

Hope that helps!

--L.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Ok, thanks for confirming some of the patches in 1/23,24 didn't fix it. (A small I2C tweak that missed the I9100 update cycle could have affected it).

Hopefully the dmesgs will be interesting - the other possibility is to just go and patch up to the EL29 codebase from the Epic 4G Touch - this may provide useful stuff for I777 and even I9100.
[AT&T Samsung Galaxy S II SGH-I777] dandrumheller:
I'll agree with Shoman94 on the reduced usefulness of autobrightness recently. I am currently on ICScrewD 2.0.1, initially with a couple of siyah's kernels, and now your DD 01/24/12. In the case of both kernels, autobrightness seems to adjust within a smaller range than it did in the past, and more of an issue to me, is that it does not go dim enough on the bottom end. The adjustment range may be just my perception, as it is often hard to tell exactly what it is doing in brighter envirionments - but I appears not to go below about 30% at the bottom. This just drives me nuts in a dark room...

I'm currently running mostly with auto brightness off and swiping to adjust, but there are some times when auto brightness is very helpful for me, so having it work better would be much appreciated. Also in this vein, JKay mod offers some options for tweaking the auto brightness range, but according to the app kernel support is required for use of most of these ranges. Is this something you would consider supporting in your kernel?

Thanks,

DD
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I would need documentation on what these interfaces are.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Swype installation got messed up

Hi Entropy,

After flashing version 1/24/2012 of your kernel using Mobile Odin Pro, somehow my Swype keyboard has gone all whacky. Its gestures are not working and my personal dictionary (of Swype keyboard) has wiped off.

Any idea what could have caused this?

Thanks!

Update: Not sure if the kernel update caused it or my uninstalling the Swype Installer app (not the Swype app itself). The latter seems more likely, but as I said, not sure. Everything else looks good.
[AT&T Samsung Galaxy S II SGH-I777] JmPTaz09:
Getting some great battery life on 1/24 exp. running Hyperdroid 6.0.8, absolutely no issues.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
99% certain it was removing Swype Installer.
[AT&T Samsung Galaxy S II SGH-I777] mkosmo:
Entropy,

I haven't seen this asked or answered on this thread, but I'm curious: Is there any reason you stopped tagging releases in your repo? I was looking at some of the commits to see what you're doing, but seeing release tags would certainly make for good baselines for comparisons.

Thanks for everything you do!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
laziness... :)

I tried to get into the habit of tagging but I failed.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
I am also noticing that. Did you figure out what's causing it?

I started seeing this wakelock after installing DD kernel.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Sure you didn't change anything else? Can't see how the kernel would cause a userland wakelock in most cases.

New upload - backport of the cpuidle driver from the Tab 7 Plus source code base.
[AT&T Samsung Galaxy S II SGH-I777] jazzboyrules:
Nope. Everything is the same. I was surprised to see another user facing the same issue in this thread and so I quoted him/her and reopened the question as I didn't find any solution to it anywhere. Well any ways, can you give any hints as to what areas I can investigate in?

Sent from my AT&T Samsung Galaxy S II
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
This (cpuidle backport) looks interesting. Any initial impressions on it?
[AT&T Samsung Galaxy S II SGH-I777] rav4kar:
Entropy, Thanks for new update!