yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] ktoonsez:
Re: [KERNEL][SPRINT][AOSP/TOUCHWIZ-JELLYBEAN][3/27/2013] KT747 - MA6 - KTweaker

Yes. A week ago
[Sprint Samsung Galaxy S III] JoeFCaputo113:
Damn! So those who have the latest test build (from last night) are still getting reboots/bootloops?? Cause I was JUST about to flash this lol.
[Sprint Samsung Galaxy S III] maxima2k53:
I using the latest ktoonsez kernel with cm10.1 3/31, working great.
[Sprint Samsung Galaxy S III] mw86:
I am on a clean install of CM nightly 4/03 and the test kernel update above no reboots since last night and so far today. Maybe you should try a fresh download of both and a clean install or use the 3/31 recommended above? We tested on this build before release to my knowledge. Please let us know if your still having troubles after troubleshooting.
[Sprint Samsung Galaxy S III] EeZeEpEe:
Yeah all the April builds are having issues. For me it was Google Play Music and Tumblr.
[Sprint Samsung Galaxy S III] mw86:
I only said 3/31 because a few users in cm thread mentioned it seemed overall pretty stable to them vs the new things being added in April builds. Its up to you but mine has been stable. I don't user those two apps so I haven't noticed that. What doesn't work in Google play music? I don't mind installing it...?

But on that note let's lean the conversations toward kernel issues and feedback :D and get users where they need to be to keep this thread on track. Please CM users chat up about these issues in the nightly thread... I and many users post there even about CM and kernel compatibilities.
[Sprint Samsung Galaxy S III] boombotz401:
I seem to have lost my nav bar once flashed latest 3.4 kernel ? Any ideas....on the 4-2 pack man lotk
[Sprint Samsung Galaxy S III] nikolkang:
I haven't had one single lockup or reboot since installing your test kernel. Thanks ktoonsez, you do awesome work! :D

Currently running carbon 1.6
[Sprint Samsung Galaxy S III] KA82:
Reboots on 3.27 3.31 4.2 kernels.

Followed installation instructions.

On cm10.1 4.4 nightly. Dirty install.

Thank you for the work ktoonz. Love your kernel. I miss it.
[Sprint Samsung Galaxy S III] socioteq:
TuneIn radio FC`

Everything seems to be working VERY well with this kernel with the exception of TuneIn Radio... I get a FC every time I try and open it... it was working with the stock CM kernel. Any ideas why this is occurring?

Great work ktoonsez, you're one of the great ones!
[Sprint Samsung Galaxy S III] EndlessDissent:
That's the problem. It doesn't work at all. It opens, loads the first screen, and closes.

In the CM10.1 thread, I narrowed the problem down to one of two commits. If the problem is kernel-related, the problem is definitely this commit:

https://github.com/CyanogenMod/andr...mmit/c1c90566a1cda7b694f562b1c5cf14207d57c71e

Putting the ILLA in KILLA since 1985
[Sprint Samsung Galaxy S III] fabzbear:
What's the difference between the last two links for aosp 4.2 kernels that's on the op page?

OK i went into web view and saw that on is for Linux 3.0 and the other 3.4.

So my question is then does the Linux refer to the type of ROM you have or something else.
[Sprint Samsung Galaxy S III] bso44:
Tunein Radio working fine for me on the 3/27 TW kernel.
[Sprint Samsung Galaxy S III] ktoonsez:
Probably need a total wipe and flash then, I cant test CM but works perfect on AOKP.
[Sprint Samsung Galaxy S III] EndlessDissent:
Lots of people are reporting the same thing on a fresh install. It was a commit made in the 4/1 nightly since it works fine on 3/31, and aside from the commit I posted earlier, the only other graphics-related commit was this:

https://github.com/CyanogenMod/andr...mmit/313336ebbbdf256aabb3198f9294b447946bd01b

But if that were the problem, then people running your kernel would still have it. However, mw86 and others using your kernel are not having the problem while using the April nightlies.

Putting the ILLA in KILLA since 1985
[Sprint Samsung Galaxy S III] shinesthru:
Linux is an OS. From what I understand, "Linux 3.4" refers to the Linux kernel version used to build this kernel. It can seem a bit confusing to a novice (like me!), just remember the Linux kernel refers to the PC used to build the kernel that runs on our Android devices. Does that make sense?
[Sprint Samsung Galaxy S III] mw86:
Now that things have settled on access going into play store it is closing the play store window. But I can get into my apps and stuff. So I think I am effected to by the cm commit even being on latest KT kernel, so we will just have to wait for CM to take care of that. Its good digging you have been doing though :) it must have taken awhile for the issue to surface as I had downloaded and installed a few apps before without running into it. Figured I'd be thorough and report back. This is all cm though and not the kernel yes??
[Sprint Samsung Galaxy S III] ktoonsez:
Must be a bad mix of conflicting dates of ROM and kernel then, weird. :(
[Sprint Samsung Galaxy S III] ktoonsez:
You got it backwards. The 3.4 means the version of Linux that the kernel is running on your android device. Just a bit more info, I compile using Ubuntu that runs a Linux 3.6 kernel.
[Sprint Samsung Galaxy S III] shinesthru:
Dangit, well I tried!
[Sprint Samsung Galaxy S III] EndlessDissent:
To add to Ktoonsez's post, Linux IS NOT AN OS. Linux is the kernel. Nothing more, nothing less. Ubuntu is an OS that combines Linux with the GNU userspace and applications, just like pretty much every Linux distribution so far. It's just easier to say you use Linux when people ask which OS you use, so that's what people do.

Putting the ILLA in KILLA since 1985
[Sprint Samsung Galaxy S III] awillis111:
IIRC, Linux is a coding language named for the lead developer Linus Torvaldes. Correct me if I'm wrong.

All battery related stats are using a ZeroLemon 7000mah battery.
[Sprint Samsung Galaxy S III] EndlessDissent:
Linux is not a language. It is a kernel, just like I said in my post. It is written in the C programming language. However, you are correct that it is named for Linus Torvalds. It is a portmanteau of "Linus" and "UNIX", the corporate OS upon which Linux is based.

Putting the ILLA in KILLA since 1985
[Sprint Samsung Galaxy S III] Snugglej:
Should we do the super clean of all the files before we flash the newest kernel?

Including

1. removing the application settings

2. deleting application

3. rebooting

4.rebooting again into recovery

5. running the kernel cleaner script (do this first right?)

6. flash the kernel

7. reboot and everything should be good

Please let me know if this is the proper steps, I will plan on not doing the flash till I get this. I really want the latest version!
[Sprint Samsung Galaxy S III] fabzbear:
So which of the version of the aosp kernels (3.0 or 3.4) should i use on my ROM (jellybam).

What im basically asking is what ROMs is the 3.0 Linux aosp kernel used for and what ROMs is the 3.4 Linux aosp kernel used for?
[Sprint Samsung Galaxy S III] awillis111:
You'll have to find which stock kernel your ROM is using. Best bet is checking the changelog for Jellybam, ask in the ROM thread, or PM the developer.

All battery related stats are using a ZeroLemon 7000mah battery.
[Sprint Samsung Galaxy S III] Putrid Polecat:
Very well put. The confusion indeed comes from the fact people informally say "I run the Linux OS" even though this is not technically correct. It has, over time, come to mean two completely different things. People used to get really upset about this but these days only a few diehards get bent out of shape.

Things get even more confusing when people redundantly and incorrectly say "I'm running the Linux kernel". :D

So, in general, when people ask what version of Linux you are running you should be a jerk and respond "3.4", not Ubuntu (the flavor) (of the Linux OS) :D
[Sprint Samsung Galaxy S III] prboy1969:
I'm using the latest 3 / 30 Kernel. Everything is working perfectly.

Flashed as per described below :

1. Force Stop KTweaker

2. Clear Data

3. Clear KTweaker from SU

4. Delete Ktweaker from system / app

5. Reboot

6. Boot into Recovery

7. Wipe Cahce

8. Wipe Dalvik

9. Flash Kernel

10. Wipe Cache

11. Wipe Dalvik

12. Fix Permissions

13. Reboot
[Sprint Samsung Galaxy S III] ktoonsez:
AOSP Linux 3.0 Test kernel, reboots are GONE!!!!!!!!!!!!! (just as good as a release, I think)

http://goo.gl/nkuIR

Change Log 4.4.2013

1. KThermal is in the HOUSE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

2. Disable built in msm_thermal inside kernel so kthermal can do is thang!

3. Disable thermald (so you dont have to delete /system/bin/thermald :D. We'll see how that goes with all the different ROMs)
[Sprint Samsung Galaxy S III] ktoonsez:
Touchwiz JB 4.1.2 Test kernel, reboots are GONE!!!!!!!!!!!!! (just as good as a release, I think)

http://goo.gl/1t1rN

Change Log 4.5.2013

1. KThermal is in the HOUSE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

2. Disable built in msm_thermal inside kernel so kthermal can do is thang!

3. Disable thermald (so you dont have to delete /system/bin/thermald :D. We'll see how that goes with all the different ROMs)

LET ME KNOW ASAP PLEASE IF THINGS ARE BACK TO NORMAL. TO TEST DO THIS:

Run Antutu stability test for 2-3 minutes to get things warmed up and then do the normal Benchmark test with the "LOCK FREQUENCIES" OFF, no reboots then you are good to go.
[Sprint Samsung Galaxy S III] fabzbear:
The latest aosp kernel 3.4 the 3/27 I can't find the smartass or other governors.
[Sprint Samsung Galaxy S III] ktoonsez:
Its not in 3.4 since its not compatible with 3.4, it was barely compatible with 3.0 (was built on Linux 2.6 standards) so it needs a lot of work before it can be added, already tried and it was gonna be a pain in the ass and have limited time.
[Sprint Samsung Galaxy S III] prboy1969:
Thank you ktoonsez :D . Running great on the 3-30 release. But about to DL and flash. Any special instructions? Or just use the same ones as before?

EDIT: I flashed it using the same method as I listed above. ZERO issues :D . Running smoothly. About to tweak, and start a run. THANK YOU ktoonsez :D:D:D

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] calebsb:
Howdy, running MOAR mb1 4.1.2

Here is how I installed the latest 4-5 test tw747 kernel

Deleted 3-16 kernel version backups

Forced stop ktweaker

Deleted data

Deleted su prompt

Deleted ktweaker apk

Rebooted

Went in recovery

Flashed kernel cleaner

Installed 4-5 kernel

Flashed kernel cleaner again

Rebooted and opened KT. It was doing well. I did my new set up. Under clock 189, stayed at 1512 max, UV 25 across the board bfq and ktoonservative, then Saved settings. Backed out of ktweaker and opened it up a couple mins later, settings stuck that was good (great new layout of KT by the way) tried over clock 2106 and KT forced closed and rebooted my phone. Edit Just reporting my experience. I ran my backup. My phone stopped being cooperative. It almost didn't want to reboot to recovery lol

*

THE PROBERS THEME with Multi View Morph

Multi-Window Theme's, Pulldown Backgrounds, Frameworks, and Morphs zips

MOAR ROM Defining / MultiWindow / Multimod / Morphology

Multi View Tool - cover art theme
[Sprint Samsung Galaxy S III] reverepats:
Well, did the Antutu test and no reboots at all. Even upon boot after initial flash, things seemed to work just great. Thanks KT
[Sprint Samsung Galaxy S III] fabzbear:
First of i wanna say thank you for all the fast info you've given me and the help.

I've not only solved a couple problems but learnt some me things.

I've been using you're kernels for a very long while and will continue to show support.

Just wanna report that both aosp 3/27 3.0 & 3.4 Linux aren't working with the ROM I'm using (jellybam), keep getting boot loops.

Update

Just read a few pages back that the boot loops were mentioned already. Apologies.

Update II

Just tried the new aosp 3.0 Linux 4/4 and got Samsung label at start but then immediately after came a black screen. (Phone may or may not have booted, can't tell because of black screen).

Running jellybam v7.2

Ktoonz aosp 4.2 Linux 3.4 kernel 3/20
[Sprint Samsung Galaxy S III] epic4GEE:
Running the 4-5-13 tw kernel, everything works fine until I enable oc steps and try to push the slider past 1512mhz, either get a ktweaker fc or a freeze followed by a reboot. Completely stumped once again, even went as far to enable oc steps, dl setcpu, let it detect frequencies, delete ktweaker, go to setcpu and raise frequency past 1512 and get a reboot shortly after. I mainly tried that thinking it's a compatibility issue between my phone and the ktweaker app, instead of an issue between my phone and the kernel itself...now I'm not sure.

I'll stay tuned and try to figure out what else I can try.
[Sprint Samsung Galaxy S III] slickdaddy96:
I tried to OC for the first time and although the first time I enabled OC and tried the slider it force closed Ktweaker upon reentering app the setting was still pushed and I could slide the bar wherever I wanted with no freezes or force closes. Now Antutu won't run a benchmark while over clocked but Quandrant Standard would.

I have had no freeze up issues so far, although I have not let it sleep or screen turn off yet!

Running TW 4.1.2 4/5 kernel.
[Sprint Samsung Galaxy S III] hermeticist:
Is it necessary to use KTweaker or can it be deleted and use CM10.1 kernel manager instead?
[Sprint Samsung Galaxy S III] ktoonsez:
Your OCing to much with not enough voltage if Antutu closes. It does that all the time with any kernel, last version of Antut is really screwed up too.
[Sprint Samsung Galaxy S III] slickdaddy96:
Ok. I had not changed voltage from default when I attempted to over clock. Didn't know I needed to overvolt to OC. I never OC anyway. I was just doing it to see if I could and what benchmark I got.

Everything is great. No freezes yet.
[Sprint Samsung Galaxy S III] Out2kill:
Installed the new 4/5 test TW kernel..Seems to be working fine even with slight overclock. Havent messed with voltages yet. Thanks Ktoons! :good:
[Sprint Samsung Galaxy S III] ktoonsez:
Some phones need some more, some actually need less. The table has the values that worked for me and the testers I have (except for 2106, didnt want to have a huge stock voltage in there). It is up to people that want to OC to find the sweet spot for there phone :D
[Sprint Samsung Galaxy S III] prboy1969:
Just wanted to post an update. Been running great since my last post. Have OC'd to the max, all good. Changed all the settings to my liking. Running asswax / Zen. UV'd 60 across the board. I have a nominal CPU. Temp has yet to go above 44 even with over an hour of web use. Also have used Navigation, and Pandora at the same time. Over an hour this morning. I'm on JellyBomb v15 Test two. Thanks again ktoonsez :D:D:D .

TEAM MiK

MikROMs Since 3/13/11
[Sprint Samsung Galaxy S III] ktoonsez:
EXCELLENT!!!!! Glad this one is a winner :good: :highfive:
[Sprint Samsung Galaxy S III] flastnoles11:
If anybody is having problems with the app telling you your min/max doesn't match, this is what I did to fix it.... go into the app, set everything up the way you want it, set on boot immediately, then reboot, upon reboot open app and it should no longer give you this message... hope this helps someone, relatively simple fix, but could be overlooked by many

SPRINT GS3 FAQ
[Sprint Samsung Galaxy S III] dillweed:
Ktoonsez, thanks for the awesome work.

I'm running the 3.4 kernel and haven't had any problems, but I noticed that the BFQ scheduler is not included in that kernel. Am I missing something? I remember reading something a few pages back where someone else asked the same question but no one answered. If it is gone do you have plans to implement BFQ back into the kernel? My opinion of the matter is that BFQ provided the best battery life without any lag at least for my phone.

Have a good one!
[Sprint Samsung Galaxy S III] fabzbear:
Are you using the 3/27 version of the 3.4 kernel or an older dated one?
[Sprint Samsung Galaxy S III] Ragnar:
This is regarding governors but I'm sure it applies to schedulers as well, I'm just guessing here.

Transmitted with a portable device using Xparent Blue Tapatalk 2
[Sprint Samsung Galaxy S III] epic4GEE:
This is prolly the last thing I can try, but seems most likely to be right. I noticed agats kernel runs 1300mv@1971mhz and my phone handles it fine, I've even dropped -25mv off that with no issue...I have little time to see right now tho, so I'll check it later.
[Sprint Samsung Galaxy S III] MassStash:
Latest TW ver. running great on Chubbz and MSG rom. Renamed thermal of course. No changing frequency issues or anything

~d2spr runnin' CarbonRom

cpu0/1: 1.7ghz | 192mhz | sleep 486mhz with latest ktoonsez kernel

Intellidemand

row

mpdecision: off
[Sprint Samsung Galaxy S III] ktoonsez:
I have not put it in yet do to it screwing over every other scheduler so I haven't had the patients yet to add it in and have to rewrite others to make everything work again.
[Sprint Samsung Galaxy S III] Samurai7314:
Just wanted to let you know. The new tw is working great no issues at all when I was playing with everything.
[Sprint Samsung Galaxy S III] Putrid Polecat:
Latest TW running flawlessly with rooted stock. ^o^ :thumbup:
[Sprint Samsung Galaxy S III] MassStash:
Update: latest TW on the chubbz Rom, getting a RR here or there. Once pulling up YouTube 3 hrs ago, and now sitting in my pocket. /proc/last_kmsg not found, what am I missing? Some ignorance is afoot! Haha

~S-Off LTEvo; Strapped to this gnarly Sense5 port; ArcReactor

cpu0/1: 1.7ghz ¦ 192mhz ¦ sleep: 486mhz max

Intellidemand

fiops

mpdecision: off
[Sprint Samsung Galaxy S III] dillweed:
Sounds good and thanks for the reply.
[Sprint Samsung Galaxy S III] fabzbear:
Latest ktoonz aosp 4.2 Linux 3.4 doesn't work with jellybam v7.2. Installs then i get a black screen from start up.
[Sprint Samsung Galaxy S III] ktoonsez:
Then it probably needs the 3.0 kernel then or they are just behind :good:
[Sprint Samsung Galaxy S III] epic4GEE:
Still going to thank you for this post once I get some thanks for today. It gave me the idea to try lowering all the oc voltages and it somewhat worked for the 4-5 tw kernel, tried a dozen or so times dropping 25mv per step, after all the reboots I came to the conclusion that 1809mhz seems to be my max on this kernel, not an issue as 1674mhz seems to be the most I'll need. Other than my oc issues, not a single other issue on boot to shutdown and everything in between on the peoples rom.

Love the ktweaker app and appreciate you taking the time to give us all these tw kernels. I know tw is not the love of your life lol...again thanks:good:
[Sprint Samsung Galaxy S III] fabzbear:
Sorry I left out like two more details and also thanks for the quick reply.

One is, I used both aosp 4.2 kernels 3.0 & 3.4 3/27 and they didn't work. I do not have a 3.0 3/20 so I couldn't see if that would work but I did have the 3.4 3/20 and that solved the problem and booted up properly. Both were on fresh installs.

Once again thanks for the work you've done.
[Sprint Samsung Galaxy S III] grizzlywan:
I just clean installed from completely nothing LiquidSmooth latest with 3.4 AOSP kernel. It works fine except when it comes to changing anything in Ktweaker. The moment I adjust something, the phone restarts. I've force closed and wiped data to try to fix it, but nothing works.
[Sprint Samsung Galaxy S III] freecharlesmanson:
Thank you ktoonsez, I did however want to report the voltage table is low for default settings, Bluetooth audio did not function well until I raised the voltage on 378 up to 950 this has been the case on absolutely all builds for me since this kernel has existed. Other then that again thank you, my gratitude for your persistent meticulous work.
[Sprint Samsung Galaxy S III] Logix:
What's the Bluetooth chips stock voltage?
[Sprint Samsung Galaxy S III] bso44:
What kind of bluetooth issues did you experience at 925?
[Sprint Samsung Galaxy S III] Thadd Valeika:
Did someone say the ktoonservative is having issues?
[Sprint Samsung Galaxy S III] ktoonsez:
Change Log 4.7.2013

1. Linux 3.4.38

2. Linux 3.4.39

3. Added BFQ - 3.4.0-v6 back in

4. Added Wheatley governor back in

5. Added SmartassH3 governor (not behaving the best, likes to pin at max forever, you guys will have to play with tunables to see what works)

6. Added dancedance governor (not behaving the best, likes to pin at max forever, you guys will have to play with tunables to see what works)

7. Added nightmare governor

8. Bunch more updates from CM (a lot for GPU)

9. Some more Linaro optimizations

10. KTweaker thermal control under "Extras" screen

11. Temperature added to "General" screen right next to current Mhz

12. Auto hotplug re-worked to stop scroll jitter for some people

13. Some more stuff I cant remember ....

ENJOY :D :good: :highfive:
[Sprint Samsung Galaxy S III] mcluvin1065:
Is there any issues with the lated ktoonz? Im running a 2-11 build and have not had issues whatsoever.... Im one of those if it ain't broke don't fix it kinda guys so can anyone clarify?

Sent from my rooted, suited, and booted SGSIII livin the dual-core life, know dat
[Sprint Samsung Galaxy S III] shinesthru:
Just read the thread for the latest feedback.
[Sprint Samsung Galaxy S III] maxima2k53:
So what is the nightmare governor?
[Sprint Samsung Galaxy S III] ktoonsez:
Its a governor and its called nightmare :D :good: FLOAM :p
[Sprint Samsung Galaxy S III] maxima2k53:
Just asking because I tried to look in the governor section for the info and its not there.
[Sprint Samsung Galaxy S III] ktoonsez:
LOL, I was only kidding while I looked at the description from the guy I got it from :highfive:
[Sprint Samsung Galaxy S III] shinesthru:
Best info I could find is that is based on the pegasusq governor, but maybe a bit more battery friendly and (or maybe because) it does not have hotplugging enabled.
[Sprint Samsung Galaxy S III] ktoonsez:
Not much info on it at all with a search, all I know is from the code, its based on ondemand with a little pegasusq action :good:
[Sprint Samsung Galaxy S III] avd:
Is the 4.1.1 TW abandoned?
[Sprint Samsung Galaxy S III] ktoonsez:
No, its still in the OP.
[Sprint Samsung Galaxy S III] slickdaddy96:
Why would you still be on TW 4.1.1 when every custom TW ROM active that I know of is running based on MB1(4.1.2)?
[Sprint Samsung Galaxy S III] Slomodrop:
Why wouldn't lack of hotplugging be worse for battery with all other variables staying the same on a reasonably tuned setup?

// Galaxy S3 SPH-L710 // KT747 ktoonservative-deadline 384-1728Mhz + TK Mod + scaling tweaks // entropy + DNS // fsTRIM // MOAR // sent from xda premium
[Sprint Samsung Galaxy S III] DrgnRebrn:
LJ7 gets higher benchmarks and battery life than MB1, for some people.

ROM - Odexed Blue LJ7 "Holy Grail"

Kernel - freeza's modified MB1

Baseband - MB1
[Sprint Samsung Galaxy S III] Slomodrop:
I've been tempted to try an LJ7 rom just to compare lag because I'm a dork like that. I hate lag.

// Galaxy S3 SPH-L710 // KT747 ktoonservative-deadline 1880Mhz + TK Mod + scaling tweaks // entropy + DNS // fsTRIM // MOAR // sent from xda premium
[Sprint Samsung Galaxy S III] avd:
I'm using the last blazer rom which is on LJ7
[Sprint Samsung Galaxy S III] slickdaddy96:
That's funny, I'm on stock rooted MB1, and I have no lag issues and couldn't care less about benchmark scores. If I wanted them I would over clock.
[Sprint Samsung Galaxy S III] cooki3monst3r77:
Awwwww YEEEA!

Alright, awesome! Let's start an argument over what VERSION of TW is better! I thought that was the point of flashing, rooting, ROM'ing, etc..... so that you can do WHAT YOU WANT with YOUR phone. If dude wants to put an LJ7 ROM on his phone, who cares! Let's try to keep the topic to the kernel in question. :cyclops:
[Sprint Samsung Galaxy S III] slickdaddy96:
Not arguing dude. Just thought it was funny his experience was completely different than mine on MB1.

At this point I would think it is safe to say the 4.1.1 kernel will never be updated again though. I'm not putting words in ktoonsez mouth here but if it were me I wouldn't update it anymore.