yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] soapinmouth:
I'm getting random reboots fairly often on interactive governor even on stock voltages(normally run -50). Anyone else?
[Verizon Samsung Galaxy S III] jamesino:
Which ROM? I've run 4/8 and 4/11 (3.4) for a combined total of about 2-3 days on interactive, no reboots yet, stock voltages. I even tweaked the go_hispeed_load and other parameters without any instability.
[Verizon Samsung Galaxy S III] soapinmouth:
I'm on the latest carbon nightly. It's odd because none of the other governors cause reboots as far as I can tell. It was like this on the last kernel release too, not sure before then because I never used interactive. I'm on ondemand now overclocked and undervolted with no issues.
[Verizon Samsung Galaxy S III] WhammyDroid:
Ktoonsez, what governor settings are you running again? What settings did change? I can't find your earlier post.
[Verizon Samsung Galaxy S III] mike216:
On liquid and no reboots, not one single issue. Stop using carbon for now it seems to have issues. The kernel is rock solid stable
[Verizon Samsung Galaxy S III] srs731:
Why not check the team kernelizers thread and get multiple options?
[Verizon Samsung Galaxy S III] PoLoMoTo:
I did a system wipe the reflashed everything and still no dice, can enable oc, lock frequencies and move a slider anything else crashes the entire phone. Are there any logs that would give more info on whats happening?
[Verizon Samsung Galaxy S III] tihsllub:
Go to settings/apps/ktweaker/clear data and cache. That should clear your issue. If you are still having issues you need to delete your ktweaker app could be system/data/app or just data folder. But find them delete them then go into recovery and reflash the kernel and wipe cache/dalvik and fix permissions.
[Verizon Samsung Galaxy S III] MorphiousGX:
I'm using nightly 4/10.

---------- Post added at 11:22 PM ---------- Previous post was at 11:20 PM ----------

I used asswax and tried to use smartassH3 but they seem to get stuck on higher frequency if you use AOSP based Roms
[Verizon Samsung Galaxy S III] PsiPhiDan:
Liquid 2.2 + latest ktoonz 3.4 kernel = WOW! Best combo I've ever run. No SOD or battery pulls needed!
[Verizon Samsung Galaxy S III] savagebunny:
I may just have to switch from carbon 1.6.1... Already have had 2 lock ups and 1 reboot.
[Verizon Samsung Galaxy S III] keynith:
Im running 4-11 v.2 with the toonmans latest aosp 3.4 kernal. Awesome runtime and great response too.
[Verizon Samsung Galaxy S III] ktoonsez:
Definetely the ROM, have heard nothing but problems with that
[Verizon Samsung Galaxy S III] WhammyDroid:
Link to the team kernelizers thread please?
[Verizon Samsung Galaxy S III] Wi1son:
http://xdaforums.com/showthread.php?t=2144004
[Verizon Samsung Galaxy S III] PsiPhiDan:
Just go to the general section of this forum. It's almost always on top of the list. It's a very active thread.

---------- Post added at 09:50 AM ---------- Previous post was at 09:15 AM ----------

I prefer Liquid to Carbon anyway, so I'd give it a go if I were you. :)
[Verizon Samsung Galaxy S III] tihsllub:
Every time I try to save my boost GPU value in the ktoonservative governor from 460 to 500 it clears it and sets the value to 0 :/
[Verizon Samsung Galaxy S III] ktoonsez:
That option is not enabled, its from my Nexus 10 kernel and want to enable it at some point so thats why it is in the list. :good:
[Verizon Samsung Galaxy S III] harosxcomp170:
I'm running Liquids new 2.2 build, and I'm trying to run this 03/11 3.4 kernel with it. I keep getting reboots! I've deleted all the ktweaker files under system and data I also went to settings/app and deleted cache and data. I keep my I/O on ROW and I run ktoonservitive for my governor. Whenever I enable overclocking I keep my low at 84 and my high at 2106 and I keep getting a reboot when my ROM starts up? I don't know why it isn't working for me? I keep the voltage at the default values? No idea?
[Verizon Samsung Galaxy S III] ktoonsez:
Pretty simple, your phone cant handle 2106, you need to go lower.
[Verizon Samsung Galaxy S III] harosxcomp170:
It used to handle 2107 on the 3.0 kernels I just don't get why it wouldn't now? Its strange when I try to overclock even to just 1607 it won't stick? Even after a reboot too? I dn I'm gonna keep trying. I've been running your kernels since I got my GS3! Thanks for the reply!
[Verizon Samsung Galaxy S III] MorphiousGX:
Exactly. Try it plain then once you know it's stable, tweak
[Verizon Samsung Galaxy S III] Hybridnoob:
He's explained it several times in this thread recently.
[Verizon Samsung Galaxy S III] savagebunny:
Running Liquid now with the latest 3.4... Mother of god this is Liquid butter with my peg/zen mod.
[Verizon Samsung Galaxy S III] pettigrew95:
Anyone use 81 mhz as their lowest frequency? If so, does the phone ever get sleep of death or anything along those lines? I would imagine the phone sometimes might not have enough CPU power to get the phone out of deep sleep. Any feedback is appreciated! Also, if anyone runs the 2106 mhz how's the stability with stock voltages? Thanks in advance!
[Verizon Samsung Galaxy S III] MorphiousGX:
I've been using 81 as my lowest. No problems. However you must test it first with the governor and scheduler. Some combinations may give you the symptoms of SOD but eventually it will wake. If that happens then it means the combo is not right
[Verizon Samsung Galaxy S III] scorchedsky:
Same here - I've been using 81 as my min for a while now. I'm also at - 30 uv, and 486 as screen off max, ktoonservative governor. No SOD ever, just a half-second of lag when waking the phone sometimes.
[Verizon Samsung Galaxy S III] pettigrew95:
Thanks for replies guys. I am using 384 as my min and my governor is lulzactive with row scheduler. Wondering if 81 would work with that governor/scheduler combo.
[Verizon Samsung Galaxy S III] savagebunny:
I use 189 as my min. Works really well.
[Verizon Samsung Galaxy S III] mademan420:
Running 81 min with ktoonservative/rom and UV'd for for about 5 hrs today with no issues so far:good:

Actually I sparingly used it (30min of screen on time) just to see if it would get the SOD. Still going strong!

Just changed screen off profile Mhz to 81. It was set to 486.
[Verizon Samsung Galaxy S III] Hans5849:
I found an error with Bluetooth audio, I can hear what's coming across the connection but no one can hear me. I initially thought the error was with CM 10.1, but after running with the stock CM 10.1 kernel and having audio work it's been narrowed down to this kernel. Here's steps I do to recreate the problem with the KTweaker Kernel

1. Turn on Bluetooth connection

2. Connect headset

3. Receive phone call

4. I can hear what's being said but no one can hear me

Attached are links to my logcats with Ktweaker, without, and my most recent KTweaker settings backup

KTweaker settings: https://docs.google.com/file/d/0B9TL6pX-UvCNTVFEU01qRXRBUUE/edit?usp=sharing

LogCat w/KTweaker: https://docs.google.com/file/d/0B9TL6pX-UvCNNmxSYlFwQzVxTTA/edit?usp=sharing

LogCat w/stock: https://docs.google.com/file/d/0B9TL6pX-UvCNMmt2a3o5MTJKYzQ/edit?usp=sharing
[Verizon Samsung Galaxy S III] thornev:
I'm one of the guys who ended up having to have this explained to me so I'll spare you from searching. There were math errors in CPU frequencies over 1500. Those frequencies are actually faster now in the later KT747 kernels so it is likely your phone cannot handle the speed, at least without cranking up the voltage. 1890 is in the same ballpark now as 2100. See my signature.
[Verizon Samsung Galaxy S III] mike216:
So what do you think about over clocking CPU'S? Do you think it puts a lot of stress on the CPU, Is it really worth it and do you OC your phone. Having a occupation related to computer science I figured you might be a good person to ask. I've read many different things on this?
[Verizon Samsung Galaxy S III] ktoonsez:
1674 is just perfect and is not gonna over work the CPU's and is what I have run since day one when I got OCing going. Its not much of an overclock but really help get things moving, especially when scrolling on web or XDA app :good:
[Verizon Samsung Galaxy S III] tihsllub:
Of course high frequencies are bad for processors. Some processors are more tolerant to higher frequencies than others.
[Verizon Samsung Galaxy S III] thornev:
OC'ing does make a difference. Screen transitions and program loads are noticeably faster. I'm a performance biggot. I overclock my desktop graphics card and my desktop memory and CPU. Do I worry? No. I figure before the hardware burns out that I'll be buying something higher tech anyway. Does OC'ing shorten the lifespan of the hardware involved? I've read that it does, but I'm a software guy and defer to hardware folks for that opinion.
[Verizon Samsung Galaxy S III] mike216:
Good point. I'm definitely an addict addicted to android crack. I always say I'll wait for my upgrade but never do. Already looking forward to the galaxy s4. Why worry about OC when I don't even get two years out of a phone. I OC my Samsung vibrant that I had back with t-mobile and is still going strong :thumbup:
[Verizon Samsung Galaxy S III] razz1:
I hate to say it, but still waiting for the GPU O.C.

It does smooth out the system a bit. It would certainly make the ultimate kernel considering all the govs and options. Non the less, this is certainly one of the best kernels out there no doubt!
[Verizon Samsung Galaxy S III] mike216:
GPU OC sometime gives more trouble then it's worth. When your developing for many devices chances are a % can't handle it. I hope if this is considered then there's two versions one stock or stock settings that boot first. If it's not broke don't fix it ;)
[Verizon Samsung Galaxy S III] ktoonsez:
Its been in my kernel twice since the beginning and it added nearly zero help to the speed of UI or anything else for that matter and caused people issue so I removed and added it twice. Qcomm just sucks so bad that it is just not worth it.
[Verizon Samsung Galaxy S III] mike216:
Not bad, 100% brightness!
[Verizon Samsung Galaxy S III] mbc663:
Wow, not bad at all for stock battery. Were u reading the whole time?
[Verizon Samsung Galaxy S III] mike216:
Mostly reading some YouTube and music. Stock battery. I'm happy with 4 hours plus. 5 hours makes me want to give ktoonsez a hug. :)

I'm broke out else I would have donated more but I will be making up for it Thursday.

Oh, the colors are absolutely perfect.
[Verizon Samsung Galaxy S III] mbc663:
I'd be very happy as well. Make a nandroid right now and name it perfection :)
[Verizon Samsung Galaxy S III] mike216:
I will be doing just that. Good time considering CWM just got updated to 6.0.3.1:thumbup:
[Verizon Samsung Galaxy S III] mw86:
Maybe check your thermals if on stock settings and over 60c it will throttle CPU and won't be able to reach 1600...

Please explain to the thread how you mean the over clock will not stick. Did you enable lock frequencies and enable OC and slide over to 1600mhz? Did you make backup with set at boot and see if it loads that MHz if loaded at boot?
[Verizon Samsung Galaxy S III] aypeeootrek:
Just flashed the latest tw kernel over goodness about an hour and a half ago over a completely charged battery. Also I have the gorilla gadgets extended. Getting constant battery drain atm. I have better battery stats and really unsure how to read it and tell what is going on. Took a screen shot of the kernel wake locks and an going to post it here . I believe it's appropriate for this thread so any help on what to do would be greatly appreciated. Have it at 1460/482 Pegasus/Zen. Whatever the top stat is, it looks like it never shuts down and I don't even know whether or not it should.
[Verizon Samsung Galaxy S III] sipock97:
Did you by chance flash the kernel while plugged in? If so, try a reboot. Seems like I read on one of these wonderful forums (at this point they all run together) that might be where the power management wavelock might come from. Worth a shot.
[Verizon Samsung Galaxy S III] aypeeootrek:
It was unplugged when I flashed but will try a reboot anyway.
[Verizon Samsung Galaxy S III] shawn01:
Hey Im running 3-14 tw on clean ROM r2. I run 3-14 over your newest release because it runs better for me. I recently reflashed and factory wipe I was getting wake locks. Since then I've been getting random reboots. Is it the ROM or the kernel. I run it as ktoonservative cfq. Or could it be the new zero lemon battery not playing well?
[Verizon Samsung Galaxy S III] mw86:
If you think you might have a bad battery load everything fully stock and see if everything is still happening then load ROM you were on and test still no trouble add kernel back on...
[Verizon Samsung Galaxy S III] brandoncarlson33:
im running your 4/11 kernel with deviantxone and loving it, thanks for all the hard work you do!
[Verizon Samsung Galaxy S III] Mattish13:
Been stable on 4/11 so far. TW
[Verizon Samsung Galaxy S III] pettigrew95:
Anyone using auto hotplug with lulzactive governor and 189 mhz min? I want to try it out for extra battery life and I think I can because I don't think lulzactive hotplugs on its own. Also, only other thing I'd be concerned about are SOD's since not only will one CPU be offline but I will be running a min of 189. Any suggestions? Thanks!
[Verizon Samsung Galaxy S III] tprophit:
Using kt737 3.4, 4/11, with carbon. Ktoonservative/row, oc to 1674, uc to 81, UV -50, except 1512 and 1674, which are stock voltages. No scheduler adjustments. Governor adjustments are boost CPU is 1296, sampling rate 90000. Rest is stock.

Screen off MHz is 378. Battery MHz control low 25/810, high 40/1080.

Battery life not that great.

Comments, thoughts, suggestions appreciated.
[Verizon Samsung Galaxy S III] srs731:
Not that great? Hour screen on time plus more than an hour phone call all in a 12 hour day. Seems pretty damn good to me.
[Verizon Samsung Galaxy S III] tprophit:
Well, I used to get more. Usually I have 2-3 hours of talk time ....trying to figure a way to optimize battery life for lots of talk time.

Thanks
[Verizon Samsung Galaxy S III] mw86:
Well just basic suggestions would be if you really want battery use Noop scheduler if balanced with more performance stay on ROW. You can always use a higher up threshold and up threshold hot plug value to gain more battery life at a linear shift towards more battery life and less performance.
[Verizon Samsung Galaxy S III] tprophit:
Thanks, trying now. What about uc at 81? Too low, or ok?
[Verizon Samsung Galaxy S III] ktoonsez:
Too low, my personal feeling is 189 with the lowest voltage u can go with is the best, its still enough horsepower to get some stuff done and doesnt have to ramp up so hard.
[Verizon Samsung Galaxy S III] airmaxx23:
The latest AOSP kernel is running great for me on CM10.1. I currently have 42% battery left after 23 hours 10 minutes while on 3G the whole time (no wifi). This is with 57% screen use and 2 hours 47 minutes screen on time. I'll post some pics once it's down to 20% or so.
[Verizon Samsung Galaxy S III] Aarongauntt:
Settings?
[Verizon Samsung Galaxy S III] Casper34:
Can you link me, the one in the first post roboots on me. I forced stopped tweeker, removed caches and all. Installed it. Ran fin for like 15-20 minutes then reboot. I went back to the stable version I was running and everything is fine since.

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] airmaxx23:
I'm using the 4/11 AOSP Linux 3.4 Version and TK Mod 1.0.2 with REricks Peq-Zen Performance 04-09 tweaks. It lowers the clock speed but I have not seen a decrease in performance or speed at all. If you have other questions just let me know.
[Verizon Samsung Galaxy S III] tihsllub:
Did you delete your battery stats? Data/system/batterystats.bin delete it. Your phone will create another one.
[Verizon Samsung Galaxy S III] airmaxx23:
Battery stats were deleted, I even double checked by verifying the stats in Battery right after I finished the last charge cycle and rebooted.

I'm now at 32%, 1 day 2 hours 33 minutes, 62% screen use, 3 hours 27minutes screen on time with 3G on the whole time.
[Verizon Samsung Galaxy S III] Stupifier:
Jesus!
[Verizon Samsung Galaxy S III] Casper34:
Stock battery or the zero lemon???

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] airmaxx23:
Here's the final results after 1 day 5 hours and 23 minutes which was connected to 3G the whole time. This is with the stock battery running the 4/11 AOSP Linux 3.4 Version and TK Mod 1.0.2 with REricks Peq-Zen Performance 04-09 tweaks on the official CM10.1. Battery stats were cleared before hand and verified as being reset.
[Verizon Samsung Galaxy S III] tprophit:
That worked well, significant improvement, with no noticeable change in performance :
[Verizon Samsung Galaxy S III] Casper34:
Here is my battery life today. I was at 4% for about an hour. Half way through the day, I updated the kernel. This time I didn't get any reboots and I forgot to force close before the update. I was running the 3-14 kernel before.

Sent from my PACmaned SCH-I535
[Verizon Samsung Galaxy S III] mw86:
Well that is great and thank you for taking the time to let me know I had helped you :) I am glad you have had only improvements in your results and no negative performance side effects. :good:
[Verizon Samsung Galaxy S III] tprophit:
Thank you.

I've read so much, and there are so many choices, it's hard to keep track.

I bumped the up threshold and up threshold hot plug to 67 and 68. How far can I go with for battery savings with minimal impact on performance. Which one has more of an impact, and do they have to have a delta of 1?

Thanks again.
[Verizon Samsung Galaxy S III] mw86:
There really is no limit but none of the values can be the same value or it causes conflicts.

Adjust slow buddy, run one set a day then raise and keep testing till its getting laggy. There's no good answer as you may get lag on what gives me none. We ALL use different phone settings and apps. I can suggest if 67/68 seems smooth try 75,80,85,90 and as you head to over 90 things yes could get to be laggy also it will save some moments to have a small gap in up threshold and up hot plug. Like 70/75. Its a balancing act. Touchwiz seems to be better raising these higher to help battery more so than aosp... Both benefit but really aosp has much less trouble to start due to lower ROM size and processes.

Stop in to a Team Kernelizer thread and a good amount mor of active users should have some contributing advice as well.

What is having a delta of 1?

Perhaps try 80 up and 85 up hotplug?
[Verizon Samsung Galaxy S III] tprophit:
Thanks. Going to start with 70-75 first....

Delta of one, I was referring to the stock 57/58, then the suggestion to change to 67/68....but you've answered that.

Thank you.
[Verizon Samsung Galaxy S III] dbornack:
Is there a way to permanently set Fast Charging enabled so I don't have to go set it every time?
[Verizon Samsung Galaxy S III] ktoonsez:
Sorry no, tried it for a bit then had 800 posts about why they cant get MTP working anymore and can't transfer files.
[Verizon Samsung Galaxy S III] dbornack:
Gotcha.. maybe that's been my MTP problem.. LOL.

Thanks anyways man. 4/11 running great for me so far on Slim Bean 3
[Verizon Samsung Galaxy S III] tprophit:
So, I changed to 75/80 this morning (after being off charger for an hour, and, 45 minutes of phone calls. Battery life considerably worse. Will charge fully and give it one more day. Other than battery life, no noticeable change in performance.
[Verizon Samsung Galaxy S III] mw86:
That's a strange result from that change, I'll be looking for your next update.
[Verizon Samsung Galaxy S III] tprophit:
Ya, I thought so. Will try tomorrow, although I'll be off wifi much more tomorrow. Today's, and yesterday's results were both with similar time on wifi.

Also, just noticed both sampling rate, and sampling rate minimum, are both set at 10000. Thoughts?
[Verizon Samsung Galaxy S III] daimerion:
Delete this please

Beamed in from my S3 with kt747 kernel and rooted/stock tw
[Verizon Samsung Galaxy S III] tprophit:
I've read elsewhere about v6 supercharger. Anyone here use it? Thoughts?

Thank you.
[Verizon Samsung Galaxy S III] Stupifier:
Most of the comments I read about it say it is more beneficial for older phones and hardly makes any difference on the S3. I still see some people have it tagged in their sigs for their S3's but I imagine they just liked it so much on their old phone they thought it would do the same on the S3.

I'd look into CrossBreeder. That is a more current mod designed for current phones that I've noticed improvements from.
[Verizon Samsung Galaxy S III] TheDriller:
I run cross breeder without the ad blocking because it breaks shortened db links and such... But crossbreeder effing rocks!

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] goldsmitht:
anything special to set it up? I tried it a couple of times, and probably had bad settings, cuz something was eating up my battery and it ran hot.

nothing against crossbreeder, just that i think i had bad settings

:cyclops:
[Verizon Samsung Galaxy S III] TheDriller:
Try the new one... Flash in recovery. I under volt quite a bit so my phone never gets hot. The newest one makes this phone as smooth as mayonaise on a corn dog lol

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] TheDriller:
LMFAO

7000 lemons? wtf!?!
[Verizon Samsung Galaxy S III] macman159:
Hey RErick. I wanted to know what are the correct steps of flashing ktoonz kernel? Isn't the same thing as other kernels? Or is there a step that someone needs to take before flashing the kernel? Every time I flash this kernel, I get random reboots every minute or less. Am I doing something wrong? I really want to try this kernel. Also, can you tell me if you have rev 0, 1, 2, 3, or 4? Also what is your cpu type? Slow nominal or fast? I want to know because I have rev0 and nominal and wanted to know if I could undervolt
[Verizon Samsung Galaxy S III] mw86:
Sample rate min is not something you can change it is a read only value which point out the lowest sample rate you can use. You should set much higher than 10k because what is happening is every 10ms the CPU must be randomly raising and lowering. Try stock 45,000 and your battery life should finally be back to normal. I wish I knew sooner as this was likely biggest kink in your works.
[Verizon Samsung Galaxy S III] tihsllub:
Wipe system. Flash. Clear cache/dalvik. Fix permissions. Reboot. Open ktweaker. Grant access. Deny access to other CPU state modifier apps. (i.e. setcpu, performance control). Anything past 1809 and most sch-i535 don't like it even if you OV your frequencies. I don't UV others do. Rev# have rumors but that is it. And CPU type. Its an Arm type architecture. Version 7 of course.

Sent from my.........
[Verizon Samsung Galaxy S III] tprophit:
Thanks, I have no idea how that got changed.....but it's back at 45000. Interestingly, I'm at 75%, 5.25 hours on battery, 40 minutes of call time, 35 minutes of screen time, and 15 minutes of gps on, and that was at the 10000 sample rate...

Thank you.
[Verizon Samsung Galaxy S III] tprophit:
This is bizarre. As I mentioned earlier, I have no idea how my sampling rate got changed. As soon as I read your post, I changed it. Noticed big battery drain after a couple of calls... it's Friday, need the phone charged up, and so I took the screen shots below, and then decided to check ktweaker. Sampling rate back at 10000!

Any idea how to make it stick?

Thank you.
[Verizon Samsung Galaxy S III] mw86:
No idea but a start is force stop and clear data on ktweaker app in settings apps all apps. Then without entering ktweaker reboot and try to set your settings like that again. It shouldn't be resetting if everything is working right
[Verizon Samsung Galaxy S III] tprophit:
Thanks. On it.
[Verizon Samsung Galaxy S III] TheDriller:
Edited:

Follow steps in the second quote.

I am rev 0 and nominal as well and I can usually under volt between 50 and 100 and still be stable

7000 lemons? wtf!?!