yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] gadgetguy08:
Running AOSP 4.2.2 (SlimROM 3 - very solid - using 3.0 kernel) on d2vzw. The device has a rev 0 processor.

Installed KT747 3/27 version about a few days ago and things were OK although KTweaker asked for SuperUser privileges about 90 times in one minute when the device started. Yesterday the device locked up and was showing Android System using lots of battery so I decided to upgrade to the 4/4 version (3.0). I deleted KTweaker and flashed, clearing cache, Davlik and fixing permissions. I was glad to see that KTweaker didn't ask for SuperUser privileges but once, but the device was never stable. It would reboot soon after starting or run hot until it went to sleep and then rebooted. I tried several different settings to no avail.

At this point I dropped back to the 3/27 version and it would start and run fine, but once it timed out or the power button was pressed, it locked up and wouldn't come on again. This had default settings.

So I dropped back to 3/14 version and things have stabilized.

Not sure what to suspect or pursue in all this, but thought I would report it in case anyone else saw this or had ideas.

UPDATE: even 3/14 version is unstable for me now. Dropped back to stock kernel.
[Verizon Samsung Galaxy S III] neyenlives:
I am on TW but I still am running the 3-14 kernel because that's the last stable one.

How do you know your cpu is a rev 0?
[Verizon Samsung Galaxy S III] Hybridnoob:
Thank you for all of your hard work! Excellent kernel!!

Confirmation: 3T1317455S928812E
[Verizon Samsung Galaxy S III] gadgetguy08:
System Settings / About phone / CPU

From what I have read that rev may have issues with undervolting.
[Verizon Samsung Galaxy S III] Stupifier:
I have rev 4 CPU. What does that mean?
[Verizon Samsung Galaxy S III] macman159:
Your voltages are hardwired and cannot be changed. Rev 0 lets your underclock, but is unstable. rev 1, 2, 3 have no problems undervolting.
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks man, appreciate it :good:
[Verizon Samsung Galaxy S III] ktoonsez:
You are under volting too much
[Verizon Samsung Galaxy S III] daimerion:
Im confused because i have rev 4 and have no problems undervolting.
[Verizon Samsung Galaxy S III] BattsNotIncld:
3.4 AOSP 4/3 kernel running smooth. Very stable with Carbon nightly.
[Verizon Samsung Galaxy S III] Neverendingxsin:
I don't think the rev number has anything to do with whether you can undervolt safely or not
[Verizon Samsung Galaxy S III] Droid316:
I concur
[Verizon Samsung Galaxy S III] PsiPhiDan:
Yeah that's not true. I undervolt with the rev4 and have no problems (at least on the 3.0 kernel).
[Verizon Samsung Galaxy S III] Äptiva:
KT you're freaking awesome. My question for you.... What changes will I need to make to build this for d2cri aka Cricket S3?
[Verizon Samsung Galaxy S III] ktoonsez:
You would need a defconfig for it to compile on and merge in all cricket specific code into the main source :good:
[Verizon Samsung Galaxy S III] Äptiva:
Almost finished compiling then errored out in the end....

WARNING: vmlinux.o(.text+0x537d2c): Section mismatch in reference from the function store_scaling_max_freq() to the function .cpuinit.text:cpu_up()

The function store_scaling_max_freq() references

the function __cpuinit cpu_up().

This is often because store_scaling_max_freq lacks a __cpuinit

annotation or the annotation of cpu_up is wrong.

:(
[Verizon Samsung Galaxy S III] neyenlives:
That doesn't show up on my phone, there is no "cpu" under "about phone"
[Verizon Samsung Galaxy S III] Addiso:
But I can undervolt that much on your 3/14 kernel and with your new kernel I get the graphical glitches.
[Verizon Samsung Galaxy S III] shawn01:
Oh 4/3 kernel I had high android system and os usage. Went back to 3/14 running better. Better battery life. I guess 4/3 no likey my phone. Oh well:( 3/14 runs cooler also.

---------- Post added at 11:17 PM ---------- Previous post was at 11:14 PM ----------

Does anyone know why factory mode does? On every rom I've tried it constantly pops up and drains my battery until I force close it. How can I stop it from popping up? Is this kernel issues or something I'm doing?
[Verizon Samsung Galaxy S III] gadgetguy08:
Run this in Terminal Emulator:

su <enter>

cat /proc/cpuinfo <enter>

(There is a space after 'cat')
[Verizon Samsung Galaxy S III] Stupifier:
This. Please explain further. It's my understanding, that I have been successfully undervolting ever since I owned this phone.
[Verizon Samsung Galaxy S III] zeus33:
Actually, it's: System Settings / About phone / Hardware Info - CPU is listed at the top.
[Verizon Samsung Galaxy S III] neyenlives:
Not there.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Any CPU control app should have that information.
[Verizon Samsung Galaxy S III] zeus33:
Looks like you will have to use TE like this post says:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Do the above and/or do the following as well:

1) Reboot

2) open Terminal Emulator and type:

su

dmesg | grep ACPU

*note, there is a space after "dmesg" "|" and "grep"

You'll see a line that tells you which CPU type you have. Slow CPUs can not UV very much, Nominal can UV to an extent, and Fast can UV the most.
[Verizon Samsung Galaxy S III] macman159:
The app will let you undervolt becuase it is not partial to the other PVS chip types. However the cpu will just ignore it. So the app is giving you a placebo effect lol
[Verizon Samsung Galaxy S III] Neverendingxsin:
Can you provide proof to this? I haven't read about it anywhere.
[Verizon Samsung Galaxy S III] Wi1son:
Are we maybe getting a 4-6 kernel tonight?
[Verizon Samsung Galaxy S III] Addiso:
I have graphical glitches and ktoonsez stated earlier that it's because you are under volting too much and I have a nominal rev 4 cpu chip. So?.... I'm lost now with people saying you can't undervolt rev 4 chips.
[Verizon Samsung Galaxy S III] cell128:
I was on this kernel until my phone started glitching. I didn't change anything just installed it and chose trinity colors with on demand governor. In love the trinity colors option but I had to go to stock kernel for now just to have stability. Sorry if this has been asked before but is there a way to get trinity colors on stock or other kernel? Thanks
[Verizon Samsung Galaxy S III] Neverendingxsin:
For now i'd seriously disregard whatever that guy said about the rev # having anything to do with your under-volting capabilities (until further proof is provided) as far as graphical glitches i had some with both ktoonz kernel (on koonservative and interactive governor, never touched the voltage) and tasks kernel (interactive governor) when i reverted back to the CM kernel the glitches went away.
[Verizon Samsung Galaxy S III] kantaris:
I just want to overclock my phone slightly when it's needed (Ingress seems to like to get really really slow after some time). Do I need to do anything other than install the Kernel?
[Verizon Samsung Galaxy S III] neyenlives:
Thanks here is the output:

All I know is it undervolts like a baus , - 125mV is stable.
[Verizon Samsung Galaxy S III] tihsllub:
Kernel is good even if it is a little glitchy. I can't build a kernel and I don't know many others that can either. All we can do is provide specific feedback until the bugs are worked out.
[Verizon Samsung Galaxy S III] Wi1son:
I see the at&t kernel has moved up to a 4-6 release. Will there be a new Verizon release soon?
[Verizon 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:
[Verizon Samsung Galaxy S III] Droid316:
So the.4-4 touch wiz kernel is the latest one?

If so how is it running for you guys?

©!Sent From My Verizon Galaxy S3 Powered By 7000mah Of Zerolemon Battery!©
[Verizon Samsung Galaxy S III] mickskillz:
I'm running the 4-4 TouchWiz version and it is working flawlessly...... Smartass2/sio UV -50 across the board... great battery and very responsive
[Verizon Samsung Galaxy S III] Mattish13:
I was getting reboots on 3/27 so I tried 4/4. Tried to open Google now because it was causing reboots before and I got a reboot again. Phone felt unusually warm so I went back to 3/14 for stability until things get sorted out. I appreciate everyone's hard work on this issue!
[Verizon Samsung Galaxy S III] guywmustang:
Yeah I definitely notice the phone being way warmer now. It just seems like it's eating through the batter WAY faster than it used to.

This is with carbon 1.6 and ktoonz 4/7. I'm using the ktoonservative governor.

I might go with a touchwiz rom until things get worked out.
[Verizon Samsung Galaxy S III] tihsllub:
Temp is reading -38 I believe its a little warmer than that.
[Verizon Samsung Galaxy S III] ktoonsez:
Whats your max Mhz?
[Verizon Samsung Galaxy S III] thornev:
I've been using KT747 with all my ROMs. Right now I'm on Plasma8 and was using the Feb KT747. Just flashed March KT747 and phone keeps rebooting. Reflashed and it was better but rebooted when I tried to adjust settings using your CPU control program. Will keep monitoring this thread for fixes. Thanks. Oh - I'm a 4.1 Touchwiz kernel guy.
[Verizon Samsung Galaxy S III] ktoonsez:
What are you doing? Trying to OC? What step are you trying to go to if you are trying to OC? Did you adjust voltage for the steps you are trying to reach? Need info man, everything is running perfect.
[Verizon Samsung Galaxy S III] thornev:
Sorry. I've been doing what I've always done - overclock to 2.1 with Performance governor and undervolt -50 across the board. This worked with all the KT747 kernels for months. The late March kernel is the first one to cause a problem.
[Verizon Samsung Galaxy S III] ktoonsez:
Well you definetely havent been around then. The 2106 step (along with the other step 1674 and up) had a math error in it that all the kernel devs inherited and is now correct and ends up being about 20% faster (at the 2106 step) and your phone will definetely NOT do it unless you OC alot than what I have in there, its up to u to tune it if you still want to attempt to reach 2106 Mhz :good:
[Verizon Samsung Galaxy S III] thornev:
Yeah I haven't been following this thread because KT747 has worked flawlessly. I guess you're saying I can't use the same settings I always used and that I have to play with voltage and CPU OC settings to find what my phone can handle. OK, will do. Thanks for the response.
[Verizon Samsung Galaxy S III] ktoonsez:
Thanks man :D, and no problem, to match the speed you used to go, 1809 or 1890 is equivalent :good:
[Verizon Samsung Galaxy S III] Aarongauntt:
All my screen flicker is gone with new build. Great job man!
[Verizon Samsung Galaxy S III] guywmustang:
It was all stock settings except the ktoonservative governor. I'm trying out the slimbean build now. I'm just gonna do the 3.0 kernel for a little.
[Verizon Samsung Galaxy S III] neyenlives:
I'm on TW, no over clocking at all, and the 3-14 kernel is the last stable one for me.
[Verizon Samsung Galaxy S III] michaelearth:
I just updated to Carbon 1.6.1. What kernel version do I not need, 3.0 or 3.4?

Thanks!
[Verizon Samsung Galaxy S III] Hobart!:
Flashed TW 4-4 on beans and lost boot animation. ..any ideas? I know it was blank and the stock sammi was put in but not sure what to do to get beans back..lol
[Verizon Samsung Galaxy S III] Wi1son:
1.6.1 uses 3.0 kernel.
[Verizon Samsung Galaxy S III] thornev:
Hmm, KTweaker keeps force closing on me. Tried to uninstall and reinstall in case maybe there's a later version that goes with the kernel, but uninstall fails. This is a bummer. I did set OC at 1809 and left voltages at stock for the kernel. Governor is Performance.

I've never had to do a clean install just for the kernel. Maybe the late March KT747 needs a factory wipe first?
[Verizon Samsung Galaxy S III] tihsllub:
Anybody get voltages tuned for the OC steps? At least running versions up to 2106. I noticed that anything over 1900 causes reboot.
[Verizon Samsung Galaxy S III] ktoonsez:
The ROM u installed is trying to use AOSP boot animations on a Touchjizzer ROM. I dont support that.
[Verizon Samsung Galaxy S III] shawn01:
Touchjizzer. Ha
[Verizon Samsung Galaxy S III] nick7893:
Check out the TK thread and flash TK mod 1.0.2
[Verizon Samsung Galaxy S III] khaoskosmos:
Same here. Used to run 2106mhz now I get a reboot on anything > 1900. CarbonRom 7apr nightly.

Edit: just got a reboot posting this @ 1890mhz. Dropped down to 1809mhz.
[Verizon Samsung Galaxy S III] tprophit:
Just clean flashed carbon 4/7 nightly, and today's kt747.

All good, except, every time ktweaker is opened, get the stored settings do not match...
[Verizon Samsung Galaxy S III] jamesino:
What is trinity colors?
[Verizon Samsung Galaxy S III] Stranger_84:
Everything running real smooth with this las test kernel update so far thanks!!!!
[Verizon Samsung Galaxy S III] MorphiousGX:
I'm using ChameleonOS (AOSP) ROM with the latest 3.4 (4/7) kernel.

Noticed that Asswax governor does not go anywhere below the MAX frequency I selected. I thought it might be the ROM, I tried the latest CM Nightly, got the same results. When I reverted to the 3/27 release of the Kernel, it was not an issue anymore.
[Verizon Samsung Galaxy S III] Hobart!:
For those who want boot animation back the TK thread looks great but the Custombootanimation.zip in OP of Sbreen Hyperdrive thread works!!! Just reporting from Beans14
[Verizon Samsung Galaxy S III] juancaperez2000:
That is a issue related to that governor
[Verizon Samsung Galaxy S III] MorphiousGX:
I believe so. I never had this problem with the governor running it on TW. Only on AOSP
[Verizon Samsung Galaxy S III] Wi1son:
See for yourself - Turn it off then turn your screen on and off.
[Verizon Samsung Galaxy S III] drecu:
Love the latest Kernel!
[Verizon Samsung Galaxy S III] jamesino:
What is fast charging? Will this let me charge faster while connected to the AC adapter or only USB port?
[Verizon Samsung Galaxy S III] ktoonsez:
Only DC sources which is USB and car charger.
[Verizon Samsung Galaxy S III] jamesino:
I noticed this kernel charges a bit more slowly than compared to LeanKernel, BMS, or Stock. Anything I can do to help it charge faster? Not a huge deal, this is so much faster than the other ones so it's a trade off that I'm willing to accept.

Running the latest v3.0 kernel with LiquidSmooth v2.1 Verizon.
[Verizon Samsung Galaxy S III] Droid316:
Well like you asked if your charging your phone through your computer/car charger enable fast charge but deselect usb debugging first in developer options.Also what chargers are you using for your car and your outlet?

[©Sent from my Samsung Galaxy S3 Verizon 4G LTE Powered by ZeroLemon 7000mah Extended Battery!!©]
[Verizon Samsung Galaxy S III] masri1987:
So using latest kernel with latest masta CM 10.1, blue tooth streaming sucks.
[Verizon Samsung Galaxy S III] failsaf3:
ktoonsez- will you be updating the Linux 3.0 kernel to 4/7? Just curious. Thanks and keep up the outstanding work.
[Verizon Samsung Galaxy S III] Setco:
Great job with the latest kernel guys. Works well with the latest Carbon ROM. Keep up the GREAT work.
[Verizon Samsung Galaxy S III] jamesino:
I'm charging it through a wall AC outlet with the stock charger.
[Verizon Samsung Galaxy S III] NITRO_2:
Sorry for the question but is 3/27 the latest TW kernel? I thought I remember seeing a 4/4?
[Verizon Samsung Galaxy S III] nick7893:
No he released a test kernel that fixed the reboots
[Verizon Samsung Galaxy S III] luis86dr:
Requests are surely not ignored, nor overlooked. I've seen many governors added at the request of a user, including faux and much more. Rebuilding this kernel from the ground up again is not an simple task, especially to the state the kernel was at. Patience is all that is needed, eventually with time more coding will be implemented and things will progress. Until then, let's give KT a break as I'm sure he needs it. If you only knew how many lines of coding goes into a kernel, its unbelievable. Especially for one sole person doing the work.

No disrespect intended to anyone. Just stating let's be a bit more patient.:)
[Verizon Samsung Galaxy S III] Neverendingxsin:
I think it's best if you guys can take this to PMs otherwise I'm sure a mod will come in here and deal with it.
[Verizon Samsung Galaxy S III] KennyG123:
Thread cleaned

As stated feel free to grab Samsung's source and start compiling

Also please ignore troll posts. Report any breaking of the rules

Please respect the developers on XDA-DEVELOPERS.com

Without them this would be XDA-twitbook.com

Thank you for your cooperation

Friendly Neighborhood Moderator
[Verizon Samsung Galaxy S III] Chris123NT:
That's more than likely ROM related. A2DP on CM 10.1 has always been iffy. Sometimes it works, sometimes it doesn't.
[Verizon Samsung Galaxy S III] neyenlives:
Amazing, it all started by me stating the obvious, that there are still some of us who can't run a kernel past 3-14 and everytime we mention it there's no responses. That's not trolling nor is it demanding, it's stating the truth. Too many people on edge around here. All I was trying to do is keep the issue out front so maybe eventually it gets resolved. You don't see me whining or demanding anything. I understand full well how this works. But until it gets resolved I will continue to occasionally pop in to say "hey it still doesn't work". That's all my post was. If you were saying the same thing week after week, and never got a response, and you weren't alone, wouldn't you feel compelled to speak up when others like you also are experiencing the same issue?

I'm all for "supporting" the devs but when did support get defined as only giving cheers? I would think knowing that you have issues with a certain number of users would be important for the development cycle. I didn't make any demands, I didn't speak negatively about him or his work. I simply stated what other members have been saying for weeks now.

Apologies for the interruption. I will just look for a different kernel. I really enjoyed your work and appreciate it, it ran so great. Sad to see it go.
[Verizon Samsung Galaxy S III] ktoonsez:
The last test release I made is the latest for 3.0, believe it was 4/3.
[Verizon Samsung Galaxy S III] harosxcomp170:
Ktoonz I've been running your 3/20 3.4 kernel with all these new 3.4 ROMs but I tried your latest 3.4 kernel but I'm still getting reboots when running over 1900mhz? But that 3/20 3.4 kernel is running perfect on 2.1ghz, so I'm just sticking to this kernel until it gets figured out.
[Verizon Samsung Galaxy S III] ktoonsez:
There is nothing to figure out, your phone wont OC that much. 3/20's OC at 2106 was only 1860 due to a math error all kernel devs had from the beginning.
[Verizon Samsung Galaxy S III] mw86:
I'm not pointing you out but in general your type of question. There has been about 6+ questions of this same nature repeated endlessly that had anyone been skimming the posts which are new since last visit would have seen the countless questions asking why for no 2.1ghz?!? Followed by the same answer post after post stating the old 3.0 kernel had a math error as KT states several times at this point and that 1860mhz is what 2106mhz used to be running at in all actuality on the 3.0 kernels. The new setup is far more powerful and is in no way worse that it can't get to 2106mhz which in all fact it NEVER did in the first place. I do hope more of our KT followers that have been away awhile read up the latest posts to avoid this seemingly unending cycle of why do I reboot at 2106mhz or possibly on 1998mhz or even some at 1890mhz. Try it yourself, experiment, raise volts on those if you have to. In most cases no one will get 2.1ghz stable, some may get 1998mhz stable in basic tasks but under full heavy load and as heat builds our new stable max is around 1810-1890mhz. Again this response is to all who have been asking and no one in particular including the user I just quoted. Thank you and as Kenny is saying, respect the developers they put more work into this than you can ever imagine!
[Verizon Samsung Galaxy S III] jlee08517:
does that mean it was miscalculated thru the entire frequencies? like if I pick like 1200 or 1300 would that be equivalent to 1500?or is it only affecting frequencies greater than 1500?
[Verizon Samsung Galaxy S III] mw86:
It was on 1674,1728,1810,1890,1998,2106mhz on the 3.0 kernels anything below that was running the correct MHz. 151hz and below should handle same or better due to kernel improvements in 3.4 kernel but has no difference in the MHz from 81-1512mhz on 3.0kernel to 3.4kernel
[Verizon Samsung Galaxy S III] siriusgamer:
So can any phone actually reach the full 2106mhz? Does anybody know?
[Verizon Samsung Galaxy S III] ktoonsez:
I have seen 3 people hit it, took a lot of voltage though I believe.
[Verizon Samsung Galaxy S III] Stupifier:
SO I bet everyone is reworking their Overclock & Undervolt tables? Should be interesting to see what people post up now.
[Verizon Samsung Galaxy S III] masri1987:
Ktoons, can you add the freelunch governor from decimal man's kernel?
[Verizon Samsung Galaxy S III] ktoonsez:
If its a 3.4 Linux kernel and you have a link.
[Verizon Samsung Galaxy S III] masri1987:
Yes and yes

http://xdaforums.com/showthread.php?t=2226894
[Verizon Samsung Galaxy S III] luv2increase:
I always run my phone at 2106 with ktoonz kernel

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] Droid316:
Your not worried about decreasing the life of your phone?

[©Sent from my Samsung Galaxy S3 Verizon 4G LTE Powered by ZeroLemon 7000mah Extended Battery!!©]
[Verizon Samsung Galaxy S III] ktoonsez:
Ill look at more closely, looks like he has it wound pretty tight into a lot of things and not sure I want to add the "extras".
[Verizon Samsung Galaxy S III] masri1987:
What's everyone's setup? Currently using ktoonservative and zen 189 min 1350 max and - 25v across the board
[Verizon Samsung Galaxy S III] tihsllub:
No OC or UV running 81-1026 with cfq and ktoonservative

---------- Post added at 07:38 PM ---------- Previous post was at 07:37 PM ----------

Getting 10 hours of moderate use at work with only 45% use
[Verizon Samsung Galaxy S III] luv2increase:
Not at all. My phone doesn't even get real hot. My CPU is rev0 . Also, I don't plan on keeping this phone all my life or for an extended amount of time like I would a PC.

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] tihsllub:
Best I can get is 1890 to run for more than an hour at 1370mv 1998 will run for bout 10 min at 1400 and 2106 not at all. Wish these processors were spec grade and not some cookie cutter ****.
[Verizon Samsung Galaxy S III] thornev:
If I were the dev, I would put something in the OP about how 2100 had the math error. Seems like the best place to announce such a critical notice that maybe would prevent the same question over and over. Just a sug. I know that suggestion in other threads has been bashed around. Being a software developer for 30+ years myself, I've come to understand that "1-stop shopping" works most of the time.