yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Like I said, I have no left channel with Google Play Music in A2DP or with wired headphones. Could this be the cure? (Sporting RC1 as of a couple of hours ago.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
Post your issues to jira, people with issues. CyanogenMod indicated that there were not many issues reported and that RC1 has been a great success (very awesome if that's the case for most devices). But if you want your issues to be alerted to the CM team before they start working on RC2, better report them now. See the CM Google+ post here:

https://plus.google.com/+CyanogenMod/posts/XHNzntyMkNq

Report issues here:

https://jira.cyanogenmod.org/secure/Dashboard.jspa

Sorry for being a broken record...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
sound issues here too, rolled back to 05/05 and all good. staying here for a while i think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigbrown:
Seems like a known issue:

https://jira.cyanogenmod.org/browse...streams-jira-plugin:activity-stream-issue-tab
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
seems like it will be fixed.

http://review.cyanogenmod.org/#/c/37261/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
Stereo Audio Issue

I also have this issue. In my case it seems to be only streaming audio. Audio on the actual device itself plays just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Importance of filing a bug if you have something to report and not just post here

https://plus.google.com/117962666888533781522/posts/XHNzntyMkNq
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yea, sound and camera issues are out there and worked on. So now what? Do we wait until tomorrow to flash a new nightly or will a RC1.2 be issued?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
you keep an eye on the change log, and do what you what with it

http://10.1.cmxlog.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
The random reboots are more of a concern I think. Every build that came after M2 has had them. At this point, I'm not sure that there is a catch-all fix for them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Honestly I reported a webkit/browser issue that affected ALL devices 4.0+ and even linked to a commit to fix it and my issue was dismissed for lack of a logcat.

How the heck am I supposed to get a logcat of something that isn't right? It's not erroring out, it's just not done right.

Take error reporting with a grain of salt, unless something is hideously broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Return to stock for me is nightly 3/17 :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Phone doesn't like Linux 3.4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kennyaa:
I get random freezes after hanging up phone calls on 3/17.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Latest nightly is out will all the fixes(Camera, one Headphone working, etc.). Go get it!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Not to answer for justin, but I haven't liked 3.4 kernel roms so far - too many bugs. For me, there are no issues with 3/17 at all and, in looking through the changelogs since then, I haven't seen any big features or improvements that make me want to switch. But maybe I missed something? What big features have been introduced since then that are game-changers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Game changers? None other than maybe the fix for the SystemUI memory leak that was affecting some people. They also updated Apollo and the Messaging app since then, but you could always just grab those from a newer ROM and put it in an older build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Running on a clean install, all stock, the camera still force closes when trying to open settings but at least you can re-open the camera and take pictures. No random reboots while streaming A2DP and no screen flickering, etc.

I flashed the AOSP camera and settings work again, so I'll probably just stick with that - seems to have all the features of the stock CM10.1 camera with a few extras thrown in.

I was really pleased with RC1 battery life though - ran 16hrs yesterday with medium usage and still had 51% left!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I'm still on RC1. The only issue I have (and I had with 3/17 as well) is that sometimes I lose my wifi connection and when I try to reconnect, it gives me a "fail to connect" error. I have to turn off and turn on the wifi (or occasionally restart the phone).

still no camera errors at all for me either. i haven't tried bluetooth yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Since moving from May 5th nightly to May 8th and then May 10th whenever I update my launcher (Nova betas) I get a reboot. Anyone else got this?

Also it seems like Deneb notification sound as well as others are gone? Anyone notice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
There were a lot of multiple names with the same sounds. So, they just cleaned them up. Argon sounds the same as Deneb.

Someone posted a list of the identical tones: http://pastebin.com/88iSucLN
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Apex Pro FTW!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't think it's launcher related though. In no time whatsoever should the launcher be actually able to soft reboot the phone when being installed. It's installed as a user app without root rights too, so yeah.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rcook55:
I just updated to the 5/10 nightly and while I haven't been in my car yet I can confirm that audio is in stereo again using earbuds and the camera doesn't freeze up!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
The main thing I noticed when switching to 3.4 was the smoothness.. When I went back to 3.0 everything felt so laggy.

Also it's always been as stable as 3.0 for me.. I waited til maybe a week or 2 after it was implemented by cm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Would anybody with more experience in submitting bugs care to submit the following bug report to CyanogenMod JIRA: Sometimes (though not always) during A2DP streaming, playback volume goes down upon receipt of a notification (as it should), but it doesn't come back up after the notification (as it should not).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I can help, but they require log cat for all issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rmead01:
Which is going to be a pain because i've noticed it VERY occasionally too but it's not the easiest thing to reproduce in a whim
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I wonder what this specifically changes

http://review.cyanogenmod.org/#/c/37327/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
It looks like it's changing the default APN to pta. This would solve the issue I posted about earlier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
It used to be on pta way back then and they changed it to something else and now they are going back to pta.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Does anyone else have issues with wifi on their phone? I'll lose wifi even though the phone sees the network. I'll try to reconnect and I get "failed to connect" sometimes turning wifi on and off works, but most of the time I have to reboot the phone. This happened on 3/17 and is currently happening on rc1. It's random, so I can't really reproduce it to grab a log. Any ideas? Are there wifi drivers I can flash? I did a Google search but came up empty.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yea cuz it doesn't work on wap.cingular. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
Yes. Keeps disconnecting for no reason and has issues reconnecting. Also finding the phone to be getting very hot on rc1, and slower than may 7 build. Going to try reflash of everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
You replying to me? Mine doesn't get hot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Have you gone into advanced wifi settings and made certain the region code is set correctly? Mine was set to Europe (don't know why) and I was getting disconnects. I set it to USA and haven't had that issue again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Yup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nrod0784:
Latest nightly is running great. No issues with camera or GPS. Don't use Bluetooth really so can't comment on that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Has download from get.cm or via cyandelta realllllllllyyyyyy slowed down lately?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
Had 510 randomly reboot twice. Once after I unlocked the screen and the second while reading mail. Still, it's an improvement...

Alberto
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Rc2 is out, downloading now. Go get it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
No, I haven't really noticed any differences in download speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
I've noticed it via get.cm. I've noticed it happens during the first few hours of a new release. I assumed it was due to everyone downloading it. It downloads at its normal rate after the initial rush.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peach007:
Do we need to wipe data every time a new nightly comes out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I don't. But if I have issues then I will. Before reporting something doesn't work be sure to do a wipe and a clean install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
Camera will also crash if you continually ask it to focus (tap the screen). Although Instagram never crashed on me...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
How would one find out if RC2 was built with all updates from 5/11 nightly or not?

In other words, is RC2 exactly the same as 5/11¿
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
There is no 5/11. Rc2 was released after 5/10 and includes fixes after 5/10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
I beg to differ

http://mobile.10.1.cmxlog.com/?device=d2att#cm-10.1-20130511-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
5/11 nightly was released after RC2 base on the time stamp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
I think rc2 is based off of rc1. The volume feature I had which was included in 510 is now gone after flashing rc2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Just flashed 5/11 and everything seems to be working fine. No crashes or reboots yet. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zeke757:
Need to try this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Latest nightly is smooth as butter!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
I'm really loving battery life on 5/11. Gps, camera, bluetooth seem fine also!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
How's 5/11 nightly compare with RC2? Any big differences?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
GPS on 5/11 nightly would connect initially but then drop off...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Makoers:
I just drove an hour and half with Google navigation without any GPS problems. So GPS seems to work perfect for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Rc2 is technically 509 (aka rc1) but more refined in terms of bugs. You don't get the features in 510 or 511.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
what features?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Is it just me, or is there a whole lotta revertin' goin' on in the development world?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uplift777:
I have been having data issues for a long time now. I'm on the latest nightly 5/11.

An ideas how to repair this issue?

I can get on WiFi fine. But my network data goes on and off... Any help will be appreciated. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Try flashing the different radios corresponding to your network. I had that issue with my device, and it was resolved when I flashed the latest radio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Rc2 working awesome for me. Think cm can release the final version before lime pie
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
May 11 working great here! Amazing battery life no crashes. I'm staying put for a while
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
One feature is the ability to adjust the media volume first instead of the ringer volume, which was introduced in 510.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uplift777:
Thanks for the advice. Can you lead me into the right direction into where I can download the radio?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
http://xdaforums.com/showthread.php?t=1831898
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I've had a data issue for quite a while too.

My problem is that the phone would rather linger on 4G and go back and forth from one bar to no signal instead of jumping back to a strong 3G lock. It hasn't always done this but for quite a while now it has. I've tried every modem for my phone and none of them have made a difference. I've just started turning off LTE cause it was passing me off so much. It used to switch back and forth much more seamless and on use 4g when it was strong.

No modem or APN change or anything that I can find will work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Have you been doing clean flashes since the data issue first started?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imfletcher32:
Unfortunately, the 4G lingering is is due to network settings (AT&T, TMO, etc.) not phone settings. Operators can use "priority" settings to force phones to camp on LTE if its signal is above a certain threshold, even if 3G is great, and stay there until it drops below another threshold. Of course, you can disable LTE like mentioned above. Getting back to 3G if 4G fades out (coverage or capacity related) causes my phone to get "lost" frequently...sometimes for hours if I don't manually toggle data on/off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
What's with the "awake" bar never being on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheCynick:
Random reboots fixed?

Sniffing around JIRA just now I came across this...

https://jira.cyanogenmod.org/browse/CYAN-1018

Dare we hope???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
God, I hope so. I got stuck in random reboot hell earlier today on 5/11 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
5/13 is out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
So far, so good after flashing about an hour and a half ago. Streamed A2DP all the way to work (about 30 minutes) and no random reboots. Camera still force closes when I try to change settings, but I can live with having to flash that AOSP camera someone found a few pages back. I'm definitely digging the battery life on these latest few nightlies and RC2. Very good when screen is off - I got close to 21 hours yesterday with about 30% left with light usage. Thank you very much devs!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
This doesn't make complete sense to me. Wouldn't it be my phone that decides what it wants to do? I thought those threshold values would be somewhere within my phone just as we can change preferred network modes etc.

I can't see how the cell towers are telling my phone what to do. As far as I'm concerned the towers just broadcast the signal and my phone uses whatever one it wants.

I've been fiddling around this morning with APNs and network modes both in the regular Android settings and within the service menu and I seem to have better jump back to 3G from a poor 4G signal. In the past it would go to no signal for a while before finally going back to 3G. It looks like I now have it going back to full bars 3G MUCH quicker once 4G is completely gone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Bug: after clean wipe and flash of latest nightly, if you use GPS and turn it off, "battery history" in settings reports that GPS never turns off. The blue bar keeps going.

To make sure it wasnt a kernel issue, I clean flashed nightly only. Bar turned off when I disconnected from maps.

Only way to get blue bar to turn off is by clearing cache and dalvik and rebooting. Blue bar reappears and stays when you use GPS again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Thanks. :) I figured if it ain't broke, don't fix it unless it's a clear upgrade. Sounds like it's not, yet. Much appreciated!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I've noticed this too. You don't need to clear stuff though. Just turning off gps and rebooting will fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
OK you found a bug, so follow CM instructions, see if it is present on RC2, and file a bug report on jira. This post does nothing here. cm himself said that the CM devs and maintainers do NOT check forums for bug reports.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
done.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Awesome, that's the only way we'll get these little things ironed out before the stable release is out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I'm still running 5/11 and haven't experienced any reboots and battery life is great, ~5hrs on screen time. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Anyone use Cerberus around here? The "take photo on failed unlock" feature stopped working for me after upgrading from an old build to 5/11.

The phone locks up while Cerberus is trying to take a photo and is completely nonresponsive.

Doing a clean 5/11 install yields the same results. Here's the logcat: http://pastebin.com/MZrEypgS

Updating to 5/13 resolves nothing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Try pushing your old nightly gallery APK back to system/app/.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Unfortunately I didn't make a nandroid that time. Is this a known issue? Where can I get that old gallery apk?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
In any old cm10.1 rom for Galaxy S3. You don't have your old ROM you flashed on your SD card or internal memory?

Extract it from the zip /system/app then push it using ADB or copy/paste it using any file browser. Make sure to set rights properly. 0644 if I'm not mistaken.

And no it's not a known issue, simply my suggestion to see if it fixes it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Unfortunately no, I was using CyanDelta, so I don't have old zips laying around.

Gallery2.apk from January didn't work. So I'm guessing it's the camera driver's fault... gah.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jason_Nguyen:
I don't really care for this issue but if anyone has tried the water live wall paper it acts up and the animations aren't smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uplift777:
12

---------- Post added at 03:16 PM ---------- Previous post was at 03:05 PM ----------

Please, let me know if you figure this out. Nothing works for me either. I can't even turn off LTE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I ran across this post this morning. It seems that the random reboots, and possibly other hardware related glitches, are related to outdated trustzone code on d2vzw. The trustzone related code seems to be part of the general d2 source as far as I know. Does anyone know what's going on here and will it help remedy the d2att issues with random reboots and camera problems that have cropped up since the new kernel was merged?

https://plus.google.com/104277415207525128383/posts/iAVpVPYqMtM

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
Saw this, too. Very glad and grateful to hear CM is working on it. Sounds like the packages might fix the random reboots, and maybe even the camera problems. Hopefully we see solutions soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
Installed 513 this morning. Outstanding all day, but just had one of those random reboots.... (Sigh).

Alberto
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I'm on 5/13, and can remotely get Cerberus to take photos just fine. Did not try the "take photo on faile unlock" because I don't use PIN, so not sure if it would have worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
5/14 is out, A commit was merged that effects the bootloader in some way specifically for our device. no idea what it does yet :P

flashing now

Edit, d2can should steer clear from this update, the bootloader is causing issues at flash. back to 5/13 for Canadian users unless someone knows some sort of workaround?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Confirmed on my 747M. Won't flash via cyandelta either. Just kicks you out to main menu of TWRP as soon as flashing tries to start.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Think this is to avoid installation on Mobiles having older firmware which causes random reboots. This will also create problem for non-AT&T users

Edit:

* CM-10.1 is known to be buggy on old tz/rpm firmware, assert for a recent firmware release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Here's the obvious question: where does one download the tz update?

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
As per my knowledge: Odin Back to latest AT&T Touchwiz ROM. This will update you with the latest firmware. Reports suggest this can be done through KIES.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peach007:
Is there any way to reinstall the apps that were on the S3 originally? Such as S-voice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stewartsoda:
No. You need to install a TouchWiz ROM to get those. You should probably search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I'm getting a bootloader assert failure and subsequent failure to flash on 5/14 with an AT&T I-747

Seems related to this commit: https://github.com/CyanogenMod/andr...mmit/efad9265de605ecb3b1578f8002e5dc36e1f0db9
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vcharette:
Are you using the d2can or d2att version of TWRP ? I'm with Bell and I always flashed the d2att version of TWRP and never had any issues. whereas my colleagues flashed the d2can and sometime ran into issues installing roms.

so easy fix would be overwrite TWRP d2can with TWRP d2att via Odin ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
can someone explain this 5/14 bootloader thing to someone who doesn't quite understand all the programming stuff? Is this new change going to mean that everyone using CM will have to go back to TW to get the latest firmware before flashing new nightlies/RC/stable releases?

What does it all mean?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
D2att all the time. Never had anything D2can on my phone ever. Never had any problems with anything.

No. Random reboots either!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
I'm using a d2att recovery. No dice
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] statickiwi:
Same here