yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maturola:
Home button

Ok so today my home button doesn't take me home anymore, but instead it open "recent app switcher"

I went to system settings, and check hardware key configuration and "enable custom action" is disable. I tried checking it in, and checking it out, reboot and nothing, anyone seen this?

Just checking before a do a new clean flash.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] detdett:
That's right

http://10.1.cmxlog.com/?device=d2att#next_build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ponty13:
I've noticed that after a while of using the phone the button and taps seem to "stick", essentially making every push/tap a long one. For example, hitting the home button brings up the task switcher; when trying to navigate the gallery, tapping a folder selects it instead of opens it. The only solution I've found so far is to reboot the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Goatblaster:
I know this isn't best practice (and I'll nandroid beforehand anyway of course!) but can I "upgrade" to this JB ROM / 7/16 GAPPS without a full wipe? I'm set up beautifully on last night's CM9, just wondering if the JB upgrade will bork my setup.

I'll titanium/etc. if I have to, just curious if anyone's done without full wipe from CM9 to this.

Tx in advance! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arcadia310:
Cool thanks man! Been wondering why the hell I couldn't boot into recovery, didn't know you also had to press the power button lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ssfirme:
Does anyone have the att pta apn settings
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
Back 1 page I posted my results doing this ..... but ya u can
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cjacks519:
I have at&t as well and my settings show this number for voicemail: +18325999998
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Goatblaster:
Much appreciated. Tx. <fires up TB and nandroid...>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
hmm, i got a install aborted code 7 or something. bad download? ugh... gotta try again with new download :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Goatblaster:
If it's that "error 7" thing, ensure you're running the latest CWM recovery. Just grab ROM Manager, update CWM and try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iBotPeaches:
Love you.

I wish my computer was faster -_- building started. Great to see JB out, kudos to all who were involved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Always... always wipe going from one ROM to another.. old firmware to a new firmware... old OS (4.0) to new OS (4.1). You can try without wiping but if you run into any problems, that is the first solution. Might as well start fresh imo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kevinl86:
Is there no toggle for percentage battery or am I just mental?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Goronok:
I'm amazed how great this is working with 7/16 jb gapps, camera fixes, and jb superuser patch.

Great work cyanogen, we definitely appreciate it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
No, this is basically an aosp build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Ok done, let me try now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Verified. I got off a call and noticed I still had lockscreen unlock sound but I couldn't play any music until I rebooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyped89:
I did, used the root fix, camera fix, etc. Everything working great except Google Now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brushrop03:
Blah. Still very impressed with this build. Are we going to have CM10 before the GNex? :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Very minor problem... I'm just ecstatic we have JB!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] w1nter456:
Does 64GB sdcard work with this rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iBotPeaches:
lol. Sorry to say, it already was reverted as it requires proper JB drivers.

http://r.cyanogenmod.com/#/c/19983/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lostsoul565:
have all the bugs been ironed out on this rom or is there still issues with anything? what is a good stable kernel that will go well with this rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwalbach:
http://xdaforums.com/showthread.php?t=1786503
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zeesubalpha:
from the sounds of things, i suggest you stay completely stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
mostly all bugs have been ironed out. i have been running this since the first nightly was released (~2 weeks) and i have not had any issues. i do get minor hick ups but i flashed kt747 kernal from ktoonsez and i really havent had any issues with that either. Ever since he introduced undervolting i think thats the only issue. i have had restarts because of it but fine tuning it a little more, its flawless. I have it oc to 1.8 and i have been still getting impressive battery life. Yesterday my screen time on was about 4 hours auto brightness, and i finished the day with still about 45% left. give it a try. like i said i use it as a daily driver
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Or just extract the MMS from the inverted gapps for task650s AOKP (they are on his goo dev site) rename stock mms.apk.bak and paste it into system apps reboot recovery and fix permissions (or use fix permissions app) I've not had that issue at all and I type extremely long texts as well..

Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
That ends up just splitting them up on my device. They then arrive split also. It should be fixed down the road, the question simply is just when. Though it could very unlikely be an issue in my market, but I doubt it. I will be heading off to the AT&T store later today to check. This issue did only pop up when I had installed CM9/10/AOKP so I don't think it would be a Network issue in my market.

EDIT: Added screenshot from my phone with testing of a phone in the store. Definitely not a network issue, my phone will rejoin long texts, but autosplits them when sending. If I use a software like DeskSMS or Airdroid and type out a text longer than 160 characters, it will never send out, it will appear like it did or error out. I did my testing while using CM9, which is my current Daily Driver since I need A2DP on a daily basis.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Moved to another world
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alirulzz:
if would a lot easier if you posted the link to the Q & A and this message in the first post that way all new users will HOPEFULLY direct there qs's there..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
While that is a great idea:good: and the rule of XDA, XDA is keenly aware that fewer and fewer people are reading OP's, or they read enough to be dangerous. Then they never go back to determine the why, where and how.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I'm getting very inconsistent behavior from the notification LED. With either the default or custom settings, the LED will activate for a brief (<5 seconds) period of time and then stop and repeat the cycle randomly until the screen is awakened and the notification cleared

Edit: Seems to be an issue only if blinking is configured. Always on works as expected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigmike34:
In Settings> System> Notification drawer I added a mobile data toggle to the power widget, but when I attempt to use the toggle I get an "Unfortunately, System UI has stopped" message.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madkapitolist:
Status 7 installation aborted error

Anyone have issues with status 7 install aborted errors from CWM? I have not had this problem with any of the other releases in this thread but I cannot install 7/23. I have the latest CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
Yeah for real. I'm fiending to flash lol

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
7/23 build I saw a 7/23 for cm9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
+1's = -1,000,000,000. So I would go with the first option dude.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madkapitolist:
My bad

Sorry had a brain fart, yes it was CM9.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatJawn:
Running into the weirdest bug. Honestly.

So, phone randomly drops signal. I then reboot it. When I reboot it. My phone gets all sorts of crazy.

It doesn't sync to google servers. And then the internal clock on it resets. And its always to January 24th 1970....I am utterly confused. I've been running it perfectly fine now since the 7/20 release and just today it did this when I rebooted it. I've reflashed it twice now and it fixes it maybe for a couple of hours but then to no avail, drops signal randomly then right back to never picking it up again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Moved again... it was time
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
Try pulling your battery and sim card for 5 min . Its Worth a try
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eAiur:
Yeah, that's been happening to me on the 23/02 nightly. Rebooting fixes it all the same
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Dude this has been discussed here numerous times and there is not a fix yet.

I havent posted here in a while because there is literally nothing in this thread worth discussing anymore. I make my own builds daily with my personal tweaks added in and i am content. Yes there are issues, no this is not the place to report them.

Seeing how there is a thread, conveniently titled, "CM 10.1 Bug and Issues Tracker" or something of similar nature posted in the General Discussion forum , Why don't we start posting bugs/issues/etc in THAT thread, and leave this one to development?

I mean come on. CM is OPEN SOURCE. so anyone and everyone here that run into these issues who are somewhat familiar with coding, developing, etc, try syncing up to their github and look into the issues yourself. Anyone can push changes for review, so i say we make this stop here by having this thread reserved for those actually working on cm/have questions about building/compiling their own builds, etc and take the bugs to the BUGS thread. Thanks. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lothos:
Has anyone done a search through the nightlies to find out when the behavior began? I would if I could get the nightlies from weeks ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
The home button issue happens at the same time as the AOSP keyboard's gesture trails "thinning". Pay attention to the gesture trails of the keyboard. Seems to me like it may be a general graphics bug or memory leak.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I've got everything back to January 21st 2013. Grab from the Dropbox folder below.

https://www.dropbox.com/sh/00ro80v3cuz7da8/PM1Ni-3WIg

https://www.dropbox.com/sh/q746bgbhn583jc2/W46PuPSNee
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kashpande:
https://jira.cyanogenmod.org/browse/CYAN-283
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
new nightlies don't show up in updater

Is everyone seeing the new nightlies from the built in update in CM?

There are many more nightlies on the build web site than show up on my phone. I'm at 0219 build.

EDIT:

DOH USER ERROR! it was set to check for stable. NM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ozzman54:
This bug has been reported and tracked for a few weeks now. As of this morning Cyanogen changed the status from Open to In Progress, so it's actively being worked on and hopefully will be fixed soon. Seeing as this is one of the most annoying bugs since it requires a daily restart, I'm very happy to see it being worked on! You can see it here: https://jira.cyanogenmod.org/browse/CYAN-283
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Yes i know that ticket was created on February 11th. It also has a comment from the creator of cyanogenmod at the bottom stating that he is working on the issue.

My point being, Jira is used to REPORT bugs officially to the CM development team for OFFICIAL releases ( pretty much anything not experimental or nightly) but this thread is NOT the place to DISCUSS the bugs. That is what the BUG thread is for.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
How come were not seeing any nightlies? Last one posted was 2.26.13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
sometimes builds fail..will have to wait for next nightly

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I think because they are preparing the release of M2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
Builds can fail for many different reasons. The D2ATT builds were one of few device builds that were succeeding for a few nights. Check this out, set yourself up and you won't have to wait. http://wiki.cyanogenmod.org/w/Build_for_d2att I personally run my Ubuntu machine in a Virtual Box.https://www.virtualbox.org/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
yeah I run Ubuntu in VM on my PC..but my PC is garbage lol.. eventually I may start trying to build..especially sense so many other users seem to be jumping into it here lately from what I have read

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
If u search u can build on windows also and it wont be as slow as vm :D just google around

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flashedmytiltblind:
Best. Nightly. Ever.

Fixed WPA supplicant for tethering!

Fixed alsa/orwhateverelse problems that was causing all Google Voice Visual Voicemail to be played back through the speaker!

Fixed a ton of other stuff judging by the changelog!

If any of the devs still read this thread: Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
that's the one complaint I have with running Ubuntu on a VM..how slow it is..I just assumed it was my PC though

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
Read the pile of posts on this issue a few pages back. Or just reboot daily for a temp fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stavrosg:
LTE tethering still broken, had to use the iptables script. Is this ever going to be included in the rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Got a incorrect script and did not get it working... can you share your iptables script?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stavrosg:
Try these
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I have two different i747s, and they have different vibration intensities and time when pressing keys like menu or back. I cannot find anywhere to adjust this vibration intensity/time. I thought it used to be under System settings > Advanced but it's no longer there now. Does anyone know if it was moved to some other menu or removed altogether? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] assaf.bm:
Go to Lang & Input --> Keyboard --> Adv. Settings --> Keypress vibration.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
That only changes the vibration time of keypresses in the keyboard. I am looking for settings that affects key presses like Menu and Back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
This depends on the kernel. The stock cm kernel doesn't come with the ability to modify this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I see. Then it's really strange that my 2 different i747s have different vibration times. Both are on stock cm10.1 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
If you are building in that environment, what sizes did you use for RAM and the virtual disk when setting up your VM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
How much do u have if u can go 60gb (this is wayy more than enough source is about 25) and go 4gb of ram and if u habe 16 then go 8;)

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] axiomjunglist:
Does anyone know what day the nightly switched over to 4.2.2? It broke PDANet but it was working in 4.2.1.

Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I'm not sure specifically when they switched but I think I know what the issue is. Android 4.2.2 requires ADB to authenticate itself with a hash and a confirmation on the phone. If you have an old version of ADB installed, this handshake isn't being sent. Try updating your SDK tools install. I don't know for sure if this will fix the PDAnet issue, but once I did this on my systems, PDAnet was at least aware of the device. There might still be routing issues if you actually try to use PDAnet for internet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pbwizkid:
Any one played with newest nightly yet? If so how's it doing I am on the edge of updating any time soon my current one seems to be really stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Not the place for these questions. That said, make a nandroid, flash the nightly and decide for yourself. If you don't like it, restore the old one.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
Bluetooth phone calls are static in my car
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Has anyone had the issue where GPS keeps running randomly and either won't connect or reconnects lots? I've cleared my Google framework cache. Unfortunately the one nandroid I have experiences the same issue. Any advice is welcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
How does this work? Is it as simple as running the script (as root?) and using built in wifi thethering?

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
Is anyone experiencing a broken brightness tile in quick settings? The bar comes up but doesn't change when sliding

Sent from my I747 running cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
What nightly are you on? I saw something related to brightness tiles in the change log for today's nightly... You might try an update and see if that fixes your issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
http://review.cyanogenmod.org/#/c/33067/

Update to the latest nightly.

Also, review the change log if you have these questions. http://mobile.10.1.cmxlog.com/?device=d2att :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
3/02 nightly is working perfectly for anyone wondering. No crt freeze, smooth as can be and all that jazz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
For some reason 12/16 comes to mind. It's around there, or one of the builds just before Christmas.

SlimBean 4.2.2 with BMS kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
I was on 0302 updated to today's and it works fine. Thanks for your input, much appreciated

Sent from my I747 running cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
This from a repo sync I did just now:

project .repo/manifests/
Updating 38fd77b..7dd0579
Fast-forward
cm-10.1-M2.xml | 377 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 377 insertions(+)
create mode 100644 cm-10.1-M2.xml
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
Have you guys seen this before.

100% clean install and the system is using 7gb
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Should we be using the new 20130301 gapps, since they have updated to 4.2.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
This isnt correct it seems lol... What app is tht?

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Yeah, 20130301 is for 4.2.2+ per their gapps changelog. It nukes redundant apps now in the market, and updates stuff locally (like google services) so we don't have to waste time & bandwidth doing the update post-rom-install.

No need to install it now, though - just wait until your next clean install...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
This is definitely not right. System should be down around 300MB. You need to reformat you SD card.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ouija147:
That app is Diskusage, great app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Try using es file explorer to see the size of ur system folder ill dl the app right now

Mine shows no such issue however i dont see the usefulness of the app really lol but whatever suits...

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
Have you done any backups?

Sent from my I747 running cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
Is there anything broken on aosp 4.2.2 roms? Seems like they fixed all the major things like wifi tether and bluetooth
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
There's an experimental m2 build that what was just posted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Nothing broken anymore... it's' all good!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stedean:
I have been using the last monthly build, so I'm curious to try this out. I have been having some bluetooth issues.

Don't forget about the new gapps that were just posted as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pbwizkid:
Forgive me for my newb question here, what are the experimental releases?. I am assuming they have a major change?? and what the M1 or M2 mean?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
M releases are basically considered mostly stable and good to go for daily stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jridda10121:
What New gaps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
check goo for new gapps package
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm running the new experimental build

Seems to be working fine. Basically seems same as last nightly despite the 20 page changelog. Not sure what is going on there. It seems like too many items for a nightly!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
The changelog of M2 is long probably because it is showing changes compared to M1. Compared to 3/3, there isn't much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirGeraint:
Is MMS (with the stock app) working as well? I can't send nor receive MMS. It has been broken for me for a long time. I have been waiting patiently.

I just tried with the M2 ROM, gapps 2013-03-01. I checked my APN settings. I searched this thread for "MMS". But didn't find a fix.

When I send an MMS it stays on "SENDING" indefinitely. When someone sends me an MMS sometimes I get a notification that the message cannot be downloaded and to try again.

When I googled I saw some instructions for downloading/installing a MMS.apk. Is that necessary?

Thanks...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
m2 beta - warp-o-vision is gone!

I'm happy to report that warp-o-vision video recording is now gone in 720p mode!

(That was a 3 month bag of suck!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
stavrosg, the enable script worked great. However, I got error message after executed lte-iptables-off.sh.

Now, running into another issue. I was trying to place the script under /sbin (or even /). I noticed that after I rebooted the phone, script got deleted. Did I have to place it in some folder so that the phone will not delete it every time it reboots?