My Trinity device is not recognized by any of my 3 pc's using any of USB ports. The problem started when I wanted to try a different ROM. I currently have 20070418_RUU_Trinity_LVSW_WWE_1.25.0.8 installed. I wanted to install img-32424-mUn_1_25_AKU3_5 but during the reboot after the ROM transfer the connection failed for the USB connection, after which I gave up and thought well let's try again and soft resetted the device. However I was never able to get a Active Sync session going again. The OS is still booting fine so I feel I am trying to fix something which is not entirely broken. I also tried the suggestion for flashing from SD card, but that did not load the TRINIMG.nbh file as I hoped (and read) it would. So I have a IR connection and possibly a bluetooth connection (I left my bluetooth module at work so I cant test this) Will this be my free ticket out of jail? Thanks for your input.
I seem to remember something about someone loosing USB connectivity after installing and messing with the GPS icon. This probably won't help but I would try in your case.
Start>Settings>Connections>GPS
Program Port>None
Hardware Port>None
Baud>9600
Check manage GPS automatically
Exit & turn phone off
Turn phone back on
Doesn't work?
You are no worse off
Works?
Reset hardware port to Com 9
Uncheck manage automatically
Leave program port to off
Set GPS software to com 9 9600
tried it, but didnt work.
Does the USB connection work in bootloader mode by any chance? (Hold the power and camera buttons down and reset with the stylus).
Try to delete the ActiveSync partnership on both the PDA and computer and then reestablish it ... it may have nothing to do with USB at all.
Problem went away after I forgot to turn off the PDA while it was connected to the wireless. It apparently didnt switch itself of because it was dead when I tried to turn it on. After charging it for a while I could turn it on, and as by a miracle the USB interface finally connected properly with my laptop. It didnt give the error "Windows has encountered an unknown device on your USB port" So thanks for all your input sofar.
Hi guys,
I am having a problem with the wireless transfering feafure on my Z3C. A couple of hours ago I still could use it to sync my music wirelessly, then suddenly now I cannot use it anymore. When I tap the PC name in the paired PC list and tap connect, the phone try to connect to the PC but some how it cannot and just pop up a failure message.
This is the second time this problem happens and I do not know what causing it. The last time I changed my PC name and it worked again but just a few days later it happened again. Both devices were connected to the same WiFi and the pairing has been set up exactly as the instruction. I don't want to change my PC name over and over again, and I absolutely do not want to use the USB cable, so can anyone suggest me a solution to fix this once and for all?
Thank you
I'm having the same problem now. It's annoying. I'm resorting to normal usb connection now, but some light on this matter would be great.
Just checked mine (win 8.1 64bit) after not using it for some weeks, it connected right away, no issues.
thundaga_bum said:
Hi guys,
I am having a problem with the wireless transfering feafure on my Z3C. A couple of hours ago I still could use it to sync my music wirelessly, then suddenly now I cannot use it anymore. When I tap the PC name in the paired PC list and tap connect, the phone try to connect to the PC but some how it cannot and just pop up a failure message.
This is the second time this problem happens and I do not know what causing it. The last time I changed my PC name and it worked again but just a few days later it happened again. Both devices were connected to the same WiFi and the pairing has been set up exactly as the instruction. I don't want to change my PC name over and over again, and I absolutely do not want to use the USB cable, so can anyone suggest me a solution to fix this once and for all?
Thank you
Click to expand...
Click to collapse
Ok, I found a solution. I restarted my wifi modem and disconnected my phone and PC. After reconnecting, I followed the instructions on the PC Companion program and now my phone connects properly every time. Hope it helps you.
Bumping this. I have the same problem on Windows 8.1, and nothing worked so far. Tried with two different Internet connections and nothing.
Reseting the rooter - Nothing
Putting screen with 30 min timer and letting it work - Nothing, it always says it's impossible to connect in less than a minute.
There's nothing else running on the PC nor on the phone, so I really don't know what else to try besides another app like AirDroid or Wifi File Transfer.
Any ideas?!
Here is what I have observed:
1.) If the phone is already paired with the Pioneer, and currently connected, AA uses that pairing/connection if you then connect the phone to the USB port.
2.) If you shut the car off, leave the phone plugged in, on restarting the car you get another pairing created, and the one pairing you had before is gone.
3.) If Bluetooth is not on, plugging the phone into the USB port will turn on the phone's bluetooth, and connect to the Pioneer, usually with a new pairing.
While I guess this can be seen as a convenience to automatically turn on Bluetooth and re-pair your phone when you connect to the USB port, it pales in significance to the inconvenience associated with re-pairing my phone and resetting it up as a trusted device when I choose not to use Android Auto on a short trip. Plus you have to make sure your phone is unlocked before plugging it in anyway (or nothing happens), so it's simple to see if Bluetooth is on at that point.
And while this may be due to bugs in Lollipop 5.0, I know that if my phone is paired with the Pioneer, and I do not plug it into the USB port, that pairing auto-connects via Bluetooth as a trusted device every time.
Wish I could explain it.
Solutions Etcetera said:
Here is what I have observed:
1.) If the phone is already paired with the Pioneer, and currently connected, AA uses that pairing/connection if you then connect the phone to the USB port.
2.) If you shut the car off, leave the phone plugged in, on restarting the car you get another pairing created, and the one pairing you had before is gone.
3.) If Bluetooth is not on, plugging the phone into the USB port will turn on the phone's bluetooth, and connect to the Pioneer, usually with a new pairing.
While I guess this can be seen as a convenience to automatically turn on Bluetooth and re-pair your phone when you connect to the USB port, it pales in significance to the inconvenience associated with re-pairing my phone and resetting it up as a trusted device when I choose not to use Android Auto on a short trip. Plus you have to make sure your phone is unlocked before plugging it in anyway (or nothing happens), so it's simple to see if Bluetooth is on at that point.
And while this may be due to bugs in Lollipop 5.0, I know that if my phone is paired with the Pioneer, and I do not plug it into the USB port, that pairing auto-connects via Bluetooth as a trusted device every time.
Click to expand...
Click to collapse
I had a similar experience when I was using Android Auto. I tried it once to see what it was like, and thought it was nice but noticed that it took over my device anytime I plugged it in to USB, which I thought was excessive. But since Pandora has not released a compatible version of their program, I stopped using it. I had to remove the Android Auto application off my phone to get it back to just a normal trusted device. Peace.
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
Hi guys, I have been having an issue with the watch not being able to connect with my phone whilst being paired- not sure if its a watch specific issue or phone issue,
The bluetooth works fine will all other devices: car/speakers they will pair + connect automatically.
However, when i try to connect with my watch, there is no problem in pairing the devices (the code thing what not) but after the pairing, the devices wont connect automatically, and whenever i try to connect the devices, i dont get any response from the phone. E.g., if i tap on my paired devices with my speaker, it will try to connect and shows "connecting..." but if i tap on the watch, nothing happens, not even an attempt to connect, simply stays at not connected. I removing the pairing and resetting the watch, as well as restarting both devices, but issue still persists. Unsure if this is a problem with my phone or the watch itself, as the phone has no problems with connecting with other devices. Havent been able to try the pairing the watch with a different phone (i dont have a spare phone i can try connecting with atm, but will try that later on in the week by borrowing a phone off friend.)
Issue is even stranger considering i had no problems using the watch with this exact phone beforehand, (i just stopped using it for about 6 months because i lost my watch charging station and i couldnt be bothered to get a replacement until now.....)
The watch has been updated to the latest version, and the phone in question is galaxy alpha, running android 5.0.2
Thanks guys.
same here.....i did not find a solution