Is there a way to by pass this, who would connect their galaxy gear while it's charging isn't the idea to connect it while it is off the dock, would look clunky and you'd be limited to space by the usb cable adding a leash to your wrist...
It pairs and everything downloaded the 11 updates and what not and now I'm prompted by this stupid popup. The seller sent me a generic dock that doesn't even snap around the watch instead it has 2 pegs and a button that ya press to release the pegs and take the watch out of the dock.
Do I need to get an official sammy dock in order to start using this damn thing? Really! LoL SMH!!
_
Also FYI, as my signature states I'm on a T-Mobile Note Edge (N915T) Hyperdrive KitKat 4.4.4 and got the Samsung Gear Manager downloaded the the Galaxy App Store, just pisses me off that after waiting a week to find out now I've gotta wait even longer in order to use it possibly.
Okay a lil step further keeps coming up with incorrect pin error now.
Okay finally somehow got it to connect after turning bluetooth off a few times.
Solved...
But for the life of me I can't find location settings in Samsung Gear Manager.
How do I get to that?
Damnit all if this isn't ridiculous as heck...
Tried flashing TWRP in Odin since I'm on 4.2.2 and then it flashed and then while trying to get into recovery I entered it successfully no TWRP though and it reset my gear and now I'm having to fight tooth and nail to get it successfully pair again and what happens next phone says its successfully pair in gear manager but the watch still shows the device setup pairing screen.
Hell if this doesn't make me want the Rufus Cuff even more. I've never seen such complicated shiet!!
Yay more failed to connect messages and unable pair due to incorrect pin messages.
Bout ready to ram this straight up samsungs arsehole!
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
AA is buggy but I'd have to say......
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse
I think this is your radio hardware and not the AA app. But you never really disclosed what phone you are using and if it has been modified or what so there is no clear help answer that I can assist you with.
hi, i've got the Note 3 (SM-N9005) running stock lollipop 5.0 (baseband N9005XXUGBOI2). my phone was previously running 4.4.2 kitkat with root.
the connection is very hit and miss. it will keep trying to read my phone when plugged to the car and the phone will keep shifting between "connected as a media device" or "connected as a USB accessory". When its connected as usb accessory, the phone screen will black out for a second and then goes back into the previous screen which is usually home page of the launcher. i think the "blackout" might be the phone trying to boot or load android auto app but gets disconnected as it tries to get in.
i have to plug the usb in and out a few times and sometimes by lottery, it will establish a successful connection and AA loads on the car screen. i've found that if i open the app first on the phone and then plug in the usb, it will have higher chance of getting a successful handshake.
hope this makes sense.
I have the exact same issue: VW App-Connect in a new 2016 vehicle with a Galaxy S5 running Lollipop. Very annoying because once the two are connected it does work reasonably well.
rafalucas said:
I've recently bought the new vw golf with the android auto function. I've updated my galaxy note 3 to the latest lollipop 5.0 UK version so i can use AA.
The phones initial connection is fine. Open the AA app, connect USB to car, car recognises the phone via AA. Phone changes connection type to USB instead of Media. AA app then prompts a few questions (as its new connection to the car) and then AA is good to go on the car screen.
All is well until the next time i hop into the car and connect the USB to the phone. you would a expect that as my phone made an initial connection, the car should be able to pick it up and AA will then load up. However the car display will keep going into a loop where it tries to read my phone but connection keeps failing. likewise for my phone it will keep shifting between connection as media and connection as USB (which is the connection type for AA). AA wouldn't load at all on my phone. i go into the app and tried connecting again but the app will just quit by itself. i've tried USB debugging, no luck. i'm using the samsung original USB cable so didn't think there would be issue here.
the funny thing is that i figured that in order to get AA to connect successfully is to go into the app and go to the settings to forget the car that i initially had it connected to. so next time i plug in the usb and go into the app, it will start the new connection prompts and voila it will work again. but next time i plug in the phone it will just go back to the connection loop and won't be able to trigger AA to load on the phone.
there was only one time that the phone managed to connect to the car and load AA without the need to forget car and connect as new. its very hit and miss and i'm not sure whether this is a bug in the app or the car's.
anyone else having similar connection issues?
Click to expand...
Click to collapse
I believe Verizon phones were having USB connection issues because of some special app they had that did stuff over USB, and an update fixed it.
Some USB connection issues can be solved by changing the mode of USB: MTP, Charge Only, etc.
Some issues can be worked around by enabling (or disabling) USB debugging. This is under Developer settings after Dev mode is entered by tapping Build number 7 times.
Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.
I have similar issues with my 2016 Skoda Fabia Combi. I'm guessing the infotainment system in the Skoda is pretty much the same as in the Volkswagen. Many parts are because Skoda is owned by VW. After tons of trial and error, I've had some success connecting my LG G3 but first let me tell you how I ended up in the current situation.
I have tried to connect thee different android devices (LG G3, HTC One M7 and Nexus 7 tablet all running Lollipop) with bunch of different USB cables. The result is always the same. On the phone I see black screen flashing before it returns to home screen and nothing else happens. From the recent apps view I can see that the black screen was AA trying to launch. CarPlay with iPhone works fine.
I live in Finland so I have sideloaded the AA app and at first I thought that the issue is caused by AA not being officially available here yet. After searching this forum and other android forums I found out that other people are having the same issues in countries where AA is supported so maybe this is not the case. Obviously it's not also a device problem because I get exactly same results with different devices from different manufacturers. Only common nominator seems to be the VW/Skoda infotainment system? Correct me if I'm wrong here..
In the Skoda smartlink menu you can choose your preferred connection protocol from Android Auto and Mirrorlink. This affects the order the car attempts to establish the connection. I read from a Skoda forum that someone had a successful connection after he had changed these options around so I tried it. I checked Mirrorlink as a preferred method and tried the connection: no luck. I changed back to AA as preferred method and to my amazement after this the AA launched on the phone and I had a successful connection! If the VW has similar option I suggest you VW guys also try this.
My current situation is that most of the time the phone does not connect at first try but after changing the preferred method around it does. I have also other issues with AA. After connecting I cannot adjust the volume first from steering wheel/stereo volume knob. Spotify audio goes to a wrong channel at first (I can hear it only when i activate voice command) After changing music app to Google Play Music and then back to Spotify it starts working normally and I can also adjust volume. And of course the restriction on browsing your Spotify library. It is the most stupid thing I've ever seen at that level of software development.
rafalucas said:
Hi Mike, I've got an Australian stock unbranded note 3.
i've spoken to the vw dealer and apparently vw is working diligently for a software upgrade to the car's infotainment system which may or may not fix the connectivity issue.
it's just frustrating that in order to get a consistent connection, i have to go into the app and "forget" the car, then it will go through the new connection prompts.
i'm hoping the next app update might fix the issue but at the moment its unclear whether its the app, or my phone or the car's problem.
Click to expand...
Click to collapse
Auto dealers tend to know almost nothing about software and smartphones. They know how to sell cars, and the mechanics tend to know how to fix them mechanically, more or less.
And they can almost always say that there is likely an update due at some point.
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
If you get it working you can get a better idea if your car HU is at fault.
I wonder if there are car stereo shops where you can plug your phone into a Pioneer AA unit, like 4100NEX, and see if it works OK on that.
I've had my 2015 Seat Leon (also VW group) for four months now and also having trouble with Android Auto through the SEAT 'Full Link' connection. It seems to be russian roulette whether it'll make a connection and start AA when you plug it in. Sometimes you'll get a 'Connection failed' message, other times you will see the system try AA, fail, then try MirrorLink then fail on that too (as my Nexus 5 doesn't support MirrorLink). As others have said you see the phone screen go black then crash out and goes back to the home screen.
The only solution I have is to restart my phone and try again. Its almost my routine now to restart my phone just before I know I'm about to go for a drive. It beats having to sit in the car watching my phone reboot before I set off!
I didn't know you can change the USB settings on the phone, so I'm going to go through the various settings in developer options to see if any of these help. I'm thinking 'Charge only' might be useful, unless AA needs MTP or network connection to operate?
seems like i'm not the only one! sounds to me its more and more likely to do with the vw made headunit (could be the firmware). I just tried a mate's phone with the AA app but it also went in a connection loop before finally establishing a handshake with the phone. hopefully next firmware update to the car's headunit may be able to fix but but i won't bet on that happening anytime soon.
guess everyone has to trial and error and find ways to establish a successful consistent connection. for me is to forget the car and establish a new connection to the car.
still frustrating as ever and i don't want to have to spend 2 - 3 mins each time before i drive to wait for AA to load.
anyone else having connection issues with other car makes?
rafalucas said:
anyone else having connection issues with other car makes?
Click to expand...
Click to collapse
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.
nimdy said:
'Charge only' might be useful, unless AA needs MTP or network connection to operate?
Click to expand...
Click to collapse
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.
mikereidis said:
With my Pioneer or my Headunit app, one of the biggest issues is quality of the USB cable and USB connections.
Testing with different/known high quality cables is worthwhile.
Click to expand...
Click to collapse
i've tried various cables but i find the original samsung cable that came with the phone the most "consistent" in establishing a successful connection.
mikereidis said:
"Charge Only" is what I try to aim for. Despite it's name apps like Android Auto can use the USB in this state.
AA does not need or use MTP or network connections via USB. Trying to use USB for other things, like network connection, would only be possible via a USB hub, but it's a crap-shoot whether that would even work.
Click to expand...
Click to collapse
i'll give this a go tonight
PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!
jonboyuk said:
PHEW. I thought maybe it was just me. I have just purchased a Skoda Fabia 2016 with Android Auto (I imagine this will be the same underlying system for VW/Skoda/Seat/Audi). I find that sometimes, I plug it in and then it magically works fine. Other times it can't connect to the device and tries to connect to MirrorLink instead....which also fails. I'm using a Samsung Note 3 official UK lollipop build - but rooted. When it fails, I have to go through the process of telling it that I want to connect to the device.
Incidentally when it has connected, it's rock solid every time (well with one random crash & reboot of the car's entertainment system).
It's just annoying. I want to get in my car, plug it in, AA to launch and that's it!
What's also slightly annoying is that there's no button to go right to AA on the dash. I have to go to 'Menu' and find Android Auto in that menu to launch back into it if I go to something else within the car's entertainment system. Grr! Not anything anyone can do on here, but just venting!
Click to expand...
Click to collapse
Galaxy s6 Stock firmware and my octavia android auto 1.4 work very well.
No luck with LG G3
Good day everyone, I just purchased a 2016 VW GTI and I have an LG G3 with Lollipop 5.01 rooted. and I can not get it to work with mirrorlink or android auto. Mirror link default or AA default. I tried different cables, plugged in car on before the car was on. MTP, PPP, charge. The head unit does see it as an LG phone but nothing works.. usb debugging on or off.. Kind of bums me out. Oh I keep getting a make sure the phone is unlocked message I turned screen lock off, and the phone is awake when I try to connect.
mikereidis said:
If you, or anyone having a problem on the car/HU side, has a USB OTG cable and a bit of time to test, you should consider trying my Headunit app; see my sig.
Click to expand...
Click to collapse
Yes! This is the best option for check if the problem is the HU/car or the phone.
From my point of view typically the most issues are related to the phone (ROM, AA app, etc.). For example, with my previous Lollipop 5.0 one month ago... the AA was inestable. With a new 5.1 phone and with the last AA app version (upgraded 1 week ago) I don't have any problem.
Please, try this before post about problems. Sometimes the problems isn't the car or the Head Unit. :angel:
Hi all. Further to my last post, I'm also sure it is a device/ROM issue. It doesn't work all the time, but most of the time the workaround for me is to open the open apps list, swipe them all off to close them, including AA app, then re-open AA. This increases the chances of my phone connecting to the car, but every so often I get a connection error and have to try again a second/third time.
I think I may have asked before, but is there anywhere we can report these bugs to? AA is technically beta (as with most Google products) so I'm sure they would welcome our bug reports.
Connection Memory ?
Hi,
I have the same experience as many others that the connection to AA is very random. I've tried:
Different phones (Nexus 5 and Nexus 6 on stock Android 6.0)
Different USB cables
AA app on and off
Screen locked and unlocked
All without being able to see a pattern. Sometimes it connects automatically in 15 seconds, sometimes automatically in 1 minute and sometimes I need to manually push the connect on the HUD (VW Passat 2106).
The only thing that is consistent is that once you are connected to AA and then disconnect, if you re-connect the phone it works flawless every time ! It seems to be working even if the re-connect happens after a few minute (e.g. not rigth away). So it seems that either the HUD or the phone has some sort of connection memory. Once it expires the connection problem reappears.
Anyone else that can confirm this ? Any ideas on where the problem can be ? I guess this rules out the USB cabel as suggested by many.
// J
Hello,
I just bought Gear VR today and I connected it to my Samsung Galaxy S6 (6.0.1). I have successfully installed Oculus software and downloaded some apps, however when I connect my phone to the VR headset, I only see the black screen. When I remove the phone from the headset, it says "Calibrating Gear VR..." after which an X appears in the corner, and doesn't allow me to do anything. I have to force restart my phone as it doesn't respond to any other function.
I tried uninstalling and reinstalling Samsung Gear VR services, Oculus Home etc. but it didn't help. I also did a factory reset for my phone, to no avail. I've also spent many hours looking for a solution, but nothing works for me.
I am not sure whether it's my phone or my Gear VR headset, but something is not right. It seems that my phone is unable to run Oculus Home (or whatever it's supposed to run) when I connect it to the headset. I hear that "connect sound", but then the screen goes black and I can only restart it by holding volume down and power buttons.
Could you please tell me what to do?
Thanks!
I've found a workaround, if anyone reads this.
I made it work, not as it's intended to work, but all functions are working and that's fine for me. I basically enabled developer mode for Gear VR service which allows Oculus apps to be run without the headset. Then I connected it to the headset, which is then recognized as a mouse, allowing you to use headset's controls and touchpad.
AsPeHeat said:
I've found a workaround, if anyone reads this.
I made it work, not as it's intended to work, but all functions are working and that's fine for me. I basically enabled developer mode for Gear VR service which allows Oculus apps to be run without the headset. Then I connected it to the headset, which is then recognized as a mouse, allowing you to use headset's controls and touchpad.
Click to expand...
Click to collapse
How did you accomplish this? Do you mind sharing the details? Im having this same issue.
asainz320 said:
How did you accomplish this? Do you mind sharing the details? Im having this same issue.
Click to expand...
Click to collapse
Sure!
First, I downloaded SideloadVR. You need to create an apk that has your device ID and install it. So go to Google Play Store, download the app and then follow instructions to build the apk. After you build it, download it and install in your device. Doing this will allow you to enter developer mode for Gear VR apps (developer mode = running VR apps without headset).
After you're done installing it, go to Settings -> Applications -> Applications Manager and look for Gear VR Service. Tap on Storage, then select Manage Storage option. You will see a few things in the new menu, and now you need to tap 6 times on VR Service Version and developer mode should be enabled.
When you do that, you can go to your Oculus app and Enter VR, and it should work. You can also run pretty much any other VR app (that's not intended for Gear VR) this way.
I am not sure if I explained it well, but please let me know if it worked for you. If not, I'll be glad to help you as much as I can.
AsPeHeat said:
Sure!
First, I downloaded SideloadVR. You need to create an apk that has your device ID and install it. So go to Google Play Store, download the app and then follow instructions to build the apk. After you build it, download it and install in your device. Doing this will allow you to enter developer mode for Gear VR apps (developer mode = running VR apps without headset).
After you're done installing it, go to Settings -> Applications -> Applications Manager and look for Gear VR Service. Tap on Storage, then select Manage Storage option. You will see a few things in the new menu, and now you need to tap 6 times on VR Service Version and developer mode should be enabled.
When you do that, you can go to your Oculus app and Enter VR, and it should work. You can also run pretty much any other VR app (that's not intended for Gear VR) this way.
I am not sure if I explained it well, but please let me know if it worked for you. If not, I'll be glad to help you as much as I can.
Click to expand...
Click to collapse
This is good information, I used it to get mine going in my note4 which has been an endless struggle. Only problem I'm having now is my track pad won't work and my phone isn't saying mouse connected. Is there a way to enable the mouse function when I connect it?
AsPeHeat said:
Hello,
I just bought Gear VR today and I connected it to my Samsung Galaxy S6 (6.0.1). I have successfully installed Oculus software and downloaded some apps, however when I connect my phone to the VR headset, I only see the black screen. When I remove the phone from the headset, it says "Calibrating Gear VR..." after which an X appears in the corner, and doesn't allow me to do anything. I have to force restart my phone as it doesn't respond to any other function.
I tried uninstalling and reinstalling Samsung Gear VR services, Oculus Home etc. but it didn't help. I also did a factory reset for my phone, to no avail. I've also spent many hours looking for a solution, but nothing works for me.
I am not sure whether it's my phone or my Gear VR headset, but something is not right. It seems that my phone is unable to run Oculus Home (or whatever it's supposed to run) when I connect it to the headset. I hear that "connect sound", but then the screen goes black and I can only restart it by holding volume down and power buttons.
Could you please tell me what to do?
Thanks!
Click to expand...
Click to collapse
I don't know if you know this, but when you connect your phone to Gear VR, the phone screen light is controlled by the light/proximity sensor built-in in Gear VR (between the lenses and above them) and not of phone. So the screen lights up only when you wear it or cover this sensor by hands or something.
See more info and a simple hack at: http://androaddyct.blogspot.in/
I know this might be a lost cause but I will ask anyway. I had my watch and loved it(still do) but since getting the Pixel XL I have had issues. These are the steps I have taken so far.
1. turned both watch and phone on and turned on bluetooth
2. watch connected to phone and reset itself
3. connected to phone via bluetooth and got the passkey (stated it would be phone audio only)
4 launched the gear manager and it tried to find it but would not (even though the bluetooth did)
5. downloaded the XDA gear manager and installed it on the phone but it force closes each time.
So anyone else with similar issue? I suspect it is the app version not being for android 7.1 or the fact the watch is no longer compatible with other devices anymore (hopefully not).
Any help is greatly appreciated on this subject.
Thank you All.
I have a friend who is having the same issue, Gear 2 on the Pixel XL. We put the app on the phone, reset the watch, but I can't connect the two. Bluetooth connection seems to work, but the app doesn't pick up where it needs to in order to complete the process. He came from a Note 4 (with a Note7 in between). I have an S2 watch I need to try this on as well, but I figure I'll likely have the same issue. Eagerly awaiting an update to fix this!
stud421 said:
I know this might be a lost cause but I will ask anyway. I had my watch and loved it(still do) but since getting the Pixel XL I have had issues. These are the steps I have taken so far.
1. turned both watch and phone on and turned on bluetooth
2. watch connected to phone and reset itself
3. connected to phone via bluetooth and got the passkey (stated it would be phone audio only)
4 launched the gear manager and it tried to find it but would not (even though the bluetooth did)
5. downloaded the XDA gear manager and installed it on the phone but it force closes each time.
So anyone else with similar issue? I suspect it is the app version not being for android 7.1 or the fact the watch is no longer compatible with other devices anymore (hopefully not).
Any help is greatly appreciated on this subject.
Thank you All.
Click to expand...
Click to collapse
I would like to know if there's a solution to this as well. I upgraded from a Note 4 and haven't had any luck getting my Neo to show up in Gear Manager for my LG V20.
I came from an S4 and had the exact same issue as stated. It will connect through bluetooth devices, but the Gear Manager app refuses to find or acknowledge it exists.
I suggest doing a factory reset. I have to do a reset every time I flash a new rom on my phone. I have to do this on both the tizen rom and android wear.
Has anyone figured out how to connect pixel XL to the gear neo 2? I am having the same problem. Can connect to watch with Bluetooth, but will not connect through the app.
Thanks for any help.
have any of you with this problem flashed android wear to the gear 2 neo? i use it as a daily driver and its very stable, might be the solution for your issues
Had it but lost it
I had my pixel XL connect to a flashed gear2 Neo
I reset my phone and know no matter what I try it won't connect this happened at the same time they updated Android Wear. W os . I installed an old version of Android Wear could not connect I flashed different roms
I'm giving up
My plan was to use my phone as a basic photo station.
So we got the Note 8, Dex Dock and the Gear 360 (2017).
Plugged it into the DEX and CRAP! Gear 360 says not working with DEX....
Anyone have a clue around this or an idea if there maybe a future upgrade to the 360 Software to work with DEX?
I have the Dex and Gear 360, but never tried to connect one to the other.
If you search around, you may be able to find a way to force the app to work in Dex. I had trouble with Teamviewer not wanting to load at all, and now it does. I wish I could point you to specific threads/apps, but I'm at work
Samsung support said it does not work. Ahhhh Crap.