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 there!
Does anyone succeed in having two phones working with AA ? One stays connected permanently to AA, the second one is connected to BT for calls and texting.
My experience is that even if both are correctly connected when they are alone, once together all is a mess. As soon as the second phone gets connected to AA, the first one gets deconnected from BT.
I tried to break BT connection within the second phone. It gets connected anyway to AA, but this didn't solve the issue. The first one was ejected from BT,stating that another device was already BT connected (even if BT is broken).
Any help ? BT Mac address modification on the first phone to match second phone ?
Thanks in advance !
i been toying with the idea to do this.
sorry i just need to ask, even you disable auto connect Bluetooth in AA setting?
Sent from my HUAWEI MT7-TL10 using Tapatalk
ahhl said:
i been toying with the idea to do this.
sorry i just need to ask, even you disable auto connect Bluetooth in AA setting?
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Haven't tried yet but surely a good idea ... On my way to test !
When you say that you've been toying, do you mean you get it to work or not ?
My purpose is to use a Nexus 7 2013 (not LTE version) as a permanent device connected to AA, and use my phone connected to BT, thus to avoid plugging/unplugging ...
No joy ... Using BT or not has no effect ... Phone is deconnected when tablet is connected to AA...
DR400 said:
Haven't tried yet but surely a good idea ... On my way to test !
When you say that you've been toying, do you mean you get it to work or not ?
My purpose is to use a Nexus 7 2013 (not LTE version) as a permanent device connected to AA, and use my phone connected to BT, thus to avoid plugging/unplugging ...
Click to expand...
Click to collapse
i tried...
it seems the Bluetooth still auto connect.
theres go my plan
any other way to delete pairing. maybe it work. just my guess
Sent from my HUAWEI MT7-TL10 using Tapatalk
ahhl said:
i tried...
it seems the Bluetooth still auto connect.
theres go my plan
any other way to delete pairing. maybe it work. just my guess
Click to expand...
Click to collapse
Deleting pairing has no impact. I even succeeded in breaking BT to avoid AA to wake it up but no joy either.
Whenever AA gets connected to the phone (via USB), any other BT connection is rejected stating that another device is already connected ...
Spoofing BT Mac address of soon to be BT-connected phone with the one of AA-connected phone might be a solution ? But not enough geek to try this one...
Seems strange nobody came across this idea ... please help if you did !
I worked it out, permanently disabling the Bluetooth using root. I described it in this thread.
https://forum.xda-developers.com/an...droid-auto-maps-spotify-iphone-calls-t3746308
Pixege said:
I worked it out, permanently disabling the Bluetooth using root. I described it in this thread.
https://forum.xda-developers.com/an...droid-auto-maps-spotify-iphone-calls-t3746308
Click to expand...
Click to collapse
Tried that already... Disabling BT doesn't prevent HU from detecting and kind-of BT pairing the device, ejecting in the same time the phone ... At least in my situation...
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
i been toying wirh aa2. 9 or aa3. 0 because of non working issues
i accidently noticed my bt does not connect to my car but aa2. 9 still works.
i need to replicate this again.
if this work, 2 phone can still works
Sent from my HUAWEI MT7-TL10 using Tapatalk
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
Please what application to spoof BT MAC Address you did you use? I can find application only for wifi MAC ardress changing.
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
Try using "app quarantine". This it the only application that really stoped my BT for good.
So success with 2 phones?
Do you need to be rooted to spoof the BT MAC address?
Thanks
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
DR400 said:
I reply to myself.
I found out a solution.
Strangely, disabling BT did not solve my problem. It seems that the headunit was retrieving information gathered at the first connection...
I then decided to hard reset the headunit. When asked to connect phone to BT, I complied.
In the meantime, I spoofed the BT MAC Address, copying phone's one to tablet. Now they both have the same BT MAC Address.
When tablet was plugged into usb for AA connection, the phone stayed BT connected. It worked and works since then.
Application to spoof BT MAC Address could be easily found on the G market.
Click to expand...
Click to collapse
Thanks for this.
I kind of have it working but cannot control the phone connected by BT from the head unit (which still tries to make calls from the phone connected via AA).
Calls made directly from the phone do however go through the head unit.
Is there a way to control the BT phone via the head unit with the other phone connected via AA?
Android Auto on the navigation screen, iPhone connected via bluetooth for phone calls. VW Passat B8 2016
thank you to Pixege !
the method described it realy works (tested on Galaxy S7 and galaxy S5) in function on galaxy S5
it works ok if tha main phone it is conected in HFP mode
but because I have and rSAP mode and I'd like it want to use this type of conection but here are some problems..
the reason it is because I try to build from a galaxy s5 SM-901F (6.0.1, version MMB29M.G901FFXXU1CQE3 rooted with chainfire ) a standalone device im my car for use android auto in the car independent of my normal phone (galaxy S8)
so I want to use in the same time 2 android phones but both want to conect by bluetooth to the car (VW Discovery Pro)
to do that I disable via Esentiale root bluetooth proceses I found and works fine if the main S8 it is conect by HFP protocol
but if s8 is conected by rSAP (and I want to be conected by rSAP) when the second phone is conected by usb(with blutooth off) somehow disconect the sim from main S8 phone (but on the phone show like the rsim it is still working) but not conect to the second phone
if I first conect the android auto (S5) and after connect the phone (S8) rhe rSAP conection works fine
if I first conect the phone (S8) and after connect the android auto (S5) the rSAP conection not work on S8
anyway I want to disable the rsap on the galaxy s5 , how can I do this?
i solved in this way
https://forum.xda-developers.com/an...general/car-dialer-instead-aa-dialer-t3809621
deleted. wrong response..
I would like Android Auto to be available directly after USB connection has been established. Right now I need to unlock my phone before I can select Android Auto on my cars head unit. Optimal would be that the phone does not unlock, but simply just lets the car communicate as what is needed for Android Auto to work.
Also it would be nice if phone "unmutes" automatically if muted before USB connection made. Or if possible to unmute on cars headunit.
This is because my phone is placed in a location in the car where it is difficult to operate when connected to USB.
Not sure if I am clear in my question, but please feel free to ask for further info if needed.
Regards, Lars.
If this isn't happening by default (it does on my devices), check Android Auto (Phone) > Settings > Connected Cars, your car should be "accepted".
If this still doesn't do it, you'll likely have to use Tasker, or change the USB settings on the phone itself
Hi everyone and sorry if my first post has been covered before, but I couldn't find a post that exactly replicated mine.
I have a Kenwood Head unit, model number DMX8020DABS which is Android Auto compatible. My phone is a Samsung A20e running Android 10.
I cannot for the life of me connect my phone to the head unit either by usb cable or wirelessly.
I have had a friends phone iphone connected to the carplay on the unit and also a Samsung Galaxy S10 also, both connected wirelessly as soon as the bluetooth connection was made. This leads me to think my phone is not compatible. I have read about various compatible phones connecting wirelessly and can't see mine in a list anywhere, but I have also read any Android phone with Android 10 should be able to connect via usb cable.
I obviously have the Android Auto app built in to the Android 10 software, one question is do I need to download the Android Auto for phone screens app also?
When I plug my phone into the usb connection to the head unit the phone acknowledges it and the Android Auto app comes up and says follow instructions on car screen, but when you press Android Auto on the kenwood unit the wheel just keeps spinning and it says 'processing' and nothing happens. I have tried resetting the unit, uninstalling/re-installing the AA app, restarting the phone, everything.
Am I missing some settings, not set properly? One thing I noticed in the phone, when you connect the phone and pull down the drop down menu on the phone if you tap on the usb connection settings a screen comes up usb controlled by connected device or this phone, it is set to this phone, and one of the options is Transferring files / Android Auto with a button next to it, when I try to activate that button it won't check it just goes off, even though this is preset in the settings>developer options>networking>default usb configuration where the button is checked.
I have been trying for days to get this to connect. As an aside, my bluetooth connection is fine the unit can make calls and play spotify from my phone, it's just Android Auto that's not working.
Do I need a to get a new phone? Any ideas or advice would be welcomed. Thanks for reading.
Hello everybody. i have a rooted samsung note8. I always keep it connected to my car. the problem is that when I turn on the car, the request for authorization for the connection between the phone and the car appears on the display every time. it's really annoying to have to click "allow" every time. is there any way to force this once and for all? thank you so much
Can anyone help me?
If the car asks the authorisation you can't do nothing.
Instead, if the authorisation popup is on the phone maybe you can try to do something with tasker
"Request for authorization?" Are you talking about the pop-up a head unit brings up when a new phone wants to connect to Android Auto?
Perhaps try pairing via Bluetooth, like it's a phone which doesn't do AA (just to get it to remember your phone). In any case, sounds like an issue with the car's headunit. You could also see if it has some way to forget previously connected phones or do a "factory reset."