Related
Hey everyone!!
Did anyone manage to connect his HTC Wings via Bluetooth to the PC and Sync it with WMDC?
It works with cable but not Bluetooth (BL).
I appreciate comments.
Thanks
A.Bagatov said:
Did anyone manage to connect his HTC Wings via Bluetooth to the PC and Sync it with WMDC?
Click to expand...
Click to collapse
It worked pretty easy on my S730. Make sure you enable BT on the phone and your computer. Pair the PC with the S730 and start ActiveSync on your mobile. Select the option 'Connect via Bluetooth' and that was it (for me).
you seem to be using activesync, however i use windows mobile device center with windows vista x32... so the procedure is different and much more problematic it seems... not just with the s730 but with all wm devices
A.Bagatov said:
you seem to be using activesync, however i use windows mobile device center with windows vista x32... so the procedure is different and much more problematic it seems... not just with the s730 but with all wm devices
Click to expand...
Click to collapse
I use Windows Vista Business (32-bit) and I needed to upgrade Mobile Device Center. It works without any problems afterwards. The only disadvantage is that I need to manually connect on my phone, before it starts synchronizing. I would rather have it syncronized whenever it is near my laptop.
it doesnt work for me. bluetooth is turned on in both devices.
does anyone have any suggestions?
i have the toshiba bluetooth stack software, do you use that too??
I had the same problem. Open you WMDC and go into Mobile Device Settings and select Connection Settings. Under Allow connection to one of the following: change the selection from Bluetooth to COM7.
Then open your device and set up your bluetooth connection again. You should see Activesync now.
You are most likely using the Toshiba Bluetooth Stack instead of WIDCOMM.
IT IS NOT WORKING
AAAAAAAAAHHHHHHHHHHHHHHHHH
this is so STUPID
when i try to set up on my phone then it says "you have no partner for activeysnc, get one?"
i say YES and choose my computer
then i can select a port a one point and i CANT select 7
whats the solution!=?!
From your response I think you are trying to set the COM port on your device but you should be changing it in Windows Mobile Device Center.
I'll go step by step in case I was not clear.
1- Disconnect your Wing from your computer.
2- Open Windows Mobile Device Center
3- The only option should be "Mobile Device Settings"
4- In Mobile Device Settings you should have two option Connection Settings and End a partnership, select Connection Settings.
5- Under the second check box "Allow connection to one of the following" there is a drop-down box which should currently read "Bluetooth". In the drop-down box change that selection to COM7.
Note: If COM7 is not available, then I suggest you uninstall your Bluetooth device drivers and then reinstall them.
6- Close Windows Mobile Device Center
Now return to your device.
Delete any existing Bluetooth connections to your computer. and reestablish your Bluetooth connection. You don't need to change any COM settings on your device. Just establish your connection and you should have the Activesync option once it is reconnected.
This is under the assumption that you are running the Toshiba Bluetooth Stack on your computer. If you are and it doesn't work, I'm all out of ideas.
I should have specified that as of Step 2 above, this is all done on your computer not your smartphone, i.e. HTC Wings.
Your problem with Bluetooth is on the computer not the device, most likely.
this doesnt work... i did all the things like u told me on the computer.
then i go to my phone and try to connect from activesync via bluetooth and it says that no computer with a partnership could be found?? even though i actually made bluetooth partnership with my pc. when i added my pc to my bluetooth devices list on my HTC it told me that my pc supported 2 services: stereo audio and com port. i ticked com port... it doesnt seem to help.
on my pc, when i open the bluetooth stack software from toshiba i can see my phone has a partnership with my pc. but it has a network symbol on it.. is this supposed to be like that? ah this is so frustrating? any suggestions?
The only difference I see between your set up and mine is that I don't have a connection appearing on my computer.
So when you open your Bluetooth Settings on the computer, I don't have a saved connection with my Smartphone. The only place I see a connection between my computer and my device is on the device itself.
So my last suggestion is to delete both connections. The one on your computer and then the one on your device.
Open your device and reestablish a connection from your device to your computer. You will be asked to enter the password on your computer but when you open your Bluetooth Settings, you may not see a saved connection.
Also, go back and make sure that in Windows Mobile Device Centre, the connection is for COM7 and has not reverted back to Bluetooth. What you described has only ever happened on my computer when the connection was not set to COM7.
Something currious happened with my device when I was reestablishing my Bluetooth connection, which may be of interest to you.
I erased my original Bluetooth connection and while reestablishing it my device was also connected to my computer with the USB cable. When I paired the device, there was no option for ActiveSync. I disconnected my device and then started the Bluetooth pairing over and this time ActiveSync was available.
Does this help?
Any of you guys who have sucessfully pairedd WDMC in Vista with S730 over bluetooth use original MS out-of-box bluetooth drivers?
I've only used the Toshiba and Widcomm Bluetooth Stacks and have been able to sync with both on Vista.
dagobert_29 said:
The only difference I see between your set up and mine is that I don't have a connection appearing on my computer.
So when you open your Bluetooth Settings on the computer, I don't have a saved connection with my Smartphone. The only place I see a connection between my computer and my device is on the device itself.
So my last suggestion is to delete both connections. The one on your computer and then the one on your device.
Open your device and reestablish a connection from your device to your computer. You will be asked to enter the password on your computer but when you open your Bluetooth Settings, you may not see a saved connection.
Also, go back and make sure that in Windows Mobile Device Centre, the connection is for COM7 and has not reverted back to Bluetooth. What you described has only ever happened on my computer when the connection was not set to COM7.
Click to expand...
Click to collapse
there is the problem: "You will be asked to enter the password on your computer but when you open your Bluetooth Settings, you may not see a saved connection."
because as soon as i enter the bluetooth password on my phone and computer, there appears a bluetooth connection in the manager from toshiba. this connection has a "network" symbol and the services offered are com port and stereo audio. thats not much is it? and also when i click "connect" an error comes up.. connection couldnt be established or something.
i hate this. how can be a SIMPLE task so problematic?
toshiba drivers are working fine. send and receive works. and my phone is fine too. the wmdc work fine as well via USB. i also installed the wmdc UPDATE..... wtf right?!
Hey A.Bagatov,
I'm at a complete loss to understand why you can't get WMDC to work with your phone over BT. You've done everything I've done but unlike you I was able toe stablish the connection.
The only other thing I can think of is to download the latest BT drivers from Toshiba. But before you install them, make a copy of the TosBtChk.dll file and once you've completed the installation of your new BT drivers, replace the new TosBtChk.dll with the one you saved. This will stop you from receiving the trial period notification.
If that doesn't work, then maybe replace your Toshiba BT stack with the Widcomm stack. You'll need to locate a version compatible with your computer.
i would like to get widcomm and get rid of the problems.
so where can i get the widcomm stack? and how do i figure out if its compatible with my laptop?
its sony vaio
A.Bagatov said:
i would like to get widcomm and get rid of the problems.
so where can i get the widcomm stack? and how do i figure out if its compatible with my laptop?
its sony vaio
Click to expand...
Click to collapse
You have to understand Widcomm is not a free replacement for your MS drivers. Its commercial and it can only be obtained with some BT hardware, not as stanalone product AFAIK. As that, it is a bit complicated to make it work with unsupported device (but quite possible). And where to get it? Generally, if you are able to pirate, you are also able to google.
However, I assume you have legal OS installed on your Sony laptop - why not to tell MS they BT drivers SUCK A BIG TIME? Go tell them its crap that does not EVEN WORK TOGETHER WITH THEIR OWN UTILITIES.
Call 1-800-MSSUCKS
A.Bagatov said:
i would like to get widcomm and get rid of the problems.
so where can i get the widcomm stack? and how do i figure out if its compatible with my laptop?
its sony vaio
Click to expand...
Click to collapse
I've also got a Sony Vaio, SZ45, and on the Notebook Review forum, there is a thread that discusses replacing the Toshiba BT stack with Widcomm, which you can get free of charge. The thread offers a modified file which should be sufficient to enable Widcommon your laptop. Here's a link to the general forum http://forum.notebookreview.com/forumdisplay.php?f=8
mpattonm said:
You have to understand Widcomm is not a free replacement for your MS drivers. Its commercial and it can only be obtained with some BT hardware, not as stanalone product AFAIK. As that, it is a bit complicated to make it work with unsupported device (but quite possible). And where to get it? Generally, if you are able to pirate, you are also able to google.
However, I assume you have legal OS installed on your Sony laptop - why not to tell MS they BT drivers SUCK A BIG TIME? Go tell them its crap that does not EVEN WORK TOGETHER WITH THEIR OWN UTILITIES.
Call 1-800-MSSUCKS
Click to expand...
Click to collapse
Microsoft are not the developers of the Widcomm Bluetooth Stack, it's owned by Broadcom. It can be obtained for free, however, you're right in saying it may not work with non-Broadcom hardware. In A.Bagatov's case, the issue is with Toshiba not Microsoft. They are the one's who developed a driver that is not always compatible with non-Toshiba products.
According to other posts I've, the Microsoft generic Bluetooth drivers would appear to work just fine with Windows Mobile devices, however, I was unable to get it working and did not pursue the matter any further once I was able to get the Toshiba BT Stack to function.
I can sympathize with your frustration, but your post does not help him solve his problem.
I have searched the forums with every combination of wording I could think of, as well as Google, for an answer to this problem...
How do I connect my Captivate to my Win 7 64 PC with Bluetooth? My laptop detects my phone, and vice versa, and I can successfully pair the devices, but after pairing Windows searches for Bluetooth drivers, and is unsuccessful in finding any.
I have searched for Bluetooth drivers, but have not found any online either.
Is there something I am missing here?
-Also, I have the USB drivers, and those work fine. I tried installing Kies and using that to connect via Bluetooth, but that is unsuccessful as well.
jordanpatrick said:
I have searched the forums with every combination of wording I could think of, as well as Google, for an answer to this problem...
How do I connect my Captivate to my Win 7 64 PC with Bluetooth? My laptop detects my phone, and vice versa, and I can successfully pair the devices, but after pairing Windows searches for Bluetooth drivers, and is unsuccessful in finding any.
I have searched for Bluetooth drivers, but have not found any online either.
Is there something I am missing here?
-Also, I have the USB drivers, and those work fine. I tried installing Kies and using that to connect via Bluetooth, but that is unsuccessful as well.
Click to expand...
Click to collapse
What dongle do you have? You have to install the bluetooth dongle drivers......if needed. Additional 'services' on bluetooth may reqquire specific drivers.
chappatti said:
What dongle do you have? You have to install the bluetooth dongle drivers......if needed. Additional 'services' on bluetooth may reqquire specific drivers.
Click to expand...
Click to collapse
The bluetooth is built into my laptop, so I am not sure, but the drivers are installed. I will try reinstalling the laptop's drivers again though, to be sure there isn't an issue there.
Reinstalled Bluetooth drivers - Still no luck. Restarted computer - Same. Rebooted phone - Now it works. Go figure.
jordanpatrick said:
The bluetooth is built into my laptop, so I am not sure, but the drivers are installed. I will try reinstalling the laptop's drivers again though, to be sure there isn't an issue there.
Click to expand...
Click to collapse
Does windows fail to find all driver updates while pairing, or only one? Can you look under Device Manager for yellow ! marks.
chappatti said:
Does windows fail to find all driver updates while pairing, or only one? Can you look under Device Manager for yellow ! marks.
Click to expand...
Click to collapse
Definitely check for this, and also, when you have successfully paired your phone, you'll see it as a device in my computer.
jordanpatrick said:
Reinstalled Bluetooth drivers - Still no luck. Restarted computer - Same. Rebooted phone - Now it works. Go figure.
Click to expand...
Click to collapse
Rebooting is such a small thing with such big consequences !!!
Hello,
I've got a Lumia 1020 and I'm trying to connect via Bluetooth to a windows 8.1 device. I'm able to pair the devices, but as soon as that process is complete, the connection drops. On my phone, I can tap on the name of my computer, and it will reconnect, but it lasts for literally 3 seconds, before dropping the connection again. I've tried connecting to both my Surface RT and my windows 8.1 ultrabook with the same result. The phone will connect to my car stereo just fine, and I never have to do anything with it. Is there some sort of protocol that's missing in Windows 8 to allow phones to connect via Bluetooth? My main use for this would be music streaming, and using my tablet as a handsfree device.
Any help on this would be greatly appreciated.
Thank you,
Dustin
There isn't really any way to do that unless you are using something other than Microsoft's generic Bluetooth driver. I'd recommend checking out Trendnet's Bluetooth dongle or something that has broadcom drivers and they are extremely feature packed. My several year old BT 2.0+EDR from them works great!
thals1992 said:
There isn't really any way to do that unless you are using something other than Microsoft's generic Bluetooth driver. I'd recommend checking out Trendnet's Bluetooth dongle or something that has broadcom drivers and they are extremely feature packed. My several year old BT 2.0+EDR from them works great!
Click to expand...
Click to collapse
Thanks for the reply, I'll give that a shot!
Have you tried opening "View Devices and Printers" from desktop control panel? From there you should be able to right-click on your Lumia and click "Control".
I haven't used any Lumias but I'm able to stream from and to my Ativ Neo with both my Surface Pro and Lenovo Lynx running 8.1
Sorry if I'm misunderstanding your question.
Sent from my SPH-I800 using Tapatalk
I can apparently get my S6 (Raptor ROM 2.1, COF8 - 5.1.1) to pair with my Dell laptop but neither the phone nor the laptop show the other as actually connected.
I've tried pairing and then removing it from Bluetooth devices in Windows, toggling Bluetooth off and on, etc but nothing seems to work. Google's not really returning anything useful either.
Has anyone been able to pair AND connect their S6 with Windows 10?
yep
General_Mayhem said:
I can apparently get my S6 (Raptor ROM 2.1, COF8 - 5.1.1) to pair with my Dell laptop but neither the phone nor the laptop show the other as actually connected.
I've tried pairing and then removing it from Bluetooth devices in Windows, toggling Bluetooth off and on, etc but nothing seems to work. Google's not really returning anything useful either.
Has anyone been able to pair AND connect their S6 with Windows 10?
Click to expand...
Click to collapse
I have. Have u installed all win 10 updates? Works fine here.
sd_N said:
I have. Have u installed all win 10 updates? Works fine here.
Click to expand...
Click to collapse
I honestly hadn't thought to check if there were any additional updates. I'll do that when I get home tonight.
Thanks.
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