Database Info

Android Auto on Galaxy S7 not working with Pioneer AVH-X8700BT

i have a Pioneer AVH-X8700BT and it is both IOS Auto & Android Auto compatible.
Problem is it works fine with an iphone 6s but when i tried it with my new samsung galaxy s7 nothing works!
i tried using both Android Auto and the Mirrolink mode but both nothing.
Tried restarting both car device and phone but nothing.
Also tried with a samsung galaxy s6 and also nothing.
Any ideas?

Same issue here.
My S7 won't connect via Android Auto either. (VW Golf)

Do you have a setting inside the radio for pairing? At least with my radio you have to activate pairing to see the radio

Had the same problem with my S7 Edge from Verizon with my Pioneer 8100NEX. Finally figured out that I have to change the USB options to get it work. After you connect the USB cable, pull down the notification drawer and look for "Connected for charging" notification". Tap that and change "Use USB for" to "Transferring media files". Android Auto worked after that for me.
I didn't have to do this with my S4. Unfortunately for the S7 I have to do this every time I connect my phone. I found this thread because I'm looking for a way to make it the default but haven't had any luck yet.

I had the same problem. Thanks for posting this. Now I also am looking to set the default functionality. Crazy to have to manually switch this every time.
Thanks,
kt

marshmallow problem
[email protected] said:
I had the same problem. Thanks for posting this. Now I also am looking to set the default functionality. Crazy to have to manually switch this every time.
Thanks,
kt
Click to expand...
Click to collapse
If this works for you to connect - the default functionality can be found under developer options. You can manually force charging, MTP etc there. USB debugging - off / USB configuration - MTP
This is a known official marshmallow issue not isolated to GS7 , LGG5 has same issue listed in google support page. some devices (like my GS7) will not connect after switching USB connection options. I have tried every mode and mine will not work - need a more advanced workaround. I also can't root phone because of corporate network restrictions.

Anyone have an update on this? I have the same issue using Galaxy S6 Edge Plus. I've enabled the developer options and enabled USB Debugging and MTP for the USB connection type with no success. I also can't change options with the connection type in the notification panel.

S-P-R-O-U-T said:
Anyone have an update on this? I have the same issue using Galaxy S6 Edge Plus. I've enabled the developer options and enabled USB Debugging and MTP for the USB connection type with no success. I also can't change options with the connection type in the notification panel.
Click to expand...
Click to collapse
My S7 Edge Duos seemed to require the disabling of Car Mode as it was interfering with AA's connection. It's a default Samsung piece of unneeded. You can download "Package Disabler Pro for Samsung" from the Playstore. It will allow you to disable apks and stubs without root. I disabled Car Mode and now AA works with the Pioneer 8100 I have. the S7 worked fine with the wife's '16 Accord and AA which was my sticking point. I guess the Pioneers support Car Mode and Mirrorlink so it confuses the hell out of the deck. It's worth the 0.99 cents to see if this works for you. You can also disable all the other bloatware you don't want with it. So it's kind of a win/win for a buck.

Hi I have a Pioneer AVH X8890bt and I want to connect my s6 edge to appradio, however, everytime i plug my phone to the usb it gets connected to android auto, Could anyone guide me as to how to establish a connection. Also, there is a HDMI port at the back of my system and I have learnt that to connect a samsung device you need miracast dongle, so if I buy a dongle will i be able to use the touch function of my car audio or everytime I will have to be dependent on my phone. Please advice.

Always losing bluetooth connection since update

Since the Oreo and Wear OS updates I've had severe connectivity issues which didn't exist beforehand. I thought I had cracked it with a factory reset of the watch and removal + reinstallation of the phone apps...
However for days now my watch hasn't been showing as connected in my phone's bluetooth settings but it has been showing as connected in the Wear OS & Huwaei Wear apps and I had been getting messages on the watch etc so I thought nothing of it. Just now I tried to make a phonecall using the watch and it said the call couldn't be made, check my bluetooth connection. So despite both phone apps saying that I was connected and the phone's BT saying that I was connected (*for a change!) there was some issue. I switched BT off & back on again on the watch and then I could finally make the call.
Buggy!
Is anyone else experiencing these phantom connectivity issues between their watch and phone since the latest updates?

I have the same problem, I did not come to the repair

I have the same problem and i found a temporary solution for it. Switch on and switch off aeroplane mode.

Same problem here. I have the 4G version of the watch and now am always connected in 4G, the bluetooth is indicated by the phone (Huawei Mate 10 Pro) as connected in the system settings, but is not connected neither on the watch nor on Wear OS app.

same problem here

Bluetooth losing connection
Here's the solution:
1) unpair watch from phone
2) delete Bluetooth app's cache on phone
3) reboot phone
4) repair watch with phone
Since I did these steps I have had no issues with Bluetooth connectivity...
Hope it helps you....

Bluetooth not working after latest LineageOS update

A few months ago (I forgot exactly when), I updated to the latest available herolte LineageOS build for my (rooted) S7.
As I use a Samsung Gear S2 Classic smartwatch, I went about updating build.prop to make the Galaxy Wear app work on my phone (the app works out of the box on everything except flashed Samsung phones, which is circumvented by replacing 'samsung' with 'htc' in build.prop). However, my watch would not connect anymore, despite resetting my watch, reinstalling the app, etc etc. It simply did not show up on the menu. Then I noticed that I was also unable to connect to my bluetooth speaker as well, despite it being on and working perfectly fine as before with my laptop. Scanning for bluetooth devices simply shows nothing. The smartwatch would show up for very short periods of time and then disappear again, the bluetooth speaker is still listed as 'paired' but attempting to connect to it does nothing.
So, my Bluetooth is broken after this update and I have no idea how to begin fixing this. I have not attempted reflashing my phone yet. Does anyone have any solutions or suggestions for troubleshooting?

Gear S3 connectivity issue

Hey guys,
So I have a Gear S3 Classic and a Galzxy Note 9 on Pie OS and I'm running through a connectivity issue every once in a while.
Basically if I don't connect my watch to my phone in a day or two, the next time I try to connect it it gets stuck on the finishing pairing screen on Galaxy Wearable, if I try to connect it from the Bluetooth settings, it says connected for calls except that it won't show it as connected on the companion app.
Also when I clear data/cache of the companion app it connects instantly but it tells me that I have to reset the watch as you can see on the screenshot. I can still fully use my Gear S3 even with that error message but I can't use the Galaxy Wearable app. So each two or threee days I have to reset my watch to keep using the Wearable app correctly.
Any ideas as to why this keeps happening? I only have this issue with my Gear S3 all the other Bluetooth equipements that I use connect just fine.
Any help is appreciated.

Screenshot.

Question Can't connect watch to. phone.

Hello All,
When I'm trying to connect watch via nfc. It just triggers a nfc tag request.
I tried to pair via bluetooth but as soon as It is paired the samsung wearable throws sn error"Unable to install : unexpected error".
Please guide.

What kind of phone do you have?

Try clearind system cache, and a network reset for starters...