Hey, do you guys get Android Auto to work fine on a car? I tried it recently with VW Passat and Opel Insignia (both 2017 models) It didn't connect to Passat, and was hanging every 2-5 minutes in Insignia. When it hung, it still worked on the phone, but the interface on the car got frozen and unresponsive.
JakubAnderwald said:
Hey, do you guys get Android Auto to work fine on a car? I tried it recently with VW Passat and Opel Insignia (both 2017 models) It didn't connect to Passat, and was hanging every 2-5 minutes in Insignia. When it hung, it still worked on the phone, but the interface on the car got frozen and unresponsive.
Click to expand...
Click to collapse
i recommend to take to service center
cause android auto is limited and it s not easy like phones to flash another firmware and etc
:good:
What do you mean by Android auto being limited? I am talking about the phone piece since it's quite clearly some issue with the phone - the same cars work fine with my girlfriend's Samsung
I have just got my P20 Pro, it seems like a great phone so far, but I have one nagging issue.
When I connect my phone to my car's (2015 BMW 3 Series) Bluetooth the now playing metadata of the audio being played is not being passed correctly. So if I play audio from Google Play Music or Pocketcasts the head unit on my car will show either Unknown Track or the track data of the first item on the album or the playlist. The audio itself sounds fine and I am able to skip tracks, select new albums from the car's controls, so it seems some information is being passed correctly, it is just that the info of the track that is currently playing seems to not be working.
Has anyone else encountered this?
At this point I have to assume it is the phone, as my Galaxy S6, S7 & S8's all worked, but I guess it is technically possible that could have been a workaround put in by BMW as they were such popular phones. Hopefully Huawei will sort this out, it may be an underlying Oreo issue as threads like this suggest that Bluetooth issues were around when 8.0 launched https://productforums.google.com/forum/#!topic/nexus/E9Q2lyFYRgI
I have done some more digging on this issue and I suspect that is might be something to do with the Bluetooth AVRCP version that the phone is using. Normally in Android (since 8.0) you could adjust the AVRCP version from within Developer Options, but for some reason this is not available on this phone. My Galaxy S8 was using AVRCP 1.4, so I suspect that this phone is using 1.5 or 1.6 and my car does not like it.
I have emailed Huawei to ask for clarification. At this point it is the only real issue I have with the phone, but it will annoy me if it isn't resolved quickly. I'm going to pester BMW too to see what versions of AVRCP they officially support.
Don't have these issues in the car, head display current track etc via Bluetooth ... Use this in a Nissan
Everything works as it should with my Pioneer headunit using Spotify
I just posted something related (possibly) in the RAM/Battery Management thread - I have issues with the Audi MMI Connect app, losing connectivity and so on.....does seem that the P20 Pro handles Bluetooth (no rsap?) and background process management quite differently to my previous phone (Galaxy S8+)....also hoping quick resolution, as love the phone!
Search facility not working in car
Hi
I've just put music onto my P20 pro and it plays fine on the device and the car, however, I can't use the search facility on the car (BMW, 3 series, 2017) to change track. I can do this on the phone. Any suggestions? I put the music onto the 'Music' app (dragged and dropped from my iTunes folder- don't know if this is relevant. Any help would be greatly appreciated as without being able to use the car's search facility and come in and out of albums/ artists is useless. Should I have put the music into somewhere else?
JQ
P20 PRO and BMW - bluetooth issue
Bojanglez, did you find a solution? I got the same issue with P20 PRO and BMW X4... so it seems a problem linked to that phone connected to the BMW multimedia system.
With my previous phone, an ASUS Zenfone, everything was fine.
It may be a BMW issue to, maby P20 pro isn't compatible with BMW or Audi. I know that some manufacturers put all in to be compatible with ios and some larger manufacturers of phones. It could be that car manufacturers don't test Huawei phones and don't support them.
Skickat från min CLT-L29 via Tapatalk
No Huawei Garbage bloatware issue, my is random something is normal, most times it plays music but gets stuck on providing music playing info.
Same issue here with my 2016 Toyota rav4. It plays the first track and shows the metadata but then as the tracks keep playing the metada remains the one of the first song. Definitely an issue with Huawei. Their music player works just fine. I think it has to do with the poor Google integration and their need to force that half baked apple wanna be emui down our throats. It should be Oreo but looks and feels like gingerbread.
Hi all, I have an update. I have resolved the issue, but not quite sure which of the following specifically fixed it.
Huawei software update
Renamed by phone in Bluetooth settings
Updated to the latest BMW firmware (from their site)
Messed with some of the Bluetooth settings in Developer Options on the phone
Unfortunately I did all these at pretty much the same time so I can't say for certain which one fixed it, I think it was the Huawei software update as after I updated my BMW firmware I still had the same issue and also in other BMWs I tried. I also noticed that the Bluetooth was dropping constantly in my wife's Puegeot 3008 so that's why I played with the Developer Options. For anyone interested I havethe following now set:
Codec: SBC
sample rate: 44.1khz
channel mode: Stereo
LDAC playback quality: 990kbps/909kbps (optimised for connectivity quality)
HWA playback quality: Best effort (400KB Optimised for connectivity)
HWA Latency: 50-100ms
So I now have track information and basic controls using Google Play Music and Pocketcasts. It does not seem to like letting me browse my library though, but it is at least functional.
Also I changed my car, this was not because the BT didn't work It worked in my 2015 3 series before I changed it. I now have a 2018 4 series and the behaviour is the same, track listing and skip functionality but no browsing.
I have installed the most recent firmware update on my 2 Series 2017, I see two fundamental issues. One is, by using your phone normally, no issues should arise most of the time but still random sync issues with metadata can occur. The second issue is, no matter how good your phone behave and how well synchronized the metadata is, once you open Android Auto app, everything goes to hell and you are back in square one.
To fix it, you should deactivate auto start when connected in the app (or not using it at all), erase your car from devices in bluetooth config within your phone. Erase your phone from the list in your car. Change the phone name. Start over with the synching process. Check for correct metadata in the car. If not working repeat. That should fix the problem eventually.
If you like very Android Auto very much, get used to see the songs information in your phone screen rather than the car.
I am also having the same problem, Huawei P20 Pro and Sony XAV-601BT head unit. I've tried enabling all the permissions in Spotify, cycling the connections, renaming the phone.
i have Pixel 3xl with Android 10, - Bluetooth connects fine there is no metadata - song info. this problem started with 8.1 Android version and I have not been able to get it to work. I really cant believe google cant fix this issue or even aware of it. plenty of threads on google. I think they all use Iphone, i am guessing ...this is very annoying. I have change the avrcp version from 1.4 to 1.6. no luck, also I read that turn off battery optimization on Bluetooth. no luck. anyone else here having similar issue??
In Android Auto, When I'm listening some music from my phone and having G. Maps on the screen, there's always some lags in music when the map's moving (like in an higwith exit road)
I have a rooted Pixel 3 and a Mazda 3 2018 (Android Auto from MZD AIO)
I've seen in developper's options many options about bluetooth, what should be the best parameters?
Thanks!
I see the same thing when using my Chinese dongle on my android head unit. I've played around with developer settings in Android auto and the settings on the dongle and nothing seemed to help. It seems to be something low level in the dongle (in your case the head unit or mod app) that causes this where moving the map seems to overwhelm to the system.
Using the same headunit and phone but instead using Emils' head unit reloaded application I do not get any sound issues, even when running in 720p mode.
It seems like the issue we're seeing is more to do with the Android auto implementation in hardware/software.
Ok, I'll try it and see how it's going. Thanks
I posted this on the AA support page but didn't get an answer so I thought I'd seek help here.
Error message: None
Are you using Android Auto on your phone screen or car’s display? Car's Display
Car / head unit make & model: 2018 Honda Pilot EX
Phone make & model: Pixel 4
Android OS version: 10
Android Auto app version: 4.7.593824-Release
Google Play services version: 19.6.29 (120400-278422107)
Morning of the 13th, after 60ish seconds I lost all audio.
Worked fine from pixel 4 release until now. And worked with my Pixel 2 before that.
Tried:
-Unplugging and replugging in. AA does launch but no audio.
-Bluetooth: Removing phone from car and car from phone. Will work for 60ish seconds then quit.
-Audio DOES work with Bluetooth outside of AA.
-Uninstalled AA updates then reinstalled.
-Uninstalled GMaps Beta went back to release but no good.
-reinstalled GMaps beta no good
Android Device Policy was updated the previous night.
Also have a Samsung Galaxy S2 watch paired. Tried turning watch off and restarting AA but no good.
Rolled AA back to the previous version and it works. Unfortunately I'm back to the old interface.
Today found that Do Not Disturb was enabled with the update on the 12-13th which caused no audio.
I have a new Subaru Outback 2020. My Samsung S8 connected to AA with no problems. I just got a new Samsung Note 20 5G, running Android 10. Now Android Auto is not launching the map. I get voice driving instructions but no map. I see on my phone, a notification saying the phone is connecting to AA, but it eventually goes away and still no map shows on the head unit. I've tried several different USB-C to USB-A cables and none of them help with this issue.
Google marketing says they've improved AA access by combining it with the Android operating system. Unfortunately, they don't seem to have done sufficient testing with this change. Typical of software giants sending out updates without full testing and ensuring it's FULLY functional.
GOOGLE: Get your act together! This is a serious issue. AA is supposed to aid drivers and the map on the head unit stops individuals looking at their phone. Well, you've just increased the chance of a crash now. It won't surprise me if GOOGLE gets sued for someone's death.
If anyone finds an update or resolution to this problem, PLEASE post the fix!!!
PS: We should not have to go through this ridiculous back and forth just to link Android Auto from our phone to our car. This is the 21st century, is it not? We send people to the moon, have smart(?) applicances, and even self-driving cars. Surely, we should be able to get a simple mapping system to show up on a car head unit (with voice directions too)!