yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Not trying to be picky or anything, but how does everyone else feel about a Holo UI in KTweaker?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I personally think this would be nice. I've always that ktweeker deserves a awesome ui. But I don't have the skill to help ktoonsez in this manner. Although I do have some ideas for icons within the app. Nevertheless I appreciate the work he's put into the app and kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Is there a way to remove the Kernel Domination splash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Here

http://xdaforums.com/showthread.php?t=
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Bad link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
http://xdaforums.com/showthread.php?t=1955964
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Good call. How are we supposed to pick up chicks with that splash screen?

Jk I think it's badass.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
I have had the same issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
reboot

[MENTION=4325945]ktoonsez[/MENTION] can you help me with this reboot? thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
Hmmm, it looks like your phone decided 1512 and 378 were not valid frequencies for some reason. Apparently, your phone had started throttling for temp, and when it stopped throttling, it threw two errors, both of them cpufreq_invalid_frequency errors, one for 1512000, and one for 378000. Then the kernel opps'ed, and finally panicked, resulting in a reboot. The really odd thing is, 1512000 and 378000 ARE valid frequencies. I don't know what would make the cpufreq driver say that they were invalid, seeing as I saw at least three or four other times that your phone throttled and resumed with no issues at all. The only thing I could possibly think of is maybe a ROM incompatibility? I think I remember KT saying something a couple of weeks ago about a certain ROM messing with the kernel's sysfs interface, which causes issues. What ROM are you running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
I'm running the PA build from the 19th
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
Thanks for taking a look at this for me. I think I figured out my issue. The frequency table for the stock kernel on that ROM is not in sync with ktoonsez. So might be headed back to CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
FWIW I'm running the PA june 21st build and have been running the past couple nightlies without any problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
What is adaptive governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks for handling that, perfect answer, Ive been traveling for work, working a billion hours and havent had much time for anything on the phones :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
It basically attempts to reduce power consumption in middle operation level. Level up will be done in step by step to prohibit system from going to max operation level.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abbz123:
Flash withdrawal of kernel :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
LoL I am going through the same thing even tho KT hasn't updated the kernel in a while I know he has a solid update coming soon he is to busy making that $$$$$ right now ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
that ROM and this kernel combo don't seem to play well for me. serious over heating issue and reboots galore... what are your ktoons settings if I may ask?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Try my setup if you like. Seems to have worked very well on PA for me as well as others I've shared this with. Report back with your results.

Locked Frequencies

CPU (MIN): 189mhz

CPU (MAX): 1458mhz

Scheduler: ROW

Scheduler Adjustments:

> hp_swrite_quatum = 5

> rp_swrite_quantum = 4

> rp_write_quantum = 4

Governor: Ktoonservative

Governor Adjustments:

> boost_cpu = 1080

> freq_step = 2

> sampling_rate = 50000

> sampling_rate_min = 10000

> sampling_rate_screen_off = 100000

Auto Hotplug: Checked

Voltage Table: -25mV across the board

Screen Off Mhz: 189

Screen Off Gov: Same governor

Screen Off Sched: Same scheduler

Battery Level Low: 15

CPU Mhz for low level battery: 1080 mhz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
ok I'll report back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
haha believe it or not I saw the above users settings in the kernel discussion thread and have been running those. So you should already be using them
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
ok so I gotta say after running these settings for the last 5 hours I haven't had any heat issues nor has the sampling_rate reset itself and there's been no reboots. previously I would set the boost_gpu, boost_hold_cycle, and down_block_cycle to 0's. would that have caused any negative effects?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Well seeing as I left those and a few others on stock values I can honestly say it was more than likely due to setting those to 0 but you can never guarantee anything. You can always experiment yourself there. glad to hear your phone liked my settings though lol. Based on your results it seems we were able to narrow things down and find the main culprits.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wi1son:
Ktoonservative already is a hot plugging governor. So what happens when you check enable hot plugging? I'm guessing the checkbox just gets ignored?

SCH-I535 on CarbonRom & KT747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
nothing it just remains enabled. I keep that checked on for whenever I decide to switch governors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
Ktoonse I know that this was answer a few times already, but with each release of the kernel.ee had new options.

For that reason can you post you're recommended setting for the TW version.

I just change from AOKP to deTmobilzed 1.3 and the TW kernel work perfect. I jst want to validate the settings. It has several fifferent options than AOSP base Rom. Also if you can for future release the opions for the low battery speed can you made the TW version like the AOSP that the options are in a separate menu under extra. Not in the gobernor adjustent option.

Thanks, my battery life is a lot better now by far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Have you tried my settings above? They are AOSP based but you would only need to input the values to those available. I tried them on both AOSP and TW and some of my testers have reported back with great results. just something for you to try if your interested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
I've experienced a number of instances recently with the phone shutting itself completely off since moving to the 2 most recent AOKP builds and this kernel (was coming from an early May AOKP build and yes, I updated the bootloader and did a fresh install).

Here's the breakdown: shuts off randomly at least 6 times a day (no trend of doing something specific on the phone); Upped the voltage by 25 after each reboot--got to +200 and still shutting off; tried numerous governors and schedulers; tried locking higher frequencies for my minimum. The weird thing is that even when I nandroid back to the 5.09 build that was previously working well, I still get the reboots. Flashing back to Underwear kernel--still getting them.

Here is a last_kmsg if anyone can help. http://xdaforums.com/showthread.php?p=42778914

I flashed back to stock then re-rooted and am doing another clean install of Task AOKP as we speak and we'll see if I still get the reboots. Will report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Bad link. Also, I know this doesn't relate to your question but why did you re-root when you were already planning on flashing a pre-rooted ROM? All you'd need is the custom recovery and flash the ROM. Just saves a lot more time don't you think?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
Thanks, mate. I updated the link to punt to a previous post of mine where the file is attached.

I rerooted because I knew that was truly going back to square one and since restoring a nandroid (for the May build that never had the reboot problem before updating) still resulted in reboots, I figured this was the next best option.

However, to update from the previous post, I am still getting reboots with a clean install.

Sent from my SGS III. Give credit where credit is due...and hit the THANKS :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Try this and see if it helps at all

- Full wipe 3x (System, Data, Cache, Dalvik Cache)

- Backup then Format internal storage.

- Flash ROM

- Flash Gapps

- Reboot

- Reboot Recovery

- Flash kernel

- Wipe Cache/Dalvik

- Fix Permissions

- Reboot

Don't restore any KTweaker settings. See how the phone runs on stock values then if all goes well you may try manually inputting your settings but reboot after every few settings applied.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
This is why I said earlier that I needed my kt and im on tw kudos man kudos
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
I followed the process and did not add any kernel adjustments and still got random shut downs. I then tried your kernel settings from the previous page and have been 6 hours without a shut down (longest yet). Thanks for sharing!

The part that stumps me is that I did all of the correct wipes and still got the shut downs on a clean version, then wiped and restored a nandroid that never had these problems and the nandroid started having shut downs. What would stay through a nandroid that could cause the issue to stay?

Sent from my SGS III. Give credit where credit is due...and hit the THANKS :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
temporary files from previous ROMS dumped into the internal storage and that's odd how my settings work flawless for you but the stock ones don't.. I would've wanted you to pinpoint the causes while tweaking the default settings before I actually recommended my settings lol. I'm glad they helped though man. They seem to be helping out quite a few users with their issues as well and that wasn't even my original intention with the hours I spent experimenting with the settings to come up with this final product lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I'm having a weird issue with some audio apps. Both Play Music and Podfy have been randomly playing at max volume, regardless of what the volume is set at. I'm thinking it's a kernel problem because i switched from PAC-man to JellyBam today and I'm still having the problem. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Yeah I'm having the same issue and I also think it's a kernel problem because when I just use the AOKP ROM/kernel I don't have this problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I don't think so. Kernel w/ audio (Pandora & JetAudio Plus) and everything else seems to be working perfectly. Perhaps a clean install is needed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
Well I went a total of about 8 hours until I encountered the next shut down. I'm tinkering with the governor parameters right now to start, but if anyone has suggestions, please feel free to chime in. I've attached a last_kmsg of the most recent shut down. Thanks, all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Governor tweaks probably won't give you stability.

Perhaps your voltages are too low on one frequency and you happen to miss that frequency due to the fact that your governor tweaking makes it skip that frequency.

Even if you don't under volt you can still run to low of voltages, this used to be a problem.

If you want to seek out where your problem is run benchmarks and every cpu intensive process you can whilst staying from highest frequency working your way down one frequency at a time. The goal is to make it reboot at frequency X, then go back and raise the voltage for X's frequency till it's stable.

Oh you can use the same method to undervolt btw, one step at a time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
After checking out your last_kmsg, it seems like your phone shutdown because the PMIC requested it. Now, I'm no expert in the different chips that make up these phones, but from my research, a PMIC is a power management integrated circuit. In other words, it is the chip that handles charging the battery and converting battery voltage to the voltage required by other chips in the device. Unfortunately, the kmsg did not give any clue as to why the PMIC requested a shutdown, at least not that I could find. Taking a guess though, I would check your battery and charger, and under/over voltage settings. At least, that's my understanding. If anyone else has more info, feel free to chime in!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Sounds like a good chance it's a hardware issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
For the 4 millionth time, USE VOLTAGE CONTROL NOT SetCPU! if you are having issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Only problem with that is that it happens with VC as well. I think mine finally stabilized. Governor was resetting to ondemand, scheduler to cfq, and the clock changes seemed random. This is after flashing 719b, wiping cache, dalvik, and fixing permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
Not to beat a dead horse, but the Sammy version is still not working properly with SetCPU. I only mention it because the change log indicated an update to try to fix it. The minimum seems to work, but the maximum is exceeded when running a benchmark. I am going to repeat my mini test with Voltage Control and see what happens!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheRevolution1:
Awesome kernel, thanks a lot. Any chance of a 480mhz GPU build in the future?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Yes, that is beating a dead horse. Addressed two posts above you by ktoonsez, and referenced in the next post by someone.

Don't beat a dead horse. Get DirectTV :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Still happening apparently. This time the governor and scheduler stuck, but the max went down to 1300~
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkeaver:
My settings are sticking just fine for both min and Max even after running a bench mark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
Edited.... I flashed the wrong kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
if you have nothing related to say about the kernel, please keep OT stuff off this thread.

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
What have you used that has made the GPU look like it needed overclocking?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TechSilver13:
The same can be said for the processor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastergrillo:
Anyone getting reboots when applying setting in voltage control

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jethro650:
I am too, just reflashed earlier kernel and all is good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caveman999:
Same here. I am getting better results with version A of today's kernel as it is not constantly rebooting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeesubalpha:
yeah sorry failed to mention VC was also giving me issues. was actually referring to VC (since I've never really used it) with this statement:

when I couldn't get VC to work i reverted back to setcpu because i figured it wasn't something that could be fixed with an app and i really like setcpu's profiles.

grey did you do anything between flashing the kernel and vc "stabilizing"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
It didn't stabilize for long. Just now it rebooted and locked min/max at full, then locked up the phone. I just got done reflashing and wiping. I'll report back soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
you can run dead trigger in ultra high with much less lag.

and like others have said, what have you needed on this phone to run at almost 2ghz?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malimal:
flashed ASOP and upon boot it flashes the SGS III screen and goes black?

any ideas to fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Are any of you guys trying to undervolt or changing governors? More info would help ktoonsez troubleshoot. I'm running noop/ondemand, 7/19b and haven't had any issues at all, and I've been using the phone, changing min/max clock, etc. Also, did you follow the install instructions in the thread (AFTER flashing, clear cache, dalvik, and fix permissions)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malimal:
how did you do that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
I actually had the same thing happen to me today. Tried different ROM but no go. Tried stock cm kernel and it works fine. Seems to only happen to Google Play Music.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
Yeah, especially since he gets the shutdowns even after nandroid to a previously working backup and after odining to stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
Update: I updated to Task 6.24 and have had 1 reboot in 24 hours. Everything seems much more stable. Still never pinpointed the problem. I will flash this kernel tomorrow and see if anything changes

Sent from my SGS III. Give credit where credit is due...and hit the THANKS :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
Hope it stays stable for you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Since Edward Snowden is on the go, ktoonsez has been less present on xda. Am I the only one who thinks ktoonsez might be Edward Snowden :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Don't say Edward Snowden so much on the internetz !! CIA is probably tapping in right now because you mention Edward Snowden so much! Linking Edward Snowden to ktoonsez might get him in trouble!! So forget Edward Snowden.. We know KT is not Edward Snowden....

Edward Snowden!! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Well I just googled Edward snowden and this thread is like the 3rd result :banghead:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Any more information or help with this?

When using this Kernel (with AOKP ROM) all of the volume on any app I use is MAXED OUT even on lowest volume setting.

However when I just use the stock AOKP kernel I do not have this problem.

I can see here that Frost5689 is also experiencing this problem with only this kernel so it must be kernel related?:eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
There have been a lot of kernel updates since the 8th.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
6/8 Is the one linked in the OP and from looking back through the posts/pages it's the latest one I can see linked by KT.

Is there a newer version available for download somewhere?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane87:
No, he is saying that the AOKP ROM relies on a bunch of new kernel code that is not present in the 06/08/2013 KT build, hence the audio issues. Until KT gets the new commits pulled in and a build out, you will either have to stick with latest AOKP + default kernel, or an AOKP build around 6/8 and KT 6/8 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Thanks for the info, you guys. :thumbup: Now I have to decide whether it's worth it to trade the amazing battery life I'm getting for my music...haha ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 6.26.2013

1. Updated to CM latest

Still out of town guys and working like a slave but had some time this morning to update it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Everything running good guys, want to make the kernel for the other variants??? Thanks :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
My boss just left for lunch... flashing now. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Flashed a little while ago, haven't tested the audio volume issue, but everything else looks good,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
Been running fine for me so far on the latest Carbon nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Running great so far, audio issue seems to be fixed! Rock on, ktoonz! :thumbup: :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
At this point no issues found and working fine on Rootbox Nightly 6/24.. Great Work!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Running great on Tasks AOKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Also running flawlessly here :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
Running smooooth on Slim
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
So far so good on CM 10.1!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Am I the only one running stock tw? Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
That's cuz a majority of us, including the dev, hate Touchjizz. No offense lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
File blocked for violation when I click on the link. Not sure why or what it violates today and why these updates have been fine in the past.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fredrick1213:
Having the same problem. Gives an error message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
Thanks for the update Ktoonsez!

If anyone managed to grab the AOSP linux 3.4 kernel before the error cropped up on mediafire, a dropbox link or something would be greatly appreciated!

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Can someone that downloaded it post it somewhere? I just got this message plus 10 more for all the releases today. This is some B.S.

The file (KT747-TW-JB-4.1.2-ATT-06-26-2013.zip) violates the MediaFire Terms of Service. Due to it being distributed from your account, is no longer shareable. Also, a Strike has been placed against your account and can lead to a termination of service.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gto:
Anyone please?

Sent from my Galaxy S III ATT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
DL http://www3.zippyshare.com/v/42091945/file.html

AOSP 3.4.x 6/26
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I've updated the OP to my thread. All posts have been updated to latest build in case anyone is looking for mirrors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dark_intel:
Flashed new build and audio output only on right side works. Video recording causes instant reboot. Latest slim rom.

Xda I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
For future reference, I keep an archive of pretty much everything ROM or kernel related that I download in a Dropbox folder, so if you need anything, just PM me and I'll probably have it. See my earlier quoted post for my KT747 folder.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Guys if anyone is having issues obtaining the latest build then please either PM [MENTION=2973923]MSgtSimon[/MENTION] or refer to my thread for mirrors. All posts have been updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Also just look in the dropbox folded I linked to in my quoted post in my last post. Roundabout much? ;)