yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jridda10121:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Yea it is its there a way to get his old kernel when he was using the Zen/ktoonz settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
It would be nice to be able to control the RGB values with the Trinity Color. I have a i1Pro Spectrophotometer that can read the values of the RGB, and white is just wayyyy too blue (hence why people say it looks brighter, paper manufacture does the same thing making their "white" paper more blue to make it seem "brighter).

Anyway just a suggestion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Sorry man, spent the day outside ;)

Flashing now. (Synergy r420)

Edit: so far so good except that with the new ktweaker the battery_control_mhz_high and _low settings still don't stick. No matter what I try with it (even not changing anything after I say yes) I still get the pop up message about governor adjustments not matching.

Stopped, cleared data and un installed the old ktweaker before I flashed.

Edit 2: setting all the battery_control values back to the default settings manually seems to stop the pop up when I open ktweaker.

So far, aside from the fact that 81mhz gets me a reboot, every thing seems to run ok with my usual settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Am I blind or are touch booster options gone?

Using build from 3/31
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpasilliumNexus:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Touchbooster = boost_cpu under governor adjustments
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Alright, so this version has been a little buggy for me, Ktweaker FC's sometimes, and I wanted to revert back maybe to the 2/14 kernel I still have on my phone.

My question is, is that an option, and I'm guessing if it is, to use the same process to Force Stop Ktweaker, clear data, and then flash back the old kernel?

For some reason, when I'm in the screen to clear data, it just hangs at calculating and.doesnt give me a number and the option to clear data is greyed out.

Any suggestions?

EDIT - Was giving me random reboots on stock 4.1.1. Reverted back to 3/6 kernel and seems to be working fine.

Clear data eventually worked but I.had to wait a good 20 minutes for it to calculate the small amount of data in the app. Any reason for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Toonz after flashing the latest build of the kernel my voice to text stopped working for Google and Swype.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Check for Google Play updates. There is an update out there. Kernel has nothing to do with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

What controls the Mic kernel or Rom? Because it's not working for any voice to text app I'm not sure if others are experiencing this my Mic works for Google now and voice calls
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

LOCKUP UPDATE:

Thanks to gravedigger for working with me last night!!!!! I finally found out what is screwing you guys over. It is a binary called /system/bin/thermald. It is kicking on when it thinks the battery is to hot and after its happy with the temps it sets a MHz setting of 2106 that causes the reboot. I'm sure most of u remember I am traveling this week and not sure how much time I am gonna have to find a GOOD work around for the new way I am losing the tables. In the mean time. If u remove that file u will have no reboots at all but will disable the thermal protection.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Hey toonz, you think I'll have a better shot with the 3/30 TW JB release then the one in the main changelog?

Im using the 3/14 right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

The ROM will turn it on and off. The kernel has the low level code that I would never touch. I had the same problem on AOKP last week and when I updated all problems went away
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

All of them r getting screwed over by thermald it doesn't matter. Read my above post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Got ya. Thanks for the quick reply, and have a good trip!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
At least I know I'm not crazy!! I was beginning to wonder...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Only way I could reproduce on boot was run antutu 4 times in a row and then reboot. So some devices just heat soak quicker than others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
So I will ask the question: if we remove thermald, what are the chances of harming our devices should something cause the battery to heat up? Maybe better to wait for the permanent fix than disable thermal protection?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Personally, I'd wait just because every device is different and I'm not willing to see how hot mine will get.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
I guess the question is if the kernel is causing increased levels of heat in certain phones, or if /system/bin/thermald has changed it's reboot threshold.

If it is the latter, then it is simply as easy as replacing the thermald file in the latest ROM with that of an older ROM. I can't tell which it is though because I can't read the file. It isn't opening right in notepad or Word.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

You could probably just rename it to thermald.bak to test it, and if your phone starts getting toasty, change the name back. I'm a huge noob, though, so that's just a guess at one plausible approach.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I would lean toward the latter since I have a hard time believing my phone got as hot just booting up as it has when I've used the GPS functionality while streaming audio in a hot car. It certainly didn't feel very hot when it was boot-looping. I did notice, however, that before the boot loops started my phone seemed to run a lot hotter in general since the 3.4 update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Instead of disabling the thermal deamon completely by deleting the binary wouldn't it be better to edit /system/etc/thermald.conf so to change the thermal alarm frequency throttle to something that exists in the frequency table ktoonsez has for the kernel?

There's no reason thermald would lockup the phone when changing the frequency unless it's trying to change to 1) a frequency that doesn't exist or 2) a frequency which is an overclock/isn't fully supported by your particular phone (or 3 = extremely heating, then it would trigger a shutdown).

Alternatively, one could change slightly the temperature threshold too, in case the alarm is being trigged too early for nothing. Not the best idea, but could be somewhat safe is done properly.

Thermald.conf is pretty easy to edit. There's a few different sensors around the phone, both with common controls:

sampling controls the thermal deamon sampling rate for that sensor

thresholds controls the value at which throttling will kick in

thresholds_clr controls when it goes back down

action is which device needs to throttle (cpu/gpu/lcd/flashlight/vibrator/battery/shutdown)

action_info is the frequency

Seems like it would be a safer way to play instead of frying the phone for the sake of running a custom kernel and overclocking. Just my 2 cents! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
So what you are saying is only turn on our phones when its cool? Haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Migrate to Canada, we're friendly. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Yep! I forgot my phone I my car this winter and when I realised it, it was at -5°c
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
I'm not sure I understand. Would this help those of us eating bootloops with the latest kernel? Do we delete/rename /system/bin/thermald prior to installing the 3/31 test kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tprophit:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I've had no problem with flashing either the 3/27 or 3/31 kernels. Easiest way is to flash rom first. This gets rid of ktweaker app. Then, delete or rename ktweaker file on sd card. Flash kernel. Enjoy.

Or, if u don't want to reflash rom, then force stop ktweaker, clear data, remove/rename ktweaker file on sd, and have at it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Lots of people have tried this and still have issues which is why there is so much back and forth trying to fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

You would delete that file before flashing kernel then flash away...

Remember though you're leaving youreself exposed to overheating. Also note this file WILL come back if you reflash ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Had to go back to 3-14. When I got up this morning the cpu was yoyoing like mad. No updates in the interim (I turn all of Google plays autocrap off). Soon as I reverted, the cpu calmed right back down and started playing nice again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
Thanks for the info! Will keep this in mind. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
CPU YoYoing means it was ramping up and down unnecessarily, instead of staying at a low mhz?

When you say 3-14 do you mean a build from 3/14? Why not the 3/27 build on the OP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neyenlives:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Thanks, I posed the same question in the d2vzw thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jonhy25:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Fast charge always getting disabled when I open back ktweaker app. Any idea? I'm on latest Carbon ROM with latest kt and using ktoonsez settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Not saying I know anything but remember when i had said it was a heat caused problem? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Not sure if its heat though... But the underlying issue which KT mentioned is the settings in that file causing it to wig out. Mostly I'm guessing false positive reading or with the 3.4 looking at a misc configured trigger... KT is a machine so probably will get it figured out as soon as he's back from the trip ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If you have always used Lock Frequencies then it is really the same as deleting the thermald file. As I have mentioned before doing the lock disabled it along with not allowing other 3rd party apps from writing another Max value. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I believe you're probably right. I was running both 3/27 task and ktoon and it was running great. So, like a dumbass, I updated to task 3/31 and ktoon 3/31. Reboots and crazy **** all over the place. So, I nandroided back to 3/27's and got reboots. So, whatever I was running I must have not hit the corrupt or f'd up file, etc.

Just something to pass along.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
It's a catch 22 though, you can't go in and lock frequencies because it bootloops :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

You may be able to rename the file in recovery tho
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ill elaborate a little more. The thermald is a Samsung proprietary that was not written very well, or short-minded really, what it does is when it detects heat based on the config file mentioned on the last page or 2 it starts to lower the Max Mhz setting but has 1 problem, it only reads the table that says how many steps there are and selects the highest step (2016 is our case) instead of reading the previous Max Mhz to set back to once its done scaling max to cool down. So even if I fix it to stop the 2106 and u use a lower setting like 1296, the stupid thing would have set it back to 1512 anyway. Make more sense guys?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah you mean when it's done scaling down, it will scale back to the maximum step, which in our case is 2106MHz, and unsurprisingly this step isn't stable for everyone?

That makes a lot of sense if it's what you mean, and it's also quite a #!&* to fix then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
Would an interim fix be to disable the OC steps in KTweaker so it sees 1512 as the highest step?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You got it. Has anybody that has been having the issue tried deleting the thermald file? You can always get it back by flashing your ROM. Just want more data before I start digging into this while on the road working a million hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Not really, "Lock Frequencies" is your best bet but wont save you from boot loops if the CPU is already too hot. As I have mention before "Lock Frequencies" blocks thermald from screwing with Max Mhz. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

My problems went away on tw with 3/31. 189-1512, lock freq, -50 uV on all, kt governor and recommended settings. This was stable until I made a phone call today (first phone call since 3/27 kernel) and it rebooted. I renamed thermald and with same settings called that person back and was on the phone for 30 minutes longer than the hang up call. I'm not sure if that info helps since I had the "lock frequencies" checked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] movingleader:
got it working

Hey Ktoonsez,

Long time lurker/user of your work; greatly appreciated!

I was having the bootloop issue with 3/31 - I renamed thermald to thermald.bak, flashed 3/31 which worked beautifully.

Then I renamed the file, deleting .bak and rebooted... it's been working fine.

Thanks again for your work!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
Going to try this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If you still have thermald WITHOUT the .bak it wil lock up at some point if your phone gets a little warm. Unless you check the box for "Lock Frequencies" :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Explains why if I have freqs locked I can run quadrant, if not the phone reboots immediately after running the tests. Must be setting the phone to a frequency that I can't handle (2ghz or something)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
For the guys who are trying to confirm that removing the file stops bootloops:

Quickest way i found to make it bootloop with the file there, (i did that today to test again), was go into recovery and clear cache and davlik and reboot, this forces OS to re-scan all apps and optimize etc.. which hits the processor pretty hard and warms it up. then as soon as you're about to hit OS, it reboots, and conitnues to reboot.

Give that a shot for testing.

To stop bootloop turn it off for a bit, and then boot in and lock freq or delete the file like KT is saying..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
Changed /system/bin/thermald to thermald.bak, rebooted into recovery and flashed 3/31. Booted fine. Opened KTweaker and enabled lock frequencies. Changed thermald back and rebooted. Bootloops. Now I didn't check set immediately on boot in KTweaker and this may be the problem. I thought that immediately on boot took a full boot to trigger, so this wouldn't matter and frequencies wouldn't lock in time to prevent thermald from restarting the phone. If removing thermald is the same as setting lock frequencies, then I will leave it out as I am not sure lock frequencies will trigger in time to prevent the bootloop. Do you think differently, KT?

---------- Post added at 05:15 PM ---------- Previous post was at 04:55 PM ----------

Edit:

Reflashed Task AOKP, deleted /system/bin/thermald and then flashed KT747. Booted up fine. Configured the kernel to KT's preferred settings. Rebooted, perfection.

Still have thermald removed, will re-add when there is a more elegant fix. Thanks to everyone that got us this far. I have KT747 working on Task's latest and I am happy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If you always have had Lock Freqs checked (this is how I have run my phone since day 1) then deleting is the same thing and you can leave it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BuBbLeFIZzY:
I deleted the thermal and mpdecision. The latest KT finally installed without boot loop. But the frequence will not go over 1512. Lock oc and set min past 1512 and it still won't go pass it no matter what I tryed. And tested benchmark stuff and the performance is like half of what I use to see. Ate my meal and when I turned on my phone it wouldn't turn on. So I just went back to what worked before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Ktoonsez I went ahead and deleted the thermald file and I have zero bootloops!! Now I am extremely happy to have the kernel working once again!! :D:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

I just flashed 3-27 jb last night and I can't get the battery control to stick am I doing something wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thermald is over-writing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Would you suggest deleting it or just not worry about it for now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I would just not worry about it right now. I am in the process of trying to write my own thermald code inside the kernel right now. So basically I will be able to delete the ROMs version and have my own but inside the kernel and controllable instead of worrying about external sources. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Thanks for the quick explanation. Got my S3 less than a week ago and I've been reading a lot, but I'm always happy to get proved wrong or my suspicions to get confirmed. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

No matter what ktoonsez you are the man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Re: [KERNEL][AT&T][AOSP/Touchwiz][JELLYBEAN][3/27/2013] KT747 - LJ7 - KTweaker

Just wanted to say renaming the file got 3-31 running great where I used to get bootloops! Thanks KT, you rock!

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Toonz how's your vacation?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Good, party is wrapping up and I got my dads junker out with interent to see whats going on :D. Ill send evevrybody a picture of Niagara Falls

from the cave of the winds on Monday :silly: :good: :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I drove my srt 4 up there last year it was a fun drive from ct the windmills were pretty cool on the farms but the bugs covered my poor car
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Thanks for responding Ktoonsez, highly appreciated, but was not for a second expected from your vacation. Hope you enjoy the rest of your trip...Niagara falls....try not to blow all of your donations in the casino :D.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
btw: where do I find 7 11? The link for Sammy kernel in the op takes me to a download for 7 10b.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, I really am on vacation totally forgot that 7/10b was the latest for Sammy. So 7/10b has the automatic setting to 1512 on boot. You will see 6 seconds or so of 1890 but that is it. If you are seeing items about 1512 after you are in your ROM, you need to fully wipe as something is corrupt/screwed up or a rogue app is setting something in the background.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] David Dee:
Thanks, will give that a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Hey guys, I'm at my army drill and just using tapatalk right now, so it's hard to search. I'm sure this has been covered, but can someone link me to explanations for the certain governors and schedulers? I think most people use on demand and noop, so that's what I put, but I have no idea what is what.

A link to the post or something would be great. Appreciate it.

I'm doing my inventory of all gear (ocis) so if you know what that is, I'm stuck here lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Also, can anyone explain why it's set at 1512, but max is at 1350?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Here's the one I read.

http://xdaforums.com/showthread.php?t=1369817
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
For some reason the processor need likes to do that just pick another clock level then move back to 1512
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
huh?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Thanks for ud

Now anyone has ever an explanation to my clock speed problem that I posted a screenshot of in my previous post?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
Unistall set cpu and/or voltage control, reboot, install voltage control and check. I think it is something set in set cpu that is conflicting with the kernel settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mk_ln:
powersave on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Yes, per but cpu one is off. Haptic, frame rate and all that are on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Trying that now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Ok installed voltage control extreme, works now...

Now to figure out what governor and scheduler to use for balanced and battery saver profiles i wanna make