yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crawlgsx:
Same here but I am on 8/28. Long delay on call answer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kd5dmg:
If you have show Battery on lock screen always on then you will not see the owner info.

Just uncheck the show battery info and owner will return. Also Battery % will still be there when plugged in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
I've gotten three calls so far this morning, the first two I said "hello?" to a few times then hung up. After checking this thread and seeing the "four second" issue, I paid attention when I got the third call. When I answered it, the phone was continuing to vibrate as if it was still ringing even after I answered. After 4 seconds the phone stopped vibration, and the "in call" timer went from 0:00 to 0:04, and I was able to talk without a problem. This leads me to believe that the phone isn't actually picking up right away, so the call isn't connected, which is why we can't hear anything and no one can hear us for the first few seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kamandor:
With all the phone call delay issues, is it safe to say people should skip the 8/31 build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
I've experienced a delay w/prior builds, as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AnarchoXen:
Me too. Calls have been an issues in some regard since jump. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
I wouldn't say to skip it. The echo is gone, and the only "issue" is that when you answer, you just have to look at the phone until the call timer updates from 0:00 to 0:04 before saying hello. That seems to be less an issue to me than echoing. That said, I typically make more calls than I receive so the delay is a very minor issue for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Hey guys,

As per moderator's post, please direct all further discussion to the old (now official nightly) thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
That happened to me after an update.. just select the alarm ringtone again. (Possibly select a different one and go back), and change the alarm volume and change it back. I think those are the two things I did to fix it. I'm guessing you were running a fairly old build? I think it happened to me when I switched to the build using open-source libaudio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaskwith:
Downloading now! I love me some nightlies! :) only issues is deleting the old ones as they pile up after flashing everyday ha ha ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
I wish at least the calling/receiving happened without any issues... Still on 8/29
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pellel2:
Not to be rude guys but why people keep posting issues based on old nightlies I don't get it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crawlgsx:
It's only 2 days, and multiple people have reported the issue still exists with current nightly. It's not an old issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Lol.. U dont what u r talking abt or maybe u didn't read my post with any thought? I did try 8/31 build, and the 4 sec delay thingy is annoying enough for me to go back to 8/29 build. Unlike u I make and receive a lot of calls on a day.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
But the delay has been present in 8/29 aswell. Possibly even further back. I believe someone mention being present in 8/28 in the other thread

Can we please continue any further discussion in Cyanogens original thread please. We really need to keep all postings in 1 thread. Mods have been contact to see if they can be merged.

Thank You.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Mine does that too if there's notifications pending when I reboot. Clear all notifications (as in:

read

your email, don't just dismiss the notification!) and reboot again. As long as nothing tries to light up the LED in the first 10-20 seconds after booting, mine works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
There are a few things I've noticed... On 8/28-8/31

- I have noticed the call pick up delay on 8/28 but the delay seems longer on 8/31

- for the last several builds, when I receive and email and read it, the email remains unread regardless of how long I look at it in the Gmail app. I have to delete the email before the new email notification goes away.

- screen flicker is still present.... To check go to phone settings and about and continuously tap on Cyanogen mod till Cid shows up and you will see flicker or exit out of a game with the home button and you will see flickeribg

- the home button wake seems to be working fine now

- wifi signal indicator seems wonky.... Even when it shows no bars I have full speed wifi

- the camera menu is still wonky as well.... Items move around in the context menu and there are also duplicates for the toggles

If you guys notice anything else let me know

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
Can we start doing this (ie no more posts here after this one). It would really help a lot. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
As I mentioned before.... I asked Archangel to merge and close the thread.... He said it would be hard to merge the threads so I said feel free to close this thread.... However most nightly relevant convo is in here and as long as this thread is open I will continue to update it as I have.

Edit:

Don't take this the wrong way and feel free to move the convo to other thread.... I just don't want people who are still subscribed to this thread to be left out of the loop.... I myself only follow this thread because this is what I am running.... I don't switch ROMs therefore only subscribe to one thread

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Electroz:
Why not just rename the thread to "OLD" and "UNOFFICIAL" like it actually is???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Meh. I'll keep posting in this thread until closed/merged with the other one, because of the hyperactive OP (neverends) that updates an exhaustive list of fixed/known issues.

dirty-flashed 8/31 over 8/29 this morning, and received 1 call where it was acceptable to test the speakerphone: still echos even with the supposed audience chip noise-cancellation support in 8/31.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Oh now I'm hyperactive.... Do you recommend Aderall? 8-)

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
If the thread was closed with the first and last posts linking to the cyanogen's thread, it probably wouldn't get rid of any/many people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Heh... well, I just mean that you're more active when compared to cyanogen, who can't be bothered to continuously update (or blamed for not updating) every device thread that CM runs on, because he's busy dev'ing instead.

Having a dedicated fan update an OP with collected&confirmed info saves a ton of time wading through all the new comments.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cashyftw:
Being 100% honest, I don't think anyone cares what build your on. Literally.

Sent from my JellyBean Galaxys3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
I know what you mean and I was just messing around....

As for updates.... Multiple people have reported that the speaker phone echo still exists on 8/31.... I too have noticed a slight echo but not as bad as 8/28

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Actually I do... Helps to know what builds the issues being reported relate to...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
menu -> system settings -> display -> Notification light
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bee2643:
Not sure if you guys are aware, but it seems that playing music through a bluetooth device doesn't work

I can play music through the music app fine, but once paired to a bluetooth device such as bluetooth headphones or my car stereo, the speaker on the phone plays static and there is no music coming out of the bluetooth device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
What build are you on... Worked fine on 8/28 and works fine on 8/31 here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Are the people who've been reporting problems with Swype only using the old non-beta version?

FWIW: I've been using the Swype Beta (1.1.1.7628) for a few months now and haven't had a single issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Yea the beta works fine for me too - although I jumped back to SwiftKey3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Why do u even bother replying then.. U dont seem to have anything useful to contribute.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
That was an issue waaaay back in the preview builds, I can tell you that using the 8/30 build it works fine (and has worked for the past couple weeks, I use it in my car daily)

Oddly though, nobody's bothered to report that the AVRCP Bluetooth profile is totally busted; It only allows a 1-way data path to the phone, and passes no data out (song title, current playback state, etc) A2DP works fine, as does the Headset/Hands-Free profile (which carries some small amount of data like current battery level) but AVRCP only allows the external device to change the playback state, not view it.

EDIT: It appears that only AVRCP v1.0 is supported in CM10. Stock Touchwiz supports 1.3, and CM7+CM9 on my Milestone also supported 1.3. Maybe there's just a bad config flag set somewhere in CM10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
Does anyone know if CM10 has updated all bluetooth firmware for a2dp? On stock rom all song tags are displayed on a Bluetooth connected stereo but not with the cm10 nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
how do i upgrade via rom manager?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pativets:
After you've made sure that the APN settings are correct, make sure that you have LTE/GSM selected under Network Mode. By default, only GSM is selected and thus the reason why you are only getting 3G and H.

Once LTE is enabled it will show up as 4G (still not showing up as LTE, although speed is probably LTE speed).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Just open ROM manager and click flash clockworkmod recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
Right but it gives me a list of devices and I do not see galaxy S III. What do i choose?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d2k12:
Flash 5.8.4.5 from this post. The first one. http://xdaforums.com/showpost.php?p=28612095&postcount=558

Install the nightly using 5.8.4.5 and then check ROM Manager and galaxy S III will be displayed. I ran into the same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
thanks ill try it.

Last question, does the LED for charging and notifications work on this rom? And can you disable the backlight on the buttons?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d2k12:
Working for notifications for sure

Edit: Wait it was working but I just got a txt and did not see a LED notification. weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jrock60:
Are there any custom kernels recommended or should I just stay on stock? Should I use voltage control or set cpu? What is the recommended governor?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ovoxo.:
WiFi speeds still not where they should be.. is this a known problem at this point?

Everything else seems to be working nicely. Been dirty flashing since the 8/20 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Itaintrite:
Since you missed it in the OP:

"NOTE: Don't use any other kernel with this ROM for right now unless you want a completely broken system. Kernel developers will need to sync the 300 or so patches that have recently gone in. Please don't post here if you've done it anyway."

Feel free to try out custom kernels though, and let us know the results :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
I'm about to flash the new build, but I have a quick question that's a bit off topic. Does anyone know when Google Now be able to tell us scores for more sports other than baseball? Football has started and it still doesn't read back anything for it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Faux123 Jelly Bean kernel is working extremely well on CM 10 latest nightly ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
Interesting. I wonder why it showed up on get.cm when Jenkins has the build marked as aborted...

http://jenkins.cyanogenmod.com/job/android/6705/console

Probably once the regular season hits. At least, that's what I'm hoping.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] instigator008:
Mine shows me my Arsenal upcoming fixture etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djkinetic:
Oops accidental thanks, just flashed lean kernel tmo version on mine, seems to be running no problem, default oc 1.9 can we say zoom zoom..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I believe he was referring to handegg :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
hahaha yeah man American football! Not "so-cah" mate
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhinez:
I just flashed Faux123 kernel. Freakin nice!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stuff:
Mine lists Manchester United (football) as my favorite team, which is correct. I assume after googling a lot it assumes you are interested in that team.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabby131:
cm10 default kernel has Interactive

I did not knew that the default cm10 kernel has the Interactive governor. Wow! and it has conservative too which was not present in sammy kernel!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
The home wake bug is occurring less frequently, but it still occurs
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Read post above yours

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
Lol. My phone browser had not refreshed. How ironic. I thought i was the only one thinking about this !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Mic is busted in Google Talk on 8-31. Anyone know a build w/o this issue? I kinda need this.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mitchdickson:
Works perfectly for me. Something on your end.

Sent from my Motorola DynaTAC 8000X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
Echo on speakerphone is still present on 8/31. Tho it's slightly improved :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pvtbacon:
Other caller reports horrible echo when I have speakerphone on, but I don't notice it on my end. I've enabled noise suppression but that doesnt seem to help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deputy13:
Same here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bee2643:
I'm also running 8/31...should i try a clean wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Try deleting previous pairing and re-pair.... If that doesn't work try a clean install

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabby131:
Battery life at 8/31

1 hr wifi, 10 hrs wireless data (HSPA+), moderate phone use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bluefire118:
Aww man, that's excellent battery life
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kd5dmg:
Anybody notice you battery status not up dating? I ran it down to about 30% at work today then charged it on the drive home. It hit 74% when I unplugged it. But then it stayed there til now. When I rebooted it showed 15% this happened yesterday also when I was on 29 dirty now on 31 dirty. Going to wipe and re-flash 31.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gabby131:
Amazes me as well...cell location is also enabled in that 11hr uptime. I will try using google maps on a trip this weekend and see how battery life goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snowbdr89:
says incoming audio fixed on 31, what exactly was fixed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WA_Bob:
I'm not sure myself. I can't get YouTube or Pandora to work for me on 8/31,but the worked on 8/28. And I wiped clean and did a fresh install with Gapps today. :confused:

Sent from this here talk tapper of mine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sbddude:
Youtube and pandora confirmed working for me. 8/31 dirty flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snowbdr89:
is the headset call audio still super loud?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
on 8/30 there was no audio when you received a call... incoming audio was broken and is now fixed

YouTube and pandora working fine here

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Thanks a lot guys. Unchecking the 'show battery' solved the issue. Appreciate the quick responses.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kd5dmg:
Anyone look at 01 yet? Change log does not show much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
9/1 build appears ok. Call delay still exists. Not sure about echo, yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
9/1 uploading to get.cm

Edit: 9/1 dirty flashed.... Running well,

... there is a lag on incoming call

... Looks like additional settings got added to phone settings

.... Minimal screen flicker

.... Once out of 50 home button clicks it did not wake

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bakasam:
Currently using the 8/31 build with KT kernel.

Wondering if anyone else is having the same issues with Lightflow:

Lightflow works well (I know the dev has been working tirelessly to get it to work on the NA S3) but whats happening with my phone is the notification LED is still "on" or "flashing" even after I've read the message or notification.

It was working fine before. The only changes I've made to my phone recently is flashing to 8/31 (clean install and TB restore) and flashing KT's kernel (with some undervolting). Just trying to narrow down whether its the app that suddenly derped out, the rom or if the problem is from the kernel/undervolting

Cheers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
Get.CM is taking awhile... for the impatient ones...

Edit: link removed 9/1 was skipped not sure why.... I reverted back to 8/31
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WA_Bob:
Strange. Well, I'll try clean with today's build and see if it happens again to me. Thanks for the input!

Sent from this here talk tapper of mine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lcheng1:
You shouldn't need light flow at all to control the LED. Just go to display, and then notification light and change the settings from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheFiveDots:
Huh? The change log is about a mile long... http://cm10log.appspot.com/?device=d2att

EDIT: I feel like the changelog is including things both before and after the 09/01 build cutoff. For example, quick message support is absent in the 09/01 build but on the changelog.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
LED's working great on 8.31
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
It seems like 9/1 is the forgotten child.... Hasn't been posted on Get.cm and no change log

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeadlyDa:
Maybe we can just 1 CM10 nightly thread?

Suggestion: Going forward, why don't we all just use the "official" CM10 nightly thread by cyanogen. I realize this thread was created back when cyanogen's original thread still referencing the CM10 preview, and of course all props to neverends for jumping in starting a thread on CM10 nightlies when there wasn't one.

However by forcing folks to flip back and forth between two separate threads, each containing some useful information...well, sooner or later someone is going to miss something important and end up in a "bad place".

...just a thought.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
I agree... I spoke to Archangel and I was under the impression that he was going to close this thread... He said it was too hard to merge this in to cyanogens thread.... I have kept updating this thread because that's what I promised to do and have said that I will update till it gets closed simply because I don't want people who frequent this thread to get screwed and for whatever reason most of the nightly discussion is still happening here...

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Does enabling noise suppression in Dialer-->Settings get rid of the echo? Did anyone try a call with the option enabled?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] neverends:
No.... Not for me

Tapatalked w/ AT&TSGS3CM10JB
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
NOOOOoooo!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KennyG123:
Closed at OP's request

FNM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
BUG (for the OP)

Plugging in the official MHL->HDMI adapter still causes the phone to reboot on 8/22.

(link to my previous bug report with kmsg)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
Here is the new boot animation for anyone who is interested

---Download---

Navigate to system/media and rename the current bootanimation.zip to "bootanimation.zip.bak"

Copy the downloaded boot animation here and rename it "bootanimation.zip"

Change the permissions to -rw-r--r-- or 644

Reboot and enjoy! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
Just installed this. Very nice brah!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobilevy:
Phone Battery

Yes i agree with you, had preview 8/14 with better battery performance

K
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
Voice Search wonkiness

Whenever I use Google Now's Voice Search, it quits in the middle of my speaking and begins searching before I'm done. I've tried this on my old Captivate (which is friggin awesome with CM10 BTW) and it works perfectly. I'm on 8/22. Thought I saw someone mention this a while ago on the Preview builds. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobilevy:
No Netflix stil not working

No Netflix stil not working
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PiperD:
Happens to me too, although I'm still on the 8/10 preview.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phoneguy589:
Added link and instructions to post in first page. Thanks Ainen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adamt19:
^ thats a lot cooler than the other preview of the CM10 anim I had seen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] captiv123:
Not sure if this is the right place to ask this; but I am running 8/22 and all is fantastic except my earpiece volume is very loud when on calls, even at the lowest volume. Is there any way to lower it? I am on Rogers in Canada.

Am loving the ROM

Thanks again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eortizr:
It's funny when people call this a daily driver
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Because it is? I've been using CM10 since the previews came out and its been a fantastic DD for me, and I couldnt ask for more.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
It's perfectly suitable for a DD. Keep that garbage out of here. No other reason to post this other than to try to instigate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ainen:
I've been using it as a daily driver since the first preview build with barely any issues
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
He doesn't have Netflix or movie apps working yet. Sorry man I don't watch tv on my phone.