yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
The kernel is required in order to use Ktweaker. Without the kernel you will more than likely get FC. Sorry bud
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWolf56:
You can use many other apps that are on the market. One that is well used is Trickster MOD. But it doesn't matter all that much which one you use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Not just that, but KT posted a long while back that his KTweaker app was only compatible with his kernel, as it looks for specific files. I'm not sure if that has changed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Look up... I said that same thing a couple of posts above you lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Oops. Didn't catch that. Sorry man, LOL.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Hi guys

Seems to me my MHz keep bouncing between 3 steps constantly:

189 (my min) , 378 and 486.

Is there a way to stabilize it?

Screenshots of BBS and my voltage config for the steps above:

Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
It's cool bro. I just had to do that lol

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

You may have other system tuners causing your frequency steps to jump around like that but it also does depend on your actions taken and when a load sample is locked in.

Try checking on "Lock Frequencies".

The setting is pretty self explanatory.

See if that better stabilizes your cpu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I don't have anything else running.

Lock freq is to lock OC I think and won't effect this bouncing. It may have to do with voltage and I played around with that a bit but still can't just get it right so its quiet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Lock freq stops other apps from changing freq - it's not just about OC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
The voltages should have nothing to do with that but it is always a possibility. However, checking on "Lock Frequencies" will lock your cpu frequency steps so that they can be controlled solely by the Ktweaker app and prevent other tuner apps from controlling them regardless if you have OC enabled or not. When you have others interfering with Ktweaker it will indeed cause steps to appear inaccurate such as yours. I'm telling you this based on personal experiences so I strongly believe that is the overall cause to your minor issue. For testing matters I would suggest ticking on that option, reboot, go about your regular activity, and monitor your cpu states every couple hours and see if you get similar results.

Please do report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Try setting idle at 378. 189 might be too low for you. Also, you could try another gov to see if it might be a setting with the Ktoonservative gov you have, specifically that 90000 screen-off setting. But I am betting on 189 being too low.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
@ LuigiBull23 I totally stand corrected. Locking freq did the trick. Set that checkbox and let it idle down to 189. It sat at 189 not budging for all of the 5 min straight that I have my screen timeout set for. Awesome. Before i can see it spin up and down constantly. Looking forward to even better battery life tomorrow. So far today with CPU going wild I got 17 hours with 2 hours of screen time. For me its very good and hoping with calmer CPU it'll be even better tomorrow.

Thanks guys for suggestions!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I have very similar settings to his but don't ever face the issue he's having.

Notice the differences. may give some clarity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Glad it worked out for you bro. Would love to see shots of your final results!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I'll post BBS shot tomorrow evening with full day usage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cerobles1:
Hi Ktoons, i switch to ATT from Sprint, and I was running your kernel. Anyways I got a GS3 and tried to installed the 5-3-13 that says it is for 4.1.2 but im running intergalactic 2.9.1.

After I installed the kernel WIFI wouldnt turn on like it was stuck. I tried to wipe cache and dalvick and fix permissions. How can I get a fix for this or get an earlier version??? Or what version do you recomme d with Intergalactic 2.9.1??? Thanks for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Refer to my thread for previous builds. link is in the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Hey Ktoonsez! Any updates coming. Task is two kernel updates ahead (3.4. 47) and says over 8 million commits ahead but I sure miss using ktweaker and seeing Task's "junk" every time my phone boots is getting old. :D. Thanks for your great work and support.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
Stop
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arcticrobot:
For each ETA requester there is an eager moralist rushing to be first to hush the sinner. Thing is never getting old. :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Kernel source available for VZW

Not specifically for our device, but I bet there are some similarities?

http://www.androidcentral.com/kerne...on-galaxy-s4-galaxy-tab-3-galaxy-mega-devices
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Great! This post likely just tacked another week onto the ETA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I think you all are over reacting. I think this question is legitimate and has a valid point. Another option is to just sit and patiently wait. Use tasks kernel it works fine. Then wait for toonz to update his.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
My comment was complete tounge in cheek. Sorry to get you all worked up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
He hasn't forgotten about you guys. Just relax and wait for him to push out an update. It's the best solution to actually receiving updates, not asking for ETAs..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
:beer: ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
I kind of understand why he asked since the 5/17 build will occasionally freeze with cm based roms dated after the 21st i believe. But... Ktoon has always been actively giving updates, give him more time and no ETAs is the golden rule on these forums. :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I flash the latest CM nightly along with the 5/17 built kernel each and every morning and haven't had one freeze or any issues what so ever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I've also done the same thing with the latest release of Vanilla Rootbox... and it's been running really fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Please check few posts back: http://xdaforums.com/showpost.php?p=41878373&postcount=12243

"We are good to go"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Very true. no issues on later CM builds nor should there be, unless it's the ROM build or user related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
This was true up until last nights nightly. Looks like there was a wackload of d2common kernel commits.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Must be either something in PACman after 5/21 or something wrong with my settings, but it has always been the same since 3.4 upgrade. Anyways running 5/28 pacman nightly with stock kernel for now. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I'm sure you haven't been living under a rock for the last few weeks but do you have the latest bootloader installed on your phone?

The 3.4 update was discovered to not be playing nicely with outdated bootloaders on everyone's phone. Everyone was forced/encouraged to update to the latest official bootloader for their varient of phone and that took care of most if not all random reboots that people were seeing after the 3.4 update.

EDIT: Just went back to your OP and you said freeze not reboot. Different issues. Sorry. Please disregard the information above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
When exactly did you upgrade to 3.4? Have you tried other 3.4 builds to this specific kernel? If so, have you always encountered the same issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
Ktoonsez is always up to date. He releases updates when there is overall enough changes and additions to make it worth while. Who needs to flash daily. He may not have a kernel this sec with the latest linux kernel available but in moments one could drop... You never know. KT is on top of his builds and never disappoints. He doesn't make nightlies like CM (maybe for himself :P) he makes updates that are proven stable and he doesn't base his timeline on others work... even if this other developer is his best friend. KT kernel is dependable, its tried and true and he accomplishes this with his own way of doing things. KT support over and out lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Cool story bro Lol. If only more users accepted this cuz it's pretty obvious, least it should be..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Wow, talk of arrogance, ktoonz created this kernel for free. I repeat free. He is not your peon. I would rather wait and get a kernel that works than having a new one come out with lots of problems. We should be thankful that there are people like ktoonz who do this on their free time. After all, they do have lives. I said my peace, let the flames begin. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Wow guys! I'm really sorry to open a can of worms! I wasn't asking so much for an ETA as just some info on how far "out of date" I was. KT's kernel is from 5/17 and Task mentioned the two linux updates plus "8 million" commits. I know KT's kernel was still working fine for me and I also know he's quite busy with SGS4 at the moment. Guess I should remember the adage "if its not broke, don't fix it"! I had just got used to seeing him in here so often and its like withdrawl without him. Back to waiting patiently for the best kernel!

Cheers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Nah, you're probably thinking of task... :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
FLOAM!!!!! Just trying to get my phone up to KT standards and I will be back this week on this. Actually alot of the stuff I am doing on the S4 is already brought into the S3, just need to debug and stuff :D

A couple new things for KTweaker:

1. Internal Read Ahead setting for speed

2. External Read Ahead setting for speed

3. GPU voernor selection (ondemand and performance)

4. Possibly add back in GPU OC with a toggle in KTweaker

5. Few more things...........
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
KT, I've been following you and Task for a while now... love you guys and your work. I'm wondering if you like the S4 enough over the S3 to recommend an upgrade (for me... or in general)? Are you now using the S4 for your DD?

Thanks as always,

The Weener.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mw86:
If finances do not factor into your purchase then I highly recommend the upgrade. Excellent display and the hardware is excellent (gpu cpu). It has a bit more premium feel vs gs3 holding and using both.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Since I have an upgrade due on one of my 3 lines, price isn't a factor since the S3 is worth more than the upgrade fee. I do like to wait around and get a refurb for like $20 -$50 though. I have had perfect luck on about 6 refurbs from AT&T and got a Skyrocket for $10 last year and my S3 for $20 to replace my S2, which I Ebayed rooted for $289 in October.....

The S4 is sounding pretty nice right about now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I would recommend it since you can get it cheap :good: :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Do you use the S4 as your DD yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
#5106355003453024S Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Yes I do :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Change Log 5.29.2013

1. Linux 3.4.46

2. Linux 3.4.47

3. Sync'd with CM as of an hour ago

4. KTweaker: "Extras" Screen: Added GPU Governor selection

5. KTweaker: "Extras" Screen: Added Internal Read Ahead (I recommend 3072)

6. KTweaker: "Extras" Screen: Added External Read Ahead (I recommend 3072)

7. Some compiler tweaks

8. Couple updates from codeaurora
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
KT is the man. The manest man, and we all want his children.

Thanks for the update KT, you rock!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davebmx05:
KT just flashed and im always impressed you never let us down :thumbup:. Just one question tho what do you recommend the GPU be set at or should I just leave it be
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
What are the units for the Read Ahead settings? Also, is the 500MHz GPU setting considered possibly unstable? Thanks for the awesome update!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Killobytes per second. And I dont know how that GPU option snuck into KTweaker but DONT use that, its not for this device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I'm guessing then screen off GPU max is also not to be used?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Do the GPU settings work at all on this device? I believe our GPU can handle 480MHz so 500 isn't unrealistic. The other setting, 450MHz is already higher than stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Only use whats in the change log for the new items.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Hows that s4 running? Hard to imagine aosp running any smoother than it does on my s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Where is everyone seeing the option to change GPU clock?

Edit: Not sure what you did, but my benchmark scores have jumped significantly. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
According to KT GPU clock is not to be messed with. You could change GPU governor under extras.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Np, appreciate the help. Yeah i have latest 4.1 jellybean bootloader. No freeze issue with stock kernel. Will try ktoon 5/29 and see
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
It's actually not much better (if any?). In terms of responsiveness, animations, etc it's identical to the S3. Benchmarks are much higher for the S4, but in regular day-to-day use you cannot notice a difference.

The main benefit of having an S4, for me, is the battery life, screen & better physical shape of the device (it's that much better). Any performance improvements have yet to be seen in AOSP-based builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
The new tj build is running well. I think I've found another bug in the updated ktweaker. If I have enable oc unchecked (which I usually do) then the voltage table is a little screwy. It starts at 1188 instead of 1512 and has a bunch of blank spots at the bottom. If I enable oc then it looks normal.

I've cleared data for ktweaker and reset defaults, same results. Can anybody reproduce?

I'm running with oc enabled and max speed set to 1512 for now.

Thanks for the awesome kernel and for continuing to support our s3s :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Subsonic44:
Thanks KT! 2ET79452SB357422W
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jde984:
Same here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
To decrease issues on updating this kernel I highly suggest starting over and following my 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) {Optional} Clear all superuser logs

6) Reboot Recovery

7) Flash kernel

8) Wipe cache/dalvik

9) Fix permissions

Clean ROM installs only require steps 6-9.

Hope this helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just checking to be safe... Is it okay to restore Prefs from sdcard that were saved from previous versions of the kernel? Like I will be flashing the newest build tonight, and I want to know if it's okay to restore my prefs from the 0509 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes, it's ok
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
BT Problem??

Just FYI, on 5-17 bluetooth and AOKP Nightly works great. On the 5-30 version the old re-connect issue pops up again. Went back to 5-17, works fine.

This same problem came up on Task last 2 versions with his kernel???? My vehicle bluetooth is UConnect. Leave the vehicle, return and will not connect on it's own.

Thanks for your work. Staying on 5-17 for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Works just fine here. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Okay I'll try it again. Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Did you force close and clear app data for KTweaker?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Third time seems to be the charm. BT working fine For now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Will the 4.1.2 kernel work on a 4.1.1 TW ROM?

Will the latest 4.1.2 kernel work on a 4.1.1 TW ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zzmomo73:
It should.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes. They are compatible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
Here are some screenshots of the voltage screen with oc disabled... not sure how well this will work.... the first slot is the top of the voltage screen, the second is the bottom.

This behavior persists through force stop, clear data and reset defaults.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I still havent figured what that ROM is doing to my sysfs files. It super creepy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
Is there anything I can check for you on my phone? I haven't changed ROM in months and months, I'm still running tj LK3....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If you are still having the problem get a screen shot of the following files opened up in Root Explorer or ES File Exp

/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table_stock

/sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

Also, post your KTweaker file too if you can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
KT

Here is an interesting one;

When using USB car dock phone becomes suuuuuper laggy like within min of plugging in. Both with some apps running and even just sitting st home screen. Then it just reboots.

Here is the last kms. Any clues in there?

http://db.tt/LcAAS6vu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
Here's the screenshots with oc disabled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
So I compared oc enabled to disabled. It looks like there are 6 extra steps with oc enabled. That's the same number of blank steps at the bottom of the voltage table in ktweaker.

Maybe somewhere the code is accounting for the 6 missing steps incorrectly? I think there are also 6 steps between 1512 and 1188....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Nope same code for the last year, makes no sense whatsoever :(. Only place 6 comes into effect is thats the number of extra steps in OCing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
My thinking with the 6 is that, when oc is enabled and max speed is 1512 then you ignore the first 6 available frequencies. With oc disabled and max speed at 1512 then 0 frequencies should be ignored, but if the first 6 frequencies were ignored then that might explain starting at 1188 and having 6 blank spots at the end.

Is there a way to test with the previous ktweaker? Can I manually extract it from my old kernel zip and install it into /system/app ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
I can say I'm having the same problem on the new build with TW. If you enable over clocking the steps return to normal. Only seems to affect the voltage table in my case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
I installed Ktweaker 3.2 from my previous tj kernel zip and the voltage table reads correctly with oc disabled...

Sorry for reporting the confusing bug :) it seems like the code for populating the voltage options in ktweaker has somehow changed...

It's not important anyway, I'll just go back to oc enabled and current ktweaker :)

---------- Post added at 09:34 PM ---------- Previous post was at 09:15 PM ----------

Last thing and I promise I'll shut up :)

If I

disable oc (max speed is 1512)

go back to the menu

go into voltages (where the max is 1188)

go back to the menu

enable oc

Then max speed goes to 1188 of 1512 (instead of 1512 of 2106). If I go back to the menu (no changes) and back into general it shows 1512 of 2106.

Thanks for the awesome kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I think I might have figured out whats going on. Somehow I believe the ROM is overriding my "scaling_booted" flag. Please check the value of:

/sys/devices/system/cpu/cpu0/cpufreq/scaling_booted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yes, we're all aware of that at this point. It is very strange though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tiernan22:
This is happening to me as well.

I have a value of 1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gerbig:
I promised to shut up, I'm trying not to be too annoying :p

ktoonsez, the file you requested says "1"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Lol all good brotha! I understand it can be frustrating but the matter is being taken care of.. Patience is key :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
If its a 1 then scaling_available_frequencies should show 81000 all the way to 2106 but I know its not, something is giving it the co*k block.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Threezees:
Value of one. Stock LK3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Another question

Any reason why ktweaker would use up so much battery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Its lying to u, KTweaker uses ZERO battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Was trying to post screenshot looks like they didn't make it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
It wouldn't have anything to do with the spontaneous reboots I saw while plugged into USB car dock. (Previous post earlier today with link to last kms : http://db.tt/LcAAS6vu)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No i doesn't, something in the ROM pissed off something. Kept repeating error:

msm_fb_wait_for_fence

Never seen that and search turned up nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Weird. I will run catlog tomorrow when I dock again. Maybe it'll turn up something on the ROM side. Thanks dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
What ROM are you using?

LiquidSmooth v2.5 & LK 3.4.47
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] golastic:
What does internal read ahead and external read ahead do? Pls
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I'm on CM latest nightlies