yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] froader:
Thanks and Happy Thanksgiving!

I see 192 now and voltage.

Any idea why the cpu tweaking programs are having trouble saving min/max cpu setttings?

I tried setcpu, and a bunch of others.

Ended up with Voltage Control, which was doing its job until 1.1b.

Now the min cpu wont stick, however cpu still shows 192 very active.

I definitely would rather use a different app. Only gripe is having to adjust each fq voltage seperately.

What app are you using with success?

I was wondering if you could list the stock voltages at some point. Thanks!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I wish I could remember what is causing it, but thats been an issue for many on our custom kernels. I dont generally use a custom one, so haven't looked at it in a while, but if you search through morfic, faux123's threads youll probably find it there from a couple mobths ago, probably more recent than that still.
[T-Mobile, Samsung Galaxy SIII] gmanhad:
I'm using setcpu, and it is saving my settings just fine. I am set at 192/1350, sio, ondemand.
[T-Mobile, Samsung Galaxy SIII] gmanhad:
Setcpu settings
[T-Mobile, Samsung Galaxy SIII] Chaos5429:
Does anyone know a good app to for GPU OC? Or is the kernel native OC for GPU?
[T-Mobile, Samsung Galaxy SIII] sairegsx:
In this kernel it comes embedded in the source. When it hits max freq it will be on 480mhz(400 stock).
[T-Mobile, Samsung Galaxy SIII] sairegsx:
I payed for SetCPU long time ago, that was my first try and it gave me many issues with this kernel, so i when ahead with Voltage Control and it works. Usually a reboot fix some of the SetCPU issues, i know is not normal behavior but as i already said, am not a developer nor a programmer so i don't have the knowledge to fix those bugs, sorry. All i did was use a lil bit of what i know and some common sense(i think it should be common:))

Stock table:

static struct acpu_level acpu_freq_tbl_8960_kraitv2_slow[] = {

{ 0, { STBY_KHZ, QSB, 0, 0, 0x00 }, L2(0), 950000 },

{ 1, { 384000, PLL_8, 0, 2, 0x00 }, L2(1), 950000 },

cpu freq--> 432000, HFPLL, 2, 0, 0x20 }, L2(7), 975000 <----voltage

{ 1, { 486000, HFPLL, 2, 0, 0x24 }, L2(7), 975000 },

{ 0, { 540000, HFPLL, 2, 0, 0x28 }, L2(7), 1000000 },

{ 1, { 594000, HFPLL, 1, 0, 0x16 }, L2(7), 1000000 },

{ 0, { 648000, HFPLL, 1, 0, 0x18 }, L2(7), 1025000 },

{ 1, { 702000, HFPLL, 1, 0, 0x1A }, L2(7), 1025000 },

{ 0, { 756000, HFPLL, 1, 0, 0x1C }, L2(7), 1075000 },

{ 1, { 810000, HFPLL, 1, 0, 0x1E }, L2(7), 1075000 },

{ 0, { 864000, HFPLL, 1, 0, 0x20 }, L2(7), 1100000 },

{ 1, { 918000, HFPLL, 1, 0, 0x22 }, L2(7), 1100000 },

{ 0, { 972000, HFPLL, 1, 0, 0x24 }, L2(7), 1125000 },

{ 1, { 1026000, HFPLL, 1, 0, 0x26 }, L2(7), 1125000 },

{ 0, { 1080000, HFPLL, 1, 0, 0x28 }, L2(16), 1175000 },

{ 1, { 1134000, HFPLL, 1, 0, 0x2A }, L2(16), 1175000 },

{ 0, { 1188000, HFPLL, 1, 0, 0x2C }, L2(16), 1200000 },

{ 1, { 1242000, HFPLL, 1, 0, 0x2E }, L2(16), 1200000 },

{ 0, { 1296000, HFPLL, 1, 0, 0x30 }, L2(16), 1225000 },

{ 1, { 1350000, HFPLL, 1, 0, 0x32 }, L2(16), 1225000 },

{ 0, { 1404000, HFPLL, 1, 0, 0x34 }, L2(16), 1237500 },

{ 1, { 1458000, HFPLL, 1, 0, 0x36 }, L2(16), 1237500 },

{ 1, { 1512000, HFPLL, 1, 0, 0x38 }, L2(16), 1250000 },

{ 0, { 0 } }

};
[T-Mobile, Samsung Galaxy SIII] froader:
Yeah, I wonder what it is. I cant get any other program to make cpu fq stick after reboot or even the next time I reopen the app, except for Voltage Contro(well not 100%). I searched their threads, but couldn't find anything, however looks like sairegsx just posted them.

I wish that I had the same luck as you, but sadly dont. Frustrating.

Funny timing. I was just jumped over to my computer because I was having trouble pasting here from my phone and you just posted...

Thanks for the stock voltages. That helps a lot!

I guess I will just go back to voltage control, although I even noticed it running 1.89, when I set the max to 1.7. it sounds like this may be a problem with our cpu and not kernels.

Maybe as an alternative would be to offer different kernels, however I have no idea the time it takes to make one change.

192-1.5

192-1.7, which I like

192-max clock

Another thing I noticed after flashing the 1.1 kernel is I have a blank area on the recent apps where you would find task manager, google now, and end all. I dont recall any other changes...

Thanks for your time - it's nice to have something to play with.
[T-Mobile, Samsung Galaxy SIII] mike102871:
I boot loop with the latest.
[T-Mobile, Samsung Galaxy SIII] sairegsx:
v1.1b or v1.1c??
[T-Mobile, Samsung Galaxy SIII] sairegsx:
I just checked mine and it is there, what rom are you using...it might be rom related. i dont see how could the kernel affect that, try reboot, or clearing cache.
[T-Mobile, Samsung Galaxy SIII] numba1cuban:
Im running the original kernel v1.1 and hands down the best kernel ive use. Ive tried them all. Has excellent battery life, my android systems is as low as its ever been and my quadrants are great. I'm scared to try the revisions. I will post pictures in the am. Thanks for this. Great work!! :good:
[T-Mobile, Samsung Galaxy SIII] froader:
I am on the stock JB update from the ota.

Flashed stock kernel, wiped cache/dalvik, set permissions and still blank.

Don't know what did it. I couldn't imagine it was the kernel although it happened around that time. Thanks for checking.

I will stay stock till we know that the settings will stick. Even Voltage Control wasn't working for me.

I'll keep up on the progress and who knows maybe you will build a 192/1.7 version. Other than the fq not sticking it worked well. Great progress!
[T-Mobile, Samsung Galaxy SIII] mike102871:
With 1, 1b and 1.1c both boot loop. Went back to original
[T-Mobile, Samsung Galaxy SIII] Craniotomy:
I've been using your kernel since first release, battery on oc highest freq, and lowest, i got about 8-9 hours with wi-fi on all the time but with auto on and off, temp was around 29c to 33c, now with the latest, temps range between 23c-28c, 6 hours and i have 55% still, with wi-fi on and about 3 hours screen on. And on all versions of the kernel everything was fast and smooth. Thanks again!
[T-Mobile, Samsung Galaxy SIII] know50:
Rom toolbox works great for me just so everyone knows, Settings stick just like they should. Thanks for the awesome kernel
[T-Mobile, Samsung Galaxy SIII] froader:
Have you double checked with cpu spy or similar? Does it do voltages as well?

Edit: just tested and it does voltage quite well, but cpu clocks wont stick, even after closing and reopening.

Back to stock once again. Arggg!
[T-Mobile, Samsung Galaxy SIII] noellenchris:
Which recovery are you using to flash the kernel's? Maybe you will need to Mount the System or something like that? I guess you already tried clearing cache's and fix permissions too. Otherwise I was thinking that some recoveries don't flash some things very well sometimes.

Noellenchris
[T-Mobile, Samsung Galaxy SIII] froader:
I have always used CWM recovery and for TAR Mobile Odin is killer.

Never thought about recovery being the problem. What do you use?

I even flashed the full stock(not ota) JB TAR from Sammobile, followed by this kernel, wiping cache, dalvik, and fixing permissions.

Quite frustrating that nothing is working for me to control clocks.

Maybe init.d support would be better. I know Voltage Control has the option to set on boot via init.d.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Flashed your latest version took away ktweaker app.. That's fine. Reinstalled ktoonz and ktweaker app is still gone. Its listed under system apps but doesn't appear in drawer. I manually pushed it to system fixed permissions still not their. Is their a script that is still their that is not allowing It to appear.?
[T-Mobile, Samsung Galaxy SIII] noellenchris:
CWM should be fine, sometimes TWRP can cause some trouble, I use TWRP, Also what other battery saving apps are you using if any? I know the app One Power or something like that found on XDA and in the market works, but it takes over control of any manual cpu controls, if you installed that or didn't fully remove it, it will overide your cpu settings. At least it did that to me. You could try TWRP, but I don't think it will help, but hey, it may work and save you some trouble.

Noellenchris
[T-Mobile, Samsung Galaxy SIII] froader:
No power saving apps for me, unless the built in Power Saving settings(only Background Color enables) messes with things.

I guess I could try TWRP, but like you said it will probably not make a difference.

What are you ussing to conteol the clocks? And are the settings sticking?
[T-Mobile, Samsung Galaxy SIII] noellenchris:
Well I hadn't tried to set on boot, so I went ahead and set it System Tuner = didn't stay, Rom Toolbox = didn't stick either. Maybe were both in the same boat I guess. No biggie, if I set it and don't reboot it seems to stick. Either way, it seems to run very nice at the default without issue, and battery seems fine too. I guess I wouldn't go to crazy...:P I try to use System Tuner since the dang thing always starts up regardless, so I may try SetCPU, haven't used it since my HD2 day's.

Noellenchris
[T-Mobile, Samsung Galaxy SIII] numba1cuban:
Here it is as promised!
[T-Mobile, Samsung Galaxy SIII] numba1cuban:
Btw Im running original v1.1 and it is able to underclock to 192 here is proof..
[T-Mobile, Samsung Galaxy SIII] mike102871:
If you have power saving mode enabled, it will over ride other cpu settings.
[T-Mobile, Samsung Galaxy SIII] know50:
Look at the post right above lol. Disable power saver in settings and you should be good to go
[T-Mobile, Samsung Galaxy SIII] froader:
Yep, sounds like the same boat for sure.

Do you have power saving setting enabled? These guys below think that may be the cause. I am guessing you don't, but just curious.

This is all that I have enabled. Does it still affect the clock speeds without having CPU Power Saving enabled?

It's worth a try, but definitely sounds like others are experiencing the same problems.

What tuner program are you guys using that you see the settings stick after boot?
[T-Mobile, Samsung Galaxy SIII] know50:
I use rom toolbox for overclocking because it was the only one that kept my settings through a reboot. But yeah power saving option always gave me issues with my cpu settings so I just leave it disabled. Give it a try to see if it helps and if not then you can always turn it back on. Works for me though. Hope this helps good luck
[T-Mobile, Samsung Galaxy SIII] WarlockW:
Same Problem here .. tried a different few things .. no luck.

Btw Thanks for the over clocked kernels!

Nice to see a new kernel guy on these threads!
[T-Mobile, Samsung Galaxy SIII] froader:
I tried Rom Toolbox as well. None of them work for me on the stock rom I guess. Disabled power saving and have the same problem.

Restored nandroid and moving on for now.

I would flash AOSP, but Google botched Activesync and my Exchange account is all screwed up.

Hoping that 4.2 fixes that.
[T-Mobile, Samsung Galaxy SIII] mike102871:
Only the first release works for me. The other releases boot loop . Still , after numerous tries.
[T-Mobile, Samsung Galaxy SIII] numba1cuban:
Try system tuner pro! Wipe cache and dalvik and fix perms
[T-Mobile, Samsung Galaxy SIII] know50:
Sorry that didn't work for you. Works great with frosty jb though. You should give frosty a go because its way better than stock man. Good luck either way
[T-Mobile, Samsung Galaxy SIII] froader:
Ah well.

I think that I will test out Frosty once v10 link is up. Where the heck did the search box go? All I see is "search all forums"

Does it come with the stock kernel?
[T-Mobile, Samsung Galaxy SIII] know50:
Yes it does come with the stock kernel.
[T-Mobile, Samsung Galaxy SIII] froader:
Great, thanks!
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Probably not. That movie has been trouble ever since T-Mob and Samsung decided to give it to us. For example, I flashed Evilart's latest, Wicked V8 and the movie wouldn't play. Then a couple of days later I'm trying to show a friend it won't play and...bam, it's playing. Played perfectly too, no skips, stutters or hiccups. No idea why it now works although I think sometimes it's related to media syncing. Haven't flashed this kernel yet, btw.

---------- Post added at 11:30 PM ---------- Previous post was at 11:25 PM ----------

Didn't someone mention that "powersave" or "batterysave" option in settings being ticked on made SetCpu settings not stick?

EDIT: Sorry, didn't know you guys already tried that.
[T-Mobile, Samsung Galaxy SIII] froader:
Flashed ovrr to Frosty v10 and still none of the apps keep the cpu clock settings..

Whatever...at least I'm on Frosty which seems better than stock.

Hope this gets ironed out as I would be stoked to tun this kernel.
[T-Mobile, Samsung Galaxy SIII] Chaos5429:
I'm getting boot loops with 1.1b(c) and using Frosty JB 4.1.1 v10. This is kinda strange since I was using 1.1b for about a week then suddenly my phone crashed and went into boot loop.
[T-Mobile, Samsung Galaxy SIII] jdidtht:
That shouldn't be happening at all..how do u use it for a week just fine and then one day it crashes into a boot loop.. What else did u do?
[T-Mobile, Samsung Galaxy SIII] Chaos5429:
I made some undervolt settings but according to the stress test in SetCPU it was ok. Now if i try to install 1.1b(c) my phone goes into a boot loop. It doesn't do that when I revert back to 1.0 or stock though. I was playing NFS and it suddently shut off last night and went into a massive boot loop. So yea, I'm confused.
[T-Mobile, Samsung Galaxy SIII] ninja75:
what rom are you using
[T-Mobile, Samsung Galaxy SIII] sairegsx:
@Chaos5429

My guess is that because v1.0 doesnt have the same freq it brakes the profile you have set on boot and the device works, when you flash the latest that allows that amount of undervoltage(that your device might not like) then you boot loop, try booting v1 then remove or clear the app data and try the v1.1b(c). Good luck.
[T-Mobile, Samsung Galaxy SIII] sairegsx:
Am already looking for info and hopefully a way to fix the freqs not sticking. As soon as i find something i will post an update. Thanks for your time and support.

I will try to add init.d support also.
[T-Mobile, Samsung Galaxy SIII] Chaos5429:
Going to give it a try. I reflashed a Frosty's rom to hope it wipes the settings. Not sure if that makes a difference though. If wiping the app data doesn't work, what other methods can I get 1.1b(c) working again?

---------- Post added at 10:02 PM ---------- Previous post was at 09:54 PM ----------

Nope, did not work after clearing app data. I also cleared both cashes in recovery and basically it boots all the way to the launcher screen, then freezes for 5 seconds, then reboot. That repeats forever if I don't pull battery or go into recovery.
[T-Mobile, Samsung Galaxy SIII] mike102871:
Exact same problem for me on the stock rom
[T-Mobile, Samsung Galaxy SIII] seshaz:
Settings stick for me using rom toolbox pro, flashed stock then this just for good measure. Using aeon flux rom
[T-Mobile, Samsung Galaxy SIII] know50:
Go back to all stock CPU and voltage settings before you flash the new kernel. Wipe cache and dalvik before and after the kernel flash then fix permissions. Also might be good to red download the kernel just for good measure. Also if the kernel worked great for a week then one day messed up then it has something to do on your end like an app or some setting that got changed. Sounds like too much UV or too much oc or maybe even a combo of both. Works fine for me on frosty jb. I can't UV without having issues with this kernel but I can get to -30 with ktoonsez kernel

---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------

Hey sairegsx thanks for working on a kernel and sharing it here with us on xda it is much appreciated. If I could make one suggestion it would be to add undervolting in steps of 5mv if its not too much trouble. Other than that good job man! I'm glad we have another kernel to play with especially a stock one without a bunch of crazy tweaks and what not. Thanks again man and good luck! I'm sure this kernel will be awesome when you are finished with it:cyclops::good:
[T-Mobile, Samsung Galaxy SIII] Chaos5429:
Well... I am going to confess that I UV everything by 100mV.... worked fine for a while every when playing NFS unwanted... So stock everything then redo everything will fix? BTW v1 works but not 1.1 or above.
[T-Mobile, Samsung Galaxy SIII] know50:
You can't just jump down -100 and expect it to be OK lol. Each kernel handles oc/UV differently so you have to go through the process of stepping down by increments of say 25 at a time then play with it for like the day and see if you can step down more. If you jump down -100 and just ride out then yeah you're probably gonna get boot loop lol. -100 is a lot dude. I am lucky to get -25 if I can and even though it may run at -25 I end up running into issues later like audio crackling and stuff. Also you have to take into account the UV and oc together. What you should do is oc to where you think you want it and if it handles that OK then UV -25 and see how it goes ya know? Its a process because no two phones or kernels for that matter will do the same. Go through the steps and I'm sure you find your optimum levels. Good luck man
[T-Mobile, Samsung Galaxy SIII] jdidtht:
Yea that's too much.. That's pretty crazy if true .. Ktoonez is undervolted in the first place so to add another 100 on top.. Whew! Too much in my opinion
[T-Mobile, Samsung Galaxy SIII] Chaos5429:
Well, is there anyway to make 1v1b(c) work again? Since I flash a different i thought it would reset the voltages but I guess it stayed in the history. I am not sure how to get those newer kernels work again. :(
[T-Mobile, Samsung Galaxy SIII] know50:
Go to whatever app you used to change voltages and uncheck the apply on boot option or just turn the voltages back up manually. If your phone is stuck in boot loop then pull the battery then put the battery back in and hold the volume up button, home button and the power button all at the same time to get into recovery then wipe all and reflash your rom again. You might have to start fresh bro. Hope this helps
[T-Mobile, Samsung Galaxy SIII] photolarry:
So just in case someone wants to use this kernel and get init.d scripts running...very easy work around is get Rom toolbox and make script with these two lines:

#!/system/bin/sh

/system/etc/init.d/*
[T-Mobile, Samsung Galaxy SIII] VolcanicSkunk:
Thanks so much for this kernel. Working great so far on Wicked v1.3. Keep up the great work!
[T-Mobile, Samsung Galaxy SIII] CousinMikeyP:
Do the scores stick with the latest kernel? For instance if I set profiles in setCPU or ROM toolbox for apps and stuff like that? I would like to know before I flash this kernel because right now I'm Just waiting for my battery level to hit 100% before I flash. I'm at like 2% now lol, But anyway if someone could answer my question I would appreciate it

Thanks in advance.

Sent from my SGH-T999 Equipped with FROSTY JELLY BEANS.
[T-Mobile, Samsung Galaxy SIII] noellenchris:
Been using your kernel since you released it. I keep trying all the others, but yours just seems to be the fastest. I know you say you didn't do much to it, but that may be the secret. At least with the rom I'm using from WildChild. All the other kernels seem to run and feel smooth also, and I don't hold much weight on benchmarks, but your kernel always benchmarks much higher and feels just as smooth. So who knows, to each their own. I'll be following your thread and hoping for your continued experiments. Thanks.

Noellenchris

EDIT: I don't use any OC/UC/OV/UV stuff, just run it the way you packaged it. :P
[T-Mobile, Samsung Galaxy SIII] itsamti:
This works great, thanks for sharing. I am on FreeGS3 7.1.1
[T-Mobile, Samsung Galaxy SIII] ismethajametovic:
I have AOKP 4.1.2 Milestone 1. Will this kernel flash/work ok with AOKP M1?
[T-Mobile, Samsung Galaxy SIII] seshaz:
No, as it says lja touchwiz
[T-Mobile, Samsung Galaxy SIII] elsocplayer:
I'm not much of an expert but I have ran into my own problems with kernels. Anyway, you can also try flashing to stock or v1(previous version that worked for you), clear app data and go into superSU app and remove the permission to the app your using to oc and uv and hopefully that takes away all settings from been set on boot and give you time to set manually again. After everything is back to normal reflash 1v1b(c). Good luck!
[T-Mobile, Samsung Galaxy SIII] bofiana:
Did support on this kernel stop? Version 1.1b is has been running flawless for me on any ROM that I've flashed. Best combo of battery/performance. Better than any custom kernel I've flashed and no issues with sound or anything else that the custom kernels have.

Only thing that's missing is init.d support. I saw that the Dev said he was gonna try and get that working but that was a while ago so just wanted to check in. Thanks.
[T-Mobile, Samsung Galaxy SIII] noellenchris:
Wondering the same thing as this kernel just works better for ME on the rom i'm using. I've tried all of them too. It's simple and great. Hopefully the dev updates as I'm no good at kernels...:P Thanks for all you've done so far OP!

Noellenchris
[T-Mobile, Samsung Galaxy SIII] seshaz:
Good battery life but for some reason after a while my keyboard lags like crazy
[T-Mobile, Samsung Galaxy SIII] numba1cuban:
Same thing happens with my phone. How are u making the settinds stick tho? Every morning I gotta go in and re set the min and max and that is the only way the phone runs and has amazing battery life. I am getting about 16h of battery life without hesitation with this kernel.
[T-Mobile, Samsung Galaxy SIII] bofiana:
System Tuner Pro works great for me. Never had a problem with settings not sticking.
[T-Mobile, Samsung Galaxy SIII] noellenchris:
I've been using the free version of CPU Adjuster on the market, seems to stick with the profiles and it's minimal mem/cpu usage.

Noellenchris
[T-Mobile, Samsung Galaxy SIII] qais9:
Anyone kind enough to please link me to the first version v1? Thanks in advance.

The link in the op does not work.
[T-Mobile, Samsung Galaxy SIII] mike102871:
Ummm. Its in the original post.

Sent from GS3 if i helped hit thanks
[T-Mobile, Samsung Galaxy SIII] qais9:
The link in the op does not work for v1
[T-Mobile, Samsung Galaxy SIII] mike102871:
Check your PM. I sent you a link for it in my dropbox.
[T-Mobile, Samsung Galaxy SIII] marseillesw:
Does anyone have a link for v1.1b? All the links in the op are down. Thanks

sent from GS3 disguised as a GNote2
[T-Mobile, Samsung Galaxy SIII] LoopDoGG79:
I do, will PM you. By the way, this kernel works flawlessly on darthstaker. 1350-192, ondemand, sio! UV -75 :D

PM sent!! :D
[T-Mobile, Samsung Galaxy SIII] Nabeel10:
Can the next update include fast charge?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] bofiana:
I don't think this kernel will be updated. Haven't seen the Dev on this thread in a long time. Too bad cuz this kernel rocks and works flawless on any JB ROM I've flashed.
[T-Mobile, Samsung Galaxy SIII] dr.devman:
It has been a month and a half
[T-Mobile, Samsung Galaxy SIII] mike102871:
Downloadig 1.1b right now just fine.?

Anythig other than version 1 has always set my phone into bootloop on any rom
[T-Mobile, Samsung Galaxy SIII] Nabeel10:
This really is one of the best kernels, too bad it's not supported...

Maybe someone can take over?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] marseillesw:
Thanks bro!!

sent from a Galaxy far far away
[T-Mobile, Samsung Galaxy SIII] Nabeel10:
What cpu app do you guys use?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] LoopDoGG79:
ROM toolbox pro
[T-Mobile, Samsung Galaxy SIII] imilleson:
ROM toolbox pro keeps dropping my OC settings.... I checked set on boot and still Nada... also my deep sleep disappeared from CPU spy? Why Lol
[T-Mobile, Samsung Galaxy SIII] imilleson:
I started using NStools to control the clock settings. It seems to be sticking ...
[T-Mobile, Samsung Galaxy SIII] imilleson:
Actually NStools loses my settings on reboot.

------

Edit

Using "no frills" to control CPU, seems to work much better then NStools or ROM toolbox