yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I got about 4.5 hours of screen time after I first installed the latest build. This last battery cycle I got 2.5 hours.... And that's after lowering my highest cpu frequency voltage a tad. My use is the same and I'm in the same physical location as well. These may seem like a weird question but can lowering voltages too low cause odd problems like this? I don't know how else to explain it. I even turned touch boosters off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
Technically sure. Realistically no.

When I would under volt or over clock my cpu / memory and or video card if it was pushed too far it would produce errors. These errors would lower my benchmark score because essentially it has to do the same thing over and over.

If you cpu has to do the same thing multiple times it consumes more energy.

Will it reduce your battery like 45 percent? Nah.

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
I did a full wipe when I installed cm10.1 1/13. So that's not it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Don't assume that because you just did a full wipe that another is not needed. It's happened to me more than once. Sometimes flashes just don't flash 100% correctly. That's just the way it is.

On the other hand, there are quite a few problems with laginess still going around... seems like flu season or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Sad but true. I'm not sure how doing the same thing produces different results. That's just the definition of insanity, but it does work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
I wipe with every flash, sometimes 2 times. And when I mean FULL, I mean /system /data / factory reset cache and dalvik. Then go back to mount /system. I rarely have bad flashes, so I highly doubt that was the case. Plus I knew that this kernel had these issues before. I'm not knocking the kernel cause I truly love it, just stating that it has lag and I did troubleshoot some things before I commented.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Lag is not yet fixed. You're not crazy.

Be patient.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CYRAXDroid:
lol for cm10 to flash the kernel its the JB AOSP version ?

Cause im on cm10 which says its 4.2 and I notice on the op it has a 4.2 version not sure which one to use
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I didn't mean for all this to last 10 posts! I was just telling you what helped me out. It made my lag problems nowhere near as bad. Like I said the problem "is still there it's just not as bad for me". Do what you want. It's your phone. I was just trying to help you out a little!

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
CM10 is 4.1.2 based and CM10.1 is android version 4.2.

I suggest you check Settings-->About-->Android version and make sure what version your are running and choose the kernel accordingly..

Edit: Seems like u got ur answer from the CM thread :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alexander2013:
Hey guys, if you recall I posted here before regarding my troubles with this kernel.

Anyways, I am running 4.1.1 (A stock Samsung Pre-rooted ROM for Rogers)

I installed this kernel, and when I do fix permissions/dalvik/cache it would boot to the lockscreen and then automatically reboot, rendering me unable to get into Android.

Here's what I did, I flashed the kernel, and DID NOT wipe cache's/fix permissions. Now I can use my phone normally and KTweaker still appears with me being able to modify my CPU voltages and OC my phone.

Will not wiping cache/fixing permissions be of harm? This is currently the only work around that I can find at this time.

Okay so I am going to run a test and try to fix permissions via ROM manager. Then if this works I will narrow it down to it being something with the dalvik cache or something.

Edit: booting....

Annnnndddd bootloop. Okay, so I can successfully narrow it down to it being something with permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I wouldn't use rom manager for anything other than updating your recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
I wouldn't use rom manager :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alexander2013:
I used Clockworkmod Recovery on numerous occasions. This is probably my 5th time restoring my phone. I have the same outcome each and every time I do this, no matter what tool I use to fix permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
I said rom manager, not cwm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
Maybe try using twrp also make sure you have the correct version of the kernel for the rom you are on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
For people that use CyanDelta or want to easily delete mpdecision and fix permissions, I attached a zip that is cwm-flashable that will delete /system/bin/mpdecision and automatically fix permissions. This is extremely helpful if you're using CyanDelta and you have this kernel set to auto-flash after installing the ROM. Just add this zip to flash after it.

EDIT: Removed logging in fix_permissions.sh. Calls /sbin/busybox instead of just busybox.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
It sounds like you might be flashing thr wrong zip.. What is the exact filename of the kernel zip you are flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Alexander2013:
This is the exact kernel that I am downloading for my device: http://www.mediafire.com/?etk37v5590266cv

This is the pre-rooted ROM I am using for my phone: http://xdaforums.com/showthread.php?t=1739426 (the jellybean 4.1.1 Rogers one)

Pretty sure everything should be working together from what was described.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
That's the exact same rom and kernel om using (att).. Not sure what's going on then :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
The difference is that he's using a Rogers ROM.

Alex, try the AT&T ROM.

You may need to manually add the Rogers APN. Otherwise, they should be nearly identical.

Better yet, go 4.2 AOKP. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I agree, I'd go for paranoidKangdroid, or pac man, our slim, or anything aosp based and not touch wiz based. Trust me it'll be much better.

Edit: not trying to derail the thread and advertise other things, just trying to give advice to help a fellow XDAer's experience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I am seeing flicker with this kernel as well. I have tried 3-4 different ROMS, including task's, CM10.1 nightlies, illusion, jellybro, etc... Every one of them seems to work fine until I flash this kernel, then I start to see flicker again. The behavior is the same on both the 1/1 build and the latest 1/10. I tried stock voltage and governer settings, disabling overlays, build.prop tweaks and nothing seems to fix it. Flashing lean kernel makes the problem go away every time. I have done many, many full wipes and the result is always the same.

The flicker is not full screen, but localized to items on screen. If I view my notifications screen and just let it sit there, the icons will randomly go crazy, get scrambled and sometimes disappear completely. Loading animations, like the one in tapatalk look strange as well. The square box around the round animation flickers in and out of view. Rotating my screen from portrait to landscape also temporarily distorts everything and only a small portion of the screen is visible for a few seconds.

Is anyone else seeing anything like this?

The first screenshot is what my screen looks like immediately after rotating. 2nd is the scrambled notification screen icons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yes. I too am having screen flicker problems with this kernel. I haven't had anything disappear or anything like that but I am getting some flickering. Ktoonsez is pretty good about updating his kernel. I think it's been kind of a pain in the ass since he started working on 4.2. I'm sure he'll have another update for us pretty soon that will fix the flickering problem. Like I said, he's usually on top of fixing stuff like that for us. He might have been busy with other things the past few days.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I just flashed Task's 1/15 build and KT 1/10 and everything is perfect. Did you guys fix permissions AFTER flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yes. I fixed permissions. Idk about the other guy. I'm on CM 10.1.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I always fix permissions after flashing a new kernel. I haven't tried Task's 1/15 build yet, but after trying 4 different ROM's, each with a full wipe and clean install, the problem comes back every time I flash this kernel and goes away as soon as I switch to LK.

1weener, Yes that is Tarrytown, NY.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Not all devices are created equal. This is known.

Your particular device can't handle this kernel. Get a new phone, or deal with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
Great battery life so far ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] deserted1:
I've noticed since the last two versions my battery meter is not updating anymore. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vashht:
I noticed my performance goes down if I keep running it over and over, could be a heat related thing or it could just be really random, mine was going down to 6500 but now I've tried it a few times leaving time between each run and I get around 7300-7500. In the end my phone is running really smoothly so I don't really care how the benchmark behaves, I wouldn't worry about your benchmark scores unless your phone also is feeling slower in real use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegandroid:
oh my god.... i have never been so thankful for a kernel in my life.... you are a GOD amongst men.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fn1046:
Wow great kernel! Thanks so much! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Question.. as of 7/10, is there voltage setting in the kernel? I am much more interested in undervolting than OC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ghost77:
Please make A version without forced over clock, setcpu is not reliable I still get occasional high jump to 1900~ and I don't want that.

Other than that it's great kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] F1reEng1neRed:
http://xdaforums.com/showpost.php?p=28548801&postcount=748
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxf250:
He did say a few pages back that this would be done soon. So now OC will be optional, but capable, in the

next release or so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
haha OMG this would have been sufficient;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
Not really. How can u even tell the screen time from that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Not sure why but I'm getting high drain with Android system. It's been at 60% all day so I switched back to the 7.8 build and it's still the same. Anyone else experiencing this?

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamesbra:
check for wake locks in better battery stats (available on xda if you don't have it already) specifically kernal and partial wakelocks. From there it should be easier for you to pin down the culprit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I did that but didn't see anything that jumped out. Everything is under 7% or lower.

My phone has been in deep sleep all day today.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Xdenwarrior:
AMEN to that!!!

FM radio is the only thing that keeps me coming back to symbian from time to time :(

Fantastic Work to the Author!!! :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I have spoken with him and it is in the queue of things I want to add
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamesbra:
your battery life seems pretty good. Maybe android system is using the highest percentage of battery because the other big drainers like screen, cell radio etc aren't being used. Were you in a good service area the whole time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I had the same exact issue when I had ICS DOMINATION installed. I revert the theme back to stock and it went away.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I'm not convinced. Full wipe. Flash 1/15 (follow all instructions to the tee). Make sure everything is set up and running perfectly like it should with the underwear kernel. Flash KT 1/10. Wipe Cache/Davlik. Fix Permissions. Delete mpdecision. Open ktweaker and switch to ktoonservative.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
I think what he's trying to say is don't keep your hopes up for having this issue resolved..no other users seem to be experiencing flickering related specifically to this kernel. Though you've done an excellent job isolating it to this kernel, you seem to be the only person having this happen.

Have you had any luck with previous builds?

EDIT:

As far as mpdecision, I think you're supposed to do that after switching to ktoonservative, and reboot after it's deleted. But I'm not sure if that's even relevant here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I understand that all devices are not created equal, and I'm only here to report on the issue that I'm having to the best of my ability in order to help the further development of this kernel. I'm not sure why you are jumping all over me for reporting this. I did every possible thing I could to ensure that the problems were related directly to the kernel before coming here to post.

Telling me to deal with it doesn't help anyone, and until ktoonsez tells me himself to get a new phone or deal with it, I will continue to post about issues that I find. Maybe someone else will see my screenshots and report that they are having similar issues. Or maybe it truly is an isolated problem with my device, but how am I supposed to know that without reporting my issues here first?

---------- Post added at 05:09 PM ---------- Previous post was at 05:02 PM ----------

I have tried going back as far as the 12/29 build, and the problem is still there. I will give task's latest a try later tonight with another full wipe and see what happens.

I don't recall exactly which version it was, but I was using this kernel at one point without any of these problems. I was also one of the few not experiencing flicker when others were reporting it in earlier 4.2.1 releases. While it seems to have been fixed for everyone else, I am not experiencing it for the first time. I'll continue trying new things until I find a combination that I'm happy with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
No...You're wrong. I too said that I was having flickering problems with this kernel. I am dealing with it for now as I love Ktoonsez's kernels, but there is definitely something going on with it! If I revert back to the 12/22 CM 10.1 build & the 1/10 kernel, I do not have this problem, & the problem doesn't exist for me on the 12/16 CM 10.1 build with the CM kernel. Just letting people know.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
Same here. It doesn't happen often, but when it does happen it makes me glad I'm not epileptic.

Herp derp SGS3 Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I just flashed task's 1/15 build and then the kernel again and things seem to be stable so far.

I followed the exact same procedure that I did the last 6 times I flashed, so I'm not sure if there is something specific in the 1/15 build that fixed things for me. I was even able to load my modified ktweaker settings with underclocking and undervolting and things still seem to be running fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yeah, it's only every once in a while for me too. When it happens, it's not really that bad & it usually goes away pretty quick, for me anyway. That's why I haven't changed kernels or anything. Maybe next update will fix it for me.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bidi1985:
Can this work on miui?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I would think that the AOSP version would work for you, but I do not have any experience with miui. I would say, make a backup and give it a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stevehkim:
Miui yes. Use aosp version. And yes i get screen tearing here and there but nothing crazy i cant deal with. Love the kernel too much to even care. Im sure things will get better. 4.2.1 is still fairly new for us sgs3 users.

ROOTBOX Charged JB 4.2.1 fueled by Ktoonez 747 octaned kernel SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Small world. I grew up in Elmsford, went to Sleepy Hollow... a long time ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
So I know when we flash a kernel we need to give it some time to settle in before we can pass any judgement on battery life and such. I assume the same hold true if we are just changing governors and I/O's?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Have it go throught a full cycle first to get the right reading.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Cool thanks. Been running 4.1.2 using ondemand/cfq for awhile. Just trying out ktoonservative/noop. Oh yeah and I have renamed mpdecision.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I installed this on my ROM and I can see the options and stuff under power management, but I never got the KTweaker app. Should I just try to reinstall, or...?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

KTweaker should install in your app drawer. If it's not there, I'd try a reflash, being sure to wipe cache/dalvik and fixing permissions immediately after.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yeah, that's what Im saying. It's not there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anudist:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Are you looking under all apps, or just downloaded? It won't be under downloaded only.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I've looked through the entire app drawer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Re-flash dude

Sent from the Dank Device, aka my GSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Been getting random reboots with ktoonservative governor. No uving or anything like that done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Have you deleted /system/bin/mpdecision? Or if on touchwiz, /system/bin/qosmgr and /system/bin/gsiff_daemon? If that has already been done, what rom and kernel version are you running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aaroncal:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

I am on touch wiz and have always had random reboots especially running ktoonzservative gov. But have only renamed qosmgr do you what does the other file do and would it help with reboots. I have been using csrom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Actually, the gsiff_daemon one I think only fixes some issues with battery drain in certain cases, I don't have a lot of experience on touchwiz, as I switched to AOKP soon after I first started using this kernel. If you could post the file /proc/last_kmsg from after the reboot happens, ktoonsez might be able to help, but I don't know if I ever ran with that governor while I had touchwiz, so I really have no other ideas.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CoogiMane1996:
will this work with t-mobile>?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

T-Mobile has the same kernel in your section bro :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android2.0:
overheating while charging

hey guys

would this kernel remove the overheating factor while charging?? my gf just got the s3 and it over heats like crazy when charging but she doesnt want a custom rom cause she likes touchwiz features.

just wondering any help would be awesome thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Yes, and the stock kernel is crappy imo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

As long as it isn't crashing, it's fine. I've used KT's kernel since I had my phone and it maxes at 140°F at the stock clock speed while charging and under heavy use. It's built to take it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

I've dropped my phone and cracked the screen. Whilst replacing it, I was surprised to find out that the CPU actually has somewhat of a heatsink. Yes, it may not be all that spectacular looking, but obviously Samsung knew what they were doing. So the person above who said the phone is built to take it is correct. Also I know what problem you were having I had that too. And yea this kernel seems to have fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

jeezz..that is hottt..i have had my phone at hottest around 105-110°f while on the charge..good to know the phone will handle much higher temps..still would have thought things would start melting at that hot of temps lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Seriously... if your GF likes TW features... this kernel might help only minimally. (JK)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Not sure if I agree with that.. The ONLY people that ever have problems are running cooked roms :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android2.0:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN & ICS][1/10/2013] KT747 - LJ7 - KTweaker

Thanks so much for the info guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] te_quiero_forever_girl:
if I wanna go back to the stock kernel should I just reflash the rom ? I'm on CM10.1 btw. Thanks in advance guys