yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thats should most definetely be the case. Touchjizz ROMs are 500-800mb and CM/AOKP are 140. Touchjizz also runs about 20-30 background processes where as CM/AOKP run 3-6 background processes. This is of course stock installed without adding any apps. If you add apps that run background processes then the count goes higher.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
always curious if thats your C6 in the avatar Ktoons...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] edmondt:
Grrrr....

My setup seems too perfect now to change; FreeGS3 R6 ROM + [9/5/2012] KT747 - LG8 Kernel.

Will wait till the screen flicker is really fixed on CM/AOKP :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Everybody has there favorite's :D. The screen flicker is gone everywhere in CM10/AOKP on stock kernel. It is also gone on mine if you do no underevolt or UC :(. Still havent figured out if I can fix that. All this new GPU driver stuff is KILLING me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Absolutely. Tw/stock I had to turn off and uninstall a massive amount of crap, and enable battery saving mode. Meaning I had a single core phone with no haptic feedback and (IMO) an unreasonably dim screen.

With aokp/kt747 I have all of the features, including the dual core processor turned ON, and I have comparable battery life.

Bear in mind too, that I'm flashing something at least once a day, so I've never given aokp/kt747 a chance to actually full discharge and charge on any one release. I expect that if task and KT cut me off for a few days, my battery life would smoke stock/tw and never look back.

As it is, it comes off the charger when I get up, goes back on when I go to bed, and in spite of very heavy use, hasn't run out on me yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
I dont undervolt or uc and still get flicker.... hmm..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theraker007:
i flashed the 9/5 kernel over my tiMIUI rom today and everything was going great. then later on i happened to open ktweaker again cuz i wanted to try another gov and soon realized that the tweaker app now refuses to open for me no matter what i do. I tried reflashing, fixing permissions, wiping caches.. nada.. short of reflashing the entire rom, is there anything else I can try to get the ktweaker app open again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] esoteric1311:
Whats the weather/clock widget you have?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
AOSP Jelly Bean couldnt boot up the first time I got black screen but just booted up now and seems to be working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Clear app data for KTweaker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
What's recommend set on boot and what CPU governor is most responsive and uses least mhz when screen is not touched. I'm on ktoonservative and want to know if theres better?

Also what's best delay for boot

I must say I only use this to use CPU governor nothing else just b/c of UV issues and phone is fast enough w/o OCing very well done Ktoonsez!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I like my governor the best, second favorite is ondemand. I added the time selection for the "Set on boot" so each phone could do its own thing. Works on mine everytime at 5 seeconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sicmadek:
which aokp rom is everyone using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
task's and mine :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sicmadek:
thats jellybean. what about aosp ics?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Im building a stock CM kernel at 192mhz to prove it one way or the other
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paganen:
Kernel Modules

I need to compile some kernel modules (usbnet and cdc_subset). Do you have the source code for your kernel available somewhere?. Since I am using the sammy version, can't I just change some version string in the make file (of the Samsung kernel source) to compile my kernel?.

I love to have the OC capability but I also need to have the those kernel modules for my stuff.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
What do u mean?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theraker007:
worked.. thanks. Everything's running so great now I can't believe it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
My CPU spy says most is 96 mhz although my set is lowest at 384 mhz is this okay for the phone, i'm guessing it's part of ktoonservative or the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Which io scheduler is everyone using with ktoonservative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hallo13th:
What does disable hardware overlay do? When I enable it my flicker goes away. Using latest ktoonsez kernel and aokp from k and task.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I modified the CM kernel code to have a minimum of 192 instead of 384 and set the voltage to 875 and I get the flicker on CM10 kernel too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbmd:
Noop

sent from Task & KT JB AOKP ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
what theme is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
It's the very first search result and most popular free theme that pops up when you search Play for "cm10 theme". It reminds me a little of KDE/Linux from a few years ago... and not in a good way. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Ever tried Blue Infinitum? Simply amazing combined with inverted apps... Is that one pretty blacked out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
No, reset timer with menu button. 96 shouldn't be there at all if it's not being used
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
I've been using JB Extreme . Its great with Tasks JB ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhostetter:
My modified Cobalt theme. Cobalt is on the market.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Running FLAWLESSLY at 1080mhz. I don't game, just browse using chrome, text a lot and listen to podcasts whenever I'm awake. I really don't see any difference at all besides benchmarks underclocked this far. No reboots, lag or stutter. Nova launcher and animations at .5, I'm living the life. Battery really couldn't get any better, if i could only run aokp for more than a day before a nightly is released by task, i might be able to get a better day out of it, but zero complaints. Screen off min is set to 192mhz. Ktoones, i was wrong about ktweaker being the problem, it definitely is quicker with the latest kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] papibone5:
9/5 is a big improvement over 8/31. I been running the Sammy version all day on stock Lg1 OC @ 1.720ghz w/ Pegasusq governor & Noop. Lag free no reboot and the phone runs smooth as butter compared to the 8/31 version. Thanks Ktoonz

Sent from my " Whichever Device I'm using right now"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
+1 to this but on aosp. Ktoonsez thank you so much for this kernel and aokp Rom you update very often a and yeah just really appreciate your work and just donations for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcejohnson:
I loaded 9/5 last night on top of 8/31. Had an unexpected reboot around 1:30PM. Was listening to Pandora on and off for hours both plugged into the USB and not. Was plugged in at the time of the reboot.

Using noop/ktoonservative, 192-1512. Voltages are 875 for 96-384. Everything else is default.

@KT -- Great work, thank you!

Edit: Running Nostalgia 7.4 ICS ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Greycloak42:
Flashed the 9/5 Sammy and had problems with ktweaker force closing. I cleared the data and it worked until I rebooted. After clearing data a second time it works great. Great work on the kernel. I'll throw some money at you as soon as I'm able.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] swpreiy:
i flashed the new PA 2.0 and the 9/5 kernel but it says im on edge. it was working prior to either of them.

any ideas or suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Full wipe. I know its not the kernel and probably not the ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcejohnson:
Just got a second reboot. Roughly 9.5hrs from the last. I grabbed a logcat immediately after boot. Is there anything else I can capture to help out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
Here's my battery stats for the first full day running the new kernel, longest I've ever ran!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Logcats r no good on random reboots. Need the /proc/last_kmsg file. And only post it if or not UCing or undervolting. If u r then u r doing too much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
I've had about 8 reboots today trying to get my uv as low as possible. Lol

Ktoonsez if it's not to much trouble can you make the phone run at 2106mhz all the time but use only 700mv on the next release.

;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
U got it :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
i got all the way down to 730 and no 800 until the 5th or 6th step... but the phone slept so deeply, my alarm never went off... phone wouldnt wake up due to radical UV settings...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
I raised them some... hopefully im not late for work tomorrow again...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tyshemi:
That's freaking hilarious I've actually done that myself lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Well after catching up and reading the last several days (week ) of posts I see 8-31 was problematic for many...I too started getting lag and camera issues and for the first tine, ktweaker settings that won't stick...but i see ur at 9-5 now so gonna flash that and hope all is back to normal.

As for those who are doing the crazy UV and getting it under 750mv I'd love to see some real stress tests and on full scalability too cuz I guarantee it'll fail..that's why its important to find that zone that gets the mv as low as possible for battery life but is 100% stable with everything and every test...not to just say well I can browse and play music... but it may reboot or freeze on other stuff it the alarm won't work when asleep...what's the point...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bravomail:
commend your work

Running ICS 4.0 on CM9 - very good battery life with noop-ondemand or noop-PegasusQ, and very solid and stable kernel.

Max Overclock won't stick - returns to 1500. Just reopen KTweaker to confirm that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Just set my min & max to 96 MHz, and stress tested at my normal 740mV... No reboots. Been running it at 740mv with no problems for over a week. Also, i was away for work this week in a hotel, and used my alarm with no issues.

Since i was testing, I thought I'd see if I could get it to crash at a lower setting. I know it reboots at 725mV from previous testing, so i tried 735mV, and it kept on going; no reboot on stress test. Think ill keep it here. :)

I love this kernel!

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
I had the same problem on 9-5 playing with stock touchwiz. even though I locked in settings in ktweaker 1674 and 384 no UV .interactive and cfq. according to CPU spy it would hang around 1500 and 384. when I would open up ktweaker each time it would tell me my current clock settings doesn't match my set clock settings. only using ktweaker and cpu spy. other then that it seems to work great..deep sleep was good. and no random reboots. just not for the life of me could get the clock speeds to not change. tried wiping data for ktweaker and uninstalling ktweaket and re flashing the kernel. but each time the speeds would change back on me again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s2556:
I have 96 uv at 725mv. It is still stable lower then that but I haven't finished all my testing on lowering it further because this is pretty much good enough for me. my first 7 steps are below 800mv. I have been running this voltage table for about a week and haven't had a single reboot or missed alarm. I also have it OC'd to 2ghz. My phone loves this kernel. I stress test it all the time with benchmarks and 3d games etc my phone flies through it all! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] swpreiy:
I did a full wipe and went back to stock. It didnt get any better, then I went to the custom stuff, and it was just a smidge better. should i just take it in since its under the 30 day warranty?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheShamsMan:
Hey guys. I'm looking to flash this kernel. I'm sorry if this has already been asked, but can someone tell me what it means by "fixing permission"?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
Go to cwm and under advanced ull see it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RTBee:
I love 'ull'. I've never seen that before, but I'll be using it, thanks! Amazing the stuff you learn here. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
What are your voltages for all your frequencies, if you don't mind me asking.

I know yours are quite dramatically low, but I want a base to start at and increment up if necessary. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hello all, I'm fresh on the S3, long time S1 captivate user.

cm10 9/7, 9/5 kernel

first things first, I did get the screen flicker when I dropped the frequency to 96 and undervolted to the specs on the 3rd post, middle column. I used KTweaker to put the freq back up to 384 and was getting flicker, don't know if this has been posted, but i went to recovery wiped cache partition, wiped davlik cache, and fixed the permissions. when i rebooted everything was looking great, no more flickers.

(i'm almost positive this was my procedure, because soon afterwards i flashed the latest 9/7 nightly....) anyways, re flashing the kernel should temporarily solve your issues.

I thought I'd share some things to help you trace out the frequency usage, this was very helpful when i was setting the minimum frequency. There's an app called cool tools that i have found to be the most helpful app for tuning governors and tweaking performance.

http://play.google.com/store/apps/d...ult#?t=W251bGwsMSwxLDEsImRzLmNwdW92ZXJsYXkiXQ..

You can set a small floating window anywhere on the screen telling you your current operating frequency in .5 second intervals. So that can give you a dead on answer to what your frequency is running at. I've never trusted CPU spy.

I remember on my old captivate there was a text file located under /system i think way in there that would list out what time the cpu had been running on certain frequencies. That text file shouldn't lie and it won't take the nominal amount of resources that cpuspy uses. maybe I'll go find it's location.

anyways loving the kernel, loving cm10 loving the S3. Thanks XDA!

EDIT: I found the text file. I'm not sure if it's in mili seconds or regular seconds, but regardless here it is. /sys/devices/system/cpu/cpu1/cpufreq/stats/ then open time_in_state.

there's two folders, one for /sys/devices/system/cpu/cpu1 and another for /sys/devices/system/cpu/cpu0. I'm almost certain it's for the different cores. looking at my two different files the one in core0 has much more time across all the frequencies. so it's operating as it should, only using two cores when needed :)

Hope this helps someone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
You'd be better off to use CPU spy or the app linked in the post above or something to watch your most used frequencies and start nudging the voltages on those freqs down from stock, rather than up from a massive UV. I believe him when he says its stable, but that kind of UV tolerance is very rare. I think the voltage tables were posted to this thread a while back though if you want to try them.

My most used frequencies could only handle -50'ish. From there apps started to malfunction and I started getting reboots. I tried jumping straight to his voltages and it was like pushing reboot as soon as it switched to the uv'd frequencies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
Impressive ..... just broke 7hrs screen time. See below post ;)

Cm10 nightly 9/7

1350max

144min

Ktoonservative

Cfq

Auto brightness

Many texts

Browsing web

Flip board

the verge

Engadget

Twitter

Few phone calls

Emails ect.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
What's that theme, looks rad
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
Arctic Grey
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Damn dude... I was impressed with 4-5... 7 is nuts. Nice work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hokiemoto:
Another one here where top OC 2106 just eventually returns to stock 1512 on its own. It can randomly be within minutes or within hours. Using CPUspy/antutu to confirm.

When going back to KTweaker, it says your current doesn't match your saved - would you like to load your saved? I can say yes, and/or manually load OC again, but it doesn't ever actually go back to 2106 unless I reboot.

I'm on 9-5 and stock UCALH1. I've tried flashing stock kernel, then back to 9-5 clean, since KTweaker app can't be uninstalled---to no avail. thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jcejohnson:
I'm at 25.5+ hours uptime now & all seems well. Set my min clock to 384 w/ no UV and everything *should* be at default -- at leadt, that was my intention. If it flips out again, I'll post last_kmsg for you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Have you try OC to 1,8ghz to see if it stay?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MWilkenson:
Does the version of CWM change if I flash this kernel? Im currently on the 5.8 version of CWM and was trying to find a way to get to CWM version 5.5.0.4 in order to properly use the OTA on AOKP. Put simply, does the version of CWM change based on kernels I flash or do I flash a separate .zip file in order to get an older version of CWM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] s2556:
not on kernel seperate .zip file
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] papibone5:
Try that I'm OC @1.720ghz and it sticks never change on me yet I'm on stock LG1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
---------- Post added at 07:14 AM ---------- Previous post was at 07:05 AM ----------

+1

exactly same experience with me. If I don't respond yes, it leaves me uc'ed to 96, but resets my oc to 1512.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cloudyphiz:
An hour and a half off the charger and 47 minutes of screen time (web browsing/tapatalk mostly) and my battery is at 90%. Crazy... I never would have believed a 7h screen time but now I see that it's possible.

I'm using noop/ktoonservative with two speeds above and below the defaults and all UV by 50mV. Extremely stable and smooth. Many thanks to ktoonsez.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Second that. Finding Ktoonsez's kernel completely changed my experience with the S3. I'd been a Blackberry user since the early 2000s and loved my highly tweaked BB for endless battery life and effortless typing, but I'd clearly outgrown the platform's capabilities. That, and was tired of tweaking on my wife's LiquidMT...

The move from Blackberry was made painless by two things: Swiftkey, and KT's ROM. TitaniumBackup would be the third for allowing me to easily debloat.

I've settled with cfq and ktoonservative, and am running reboot-free down to 92mhz at 770mv.

Thanks KT!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gfrt94yn:
Alright so I decided to go crazy and switch from CM10 (AOKP) to MIUI; I've been curious to try this out for quite some time, but it's had too many bugs for my taste. Another reason I've hesitated is because I love buttery smooth animations, overclocking, under volting, and all that good stuff.

Anyway I'll get on with it, first a few questions:

Is miui aosp based? In other words, can I flash the aosp jb kernal? (update) Yes, you can. I just did, but none of the settings stick and for some reason the over clock won't work either, even though the box is checked. Another problem I have is the wonderful force close of the ktweaker app; just happens randomly but it seems like the remedy is to wipe dalvik/cache and fix permissions (sometimes works).

Anyway I don't mean to come across as a complaining winey-baby, I love your work and all that you've contributed to the XDA community, keep it up man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] socalforlife:
$5 goes to whoever can help me with my issue, I'm on DietIcs rom, flashed the 9-5 kernel, was on the previous version of this kernel, I wiped cache / dalvik and fixed permissions, for some reason I tried using system tuner pro / setcpu / ktweaker but they aren't letting me go above 1512mhz, now I do LOVE the 96mhz setting, pretty cool but I'd like to go higher than stock 1512, here is a picture of what it looks like, some reason its just not letting me go above it, weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
You need to check the "enable OC steps."

Also my phone seems to hate the 96mhz. I always get reboots. Bleh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Enable the OC Steps. Its the top check mark bro. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] socalforlife:
Thanks man, Am I able to change voltages on this app KTweaker? Also here's Paypal - Payment Sent (Unique Transaction ID # 8CE72877BL767472X)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes, from the main screen, click on Voltages. And you can change the voltage for every Mhz step. Thanks for the bucks :D