yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SizAndals:
Having flicker issues on T-Mobile S3 while using LiquidSmooth v2.10. Just a heads up to anyone wishing to flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Couple of things to report...

Sometimes my screen won't turn on after the flash with PA3+ RC-2. And no, my lowest CPU is 384mhz

2nd, since I have flash this kernel I am no longer able to use FolderMount anymore. Now, Folder Mount just kills my extSdCard link.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Just spent two hours. wiped everything installed pac 10/15 10/16 10/17 kernel keeps me in a boot loop after the rom install/setup. Installing 16 or 17 is a fail unless upgraded dirty from 15. So I don't know what to say besides 10/01 being the prize winner.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Are you using a T-Mobile phone on AT&T? If so, stick with T-Mobile ROMs and kernels. The ROMs and kernels are designed for the specific hardware, not carrier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
The T-Mobile variant users the AT&T version of this kernel. They are compatible with each other.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
what is a good governor to run in Screen Off that I can use with intensive task with V4A? Right now I think everytime I switch to a different governor for screen off I can't get it to turn back on after the screen is off. But I want to find something were don't get any hiccups with V4A during screen off
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Doesn't matter. Ktweaker has the option to adjust your screen off MHz. Just raise your screen off profile MHz a few steps and see if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shane269:
Check your minimum CPU speed my processor won't run under 385 I think the defaults are 185.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Yes I have done that... I have it up to now in the 700mhz area so that V4A doesn't hiccup. (as much)

However I still don't understand why so far all the governors I have try will have the screen bug if it's set to a different governor other than what is set as the initial governor. So another word mixed governor just wont work?

---------- Post added at 09:58 AM ---------- Previous post was at 09:56 AM ----------

Anyone know if during Screen Off, it only allows 1 CPU to be active or does it allow BOTH CPUs to be active?

If you have read my post earlier then that post, I said I had it on 384. The problem with the screen bug isn't with the lowered mhz, its the mix matching governor
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Depends on the ROM/phone/app that you are using. It works for thousands of people including myself but a few people do have troubles. Usually it ends up being a poorly written app that they are using to play.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Would someone mind explaining what this "V4A" is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
That's attributed To Liquid. I have T-Mo version of S3. I used to get that with Liquid. Turn off Hardware OVerlay in Debug.

You need to change Screen Off MHZ in Extras under Ktweaker. Check the link in my signature.

I think he was referring to some band.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
V4A = Viper4Android http://xdaforums.com/showthread.php?t=2191223

---------- Post added at 02:09 PM ---------- Previous post was at 02:07 PM ----------

Did you not read this part. Although the write up is nice, but doesn't answer my question regarding how the CPU works in Screen off situations.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Yup. There's been plenty reports of it not functioning on 4.3.1 but I'm here to report Viper4Android is working flawlessly on Slim weekly 1.8 and latest KT kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Ok My bad. I mis understood that in context of your Governer Changes question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
It works fine too if I leave it on Performance governor on PA3+ RC2 (which I don't think they have commits from 4.3.1 yet anyway) but that kinda kills the battery.

I guess I am trying to find the "perfect" settings for SCREEN OFF situation so I don't get any hiccups while listening to music via V4A
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
I have a S3 running Bam Rom 1.0rc2 Android 4.3.1. I tried installing ktooz kernel 10/16/2013, but phone hangs on reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
2 questions. Did you download correct version ? and did you wipe dalvik and cache beforehand ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Not to be a stickler, but is the OP going to be updated with this too? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SkyboneNoya:
Noticed with Pac the kernel it ships with (cyanogen?) is really good on battery when it comes to Media Server.

As soon as I use kt it bumps up. Media Server ends up draining around 40% of my battery.

Not sure if that's something you can fix from a kernel point of view but just something to note.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
AOSP Test kernel

1. 100 % sync'd up with CM as of a few hours ago

2. Added PAC ROM dependancy to ramdisk

3. Updated Ramdisk to latest CM including 4.3.1 stuff

Only load with CM 10.2 with date 10/19 or newer!

http://goo.gl/aCwLSG
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
KT, I know this is a few days old, but I flashed this over the 10-19 CM10.2, and got some very strange colors. The boot screen was solid cyan with flashing purple blocks and, once booted, Android was orange instead of blue. Any thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
must flash! :good: :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
U gotta test the one I just posted about 30 seconds ago and see what happens, there was a whole buttload of video/gpu commits :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea, I got the notification that you'd posted as soon as I posted. Testing now.

---------- Post added at 01:13 AM ---------- Previous post was at 12:54 AM ----------

::highfive::

Nice!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FtaWolf:
Wiped both caches installed KT747-AOSP-JB-MR2-3.4-ATT-10-19-2013 on quantum v2.12 boots up to messed up screen .

Loaded up kt-10-16 kernel booted up fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Guess you didnt catch my post above. There were butt-loads of updates with video and gpu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Interestingly, I had the opposite experience on CM10.2 with the 10-19 nightly, that is, busted screen with 10-16 KT747 and working as intended on 10-19 KT747.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
only load with cm 10.2 with date 10/19 or newer!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Gotta wait for my rom (Quntum) to update, but thanks dude!!! I hope this continues to get updated. All the PAC fans who stuck with 10/1 are gonna have to let it go now if they want to run the best kernel around :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mgsfan:
flashed on my TMO CM 10.2 10/20 nightly and booted up just fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Flashed over today's updated Slimrom. Specifically, wiped cache and dalvik with CWM, then flashed slim + gapps, then rebooted, then wiped c+d, flashed KT last night's version, wiped c+d again, then rebooted.

On reboot, the display was kerflooey. Green tinge with scaling all zoomed. Looked like a Picasso of my lockscreen. Hard rebooted to recovery and reflashed slim.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zander21510:
Flashed CM 10.2 nightly 10/20, then gapps, then 10/19 KT747, wiped cache and dalvik, got a yellow cyanogenmod logo then a blank screen and nothing. Just offering my feedback :) thanks for the update KT!

My mistake, I flashed 10.2 Not 10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niphoet:
Exactly the same here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Again :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Where are you downloading 10.1 nightly.. CM is only offering 10.2 nightlies at the moment..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zander21510:
I mistyped, it was 10.2!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The latest release works for me on cm 10.2 20/10 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zander21510:
I assume with a full wipe? I wiped only /system and /cache on my flash...I'll try again when I have time later today, if it still doesn't work I'll do a full wipe. The fact i'm on a d2tmo doesn't affect it since its the same hardware, correct?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Full wipe for me = Format system, data and cache. That works for me. Yes the hardware are almost identical
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Seems like no, waaaaaay to many people having a hard time with the 10.2 from 10/19 or newer part. Probably wait till tonight or tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
You are the man!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
So great to have you back, KT! You were missed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
Same issue here with task latest. Tried flashing twice now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sirrkitt:
It says not to flash it unless you're running cm10.2 10/19 or newer. A lot of ROMs still haven't synced up yet with CM's new graphics driver change. So switch ROMs or wait patiently until the one you're running pulls in the changes fr CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Yes to both. In fact, I tried the wipe before and after.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zander21510:
Okay, turns out I used the wrong CM file. Sorry for the confusion. This flashes just fine on CM 10/20, without wiping data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Gonna recompile and release, 10/20 version will be the same as 10/19 test. It will be up in 15 minutes :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Only load with CM 10.2 with date 10/19 or newer!

Change Log 10/20

1. 100% caught up with CM

2. LOTS of Linux and video/gpu updates

3. Too many to list, if u want full list, Go here and its page 4-6 (October 3- 19)

https://github.com/ktoonsez/KT747-JB/commits/mr2?page=4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
OP Updated

Only load with CM 10.2 with date 10/19 or newer!

Change Log 10/20

1. 100% caught up with CM

2. LOTS of Linux and video/gpu updates

3. Added compatibility to 4.3.1

4. Added compatibility to PAC ROM new 4.3.1 requirements

5. Too many to list, if u want full list, Go here and its page 1-6 (October 3- 19)

https://github.com/ktoonsez/KT747-JB/commits/mr2?page=4
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Confirmed that the newest CM commits didn't make it into today's Slimrom, so slim users should stick to the KT 10/16 build for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I assume you are referring to Slimrom v1.9. If so thanks for letting know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
Right - Slim 1.9 weekly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I did read both comments on both the threads. I am using 10-16 kernel with Slim 1.9 at this time.

But I am confused. Is it the Slim that's not caught up with the CM changes according to you. Or is it that CM does not contain latest driver changes Slim needs so KT10-19 is missing out on those driver related changes ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
Yes there is ROM changes that are a prerequisite for the kernel changes, Slim has not made the changes for some reason, probably because they are preparing to release a stable and found these changes unnecessary?

anyway, to sum it all up

Liquidsmooth stable, Task's AOKP & Slimbean users, flash the 10/16 build of this kernel as it works perfectly for us

CM and Carbon users flash the latest :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
How has 10/20 been in terms of battery life? I ended up restoring my CM10.1 backup since battery life has always beem worse on 4.3 for me.

Perhaps those GPU commits will do the trick?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshReuben:
It's Slim that's not caught up with the CM changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Thanks guys for the clarification.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks man, eagerly waiting for the next big update for tw rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I updated my rom to BamRom 1.0 rc3 based on 4.3.1. I tried to install 10/19 build but no love. It just hung up. I hope the 10/20 build works.

Sent from BamRom S3 with Viper4Android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Try 10-16
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kyanox:
Hey, love the kernel. I use touchwiz though and haven't seen an update in a long time.

I keep getting random reboots and have tried upping the voltage. Am I missing something or is there maybe a memory leak. The random reboots are happening after 4 or more hours of sitting idle..............

I'm mostly wondering if this is a known bug or if there will be a kernel update to match the current kernels for 4.2/4.3?

I'll try to pull some diag data and post as well. My phone is picky, it hates lower voltages :( Thank you in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
The most recent version is 8-20. I assume you have that version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I am also waiting for the update on tw kernel. Hope op get some time for this from his busy schedule..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Hey ktoons I'm having random reboots on the 10/20 build on pacman 10/21 nightly. But If I load default kernel settings in ktweaker I don't get any reboots...Also while playing galaxy legend for about 5-10 mins the screen gets glitchy and freezes yet the phone doesn't reboot, have to hold power button or pull battery. Also noticed toast notifications have glitchy transitions sometimes and also a couple other glitches from other transitions.

No OC or UV I'm actually under clocking to 1188mhz, if I do UV I get reboots a lot quicker. I was able to UV from 75-150 on quantum and dkp kernel, so I'm not sure what's wrong.

Logs:

Dmesg

https://db.tt/VtRWoxqH

Kmsg

https://db.tt/RYS12eai

My settings

https://db.tt/pxAguPnD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
Anyone else getting "Unfortunately, the process com.android.phone has stopped." with the 10/22 CM nightly or is it just me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
KT is working on it bud.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
I have the same issue.

KT if you need a log for this let me know I will get one after work till then I have to use stock CM kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I will take a look:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Been trying all morning with the Verizon guys with no luck so far. I'll build one up to u when I get back from lunch
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Xda is thanking posts on me that I didn't thank lol weird
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Try this one guys and let me know:

http://ktoonsez.jonathanjsimon.com/sgs3/aosp/KT747-AOSP-JB-MR2-3.4-ATT-10-22-2013.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
KT is back with an update for our lil' old S3? Praise da lord!

I've been rocking LeanKernel for a while, but now I'm going to be super tempted to try out this new KT build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
This worked for me after re-naming it to .zip ... just a small oversight I'm sure.:p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Awesome!!!!!!!!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wutname:
none of these seem to work with i747m on pacrom 10/17 nightly.

always hangs on boot and never loads >: (
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
You may want to go back to older than 10-16. Pacman may not have included all the latest CM changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I am running pacrom 10/21 and kt747 10/20 without issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Without issue? I keep getting reboots...even switched goveners and schedulers changed other settings around and still get reboots, freezing or glitches....

Running the same setup 10/21 PAC, 10/20 kt747

EDIT

This is on a clean flash even formatted internal storage. Flashed ROM gapps, let it load up set all my settings, install apps from titanium. Then flashed the 10/20 kt747 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cirusnb:
This one works with Vanir Rom, Oct 23rd nightly build.

Of to 1634, voltage minus 25 across the board, conservative, , row.

Thanks for quick fix.:sly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Hey KT I just had another freeze but I was able to shut the screen off before it completely froze and I have a dmesg and kmsg of right after it froze and glitched if it makes a difference. The last logs I sent yesterday were after a reboot.

Dmesg

https://db.tt/VtRWoxqH

Kmsg

https://db.tt/RYS12eai
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
No good info in there :(. Just rebooted without a kernel panic, so there is no bug in the code (just a vulnerability) so its something that the ROM is causing :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Hey KT, A touchwiz user reported very low speaker volume on 10-16 Kernel. His post with Dmsg & Logcat over here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Hmm, you don't think its the kernel? I didn't have any reboots or freezes with the kernel that comes with pacman.

Maybe its just the 10/21 build I'll flash the 10/22 build of pacman and see if that helps the cause.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Also go back to 10-16 version of KT747 just in case Packman missed out on the CM changes for display drivers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
So I should just flash over the 10/16 build on top of PAC 10/21 build? Or should I do a fresh install with kt's 10/16?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
I'd do fresh install with 10-16
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
I went ahead and just flashed kt's 10/16 on top of PACs 10/21 without a clean install and....after the kernel domination boot screen it was a green screen with glitches everywhere...so I'm guessing PAC did integrate the video commits.

So I reflashed kt's 10/20 again and here I am lol.

---------- Post added at 01:00 PM ---------- Previous post was at 12:58 PM ----------

Idk I'll download PACs 10/16 with kt's 10/16 and reflash and see if it doesn't reboot or freeze.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Do please a Clean Flash. Given your problems, Dirty flashing may not help diagnose.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Ofcourse, I just wanted to see if PAC integrated the video commits.

Downloading PACs 10/16 right now and then I'll flash kt's 10/16 and illreport back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
I was getting a lot of that at first, but then I reset my cpu to stock voltages and it has run fairly well since then. I think I only had one reboot last night as compared to one every 30-45 minutes before that. I just looked and I don't think I kept the last_kmsg from that most recent one, but it had a lot of gpu page fault messages so I changed the gpu governor back to on demand to see if that made a difference and it hasn't had an issue yet today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
I always run the GPU with ondemand and was still having reboots :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbze430:
Seems to be working well with PA3+ RC2 10/23 build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] haveagr8day:
Yeah, looks like that didn't fix mine either. I just had the same thing happen again as last night, but I got the logs this time.

First the screen froze up on the lockscreen after pulling it out of my pocket, and after about a minute, it did a hot reboot. After it came back up I grabbed these. It looks like there was a bunch of the GPU page fault errors again in the Dmesg.

Dmesg : http://xdaforums.com/attachment.php?attachmentid=2346022&stc=1&d=1382563845

Logcat : http://xdaforums.com/attachment.php?attachmentid=2346023&stc=1&d=1382563845

Last_kmsg (This probably isn't useful because it wasn't a full reboot) : http://xdaforums.com/attachment.php?attachmentid=2346024&stc=1&d=1382563845

Then, as I was getting ready to post those, it did a full reboot (from still running after the previous hot reboot a few minutes before), here is the log for that.

Last_kmsg : http://xdaforums.com/attachment.php?attachmentid=2346025&stc=1&d=1382563845

Hope there is something useful in there.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Pacman build 10/16 does not work with kt747 10/16, even tried probam 10/16. Both ROMs boot animation just keeps looping, not a boot loop. Damn I can't be without the features :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cameronmx9:
I have the stock 4.1.1 rom. Will this add the CRT feature for me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
probably. But I think that mod needs Xposed Apps framwork. If yes, then you are out of luck.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Sorry to be so persistent KT but I literally cannot get any of the newer builds to be stable on any pacrom build...It either doesn't boot, or if it does boot then it constantly freezes, reboots, and has graphic artifacts/glitches.

I spent most of of my night last night downloading every pacrom nightly and all 3 new kt747 builds and tried every combination possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
Are you sure you must have Pacman ? Is there a particular feature that you like ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
I love PAC because it has basically every feature possible and there still adding new features like active display and the new wakelock blocker and all of the ui customizations including per app DPI and a plethora of other features one must have with his android phone LoL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jowilk:
Hi, I am having the same problem with BamRom. I read in fb post that the problem lies with the roms framework. Because of the size of the roms, the framework is split into 2.

Sent from BamRom S3 with Viper4Android.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
I think it's bc pac is 4.3 and this kernel is for 4.3.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DiViNEX:
Pacrom is 4.3.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Perseus:
If its a rom issue, can we please take it to the Rom's thread ? I am just trying to keep the thread on Track.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobapunk:
I am experiencing this too. AnTuTu CPU speeds are all over the place. However, after running a graphic intense game, like Race of Champions or Real Racing 2, CPU Spy is reporting that the CPU is running at or below the set MAX (Set CPU).

So it does appear that AnTuTu is doing its own thing with setting the CPU Clock. That explains why the score is all over the place and why it appears to be lower at higher clock speeds...

My advice is to not use AnTuTu to "stress" the CPU. Use a game such as Real Racing, Race of Champions, or any other "graphic intense" game.

:)