yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Ktoonsez said it was for people experiencing wifi problems. If you're not, there's nothing to do. If you are, then you could tweak to see if it helped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Not exactly as always.

There is no mention of people having problems -thats one. Two that was not my question. Three this is coming from s4 drivers and features so the question is to people who played with the settings and not someone who has not. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
There has already been discussion on this matter just not on THIS thread just yet.

Read through here. Should give some clarity.

http://xdaforums.com/showthread.php?p=42385734

http://xdaforums.com/showthread.php?p=42387434
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
That's exactly the info I was looking for. Got to monitor S4 thread now :). Thanks dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Very nice

Everything sweet so far even Bluetooth!

thanks again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
random power off

Thanks for the great work KT! Newest kernel is running very smooth. Just wanted to report a random power off while the screen was off after listening to Doubletwist player. I'm running your settings, except I have stock voltages and on Tasks latest (6.7)

I've since set 'screen off profile mhz' = selected scaling max and returned 'sampling_rate_screen_off' = 45000 to see if it happens again.

Attached is my last_kmsg. Keep up the great work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I've gotten a couple reboots as well. Both while listening to music with GPS enabled. It looks like it may have something to do with the modem, but everything was fine running the kernel that came with task's latest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
My phone sucks and I've had

no issues try his kernel with this Rom

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

Imo it's a flawless combo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krufttangoud:
Weird issue can't tell if it is ROM or kernel

I am posting this in here and AOKP to see if anyone else has had this issue...I was never able to get back to the operating system after the incident so I dont have any data to provide...so that means I can't tell if it is Kernel or ROM or Recovery related,.

So I have been running the AOKP nightlies in Goo and Ktoons kernel. This has been a very trouble free combo. However, out of nowhere I go to reboot in recovery and it takes a dump. Mind you its been running fine all weekend. It will get right to the Teamwin splash and start boot looping. All I did was reboot. Recovery is now broken, so I odin CWM on and that gets me back to a recovery, but when I try to flash TWRP again same issue. So I put CWM back on, factory reset, reflash, wipe everything, sticks on boot splash on every build. Finally, I gave up flashed back to stock, and re-rooted....lost all my stuff on the internal card but I was able to re-install TWRP and restore my backup.

This is so very random and frustrating...it just randomly for no reason stopped booting to recovery. Anyone had this same experience?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reflectingod96:
i'm using Task's Aokp + kt747

updated both yesterday

wiped everything, flashed, rom, booted in rom, reboot recovery, flash gapp+ kt747,wipe cache/dalvik+ fix Permissions, everything went well....

restore all my TiBu backups. phone randomly reboot about ten minutes after that. phones get stuck forever at kt747 splashscreen needed to full wipe and reinstall my rom, i did not try again to reinstall kt747 :( i missed it already but i guess i'll wait for next release. there is probably something wrong in this one...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Your was the modem crash thing that has been posted a bunch of times, no way to fix it that I know of :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, thats a good one. Your ROM executed a reboot behind your back, very last line in the last_kmsg:

[ 3078.686219] Restarting system with command 'recovery'.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] martinomac:
haha, that's too funny - I guess it wasn't feeling the love of the tunes I was listening. Thanks KT
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
Did you post the last_kmsg from your phone? If so how did you do it?

Carbon v1.7 & lk v6.3 that's Blacked Out!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I think I found a small typo in asswax tunables. Sleep_wakeup_freq says 151200 instead of 1512000.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CrackerTeg:
In KTweaker, there's an option to generate it under the extras section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Yes, I did. How did I get the last_kmsg? It's in /proc on the internal sd card. I copied it to my ext sd card and then emailed it to myself. For some reason it won't let me email it directly from /proc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
I have to put it in a zip file "last_kmsg" and email it to myself. But I still can't post the file from my phone. Even from the web browser. I can only get it to post on my PC.

Carbon v1.7 & lk v6.3 that's Blacked Out!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Just add a .txt extension and you should be good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Had a random reboot while connected to Bluetooth sync in my car
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seko666:
Still doesn't work with .txt added..

Carbon v1.7 & lk v6.3 that's Blacked Out!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Well then you're doing something wrong cuz valid file extensions when posting attachments include 7z, apk, bmp, bz2, c, cab, cab2, diff, doc, docx, gif, gz, h, img, jar, jpe, jpeg, jpg, jps, mtz, patch, pdf, png, psd, rar, tar, torrent, txt, wma, xap, xls, xlsx, and zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If someone wants to try asswax or conservative as governor on cpu1, I would like some feedbacks.

Go here for more explanations: http://xdaforums.com/showthread.php?p=42445903

Thanks!:beer:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
I'm feeling good about this :] That's using the same settings as KT, on ReVolt with a Hyperion 4200 mAh :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So I have seen it mentioned throughout this thread that the Wi-Fi drivers included with his kernel aren't necessarily replaced when I flash other ROMs or Kernels. Since I have been experimenting with other kernels as of late, does that mean I still have the KT Wi-Fi drivers from the last time I flashed it?

I have been trying out LeanKernel for a while on CM 10.1 RC5. Would the Wi-Fi drivers from my previous install of KT's kernel still be on there?

I ask because I have had some issues with my data connection dropping out as soon as I disable my Wi-Fi when I leave my house, and I was wondering whether I had the stock or KT Wi-Fi drivers on here before I started troubleshooting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
The WiFi fix is included in all popular latest kernel including latest lean kernel and ktoonz(the great).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
The fix? Was my problem a known issue with the KT Wi-Fi drivers before?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
I was just going to post about this. I was reading about it a few months ago but what stopped me was the drivers thing I read.

I recall something along the lines that simply flashing another kernel wouldnt work and you need to install the driver as well.

I have the following kernel for stock TW JB 4.1.1

3.0.31-538866

se.infra@SEP-106#1

What driver would I need to DL (and where would I find it) incase I want to revert back to this kernel, or try other kernels?

I want to do my research before flashing this kernel so I can jump around to other kernels without an issue.

Also....i can't quite recall, why was the driver updated? Using my stock kernel, im assuming the driver is an older version. I dont think i've experienced any issues with it yet....

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
Has anyone tried the 613 cm build with this kernel? The only reason I ask is the change log from cm updater says "this is the first cyanogenmod build of this type for device d2att"

But I have not found any details on it yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Where do you see that? I'm using the kernel with 6/13 just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phantomofheat:
When I go to settings>about phone> update then update and click on the name of the nightly it displays the changes.

It's good to know that it works though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I think I've seen that in the past. I'm pretty sure it's just a typo(that probably shows up when there's no changelog). I think it means that it is the first release of CM10.1 for this phone(remember, these are pre-release nightlies for the initial release). It is written with the knowledge that there may be a CM10.1.1(like there was a CM7.1 and CM7.2).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] paluinfusion:
Can I flash this kernel on top of task AOKP ROM (6-7 build). Will there be any advantage/compatible ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmccool80:
Yes you can. Make sure to get the Linux 3.4 aosp version. Whether there is any advantage will depend on your phone/usage/settings. Only way to know is to try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Hey, please don't double post.

[MENTION=4325945]ktoonsez[/MENTION] if you're free can we get a definitive explanation on this?

Sent from a Galaxy far far away...

---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------

Yes guys, please go try fooling with the cpu1 settings. We need people to test this! :)

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
The issue really doesnt exist anymore. In the first 3 onths or so there were many, many n00bs making ROMs and kernels and were not providing the drivers for there stuff (basicaly an incomplete zip file) so when someone went and flashed another kernel or ROM with a kernel, my drivers remained so the phone would not boot. The updated drivers were mainly the wifi and bluetooth ones.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
hey thanks for the reply.

so basically speaking.......if i flashed your kernel and wanted to revert back to my old one via a nandroid. I can with no issues?

I'm running a stock tw 4.1.1 with

kernel

3.0.31-538866

se.infra@SEP-106#1

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alacrify:
Restoring a nandroid will always get you back to square one ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
anyone know why the sampling rate gets set to 10000 on its own on ktoonservative governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
KT

Is there any tunables available on WiFi driver to get better WiFi signal connection? I'm seeing crappy WiFi inside my house where other devices including my N10 have excellent signal strength.

Not sure if the s4 drivers that were added helped/hurt/didn't do jack. Or am I SOL with s3 hardware?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Try a different congestion control under the extras section in Ktweaker and see if it makes a difference.

---------- Post added at 12:38 AM ---------- Previous post was at 12:35 AM ----------

I basically told you the same thing on my thread but you just got confirmation on this matter by [MENTION=4325945]ktoonsez[/MENTION] himself so don't sweat it. You're good bro.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Yep I tried reno for a while and do not see any difference in signal strength at all :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Hahaha baconator and me gave him the same confirmation in my thread :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Nothing wrong with being EXTRA careful. Hehhe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Signal strength is always hardware, cant make the hardware signal get stronger with software :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Dang :(

Is it better on S4? :)))
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I think its the same as far as signal strength (I.E. distance), but has a much better piece of hardware in it for boost. Tonight for example, there was an update for my CM Theme that was 23MB, took about 3 seconds to download it :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
Thanks, I just wanted to confirm because i thought i read that even a nandroid would not restore the driver.

Thanks again, wanted to be safe than sorry :P, just a bit cautious when i read
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
What exactly does the read-ahead buffer do and has anybody noticed a difference when using it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BTT8:
Would also like to know this as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shels:
Is anyone else experiencing wifi issues flashing the latest tw kernel with any of the tw roms like goodness rebuilt, etc.? After flashing kt everything works fine but wifi, however flash another kernel and the problems gone. Of course the simple fix would be to use the other kernels but ive always been a kt type of guy. Help me out pls guys

Oh n fyi the problem has been there since the beginning of the month I was just using other kernels but I can't take em no more I need my kt

Update: it's working on hyperdrive but when I flash the tk mod something goes off again I'm thinking when I do the build prop tweaks might conflict with ones the author already implements just a theory but all I got and I know wrong forum since I use tk mod too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Not me. I have AOSP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Ktoonsez is also my type of guy :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Ktoonsez for the win! :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Cache size for io reads, they say for peak io performance 2048 works best

Source: http://xdaforums.com/showthread.php?t=1010807
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] androidGuy302:
screen not working after install

Aokp 4.2.2 mr1, d2att, clockworkmod- when ever i boot up there will be nothing on the screen although the phone still senses touches

-thank you for reading this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oddspec:
Not sure what kernel mr1 uses but make sure u download the rite version of this kernel to match ur ROM 3.0 3.4 etc also there was some display changes made to kernels around 5/19 i wanna say which sounds like the issue u r having try the correct kernel version an old one before 5/19 and see if that works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
think you're referring to the CM display drivers made on 4/19. Nonetheless, you are correct on which builds he should be using depending on which MR1 build he's on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Working perfect for me, especially since all my S3 does is wifi now that its deactivated from AT&T.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Same here Wi-Fi at home, the gym, and work and it works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
How's the S4, toons? Worth the early upgrade?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Please help! Before installing KT747, I had 4 out of 4 bars. Now I have 2 out of 4! Please help! I have also noticed that my battery life is worse after getting this, please fix the signal.

---------- Post added at 05:09 PM ---------- Previous post was at 05:04 PM ----------

Got 4 bars again. :D. I'll see if that was just a temporary glitch. If not, i'll report back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Signal strength has NOTHING to do with the kernel, that is purely hardware, no software can control your signal strength.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
I think so, if you can get it for 350 or below, dont go 400-600, Id wait if they r gonna rob you for that much
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
For those running AOSP ROMs, what improvements have you noticed? Is it noticeably faster? How does battery life compare?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Guys are getting 5-7 hours screen on and it is quite a bit faster when doing multiple things since there is 4 cores instead of only 2. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
I wish your kernels gave us s3 people 4 cores... :)

What do you mean the aosp roms give the s4 4 cores? Are there two cores turned off for the stupid LTE issue? that's nuts.

that's like when AMD would make 6 core's and if one or two were bad they would disable them and make it into a 3 or 4 core, people could unlock them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Lol, I was comparing the S3 2 core to the S4 4 core.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
lmao.. this made my day!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Ikr

If it's speed that your concerned about, you can always OC. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
What is "nightmere" governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
naw, I don't need the speed, AOSP with ktoonsez making kernels doesn't need a 1.5ghz dual core. nowadays i'm underclocking and de-tuning cpu1. Now my car on the other hand... that's where I pour on the speed like gravey, but that's not on topic.

I thought it was nightmare governor, perhaps it's a typo or something?

eitherway it's still just one of the many governors. there's a xda post with all the governors and information about each one somewhere, like right here http://xdaforums.com/showthread.php?t=2017715
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
This may be a slightly better source for you on governors and I/O schedulers

http://rootzwiki.com/topic/40336-cpu-governors-explained/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
It does not have nightmare. Is nightmare the same as "Scary" or is it a new version?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
The only thing of value I stumbled across on the subject of the nightmare governor is that it is based on Pegasusq with battery optimizations. Hope that helps..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Woops. Guess I sent you the wrong link. Anyways, the nightmare governor is a blend between ondemand and pegasusq. Think of it as ondemand but with lots more options. It's very similar to the SLP governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
So it is good for battery life and performance?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Well pegasusq is also based off ondemand but with integrated hotplugging and with that said, nightmare is a tad bit more on the performance side but is intended to serve as a balance between performance and battery saver but don't expect the greatest battery life out of this one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
You should come hang out here if you're wanting help getting battery life and good settings http://xdaforums.com/showthread.php?t=1886233
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juancollado2003:
ntfs

anybody has the KT747-Kernel-AOSP-JB-ATT-NTFS-TEST.zip?, the link is dead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
May I ask why you're looking for that specific test build? It's not needed anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juancollado2003:
I have an a AT&T i747, and can't read files on my ntfs hdd in aosp roms, just on TW roms, I tried the last built of KT747 and it sees the hdd connected but didn't mount it, using paragon I mount the hdd but can't see the files

----------

Solved

______

Looks usb otg helper solved my problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
I believe it's because those will only mount as read-only on the phone. Try reformatting it to FAT32 and see if it helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
[MENTION=4325945]ktoonsez[/MENTION], can you take a look at this log cat? I tried the slim thread but I was recommended to ask here

I had some amazingly bad behaviour that I've never seen before. I had an incredibly long screen lockup, it would last for about 3-5 minutes of un responsiveness until the lock screen would finally engage. And then it would run normal for about thirty seconds then lockup again. I don't think it was an app issue cause it didn't matter what app I used.

I rebooted a couple times but that didn't make a difference.

In recovery I wiped the caches and fixed the permissions and I haven't seen it since.

I know you normally like the last.kswhateverthehellit'scalled but I was barely able to get catlog to save the log cat.

I'd love it if you could take a look, thanks so much

http://db.tt/2x2vl4EN

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Sorry but the logcat is for ROM stuff, so it didnt tell me anything, I needed the last_kmsg after a reboot if it did reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Hey ktoonsez! I've been messing a lot with cpu1 governor lately. Right now I use ktoonservative on cpu0 and asswax on cpu1 and it is working like a charm. And I was wondering if it would be possible to add different freq step for ramping up and ramping down, like the ramp up step and ramp down step in asswax. I'm just asking because I really like ktoonservative but I would also like to be able to make it ramp up slowly but ramp down faster.

Thanks for your work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
They are called:

freq_step for up

sampling_down_factor for down
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I thought Sampling down factor was to control the rate at which the kernel reevaluate the load to decide if it it ramp down. What I was thinking is more like by how many freq it will ramp down when the kernel makes the cpu ramp down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
In that case, no I can't it can only be one way or the other and I like the way it is :D :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
I've been getting a fair number of modem-based reboots lately and it only seems to happen when actively using GPS. Has anyone else experienced this or does anyone have any idea why GPS might be causing problems for the modem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
I am also getting these. I tried raising the voltage and changing the gps settings in ktweaker. Mine are relatively infrequent, though, and only happen when I'm listening to Spotify.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Try reflashing the kernel and inputting your settings manually.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
I also already tried that. It's not a prohibitive issue for me so I'll just use Underwear for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Actually, I just discovered that I get this with both kt747 and Underwear. Like you, it happens when listening to audio while using GPS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drthedoctor:
It also happens with underwear but it's more infrequent for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sargon151:
Don't like it too much the way it is. We want new builds :victory: