yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
You nandroid is restoring a REALLY outdated ROM... Try a fresh install with the latest ROM in the ROM thread. Also, the gapps have been updated...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
Im not a flashaholic, I figured updating every couple weeks wouldn't do any harm, anyway I'm downloading as we speak the last version of the rom and the last version of the inverted gapps, thank you for responding, I will be back reporting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
The kernel has lots of new commits that are conflicting with your nandroid's ROM version...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anudist:
It appears to me that 10/9 and 10/9b do not work with nightly 10/14. Just flashed the ROM and, first, 10/9b which would not boot. Black screen after SIII splash screen. Flashed 10/9 and same thing. Reflashed nightly and perfect boot.

Sent from my pahoney.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boss Daddy:
CM10 Nightlies 10/14, just released, doesn't work with the current version of KT747. Flashed like I always do and this time it just goes to a black screen. Love the kernel, but just wished it work with the new Nightlies update.

Currently restored to a previous Nightlies and the kernel works fine again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Quick update kernel for CM10

Here is a new kernel for those of you that are updated to the newest CM10 and get the black screen:

http://www.mediafire.com/?wr0f47ax4xnx819
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Really fast thank you :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbmd:
Will this work on AOKP?

sent from Task & KT JB AOKP ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Not till next release, should be today, a little later on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] teesee150:
I just tried flashing the JB AOSP version of this kernal onto todays update of MIUI and it will not boot past the Samsung Galaxy SIII logo.

I flashed from external SD Card using cwm recovery, wiped cache, wiped dalvik, then fixed permissions.

After it wouldnt boot a few times, I rebooted into recovery and tried flashing again with no luck. Any ideas what the problem could be?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Come on man!!!!!! At least read THIS page!!!!!!!!!!!! Try the one from 5 posts up. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Trust me I feel your pain Lmao
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
by black screen do you mean sod?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Read the last page or two.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No, there were 39 kernel commits 19 rom commits for CM10/AOKP and the old kernel wont show video, new one does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Hey KT, if I'm getting screen flicker, it's probably too much UV, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Pretty much all of the JB roms have a flickering issue right now. Try disabling hw overlays in developer settings and see if that fixes it.

If not, knock the voltage up a little.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
I dont know if is the la test nightly or your kernel but now my screen flickers and with this Build i have poor perfomance

Enviado desde mi SAMSUNG-SGH-I747 usando Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Yeah the screen flicker was fixed on AOKP, but now it's back. Probably something to do with the 4.1.2 update, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
In the previous Build that was 4.1.2 there wasnt flickering and i notice this Build isnt as fluid as before

Enviado desde mi SAMSUNG-SGH-I747 usando Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
No flickering here and I'm on the latest version of AOKP released on Oct 13.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bkeaver:
What's the deleted_wake_locks. I'm seeing this in in better battery stats under kernel wakelocks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] grubby0:
Good info here!

http://xdaforums.com/showthread.php?t=1179809
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Tweaked my under volt some more this weekend. Been testing / running smooth all day,

so far

. Gave it a 2 hr. scaling test and some "real world" tests; no reboots so far (*knock on wood*). Battery has been the best I've experienced so far too.

If you try this, remember to make sure you disable "set on boot" so you wont get caught in a loop, if your phone doesn't like the settings. ;)

ROM: AOKP 10-13

Kernel: KT747 AOSP JB 10-9b

Kernel Settings:

Min = 96 Mhz

Max = 1728 Mhz

Governor = ktoonservative (stock adjustments)

I/O Scheduler = deadline (stock adjustments)

Touch Boosters = Stock

Screen Off Profile = 486000

Vibration Strength = 100

Voltages:

1728Mhz = 1080mv

1674Mhz = 1070mv

1512Mhz = 1060mv

1458Mhz = 1040mv

1404Mhz = 1030mv

1350Mhz = 1020mv

1296Mhz = 1010mv

1242Mhz = 1000mv

1188Mhz = 980mv

1134Mhz = 960mv

1080Mhz = 940mv

1026Mhz = 920mv

972Mhz = 900mv

918Mhz = 885mv

864Mhz = 870mv

810Mhz = 855mv

756Mhz = 840mv

702Mhz = 825mv

648Mhz = 810mv

594Mhz = 800mv

540Mhz = 790mv

486Mhz = 780mv

384Mhz = 770mv

192Mhz = 760mv

144Mhz = 750mv

96Mhz = 740mv

Hope this helps.

Ktoonsez, I've never been able to under-volt like this on any other device... your kernel is da bomb!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maxrdlf95:
Neither on my device it restarts to low for my S3 :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anudist:
You rock, my friend. Thanks. Working perfectly here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Thanks dude, I'll use these as a starting point. I was never able to uv till 10/9b either. I've been working on it since I found out that I could, but only did steps 96-594 just last night. Since my results are pretty close to yours for those steps, you may have just saved me a lot of time :)

Edit: So far so good. Haven't tried any settings over 1350 (I don't go that high, haven't needed it) but 96-1350 are working so far :) My 96mhz step actually tolerates 730, so I'm hoping that trend continues through the steps and I have a little safety margin

KT, I can't thank you enough for 10/09b. I don't understand half of what you did (ok, I don't understand 1/8 of what you did) but it fckin worked man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
I've been under volting since this kernels release, just tweaked my settings some more. :)

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Ah, see I've been trying on every release. Something KT changed on 10/09b (linaro -O3, whatever that means) made it so I could. Previously my phone wouldn't tolerate -5mv on most steps or -30mv on any step.

Every time I tried; the "Apply" button became the "Reboot" button, as in: as soon as I hit apply the phone rebooted. No errors, no glitches, do not pass go, do not undervolt at all, lol.

In fact the first few releases I tried, I had to up the voltage and set the minimum cpu freq to the 384 step. I have one of the semi-nasty phones that barely tolerated the kernel up to about mid-September. I could make it work, and it was very stable, and did help with the battery life, but I couldn't get at the really cool stuff till 10/09b. Somewhere in September, he made it so I could utilize the 96mhz step reliably (as in my alarm still went off in the morning) and that was very happy-making, but I'm simply over the moon with 10/09b.

In fact... Now that I think about it... You're the one I was always jealous of, your name finally registered to me. You're also the one that taught me not to use set at boot, lol! I tried one of your earlier voltage tables a while back and spent the next 45 minutes figuring out how to get it to quit looping.

Edit: I suppose, just in case any of this info is relevant to KT or anyone else, I should post whats different on mine:

I only use the 96-1350mhz steps (I use an otterbox defender, so I'm worried about heat)

Ktoonservative/noop (I don't know enough to monkey with their adjustments)

touch boosters are off

screen off is set to 96mhz (I think I may change this to 486 if anything goes sideways on me)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Okay guys, tonight I am going to go balls deep with KTweaker. Few questions before I get started. For some reason search isn't working for me (just a blank page), and google search within the site isn't helping at all. They should be pretty easy to answer for you veterans. I have done plenty of OCing and UVing with computers, but phones is a whole new world to me (iPhone convert here).

My goal is better battery life. I plan on undervolting but not overclocking (I think this is the right choice for battery life, but correct me if I am wrong). In the future if I need more processing power, I can OC.

1. When I start KTweaker, I sometimes get an error saying "Your something does not match current, apply something value? I get this with a bunch of settings. What gives?

2. What is the best governor for battery life? I am currently on ktoonservative, being that KT made it ;) and the fact that I have seen it is pretty good on battery life. Is it a good idea to think about changing any of the governor adjustments?

3. I/O Scheduler. No idea what this is, and I can't seem to find any information on it specific to android phones.

4. What touchbooster settings are good for battery life, or doesn't it really make any difference?

5. When I UV/OC... how can I check for stability? Are there stress tests that are recommended, or just using the phone for a few days to see if it is fine?

6. Should I decrease my max clock? I notice that I barely run at it based off betterbatterystats, but I really have no idea how much of a difference it can make.

7. When I flash a newer ROM version (task650's AOKP) or upgrade the kernel, will the same settings work, or should I redo the whole OC/UV?

Thanks a ton guys, really looking forward to getting into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
Here is some great literature on governors, i/o schedulers, etc. http://xdaforums.com/showthread.php?t=1369817

Sent from my GS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Screen Flicker

To anyone with screen flicker, you should be running the one I released today ONLY on CM10 from 10/14. THATS IT, NO OTHER ROM's. We will be updating AOKP today or tomorrow and then that one will be on the list too. :good:

EDIT:

not gonna release AOKP today. It is horrible from what task has just told me. The new QCOM display updates are just aweful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] psloan:
I have screen flicker on my TW (stock sammy rom) even after today's update. Only place I notice it is while using the facebook messenger app, typing in a message. Have not noticed it anywhere else, but I honestly have not bee looking to hard for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigal1542:
Thanks a ton guys. I will get reading and getting into all this fun stuff :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dankest:
Will this kernel work with paranoid android?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amf66:
Yes. Use the AOSP kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
24hr and no problems. Don't really notice a speed difference though as before it was lightning fast also (apple is going to sue me for using the word lightning now)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Most of the speed increase is aparent in scrolling, especially web browsing and XDA app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yep. After 9.5 hours straight of trying to get today's release compiled I finally got it to work. But all the new gcom commits I merged created some major graphical glitches. Definitely not something we will release. Gonna start fresh in the morning and see what happens. Ugh...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I didn't run today's build. I was getting flicker for a couple of days before on 10/9a. Not complaining or anything. Just wanted you to know I'm not THAT dumb :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
I got 2 reboots today on this build. The 10/9 build is stable. I guess no o3 for me...

Thanks for the awesome kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Leandre20:
hey i have cm10 m2 but im not sure which kernel download to use can someone point me to the one to download

I have the us version of the s3

d2att

S3 I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rocket Nine:
AOSP JB. Try the alternative version posted a few pages back with the -O3 flag if you don't mind looking for it. That may yield better performance over the standard release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I have searched around a lot and I can't find out what exactly isthe above hispeed delay in interactive governor. Someone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
42
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
10/9b fixed screen flicker for me... and I UV'd by 25 more :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theraker007:
Apoligies if this has been asked before but search isn't working on my phone app:

The main post says that the tw jb version weekend in frosty jb. I just flashed kttweaker on the fresh rom but the app won't open. I tried clearing data, restarting, and reflashingwithout success. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sguerra923:
Can you give us you current numbers for your UV. Just curious where your at..Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Well actually it didn't really fix screen flicker lol I just got a bit in XDA app. But I'm about -100 on all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
And old solution around here, but disabling hw overlay in Developer Options solved the screen flicker issue for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drothenberger:
Audio crackle gone with pegasusq

I've always had problems with audio crackle, especially over bluetooth, when I'm undervolting. (I'm using the TW kernel and LH9 stock.) I had been using smartassv2 and sometimes ktoonservative and I always found that I got crackling unless the voltage for my min frequency was above 925mv. My solution so far has been to have a saved configuration that increases my min frequency to 702 (the first one with a voltage above 925mv in my configuration).

Yesterday I decided to experiment with pegasusq and found to my surprise that the crackling was gone, at least when the screen is off. The crackling comes back as soon as the screen is turned back on. My mainly uninformed guess is that pegasusq is taking one of the CPUs offline when the screen is off and that is somehow preventing the crackling.

I'm not sure if this info is useful to anyone, but I figured I'd throw it out there anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Anyone else having this issue where when using Google Navigation (maps) the phone will reboot by itself after

about 5 minutes?

It only happens with this application and nothing else...

Thanks

(btw i'm on Touchwiz ICS VERSION)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Why does this belong in a kernel thread? and no... no issues with the Maps... Clear all it's data...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
......ugh?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Because it didn't happen before I installed this kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Try clearing all it's data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
Happy to report running 96-1512 mhz, lots more UV than before and stable on the O3 version for ICS Sammy. So far for me this had been the best kernel. I had random reboots with 10/9 O2 version with no UV, on anything set lower than 384mhz. Superb response and battery life so far. Only ran this 1.5 says so far.

ROM is same i used before, Wanamlite 1 2. LG1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jerrygooch:
So just tried the aokp ota updater, which is pretty nifty. Has anyone had the updater also install the kernel? Or would it be better manually flash the kernel after?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
It could probably be flashed along with the gapps, but you'll still have to clear the caches and fix permissions... I prefer to manually update still... and I flash the kernal after the gapps...

How's your UV going? Always been a fan of you and Swiftks UV settings...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akates:
I've been using this kernel for a month or so now with the ktoonservative governer and love the battery life, but I'm continuing to have issues with my Slingplayer app. On other governers such as ondemand or smartassV2 the video is smooth as can be, but with ktoonservative it's extremely choppy. Any tweaks I can make to ktoonservative to make video smoother while still keeping the great battery performance of this governer?

I'm also continuing to have issues with bluetooth audio skipping every minute or two when connected to both an A2DP source and my car's Handfree source at the same time. As soon as I disconnect the car's Handsfree, the skipping stops.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Undervolted? You'll probably have to raise your min Mhz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ARchamps:
Hi. I'm currently on Ariel 2.10 on the stock kernel. Using the custom kernel from that Rom caused mounting problems for my 64gb sdxc class 10 card. Are you aware of this kernel causing similar issues?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
Format it as FAT32
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] akates:
Removing the undervolt seems to have worked for the Slingplayer, still don't know why it would affect one governer and not the other! Anyways Slingplayer is working smoothly now! :good:

Any ideas on the bluetooth issues? This happens when running on either this kernel with defaults or on the CM10 kernel packaged with AOKP. Haven't tried stock in a while, but I think it happened on that as well. Don't know if there is a fix for it anywhere?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Bluetooth is the same issue, too much undervolting. In some cases that doesnt even fix it either, you just got one of the unlucky phones if it doesnt go away after returning all the voltages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
Wait what? I was going to flash this kernel, but apparently it can now cause permanent damage to my hardware? Ahhh what are you talking about? I just need a heads up lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
WHAT??????? I am not talking about damage at all. Some phones can run this kernel some cant. Especially with A2DP, some people just cant get it to work without static.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
He's saying some phones can't UV/UC like others can...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
hi

what are the main differences between this and the other task and koot AOKP rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
This isn't a ROM. Its a kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeesubalpha:
in b4 "my phone wont boot"

seriously though, save yourself some grief and read through these forums, rootzwiki (google it), etc before doing anything to your phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] teesee150:
With the latest kernel (10/14 for CM10) and MIUI, whenever I'm running a theme, or I'm using the 'torch', my phone will reboot, but it doesn't reboot completely. It goes black for a split second then displays the MI/Xiaomi logo and only takes about 15~20 seconds to get back to the main screen. It doesn't display the Samsung or Galaxy logos like a normal reboot would.

I've tried adjusting the overclock min/max and undervolting with no success. Everytime I use the torch, after about 15 seconds, the phone will do the issue I describe. Also, whenever I have a theme, about 1/2 the time when the phone wakes from sleep, it will do the same thing.

I do not exhibit any of these issues on a stock kernel. I've tried searching, but I haven't seen anyone else talk about a similar issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You are gonna have to expect those kind of things with MIUI. They are CLOSED source and mostly based on Touchjiz. You can try to do a full wipe and see what happens but like I said MIUI is CLOSED source so it is almost impossible to pinpoint the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corythug:
Our miui is based fully on cm10, not touchwiz, but yeah the actual miui part with it being closed source makes an issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Good to know, at least they got off the Touchwiz part. When I was making for the SGS2 (SGH-I777) guys it was Touchwiz based.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gangpe:
Hey ktoonsez,

Big fan. I'm on the latest pa (CM10, 4.1.2). Should the 10/14 version work with this Rom? Got the black screen, and it never got passed that.

If it should work, any suggestions? If not, no biggie.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If it goes to a black screen then no it wont work and that means that they have not updated to newest CM10 standards.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gangpe:
Got it, thanks dude. Might have to jump the pa ship to get some sweet, sweet fast charging...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
I have this weird issue and I'm wondering if I'm the only one. It's been happening on every kt kernel update I installed. If I start my day with a full charge, I get good battery life. Then, if I have to reboot for whaterver reason, after the reboot, my battery starts to drain real fast. I check battery stats and my phone doesn't stay awake or there's no app that seems to act crazy. All in all my phone seems to act normally after reboot but I get huge battery drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
it's a ****load of pages hahah
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geomax45:
Did you check out MediaScanner service to see if it was running continuously?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Yeah, I checked, it ran for 4 min but hasn't done anything since. It's really weird, no application itself is running non-stop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
2 days on this - 02 oe whatever tw kernel and still everything is perfect.. Not sure if others are using it but as far as I can tell this is ready for mainstream...

But still don't notice a difference in xda scrolling (a bit choppy, always has been) though web is fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ziizy:
Hey I'm using liquid smooths ROM today,does anyone know whether to classify this as touchwiz or aosp?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lsusparky621:
C'mon man, why wouldn't you post this question in the Liquid Smooth thread? Just read. For your answer, see the screenshot below from Liquid Smooth OP. "CyanogenMod" is AOSP based.

Give credit where credit is due...and hit the THANKS :)