yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
My first clue was that Antutu couldnt even get the phones info, says something like, call an 866 number for help and that it couldnt collect the data.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Just curious, but what app do people use to under volt? I tried voltage control and system tuner when I was on stock Sammy kernel and no UV option showed up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
Undervolting is in this kernel, not in stock kernel. It shows up in voltage control of the kernel supports under volting.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fmllc:
FURTHER UPDATE:

All was well after raising all the voltages by 50 so...bored...I narrowed it down to just 1. Well maybe 2...but I don't use the 192mhz setting so I wouldn't be able to tell you!

CONCLUSION:

If your notifications icons are acting all crazy when pulling down and rolling up the window and UI objects are present but aren't drawn onto your screen, Widgets too....THEN....raise the 384mhz voltage by 25 to 850mV using voltage control and all should be well! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
Just thought id at least mention this here, because your instructions are how i found this problem. In your instructions you say to fix permissions everytime. In all my droid experience ive never used that before and have never had issues. I started using it as instructed and at first everything was gravy. But after that i lose connectivity to google. I cannot connect to play store, gmail, etc and i dont have the "blue" signal bars on wifi or mobile data and my clock doesnt sync. This didnt happen until i started using fix permissions. I just thought id post this in case anyone else had weird issues after using fix permissions.

Theres no reliable way to undo the problem except for restoring a backup, but ive only done that a couple times

Yes i understand this Might be unique.and no i dont expect ktoonz to do anything about it because its not his error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
I know I was using the kt747 uv/oc/uc sammy kernel on tuchmi s3x and no voltage control tab
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Probably your CWM version, you using touch version? If not what version and if it is touch version or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
It's not touch

Also, anytime I flash something, such as a simple MMS, it does it too. It's rly weird
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
I've also noticed a lack of external sd capabilities with this version. There's not even an option for it. Do you think I should try an older version of cwm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
RUSS​
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] woodydog:
8P530607BK628525M. Thanks for your awesome dev skills
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beast3300:
Oh then i misunderstood the question.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its worth a shot, I was on 5.8.4.5 until today when I noticed that there was a 5.8.4.7. Maybe it s a new bug in there recovery, cant way for sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
I flashed one version back to 5.8.4.6, rebooted. Then I rebooted into recovery, wiped cache and dalvik, and installed your 7/19c aosp kernel. Rebooted and had the same issue with not connecting to any gapp. Then i fixed permissions in ROM MANAGER, NOT CWM, and rebooted. Now I'm back to normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ewingr:
UV by default in new kernel?

Maybe I missed something in the tread (I have been following all of it).

But I notice a few needing to raise voltages. Are the voltages lowered by default in the kernel, which then necessitates raising it, depending on your individual phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes that is correct, I have been meaning to post a table of KT747 and stock, but I can tell you that a bunch of levels have up to 100 less mv than stock to give us that great battery life :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Franky_V:
So, immediately following those actions, I decided to install a new MMS thru cwm. I rebooted into recovery, installed the MMS. When I rebooted I couldn't connect to gapps again. So I did a basic restart and now it's working.

Sigh, if a simple reboot will fix it I won't worry about it anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigblue95z:
Yes, this is a known issue for .7 CWM official. The only one with ext support is .5 CWM official.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
My apologies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Its all good man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
I scrolled back till 10/22 and didn't see anyone confirm KTz kernel works with Task's AOKP 10/23. Consider it working perfectly using 'nightmare to remember' with freq adjusted to 81-1674mhz.

Sent from Task's AOKP on a Bell SGSIII using Tapatalk 4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I believe you are the first person since the new kernel was posted, to ask about this rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
I re-read my post and maybe it isn't clear... This kernel and tasks aokp 10/23 rom seem to work perfectly together.

Sent from Task's AOKP on a Bell SGSIII using Tapatalk 4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Yes I did get that part. I meant to say mention but said asked instead. :p My bad.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I've been having lots of crashes reboots lag and glitches like divinex on pac and kt. Sounds like it may be a Rom issue but I can't be sure. Until kt or pac release something that fixes it I'm gonna switch back to quantum + kt or quantum +quantum (can't decide, leaning towards kt because it worked well in the past with the 10/16 build and I love ktweaker) so yeah until pac gets their stuff straight I won't be using it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Euphoria64:
Tasks newest and KT's kernel are a match made in heaven....just like they are!

MOLAF!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrFhenix:
ktoozen will this help update the TW kernel??

http://xdaforums.com/showthread.php?p=46804949&posted=1#post46804949
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Not sure I got your question. The post you linked seems to talk about Modem backup
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Disregard
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Looks like we're getting an official 4.3 rom from AT&T, not sure if it can improve this kernel but I know the new modem and such will be nice for us users, and maybe it'll improve the current 4.3 roms and (fingers crossed) be the answer to our bluetooth issues!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Had a reboot using AOKP 10/23 and kt747 10/20....I was playing colony attack when it happened.

Logs right after reboot

Dmesg

https://db.tt/VtRWoxqH

Kmsg

https://db.tt/RYS12eai

I don't understand AOKP runs perfect, smooth smooth and then all of a sudden reboot....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Vibration

Is there any way to turn the vibrations off completely? I was able to eliminate them with the CM kernel, but now after flashing KT it seems like it's always there. All I could find was vibration settings in the KTweaker app which lets you lower the strength, but not turn it off. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Unable to boot using newest version of 3.4 kernel on newest nightly of Revolt JB ROM. Tried clearing cache, dalvik and fixing permissions but no dice. Goes past kernel boot animation but hangs on ROM boot animation. Was able to use 3.4 version of BMS kernel no problem on same ROM. Thanks for any help that you can give me. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Kernel correctly allows you to control the intensity of the vibration.

Go one Version back to 10-16
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
You could disable vibrations under settings->sound for phone calls, notifications and touch pad. Pretty sure that'll disable it completely.

Some ROMs have specific settings for it but mine (Quantum) does not besides those few sound settings... But I can't think of anything off the top of my head that also uses vibration.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Thanks! I got it worked out

I'm having another problem with the music occasionally lagging after flashing this kernel with the conservative battery profile found here:

http://xdaforums.com/showthread.php?t=2367975&page=2

The battery life seems great but my music keeps skipping or lagging from time to time, especially when the screen is off and I turn it on to switch tracks... what are the best options to tweak to fix this?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Try my updated version buddy and see if it helps.

ROW Balanced Bull v4

https://copy.com/9HYr9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Awesome! Thanks for that, I'll test it out and let you know how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Luigi, since I focus exclusively on Battery, what'd you choose between Bless the child or this one ? TIA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Bless The Child favors more battery over performance as opposed to Balanced Bull, which favors both. Results will obviously still vary depending on user activity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Thanks Luigi. As always. So far I am favoring Bless the child. Only thing I see is Waking to lock screen. But I blame it on Locket.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Luigi,

It looks like your updated version has eliminated the lagging when waking the screen, but there is still a bit of a lag when skipping tracks. If it matters, I'm using Poweramp, and the songs are on my microSD. While skipping through a few tracks eventually one will hang for a second before playing.. I'm wondering if it has anything to do with the SD options in KTweaker extras.

Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Definitely not the settings then.

Go into Poweramp and navigate to Settings > Audio > Advanced Tweaks and raise your "Audio Buffer Size" and/or "Audio Thread Priority". See if that makes a difference.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 10.27

1. CM Sync

2. apexq: move if to support logo on certain panel revs

3. Prima 3.2.6.121

4. msm: pil-riva: allow forcing of insecure mode"

5. KTweaker update for GPU voltage steps limited to 25mV instead of 5 which caused issues for some people
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Rad! Flashing this sucker right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
I just had a random reboot just swiping between screens. On Task's latest (I know he's about to release a new one) and yours latest from a few hours ago.

DMESG - https://db.tt/goZPPyJF

KMSG - https://db.tt/goZPPyJF

Sent from another Galaxy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nothing good in there :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] err0r76:
Thanks for looking man

Sent from another Galaxy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
I'm doubtful there is anything to be seen from this as i don't have log files or kmsg but while on the 10/20 4.3 kernel with the newest paranoid android i tried importing the "Bless the Child" settings to ktweaker and immediately after the app crashed and hasn't functioned since. Also i tried updating the kernel to 10/27 after this happened clearing caches and fixing permissions but the problem persists. I am going to try a clean install tomorrow and see if the issue persists.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You did not extract the profile and name it correctly before importing. The app expects text files only. I think this was explained earlier on as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Steuartl:
Thank you! glad to hear its something i did and not my phones issue. Thanks, i will make sure to do that before i try again after a clean install of everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
Just clear the app data for ktweaker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Still no luck booting with RevoltRom 10/20 nightly even with new kernel release. Must be some incompatibility I guess. I know someone suggested RevoltRom 10/16 nightly but as much as I would love to try KT, I don't want to have to do a clean install again just to see if it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Don't use latest KT version. Use the KT 10-16 version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Will we see a TW 4.3 kernel anytime soon?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Running nicely on PAC 10/27 :thumbup:

Had a reboot but only when undervolting the GPU. Otherwise this kernel is perfect now with pac. Thanks man. Much appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I wouldn't touch the GPU. Its not built like the CPU with Varied Power States that you will work well with undervolting or any changes to voltages for that matter..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
So why did KT add a setting for UV/OV of the GPU if it shouldn't be touched...? I was able to undervolt the GPU by 75mv on slimbean before without issue...I don't remember KT saying to not mess with GPU voltages...why would he add a setting that is unusable...You don't entirely make sense to me. Explain further...? The GPU has varied power states, Low medium and high as stated in ktweaker, and if you use ondemand it'll switch between the power states.

I'm not trying to sound rude I just dont understand your logic. Its like adding an option to a car to adjust gas milage but shouldn't be used because it'll make your car unstable at the slightest change. So why would they add that option if it doesn't function properly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
No offense taken. :laugh: I guess I did make a bit of a cryptic comment there.

Let's start with your car and go backwards. You know you can buy a NOS kit or Turbo, for your car. Will you get one even if all you are going to do is suburban drive on surface street ? :laugh:

Please understand, this kernel is designed for 2 Devices, The Galaxy S4 with its GPU PowerVR SGX 544MP3 and then there's Galaxy S3 with Adreno 225 GPU. Both of them are dramatically different on how they approach the delivery.

As a basic principle, a GPU is expected to deliver at the peak of its capacity any given time. In modern times, depending on the kind of rendering involved, manufacturers have implemented multiple cores. So depending on its usage (Video Decoding, Game Frame Rendering), different Graphics formats and decoders come into play. Since the decoders are hardware based, additional cores are brought online by the GPU and the phone Chipset. For Graphics rendering, where pre-optimized images are present, (Games), mostly no Decoder is needed. Hence less cores may be used. Hence, unlike the CPU, GPUs do have a different way to manage Cores. Their load management is also driven by Decoders and Frame Rate among others. Now, when it comes to voltages, given the GPU is expected to deliver 100 % practically all the time, it is not able to perform optimally when the operational voltages are tweaked. However, as all Silicon goes, lowering voltage will lower Wattage and thus heat.

Both Power VR and Qualcomm Adreno implement Frame rate Control and Hardware Acceleration differently, not to mention Decoding.

It is my understanding, that the Power VR does indeed allow for core shut off and voltage variations to an extent. The Adreno does not, as evidenced by the recent testing at 5mv vs. 25 mv changes. Also VR derives its Load Management from CPU +Chipset and so CPU Governer indirectly plays its part. In case of Adreno, Governor changes may be possible, the chip may not like it. One thing's clear. For both of them, setting

different Governor from CPU Governor will potentially give choppy performance.

Hope this helps you understand this better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
+1 To the point :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Well said. I'm a computer technician I've been taking apart and building/repairing computers since I was 12. You are entirely correct. It was just your initial comment that had implied that the gpu voltage settings were dysfunctional but you cleared it up in an intelligent way. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
Running the 10/27 Kernel on Slim Rom 4.3 Build 2 I'm seeing a LOT of random reboots, especially when using GPS/NAV with BT audio in the car. Didn't see this on Slim 4.3 build 1 using the 8/31 KT kernel. Has something changed that could cause that? Slim build 2 is Android 4.3.1 so maybe that's the problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Slim rom v2.0 was built on 25th while kt kernel war built on 27th. There have been kernel changes since the slim v2.0 which may result in random reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
I think I misfired that post. Went back and read the Slim install instructions and it requires a full wipe. I was trying to keep my /data partition in tact, but I guess 4.3 to 4.3.1 doesn't play nice. Running Slim build 2 with the 10/27 KT kernel at 1800mhz on a full wipe and so far it hasn't random rebooted once.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Thanks for the heads up but I can't find the 10-16 version. I went to the thread with the older builds but it jumped from 8-31 right to 10-20.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You go get this version asuuming you are on AOSP and 4.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Not true. Look again. I promise you they are ALL there, including 10/16. You must have missed it somehow.

Perseus, the link you provided is for the Verizon GS3 and from 8/16.. Have I missed something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Luigi Guilty on the Wrong date. Not sure that's VZW version though. I used that version myself and worked for me...

EDIT - Checked from this post. Doesn't seem like Verizon...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Sorry my bad, I found it now. Thanks for the help, I will try it now. Are the default settings pretty good or do I need to tweak around right away? Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Are you sure? Please correct me if I'm wrong but the filename linked in your OP indicates VZW?? Unless I'm just that blind..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
Just flashed 10/16, wiped cache, dalvik and fixed permissions. Kernel boot logo comes up then just a complete blue screen with dashes of dark blue, green and pink. Can't say I've seen that before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I suggest you update BOTH your ROM and kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reechings:
I'll have to wait until the next RevoltRom nightly then I guess. I have tried Task650 and PACMan and Revolt has the features and customization that I like. I wanted to try this kernel because it seems to be one of the most popular and respected. Thanks for your help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
I stand corrected once again. Everything was well until I tried to use GPS/NAV with BT audio connected in my car on the way home work today. Instant reboot. I reverted back to the stock Slim kernel and everything is seemingly stable. I'll gladly help debug this; just let me know what you need me to attach to this post. I do software QA for a living.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
[MENTION=293206]Luigi[/MENTION]

So far your v4 settings have been working well, although in honesty I can't say I see much, if any performance increase compared to the CM stock kernel. I get about 3-5% battery drain overnight while phone is sleeping, same as stock kernel, as well as about 60% battery drain throughout the day with light use, again same as stock. I know it's hard to compare with other people's settings, but is this normal, is it doing its thing in the background, or is there something else to be tweaked/played with.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
You may have some background processing of unnecessary apps waking your phone from sleep more often than it needs to. Use Betterbattarystats to monitor and take shots of "Other", "Kernel Wakelocks", and "Partial Wakelocks". Better yet, PM me those results so we don't begin a brand new battery life conversation in a kernel development thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Great! Will do : )
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Do me a favor. keep the Bluetooth off. Just turn on the GPS and let it lock on a signal outdoors. Once it did, navigate somewhere. See if that goes ok.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Does BT work without GPS?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tugz101611:
Can is use this >> AOSP JELLYBEAN 4.3 Linux 3.4 VERSIONS << on Slimbean 4.3.1?

And if I can, Is the one in the OP flashable?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
There's no connection between Bluetooth and GPS. So yes.

Yes and Yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FrankieSixxxgun:
Okay, I can give that a shot.

Yes, BT works fine until I start up Waze and let it start navigating the map.

In further testing it's not just the BT/GPS combo that was killing it. The phone randomly rebooted on my while typing notes and while browsing Facebook too. Something with this new KT kernel doesn't agree with this latest Slim ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Switch to one version prior of the KT747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kdp162:
Flashed the last two versions of the kernel and it totally screwed up my phones display... It booted but either the screen came up scrambled or just a black screen... 10/17 works just fine... SIII running PA3.99 RC2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Prufta:
That's because your rom does not have the latest compatability or commits of the kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
I just noticed the first time I open ktweaker the GPU voltage on low reads 945 and in op it says 945 is the stock voltage for low. Even if I don't touch the GPU voltage, after changing ktweaker to my liking then rebooting, the GPU voltage goes to 950 and I'm unable to set it back to the original stock setting. Could this cause any issues? I don't remember seeing any glitches on the first boot and now I am seeing them. Toast notifications are glitchy and sometimes transitions are glitchy.

Running slim bean build 2 10/27, and kt747 10/27.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I have the same combo and I just checked. It does indeed happen. In this version of KTweaker, [MENTION=4325945]ktoonsez[/MENTION] did change it so that you can not reduce GPU Voltages in increments/Decrements of 5. So It will automatically take the value to 950 when you change CPU voltages. Its also the reason why you can't go back to 945.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes, you nailed it :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Yes exactly but wouldn't this cause issues?