yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I don't have any proxy set up. But I do have adblocking. The thing is this issue happens on a clean install of the recent nightlies but not on cm11 m2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah that's really curious. :S
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I'm assuming you aren't getting this problem.??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
The Bluesleep issue looks like it was fixed in 02/07 Nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Wait what nightly are you on? This is related to alarmtimer stuff. Update to a newer nighlty or use a different kernel that is built past the end of january
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I am not currently on CM but I test drive a nightly every week or so just to keep up with things. Use it for a day, then go back to my setup. :)

But no, I did not get any issue like this any time, including less than a week ago.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Looks like it's still not working (Am using last nights 2/7 - the entry I thought would fix it is this).

http://review.cyanogenmod.org/#/c/59253/

It works with BMS kernel from 12/09 which I was recommended somewhere.

I had the same issue with Quantum and Liquid Smooth this last week. (Although only tried the BMS kernel on the CM Nightly from 2/6).

Have been switching between S3R and a 4.4.2 Rom for the last month but kept going back to 4.3 due to Bluetooth issues. Those issues then worked these last few days, but at the expense of a Bluesleep wakelock. Last night was pretty good with the odler BMS kernel.

Thanks Pwn..

Rob
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
After more... testing... I think its a problem with my phone. I dunno how it could only be me, unless its hardware issue, but yeah. Flashing back to M2 again and the issue is still present, so my initial observations were incorrect. I'm running into a lot of issues that I cannot seem to fix and no one or very few people are experiencing it. My phone runs perfectly fine otherwise but the black screen in chrome really bugs me. I think I'm going to jump ship to nexus phone when I'm up for an upgrade but thats not for another year. JUST KILL ME NOW hahah

Thanks for your help though, maybe some how it will magically work again like it magically stopped.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That would be a very strange issue. Before calling it broken, there's always restoring to TouchWiz to see if the problems still occur.

What are your other problems?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] roey1:
Hey ,

The CM 10.2 Rom is support of Hebrew language?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
- I have cache corruption issues that only affects my recovery. (Doesnt happen in TouchWiz but CM for sure)

- Slow WiFi. After a random amount of time my wifi download speeds gets throttled to a set amount between 3 and 6 mbps untill I reconnect to wifi. (Also doesnt happen in TouchWiz)

and now this. (I haven't tried yet cause im tired of flashing back to touchwiz, I think ive done it like 10 or more times in the last two weeks)

None of these issues seems to be prevalent cause no one is really reporting or even noticing them. I really don't want to go to touchwiz cuase I HATE it... but I have so many issues that only affect my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Have you tried checking for bad blocks?

Not saying that is, but a scan takes less than 10 minutes overall.

http://xdaforums.com/showpost.php?p=49503153&postcount=9423
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
I updated to the 2/6 nightly & no longer need to toggle bluetooth on & off to get it to connect to my car stereo (phone only, I don't let it connect bluetooth audio). It was working previously , I just had to toggle bluetooth off then back on to get it to connect. At any rate its working properly now.

I'm still having issues with the GPS in the past few nightlies I've tried over the past week or 2. Frequently I have to reboot the phone to get a fix for navigation. The phone ends up rebooting after running Google maps/navigation or Waze after running for 10-20 minutes. I think it's overheating. It's been doing this for at least a few weeks & I think started after I jumped from 10.2 to the 11 nightlies, even after a full wipe. Anybody else having GPS issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Thanks~ I just tried this but no bad blocks. I was actually hoping that there were cause then I would have a solution to my problems... but nope. Thanks for trying to help me out~
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Epikarus, it sounds like you should just use Chrome stable and just deal with the black screen for now. That's what I'm doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Bluetooth still not working properly for me on 02/08 even though I see the commit on 02/06 that should have fixed it. Back to 01/18 I go...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nahrah:
Working fine for me. Was using my BT headset all day at work then connected to car fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
It doesn't seem to like my Pebble. Maybe I'll try again tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
GPS issues here as well, just came to the forum to find out whats going on. Hoping it gets fixed soon!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
No GPS issues here. Using Maps on latest nightly and latest modem w/ leaked 4.3 bootloader.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Having camera issues on last few nightlies (Vanir)... anyone with plain CM11 seeing it? Freezing after 1 photo, have to reboot and keeps happening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
There have been some new camera related merges. For me, the camera app will crash if I enable the "Power shutter" feature, and give me the message "Unfortunately, Camera has stopped". I had to clear data on the camera app, and a reboot to get it working again. Note that I am running on ART, not sure if it affects it. You should try clearing data on the camera app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
When I had GPS issues, I installed an app called GPS Status, selected tools, and reset and downloaded A-GPS data. That worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rsanchez:
Had same issues with the Camera. Followed your recommendation to clear data on camera app and been fine since then. Running 2/8 nightly now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Anyone still having that lag that was present on the previous 4.4 nightlies when you click on app to open it, the white glow engulfs the app, and THEN it opens? It's extremely annoying and makes the entire user experience feel very slow for fast users like myself...

I went back to 4.3 because that lag is not present.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Are you having this issue as well?

I was looking through the app review for chrome beta and I found one person with this SSL error as well. Maybe its not just me?

Also I flashed to 4.3 touchwiz and Chrome beta issue still exists. Very odd [MENTION=268754]___[/MENTION]@/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] km00000:
My friend has a At&t version of the GS3. A SGH-I747. Should he install d2tmo or d2att?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
No, I haven't seen any SSL errors, just the black screen. Have never tried Chrome beta.

---------- Post added at 11:14 PM ---------- Previous post was at 11:13 PM ----------

d2att, not sure why you asked. Even if he wants to use a T-mobile SIM he needs a d2att ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] km00000:
Just wanted to make sure... Maybe the T-Mobile version would get him better service or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
That statement is incorrect. He can use many tmo Roms. Hey needs an att boot loader and modem. But he can use tmo Roms. That said there is likely no point in doing that for the most part as functionality is the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Right, haven't heard anyone on AT&T suggest that it's worth the hassle to use a T-Mobile ROM. I am using a d2att CM ROM on my phone even though I now use T-Mobile service.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yeah why the hell someone would do they in the first place...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Snapshot M3 is out for those who are interested. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skdi:
Hey has anyone had issues installing the latest night lies of cm11? It keeps flashing half way through and then failing. It reboots too quickly to see what the error is but I think I saw build. Prop or something. I tried looking through this forum but can't find anything. Is there a brand new bootloader or something? Any help would be greatly appreciated, thank you in advance!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Are you using the CM updater? Try to flash it manually by rebooting to the recovery and flashing it that way, then you should be able to see the error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skdi:
Thanks that's helpful. Yeah it says fail to get prop bootloader and it lists several bootloader, apparently it doesn't support ucuemjb anymore? Is it possible to just flash the leaked mj2 bootloader without going back to stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I just checked, here's the update script and supported bootloader

assert(getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747UCUEMJ2" ||
getprop("ro.bootloader") == "I747UCUEMJB" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MVLUEMK5")

DO NOT go back to a previous bootloader. Ever.

You error would lie somewhere else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skdi:
That's basically the error I get but it doesn't list JB.... That's really weird. Do you know if you can just flash mj2 over JB without having to go back to stock? I believe all the other bootloader are downgrades so I don't know what else to do. What bootloader are you on? Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I use a Canadian phone, bootloaders are not cross compatible. Once again, DO NOT try to downgrade your bootloader.

What zip are you trying to flash, what is the exact name? This was taken from cm-11-20140210-NIGHTLY-d2att.zip just when I posted it. You can open the zip with most file managers and look for update-script in the directory META-INF/com/google/android, you will see the support bootloaders.

Also, double check the current bootloader you have, just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skdi:
I'm not trying to downgrade mj2 is an upgrade, I'm just worried about flashing it without reverting to stock since it's a leaked version
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
MJ2 is a downgrade from MJB, MJ2 was the leaked bootloader AFAIK.

There's no reason to try a bootloader upgrade downgrade switcharoo if you're on MJB. MJB is supported, check that it's in the update-script like it should be.

Still, I'm warning you, if you go with a flash you'll likely get a shiny plastic brick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skdi:
Your bootloader aint supported son

Yeah, I'm not sure about that it looks like a lot of people are using MJ2 recently but you're right it's probably not worth it. I figured out what the problem was though, so I almost always flash the same modem/bootloader so I can check the version in settings but I checked the bootloader version anyways and it wasn't supported durp ><. Thanks for your help though man.

<<<Solution>>> In case anyone has similar issues and finds this, the first thing you should do is double check your bootloader version

To check use the adb command: adb bugreport | find "bootloader"

If your bootloader version is not one of the ones Polobunny listed above, here are the new supported bootloaders: http://xdaforums.com/showthread.php?t=2321310
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Stop being stubborn, MJB is the latest bootloader. MJ2 was the leaked bootloader for 4.3 that didn't have an eFuse. They're running it because it's the latest WITHOUT eFuse, while MJB is the LATEST PERIOD.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
So which bootloader did you have on your device?

People use the MJ2 bootloader (leaked 4.3) because if they didn't update to the MJB (official for 4.3) it doesn't trigger the efuse so you can technically roll back to previous bootloaders and/or stock roms. If you have already flashed MJB then going back is a no-no.

Edit: damn ninja pwn! :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Skdi:
Hey, no need to be rude man, I didn't know that.

And polo, I was on UCDLK3, and I decided to go with MG2 since I wasn't sure about the MJ's. And thanks for all the info I appreciate it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Great, glad you got it sorted. It's all a bit confusing sometimes. @_@
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
My spider sense is tingling.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Lol thought something wasn't working but got it to...

Something that's really annoying on CM11 ever since the beginning I think is when I restart my phone, it defaults back to LTE on startup. I have to go into the settings and turn it off manually. I made a toggle in the notification bar and it doesn't work...hit it and nothing happens. :crying: Been like this for a long time now on all nightlies...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
This is the latest firmware CM wants installed especially if you plan to submit tickets on jira: http://invisiblek.org/d2firmware.html

I'm considering going to the CM11 M3 release from CM 10.2.1. can someone give me the upgrade path? i don't see an CM 11 kitkat gapps listed here: http://goo.im/gapps ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I just upgraded CM10.2 to CM11 and I used ParanoidAndroid's GAPPS (what a lot of people are using).

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

I chose the "full modular package" because I wanted to keep the CM Launcher.

Works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I would like to know your experience if you do. I had to go from cm11 to 10.2.x as I couldn't take the lag, battery life, random boots(also in 102.x though), and lastly and maybe personally the most important, the unusable Bluetooth with Ford sync(with touchscreen). I know sync is partial to blame but it works very well with any other Bluetooth source.

I'm eager for 11 to be daily driver ready because I prefer it on my other androids.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
I think M3 breaks LTE tethering. Can anyone on Rogers or Fido confirm. I flashed back to 2/7 and its working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Got my first random reboot on 10.2.1 where i'm running the firmware they want. jira report logged here if anyone else is getting it and has log files and correct versions loaded on their phone.

https://jira.cyanogenmod.org/browse/CYAN-3440
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
I have to say my thoughts were like yours on the lag note for CM11 compared to 10.2...I just upgraded to 02/10 yesterday and have to say I was presently surprised that the lag is almost 100% gone and now that I've turned on ART the phone is even faster than it was on 10.2.

I know people say ART is placebo but I can assure you I notice a difference especially going back back back through an app (if you know what I mean).

I can't speak on the subject of Bluetooth because I don't use it...but I'm sure it's been fixed by now considering I don't see a lot of people complaining it's not working.

I didn't get the M3 because 2/10 has even more updates...

I suggest you do a backup and try 02/10 out...if you don't like it just restore.

Elliott

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Looks like trouble writing to userdata (p15, which is mounted as userdata). I'm not sure this would be entirely CM fault...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Hey! I'm stubborn! :p In the OP it states that you can't downgrade (got that) once you go to MJB nor can you use an odin tar. Is that in reference only to trying to revert to an earlier bootloader .tar? Sometimes I've really honked things up and needed to odin back to a stock config to straighten everything out - but if I'm reading it correctly, there's no way to get a 'stock-ish' refreshing after going to MJB?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
This one? pa_gapps-modular-full-4.4.2-20140207-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Yes.

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Stock MJB is always a possibility...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You can't ODIN anything that contains a previous bootloader. If your zip contains one, you'll brick your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Bootloader, 10.2.1 -> 11, TWRP 2.6.3.1

I'm trying to go from 10.2.1 to CM 11 2/11 nightly.

My baseband is I747UCUEMJB. I'm on TWRP 2.6.3.1

I'm getting the assert error about updating though. Should this work for MJB bootloader?

I:Zip contains SELinux file_contexts file in its root. Extracting to /file_contexts
script aborted: assert failed: getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747UCUEMJ2" ||
getprop("ro.bootloader") == "I747UCUEMJB" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MVLUEMK5"
assert failed: getprop("ro.bootloader") == "I747UCDMG2" || getprop("ro.bootloader") == "I747UCUEMJ2" || getprop("ro.boot
loader") == "I747UCUEMJB" || getprop("ro.bootloader") == "I747MVLDMF1" || getprop("ro.bootloader") == "I747MVLUEMK5"
E:Error executing updater binary in zip '/external_sd/Download/cm-11-20140211-NIGHTLY-d2att.zip'
Error flashing zip '/external_sd/Download/cm-11-20140211-NIGHTLY-d2att.zip'

---

I've got some terminology mixed up. Man, this is confusing. Looks like my bootloader is actually I747UCDLK3 ?

adb bugreport | find "bootloader"
Command line: androidboot.hardware=qcom user_debug=31 zcache sec_log=0x80000@0x88d00008 sec_dbg=0x40000@0x88d90004 sec_debug.reset_r
eason=0x1a2b3c00 etb_buf=0x4000@0x8fffb9c0 androidboot.debug_level=0x4f4c sec_debug.enable=0 sec_debug.enable_user=0 androidboot.cp_
debug_level=0x55FF sec_debug.enable_cp_debug=0 cordon=c5390215cde68ef3a338812ba7a5b572 sysscope=0xee000000 loglevel=4 samsung.hardwa
re=SGH-I747 androidboot.emmc_checksum=3 androidboot.bootloader=I747UCDLK3 androidboot.nvdata_backup=0 androidboot.boot_recovery=0 an
droidboot.batt_check_recovery=0 level=0x574f4c44 sec_pvs=0 androidboot.emmc=true androidboot.serialno=af0362b1 androidboot.baseband=
msm
<5>[ 0.000000] Kernel command line: androidboot.hardware=qcom user_debug=31 zcache sec_log=0x80000@0x88d00008 sec_dbg=0x40000@0x8
8d90004 sec_debug.reset_reason=0x1a2b3c00 etb_buf=0x4000@0x8fffb9c0 androidboot.debug_level=0x4f4c sec_debug.enable=0 sec_debug.enab
le_user=0 androidboot.cp_debug_level=0x55FF sec_debug.enable_cp_debug=0 cordon=c5390215cde68ef3a338812ba7a5b572 sysscope=0xee000000
loglevel=4 samsung.hardware=SGH-I747 androidboot.emmc_checksum=3 androidboot.bootloader=I747UCDLK3 androidboot.nvdata_backup=0 andro
idboot.boot_recovery=0 androidboot.batt_check_recovery=0 level=0x574f4c44 sec_pvs=0 androidboot.emmc=true androidboot.serialno=af036
2b1 androidboot.baseband=msm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Browser.apk from CM10.2.1

Yes. The easiest way is to boot in download mode and check your bootloader there, if you want to be 101% sure. Baseband is not bootloader, that's modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Extremely weird. I was 90% sure I had already flashed that bootloader,(MJ2), and had even been running CM11 for a while, up until last week. Maybe something set it back? Never heard of anything that would cause that.

Anyway, I flashed it 'again' and it looks like the cm11 is installing now. Very strange. Even in recovery, I have to install CM11 from the external SD card. I can't install from internal stored zip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
On the lock screen, swipe up. You can also use the search bar or long press the menu button to access it. There is no app for Google Now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Umm..i know those are the different ways to access it. However when i do those things...nothing comes up. Its as if nothing is there. Am i supposed to flash GApps to get it to wrk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tehsprayer:
Yes you need gapps for it also for pay store camera stock stuff
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
Yea you'll need to flash gapps. And I had to flash gapps again when I dirty flashed updated from 7/27 to 7/29. Everything worked fine but the search bar just showed universal search instead of Google now. I reflashed gapps and all was good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Hey..thanks for the reply. Is the version on GApps from this link fine?

http://xdaforums.com/showthread.php?t=1769508
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
Those are a little outdated. You can try justinbean's gapps from here, but they are inverted. If you want regular gapps, I'm afraid you'll have to wait a little while as it appears goo.im is down and that's the only place I know of to download the latest JB gapps from.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
No those are ics. Here

http://d-h.st/HXx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] scott8281:
I'm using the jellybean gapps dated 7/17 from here...

http://www.google.com/url?sa=t&sour...zoGgAg&usg=AFQjCNHa8yu7QXlTt_of_kFiqrd_r_OcyA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Thanks for the quick reply guys..Appreciate it.

Unfortunately, I just flashed the old GApps and its throwing up some errors. Lemme do a clean install again. :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dyno0919:
Good find 2Chainz, we can always rely on you to find the answers ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
I finally got this rom installed via twrp which was quite the adventure getting going on its own.

Anyways I'm a bit surprised that jb 4.1.1 looks very similar to the older ics 4.0.3. I'm coming from the newest stock ics 4.0.4 rom that comes on the S3 and it is actually pretty good. The menus, icons and camera are all different but this jb looks like all older familiar ics menus icons, etc. Especially the camera its the very basic version that was with the first ics. The new stock S3 camera app is actually a lot more advanced which was surprising. Just curious what I'm missing and what jb's key differences and new features are?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] simplex123:
LTE works on Telus but you need to go into the info menu with the dialer code *#*#4636#*#* to turn on GSM/LTE

Got really fast speeds too!

58Mbps Download/13Mbps Upload
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] entropism:
By the way, Goo.im was only down for an hour or so. GAPPS are right here: http://goo.im/gapps/gapps-jb-20120726-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pizz0wn3d:
Http://bit.ly/T6c8Lk

Herp derp SGS3 Tapatalk 2