yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
YOYO

Yoyo effect explained visually

Thanks to "haveagr8day" for posting up a kmsg file I can should you what all of us dev's are dealing with on 4.2:

In simplest terms, left of the decimal is number seconds the phone has been up and right of the decimal is microseconds.

You can the stupidity of the yoyo effect coming from the system "cpu_load" calculations. Line 1 has CPU load at 100%, about 100 milliseconds later it thinks its 14, then 50 milli's later 21.......... and so on. So the first 7 lines show that the system think the load went from 100 to almost nothing to 99 to almost nothing again all under 1 second. And as you follow down the list it just keeps doing the same thing forever and ever!!!!!!!!!!!

[ 9060.019226] cpu_up 100 - 83

[ 9060.269219] cpu_down 14 - 45

[ 9060.319242] cpu_down 21 - 45

[ 9060.369753] cpu_down 36 - 45

[ 9060.520188] cpu_down 44 - 45

[ 9060.669249] cpu_up 99 - 83

[ 9060.919242] cpu_down 32 - 45

[ 9061.169264] cpu_up 100 - 83

[ 9061.519242] cpu_down 23 - 45

[ 9061.569234] cpu_down 31 - 45

[ 9061.619257] cpu_down 41 - 45

[ 9061.719211] cpu_up 86 - 83

[ 9061.969295] cpu_down 40 - 45

[ 9062.019196] cpu_down 43 - 45

[ 9062.069341] cpu_down 42 - 45

[ 9062.120127] cpu_down 44 - 45

[ 9062.219287] cpu_up 100 - 83

[ 9062.319242] cpu_down 38 - 45

[ 9062.469341] cpu_up 85 - 83

[ 9062.670043] cpu_down 41 - 45

[ 9062.819867] cpu_down 35 - 45

[ 9062.919303] cpu_up 84 - 83

[ 9063.019226] cpu_down 27 - 45

[ 9063.069249] cpu_down 44 - 45

[ 9063.169356] cpu_up 99 - 83

[ 9065.019226] cpu_down 42 - 45

[ 9065.219287] cpu_up 94 - 83

[ 9065.519303] cpu_down 42 - 45

[ 9065.569203] cpu_down 40 - 45

[ 9065.619196] cpu_down 40 - 45

[ 9065.669890] cpu_down 40 - 45

[ 9065.869249] cpu_up 95 - 83

[ 9066.119211] cpu_down 44 - 45

[ 9066.369325] cpu_up 95 - 83

[ 9066.469188] cpu_down 24 - 45

[ 9066.519211] cpu_down 36 - 45

[ 9066.669249] cpu_up 98 - 83

[ 9066.769203] cpu_down 32 - 45

[ 9066.819196] cpu_down 38 - 45

[ 9066.969234] cpu_up 92 - 83

[ 9067.269219] cpu_down 41 - 45

And the worst part of all this, is that the phone was probably in his pocket doing all that yoyo s.hit!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android2.0:
back up

hey ktoozes

as you mentioned the blue tooth and wifi is updated. if i have a nandroid of my stock rom and i restored it... would be go back to normal and have the bt and wifi drivers.????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Yes. Or flashing any ROM would do the same. That's an old message ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
Am i the only one having issue playing youtube video with the kernel 1/8 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Just watched two without issue. 1/8 build, Ktoonservative/ROW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XblackdemonX:
ok ill make more tests then. thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I just watched 1 without a problem.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Latest update is working flawlessly.

Keep up the good work ktoonsez!

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
Holy hell is this latest kernel fast! Using ktoonsez settings with aokp. Running flawless and YouTube works also.

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Today's release is extremely responsive with Ktoonservative/ROW, - 75 UV across the board, and 486 screen off max. Keep up the flawless work KT! :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
Ktoonsez just fixed 4.2 :eek:

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks guys, glad this is working out so well :D :good:. Also hope you guys enjoyed the post showing the YOYO effect, seeing is believing, huh?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BTT8:
Lets get some screenshots on screen time and battery time!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
You're going to need to give us more time to accurately gauge battery life improvements from the update. I will reiterate that performance is incredibly smooth for me on 1/8.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
Has anyone tested with Face Unlock? I have 1/8 CM10.1, ktoon, row, -50mv and didn't set any screen off max but when I press the unlock/power button, the Face Unlock window sometimes pops up but it hangs at black for 2-3 seconds and then finally opens to show my face and then hangs there for another 2-3 seconds before finally letting me in. On stock CM kernel it instantly unlocks. I have my min set to 192 and max at 1512.

It doesn't happen every time but I would say over 50% of the time it does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mickskillz:
Any chance of incorporating these changes into your 4.1.2 kernel? or is development done on that? I Love this kernel and am just not ready to leave MIUI and it's stuck on 4.1.2. Thanks for your great work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
All of this stuff I am doing is to FIX 4.2. 4.1 is perfect (other than that stupid screen wake issue) and does not need all this crap. I will be releasing all versions soon, you will get zen and row scheduler and a few CM patches.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Thanks for bringing back project butter ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milicigoran:
Where can I adjust the yoyo=1 and cpu_down_cycles=22? Sorry I don't see that any where in ktweaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
General -> Governor Adjustments, assuming you're running ktoonservative.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Ktoonsez idk if my device just doesnt like ur kernel but running ur aosp stuff causes my screen to go mad nuts. Then i have to lock and unlock. It got really bad so i had to flash stock cm kernel which doesnt have the issue... But my battery life isnt as good and we all know ur ktweaker and settings are dope af. Any possible idea on how to fix?

trolol and awayyy!! Expect typos this is my phone.

running ultimatum, cm built by me, other cm if im lazy, or task if im adventurous and bored. also hit the thanks because u can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
Be sure to wipe cache/dalvik + fix permission right after the kernel flash. Otherwise it might do strange stuff like that.. and be sure you downloaded the 4.2.1 AOSP version. Mistakes happens sometimes.

Sent from my toaster
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Is it bad for a core in a CPU to turn on & off quickly? Is it bad for the CPU? Does it do any damage or shorten the life of the chip?

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidFiend76:
Ktoonsez, what do you recommend on what scheduler I should use for possible better battery life?

I'm using the Ktoonservative governor.

Thanks ;) Great Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
+1. I think he mentioned this sometime back but this time it will be reassuring.. Both for two and aosp

---------- Post added at 02:08 PM ---------- Previous post was at 02:06 PM ----------

It would not effect the chip in near future but over the period it may effect the life. It's like frequently switching something on or off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Please use quote - those really don't make sense without context.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
I think he would recommend row.

Sent from the Dank Device, aka my GSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I did used quote but somehow the mobile app messed this. I will move back to browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I doubt it will have any issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
I am not having any luck with this kernel and the latest AOKP builds. After a full wipe and fresh install of both Tasks 1/8 built and the latest Rootbox, installing any recent version of this kernel gets me stuck in a boot loop.

I tried all the way back to the 1/1 build which had always worked for me before. Lean Kernel and stock kernels are working fine.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Dont install Rootbox! Wipe everything, install AOKP and let it boot, then go back and flash my kernel in its own session.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
Lesson learned. I thought I had done a full wipe before installing Tasks build, but I guess not. I'm back up and running. Thanks. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
That's def not the issue because ive done all this... The kernel works fine but i get random touch inputs sometimes that arent present in stock cm kernel...if it wasn't 4.2.1 it wouldnt really boot...

trolol and awayyy!! Expect typos this is my phone.

running ultimatum, cm built by me, other cm if im lazy, or task if im adventurous and bored. also hit the thanks because u can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Does Rootbox not play well with your kernel?

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I have no clue, no need for it so I never installed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Could this be kernel related? The only thing I changed is updated the Rom and then the kernel with yoyo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Are you talking about being at 67%? R u on AOSP? If so, are you using ktoonservative? If you are using my gov, did you delete mpdecision?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
Did you wipe data when flashing new rom? I suspect rom not kernel.

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Yes and yes with row and no not sure how to do that last part. The phone app is staying awake and I haven't made a call in a few days
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Just wanted to report that every time I exit out of a game (subway surfer) it gets laggy. The only fix is to turn off screen and back on. Lag is gone and all is well. Running ktoonservative. This probably atleast for me has been around for the past two releases or so. I'm sure you're aware of it. Just reporting it :D

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GalaxyHeart:
Happens with Underwear as well. I've noticed it since the 1/1 releases.

For me, games are laggy as well. A particular puzzle game I play (7 Little Words) refuses to update the screen on each touch - it updates every second touch.

For instance, I press a button - nothing happens. I then press a blank space on the screen (which should do nothing) and my previous button press is registered.

I can recreate this on any governor/scheduler combination, with KT747 or Underwear.

I blame CM. =P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Yes always
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I'm glad I'm not the only one lol. What about playing videos on the Web?

As soon as I hit the full screen button I have to put my phone on landscape for it to play. And right before I exit it, I have to put my phone on portrait mode then exit. Otherwise it won't let me leave until I turn off screen and back on lol. It's weird. I'm sure it's the rom and 4.2 lol

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok, you are talking about the phone app, ya that is definetely ROM. But you should delete the file mp decision binary anyway so its not fighting with ktoonservative, its here:

/system/bin/mpdecision
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Is deleting the binary advised for all for increased performance on Ktoonservative, KT?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Wondering the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes, but it only exists on certain AOSP ROMs. Not all of them have it. If you are on Touchjizz, you should delete the qosmgr file in the /system/bin/ folder.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JediSooner:
I assume renaming works as well as deleting it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geomax45:
I renamed and saw a huge settling down of the hotplug process immediately.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 1.9

1. Built with newest Linaro compiler so its EVEN FASTER (about 25 billion times faster)

2. Added Row scheduler to all other versions

3. Added Zen scheduler to all other versions

4. CM patches for AOSP guys

5. Thats all I can remember

ENJOY
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sure
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sun0fNothing:
Is there a 1/9 release and I can't find it? Or is it still 1/8 and the thread title is just wrong?

Edit: whoops lol I think KT posted the release literally as I was typing this post.

Sent from the Dank Device, aka my GSIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pat713:
Anyone else having Bluetooth media streaming issues? I stream in my car and it skips every few seconds, whether it's on Pandora or locally stored.

Sent from my AT&T Samsung Galaxy S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
This has been covered 1 million times!!!!!!!!!!!!!! Stop undervolting so much and or raise your minimum Mhz and problem goes away :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for the update of TW kernel. You guys rock all the time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pat713:
So if left as is there's not enough power to keep it stable?

Sent from my AT&T Samsung Galaxy S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Even for TW? I was unable to find any setting related to row in Ktweaker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I'm running the 1/8 Task build, is this what i should do if I want to use ktoonservative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
You can use Ktoonservative without deleting the binary, but doing so will further enhance performance. It can be deleted on the 1/8 Task and KT AOKP build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Can't you add a script to delete that file? Only asking
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
I installed the 1/8 version the moment it was released. I'm assuming there wasn't much change between 1/8 and 1/9? I'd hate to update if there wasn't any huge changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I don't think there were many major changes from yesterday's to this one, but for the few minutes it takes to update, I don't see why not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Just this patch from CM guys (its probably worth updating):

https://github.com/ktoonsez/KT747-JB/commit/f577a9eb23bb7b2c300c1cae8a1dba33c25e0360
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Not everyone uses ktoonservative so no I can't add that to the kernel install. Ill look around and see if I can create a separate one zip that only does the delete:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Fair enough.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Thanks for the great work ktoonsez, all the freezes and reboots are gone now thanks to the updates or my less aggressive UV. I would advise anyone that is experiencing freezes or reboots to not under volt quite as much as you did in 4.1.2. I had some insane -150 uv's on 4.1.2!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I'll give that a try. Right now I'm at - 125 lol so maybe that will help if I raise it by 25-50

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ImEVO:
So what are row and Zen schedulers??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Schedulers made for Linux. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
I did not think my phone can go faster ktoonsez. Bless you sir. Feels like my s3 CPU transformed into an i5.

Although I did read up on samsung new 8core CPU and their flexible oled screen. I can't imagine what the s4 is gonna be like

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ImEVO:
What do they do?? is what I meant.. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrvirginia:
ROW & ZEN

ROW stands for "READ Over WRITE" which is the main requests dispatch policy of this algorithm.

-The ROW IO scheduler was developed with the mobile devices needs in mind. In mobile devices we favor user experience upon everything else, thus we want to give READ IO requests as much priority as possible.

-The main idea of the ROW scheduling policy is:

--If there are READ requests in pipe - dispatch them but don't starve the WRITE requests too much.

ROW and FIOPS were designed for flash

ZEN

Q: What is the zen I/O scheduler?

A: Well, the question that was asked above led me to an analysis of V(R ), deadline, and some others. I already knew, but realized "this is the main feature of V(R), but wait it has no benefit to us smartphone users." So I thought about adjusting the way V(R ) handled requests and how it dispatched them (I chose V(R ) because i'd rather not tinker with a scheduler thats official and widely supported). Then I was looking over it, and realized I might as well just write a new one I don't need any of this stuff. So I came up with something awfully similar to SIO, although its a bit simpler than SIO (closer to no-op) and works just slightly different.

- It's an FCFS (First come, first serve) based algorithm. It's not strictly FIFO. It does not do any sorting. It uses deadlines for fairness, and treats synchronous requests with priority over asynchronous ones. Other than that, pretty much the same as no-op.

[can be found in context here http://xdaforums.com/showpost.php?p=33327389&postcount=3]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I was just kidding cus I wasnt at my PC to type it out, lol. Looks like someone beat me to it :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Not Trying to badmouth your work at all I'm just trying to let you know that I have had the worst battery life I have ever had on this phone after the 1/9 I'm going to fully wipe and try it again and see if it's something that I'm missing could it be the yoyo settings? I have them 1and 22
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Don't you need to give it three cycles (at least a couple) before really knowing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Dude I don't think an hour screen on time and 12 hours standby time is good regardless I have never had this problem and I have never had to wait three cycles something is wrong with some setting in the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I trust you since you have been around for a long while and yes you can tell when something is really wrong. Example: if you are 20-30% less than normal.

It could be yoyo. Did u ever delete the mpdecision file and reboot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Yes I did

Yup you can usually tell I don't expect to get 4 to 5 hours upon first cycle screen on time but one and a half is not good at all. Them wondering if yo-yo and my application called lux auto brightness is causing the severe battery drain I have it set on dynamic settings for auto brightness I'm not sure what else it could be hardly used the phone today and it died.

I'll try turning off the yoyo settings and use on-demand instead ktoonzservitive while charging, and listening to music won't let me unlock my screen without yoyo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Is there any reason to delete mpdecision on touch wiz or it a 4.2 thing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
It's an AOSP thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
With Touchjizz JB you should delete or rename /system/bin/qosmgr like it says in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Didn't you determine that the phone was staying awake? If it stays that way then you simply need a re-flash cause something ain't right. It's not the kernel unless at least a few others have the same issue... and it doesn't seem as though we do.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
Idle battery life has been superb. Probably better than 4.1 (for a change...)

Performance is through the roof. Running 1/9 aokp and your kernel.

Thanks for sharing your work!

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Using ktoonservative gov? If so, are u using yoyo mode? Just so others can see whats going on out there:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Running on Task and Ktoonsez AOKP 1/9 build with KT747 1/9 build. Ktoonservative/ROW, - 75 mV across the board. 96min/1512max, 486 max screen off. I've deleted the mpdecision binary and am using the yoyo.

I am seeing great battery life and performance. Smooth as butter, KT.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks for the report :highfive: :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] benefit14snake:
Yes I am using ktoonservative with yoyo. I am using the settings you recommended. I am using row for my storage.

Sent from my T999 GS3 @ 2. 1GHZ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
If it matters, I'm not using yoyo, ktoonservative, row, uv -125 across the board. Smoother than silk here. Big ups toons. Oh yeah, latest version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bustabo:
This!!!!!

Great to see u here!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Found the issue performance is on by default
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasvncnt1:
So we have to use setcpu to change it?

Zepp's V6 SuperCharger...I put that **** on everything
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Yes but I'm not sure it is still correct the minimum is too high and I do not know what's decided that I put the minimums the lowest setting hopefully it doesn't cause the phone to get stuck . As soon as I took it off performance the phone stopped being really hot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Forcepath:
Working fantastic! Thanks ktoonsez! Look forward to AOKP and all the joy of this community growing together just like when the sgs2 came out! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Im changing that this morning to use some of my Fluxi defaults. Gonna do ondemand and noop as defaults:D. The others seem to be doing the same thing, of course not as bad as performance though. Anybody that wants to do me a favor and go back to stock and check out cpuspy with it would be doing me a big favor:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
wifi isn't working as soon as flashed. On DIET ICS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
That's strange. I just flashed over Diet ICS and I am not having any problems with wifi?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
I know same here, then all of a sudden It stopped working .. and now the toggle doesn't even light up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
kernel. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jroyalty7:
I'm still on stock rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xhead:
Nevermind reflashed the Kernel and WIFI works ahah
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
I didn't see any mention of this, but is this kernel safe to flash for a Canadian SGH-I747 (Telus)?

Is it safe to assume that the flash won't mess with the phone's baseband?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jroyalty7:
Stock settings