[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Many people have mentioned it, and when asked for more details, without fail, every time in the past 3 weeks they did not provide additional debugging information, and in fact indicated that this problem was only a minor annoyance to them. From 12/12 until 12/21, debugging this was my priority. 12/21 would have shown up a LOT sooner if not for the wake lag complaints, which NO ONE provided useful debugging info on, I eventually gave up. I was unable to reproduce it myself, and NO ONE provided a useful dmesg, and when asked for further info, everyone who actually bothered to say anything indicated that this was a rare problem for them.

Being plugged in would make sense... Since it inhibits deep sleep.

You really claim that you were unaware I was looking for information and that I was being led to believe that this was not anything beyond an annoyance for anyone?

December 14:

[22:18:19] <Entropy512> gtg465x: were you ever able to reproduce that touchscreen issue yourself?
[22:18:29] <Entropy512> I have been completely unable to reproduce it
[22:18:37] <Entropy512> and so far only one dmesg that has nothing obvious
[22:18:38] <Misterjunky> speaking of speed, quadrant tells me my score is 4209
[22:18:53] <shoman94> uninstall quadrant
[22:18:59] <MikeyMike01> Yes
[22:19:12] <MikeyMike01> Or I'll beat you up
[22:19:37] <Entropy512> at least antutu breaks down the score by category
[22:19:47] <Misterjunky> gtg465x, where and what would I need to start modifiying to get rid of the text under dock icons?
[22:19:49] <shoman94> and very consistant
[22:19:53] <gtg465x> yeah entropy... it's not that obvious... the screen just doesn't respond for about half a second sometimes after it wakes up on your 1212 kernel
[22:20:06] <Entropy512> OK you were able to reproduce it yourself?
[22:20:10] <shoman94> antutu has been my choice for quite sometime
[22:20:12] <gtg465x> yeah
[22:20:13] <Entropy512> any chance of a dmesg?
[22:20:20] <Entropy512> I have NEVER seen it happen
[22:20:47] <Entropy512> I am wondering if it is a negative interaction between UCKK2 and the I9100 update3 sources
[22:21:02] <Entropy512> since no one in I9100-land complains of that particular touchscreen issue
[22:21:05] <shoman94> uckk6
[22:21:09] <Misterjunky> gtg465x, was just thinking.. is there a way I could simply replace the touchwiz apk with the one in UnNamed v1.3.2 ? (just like replacing the camera.apk for normal zoom?)
[22:21:13] <Entropy512> er yeah uckk6
[22:21:23] <gtg465x> i wouldn't call it a bug... don't think dmesg will help you
[22:21:55] <Entropy512> dmesg might catch some failed calibrations or something
[22:22:01] <gtg465x> maybe i9100 users just don't see it because they've always had it
[22:22:08] <Entropy512> the thing is other people say it improves touchscreen responsiveness
[22:22:13] <gtg465x> it does
[22:22:21] <shoman94> Misterjunky just use the stock uckk6 camera
[22:22:52] <Entropy512> so right now - considering the unlock issue is very minor and rare, I'm probably going to go ahead with update3. Hopefully I can figure out a way to get the best of both worlds
[22:23:05] <Entropy512> gtg465x: do you have a screen protector?
[22:23:22] <Misterjunky> I did shoman94 , that works great.. I was talking about removing the text underneath the dock icons, thought perhaps by replacing touchwiz apk from 1.3.2 ? would that work?
[22:23:45] <gtg465x> it's like it turns the screen on a split second before it's ready to accept input... whereas 1208 seems to take a split second longer to turn the screen on when pressing the power button, but as soon as it's on it's ready to go
[22:23:51] <gtg465x> no screen protector
[22:24:24] <Entropy512> common themes seem to be UCKK6 and no screen protector
[22:24:41] <Misterjunky> I use the ZAGG protector and after much testing, I could not tell any difference in screen sensitivity with or without it.
[22:24:52] <gtg465x> screen protector helps? weirdness
[22:25:10] <gtg465x> we aren't talking about screen sensitivity misterjunky
[22:25:20] <Misterjunky> sorry bout that :)
[22:25:53] <shoman94> how is having a screen protector gonna change how the screen turns on?
[22:26:52] <Entropy512> it may alter the touchscreen calibration cycle
[22:26:56] <gtg465x> Misterjunky> gtg465x, was just thinking.. is there a way I could simply replace the touchwiz apk with the one in UnNamed v1.3.2 ? (just like replacing the camera.apk for normal zoom?)
[22:26:59] <gtg465x> yeah you can do that

You were FULLY AWARE that I was looking for dmesgs, you were FULLY AWARE that I was under the impression that this was only a minor rare issue at best, and YOU DIDN'T SAY A DAMN THING.

A few days later:

[22:38:05] <shoman94> gtg465x I'm gonna lead him in here for you.
[22:38:27] <shoman94> that way he can have a direct chat with you
[22:38:29] <shoman94> :P
[22:39:05] <Hossy923> Entropy512: any known issues not posted (or posted that i might've missed :-P) with DD_12122011?
[22:39:53] <Entropy512> Some people have indicated that they have slight touchscreen responsiveness lag when unlocking from sleep
[22:40:02] <Entropy512> fairly minor thing
[22:40:20] <Entropy512> other than that... it's not nuclear-powered and the battery doesn't last forever

Another indication to you that I was under the impression that this only applied to unlocks from sleep and not phone calls, ANOTHER instance where you said NOTHING after the quoted conversation related to the issue.

A few days later...

[19:01:42] <Entropy512> jivy26: right now, the screen wake lag seems to be so rare and the benefits of improved touchscreen responsiveness are such that I'm not likely to revert the update3 change
[19:01:59] <Entropy512> I've seen it happen once, I think... it's so damn subtle I'm not even sure if it happened
[19:02:28] <jivy26> Gotcha, lmao you know the community they will find any small thing. Honestly, doesn't bother me.
[19:02:47] <Entropy512> Yeah, when gtg said he'd seen it but it was minor, I trusted his judgement
[19:03:21] <jivy26> yeah nothing major
[19:03:26] <Entropy512> there's a slight chance that when the rest of update3 is in things will change - there are some touchscreen constants in the platform code
[19:03:47] <jivy26> lately he's been busy eloping with his htc titan though
[19:06:27] <Entropy512> yeah... but he did file a useful report
[19:07:38] <Entropy512> rumor is that AT&T may have pulled KK6 for a while due to complaints of call quality and bluetooth issues
[19:07:42] <madLyfe> how do you guys get music to your sgs2?
[19:08:36] <FL7> usb cable
[19:08:58] <madLyfe> lol i mean where do you put it?
[19:09:28] <madLyfe> guess i could just use the kies crap or something..
[19:09:36] <Entropy512> can be pretty much anywhere and media scanner will pick it up (sometimes need to reboot...), I usually use /sdcard/media/music/
[19:09:50] <madLyfe> cool thanks
[19:11:35] <jivy26> madlyfe download rescan media from market
[19:11:43] <jivy26> to make it rescan if music is not showing up
[19:13:54] <Entropy512> and if that doesn't work, make sure you didn't accidentally stick a .nomedia file somewhere...
[19:14:05] <madLyfe> ok, did your ROM install an explorer?
[19:14:14] <Entropy512> afk
[19:29:02] <shoman94-mobile> GHz
[19:29:12] <-- xlr8shun (~xlr8shun@97.103.237.156) has quit (Ping timeout: 252 seconds)
[19:29:14] <shoman94-mobile> Ugh
[19:30:21] <shoman94-mobile> Entropy512: rumor is? Hear say? News article?

Yet again, you were CLEARLY aware that I was under the impression that this issue was at worst minor for anyone affected and was moving onwards, and again, you SAID NOTHING.

Now, three weeks after the 12/12 release you have the balls to come and be, "Y U NO FIX?" like so many XDA users, expecting me to pull a fix out of my ass for a problem I could not reproduce myself and could not get any information from people who could reproduce the problem? Seriously, I expect FAR more from someone who is a ROM developer. You say I have a bad attitude? You are the one who sat for three weeks affected by a bug and did NOTHING to help even though you were fully aware I was unable to reproduce it myself.

Here's a story: Back in the spring of this year, over in the Tilt2/TouchPro2 Android dev community, there was a small subset of users that had fairly rare hardware (An AUO paneltype). Things were more likely to be broken because of this. For example, camera support for their panel variant was far less stable than any other.

For a month or so, one developer focused exclusively on camera stability. There were multiple test releases, and camera functionality for most panel types was vastly improved. However, because the first test release didn't provide any obvious fixes, the AUO panel users didn't bother with any later releases, and the entire time not a single one of them provided any debugging data.

When the camera support effort was complete, every panel type except AUO had robust camera support. When the final version was released - all the AUO users whined that their camera was still broken, even though they didn't lift a finger to help the dev (who did not have an AUO panel) debug issues. The dev moved on to other stuff, and AUO panel users had to live without camera support for a few more months because the dev had changed priorities.

So - I'll take a look at the dmesgs, but because for three weeks no one bothered to indicate that this was anything but a minor annoyance for them, this is not a priority. I spent nine days from 12/12 to 12/21 feeling like stickman fighting the door trying to get debugging info from affected users, putting the effort to patch up to update3 WAY behind. (I'd probably have finished before the holidays if not for the wake lag complaints causing me to hold off for a bit.)

You had your chance to be the debugging priority - now my priorities lie elsewhere. Time permitting I'm going to look at the dmesgs and if there's anything obvious I'll try to fix it, but I really need to finish moving to update3. Maybe when it's fully implemented things will work better - if not I'll take another look at this specific issue once I finish moving to update3.

Thanks. I'll take a look when I have time.

Speaking of that - time for BEER! I need a drink.