yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
I think he's made it very clear in various posts over the past dozen or so pages that he has attempted to reproduce it and hasn't been able to.

You might be surprised to learn how similar this phone is to a modern car. However, the point of that wasn't and isn't to relate a car to a phone, but to relate the reporting of a problem. I guess you kind of missed that.

That version of the request was made around mid-Dec when the problem first came up. As time has gone on and people have continued to complain about the issue without any willingness to actually help solve it, the tone has turned more negative.

Good thing. If I was in his shoes, I'd be more direct and tell you that if you didn't like it and are too lazy to help fix it, to not use it. Instead, I'm trying to give you an alternative perspective of WHY the tone of the dmesg request has gone from pleasent to short and WHY the information is needed. However, it's apparently in your nature to be a prick, as even my attempt at helping you to understand has resulted in rudeness.
[AT&T Samsung Galaxy S II SGH-I777] kytrauma:
Wow what happened to all the love?
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Here are 2 dmesg's..... They are name accordingly. I can tell you that being plugged in makes it more responsive. Not sure if that matters. The issue also is not the wake speed of the LCD... but the time it takes from when the screen wakses and touching it does something.
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Maybe so but I'm not gonna read 50 pages when something didn't show up for me in search.

I didn't miss anything.... I explained where I noticed the issue and what I was doing.

Also... they aren't similar at all..... sorry

This didn't pertain to me. It's not very productive to treat everyone a certain way just because a few have not gone the extra mile for you. Treat as you are treated..... hence my aggressiveness with you.

Here we go again... More name calling....

Laziness is not the issue but communication. You want help... asking is usually a good request. I've never dmesg'd before and never had to help debug a kernel issue. Am I suppose to be a mind reader? Prick? More name calling... really? Grow up man.

---------- Post added at 02:36 AM ---------- Previous post was at 02:34 AM ----------

I'm sorry but I just don't like bad attitudes.

I'll stop though....
[AT&T Samsung Galaxy S II SGH-I777] :
Whoa, there is just way too much manly love in this thread.

OK, now that Shoman has graciously given two dmesg's wrapped up nicely in a .zip, hopefully Entropy can see something in there that might point to a clue. Otherwise, we will just have to wait for Entropy to finish with migrating the updates... and with all the Holidays and such, Im not expecting that to be his top priority, so just wait it out guys. Hes giving us this nice gift... dont kick a horse in the mouth.

And I see that Entropy edited his post 15 minutes after the original message... damn, I wanted to read what he really thought. :D
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
Trust me when I say I wanna help... I use his kernel for a reason... I just don't tolerate disrespect.

PS: His message didn't change much... The edit didn't help in any way....
[AT&T Samsung Galaxy S II SGH-I777] MikeyMike01:
[youtube]GGl_JgKLt8k[/youtube]
[AT&T Samsung Galaxy S II SGH-I777] garyd9:
It's all good. I'm always "aggressive" with those I love. ;)
[AT&T Samsung Galaxy S II SGH-I777] dandrumheller:
Guilty as charged

I'm one of the guys who complained, promised logs, and then never delivered. At any rate, here are 3 dmesg pulls under slightly differing conditions, along with some notes as to what the specifics of those conditions were. Hope it helps...I don't have a clue how to interpret them...
[AT&T Samsung Galaxy S II SGH-I777] shoman94:
To be honest I was never fully into your conversation about it as it did not effect me. I never even loaded 12/12 on my phone nor use it on the Rom because I saw some people say something about it. Now I loaded your 12/22 two days after you released and used it through the holidays. So I had a few days to fiddle and be annoyed by it that I went back to 12/08 and it was gone.

It was my fault I didn't read the OP well enough to see that you ask for dmesg's etc... for errors in general.

Maybe I over reacted on you and for that I'm sorry... but I don't take kindly to bantering that is not in good fun..... My response wasn't aggressive until you edited yours calling me a nit picker. So my friend I'm hear to help and I have no love lost for you and your work. I want what I hope you and everyone wants. Making this device the best that it can be.

Man-o-man that post of yours took alot of work..... I see why you need a beer... :D
[AT&T Samsung Galaxy S II SGH-I777] autonomous-inc:
Entropy, thanks for all your hard work bro. You're a hard working bastard that has really made the I777 community great, and I'm not being an ass kisser here, just saying it like it is - without your work our kernel choices would be limited to siyah and as far as many ROM developers are concerned, stock. I've played with them all, and yours is the damn best.

Let this stuff slide, and keep dragging this community (whiners and helpful members) towards the international version. This "lockscreen bug" is too small for everyone to get their panties in a wad over, especially considering the work you've done to make our phones faster, more responsive, and overall, better.
[AT&T Samsung Galaxy S II SGH-I777] dhostetter:
I have to agree. My phone has never run so smooth.

GREAT JOB!
[AT&T Samsung Galaxy S II SGH-I777] Jonnyredcorn:
I posted this in the UnNamed thread as well, as I was not sure if this is a kernel or ROM issue.

So I just today for the first time noticed the AOS bug I believe. It is currently at 69%, and is usually around 17%. I am running unnamed 2.2.1 & DD 12/08...I've never seen it before, and thought it was supposed to be fixed with 2.3.6. Is this still a known issue, and if so, is there a fix? I remember seeing that entropys 12/12_exp hid the AOS bug, but not sure if I want to flash that.
[AT&T Samsung Galaxy S II SGH-I777] :
Depends on how you're using your phone. Remember, your phone is splitting its "100%" usage to what is using resources... so if you havent used your phone much and there is very little screen time, then AOS is going to take up the brunt of that 100% that is being used... even if your battery is still awesome. If you unplug your phone for 5 minutes and your battery has dropped to 99% but something has been using your phone for 100% of those 5 minutes. If you had your screen on the whole time, its most likely going to be your display that accounts for most of that 100%... if you have not had your screen on, then AOS takes the blame for using up all the resources that have been used in those 5 minutes. It may not be acting up or malfunctioning at all, but something has to be blamed for taking juice.

So to find out more, we need info like how long your phone has been on, and what all your numbers are. A lot of people are posting screenshots if their battery usage and graphs. Thats a great way to tell.
[AT&T Samsung Galaxy S II SGH-I777] Jonnyredcorn:
I thought about that as I've been thinking about it a lot since it has been bugging me, and you're absolutely right. I have hardly used my phone at all today because I have been working on my laptop all morning trying to get it running(had to reformat). The thing that bugged me though, was that my battery was down to like 66%, and if I hadn't used it all morning it should not have dropped that fast...so something was going on because AOS also said it was going for like 1 1/2 hours or something like that...it may have even said 2. I'm gonna charge to 100% and reboot and see what happens.
[AT&T Samsung Galaxy S II SGH-I777] :
Dont worry about it, a lot of people dont really think about it that way. I think it explains half of the " Y MAH AOS BUG AL BIG?" threads. The other half have a lagitiment issue that needs looking into, like this part vv

If you have not really used your phone and it dropped to 66% and AOS says its been accounted for 1.2/2 hours then there is a problem. It could be a rogue app that wouldnt let go of the internet and continued to use data (Facebook, Skype, Twitter, Gtalk are known for doing that) or just kept the phone awake and never allowing it to sleep (keeping the phone constantly away but with the screen off). Sometimes, or maybe most of the time, a reboot will fix issues like these.

Its not a secret taht we no doubt have an issue somewhere where our phones do this (whether it being a rogue app or something else) from time to time and it can be a bit aggravating. Like your case, you didnt use your phone and when you go to use it, you find that half of your battery is already drained. If you forgot your charger or were not around a power source, you could be screwed by not having a phone to use in a couple of hours.

Anyways, its obvious my third cup of coffee is kicking in because Im rambling, so I hope that a reboot fixes your issue and wait to hear you report back.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Actually, 2.3.6 may have CAUSED the first Android OS "bug" that is actually a bug and not a rogue app.

See my Known Battery Drainers thread. Also read the threads on UCKK6 battery drain - Unnamed 2.x is UCKK6-based.

Rebooting will often fix the issue for a while.
[AT&T Samsung Galaxy S II SGH-I777] brent8577:
it is either not a problem, or one of your apps is being bad.

edit: oh! look at that! there was another page! ok I'm going back to sleep. wake me up next year.
[AT&T Samsung Galaxy S II SGH-I777] smknutson:
Rebooting once or twice daily is something I have always preached. It doesn't take but two minutes.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
That's just bandaiding around a problem.

Plus this problem, when it occurs, can drain quite a bit of battery before you notice and reboot.
[AT&T Samsung Galaxy S II SGH-I777] Jonnyredcorn:
My concern exactly. I charged to 100% and rebooted and it seems to be fixed. This has only happened a few times that something kept the phone awake and drained my battery. Usually its Facebook.chat session or whatever, indicating Facebook went rouge. This time however BBS didn't show anything.
[AT&T Samsung Galaxy S II SGH-I777] \/icious:
This is the first time ive heard about this issue but i reboot regularly and have had great battery life. Im going to have to try and not reboot for a while and see if i need to and can iron out any issues. Thanks guys.
[AT&T Samsung Galaxy S II SGH-I777] Emil9727:
Voodoo Louder

Hey Entropy thanks for the awesome work you continue to do. I had a (hopefully small) request for your kernel. Supercurio recently came out with his Voodoo Louder app for our phones. I tried different ROMs but it didnt work until I flashed the Siyah kernel. Nothing against that kernel but I have been a fan of yours since the beginning. I was wondering if you could enable it in your kernel :) Thanks again.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
That's on my list now that it has matured more and has documentation - once I finish the I9100 update3 patching.

I have a test build running on my phone, going to beat on it a bit more before building and releasing. A LOT changed (all the remaining I9100 update3 patches, reverted the touchscreen stuff because of the wake lag issue AND because siyahkernel also reverted - I think I figured out how to get the sensitivity improvements. That said, I always feel dirty including AT&T hacks...) so I'm going to beat on it a few days before releasing.
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
If you need anyone else to help "beat on it" , I'm game :)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Probably after one day more of beating on it I'll push sources to github - you can build and test then. ;)

I've moved it from a test branch to my main branches - however once I push I can't rework the branches.

As to Voodoo LOUDER - After looking further, there are two module parameters (vol_hpgain_addr and vol_hpsp_addr) that are completely undocumented, and no way to properly test the functionality without buying the app (a basic compatibility check is NOT a proper test). Since I can't properly test this module without spending money ON TOP of the time needed to rework my build scripts to pull in the module, I'm not touching it until there is documentation on these module parameters and a way to release-test the module manually.
[AT&T Samsung Galaxy S II SGH-I777] systoxity:
Hola, been using this Kernel since the first few Weeks it was released. Thanks for the great job entropy.

I recently updated my ROM from unnamed 1.2 to 2.2.1 and have been trying to nail down some battery drain issues since the switch. Anyhow i'm looking at my better battery stats and it states that I have	a kernel wake lock of 7 hours from "audio out lock". This seams like it may be the culprit. Does anyone here know what's going on? I apologize ahead of time for my ignorance our if the question has already been addressed.
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
Nice, I'll be on the lookout for it :)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Honestly, I don't know - I'm not even sure why it appears as a kernel wakelock!

It isn't even held by the kernel - it's held by one of the low-level platform drivers - http://gitorious.org/android-on-fre...e10bd92a9fc9aa7b174246/AudioStreamOutALSA.cpp is one example for a different device.

It seems to be related to audio playback.

My guess is that it appears as a kernel wakelock and not as a userland wakelock because it's held by fairly low level (native code, not Java) libraries in userland. It looks like this would be caused by an app playing back audio and then not closing the audio interface properly.
[AT&T Samsung Galaxy S II SGH-I777] Nizda1:
Entropy

Since were on the topic of sound I've been noticing a constant flooding of Yamaha media ctrl errors in catlog. Is this anything I should look into? I don't notice any sound problems per se but just wanted your opinion.

Thank

Sent from my SAMSUNG-SGH-I777
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Probably fine - in dmesg or logcat? Logcats tend to be VERY chatty. An overly chatty dmesg is interesting as I've never seen much yamaha-related in dmesg.
[AT&T Samsung Galaxy S II SGH-I777] systoxity:
thanks for the quick reply, I use Pandora very often, I'll try closing it all the way out when i'm done with it and see if the issue persists.
[AT&T Samsung Galaxy S II SGH-I777] Emil9727:
I bought the app so if you are interested I can test it for you.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
In that case I may consider it. I still don't like that he expects kernel developers to pay for his app in order to make HIM money, which is what he is doing by providing this without a test suite.
[AT&T Samsung Galaxy S II SGH-I777] :
Looking forward to your 1212 update. :D
[AT&T Samsung Galaxy S II SGH-I777] kytrauma:
+1 for testing if you need it. I installed siyahs latest to test this app and it does make a big difference. But I won't give up great battery life and stability to run this app.

Knowing supercurio tho he would prob. Get you a free copy being that you are the biggest kernel Dec in our forum if you just asked.
[AT&T Samsung Galaxy S II SGH-I777] jdbeitz:
Entropy,

Are going going to add the parameters needed for LOUDER by supercurio? They are listed in the market description.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
You realize this has been discussed repeatedly over the past three pages?

Not until he provides a functional (not just interface) test suite/demo. I don't want to claim support and then have people coming back and complaining they spent money and it didn't actually work. And even then - time permitting, there's a whole ton of other stuff I need to start working on.

There's also the fact that he responds to questions about his code by insulting kernel developers and telling them they should learn to read C - when kernel developers that actually read C rather than blindly compiling in code are the only ones who will actually have questions.

Last time the Infuse community had questions stemming from code review of the Infuse implementation of Voodoo Sound, it took over 2 months to get an answer.
[AT&T Samsung Galaxy S II SGH-I777] :
We could compromise. You put a big disclaimer in the OP about the sound and how your not responsible and it may not work yada yada yada, and as soon as someone complains or says it doesn't work ill insta-ban them for you. :D

Nah, I understand why you choose to play it safe with this one. Supporting something that has no documentation or help from the creator can be extremely difficult and stressfull because you will be the one that gets all the questions and blame if it doesn't work right. I can't blame you in the least.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I'll consider this.

Edit: Sources pushed to github. I'll do the binary release in a day or two if things continue to be stable.

Edit 2: Supercurio had the balls to insult me and imply that I'm a patch-o-matic kernel developer who doesn't read C code, while the whole reason I had questions and doubts is because unlike other kernel developers who blindly compiled his module without thinking, I actually read the code and found things that were odd. Then he claims that *I* am being aggressive and he feels like a punching bag when I call him out on insulting me like that.

The last time I approached him with a question about code (Voodoo Sound for the Infuse) he accused me of being a critic about code cosmetics, and when I rephrased my question to be clearer (I assumed a language barrier problem at this point, I was wrong), he ignored me so the Infuse community had code in an unknown state until after October 25 (we couldn't get anything out of him until he started testing his screen tuning app)

https://github.com/project-voodoo/l...3d96b6baacd649b419d6b787cc64e89c428a38f#L6R11 - See for yourself, I was not aggressive, but he accused me of nitpicking his code cosmetics and then blew me off when I rephrased my question more specifically.

He's an ass, and I will not support his financial gain when he immediately goes to insult anyone who dares question his code, then claims that HE is the one being a "punching bag" when he is called out on his insults.
[AT&T Samsung Galaxy S II SGH-I777] jdbeitz:
I know I know. I was just poking some fun at you man. I had a little talk with supercurio this morning about it. Louder, to me isn't a big deal. I switched kernels to use it but I'd rather have your kernel with awesome support and performance :)

Let me know if you need any testers as well dude and I'll give you a hand! Keep up the work and I can't wait for the next release!

Also, there's a reason I went from am I fuse to my i777. I'm following one of the best devs in my opinion :) thanks dude.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
New version posted in OP, changelog updated. The road to I9100 update3 is complete except for touchscreen changes - The touchscreen stuff in arch/arm/mach-s5pv310 wouldn't even compile for AT&T targets, and reverting was easier than diddling with it considering the regressions indicated by some users with the update3 sources.

This will unfortunately lead to a loss of touchscreen responsiveness, however the following MIGHT get you the best of both worlds:

echo "55" > /sys/devices/virtual/sec/sec_touchscreen

Default is 70, Siyah default is 60, I9100 update3 seemed to be 50? Lower is more sensitive. Make it too low and you might find your screen "jammed" so be careful.

To have this done on boot, take one of the init.d script examples in my init.d thread (like the governor script) and modify it with the code above
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Flashing now, thanks again for all your hard work! :)
[AT&T Samsung Galaxy S II SGH-I777] TechSilver13:
If he is being a **** to the best dev on this board I don't want his crap anyway. I wouldn't support a damn thing with his name on it. We appreciate everything you've done for us Entropy!
[AT&T Samsung Galaxy S II SGH-I777] AcmeWidgets:
I'm on Siyah's latest and Unnamed's latest.

If it means anything, From this thread I installed The "voodoo louder" from Curio. It won't run. My phone freezes, then I get the force close message, then the phone reboots by itself.

So much for his condescending attitude! He sounds like a drama queen.
[AT&T Samsung Galaxy S II SGH-I777] jdbeitz:
The problem is supercurio is an amazing dev and knows his sh1t. I've loved, downloaded, and bought every one of his apps. Now lets all get along :)

Excited for the new release!
[AT&T Samsung Galaxy S II SGH-I777] iteam:
Low Auto screen brightness

Hey all, just thought I'd report I updated from Entopy's 12-21-2011 to 1-2-2012 and the wake lock delay was gone, but I did notice a bit more screen lag. Also the deal breaker for me was that I found auto screen brigtness way to low for my viewing. Running rooted stock 2.3.5 I-777 reverted back to 12-21-2011 for the time being as it's all good there. Just have the wakelock delay as stated...
[AT&T Samsung Galaxy S II SGH-I777] eep2378:
If you are using the latest jkay mod it allows for a brighter auto brightness profile.
[AT&T Samsung Galaxy S II SGH-I777] iteam:
Sweet. I'd love to try it. Can I install it on my stock rooted rom? If so, would u possibly have a link? ;)
[AT&T Samsung Galaxy S II SGH-I777] LiLChris06:
Played a few games, messed with settings, tried a few apps, tethered by USB and Wifi, rebooted, and other misc things and everything seems to be working perfectly fine.

Waking up the phone seems snappier, or its a placebo effect not sure yet. :p
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Supercurio is quite smart, I give him that. However, whenever you dare ask a question of him, even a basic "what is thise code doing?" his response is to insult you, and as a result, my conclusion is that he's an egotistical prima donna.

Yes, I know I've been known to get pushed over the edge a few times - but when he insults the only person who actually bothered to read his code by telling them they should learn to read C, that's going too far - especially for someone whom he is asking for help making money. The saying goes, "don't bite the hand that feeds you" - and he's done that. Maybe I started off a bit more aggressively this time than last - but he's asking for us to spend time to help make HIM money, when in my case, he'd already been an ass to me once. (See the linked github convo a page or two ago for the history on that - Infuse users didn't get a proper answer from him until some time after October 25, and as you can see there, he clearly moved to insults rapidly, and I, at most, tried to rephrase my question more clearly due to a potential language barrier, after which he basically blew me off.) He's already been proven wrong regarding the sufficiency of his compat checks by Cyanogenmod users - a number of them are getting false positive compatibility reports from his app, followed by the app not actually doing anything.

I'll take a look at the autobrightness stuff. Honestly, I don't use it - it's one of the first things I disable to improve battery life. (Since we can adjust brightness just by swiping the notification bar, why trust autobl?) In my experience it has always been WAY too bright for me.

If it's actually dimmer, then that would make it something I might actually try again... But maybe it can be configured like it is on CM7. I'll need to poke at it.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
I'll take a look at that in a day or two... I know that on my device, resume always took 650 msec to finish late resume processing, on some I9100 dmesgs it varied a bit, and was usually a little less, so this might be slightly improved. (Not less than 500 msec though)