Related
I setup ActiveSync to work over Bluetooth and it was working fine for a few weeks.
I just stopped so I deleted the partnership and tried to re-establish one.
When I try to setup my phone I can see the computer from the handset but when I put the PIN in my computer never prompts me to enter it on the desktop.
I can pair the handset from the desktop but when I do that I only get COM ports over 20 and ActiveSync doesn't recognize them.
I’ve tried deleting the Bluetooth adaptor and reinstalling it. My last resort is to do a hard reset but I have the phone just the way I want it and would hate to have go through the setup process.
Did you delete the partnership in Bluetooth on the dektop side as well? Perhaps it's dragging along legacy junk because that's still there.
I did delete all settings, however I had to show all hidden devices and delete the older BT com ports. I did a re sync and it seems to be working.
this is what I used. you might find it useful
http://axim.dpicts.com/
I installed the android wear google app to check it out. After uninstalling it, reinstalling and uninstalling again, wiping cache including play services cache. The aformentioned in the title just wont go away! Any suggestions or insights? I have the 64gb Turbo.
Does it say "boot loop sync" if it does then you have developer options on. Turn that off and the message will go away.
Wait, do you even have a wear device do connect to? You have to have a watch of some type for it to connect to anything.
It will always show in your notification bar when it is trying to connect to a watch one you have Bluetooth turned on.
I'm assuming you don't have a watch which leads me to the most important question, why are you installing android wear if you don't have a wear device connected?
I have a chinese clone bt watch but it doesnt use android wear. I installed the app to check it out for i will be getting a wear compatible watch soon. The watch is currently connected to my phone but the android wear connecting notification is still there. And i do not have debugging enabled.
jndd333 said:
I have a chinese clone bt watch but it doesnt use android wear. I installed the app to check it out for i will be getting a wear compatible watch soon. The watch is currently connected to my phone but the android wear connecting notification is still there. And i do not have debugging enabled.
Click to expand...
Click to collapse
You answered your own question. If it's not compatible with android wear then wear is still going to be searching for a device to connect to
Sent from my XT1254 using Tapatalk 2
I did not have this issue when i first got the watch. I use a bt notification app and it syncs through that app. I installed wear a couple weeks after abd did not have this issue until after i uninstalled the wear app.
ok since no one else has helped I will bump this up again.I uninstall Android wear and all the other Bluetooth applications I tried with the watch I turn the Bluetooth off so nothing should be paired and I wiped Google Play services cache restart and its still trying to connect android wear.
jndd333 said:
ok since no one else has helped I will bump this up again.I uninstall Android wear and all the other Bluetooth applications I tried with the watch I turn the Bluetooth off so nothing should be paired and I wiped Google Play services cache restart and its still trying to connect android wear.
Click to expand...
Click to collapse
Why don't you post this in the android wear section? If you uninstalled android wear and it's off your phone I don't see how android wear can be requesting access unless there's a setting on your watch
Sent from my XT1254 using Tapatalk 2
Hi,
I'm using AA for about 4 weeks in my VW MY16. It's very nice! :victory:
However, I have some question: If I start the AA app, and after I connect the device to the car, then I can select the AA in the car screen. But, If I reboot the phone and I connect to the car, then the AA in the car don't connect.
So the problem is quite simple: Only if the AA app is launched in the phone, then it automatically connects to the car when you connect the USB wire to the car. You don't need to have the app in the foreground, only in the background. But when you reboot, the App don't start.
Someone knows a method for auto-launching the AA app when the phone is connected to the car?
It SHOULD be automatic. I have never heard of needing to have the AA companion app open.
What phone and Android version/ROM ?
mikereidis said:
It SHOULD be automatic. I have never heard of needing to have the AA companion app open.
What phone and Android version/ROM ?
Click to expand...
Click to collapse
Hi,
I have a Wiko Fever with stock Lollippop 5.1.
Please, try these tests:
1) Open AA, push HOME button (the App continues in background), and lock the phone. Then connect to the card and start it. Result: The AA opens in the car automatically.
2) Open AA, push HOME button (the App continues in background), select "running Apps", CLOSE AA and lock the phone. Then connect to the card and start it. Result: The AA don't start in the car automatically; you need to unlock the phone and start the AA app.
3) Reboot the phone. Don't open AA and lock the phone. Then connect to the card and start it. Result: The AA don't start in the car automatically; you need to unlock the phone and start the AA app.
It's the same in your case?
manos78 said:
Hi,
I'm using AA for about 4 weeks in my VW MY16. It's very nice! :victory:
However, I have some question: If I start the AA app, and after I connect the device to the car, then I can select the AA in the car screen. But, If I reboot the phone and I connect to the car, then the AA in the car don't connect.
So the problem is quite simple: Only if the AA app is launched in the phone, then it automatically connects to the car when you connect the USB wire to the car. You don't need to have the app in the foreground, only in the background. But when you reboot, the App don't start.
Someone knows a method for auto-launching the AA app when the phone is connected to the car?
Click to expand...
Click to collapse
In my Skoda Octavia MY16 when I connect the USB cable AA starts automatically in my phone Galaxy S6,
Then select the AA in the Infotainment menu.
I've been having to open the app before plugging my phone into my Hyundai Sonata. Unfortunately, it sometimes still doesn't launch in the car, so I have to unplug, force close android auto and then reopen. It's a pain to get it started up. I have a Note 4.
Sent from my Nexus 7 using Tapatalk
ireknole said:
I've been having to open the app before plugging my phone into my Hyundai Sonata.
Click to expand...
Click to collapse
That is! You need to open the AA app before plug the phone in the car.
war1 said:
In my Skoda Octavia MY16 when I connect the USB cable AA starts automatically in my phone Galaxy S6,
Then select the AA in the Infotainment menu.
Click to expand...
Click to collapse
That is because you first opened the AA app and it's running in the background. Try this: reboot your phone, don't start AA, plug the phone, start the car... You can select the AA in the Infotainment menu?
manos78 said:
That is! You need to open the AA app before plug the phone in the car.
That is because you first opened the AA app and it's running in the background. Try this: reboot your phone, don't start AA, plug the phone, start the car... You can select the AA in the Infotainment menu?
Click to expand...
Click to collapse
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
war1 said:
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
Click to expand...
Click to collapse
My test is:
1) Phone reboot
2) Unlock phone and connect to the car
3) Start the car
4) Try to select AA in the screen of the car
In this order, don't work with my car (VW MY16). I'll try your suggestion. :fingers-crossed:
Thank you!
war1 said:
I did those steps:
1 - I made a phone reboot
2 - I started the car and wait for the bluetooth sync
3 - I plug the phone
4 - Selected AA in the Infotainment menu
Always runs smoothly
Click to expand...
Click to collapse
You restart your phone everytime? That would get annoying.
I think the key is waiting until Bluetooth is connected before starting android auto. But even when I do that it sometimes still doesn't work in my Hyundai Sonata. I really haven't found anything that works consistently.
Sent from my SM-N910V using Tapatalk
ireknole said:
You restart your phone everytime? That would get annoying.
I think the key is waiting until Bluetooth is connected before starting android auto. But even when I do that it sometimes still doesn't work in my Hyundai Sonata. I really haven't found anything that works consistently.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
Not every time of course, I did a reboot just to test,:laugh:
ireknole said:
I think the key is waiting until Bluetooth is connected before starting android auto.
Click to expand...
Click to collapse
Starting AA companion app or AA in the car? Of course, if I start the AA companion in the phone, then the car connects (in my case is indifferent if the car is on after/before or if AA is started after/before Bluetooth).
My concern is: plug the phone and start automatically the AA companion app, even if you don't start it after you reboot your phone. This is the request!
Hi,
This really works:
1) Reboot phone and NOT start AA companion app.
2) Start the car, wait until Bluetooth is connected to the phone.
3) Connect the phone to the USB of the car.
4) Select AA on the Infotainment menu... IT WORKS!
I'll do more tests... typically I connect first, then I start the car...
manos78 said:
Hi,
This really works:
1) Reboot phone and NOT start AA companion app.
2) Start the car, wait until Bluetooth is connected to the phone.
3) Connect the phone to the USB of the car.
4) Select AA on the Infotainment menu... IT WORKS!
I'll do more tests... typically I connect first, then I start the car...
Click to expand...
Click to collapse
The rule is first wait for the bluetooth sync and then connect the usb cable because AA need the bluetooth for make calls.
war1 said:
The rule is first wait for the bluetooth sync and then connect the usb cable because AA need the bluetooth for make calls.
Click to expand...
Click to collapse
Not completely really,
After several tests with different order and reboots, I like to confirm that the AA companion app don't need to be started before connect the phone to the car. The KEY point is the BLUETOOTH (yeah!)! If the phone isn't paired with Bluetooth, or the Bluetooth is disabled in the phone, or (and this can be the annoying trouble for some like me) if the bluetooth connection is stalled in the phone... then the AA connection don't work.
So, my recomendation: You can connect the phone to the car in any order, but check Bluetooth if you have troubles.
:good:
I'm finding that even after Bluetooth is connected, it still doesn't start up. Today I tried unplugging and replugging the USB for about 10 minutes before it finally, for no apparent reason, decided to take and launch AA.
Sent from my SM-N910V using Tapatalk
I just read something on Twitter yesterday from Android support and it seemed to help. Go into the Android Auto app in the application manager and clear the cache. Once I did that, the app seems to connect better.
I also found that if I start the app and it doesn't connect, if I go into my active apps and clear out Android Auto, it will connect the next time I plug in the USB.
Sent from my SM-N910V using Tapatalk
I think all the car radios work differently. I don't turn on any Bluetooth, or run the AA before plugging. All I do is plug in, and the Bluetooth and everything else connects automatically. So I guess it all has to do with your initial setup.
Hi,
I used to be able to launch android auto on my galaxy s6 Skoda Fabia 2016. It also used to work with a galaxy s4.
About a month ago (or more), it stopped working:
When I connect the phone, AA is launched but the exists and the USB connection is reset. I can see in my task manager that AA is active in background.
I can connect with MirrorLink, but I rather use AA.
The car didn't go through any upgrades so I guess the blame is at AA.
I tried replacing USB cables, resetting the AA on my phone, changing USB connection from MTP to all other possible options... nothing helps.
Any ideas?
AA found that new version is available, but you are somehow frozen during inicialization.
Please provide following info:
1. AA version (go to Application Manager -> current is 1.6.281040
2. in Application manager press FORCE STOP for AA. If you have any cash data for AA, remove it
3. (OPTIONAL). IN skoda HeadUnit, go to settings -> Factory Reset -> Navigate to FUllink/SkodaLink/Whatever link and have reset of AA/Mirrorlink
4. check in mobile, that AA is not running. If yes, clear it from memory!
5. connect via USB, go to Headunit and launch Android Auto. You should go thru setup phase and everything should work.
Fast check if you need update of AA:
Launch AA application, if you see Update/Upgrade banner, you need to perform above. If you are unsure, create a screenshot and i can advise.
Mgx
skfree said:
AA found that new version is available, but you are somehow frozen during inicialization.
Please provide following info:
1. AA version (go to Application Manager -> current is 1.6.281040
2. in Application manager press FORCE STOP for AA. If you have any cash data for AA, remove it
3. (OPTIONAL). IN skoda HeadUnit, go to settings -> Factory Reset -> Navigate to FUllink/SkodaLink/Whatever link and have reset of AA/Mirrorlink
4. check in mobile, that AA is not running. If yes, clear it from memory!
5. connect via USB, go to Headunit and launch Android Auto. You should go thru setup phase and everything should work.
Fast check if you need update of AA:
Launch AA application, if you see Update/Upgrade banner, you need to perform above. If you are unsure, create a screenshot and i can advise.
Mgx
Click to expand...
Click to collapse
Thanks for the instructions but it didn't help
My AA version is 1.6.281040. No update\upgrade banner when I open the app.
I tried all of the above steps (force stop + clear data and cache + factory reset my car smartlink) but the result is the same:
When I try to connect the car- AA launches and immediately goes to the background and the connection fails.
Any other ideas?
How can I debug this?
questions
Hi,
1. before launching AA, is bluetooth on your phone activated and you are paired with Skoda HeadUnit? You should be able to make a call via HeadUnit with buttons on wheel/buttons on headunit. Working bluetooth connection is mandatory prereq for working AA yet (USB cable is just not enough)
2. USB cable - i have seen situations, when setup has been not working with long cable or chinese fake cable. Try to use short original factory cable 0.3m maximum from Samsung (should be white), this works
3. what ROM are you using? Its original rom from SAMSUNG? If yes, please indicate build number+version. If not, this may be problem as non-original rom doesn't support DPIchange yet.
4. You can enable devel mode. enable usb debugging on android side + in AA - follow http://www.androidexplained.com/android-auto-developer-mode/
5. do you see on mobile at least ANDROID AUTO label for second?
6. where are you located? S6 is oficially supported phone on SkodaHU, so you may also ask support from importer via dealer.
Hey,
over at the Mazda headunit project, with a opensource custom AA, there is problems too. It appears that a new version of "Google Play Services" broke AA.
Play services is a sort of API that broker things like GPS and USB for apps.
Last working version is 9.0.83. Your timeline fits with the issue of the affected versions. Please send a bug report to Google to get them to fix it : [email protected]
larxxor said:
Hey,
over at the Mazda headunit project, with a opensource custom AA, there is problems too. It appears that a new version of "Google Play Services" broke AA.
Play services is a sort of API that broker things like GPS and USB for apps.
Last working version is 9.0.83. Your timeline fits with the issue of the affected versions. Please send a bug report to Google to get them to fix it : [email protected]
Click to expand...
Click to collapse
That email just gives us a bounce back not sure if google receives you but you guys should post here!
https://productforums.google.com/forum/#!topic/play/tflL2_GCj4s
skfree said:
Hi,
1. before launching AA, is bluetooth on your phone activated and you are paired with Skoda HeadUnit? You should be able to make a call via HeadUnit with buttons on wheel/buttons on headunit. Working bluetooth connection is mandatory prereq for working AA yet (USB cable is just not enough)
2. USB cable - i have seen situations, when setup has been not working with long cable or chinese fake cable. Try to use short original factory cable 0.3m maximum from Samsung (should be white), this works
3. what ROM are you using? Its original rom from SAMSUNG? If yes, please indicate build number+version. If not, this may be problem as non-original rom doesn't support DPIchange yet.
4. You can enable devel mode. enable usb debugging on android side + in AA - follow http://www.androidexplained.com/android-auto-developer-mode/
5. do you see on mobile at least ANDROID AUTO label for second?
6. where are you located? S6 is oficially supported phone on SkodaHU, so you may also ask support from importer via dealer.
Click to expand...
Click to collapse
Bluetooth is working and connected to the car.
I tried several different USB cables (originals and non-originals) but none helped.
I'm using stock rom: 6.0.1 build number MMB29K.G920FXXU3DPEK
5. do you see on mobile at least ANDROID AUTO label for second? I see AA launches and then it moves to the background. I don't see the "Android auto" overlay that was usually there.
I'll try contacting Skoda representative but since nothing has changed in the car unit, I believe it's a software issue in the phone.
soulz said:
That email just gives us a bounce back not sure if google receives you but you guys should post here!
https://productforums.google.com/forum/#!topic/play/tflL2_GCj4s
Click to expand...
Click to collapse
Sounds like my issue. I posted in the forum link.
After reading through he posts in @soulz link, I found a solution:
https://productforums.google.com/d/msg/play/tflL2_GCj4s/Y5Ens5WxBwAJ
Basically, I disabled the following services:
ReschedulerUsingAlarmManager
ReschedulerUsingBroadcast
This needs root! but it works like a charm.
Now, all that's left to do is wait for Google to fix the play services issue.
I've tried three Roms (2 Oreo and 1 nougat) and I can't get Android Auto to work with any of them. Has anyone gotten Android Auto to work with any of the Roms available here?
Sent from my Nexus 6 using Tapatalk
It has worked well for me on the latest 7.1.2 Pure Nexus ROM. I am currently running AICP Oreo and it works great. It also worked on S.I.X. ROM Oreo and Republic of Madness Oreo ROMs for me.
What issues are you having?
Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?
imaGine00 said:
Hi, I've been running Android Auto perfectly with Nitrogen OS until 2 weeks. Suddenly I can't connect my N6 correctly anymore. My car (Ford with SYNC system) tells that it can"t find Android Auto. I tried Stock version of N6 Nougat, S.I.X Oreo rom and same issue..
Could it be related to some app update (maps, google, AA,...) ?
Sometimes I get a red error screen from AA app telling me about "communication error code 17" but I can't find any reference about that anywhere.
any tip ?
Click to expand...
Click to collapse
Have you tried a different cable? I had to try 3 of them before it worked right to start with in my F150
some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks
imaGine00 said:
some premium Anker cable fromage Amazon is supposed to arrive any Time soon but I have doubts because I already tried with different cables. What is your setup? AA, Google and maps version ?? Thanks
Click to expand...
Click to collapse
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?
AAuto works great on my N6 with LineageOS on my Kia Sportage. It's a brand new 2018 Kia purchased two days ago. One of the main reasons for that purchase was AAuto in the electronics package.
bfmetcalf said:
AA - 2.7.573953-release
Google - 7.15.19.21.arm
Waze - 4.32.0.2
I don't use google maps anymore now that Waze is available for AA.
One thing that may work is to delete your phone out of Sync and delete Sync out of your phone both under bluetooth and AA. Once you have them removed. Just plug the phone into sync and let it re-setup everything (I don't even pair bluetooth separately, I let AA do the bluetooth pairing).
What version # of Sync3 do you have?
Click to expand...
Click to collapse
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version
imaGine00 said:
pairing bluetooth with AA didn't work after deleting Sync and phone config :/
Sync continue to say it can't reach AA.. still waiting for the new anker microUSB cable
And I got same app version installed too
here 's my sync version
Click to expand...
Click to collapse
Try clearing data for AA and see if that helps.
Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk
Negotiator50 said:
Still can't get it to work in a 2017 Chevy Tahoe. I have now tried 4 different cords and I am currently on Six Oreo Rom. I know the head unit is compatible since I had it working with the pixel 2 xl during the brief time I had that phone.
Do I need to change any settings such as USB debugging? What setting should I set it to when I connect the cord (i.e. Transfer Files, etc)?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
This did the trick!! Thank you so much!
Sent from my Nexus 6 using Tapatalk
bfmetcalf said:
Try going into settings > six settings > Other > look for Enable MTP instead charging when connect to PC
Make sure that is UN-ticked. That will block AA from working for some reason.
Click to expand...
Click to collapse
woooooh that did the trick ! Thank you !!
I use it with crDroid 4.0 Beta 6 and everything work ...