yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I'll hold off on doing a full-gonzo reinstall until then. If I'm going to do that, I might as well put the latest stuff through its paces, right? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Rad news about mpdecision, me gusta auto-hotplugging.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
For those of us who have trouble remembering where we left our dirty socks the previous night :), could you refresh our memories about what mpdecision is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
MP-Decision is a qualcomm made hotplugging service. It is used across all of our Snapdragon S4 devices essentially, regardless of how many cores the phone has or what make the phone is. It turns core 1 off when the screen is off, and it also contains temperature throttling. The only issue is that MP-decision is a software based solution for hotplugging, as opposed to this newly introduced method of MSM-Hotplug, which is based on our ARM architecture.

Also just got to class, so expect a build later tonight around 9 or so. Gotta build and test!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peach007:
Anytime I connect heaphobes, the music plays through the speaker. Is this related to faux sound?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tybalt:
Does anyone have working Wifi Tethering? I am on Quantum 1.25 and just tried Wifi tethering and it doesn't seem to work.

Some google searches seem to indicate that it's a CM10.2 problem and not specifically a Quantum problem.

Wondering if anyone has got it to work?!? Or using a workaround?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I just checked mine. I tried it both without security & with WPA2 security & it seemed to be working fine. I connected to it with my tablet & it all worked fine. Running 1.25 & latest DKP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Works fine just fine on my end, I acutlaly just tried it out today for the first time as well.

ALSO. I need people to test out a new kernel ASAP!! Let me know so I can make more adjustments before release!

http://d-h.st/lpX
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
The latest version of chrome beta appears to be an incredible waste of battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
This kernel seems to be running fine for me. I haven't been on it too long though. Anything in particular that you want me to test? Any certain governors or schedulers? I'm using Interactive & ROW right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Just watch battery and for random reboots. Did you have issues with any previous QK versions?

ALSO EVERYONE SWITCH OFF MP-DECISION IN TRICKSTER.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dankaren:
Phone just shut off with new test kernel. I didn't adjust any settings except turning off MP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
This is actually the first one I have run. I just flashed it b/c you asked for testers & I've been meaning to try it out. It was a good time to do that. Still running strong now using the Asswax gov. Been running for an hour total.

*Edit* - I'm also UV'ed by 50.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Haven't seen that yet, maybe my voltage tables aren't going to the right processors?

the 918 Bug is known and is probably an issue from my build environment. I'll build again later on and test things out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Kernel working for me with mp off. Asswax governor and default settings, but changed SD read to 1280 fifo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
the test build working good for me so far, i let my phone sit for about 15 mins to see if it would lock up nd it didn't:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Did all of you have issues with a previous kernel release?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tybalt:
So, I can turn Wifi Tethering on, I can connect to me phone with another device.

After that I can't access the internet. Neither browsing or apps can access internet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Test installed - wiped sys dalvik cache installed 25 test and gasps.

Boots correctly... Setting kernel settings now.

Is there a stress test framework we can throw at this?

---------- Post added at 09:17 PM ---------- Previous post was at 09:13 PM ----------

Also confirmed asswax my off fifa 1024

---------- Post added at 09:26 PM ---------- Previous post was at 09:17 PM ----------

Ran quadrant benchmark result

Total 5325

Cpu 12667

Memory 4582

IO 6339

2D 1000

3D 1983

---------- Post added at 09:31 PM ---------- Previous post was at 09:26 PM ----------

Running supersu time 512k to stress test

---------- Post added at 09:38 PM ---------- Previous post was at 09:31 PM ----------

Super pi that is... In the background 444 seconds no crash.

---------- Post added at 09:40 PM ---------- Previous post was at 09:38 PM ----------

Test kernel may have bugs but it does not fall down dead from Cpu gps stress.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
test kernel - did not try

0.99 working fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
I have not had any trouble with any previous builds or kernels

Sent using xda app-developers app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
No trouble on .99 but I haven't tried the test kernel yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Tried the test kernel and when device went to sleep after first reboot, needed to pull battery to get device to wake up. Flashed 1.25 with the kernel it came with and things are good. Kernel packaged with 1.25 is faster than all the other kernels IMHO.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
Been testing the test kernel with 1.25 and things have been running smoothly. Settings are: MP off, io 1024, Fifi, and asswax. Rest are stock.

Haven't used it enough to report battery life but the kernel has been running with no problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Maps crashed today. Up time of about 12 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
OT: Fifi and asswax... Only here are those perfectly acceptable to be in the same sentence together. Lmao.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
Hahaha tell me about it, some of these names :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peach007:
Anytime I install the quantum kernels, my phone randomly shuts off when I'm not using it and I have to battery pull to turn it on half the time.

This is wish all the kernels you released. Once I went back to stock it was perfect again.

I really enjoyed the kernel you released. Good performance/battery life.

I'll try again when I get back home.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] willbs94:
Logcat may help to figure out what is happening
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WaterMan!:
Is anyone getting random signal / internet connection drop? I really like this ROM but its driving me crazy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Your CPU is a "slow" cpu and it times out when trying to wake up your second core from power collapse. Some devices can't handle it, but the ones who can get to see a nice battery boost. I'm trying to hold off building into they (CM) merge from CAF.

Although on the other hand the default kernel does have power collapse enabled, so who knows what's actually going on. In my last kernel test I reverted user voltage control and it seems to have helped on my end, though my friend running stock CM has also seen a ton of reboots. It's an odd issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
bug gallery select pic menu details boom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Fixed in my latest test version of 1.3 ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Nicely done. Battery life isn't what is was back in 20. 5hours battery life. Can't leave home without my USB cable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
1.25 and. 99 bug fresh install of mega app. run. log on. pause 2 3 boom

---------- Post added at 04:06 PM ---------- Previous post was at 04:01 PM ----------

... Will download 1.3 test this email eve if on the share
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobchef:
This a feature request. Will dark UI be integrated anytime in the future? Thanks for your work.:thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can't find the download link for 1.3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I don't think he has posted it yet. It's not on his dev host.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nishchhal:
Keep an eye on this :p

http://d-h.st/users/TommyTarts/?fld_id=23007#files
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bountyman334:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ki11aprime:
1.35 is up, testing now will give an update in a few hrs :D:D:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polsonov:
1.35 downloaded and flashed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Quantum v1.35

Kernel updated to 3.4.61

In kernel MP-Decision ***Make sure your cpu min is set to 384 as opposed to 918 by default**

Power Collapse

Power profile updated (mastamoon)

CM sync as of 2 AM

CM Account

Bluetooth fixed!

ARM Optimizations

Gallery fixed

Fixed screen waking up

Audio Fixes

QuantumKernel-TEST2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
1.5/test

1.5 + stock kernel - ~4 hours. No problems.

1.5 + dkp kernel - ~1 hour. One random reboot.

1.5 + test kernel - ~14 hours. No problems.

So battery not so good, but no doubt the issue is "Google Services". After observing this at about 6 hours in, I wiped the data for the Play Store, and Google Services seemed to behave for a while, but overnight came on strong. Hmmm..?

Battery pic here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Turn off wifi always scanning for location, and under google settings change reporting location to off, location history on
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
Thanks! I think you actually said that a bazillion or so posts back. My bad; sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jndrad:
wont stick

set mim cpu to 384....keeps going back to 918...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Same here with stock kernel. Going to try the test kernel now...

Edit: Same results with test kernel. Max CPU setting will stick, but min will not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
Thanks for the info... ill be staying on 1.19 and below for now then... battery life is most important for me, spoiled ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
it's weird though. Even though it says in trickster the MIN is set to 918, watching device status shows it idles at 384. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Same here on test2 kernel, however, the processor itself shows it's going to 384.

I used TricksterMOD to force min-max freq lock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I told you guys! It sticks for me every time, so make sure that you don't have frequency lock on. Even though it says 918, most of the time it defaults back down to 384. The other way is to turn off touch booster under MP-Decision in trickster. It surprisingly hasn't given me an issue since I did my clean install this morning, every other day I had to change it at least once.

The battery life is also worth having this little issue.

Just noticed in for the first time on my end. Just turn off those damn boosts :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
On 1.35 a day test kernel downloaded eve of Sep 12. Wiped dalvik and Cache. Running haven't tested yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Flashed 1.35 and TEST2 kernel; Asswax governor, minimum 384, maximum 1512, MP-Decision and Frequency Lock turned OFF in Trickster. No issues so far other than what others are reporting with the minimum frequency showing 918 in Performance (current frequency does go down to 384, though, so it does seem to be working properly).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Updating to 1.35 and the 2nd test kernel, are we supposed to keep MP-Decisions on or off with this kernel?

Wiping dalvik/cach and system, flashing rom, gapps, kernel, supersu, fix permissions, wipe dalvik/cache and reboot. Never had an issue this way
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Turn off MP-Decision, the implementation I have in place now overrides it. Also go into MP-Decision and turn off Boost if you guys are having any issues with the minimum frequencies.

The reason this is happening is due to the fact that it manually writes your boost settings every time you touch your screen in order to be more responsive. It will get worked out once the port is finally completed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Alright, installed and using asswax this time around. MP-decisions and touch boost turned off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Suggestion: on the About screen, perhaps the CyanogenMod Version field chould show the version and date of the CM version you synced, and the Build Number field chould show the Quantum version and build numbers. This might be especially helpful during development, so that we may present you with the most accurate information possible. Just a thought. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
There is a build date box right below it in settings. All it does it tell you the Cyanogenmod day, which is based on the build date.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Fair enough, but what about the actual CyanogenMod version (i.e. 10.2, 10.2.1, etc.)? I know, I know, it's just a tiny, unimportant, insignificant little thing, but I'm kinda Sheldon Cooper-esque about stuff like that. :) As I said, it's only a suggestion, your call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
Running 1.35/Test2 w/suggested settings. All ok; Battery life tbd.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Excellent. With those settings the 384 min CPU sticks. And based on your explanation it make sense why it wasn't sticking previously!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Bluetooth was supposed to be fixed in 1.35 (just what part, though?), but I'm still running into the problem of BT not connecting to my car (2013 Dodge Dart with Uconnect) right off the bat; I still sometimes need to shut BT off, wait (it'll do a quick on/off by itself), then turn it back on before it'll connect. I haven't tried turning it off before I turn off my car, which caused BT to stay enabled on the phone (requiring force-stopping BT share); that's my next test. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
1.35 and test 2 kernel.. Haven't touched mp decision or any settings and all is well.. Guess I'm lucky.. And haven't touched boost either ;).. We shall see
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oriveradel:
Did you pair using your cars provided BT code? Or w/ automatic pairing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peach007:
I am using quantum v.1.35 and the new kernel. Everything is running smooth and fast.

I am just unsure what governors are good for what. Like the cons and pros of each governor. At the moment I am using badass but I don't know why (technically speaking, otherwise, it just sounds funny so that's why I chose it).

Also is here a way to see what changes when you change the governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Stick with interactive or asswax or intellidemand. They all just change on how your cpu reacts to your inputs and the processes that the cpu are handling.

Well what got fixed was that Bluetooth finally works when pairing with a car. It wouldn't work for me up until a few days ago, which it now finally connects under the media profile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
Hey pwn it is OK to run default settings right.. I have test 2 kernel and haven't touched anything and seems fine to me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Automatic, but that worked just fine when I was running CM10.0. It only started acting weird with CM10.2 (nee Quantum), which tells me that the CM team did something that "broke" it (I know it's not PwnCakes' fault). It still works, of course, it's just an annoyance; I've gotten used to getting around it. :) (Glad it's now working to get people connected that couldn't otherwise, though!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
I haven't changed a single setting from default and I'm rolling good
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Could anyone post a link for me for the newest kernel? I can't seem to find it in the OP either that or i'm blind... :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dankaren:
http://d-h.st/users/TommyTarts/?fld_id=23007#files
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Thank you, I remember seeing it a few pages back, but I couldn't find it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
Wow so it turns out audiko was the reason my launcher kept resetting. For some reason audiko shows up as a launcher. I deleted audiko restarted and my launcher didn't reset. Very weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
cpu governors explained

I posted this link in post #2034 on page 204. It explains the different cpu govenors. I had no idea either as to which one to use. Still a little muddy after reading the post.

http://xdaforums.com/showthread.php?t=2031214

Updated link. The one I posted in this post didn't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Check 2 pages back. I won't put kernel in OP due to the fact that it's still giving people som eproblems.

On the other hand expect a new kernel update soon!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
Does anyone else experience cracked sounds when using Bluetooth on the newest Rom? I did dirty flash since I moved to this should I try a clean flash

Sent from my sexy Android 4.3 thanks PWNCAKES
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I haven't noticed this at all, and I use Bluetooth a lot. My friend on the other hand did have this issue. I tried compiling some new builds for him but nothing solved the issue. Its probably a CM thing that'll get worked out sooner or later
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
I smell a new build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
Me to I'm smelling it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Never mind its my grandmas muffins. Lol. Just kidding. Nice work pwncakes. (:

Can't wait for more! (:

sent from my paranoid android powered s3!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
At the very least there will be a kernel update today. Does everyone want over clock and under clock back in? There's been some nice WiFi updates as well as removing some crud from cm10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
OC & UC sounds good to me. Whatever you can do man! (:

sent from my paranoid android powered s3!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rob_z11:
not if it breaks overall stability of the phone. May be one regular kernel with stock settings, and other is performance kernel with people who wants to tinker theirs with it to get overclocking or under clocking their heart desires. I personally desire rock solid stable kernel with optimum battery savings for my wife's phone. I am running AOSP on my note2 4.3 slimrom, and it has gotten to where I don't go back to Samsung stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Only if stability can be maintained, otherwise I say leave 'em out. Like others have said, I want stability and good battery life overall, and if that means sacrificing OC/UC and UV, I can live with that. (Perhaps you could release a separate, "performance" kernel that has these. Use the stable kernel in the ROM, and make the performance kernel a separate flashable package?)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] st0nez0r:
+1. I've been following this rom, but haven't flashed it yet due to the issues others are having. I like the above idea, and... stability/battery are far beyond more important to me than tinkering with clock speeds on my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Honestly it seems to have evened out, the reboots have seemed to disappear, I think a CAF merge fixed the SPC errors. But I'm working on a kernel now, drinking some beer after a horrid day of work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sledgeharvy:
As long as you keep "Fast Charge", I don't really care how much you over clock it.. Lol.. That's the only feature I NEED!! By the way, I love this ROM! Thanks Pwncakes!.. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibilln:
battery - eh...

1.35/test2. Pwn's suggested settings. Uses ~5%/hr not doing much - a call or two; some twitter; some Chome; some RSS. ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sledgeharvy:
Okay, so now I found an issue.. The Performance settings are not sticking.. Well.. Only the Processor speed is not sticking.. The rest are..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
I think pwns got a fix for it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Issues with this rom have been minimal. Don't be scared away because bug reports and issues get reported in this thread. Pancakes has been releasing stable builds and working through the bullish as fast as people find them. I wish the cm Devs were as structured in their builds.

---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Finally found a good medium between the kernel and everything. The new kerbelbwill include a decent amount of stuff again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Awesome! Looking forward to flashing it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
can't wait. (:

Sent From My SlimBean Powered SFree!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Here's a preview. I'll update this post with the kernel once I get it figured out.

QUANTUM KERNEL FINAL

Linaro 4.7.4 2013/09 Release (Just came out today)

Linux 3.4.62

Overclock/Underlock 270-1620

User Voltage Control

Faux Sound

Fastchare

Governors: Asswax, Intellidemand, SmartassH3, Badass, Smartmax

I/O: SIO, FIFO, TripnDroid

IN KERNEL MPDECISION FOR MORE RESPONSIVE TOUCH (DISABLE TOUCH BOOSTERS IN TRCKSTER)

Standalone Power Collapse

Updated Wifi Drivers

Disabled old crud from CM10 ( a reboot after install is nothing to worry about)

Touchscreen Optimizations

Get ready for one smoooooth kernel :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Very nice. You're going to have to collect a few volunteers to help you keep this going before work/school overwhelm your good intentions.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
Nice! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Newest kernel is unbelievably smooth. Get ready you guys.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sajoeee:
downloading and gonna try... (;

Sent From My SlimBean Powered SFree!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moz68:
I am not seeing Smartmax as a choice in govenors.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Well that's a derp on my part. I'll add it in in the next release, or just re upload one. Do you use smartmax?