yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
For tw users qualcomm throttle will still exist. So you are safe. The new KT cooler ;) will come to TW eventually and so far in testing is outstanding!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I know you're going with your personal experience. But in all reality, your personal experience with wiping battery stats on this device was nothing but a stroke of luck. Because this device does not work that way and wiping battery stats with a 3rd party app or recovery will do absolutely nothing to touch this devices fuel gauge. Its just how it works. Its good that you've gotten that luck though. Sometimes placebo is one of the best things a user can experience. I'm sincere when I say that too. :D

P.S- We don't need to go into this any further and potentially derail this thread with this stuff. Just wanted to fill you in if you didn't know for sure. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Thanks, I might just switch over to Tasks AOKP, because I'm curious.

Would the easiest way to do it be to port my backup to a separate External SD, flash Tasks, and if I dont like it, flash back my stock Rom with KT Kernel with the seperate SD card?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
It would be exactly the same as any other ROM/ kernel you've flashed. Make backup to external, wipe wipe wipe, flash new stuff, restart, money.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amwbt:
Does this kernel support FauxSound mod?

Sent from my SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crash822:
Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Thanks, I'm gonna try real soon.

Another question, if I restore the backup through either CWM or Rom Manager, what option do I choose to restore the backup because I've seen various?

And it's basically flashing a Rom(backup) back to the exact state it was, correct?

Sorry I've never restored a backup. Never needed to yet. (Crosses finger)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Reboot (last_kmsg attached)

Installed the newest kernel along with task's AOKP and everything was great until I started up Netflix and the phone suddenly restarted. I've attached the last_kmsg if it helps...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks like a bad interaction with the ROm and kernel for the video driver stuff, nothing we can do till the genius Cyangen gets all his patches back in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
So are there alot of people lagging behind and still using the AOSP 4.2.2 3.0 kernel? Before I waste time updating that one????
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I'm sure there are some. There always are. You might help persuade them to switch if you stopped updating it...

BTW, your newest 3.4 kernel runs Netflix just fine on the CM 0404 ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mdoctor:
Most SlimRom users who also use this kernel, have to use the 3.0 version. I for one have been on SlimRom from the original galaxy s days. But I like the choice of governors and schedulers on your kernel. So I would like you to keep it updated until Slim releases a 3.4 version of their rom. Having said that the current version works just fine for me, so it's entirely up to you. Your latest version of 3.0 is very stable, so I would not worry too much if you decide not to update it.

Thanks for all your hard work on this.

Cheers,

Md
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok, I just got back to hotel and checked the 3/27 download count and it was about 3,000 so I guess you aren't alone, lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Same here, on SlimRom that still uses 3.0... I'm on the 3/14/2013 kernel actually because the 3/27/2013 kernel was giving me errors here and there and force close, and I used the same install method for both.

Your call, but like mentioned above, if you do update it, great, if not, it's still fine.
[AT&T, Rogers, Bell, Telus 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/FZFVb

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)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
I'll give this 3.0 a try and report back tomorrow with a bit of use!

Thanks for the update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
All anybody has to do to test if I got it working is to 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. Please let me know ASAP guys. :highfive: :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
I'll download Antutu and give it a shot, what settings should I use? On the previous versions I would use ktoonservative and row, should I use the same settings?

Should I leave all settings as is for now without any OC when I do the benchmark testing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Touchwiz JB Test kernel, reboots are GONE!!!!!!!!!!!!! (just as good as a release, I think)

http://goo.gl/Lvn2j

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)

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 (best if you do it while plugged in as the charging will add some heat) and then do the normal Benchmark test with the "LOCK FREQUENCIES" OFF, no reboots then you are good to go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
All I did was OC to 1674 to get it to 60 degrees C which is when kthermal kicks in and the old thermald would have screwed u over, lol. Use whatever other settings you want.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
If having trouble building the heat to do the test do the antutu testing plugged in on charger and it adds heat to battery cpu by nature of charging and won't be an issue if just running it like that for this few minute test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Got it, will download tomorrow morning, as I can't tonight and report back after some use!

Thanks again for the great support, I feel that my donation was paid off a long time ago!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Downloaded and installed twice locked up on boot both times...? File that downloaded is about 8mb much larger than previous files...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Because you are loading 3.0 Linux kernel on a 3.4 ROM!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Confirmation number: 3A705348P5147653U

Hopefully that joint has a bar...have one on me bro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks man :D. No bar though :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
I gotta stop doing this stuff when I'm exhausted... This makes TWICE! :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Wow...this Task AOSP is soooo buttery smooth. How did I live on TW??? Feels so bare bones though.

Gonna try loading the KT kernel on next. Thanks for all the help guys. Ktoonz , you the man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
TW=poop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Dl now, see you on the other side.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
The post was written by an Android engineer. It's literally science that all that gets stored in the battery stats file is info about battery usage not remaining charge. There is likely another explanation for the result you are seeing. Maybe clearing the battery stats file forces the battery to reset its circuitry, but there is no information about how much battery is available stores in that file. If there were, anybody who pops in a full battery after running their first battery to 0% would be screwed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Passes stability test just fine, only reboots were intentional (and didn't result in a bootloop).

Battery control mhz high and low governor adjustments still don't stick in ktweaker though.

Pristine, super wiped synergyrom install (r443) from rooted stock. Qqosmgr renamed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
Is, there a 3.4 aosp jb version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Right in the op
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Thanks for the feedback. For battery Mhz Control, your setting them to bad values then. Thats why they dont stick. The low values have to be lower than the High values or it wont save.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Just got down to 1% battery. I had a total of 14 1/4 hours and 4 hours screen on time, without having to plug in at all. Literally the best battery life I've ever experienced. No more reboots. I'm using conservative and row, with a couple of governor tweaks. My voltage table had gone up in the new release (lowest values went from 850 to 900), so I'm undervolted -100 across the board. Amazing work, ktoonsez! If I hadn't just lost my job, I'd throw a few bucks your way, but I know you can run on gratitude too, haha. :thumbup:

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Need some more feedback on the 3.0 and Touchwiz guys, Im getting tired and want to know if I got it worked out :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
The op file for 3.4 is from 3/27, is there one for 4.4 thermal fix? 4/3 didn't fix the reboots for me. Had to rename the thermal file to fix. So, hopefully 4/4 version fixes it for 3.4 Linux, aosp version. Willing to test! :)

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Attached ss of what I'm setting that's not sticking. Every time I go back into ktweaker it says the values don't match, would I like to set them.

No matter what answer I give, both high and low frequency are back at 0 by the time I get to this screen.

On a positive note, 81mhz no longer SODs my phone though, far as I can tell it's running the full range perfectly.

Not too heartbroken about the battery mhz settings, I only really started playing with them a few releases back. Being able to run 81mhz makes me much happier :D

Edit: I did try swapping the values too, 1080 for 810 and vice versa, just in case the was a mismatch in the naming. Same effect
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
4/3 currently is the most recent for aosp 3.4 and does include the thermal fix already I believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
Regarding the TJ kernel... I turned off lock frequencies, cranked the oc up to 1800, put the cpu governor to performance, ran the stability test for a bit while charging, and successfully ran a regular benchmark. No issues or reboots.

How can I judge temperature? I don't think I see that in ktweaker or antutu and I'm not sure if the phone got hot enough for thermal control to kick in. I'll stay on these settings and see if stability test makes anything unstable.

Thanks ktoonsez! Get some rest!

Added after more testing: I ran the stability test and watched in ktweaker. My cpu started at 1800 and went down to 1400. I'm guessing that's your thermal control kicking in? Everything is still stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
It did for sure, only takes about 30 seconds into benchmark to kick in, but if your good with adb you can run this from your PC while plugged in usb:

adb shell cat /sys/devices/system/cpu/cpufreq/kthermal/current_temp

KTweaker will have the current temp in next release on the "General" screen and in the new "Thermal Control" screen in Extras :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Ok, I got it now, whoever requested the dropdown Mhz selection be in that governor adjustment screen is who screwed me over, FLOAM. I think I got it. Your a Touchjizzer right?

IF SO, download this to see if it fixed it:

http://goo.gl/Sx1KB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Yessir that's me :)

I like the drop downs, but I'm not too good to enter it longhand if I have to

I'll report back shortly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
4/3 version works for 3.4 Linux, aosp. Ran all the tests and no reboots. Not sure why I was getting them before.

Thanks!! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Edit: hold up, I'm a dumb ****, I fat fingered it and froze ktweaker wiping the data.

Re edit: you nailed it boss. Working 100% min 81 max 1.5, all settings stick. Flawless victory.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Excellent :D. And it still uses the drop down list right? :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Excellent, and FLOAM, read any of the last 27 pages and you will see why some were getting reboots :D :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Yep, absolutely zero unexpected behavior, no error messages, sails right through stability test and still no sod with min at 81mhz.

Perfect functionality

Edit: Antutu stability test is actually running as I write this and I just saw ktweaker set the frequency for 40% battery, then watched it go back to full speed when I plugged it in.

So it's definitely functioning perfectly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Are there any other Samsung files that cause problems that could be re written? Just curious about what's under the hood, ya know for science.

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Still have to FC and delete Ktweaker data to install the new TW kernel if coming from 3/14 right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its a good idea yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daymz:
I tried the 3.0 kernel version 3.0.69 (03/27) on my Bell Galaxy S3 (I747M) running CM 10.0 release, and I had a number of issues. I don't know if they are known or not so I just thought I'd report them.

Kernel installation procedure:

- Reboot in CWM 6.0.2

- Install zip kernel

- Wipe cache (x2)

- Wipe dalvik cache (x2)

- Fix permissions

- Reboot

Issues:

(1) One skin in Beautiful Widgets is no longer displaying the time. Sense V2 is the skin name. I know there was an issue at some point in ICS 4.0 on my Asus TF201 tablet with large fonts, maybe this is related (or not).

(2) There are display issues in apps screens, which get wiped out. Forcing a refresh of the display (such as initiating a drop down of the notification area and pulling backup, or scrolling the app`s screen up and down if it can) solves the issue, but it`s annoying. I`ve had this happen on the Calendar (entering the screen, virtual keyboard popped up), on NewsRepublic within 30 minutes of use. I never experienced this before using Samsung Stock firmware or CM`s default kernel.

(3) Video issues running MX Video Player, some extensive action scenes had the FPS drop to a couple frame per second. Audio was running fine. Never had that behavior either with Samsung Stock firmware with the CM and the default kernel.

(4) Some cracking noises in bluetooth. In 15 minutes of listening, it happened 3 times. Pretty noticeable. Again, never experienced any of these with either

Other than that, it seems like it was running pretty well. For now, I've returned to CM's stock kernel mainly because of (2) and (3). (1) was fixed by installing a different skin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Bw works fine over here. Mxplayer and bt also. Wierd. Not going to tell you to try full wipe as you already know to do that I assume.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Very quiet in here, everything must be running great on the new kernel's from last night :D :p :good: :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
I'll get a random reboot every once in a while. Would that be logged somewhere as part of a system function?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fendulon:
It all seems to be running pretty well. It's definitely smooth, can't report on battery until I go through a cycle. I am running the latest PACman stable and I am getting an occasional freeze up. Screen won't turn on at all and I have to hold the power button until it powers off and then I boot it back up. I was a little undervolted so I've upped that to see if it happens again.

Loving the kernel though, good work and thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
/system/proc/last_kmsg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
What version of the kernel? What date? What ROM? Are you UC'd, UV'd or OC'd?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExBrasil:
Thank you, good sir. I haven't had a chance to flash it yet being that I'm working, but I'm going to try later on today. Then, once I find out how to easily get all of my info+data back on the phone after flashing Tasks AOSP, I'll try with that as well.

TiBu restores the apps to my phone but not the info from them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
Toons again u r the man running flawless and perfect love ur work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
4.3, AOSP, 4/3, Task's ROM, -75 UV
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You probably UV'd to much then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
TJ user here, new test kernel and tweaker 3.1 have been flawless. Antutu runs without problem (lock freq off). Mhz high and low stick. Kt your work is unbelievable!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
Been solid as a rock on AOSP 3.4. Zero issues, amazing battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Babydollll:
The latest 3.0 AOSP kernel works flawlessly. I'm running Slim build 3 btw

(I left all the settings as you set them when I flashed)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NycKid175:
Instead of -75 go -50 not all phones take UV the same like my phone would not take -75 so I changed to -50 with no problems
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
some people with issues should try over volting. it's not going to make a huge impact on battery drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nickovtyme:
I flashed the newest 3.1 onto the Intergalactic TW JB 4.1.2 and it seems to be working fine. OC'd @ 1.7 uv'd a few volts - no noticeable hiccups, freezes or bootloops.

Ktweaker is maintaining a cool temp reading and kThermal says that its throttling which is what I hope its supposed to be doing.

Thanks^

sent from my Intergalactic s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
Has anyone experienced an msm_otg kernel wakelock? Betterbatterystats is reporting it and my phone won't go into deep sleep. I'm losing battery like it's going out of style. My Google-fu let me down and I couldn't find a solution. I do not use any OTG devices. Any suggestions on what I should look for?

Running PACman 22.0.1 April 3 nightly with 3.4.38 kernel (April 3).

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
This has to do with the ROM, not the kernel. It's triggered by booting while your phone is plugged in. Rebooting while your phone is not connected to power should fix it. I know task fixed this recently in his ROM and I'm guessing it was a CM commit that he incorporated. You might ask the dev for your ROM if he knows anything about this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jgaf:
Try connecting the phone to your pc and removing it. That fixed it for me when I had that problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I'm using the last PAC-Man release klin did before switching to nightlies, and I haven't seen that issue. Haven't found time to try the nightlies yet.

AT&T Samsung Galaxy S3

Current ROM: PAC-Man (klin1344)

Current Kernel: KT747 (ktoonsez)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Still awesome on TW and I decided to hammer it a bit too.

Apparently 1890 is the magic oc on my phone. Anything higher and it reboots instantly.

Plugged in, oc to 1890, and running Antutu stability test all the way through, 3x back to back, it didn't get hot enough to start throttling until halfway through the second run.

Still no reboots, sod, etc. It's as mild mannered and stable and clean as can be. I think this weekend I'm going to see what I can get away with in terms of uv.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Task650 explained it very nicely. This wasn't very necessary but thank you for the additional explanation. I think something else fixed my issues and It just seemed it was the stats. I don't know but maybe just a battery pull and letting it sit was what fixed it. In any case we have the topic well covered and I will not recommend users to wipe battery stats bin if having charge issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
I was on a phone call and the phone locked up and then rebooted after a few minutes. This has happened a few times in the last few days and here's the last_kmsg from the last time it happened. When I was looking at it, I saw a lot of "cpufreq_gov_resume_gov_DENIED" so I assumed it might be something you guys could help with. I'm running the 4/3/2013 KT build and CM 10.1 4/5 build (3.4 kernel). If it helps at all, when I use bluetooth it doesn't seem to be an issue.

I have UV -25 (I was having problems with -50 awhile ago) and a screen off of 864, but disabled while in a call. Otherwise I'm using ktoonservative and zen with no OC.

Thanks guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
Thanks. I read a lot about it being related to the kernel which is why I posted here. My bad. I'll try to boot with it unplugged to see what happens and will reach out to my ROM dev.

Edit:

Rebooted with the phone unplugged and the wakelock disappeared. All good now. I'll have to remember not to boot with the phone plugged in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] waiters:
Still doesn't work for me. I enable oc steps and attempt to move slider.. Kt crashes..

Then open back up.. Move slider.. Auto reboot..

If I leave it non oc.. Stock settings.. Seems to work fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That is a well known ROM issue. I get them too but I always had to reboot manually. Maybe this last kmsg will reveal something. The denieds are no big deal. Just my debug stuff
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
How far are you moving the slider when you start it back up? I know the phones tolerance for oc had dropped considerably with the new math. If I take mine past 1890 it's an instant reboot.

Mine crashes ktweaker the first attempt at raising clock speed after enabling too, but after I start it back up it works fine as long as I stay below 1890.

I'd also recommend stock voltages or higher if you're going to oc, at least until you know where the new tolerances are. I haven't even begun monkeying with my voltages yet on the latest kernel