yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Check the Superuser app to make sure it isn't set to always deny superuser permissions to KTweaker. Is clearing data on Superuser a bad idea? If you are running CM (or any other ROM that has this setting), check under Settings -> Developer Options to see if Root is even allowed for Apps (and ADB).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Yes i would clear the entry for ktweaker in super user and regrant super user permission. If that doesn't solve additionally force stop ktweaker in settings/application/move over two tabs to the right and go to ktweaker. As mentioned force stop the hit clear data and just reboot after leaving the menu without entering ktweaker before reboot.

All should be good then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slimshotty:
Am I missing something or is the download link for the TW JB 4.1.2 pointing to version 5/3 instead of 5/9?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
The 5/9 was AOSP only. TW latest is 5/3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
That's the list update on the tw kernel. It's not updated as often as aosp since tw isn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Works now :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Ktoonsez's settings, but for my phone, cfq seems to work better. I've used rom toolbox autostart to freeze a slew of unnecessary receivers. Apologies for the OT post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you share those settings please. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
KT

Weirdest thing... On today's 5/10 CM nighyly , with KT 5/9 kernel...

My CPU is going nuts. Its jumping all over the place without idling down. Never had this problem before.

Here us my settings file as well as catlog. Nothing is running in background.

Catlog shows a bunch of alsa stuff (sound?)...

Any suggestions by chance to get this puppy tamed?

Catlog:

http://db.tt/JkzkLKnf

Settings:

http://db.tt/R1Nkuxft

Because its bouncing like its in speed this thing is starting to cook in the back.

Thanks dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
They're in the third post in the thread.

On an unrelated note, can you disable the KT747 boot splash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Reboot a few times and let the kernel settle down. It will stop. Like mine did after a clean flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I rebooted a number of times. This is also a very clean install with today's nightly. Full wipe. Thought I let it settle as bit...its been about 3 hours and its still having fun bouncing all over v

---------- Post added at 10:21 PM ---------- Previous post was at 10:08 PM ----------

I think I figured it out..

Cleared ktweaker data. Reflashed kernel. Re cleared cache and davlik. Re ran fix permissions. Then re setup ktweaker again... It be calm now.

Weird what may have caused it in first place.

On a really really clean install...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
No you can't. You can flash another one. And I design them ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
I'm going to design my own boot animation, but I don't want that splash screen at the beginning :P

EDIT: What would I need to flash a new one of?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
:highfive:

If you want to change the splash screen you will need to compile the kernel yourself and add the new .rle file that you want as the splash screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Oh well... That is way over my head :/ I just don't want any splash at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
Quick question guys telus still has their phones running 4.1.1 but the download link is for 4.1.2 and I can't find the latest specific 4.1.1 updated kernel. Could I use the given link 4.1.2 in OP for the 4.1.1 version in TW. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
I'm running 4.1.1 right now on Att and I'm using the 4.1.2 kernel its working great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Mine also did that 2 days ago, went to recovery and wiped cache and dalvik and it went away :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The 4.1.2 kernel will run perfectly on 4.1.1 also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KiiKeEp:
I like this kernel.. but the splash screen makes me want to use another kernel..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geomax45:
Life must be tough, being so sensitive..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Gtfoh compile your own then
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
FLOAM!!!!!!!!! That made my morning.

WOOOHOOO, just hit 19k thanks. You guys are awesome, except for sensitive boy back there, lol. :highfive: :good: :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
The z at the end of your user name is too ghetto for me. It makes me not want to use your kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I know, I have been thinking of changing it, lol :D. Oh and the 860 on yours is just to large and offends me very deeply!!!!!!! :laugh: :silly: :crying:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
So now your battery being much better, is the 3.4 behaving for you or still rebooting randomly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Dats my area code homie

No issues so far. Haven't had a full day of heavy use though. I used the GPS to get to the dentist just now and it got lagged I have to double check KT app tough no static screen so far either
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Is it okay if I flash the latest version of this kernel with 26.04.2013 build of tasks AOKP? Like is it OK to flash since this is a recent kernel and that's an older build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
Hey ktoonz. I had a lot of random reboots on my phone, but I found that using the BMS voltage settings have stabilized my phone significantly. Maybe this might help some others who are getting reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
All you can do is try, I would suggest updating to latest AOKP though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x10user2011:
Thank you for the quick reply. Ya I would update but for my phone I always have to format internal when clean flashing which is just weird or else my phone doesnt boot up. That's why it takes me longer to get things done so I just want to have the latest version of this kernel :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BIGDADDYXXL:
Now its 19k and 1 lol. Awsome work man keep it up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Just wanted to say awsome work on the kernel I've been using for awhile. Actually went back to tw and im still getting amazing life. Oh I should say a huge thanks to team kernelizers as well its luis's settings that im running and now that the phone has settled and gone through a couple cycles its just amazing, kudos again and GREAT WORK

Sent from my SGH-I747 using Xparent BlueTapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I love your kernel. The tweaker app is superb. If it's possible to request in the extras setting, governor & frequency when changing is on. Thanks. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Woah hey you live right near me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Updated to CM10.1 RC2 and the latest nightly for the KT747 kernel, and I haven't had any reboots or screen flashing like I did with RC1 and an earlier build of this kernel. Not sure which is responsible for the fix, but I'm happy either way. :good:

This is the best kernel I've used for the S3, bar none. The ktoonservative governor is godlike in terms of battery and performance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I live in burrville
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Latest update is running great. No flickers. Also just got the s4 today. Really. Hope you get the phone ktoonsez. I can definitely see a huge improvement in performance if you take over :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Knivez:
Hey, If possible could I get a download link for the older (Change Log 4.11.2013) from anyone? Im trying to find a good kernel that works with the AOKP Milestone 1. thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Here is my Dropbox folder for KT747. I've got everything since the 3-20 build. Have fun.

https://www.dropbox.com/sh/5cipia9hxdkqtji/ueQJx7n07O
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
KT747-AOSP-JB-MR1-3.4-ATT-04-11-2013.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Much appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Noticing that AssWax is sticking at some frequencies around 1188 up to 1512 and will just sit there for a while. No idea what causes it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Ok went a full day heavy use no static screen issues! Thanx Mr toons*
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeeVine:
No more love for the 4.1.2 ? Still your kernel is the bomb .......love u ktoonez..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That is GREAT news!!!!!!!!!!!!!!!!!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
With regard to random reboots, are they something that started with 3.4 kernels or post-M2 versions of CM10.1?

I'm just curious because my jump from M2 to the most recent builds has resulted in random reboots no matter which 3.4 kernel I use. Since they happen on both the stock CM kernel and this one, I am tempted to say that they are a ROM-specific issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes it is pretty much the move to 3.4. Your best bet is to stay on the same day releases. What I mean is if u r running the kernel from 5/9 use CM or AOKP built on 5/9 and u should have better luck
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Okay, thanks for the info. I'm on RC2 at the moment with the 05/09 build of this kernel. So I think that is pretty much the same day release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Yo toonz had my first reboot since flashing on Friday. I'm running your settings OCd to 1674 and stock voltages. Would you recommend stepping up another 25mv across the board?

Last kmsg:

http://db.tt/ABc5XsOr

Edit: This was after turning the screen on and trying to unlock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ilanderek:
Im new to all kernel stuff, whats the best settings I could use to get good battery and good performance?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
KT's settings. Check the third post of this entire thread. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ilanderek:
in ktweeker app there´s an option, swipe to wake and another, trinity colors what are they for and how do we use them?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Trinity colors is a modification that changes the way your screen displays colors. It should be a cooler look with stronger blues. Some say it helps with the dim nature of the S3 screen. I would tend to agree.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ilanderek:
sweet!!!, and the swipe thing???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Wake up your phone by swiping the black screen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
Installed the 5/9 build of the aosp 3.4 kernel over Carbon 1.7 and now my SD card random unmounts. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
Update to a newer nightly. Doesn't happen on mine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I used to have this issue all the time. Turns out the 32 GB Sandisk card I was using was defective. I got a replacement and haven't had an issue since.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I'm partial to using the ktoonservative governor with the ROW scheduler. Great battery and performance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Hmm this doesn't seem to work for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
From left to right across the screen?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
What ROM, and yes you should always start with removing UV/UC/OC?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
Hmmmm I have a 32GB SanDisk too. It just started happening but it could be the SD reader in the phone. I dropped it pretty hard earlier. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Latest Task and I was at 1512 max freq and stock voltages. Overvolt 25mv?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
You can try +25mV. I had same problem with the combo of 5/9 kernel and task 5/7 but went away completely with 5/9 kernel and 5/9 ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Cool ill give it a shot. Also lowered my boost_cpu from 1296 to 1134.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Try getting rid of the OC first.

EDIT: ninja'd by KT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Never worked for me either. Maybe its ROM specific
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Not sure if it is just slide from left to rite and it should wake up maybe try enabling it And rebooting first ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Left to right at the bottom. You can't move too fast or it won't read. It didn't require a reboot for me. Turned off and on, tried several times to try and trip it. TASK's and this kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rwbarnes67:
I just found that funny!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
KT

Had a reboot while using GPS with GPS settings again. Last reboot was also using gps. Doe not happen instantly or anything. Was on gps for like 30min and then bam.... Anything good in the log?

I'm on CM 5/11

http://db.tt/LcAAS6vu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nothing to do with GPS, it was modem crash:

"Kernel panic - not syncing: subsys-restart: Resetting the SoC - modem crashed."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Again grrr that is now 3rd or 4th due to modem. I reflashed modem not too long ago as well. Hmm I'll do it again since then I swapped over to cm from tasks.

Thanks for taking a look dude!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] golastic:
Nice build man..... Hoping to see more updates for our perfect phone :thumbup::thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Setting the mhz screen off profile to 486 while using an app like this https://play.google.com/store/apps/details?id=com.runtastic.android.mountainbike.pro is a bad idea right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
Most apps can run in the background at a very low Mhz, don't expect multi-tasking though ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
I set mine to 540 and min of 486 to run Bluetooth. Still trying to verify this will stop random reboots while streaming to the car or headphones on the current kernel. 386 this morning was not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Lowering the off-screen max to 486 can result in random reboots while playing music in the car or wherever? I'll have to test this today, as I only recently started modifying the screen-off settings with this kernel.

I'll probably test Navigation too, since I usually use that with the screen off. Is that too low of a value, given the intensive nature of the Navigation app?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
I stream music and use navigation with screen off at 486Mhz and noop scheduler without any problem. That being said, it's device specific. Some phones won't handle it as well as others.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
KT,

Looks like all the modem related crashes i've had, could all be related to this: https://plus.google.com/104277415207525128383/posts/iAVpVPYqMtM

Someone posted it in CM10 thread as well, but it fits my symptoms....

Above post is specific to d2vzw, but comments seem to mention that d2att is impacted as well...

i'm on the latest firmware as far as i know - UDLK3

Do you , or anyone know how to go about finding what can be updated as far as old tz (trustzone) for our phones?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Never heard of the TrustZone thing, might just be a Verizon thing. But looks like a promising fix and is exactly what a few of you guys are getting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Random reboot with screen off
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Looks like the same thing we have seen before ("SysRq : Emergency Remount R/O"), something to do with SDcard driver getting pissed about something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Had my first reboot in a while. I don't think it's modem or sdcard related, but I can't tell for sure. Can anyone else see what might have caused it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
That one is the 3rd FAN favorite, the wifi (dhd) device interfered with sleep mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I was afraid of that. My last few reboots have been the same issue. Is this something that may be fixed by future CM updates?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
External or internal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
First random reboot i get. Not so sure why though. Was listening to music and on palringo.

http://db.tt/qrqxcmcz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjranucci:
I have had a ton less reboots since I switched from ROW to ZEN scheduler. I hate the battery life compromise, but it is better than reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Change Log 5.14.2013

1. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.296 from codeaurora.org

2. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.298 from codeaurora.org

3. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.301 from codeaurora.org

4. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.306 from codeaurora.org

5. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.308 from codeaurora.org

6. Merged in AU_LINUX_ANDROID_JB_2.5.04.02.02.040.309 from codeaurora.org

7. Linux 3.4.45

8. A few patches to get completely sync'd with CM

ENJOY
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Must remember to clear app data when updating kernels. Thanks for the update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] YoHoJo:
Any way to find out what exactly these updates changed?

I assume it's mostly minor under the hood stuff/optimizations that non-coders wouldn't really understand or care for or notice that much?

Why do you say this? I know it's a common practice/thing to do, but what's making you say it now?

Also what happens if you don't?!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
He gave you the site and the names - you can go see if you're that interested. Mostly I just accept the magic ;)

I think he was probably reminding us about clearing data while he's reminding himself :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
In the recovery, just clear cache and dalvik. You might also fix permissions.. You don't really have to do anything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
Ktweaker may crash if you don't clear the app data. Forgot when I updated and was confused for a moment when it did.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Update the ROM and you won't have to worry about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
Keep it simple...

Just my 2 cents, I am fairly new to this device. I run AOKP and this kernel and have found that if you want everything to behave nicely after a dirty flash....Do a NANDROIOD...and then flash in this order: ROM then Kernel( immediately wipe dalvik/cache, and fix permissions) THEN flash GAPPS. If you do it out of that order you get UI FC and keyboard FC. Confirmed this last night when I flashed the newest kernel and then flashed the lastest ROM. Hope this helps someone, I don't want to do a full wipe every time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
That's never happened to me, and I've always, for clean flash, flashed ROM, then gapps, boot up to make sure everything is working and set up, then reboot back into recovery and flash kernel. I've never had an issue dirty flashing a newer release for the kernel either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
If you're running Task's AOKP and you're getting UI fcs then you flashed the wrong GApps. Nothing to do with the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickscap:
Question has anyone had any luck getting the zedomax int.d script to work on recent jelly bean release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geomax45:
Zedomax and luck truly belong in the same sentence.. Good luck with anything Zedomax..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Zedomax = voldemort for xda

He who name must not be spoken round these parts

Also anytime I hear zedomax all I think is here comes someone gunnna hard brick their device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nickscap:
Thanks for the laugh well at least I know now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
I believe there is a May 7 version of gapps you must use if you are running Tasks latest. He links to it in his OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gunz.jones:
5-8. 5-7 had a broken keyboard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
Worked great for me. Every phone can be a bit different!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mikehud1984:
I must be doing something wrong.

I really want to use this kernel. Except whenever I install it its super buggy and never works right. I follow the install intructions but no luck. The problems I am having are that while this kernel is installed if my phone isn't plugged in overnight it will be dead in the morning even if it was full. Also I can't get ktweaker to work properly. If I tick enable OC steps the slider changez to allow to slide all the way to 2106 but if you try to slide past 1512 it freezes and reboots. Now I'm running stock ATT jellybean latest build rooted and CWM Recovery. I've tried reflashing and fixing permissions and even different roms but its always the same result. Sorry if this is already mentioned. I appreciate any help with this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Some devices just can't handle it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] galaxys3man30:
Whats ur flashing process?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Most likely the ROM is what is screwing you. Especially if it is TJ.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Recently cyanogen himself made a post claiming the latest cm rc and nightlies require the latest 4.1 jellybean bootloader to be able to work those that came from stock ice cream sandwich need to flash stock jellybean and nandroid restore back to custom rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Deleted.. Took it to PM so it won't clutter thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mikehud1984:
I typivcally do this.

1. Wipe data

2. Wipe cache

3. Wipe Dalv

4,, 'advanced' format system

5. Flash rom /gapps if needed

6.Flash Kernel

And sometimes I try fixing permissions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jacqstrap:
What are good settings for Ktweaker to get very good battery life? I do not see any improvement with the ones Ktoonsez has