yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] xkjtx:
Update?

I found on the site an update (05-07-2014), but there was nothing about it here.. Anyone check it out? Just wanted to know a bit about it, but I can't find a change log.. Any help? Thanks!!..

xKJTx
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
5/7 is already up in the OP for AOSP 4.4 versions. Here's the change log. Nothing much but kernel and ramdisk code enhancements.
[T-Mobile, Samsung Galaxy SIII] xkjtx:
Fast reply!!

Thank you for quick reply! That is what I was wondering.. Always a good reply very quick!..

-xkjtx

Edit: getting Error (Status 7) set_perm and it wont install (version 5-7-2014)..
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
What recovery and version are you on?
[T-Mobile, Samsung Galaxy SIII] xkjtx:
Wow, what the reply!..

You are brilliant, well and me too with understanding what your reply meant. :D I saw into your head!!! :cool: lolol

I updated my recovery through Rom Manager(free on google play) and then flashed again, everything is working great.

I will reply back if I find any issues or glitches.. I guess my recovery had some sort of issue and now not any more!..

Thanks again for the great and fast replies!..

-xkjtx
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
There's really nothing much left to say as what I was going to mention has already been stated. However, in addition to that I would like to say that the more features added/merged into a ROM the more difficult it is to keep that same optimal battery life you once previously had. They require so many background processes to keep the phones running as smoothly as possible The kernel will only push out what is fed to it by the ROM and apps installed by the user so I'd like to think that it's more the ROM than the actual kernel, at least for the most part in this case. Understand that ROMs today will cause more partial wakelocks than they did a year ago or even 5 months ago, depending on what exactly is running on that specific ROM. I could be wrong but it looks to me like your phone is having a pretty rough time sleeping. As I tell everyone I would suggest installing Betterbatterystats to monitor everything occurring "under the hood" of your device, thus better determining the cause to your battery drain issues. I would also recommend matching your favorite kernel build from 11/11 with a ROM from that same point in time simply just for battery testing to see if you get similar results. Now in regards to kernel builds alone, I too have had roughly around the same battery life over the course of these KT747 builds but the same has applied to various kernel builds I've tested across the board.

If you can possibly confirm none of this to be the issue then it must be the battery itself. Purchase a new one and make your own definite comparisons. I wish I had more to tell you but this is all I got to help you unfortunately but test out what's been suggested by us and report back as soon as you can and if you do so wish to..
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Although I may have experienced optimal battery life throughout these builds I do have to agree with you on the simplicity of the earlier builds. You can't deny the fact that with simplicity or "lack of features" on those builds you're bound to gain a significant amount of battery life with those as opposed to the current ones. Regardless, I must only speak on personnel experiences as well as what's been reported by users.
[T-Mobile, Samsung Galaxy SIII] JAG50:
Luigi,

Thanks for your contribution. Again, I'm not trying to say that I have any issues. My S3 is purring like a kitten. I do have cpu spy and my phone goes into deep sleep 90% of the time. So, I'm good.

The reason I wrote my comments was because I've seeing a string of comments complaining about battery life with the latest kernels. That was all. And if you noticed, I posted my comments on this new thread and not on the main forum, mainly because I wanted to keep this conversation low key.

Again, just trying to share insight that might contribute.
[T-Mobile, Samsung Galaxy SIII] mw86:
I see where Jag50 is coming from too so it seems to make semse with added features such as our own manual implementation of thermal throttle which requires monitoring temps and setting max mhz as just one example of a feature very helpful and useful but at a small cost of some added resources.

The less of these features likely less keeping kernel/system active in background. So acknowledging that it seems thats not the issue Jag50 may be facing. Seems just loading kernel straight up something is keeping it awake.

Jag50 your a bright person you likely don't have an obvious thing like swipe to wake enabled right? Basically even if it seems normal drain old kernel and back to crazy drain fresh install of new would say its kernel its just as likely the new stock rom with all new features keeps system awake on new kernel just because something new in rom. So the effect of better battery makes sense on old kernel where less flags and options etc are running as im sure in latest tw builds there has been a ton of code added. I don't think ita battery based on what youve said. Ive abused mine and they dont get max but still right up where they were for me.

Example Ktoonsez had a hair pulling week on his phone which is his buisness work phone too so consider his stress, he had exact drain you do now. It in the end was his wifi router at home. He wasn't using net but left wifi only on at home and it somehow due to faulty hardware caused drain on his phone just being idle and about 20-40% down like you. New router solved it. So Jag50 lets continue to investigate and if i were you try seeing as much as you can on wake locks or diagnosing radio drains etc. If you find for example it never happens on airplane mode you have a start at figuring it radio related. Theres a lot of factors and such a drastic drain seems many kt users would have reported but point being kt had a issues to diagnose and solve similar he even thought was his kernel once... poor guy but no... So goes to show sometimes the last thing we think is the cause. Keep us posted Jag50.
[T-Mobile, Samsung Galaxy SIII] JAG50:
mw86,

Much honored for you taking the time to discuss this issue. I completely agree that there might be other factors at play here.

What I've done is create several nandroid backups and in that manner I can continue testing new kernels and ROMs. I do full wipes before restoring and never have had issues restoring.

This whole conversation will fade away anyways as newer smart phones are released. I'm not upgrading to the S4, but will stay current on that forum.

In any event, thanks for your suggestions and comments. I truly believe our kernelizer forum is the best in xda.

JAG50
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
No arguments there bro.
[T-Mobile, Samsung Galaxy SIII] dablitzkrieg:
Which file for Verizon is the most recent?? I'm not seeing any labels on your drop box

Sent from my SCH-I535 using Xparent Purple Tapatalk 2
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Well it really depends on which group of builds you're referring to but you can check the most recent build for each group by the dates included in the file names. For example, 5/17 is the most recent 3.4 build released by Ktoonsez.
[T-Mobile, Samsung Galaxy SIII] bouzouki:
I tried this kernel yesterday and I have hide drain by the os. I have used this kernel in the past and I always have the same issue.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Android OS is taking up over 50% of your battery. Any idea what may be consuming that? Do you have many apps running? Is your phone sleeping? Have you tried using apps such as Betterbatterystats to better monitor and determine what's running "under the hood" of your phone? If not, I would suggest doing so and posting some shots of "Other", "Kernel Wakelocks", and "Partial Wakelocks". Hopefully I or someone else can better assist you then.
[T-Mobile, Samsung Galaxy SIII] bouzouki:
all i did was switch kernels. i was running leankernel and it was great. i switched to kt to try it out and i always get this. no matter what. thats why i have stayed away from kt. the phone doesnt go into deep sleep either. i had swipe to wake enabled and i read somewhere that that causes drain. i disabled it this morning and now it seems to be going into deep sleep. so i will monitor the battery for a couple of hours and see what happens.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Different kernels will run some different aspects of your entire phone, especially depending on the ROM your running the kernel on. . Unfortunately, it seems though as if something about this kernel is constantly causing your phone to stay awake. I don't want you to miss out on this beast of a kernel so If you do have any hope left in this kernel then please do install that app, post those screenshots I mentioned, and I'll personally help you in identifying the cause if you can't do so yourself.

Hopefully that swipe to wake is the main culprit.
[T-Mobile, Samsung Galaxy SIII] merwin:
I agree. Kernel devs need help from people with problems in order to make their product better. Please don't drop it right away. While KT may not be the kernel for everyone, maybe not even you, if you have problems it is your responsibility as a guinea pig... err... user... to help report and test issues :)
[T-Mobile, Samsung Galaxy SIII] bouzouki:
Turned off swipe to wake and battery life seems much better but still not great.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Considering you've got wifi on the entire time this really isn't bad at all. If you wanna improve it even further then take care of your wifi. Try turning it off when not in use.

Also view your partial wakelocks to identify exactly what apps or widgets are running and, if possible, Greenify most of your apps
[T-Mobile, Samsung Galaxy SIII] bouzouki:
But why is android system and operating system taking so much? Is that normal?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
It looks relatively normal but your screen is nearly 50%. Try dimming down the brightness to about half or at least reduce the times it increases towards it's max when using it. As far as android system and OS goes, it's not taking much off your battery and as you can see the phone is sleeping for the most part. It just looks as if you got small background processes going on that has kept the phone awake for 45 minutes out of those 3 hours. You can post a screenshot of your partial wakelocks if you like. it may also have something to do with your screen off states. What are your Ktweaker settings if I may ask?
[T-Mobile, Samsung Galaxy SIII] prboy1969:
S2W is a big drain to the battery if left on all the time. Glad you figured that out. I only have it enabled when plugged in. Still really like the feature.

One question I have, did you rename the files? As is suggested in the KT thread.

TEAM MiK

MikROMs Since 3/13/11
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
OP has been updated to latest builds peeps!! As always go thank the main man responsible!
[T-Mobile, Samsung Galaxy SIII] merwin:
Oh yeah! What's the GPU governor control?

And could you guys add the Zen I/O Scheduler and possibly GPU speed selection for Android Tuner support?

I'm working on the second part myself but don't think I'm as quick as this team at it. And the Zen scheduler is quick and easy... Possibly the best scheduler out there... at least it's the best one I've found.
[T-Mobile, Samsung Galaxy SIII] Romcrazguy:
The new update feel much smoother however my voltage table wont stick anyone notice
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
GPU Governor Control? pretty self explanatory lol. It comes with GPU clocking as well. However, according to Ktoonsez those were accidentally merged into Ktweaker to our device somehow and must not be played with. Stick with the new things listed in the change log.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
works fine for me bro. How did you update?
[T-Mobile, Samsung Galaxy SIII] Romcrazguy:
Via the phone
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Lol like your sense of humor.

What was your install procedure on updating the kernel?
[T-Mobile, Samsung Galaxy SIII] Romcrazguy:
Wiped then dalvik flashed rom the fix permission
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
To update your kernel this is the recommended procedure:

1) Backup current Ktweaker settings

2) Go into Settengs > Apps > Ktweaker

3) Clear cache and data then force stop

4) {Optional} Open any root browser, navigate to /system/app/ and delete Ktweaker apk

5) Reboot Recovery

6) Flash kernel

7) Wipe cache/dalvik

8) Fix permissions

If need be also clear your superuser logs. Clean ROM installs only require steps 5-8 but I'm sure you already know this.
[T-Mobile, Samsung Galaxy SIII] BTT8:
I personally have never done steps 2-4 before and I have never had any problems and I've been flashing KT since the beginning of time.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
That's fine! You're a lucky camper then lol It's the recommended procedure in updating to minimize one's chances of facing any issues.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
What if one doesn't use KTweaker? Does the ROM use it nevertheless?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
It will come with the kernel regardless but you can always disable the app and use one of your preference. However, you will no longer be able to OC, unless you run the script to enable OC steps and set it to automatically run at each boot.

It's located in the /etc/init.d/ directory.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
I'm using SetCPU (paid for it... Might as well... lol) I'm running KT747, OC'd at 485/1512, ktoonservative/row... Pretty smooth.

Thanks for the advice. :good:
[T-Mobile, Samsung Galaxy SIII] seko666:
What would be the best set up(governors, voltage, OC) for general use? Twitter, games?

LiquidSmooth v2.5
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
My personal settings:

Locked Frequencies

CPU (MIN): 189mhz

CPU (MAX): 1458mhz

Scheduler: ROW

Governor: Ktoonservative

Governor Adjustments > boost_cpu: 1080

Auto Hotplug: Checked

Voltage Table: -50mV across the board

Screen Off Mhz: 189

Screen Off Gov: Same governor

Screen Off Sched: Same scheduler

Battery Level Low: 10

CPU Mhz for low level battery: 1080 mhz
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I was using -25mV. I was seeing some unexplainable battery fluctuations overnight. Going to disable undervolt for now to see if it goes away.

One night, 0.9% an hour. Next night, 3.0% an hour. No changes were made to anything. Wakelock info looks the same as it did the previous day. As in, nothing stood out to me.
[T-Mobile, Samsung Galaxy SIII] seko666:
Sorry n00b? What is wakelock?

LiquidSmooth v2.5

---------- Post added at 08:12 PM ---------- Previous post was at 08:08 PM ----------

What about set options on boot? And OC is that checked. Not sure what OC does.

Thanks

LiquidSmooth v2.5 & KT747
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yes, applying at boot will ensure your settings stick by applying them upon each boot up.

In general terms, overclocking is basically the process of allowing your device to operate faster than the actual stock clock frequency applied by the manufacturer. By doing this you can experience anything from increased performance to less game lag but at the expense of battery life. You should read up more on it if your're still unsure of it's functions/operations..
[T-Mobile, Samsung Galaxy SIII] astrosplatt:
Not sure if this is something else that's happened before, but i switched to the latest KT kernel and after the Samsung Galaxy SIII boot screen i get nothing. Yet when i press my home button and swipe like I'm unlocking i can hear everything working, yet the screen stays black. Thoughts? Thanks for the help in advance guys. Sorry for the noob question. Running latest LiquidSmooth on tmobile.
[T-Mobile, Samsung Galaxy SIII] prboy1969:
Boot back into Recovery. Wipe Cache, Wipe Dalvik, Fix Permissions, and Reboot.

TEAM MiK

MikROMs Since 3/13/11
[T-Mobile, Samsung Galaxy SIII] astrosplatt:
Yes sir. Did that twice.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
I suggest redownloading and flashing again. If that doesn't do it for you then please provide your entire install procedure of the ROM and kernel, including the respective filenames for which your flashing.
[T-Mobile, Samsung Galaxy SIII] astrosplatt:
Will do. Probably later today.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
OP updated to latest Touchwiz builds!! Please go give the dev a huge thanks as he was up all night resolving the issues encountered on the 5/29 build!
[T-Mobile, Samsung Galaxy SIII] seko666:
I been using the AOSP JB 4.2.2 linux 3.4 version of this kernel. but had to many problems with it. Could I use the touchwiz version instead?

LiquidSmooth v2.5 & BMS 3.4y
[T-Mobile, Samsung Galaxy SIII] mt3g:
Touchwiz is for Touchwiz and AOSP is for AOSP 3.0 is for 3.0 and 3.4 is for 3.4
[T-Mobile, Samsung Galaxy SIII] kingston73:
This might be a stupid question but can I use a 4.1.2 TW kernel on a 4.1.1 rom? I just want to use whatever the best 4.1.1 kernel currently is, thank you ahead of time.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Same answer I gave you in the TMO kernel thread. Yes, they are compatible.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
OP updated to latest 3.4 builds peeps!! Go grab your copy, show the dev some love, and ENJOY!!!
[T-Mobile, Samsung Galaxy SIII] mw86:
Excellent work Luigi your doing a great job sir.
[T-Mobile, Samsung Galaxy SIII] ace2153:
Don't this kernel support fast charge when I turn on fast charge then plug my charger in its saying I'm not rooted? Also i'm using trickster mods/kernel tweaker is that okay?
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Have you actually granted it superuser permissions? Whatever the case may be I wouldn't even recommend using an alternate tuner app when there's already an app specifically for this kernel. It may conflict with the Ktweaker app, which can cause various issues such as this. What I'd recommend doing is to first confirm that you are indeed still rooted and that superuser binaries are up to date then uninstall Trickster and see what happens after that. If still a no go then clear Superuser logs, run the kernel cleaner in recovery and proceed to reflashing the kernel, clear cache/dalvik, and fix permissions. After rebooting grant ktweaker superuser permissions and see if you can turn fast charge on before actually reinstalling Trickster Mod if you do so choose to reinstall it, which again I don't recommend.
[T-Mobile, Samsung Galaxy SIII] ace2153:
Okay I have root access what app should i be using kernel tweaking. Okay I uninstalled trickster app fast charge is working now. Still a noob to this device
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Ktweaker, the app the kernel comes with... You should already know this.. Besides, I've shared my installation procedure numerous times across many threads. If you're at a loss you should really get some more reading done bud. No one is here to hold yours or anyone's hands. Until then just follow these steps to reinstall/update the kernel. Once complete, try enabling Fast Charge in Ktweaker before plugging in the cable and grant it permissions.

1) Backup current Ktweaker settings

2) Go into Settengs > Apps > Ktweaker

3) Clear cache and data then force stop

4) {Optional} Open any root browser, navigate to /system/app/ and delete Ktweaker apk

5) Clear Superuser logs

5) Reboot Recovery

6) Flash kernel

7) Wipe cache/dalvik

8) Fix permissions

9) First test out the kernel before actually restoring your settings or any kernel tweaking apps

Keep in mind, clean ROM installs only require steps 5-8.
[T-Mobile, Samsung Galaxy SIII] ace2153:
Got it working thanks
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
You're welcome bro. Please do hit that thanks button as it really does help my status on XDA
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
I went back through two pages before I got bored. Welcome.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
lol this just made my day.
[T-Mobile, Samsung Galaxy SIII] mikoal:
for touchwiz jb 4.1.1, which kernels would work?

Looking at the ATT files

The older type are titled as

KT747-Kernel-TW-JB-ATT-12-11-2012.zip

The newer ones as

KT747-TW-JB-4.1.2-ATT-05-31-2013.zip

Is the ones with 4.1.2 compatible with 4.1.1 or did 4.1.1 end when the 4.1.2 came out?

thanks,

EDIT: NM i think i found the answer http://xdaforums.com/showpost.php?p=42160478&postcount=67

they(the new kernels) are compatible with 4.1.1.

Just reading through these 8 pages. I must say this is probably the friendliest thread I've been to. Now I'm going to go through the last 100 pages of this kernel before trying it out to see what bugs and what i need to do.
[T-Mobile, Samsung Galaxy SIII] krntehknik303:
Just wanted to comment.. I have come to the conclusion my phone does not like undervolting. Even if its -25mv across the board. My phone freezes and ends up rebooting on its own.

This time I have left my voltage setting stock. Under clocked down to 1134mhz. And some extra stuff. So far, so good. No random freezes or reboots just yet.

I'm assuming my phone didn't like the under volt. Anyways, learned a lot and still learning a lot. Just wanted to thank those that helped the community out with this dope kernel and teaching us how to tweak it.

Thanks!
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Thank you for the kind words my friend.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Ya. Undervolting can be a tad bit overrated in my honest opinion. It doesn't necessarily provide nearly as much battery life as many may think. I'm glad you found a solution for yourself though. Check out this post by [MENTION=4983878]castle_bravo[/MENTION]. He made an outstanding clarification/explanation towards undervolting and this theory of, "If you undervolt you'll get much better battery life". Be sure to thank him as well as the rest of the TK team for their amazing work and contributions.

http://xdaforums.com/showthread.php?p=42258652
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It's very overrated. I don't bother anymore. Well, pretty sure the kernel is underclocked by default, but I no longer underclock it further.
[T-Mobile, Samsung Galaxy SIII] mikoal:
I asked this question in the main thread and didn't seem to get a reply yet.

I was wondering about the process it takes to change from one kernel to the next, back to stock etc.

I was reading about it a few months ago and I swear I read something related to drivers that needs to be changed, and if i wanted to go back to stock i would have to downgrade the drivers.

It was something along the lines that simply flashing another kernel wouldnt work and you need to install the driver as well. Even going back to a nandroid wouldn't work.........correct me if im wrong, im not sure where i read this....

I have the following kernel for stock TW JB 4.1.1

3.0.31-538866

se.infra@SEP-106#1

What driver would I need to download (and where would I find it) incase I want to revert back to this kernel, or try other kernels?

I want to do my research before flashing this kernel so I can jump around to other kernels without an issue.

Also....i can't quite recall, why was the driver updated? Using my stock kernel, im assuming the driver is an older version. I dont think i've experienced any issues with it yet....

Thanks!
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
Yes. It was stated not too long ago that if one flashed a kernel build that included updated wifi or bluetooth drivers and went back to stock you would've needed to get those drivers back cuz simply flashing the kernel wouldn't cut it but to my knowledge you don't have to worry about that anymore, unless you're on an extremely outdated build between the kernel and ROM. All you'd need to do is reflash the ROM with the correct modules in it if need be. You can compare the /system/lib/modules/ directories within the kernel and ROM zip and if all is well then you should be good to go. As long as both are current then you don't have to worry..