yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Thanks for the update, runs alot better now...and did you check out that link I sent to your PM? didn't know if you did that or knew about it or not, you can practically build a device OS with all that info haha which incase anyone else is curious to/and or wants to help develop for the device add this to your SDK and or knowledge, since I work mostly with computers, the hardware always plays an important role in performance and tuning, https://developer.qualcomm.com/blog/snapdragon-sdk-android-public-preview
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sorry, nothing to really look into. Its either a hardware issue or a bad flash. I would just format the card, ur talking about the external right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
I can confirm Bell for sure, but I can't imagine that all variants with the same hardware won't work.

The only real difference are slight software tweaks (or downgrades) by AT&T, like no tethering, or ability to turn off LTE.

I have seen Rogers and Telus confirmed in this thread also, no word on Sasktel, but see above...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Yea the external. I was just making sure it doesn't do it to everybody because of the kernel.

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lilbigdude1:
Now that your here...it'll be time for me to jump ship over to here soon......:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PhantomHacker:
Hi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
I love waking up to new better things. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
@ktoonsez great job sir! I was looking at the app 2ndcore and see that both cores are always on when on stock, one will go offline when not in use. With your tweaks, will the battery perform the same?

SGS3 awaiting some dev love
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkeaver:
This is happening with me as well. I don't think its a bad flash and I really don't want to reformat my SD. Its working fine with stock kernel. After flashing yours it no longer can mount it.. it has to be kernel related since that is only thing that changed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 09CarreraS:
This is exactly what I am seeing. CPU spy is logging less than 10 secs at bootup, then it shows several minutes at 1890 after benchmarking. I wish Ktoonsez would offer a version that takes out OC completely. I personally did not see any battery improvement with 7-10-12B. I have not run 7-18-12 yet. I know a new version is going to be released soon. I am hoping he will address this concern
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Strange, here is my cpu spy screen today, including my antutu test. Did not move from 6 seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
I am hoping the same, as the kernel did noticeably increase smoothness in some apps, but running an OC on this phone increases the temperature to the point where it's actually quite uncomfortable to hold.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bravomail:
Thanks Ktoonsez

Just reporting results with 7/18 Sammy - absolutely no problems, OC is stable, etc

Benchmarks are showing some slowness, I know I can shove it, but just something to think about. May be applying Linaro Toolchain will solve some issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Phone going above 1512 on Stress Test

It could be that the apps are reading my Mhz table and setting it to the max, not sure on that. One thing you guys can try is to go into recovery and clear cache, clean dalvik, and fix permissions. Then retry the test. I am not seeing it go above 1512 on stress test and that is the procedure I do everytime I install a ROM, restore from a nandroid, or flash a kernel. Give it a try and see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Not that I trust any benchmark apps, but the slowness could be caused by the fact that several Mhz steps are undervolted in my kernel which would probably cause a lower number.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
do you know what the linaro toolchain is? its been proven by many developers to do absolutely nothing different then the other toolchains that we've been using for a while now. :D

Benchmarks = Pull numbers at random and place on screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Think you need another "Thanks" meter, your is full :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] junglizste:
Does the AOSP version of this kernel support dock audio?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CPeterson:
I don't know if it's something you or the CM team would be responsible for, but any plans to add kexec support so we can get the dualboot feature that's available in the Sprint forum?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jaxf250:
Just a quick report - since I put on the latest aokp kernel from the 18th my battery life is some of the best I have

seen. Using ondemand/noop and OC to 1728 (no UV at all just whatever comes as stock kernel settings).

Using the latest and greatest aokp ROM from task - what else?!

Can't wait to see what else you have in store with the next release and further power savings - wow!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I can not find any info on whether our phone supports it or not. All I can tell you is that CM has included it in the sprint defconfig but has not put it in the ATT version. SO my guess right now is that our phone does not support the kexec.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
fix permissions? I assume the permissions should be set to 644 (read+write, read, read), but i'm not sure where or what to apply them to...setcpu perhaps?

Please let me know, as I do appreciate the the work you have done, i.e. this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Read the instructions again. All 3 steps are in Recovery, fix permissions is under "Advanced".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
I didnt see this in changelogs bt has sammy kernel have fixed adb remount?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 09CarreraS:
I just tried 7-18-12 kernel and I still have the same issue when running Antutu. The test was run at 1890 for 3 minutes even though Voltage control is set to 1512. After checking Voltage control after running Antutu is shows the slidebar set to 1890. Also, when the test is completed Antutu states the CPU speed is 1134. Please look into this. Also the testing shows a strange scaling. As you stated, your UV is possible causing issues with certain programs skipping scaling steps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
I didn't, and still don't see, the instructions; they don't seem to be on the first page. Thanks, though, for explaining where the permissions settings are :)

I had the same issue; even after setting clock speed to 1512, seems max regular usage would only go to 1134.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
I think he means those instructions
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I think he is lost, thought I was clear. And it looks like he doesnt even have our phone from looking at the "Rogers" symbol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
LOL.. your instructions were pretty clear...even to me and I'm an idiot. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
That's not how I do it. Reason being that you might be on the border of failure and just not know it yet. I lower mine until it does fail, by either a freeze or a reboot, and then I add 50mV. For instance, My 189MHz setting reboots the phone at 775mV... it will run fine at 800mV, but I feel more comfortable at 825mV.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I give up. Back to cm 10.1 3/17 Linux 3.0 thank you for all of your effort toonz this phone is retarded.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sorry buddy, we gave it our best shot I think, you can drive over to Chicago and we can beat the crap out of it together!!!!!!!!!!!!!!!!!!! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
On that mountain bike!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
+1

I feel like my phone is like that sometimes too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Today I only had 1.5 hours screen on time and many static screens I know that it's not your fault and I really do appreciate your work it's just this phone. I got it the day it came out that was probably a bad idea

---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------

I'm really thinking about making a YouTube video microwaving it since I am going to be getting a free galaxy notes two from a friend of mine

---------- Post added at 07:17 PM ---------- Previous post was at 07:10 PM ----------

Lol I have a car I jest love my new toy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] double RL:
Your phone is doing exactly what mine did last week. I was running Task AOKP and it just shut off for no reason with 75% battery. Did exactly as you described. It would go into download or recovery mode for a second or two and then shut down. I tried for three days to figure it out and finally carried it to the devices support center and they said that it appeared to have a bad motherboard and gave me a new one. Hope that helps. It's definitely not a rom or kernel issue.

---------- Post added at 06:10 PM ---------- Previous post was at 06:03 PM ----------

You can certainly try and may have better results, but adb would not work on mine either. Button combo or a jig would put it in download, but that doesn't help when it shuts off after two seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
My phone didn't stay stable on 3.4 releases until 3.4.43 (very recently in other words). Although it seemed to last a little longer with each major update but still only a few hours max then constant reboots.

Havent had a single random reboot since 3.4.43 (5-2-13 task build though I'm now on 5-5-13b) on either tasks kernel or ktoonz kernel, using each for at least 2 days to test run (I always run tasks AOKP). In fact i oc'ed to 1809 and uv'ed 50mv or more on the higher ends and its working great.

I wouldn't give up completely but u will likely need to sacrifice some time on older 3.0 roms until it gets fixed. What i did was constantly check tasks kernel source and see what fixes have been being added. Anytime something major was updated in regards to the kernel, I would nandroid and test for a while. Once the random reboots kicked in, restore and wait again.

There must have been huge fixes considering when my device started going into reboots, it was BAD. Basically unusable. Now im no expert at all with linux or android development but you'd be surprised how informed you can stay by checking the source modifications. It's like getting preview updates daily. :)

Edit: in a nutshell, don't give up but at the same time don't go nuts with each build trying to force it to work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Thanks for the response dude, I'm guessing this is going to be the result for myself as well, it's actually the second weird thing to happen, last time it would just boot loop, but a restore from odin ended up solving that. Now I'm guessing it is rolling over on me and giving up.

P.S. I PM'ed you about what you needed to do with going to samsung...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I've been doing that. I stayed on a week but 1.5 hours screen on is not going to work on a ten hour shift with no access to wall outlets I get 4+ on 3.0
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
@ Everyone

This only applies to whoever might be moving over to the SGS4 or who have already moved to that device. I did this when me & Ktoonsez were on the SGS2 and wanted to get him the SGS3 so he could stay with me in terms of devices. We had great success. If any would like to help Ktoonsez get the SGS4 and want to donate to the cause we are accepting any help. You know ktoonsez's donation link HERE . I already have the SGS4 and might not be keeping it due to not being able to justify the expense for the device. So if you'd like to help me justify keeping mine the you can donate to me HERE. I already have AOKP builds for it, we just need the bootloader to get unlocked and within minutes my AOKP builds will be posted for it. Let me or Ktoonsez know if you would like to help. It's your choice. We are not beggars. Just seeing who would like to pitch in. Thanks. :D

P.S- We will still be supporting this device. If you notice. I'm still supporting the SGS2 and I hate that device with a passion. ;)

Figured I would repost this I'm case some didn't see it. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] i5lee8bit:
Task: as much as I love the movie, maybe it might be a good idea to change the AOKP for sgs4 link to direct to one of those posts. I dunno if that would be inappropriate for any reason but it may help inform more of those who are interested.

Justin: sorry to hear that. That is really bizarre and I guess if toonz hasn't seen it yet... Well I dunno! :\ For the risk of derailing the thread ill stop. I'm sure you've tried checking apps and battery stats. Hopefully one day it will magically remedy thanks to the developers contributing to the new kernel. Until then, good luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
At least yours reboot... My 189 can run at 700mv and doesnt reboot. It just drains battery like mad due to ECC:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You can watch the CPU action KT's app. If the CPU won't sit on 189 with one CPU and jumps around like crazy WHILE AT IDLE, (make sure it's not busy) then use that as your failure point. So if it goes jumpy at 700mV and not at 725mV, use 750mV and you should be good to go... and that is a really significant under volt!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Hey at&t got a new test zip up for testers trying to the people rom over to here

http://xdaforums.com/showthread.php?p=41096574
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I did some searching and didn't see anything about this, so here I am posting about it.

My Google+ app is chewing up a great deal of CPU time, so much so that I instructed Watchdog to kill it if it goes over 30% CPU utilization. I've tried uninstalling it and reinstalling it., disabling instant upload, disabling location features, etc. Is anybody else seeing this issue before I go do a full wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Nothing to do with this kernel but download Greenify from the play store and configure it accordingly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Larz_Plummer:
I am noticing this as well. G+ appears to be quite the resource hog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I think it's a 3.4 kernel thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
mind explaining how google+ is affected by a kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I know it doesn't really make sense, but consider the following cause and effect:

Google+ acts "normally".

I update my phone to a 3.4 kernel.

Google+ doesn't act normally.

Something tells me there is some causality there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
To update to a 3.4 kernel you would have had to update to a 3.4 supported ROM release as well wouldn't you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
This is true. After thinking about the specific sequence of events, I think a more precise description would be that the issue first presented after switching to this kernel from the stock CM kernel. I'm probably doing a full wipe this weekend anyway, so we'll see what happens. Nevermind for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I always do a full wipe every time KToonz releases, I can't wait for the next update that'll include some of those kernel changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Sorry if the answer to this question is buried somewhere in here, but I did an in-thread search as well as a Google search first.

Does the ktoonservative kernel use hotplugging? If not, is enabling Auto Hotplug to force it worth it, or does it typically result in some annoyances?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Sometimes you just need to search on your device. Looking through ktweaker under governor adjustments for ktoonservative would've answered your question.

Yes ktoonservative is a hot plugging governor. You don't need to enable auto hot plug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Ktoonsez,

Here is a little for you an S4 and all your hard work. Not as much as last time towards the S3 but anyways happy developing. :highfive:

Confirmation number: 21V76436SM2056308
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Wow, man. This kernel is fantastic. Great work, ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
I have had 3 reboots this morning https://drive.google.com/folderview?id=0BwPHM0MVJt7sMWhyRjBBMnNXbG8&usp=sharing

I'm running CM10.1 on the 3.0 kernel this is the first time I have had my phone reboot.

I'm still on 3.0 because when I change to 3.4 I will get screen wake issues that if it does not start in the first 5min will start 3days later. I have not figured that out yet but have even tried starting a fresh install of CM stock and using the KT 3.4 kernel.

Thanks for the great work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Any latest nightlies ktoonz? I updated to latest aokp, but it said there were a lot of kernel changes so I don't want to go backwards and just remove them, as I assume they're good changes :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
He's away for another week I think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Ah ok
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
While I know toons is away, the one change in CM's latest that's really nice is the ability to change the color tint through the advanced menu. Since i've been using this the settings are much better than morfics on/off choice. if there is a way to implement this you could remove the option in ktweaker, or just improve the option in ktweaker to take advantage of the additional settings. They have 0-4 to adjust now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Maybe it can be made to be an additional menu option and adjustment in Ktweaker possibly leaving the morphic part intact. I don't know if they can be used together or if they are all same thing and the new option is just more precise. In any case KT when he is back to his workstation at home he can look into things. He has been very busy but we all know he is one of the most dedicated kernel developers and updates will resume without a hitch as soon as he arrives at home again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
no doubt! nothing but respect here. He is an awesome dev.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
3.0 5/3 working flawless thanks again toonz

Edit: kernel boot animation isn't working though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Just got back to the hotel (short day today, only 13 hours), Ill brew up the latest right now. No trinity color changes right now, cant debug KTweaker remotely but if I have free time this weekedn after work I will try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Glas4d:
TW 4.1.1

I'm trying to locate a link for the most current TouchWiz 4.1.1 kernel. Could someone point me in the right direction? I've searched through the thread but found no conclusive evidence as to the last TW 4.1.1 compatible kernel

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] syintiphic:
You can use the 4.1.2 kernel.

http://xdaforums.com/showthread.php?p=41019651
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 5.9.2013

1. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.295 from codeaurora.org

2. ARM: 7467/1: mutex: use generic xchg-based implementation for ARMv6

3. Revert "ASoC: msm: Support independent left-right channel volume cont

4. Revert "arm: mm: Add VM_ARM_EMPTY_MAPPING flag to mark the PMD gaps

5. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.292 from codeaurora.org

6. Couple patches for schedulers main code

7. Raise MDP bandwidth requirements (this should get rid of the screen flicker that some were getting)

8. Compiled with latest Linaro

9. Linux 3.4.44

10. Completely sync'd with CM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Even while you're on a trip. You are the ****ing MAN, KT! I don't know what I did before you came into my life!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Huh, did you figure that out? Has to be a missing boot animation zip file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
For realz. Dedication.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Ballerism.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Pimpinism.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Ktoonsez so far the 5/9 update is working flawlessly I am experiencing zero screen flickers and I will monitor battery life awesome update as usual :D:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Honestly ktoonz, if you don't stop being so goddamn awesome, I'm going to develop feelings for you. You can either be worried, or feel lucky that you're going to be my first man crush.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I get concerned when I read things like this.. But I didn't flash yet so what do I know :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Pimpalicious!

Great work KT!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Well, to be fair, ktoonz himself did refer to someone else's comment as "thick and veiny", if I'm not mistaken. Haha ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
0.8% per hour battery consumption so far tonight, using 5/9 KT over slimrom build 5. I love your work, KT!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Too late here. I already have the man crush on him. Stay back! He's mine!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Any specific settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Yes, but he knows me :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
I've searched the thread and noticed people were deleting or renaming mpdecision is system/bin is this necessary? from what I understand this might conflict with hotplugging if left enabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Forgot my phone at home when I left for work 10 hours later only lost 10% :)

3.4 5/9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Exactly use the autohotplug option and disable mpdecision or use a hotplugging governor
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
WOW, thats awesome man, last release you were getting 5% an hour, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Sometimes more 5-8% loss
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I get about 5-8%/hour during the work week because there is basically no signal where I work, so it's constantly connecting and disconnecting from AT&T.

On the weekend, if I don't go out, I can easily see ~3%/hour. My phone is syncing with my entire life, so I'm impressed with 3%. Basically every service I have an account for that can sync with Android is syncing.

Extra nice toonz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Not sure what's going on... KTweaker never asked for Superuser, and every time I change any setting, it FCs :(