yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] mw86:
Yeah true stop mpdecision command can be used everytime at boot or make script with that and run it at boot but the easiest workaround seems to be Decimalmans suggestion which doesn't need to be run after its set and no longer seeting those logcat errors.

http://xdaforums.com/showthread.php?p=36240020

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] evouser22:
Ktoonz
[Sprint Samsung Galaxy S III] dcmasta:
I flashed this Kernel last night for my stock TW 4.1 and enabled the fast charging option.

The battery died a little while ago and now it's refusing to charge. I've tried different chargers pushing 1 amp.

I don't have the stock charger but this one usually does it. Any suggestions?

Edit

Finally came on after dicking around playing around with disconnecting and reconnecting the battery when the charge indicator came on.

I'm going to disable the fast charging for now.
[Sprint Samsung Galaxy S III] JAG50:
Download battery calibrator and delete the batterystats.bin file, shut down phone and try recharging battery.
[Sprint Samsung Galaxy S III] dcmasta:
Did that and now it's not turning on. All I can get at this time is the image for the battery charging but it doesn't stay on (displaying it is charging).

Edit:

Interestingly enough it won't boot if I have the charger attached. If I remove it then pull the battery it will boot then.

The battery is at 12% now but i'm not seeing the charging indicator on after plugging it in.
[Sprint Samsung Galaxy S III] JAG50:
When you do this, your supposed to let it charge overnight. Also, I would take battery to Sprint store. They'll give you a new one.
[Sprint Samsung Galaxy S III] slickdaddy96:
If you will look back in this thread you will see I had this problem kind of similar. I let the phone go to 0% and it would not charge. It would just give me the battery icon with the circle briefly. Wouldn't boot either no matter how long I let it sit on the charger. I didn't have fast charging on but I am running stock TW rooted with this kernel

I ended up having to put my battery in my wife's completely stock S3 and let it charge for a while. Then put my battery back in my phone and it booted fine and charged fine. Now I just have to be careful and not let my battery completely die until I can buy an external battery charger.

It definitely has something to do with the kernel, but no one really gave me a solution for the problem. Your battery isn't dead either you just need to charge it from an external charger or another S3. No need to take it back to sprint.
[Sprint Samsung Galaxy S III] akarol:
Happens to me too. All I do is reboot the phone in download mode by holding the power + vol down + home buttons together and click the vol down button when prompted to restart. That'll cause the phone to reboot fine. Saves having to pull the battery out.

Sent from my badass Samsung Galaxy SIII.
[Sprint Samsung Galaxy S III] slickdaddy96:
That didn't work with me. Tried to get into recovery and download mode and neither will pull up. Just the battery icon with the circle in it briefly.
[Sprint Samsung Galaxy S III] carhauler1969:
It's vol down + home then power, then volume up to get into download mode.

---------- Post added 7th January 2013 at 12:03 AM ---------- Previous post was 6th January 2013 at 11:49 PM ----------

Forgive me I'm a little out of the loop :o does this kernel (touchwiz) support exFAT file system on the external storage?

I've read through the changelogs, and searched the thread but can't find anything about it :confused:

Edit: The answer is no KT747-s TW kernel does not support exFAT, nor does Agat 3.2. Only the stock TW kernel supports exFAT :(

Hey KToonsez any chance of adding support for the exFAT file system to the TW kernel???
[Sprint Samsung Galaxy S III] Robalboa:
No it doesn't. If the over underclocking /over clocking is not enabled bluetooth min stays at stock min. 384

Galaxy S 3 32gb ...Sprint ;)

jelly bean LJ7 rooted....yahhhyuhhh
[Sprint Samsung Galaxy S III] youngpro83:
Maybe someone can help me. I have searched but to no prevail. Basically I go into ktweaker, go into my cpu adjustments and tweak them. Then I exited out of the app. When I go back into the app the ktweaker app says that my settings do not match my saved settings and asks if I would like to revert back to my saved settings. This happens each time I open the app. Is there something I should be doing to get these values to stay after I exit the app? Thanks in advance for any help given.
[Sprint Samsung Galaxy S III] jcdominguez:
Have you removed the script from system/etc/init.d ? If not navigate to that folder and remove 70cpu or anything that might say CPU in it. Don't delete enable-oc file. That should get rid of your message. It might be more to this issue but usually this is caused by a script.

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] JAG50:
Robalboa

I enabled over clocking, even though I kept the standard clock speed (1526) as default. Just because you enable doesn't mean you have to overclock device. Just try it, adjust Bluetooth speed and see if it eliminates the crackling.

---------- Post added at 03:34 PM ---------- Previous post was at 03:30 PM ----------

Youngpro,

Did you update kernel to 11 Dec? I was having same problem with 13 Nov version, but went away after updating.
[Sprint Samsung Galaxy S III] youngpro83:
Here is a picture of what I have in my init.d folder.

Yes I am updated. I am also running Freezas Deodexed LJ7 RoM. (Name may be off.)
[Sprint Samsung Galaxy S III] JAG50:
Well, go into recovery, erase cache/dalvic and reinstall kernel. Erase both again after installing and then fix permissions. That should do it.
[Sprint Samsung Galaxy S III] GTOJim:
Never mind
[Sprint Samsung Galaxy S III] rdhddmazoku:
I saw this mentioned in this forum, but did not see any solutions posted. I too have the issue where the battery will drain (quite quickly actually) to 0%, shut off, and then I am unable to get it to charge unless I put my battery in my friend's phone or I go into recovery. The funny thing is once I put it in my friend's phone it says I have like 50% battery, but it died at 0%. When I get it back in my phone, it will say the right % for a while and then it quickly goes down and dies. I am using Team Sonic FreeGS3 3.0 and it installs the kernel through Aroma. I add .bak to all of the suggested files and not adding bak to them with no difference. If I switch back to the stock kernel, the battery works normally. Any news/ideas on how to fix this?
[Sprint Samsung Galaxy S III] stricklerjosh:
Question, if I'm on agat kernel with odex blue by SS, do I have to flash anything before I flash your TW kernel? Or just wipe both caches?
[Sprint Samsung Galaxy S III] jcdominguez:
I would flash the kernel cleaner found on the OP this will ensure proper kernel cleaning and avoid any problems. Flash the cleaner first then the kernel.

Also make sure to follow the TW recommendations for this rom. Such as adding .bak to a few files located at system/bin

See: http://xdaforums.com/showthread.php?p=36050868#post36050868

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] mw86:
Has wiping battery stats helped that issue? As this could be related to corrupt entries in your battery stats. CWM RECOVERY latest does not have it anymore but it used to be an option. There are a few apps on the market that can wipe the stats, not sure of a good one off hand but I would try that as well since the kernel is only part of the whole picture.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] decimalman:
Ktoonsez, there's a commit you might want to look at. I was reliably able to reproduce the horrible lag people were mentioning after the 12/30 build until reverting this commit. I'm not sure how exactly it's causing problems, but reverting it seems to help (as always: IWFM, YMMV). Even though Cyanogen first committed it on 12/21, it doesn't look like that commit would have made it into your 12/21 d2att build, but it should have been in the 12/30 one, where people first mentioned the bug.

EDIT: Nevermind. A couple hours of trying to reproduce, and 30 seconds after posting the lag is back.
[Sprint Samsung Galaxy S III] dyehya:
Can we add an option to ignore screen off MHz when plugged in like there currently is for in a call?
[Sprint Samsung Galaxy S III] rdhddmazoku:
Wiping battery stats did not help at all. I thought that was the issue at first, but it continued to die just as fast and misread just as much. I tried a clean wipe with no TB or other kind of restore. As soon as I put it back on stock, its just fine.
[Sprint Samsung Galaxy S III] slickdaddy96:
What kind of life do you get on it with the regular kernel? If you are getting less than at least 12 hours or so maybe look at getting your battery replaced. Maybe it is faulty.
[Sprint Samsung Galaxy S III] rdhddmazoku:
It will typically last about 14-16 hours with regular use, less if I have the screen on a lot, stream music, watch videos.
[Sprint Samsung Galaxy S III] ktoonsez:
Ill think about it once 4.2 settles down.
[Sprint Samsung Galaxy S III] clothednblack:
@ ktoonsez

I sent a pm, I know you are busy and have been sick, I've had previous issues with pm's so never know if they were recieved. :)

Ridin the Mystic inverted jellybean unicorn on my Ktweaked SG3
[Sprint Samsung Galaxy S III] slickdaddy96:
Well in that case I would advise you to wipe everything back to factory. Flash stock TW JB again and run with it for a few days and see how it works for you then flash Ktoonsez kernel and let it run a few days and see if that fixed the problem. Obviously if you are having drainage from qsmgr or whatever it is called after installing his kernel just rename it with Bak at the end.
[Sprint Samsung Galaxy S III] boglwe:
I have installed ktoonsez kernel on jellybam. But I cannot seem to get to governor to go above 1500. Am I missing something. Thank u in advance.
[Sprint Samsung Galaxy S III] awillis111:
You have to click "Enable OC Steps" above the adjustment sliders.
[Sprint Samsung Galaxy S III] rdhddmazoku:
I will certainly try a third time and see if that makes a difference, but I am not very optimistic that it will be any different. That, and from the few posts on this thread and on the Team Sonic FreeGS3 thread no one else who had this issue got any resolution either. If there are any logs I can provide that would help I would be happy to post them.
[Sprint Samsung Galaxy S III] slickdaddy96:
You all got any reasoning for my S3 to just randomly quit keeping accurate time. It is set to get it from the tower/network but sometimes it doesn't. I end up having to restart or go into airplane mode and back to get to set it right.
[Sprint Samsung Galaxy S III] mw86:
Not sure its happened to me in the past. At the time i had network issues like it would not get voice/text even... Doesn't seem to be touchwiz or aosp only issue as i have had that rarely on both. Thats all i remember of my clock having the wrong time. I had to reactivate after one of them.

GS3 L710 4.2.1 AOSP Kt747 2.1Ghz ROW/Ktoonservative *Tapatalk
[Sprint Samsung Galaxy S III] Custodian:
That happens to me too when im gazing at my phone like its a thick white girl.

Sent from my SPH-L710 using Xparent SkyBlue Tapatalk 2
[Sprint Samsung Galaxy S III] JAG50:
It's happened to me as well two or three times. Had to unclick automatic date/time box for it to reset.
[Sprint Samsung Galaxy S III] monty_python:
Any chance of getting two way call record kernel support..
[Sprint Samsung Galaxy S III] ktoonsez:
Never found any examples to work from so you'll have to use the app made for that.
[Sprint 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

*****4.2 Specific*****Change Log 1.9

1. Added Yoyo mode to ktoonservative (mimics the test from 1/5) and is DISABLED by default

2. To enable yoyo mode, set "use_yoyo_cpuload" to a 1, I recommend setting "cpu_down_block_cycles" to a 22 or 44.

3. You can enable yoyo if you feel ktoonservative is lagy since moving to 4.2. It does jump around the Mhz range and hotplugs the 2nd cpu alot more than normal mode but is very responsive!.

ENJOY
[Sprint Samsung Galaxy S III] jcdominguez:
Can someone explain zen vs/difference bfq.

Is one recommended over the other.

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] JAG50:
I tested new kernel and its only 24.9999 billion faster. What's going on? :)

Also, I went to main page and your profile to find donate link and the profile link doesn't work. If you send link, I'll send you some John Adams' funds.

Hope others follow suit. This kernel its proven and its rock solid. Ktoonz deserves some remuneration for his hard work.
[Sprint Samsung Galaxy S III] ktoonsez:
Thanks man, glad you are enjoying :D. Here is the link and it is also at the bottom of all of my posts (below the blue letters that say "If you like my work, donate with this link:"):

http://xdaforums.com/donatetome.php?u=4325945
[Sprint Samsung Galaxy S III] luckymoney718:
I'm running the new ktoons kernel. My phone seems to get fairly hot after moderate use which I know can lead to draining of the battery any idea what can cause my phone to get so hot? Thanks in advance
[Sprint Samsung Galaxy S III] jcdominguez:
Are you changing the voltage? What are your settings.

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] jcdominguez:
What about voltage chart

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] luckymoney718:
I notice you guys don't use battery saving apps is there a reason why??
[Sprint Samsung Galaxy S III] GTOJim:
If overclocked, using phone while charging will cause it to get hot. Especially if running stock voltages.

---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------

Some use Juice Defender, properly configured it can save juice. Also you might check out this thread, kernel and other tweaks to improve battery life.

http://xdaforums.com/showthread.php?t=2032956
[Sprint Samsung Galaxy S III] luckymoney718:
I don't use my phone while it's being charged
[Sprint Samsung Galaxy S III] jcdominguez:
Luckymoney voltage might be why let me recommend you do the following

1. In ktweaker hit load defaults

2. In general enable OC, adjust min 96 max 1800, then lock frequencies

3. Click on I/o scheduler And choose bfq

4. CPU governor ktoonzervative

5. Disable touch boost

6. Go to voltage if you get a message asking if you want to load default hit yes and hit menu and subtract 25 all across hit apply

7. Set options on boot immedietly

Do that in that exact order. Report back. Also if you are on a touchwiz ROM do t forget to add .bak to the following files see scteenshot

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] jcdominguez:
....also remove 70cpu (can't remember full name but it has a form of those variables) from system/etc/init.d if you have it

Also please verify that it is the battery. I've experienced a hot device and upon removing the battery I found out it was not hot. My CPU (or internally) was actually producing heat. If so we are dealing with CPU and not battery.

___________

Device: Sprint Galaxy SIII

ROM: Jellybam

Kernel: Ktoonz KT747-Kernel-AOSP

Settings: Mhz 96 min 2106 max

Gov: ktoonzervative UV: -25

Battery: 23 hrs w/5h screen time

Proud contributor and tester of Team Kernelizers!
[Sprint Samsung Galaxy S III] mw86:
I see thats a minor hiccup I would be so in gratitude if you managed to fix that boot of the kernel initialization. As CM10 keeps updating CPU score shouold get closer to my ICSs runs as well as the I/O. btw I always had SD cache to 2048 from 128 and SIO on your kernel or NOOP and NOOP was the only one available on Kettle Corn that I saw worked that good... Deadline gets bottle necked I think. Noop is it I think scales with CPU :) win win there. What mv did you run 2106mhz for :) thats so cool. I noticed something Ktoonsez. once in awhile could of been software playing with me... but I monitor cpu speed and usage with Cool Tool from play store and I noticed if the mv for 1890 is 0ver 1300 it would drop into 1100mhz range a sec or stay there and give me trouble setting it. but the lower i went on voltage it did that less but as you know isnt stable if you start lowering the overclock range like that by much at all. I think it may be heat is there a protection built in like a throttle at a certain temp? What is the most accurate way to monitor cpu temp... given i know almost any of them are very in accurate and sensor can be off. I am going to leave a bunch of apps off my phone till I get a handle more on the performance and that way perhaps conflicting software wont throw me off. what exactly are you using Kbizzle for setting volts and same for mhz and governor + scheduler... you can set in rom settings with no volts and no scheduler options and system tuner has volts, speed, governor, scheduler, set cpu has volts, speed and governor and voltage control has volts, speed governor and I think scheduler. I'd like to stick to one of those. As between all those and the roms settings I sense boot options could start conflicting. So whats your preference Ktoonsez?

thanks about the scores... those are basically IMO peak performance... not in anyway an average. So for both it paints a good picture of how things are going based on subscore... the overall score on quadrant is a worthless comparison and subscores seem to show all. I should retest with another bench something that is technical. Is Chainfire bench etc good to compare the two?

I'm loving this kernel. I'd be glad to test any extreme ghz (ie >1890mhz) versions in the future (. feel free to PM me Ktoonsez. Im not afraid of lockups in testing as long as I can remove power and boot CWM to reflash to reset things... just hit me up :fingers-crossed:
[Sprint Samsung Galaxy S III] jamcar:
Me too I'm loving it! Also I will test too but I'll be using TWRP
[Sprint Samsung Galaxy S III] Felnarion:
There most certainly is a built in throttle. On most of our phones, it kicks in between 1736 (or whatever the exact speed is and 1890. You'll notice, especially if you go to the kettle corn kernel thread, that most of us actually lose speed/fluidity at 1890 and above. Even though it is stable, it is slower.
[Sprint Samsung Galaxy S III] ktoonsez:
Yep. That is exactly what I see. I have raised the buss speed and it is a little better but nothing huge.
[Sprint Samsung Galaxy S III] mw86:
Thats what I see on any Jelly Bean rom ive tried so far but on Blazer it didnt do that on mine. The governor gave me trouble but if i set to on demand min and max and watched cool tool it doesnt drop on mine. Thats why quadrant is scoring almost 10k cpu on Kettle Corn ICS. performance governor for me doesnt lock at full speed but on demand did for me. My Score scaled with mhz on Kettle corn and didnt drop when i got to 1890. The score was higher for me than on 1700mhz. Im not sure why I had different results.

Any thoughts on why mine is handling different?

Edit: gonna add thanks but ran out

Edit2: hey guys reread the kettle corn thread for more ideas. I came across quite a few with similar results you guys are reporting of 1700mhz scoring and handling better than 1890-1800mhz. What I noticed is sometimes governor would give me trouble setting the frequency and sticking. This followed on a few overclock apps. Voltage control and System tuner set to on demand and playing with the min max slider a sec i can lock it at max 1890 and min with no drops. On kettle corn and this kernel. Interesting thing i noticed is that CM9 bases vs our Jelly Bean scores score similar with I/O just a bit lower on Jelly Bean. See here http://xdaforums.com/showpost.php?p=28709862&postcount=99 that post results and the following one after the next post has more resukts of CM9 on Kettle Corn. We see CM9 around 5-6k cpu 12k+ mem and i/o around 5-6k. 2d and 3d around same as others. jelly bean Scoring same in those areas but slightly lower i/o around 4k. The ICS blazer with kettle corn scoring 9k+ cpu 8k+ mem 7k+ i/o. I had a 6007 overal with almost 10k cpu low 9k mem and low 8k i/o. I lost that along with all my antutu results for the same roms and kernels. Im going to redo those and add chainfire benchmark to get a broad picture of differences. I had Velammo too but will leave that out since its qualcomms own test.

To clarify I just like to be investigative. I already knkw Jelly Bean is the superior OS. I also see ICS blazer gets high cpu medium high mem. cM9 and Jelly Bean CM10 get medium cpu but extreme high mem... strange it is and its repeatable and happens on stock or this kernel... so its not overclock related as to why they score like this. This could be that memory has been optimized through the roof in these JB and CM9 roms and cpu i have no theory why it would lower. Ill post results when i have more built up again. It may be a day or two.

Glad to hear what you guys think.
[Sprint Samsung Galaxy S III] Custodian:
Can we use Extweaks with this kernel? :)

Sent from my SPH-L710

---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------

Well scores dont mean much. Ijs. :)...

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] nicholaaaas:
That'd be awesome if that got working
[Sprint Samsung Galaxy S III] dtr145r:
nope.

i did pm you but never got a response.

:)

thanks

my phone went 51 hours on a single charge with this kernel.

normally id only get 12-13 hours.
[Sprint Samsung Galaxy S III] ktoonsez:
Uploading new kernel, still cant get things stable for 2106mhz so you guys will have to wait on that. But lots of great upgrades :D
[Sprint Samsung Galaxy S III] nicholaaaas:
i guess i'll sit here and hit refresh for awhile
[Sprint Samsung Galaxy S III] Custodian:
Honestly we don't need to go past 1.8ghz since it is the highest stable correct?..
[Sprint Samsung Galaxy S III] ktoonsez:
OP Updated

AOSP JELLYBEAN: Download CWM flashable zip kernel

http://www.mediafire.com/?xb4hrcjqgr2wp7x

Change Log 8.15

1. Updated to latest patches from CM team

2. Linux 3.0.41

3. Lots of tweaks to the Normal and OC'd mhz ranges

4. Upped bus frequencys on a few steps for better performance

5. Lowered minimum voltage to 700

6. Upped maximum voltage to 1400

7. Added govs: abyssplug, badass, lagfree, scary, superbad

8. So much other underwear..........
[Sprint Samsung Galaxy S III] ktoonsez:
Probably not, but there are curious people out there :D
[Sprint Samsung Galaxy S III] IcOpRo:
Awesome can't wait to flash, thanks
[Sprint Samsung Galaxy S III] nicholaaaas:
depends on the phone really. mine doesn;t like anything over 1.6 or 1.7

---------- Post added at 10:02 PM ---------- Previous post was at 10:01 PM ----------

I was just about to ask about further undervolting