Database Develop

[Q] Is Bluetooth AVRCP 1.3 Working?

I am just wondering if anyone has had success getting Bluetooth Track metadata to be listed when syncing to bluetooth devices such as ones found in our cars. I have a Ford Focus and when I send media to the Ford Sync system using things like Pandora or BeyondPod, the only information listed is "Unknown" under the bluetooth category.
I know that this in particular was an Android issue and was not support through Android until 4.3 Jelly Bean. My previous phone was a Galaxy S3 rooted with Tasks latest rom running Android 4.3 and that device works properly. It syncs immediately with the car stereo and track listings are displayed properly as well as incoming text messages display on the screen.
This is not the case with my brand new Galaxy Note 3. I assumed that since it was running Android 4.3 and supported the newer bluetooth standards that it would perform similarly. That might have been my first mistake...assuming....but is anyone else having similar issues? Can someone point me in a direction that I might be doing something wrong? Im really hoping its just a setting I am missing and not something that Samsung decided to leave out or forgot about.
Thanks in advance.

Vgamer4550 said:
I am just wondering if anyone has had success getting Bluetooth Track metadata to be listed when syncing to bluetooth devices such as ones found in our cars. I have a Ford Focus and when I send media to the Ford Sync system using things like Pandora or BeyondPod, the only information listed is "Unknown" under the bluetooth category.
I know that this in particular was an Android issue and was not support through Android until 4.3 Jelly Bean. My previous phone was a Galaxy S3 rooted with Tasks latest rom running Android 4.3 and that device works properly. It syncs immediately with the car stereo and track listings are displayed properly as well as incoming text messages display on the screen.
This is not the case with my brand new Galaxy Note 3. I assumed that since it was running Android 4.3 and supported the newer bluetooth standards that it would perform similarly. That might have been my first mistake...assuming....but is anyone else having similar issues? Can someone point me in a direction that I might be doing something wrong? Im really hoping its just a setting I am missing and not something that Samsung decided to leave out or forgot about.
Thanks in advance.
Click to expand...
Click to collapse
It works on Note 3, in fact it works on all 4.3's now, I've had this issue on Nexus 4 and the last few new updates it started working.
You can see the name of song and artist and so on...

odeccacccp said:
It works on Note 3, in fact it works on all 4.3's now, I've had this issue on Nexus 4 and the last few new updates it started working.
You can see the name of song and artist and so on...
Click to expand...
Click to collapse
Thanks for the reply. I have had it working on a couple of 4.3 devices now, including my own Galaxy S3 running 4.3 and on all of those devices I really did not have to do anything besides sync the Phone with the device and send a Pandora track to it. Did you confirm it is working on the Note 3 in particular, and if so, did you have to turn any settings on or do anything special to get it to send the data?
As of right now, the song is played by the bluetooth device but no track information is displayed. This is also supposed to work for text messages, however I dont see that information displayed either. I want to confirm it is working on these Note 3 so I can try and narrow down a software or hardware issue.

Doesn't work on my Note, syncd with a Kenwood DDX429.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Vgamer4550 said:
Thanks for the reply. I have had it working on a couple of 4.3 devices now, including my own Galaxy S3 running 4.3 and on all of those devices I really did not have to do anything besides sync the Phone with the device and send a Pandora track to it. Did you confirm it is working on the Note 3 in particular, and if so, did you have to turn any settings on or do anything special to get it to send the data?
As of right now, the song is played by the bluetooth device but no track information is displayed. This is also supposed to work for text messages, however I dont see that information displayed either. I want to confirm it is working on these Note 3 so I can try and narrow down a software or hardware issue.
Click to expand...
Click to collapse
Maybe S3 did not the lates updates.
Nexus 4 is like the lates you can get them, and NOTE 3 just came out so should have latest.
I can confirm BT work amazing with all the proper displaying, SMS, pictures in phonebook and so on on my NOTE 3 N900W8 and my Ford SYNC, touch, latest firmware.
I did not have to do anything special, just paired and done.
Voice clarity and sound volume are amazing.
One problem BT creats a wakelocck "bluetooth_timer" trying to figure it out why.

Thanks for that.. So we have a Note 3 that works and one that doesn't. My Note 3 is an N900A on ATT..... I wonder if there is a carrier software issue at play here?
Can anyone else on different carriers confirm or deny the functionality of this feature?
Sent from my SAMSUNG-SM-N900A using Tapatalk 4

My n900a works great on my Kenwood ddx480
Sent from my SAMSUNG-SM-N900A using xda app-developers app

I get some bluetooth crashes when I try to use apps with bluetooth metadata, such as the Spotify app that I modified to have bluetooth metadata... It works on every device I have except the Note 3... I get an error that says Bluetooth share has crashed every so often when I try...

hotbyz168 said:
My n900a works great on my Kenwood ddx480
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
After a bit more testing, it looks like my text messages on my N900A actually do work with the car bluetooth unit. Which makes things a bit more odd since I know that before I got 4.3 on my S3, I was not able to receive any information on the display. Once I upgraded to 4.3 then everything just started working.
Since your N900A seems to work properly it makes me wonder if something is wrong with this particular phone. I'll have to test with a friends Note 3 and see what happens.
What apps were you using that worked properly? Did you do anything special (i.e. settings, app settings, etc) or like previously mentioned, did you just sync the phone and everything started working?

Vgamer4550 said:
Thanks for that.. So we have a Note 3 that works and one that doesn't. My Note 3 is an N900A on ATT..... I wonder if there is a carrier software issue at play here?
Can anyone else on different carriers confirm or deny the functionality of this feature?
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
Click to expand...
Click to collapse
Try looking if there is a new soft for the car.
Also I've checked the "bluetooth_timer" wakelock problem, and if you press "cancel" when phone asks you to allow messages, and you don't check markalways allow for the phone book, the wakelock is not a problem. Also don;t set phonebook to auto download if you have the option, just do one time download.

odeccacccp said:
Try looking if there is a new soft for the car.
Also I've checked the "bluetooth_timer" wakelock problem, and if you press "cancel" when phone asks you to allow messages, and you don't check markalways allow for the phone book, the wakelock is not a problem. Also don;t set phonebook to auto download if you have the option, just do one time download.
Click to expand...
Click to collapse
Thanks for the suggestion, unfortunately I just upgraded the car software to the latest release as of last month. I also ruled that out because the S3 is working just fine. Where before it was on Android 4.3 I would not see any info on the screen.
At this point I might be leaning towards a defective phone, due to text messages appearing on the screen but no metadata, but I will try some more testing. I have access to a second Note 3 that I will try to sync up and see what happens.
I am hoping I get some more feed back before I resort to replacing the unit. We shall see.

Vgamer4550 said:
Thanks for the suggestion, unfortunately I just upgraded the car software to the latest release as of last month. I also ruled that out because the S3 is working just fine. Where before it was on Android 4.3 I would not see any info on the screen.
At this point I might be leaning towards a defective phone, due to text messages appearing on the screen but no metadata, but I will try some more testing. I have access to a second Note 3 that I will try to sync up and see what happens.
I am hoping I get some more feed back before I resort to replacing the unit. We shall see.
Click to expand...
Click to collapse
that sucks, but I highly doubte it's the phone defect, it's just software of the car or phone. Best bet is to wait for CM ROM for this phone CM worked always best for me re: car bluetooth.
Also some cars are just bad that way I tried my Nexus 4 on brand new Infinity FX fully loaded everything, the phone would not even connect to their system
My friend has Infinity EX35 2008, his Andorid phone would not allow him to play music through BT or cable, but I gave him my old crappy Iphone 3G and it works perfectly.
Try googling your car's smartphone supported list. Like this but for your car: here
My best suggestion keep the phone try not to get bothered by this and eventually it will work, I had to wait for about 5-6 month till it started working again. It all has to do with software updates and BT files.

odeccacccp said:
that sucks, but I highly doubte it's the phone defect, it's just software of the car or phone. Best bet is to wait for CM ROM for this phone CM worked always best for me re: car bluetooth.
Also some cars are just bad that way I tried my Nexus 4 on brand new Infinity FX fully loaded everything, the phone would not even connect to their system
My friend has Infinity EX35 2008, his Andorid phone would not allow him to play music through BT or cable, but I gave him my old crappy Iphone 3G and it works perfectly.
Try googling your car's smartphone supported list. Like this but for your car: here
My best suggestion keep the phone try not to get bothered by this and eventually it will work, I had to wait for about 5-6 month till it started working again. It all has to do with software updates and BT files.
Click to expand...
Click to collapse
I thought of that too, just wait for software patch or CM. Its my OCD that is getting in the way. The phone seems to work fine otherwise. I know its a little thing and it could also just be that the phone is newer then my car and car software so it may just take some time to get the kinks worked out.
I'll give it a few more days and see who else replies before I do anything rash I did live with the S3 just fine with no metadata before it got upgraded. Thanks for taking the time to reply. I'll keep your wakelock suggestions in mind as well.

Vgamer4550 said:
I thought of that too, just wait for software patch or CM. Its my OCD that is getting in the way. The phone seems to work fine otherwise. I know its a little thing and it could also just be that the phone is newer then my car and car software so it may just take some time to get the kinks worked out.
I'll give it a few more days and see who else replies before I do anything rash I did live with the S3 just fine with no metadata before it got upgraded. Thanks for taking the time to reply. I'll keep your wakelock suggestions in mind as well.
Click to expand...
Click to collapse
No problem, I've had lot's BT issues and been trying to solve then over the years. It's surprising not that many people use phones here with car BT's like that, so not many replies
Re: Wakelock, install this and see if you even have the problem, it would be in Kernel Wakelocks.
Also what car do you have? I'll keep an eye out if I hear anything, I'll let you know.

odeccacccp said:
No problem, I've had lot's BT issues and been trying to solve then over the years. It's surprising not that many people use phones here with car BT's like that, so not many replies
Re: Wakelock, install this and see if you even have the problem, it would be in Kernel Wakelocks.
Also what car do you have? I'll keep an eye out if I hear anything, I'll let you know.
Click to expand...
Click to collapse
Ford Focus Titanium 2013, I really appreciate it.
It always makes me laugh when I see so many people who have bluetooth in their vehicle or a fancy smartphone and have no idea what they can do together Its a curse being the tech guy and knowing what things can do and agonizing over some specific issue that the normal person/user doesn't even realize is there. I.E. metadata on the display.
Me: "The phone isn't working right"
Normal Person: "Does the car play the song?"
Me: "Ya"
Normal Person: "Then what's the problem"
Me: "Its supposed to do more tho...gahhhh"

Vgamer4550 said:
Ford Focus Titanium 2013, I really appreciate it.
It always makes me laugh when I see so many people who have bluetooth in their vehicle or a fancy smartphone and have no idea what they can do together Its a curse being the tech guy and knowing what things can do and agonizing over some specific issue that the normal person/user doesn't even realize is there. I.E. metadata on the display.
Me: "The phone isn't working right"
Normal Person: "Does the car play the song?"
Me: "Ya"
Normal Person: "Then what's the problem"
Me: "Its supposed to do more tho...gahhhh"
Click to expand...
Click to collapse
Hahah
I used to contact SYNC support and the answers where just crazy, that's when I started to do it myself, my problem is I don;t know Linux well

Can anyone else confirm or deny how well the AVRCP 1.3 is working on their Note 3 to show track information on their bluetooth devices.?
Please list model and carrier if possible.
Sent from my SAMSUNG-SM-N900A using Tapatalk 4

DanMc85 said:
I get some bluetooth crashes when I try to use apps with bluetooth metadata, such as the Spotify app that I modified to have bluetooth metadata... It works on every device I have except the Note 3... I get an error that says Bluetooth share has crashed every so often when I try...
Click to expand...
Click to collapse
I get this same error with Pandora modified. It works perfect on all other devices but my note3 on tmobile. Saddens me that I had to downgrade.

Bluetooth AVRCP issues
I have used multiple devices in my car and the song information always displays correctly. Ever since I purchased my Note 3, I have noticed that my car's
display gets stuck on the first song's information and never switches. The songs will correctly play and quality does not seem to be impaired.
I have not found a way to update my car's software but I will look into it. Just wanted to add my issues to the thread.
I have the AT&T SM-N900A version of the Note and my car is a 2012 Honda Civic Si.

smkcody said:
I have used multiple devices in my car and the song information always displays correctly. Ever since I purchased my Note 3, I have noticed that my car's display gets stuck on the first song's information and never switches. The songs will correctly play and quality does not seem to be impaired.
I have not found a way to update my car's software but I will look into it. Just wanted to add my issues to the thread. I have the AT&T SM-N900A version of the Note and my car is a 2012 Honda Civic Si.
Click to expand...
Click to collapse
Thanks for the reply, I would bet Samsung is doing things a little differently with these new phones and it might take a bit for the Manufacturers to catch up. I have also read on a couple other sites that AVRCP 1.3 may not be implemented properly and might need to be updated by Samsung, it is unknown at this point but hopefully I will be able to test this out with a Tmobile Note 3 this afternoon and report back on how things look.
With my ATT Note 3, I get text messages on the screen (which I didnt on the S3 prior to updating) but I dont get any track info.
Lets keep the confirmations coming, maybe we can narrow down a make and model and let the Carriers/Samsung know they need to fix something if its broke.

Text notifications

Hi. I posted briefly before about a problem I was having. I have a nexus 6p and a vw 2016 head unit. Everything works really well & connects instantly etc except: I am not getting any notification sound for incoming text or hangouts messages. This is not very safe as you have to keep looking at the screen to make sure you haven't missed anything important. The strange thing is that this corrected itself on a recent journey and it was bleeping incoming messages just fine. But now it's gone back to complete silence again?! I'm not aware of having changed anything in set up. Is there anything I could have missed in terms of settings?
Any thoughts or experiences welcome.
Thanks.

dwj said:
Hi. I posted briefly before about a problem I was having. I have a nexus 6p and a vw 2016 head unit. Everything works really well & connects instantly etc except: I am not getting any notification sound for incoming text or hangouts messages. This is not very safe as you have to keep looking at the screen to make sure you haven't missed anything important. The strange thing is that this corrected itself on a recent journey and it was bleeping incoming messages just fine. But now it's gone back to complete silence again?! I'm not aware of having changed anything in set up. Is there anything I could have missed in terms of settings?
Any thoughts or experiences welcome.
Thanks.
Click to expand...
Click to collapse
You're not alone. I have found a post somewhere were someone was experiencing the same issue. I also have this issue. No matter what application, there is no notification sound. I think they've changed something in the code that doesn't allow the notifications to gain audio focus, therefore it doesn't play notification sounds. I made a work around using tasker. It seems when I use tasker and use the "say" command (for TTS) and have it set to respect audio focus, then it will interrupt (audio ducking) the audio on the stereo and say whatever I need it to say. I use Autonotification and a few other things to trigger the TTS. For example, if I get a telegram message it will say "New Telegram Message".

MrSickle said:
You're not alone. I have found a post somewhere were someone was experiencing the same issue. I also have this issue. No matter what application, there is no notification sound. I think they've changed something in the code that doesn't allow the notifications to gain audio focus, therefore it doesn't play notification sounds. I made a work around using tasker. It seems when I use tasker and use the "say" command (for TTS) and have it set to respect audio focus, then it will interrupt (audio ducking) the audio on the stereo and say whatever I need it to say. I use Autonotification and a few other things to trigger the TTS. For example, if I get a telegram message it will say "New Telegram Message".
Click to expand...
Click to collapse
Ok. Thanks for your thoughts on this. The thing I find quite strange too, is that the time it was functioning correctly, was definately since the last AA update version. End of March I believe. Now it no longer functions in my case and to my knowledge there have been no software updates to either AA or the phone itself since then to change anything . Stranger and stranger!

Apologies for resurrecting an old thread, but I'm having exactly this issue on a Nexus 5x connecting to a Kia Niro stock Android Auto head unit.
When connected, new messages received in Google Messenger and WhatsApp generate notification cards on the head unit and are read when tapping the card. However no notification tone is generated when the message is received.
Are you guys still having the same issue? Or did you find a resolution..

CodeMonkey said:
Apologies for resurrecting an old thread, but I'm having exactly this issue on a Nexus 5x connecting to a Kia Niro stock Android Auto head unit.
When connected, new messages received in Google Messenger and WhatsApp generate notification cards on the head unit and are read when tapping the card. However no notification tone is generated when the message is received.
Are you guys still having the same issue? Or did you find a resolution..
Click to expand...
Click to collapse
Hi. In my experience, I don't think there are any solutions as such. There are many "solutions" talked about on forums and it seems some of them work for some & not others and even amongst those that they work for, they may not work all the time. Therefore they can hardly be called a solution really. My experience of this is that it seems to depend on the software of the phone rather than just the AA app. By that I mean that after I upgraded my Nexus 6p from android 6 to android 7, performance on android auto in the car has been much more reliable. Pretty much 100% as it should work in fact.
Sent from my Nexus 6P using XDA-Developers mobile app

dwj said:
Hi. In my experience, I don't think there are any solutions as such. There are many "solutions" talked about on forums and it seems some of them work for some & not others and even amongst those that they work for, they may not work all the time. Therefore they can hardly be called a solution really. My experience of this is that it seems to depend on the software of the phone rather than just the AA app. By that I mean that after I upgraded my Nexus 6p from android 6 to android 7, performance on android auto in the car has been much more reliable. Pretty much 100% as it should work in fact.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks for responding - I expected as much, just wanted to avoid a DenverCoder9 scenario.
I've implemented a workaround for now using existing an existing Tasker + OutLoud profile to announce the message arrival over the media connection. Hopefully it'll simply start working one day..

And my notifications on a vw at are too loud. Try to increase the volume while you have a notification playing

I, too was having this issue and I think I have it solved, at least for my situation. Once I turned off AT&T's Advanced Messaging, I began to receive all my text notifications again. I know this solution might not apply to everyone but I know other carriers have similar features that may also cause issues.

jezzagroove said:
I, too was having this issue and I think I have it solved, at least for my situation. Once I turned off AT&T's Advanced Messaging, I began to receive all my text notifications again. I know this solution might not apply to everyone but I know other carriers have similar features that may also cause issues.
Click to expand...
Click to collapse
I had to switch to a yaata messaging app to fix it. and wondered if it was advanced messaging

Waze Beta Feedback/Discussion

Not an official part of the beta...but I've been installing and using the betas via apkmirror. I use the Sony XAV-AX100 for android auto on it's latest firmware (1.02.06 as of this writing). Phone is a Nexus 6P running 7.1.2. Started with the v4.24.0.113 beta....it worked...albeit with frequent crashes/restarts. It seemed VERY beta. Sometimes it didn't audibly report hazards/police, etc. The "OK Google" style voice recognition worked fine in the app....e.g if I had Waze selected for Nav, a "Navigate to DESTINATION" responded with "OK, handing that to Waze..." and then the destination came up fine in Waze.
I tried this on a few long trips, but ultimately the frequent crashes (sometimes at critical navigation points) were too much, so I largely reverted back to Google Maps.
I am now on v4.26.0.902. It is overall MUCH more stable than the 113 beta, however, all of the OK Google voice recognition defaults to Google Maps...e.g. "Navigate to DESTINATION" switches you to Google Maps by default, even if you are in Waze when you do it...even when tapping the microphone in the waze search box. I really hope that isn't going to be the case in the release version of this when it comes out. It's kind of a deal breaker....you really need that ability to choose a new navigation destination on the fly with voice commands as you can do in GM.
Overall Feedback for both versions so far:
1. I miss the speed/speed limit overlay terribly. I know they are dealing with a screen real estate issue here...but I'd really like to see this added back in.
2. No ability to send ETA in the AA UX. Not really a deal breaker for me....I found this functionality spotty at best in the release versions of Waze.
3. The Map detail could be better. I know the head unit has lower resolution than my phone, but Google Maps looks much better on it.
4. I wish the dark theme/dark map would work on AA. If I switch the lights on, it goes to dark, but I'd like the ability to have this on all the time. The dark map seems to look better on the head unit's screen.
I'd be interested to hear the experiences of others so far.....

You know, I just don't understand the lack of talk in this forum about Waze Beta. I keep coming here and looking and this is really the only thing about it.
1. Speed limit overlay is coming back, they talked about it when the new version came out last week.
2. Agreed. It should prompt you via voice after you hit a Send ETA button on who you want to send it to.
3. Agreed. I am a Geographer/GIS Specialist by trade, so I know maps, this small of font on the screen when driving is unacceptable. The detail is also very poor.
4. You DO know you can set your Android Auto to always be Night Mode right? I prefer it that way.
https://forum.xda-developers.com/showpost.php?p=68249351&postcount=7
Gives you the dark map all the time. Dark Google Play Music is better too.

RED ZMAN said:
4. You DO know you can set your Android Auto to always be Night Mode right? I prefer it that way.
https://forum.xda-developers.com/showpost.php?p=68249351&postcount=7
Gives you the dark map all the time. Dark Google Play Music is better too.
Click to expand...
Click to collapse
I did not know that! Thanks for the tip!
I've got 905 installed now but the "Navigate to DESTINATION" via voice switching you to Google Maps by default issue persists, unfortunately. 113 didn't do that. I really hope they restore that so that it uses your last used navigation app, similar to how music works.

skylaneffz said:
I did not know that! Thanks for the tip!
I've got 905 installed now but the "Navigate to DESTINATION" via voice switching you to Google Maps by default issue persists, unfortunately. 113 didn't do that. I really hope they restore that so that it uses your last used navigation app, similar to how music works.
Click to expand...
Click to collapse
905? Is that a new version that is AA capable?
We should use this thread, or maybe start a new one to notify XDA folks that do stumble in here when there's a new AA compatible beta. I've had to find out on *shudder* Reddit.

Installed 4.27.0.0 Beta on Friday. http://www.apkmirror.com/apk/waze/waze-gps-maps-traffic-alerts-live-navigation/waze-gps-maps-traffic-alerts-live-navigation-4-27-0-0-release/
I can confirm this version works with AA. Seems very stable, they fixed the "Navigate to DESTINATION" issue as well. Still no Speedometer. It may be because I've switched to always on night mode, but the map seems to look a little better than it did. I think they still need work with the fonts, etc. but this looks promising.

How does waze download map? I use it in car without Internet.
Last time i used it, i send Internet from phone to find the destination. Then i stoped Internet and working fine.
Last time i was in a trip, i started waze again, without Internet and without settings an adress. It was working but after a few minutes it didn't have map anyone. It just showing black for map..
Probably if i started Internet again it would show map. The program was working. It did work navigation but without map..
So i think when you search an andress, it download the map to go there. So even without Internet it will work. But if you dont follow the navigation and go to some other place, it wont have the map from the other place..
Sent from my SM-G9350 using XDA-Developers Legacy app

sosimple said:
How does waze download map? I use it in car without Internet.
Last time i used it, i send Internet from phone to find the destination. Then i stoped Internet and working fine.
Last time i was in a trip, i started waze again, without Internet and without settings an adress. It was working but after a few minutes it didn't have map anyone. It just showing black for map..
Probably if i started Internet again it would show map. The program was working. It did work navigation but without map..
So i think when you search an andress, it download the map to go there. So even without Internet it will work. But if you dont follow the navigation and go to some other place, it wont have the map from the other place..
Sent from my SM-G9350 using XDA-Developers Legacy app
Click to expand...
Click to collapse
The purpose of this thread is for discussion of the Waze Beta on Android Auto. Perhaps you should ask your question in the general Waze forum: https://www.waze.com/forum/ With a general google search, I found this relevent thread here: https://www.waze.com/forum/viewtopic.php?f=657&t=67879#p682703

Installed 4.27.0.1 beta. Working fine with AA. I don't see any feature updates...seems to be a bug fix release.

skylaneffz said:
Installed 4.27.0.1 beta. Working fine with AA. I don't see any feature updates...seems to be a bug fix release.
Click to expand...
Click to collapse
Hey there. I am having trouble with android auto. I have the same head unit as you as well as the same phone. I have tried many times to get android auto running with my phone on the head unit and I always get a message about "android auto will resume when you are parked". The head unit does not give this message when connected to a samsung phone or an i-Phone (apple car play). This error only pops up with my device, Nexus 6P so I am assuming it was wired correctly by the installer. Can you PLEASE let me know what ROM you are on (including the build date) and possibly what cord you are using to connect to the provided USB extension cable? I have yet to get this head unit to work with my Nexus 6P and I have tried a different ROMs, settings, reboots etc. Please help.

thesticks00 said:
Hey there. I am having trouble with android auto. I have the same head unit as you as well as the same phone. I have tried many times to get android auto running with my phone on the head unit and I always get a message about "android auto will resume when you are parked". The head unit does not give this message when connected to a samsung phone or an i-Phone (apple car play). This error only pops up with my device, Nexus 6P so I am assuming it was wired correctly by the installer. Can you PLEASE let me know what ROM you are on (including the build date) and possibly what cord you are using to connect to the provided USB extension cable? I have yet to get this head unit to work with my Nexus 6P and I have tried a different ROMs, settings, reboots etc. Please help.
Click to expand...
Click to collapse
I'm on the stock ROM....7.1.2 Build No: N2G470. The cord is just a generic USB-A to USB-C cord I bought at Fry's Electronics. FYI...I installed the head unit myself, and I think I may have had that issue initially. What I did to resolve it was ground the parking brake wire. This allows you to watch video on the head unit as well, if you have a USB stick with media on it (although I never do that).
Hope that helps....

skylaneffz said:
I'm on the stock ROM....7.1.2 Build No: N2G470. The cord is just a generic USB-A to USB-C cord I bought at Fry's Electronics. FYI...I installed the head unit myself, and I think I may have had that issue initially. What I did to resolve it was ground the parking brake wire. This allows you to watch video on the head unit as well, if you have a USB stick with media on it (although I never do that).
Hope that helps....
Click to expand...
Click to collapse
Thanks skylaneffz. I am going to get the parking break wire grounded tomorrow. Debating if I want to just return to stock now and if everything works tomorrow, I can try a custom rom again later. Kinda annoying that I can get my girlfriends I-phone to work with the head unit and not my own. Currently running pure nexus 6/12 with no luck. Thanks again for your advice. Getting waze to work will be the next step once android auto is up and running.

thesticks00 said:
Debating if I want to just return to stock now and if everything works tomorrow, I can try a custom rom again later.
Click to expand...
Click to collapse
I'd see if grounding the brake wire works first if I were you. Seems like a lot of trouble to go through. I'm on the stock ROM because my "Flashaholic" days are over

skylaneffz said:
I'd see if grounding the brake wire works first if I were you. Seems like a lot of trouble to go through. I'm on the stock ROM because my "Flashaholic" days are over
Click to expand...
Click to collapse
Thanks,
I may revert to stock regardless. I only really use a custom rom because they tended to be considerably better than stock (at least initially with battery life etc). I have not been on a stock rom in so long I have no idea how they compare to customs now. Since i have flashed so many times now trying to get this to work, and I had no guarantee any flash would prove fruitful, my phone is not even completely set up. LOL. So may as well give stock a spin. Regardless, thank you so very much. I was about to give up hope getting android auto to work with my phone and head unit. Especially since the good people of Sony have told me twice the head unit does NOTwork with 6P (granted they also told me twice it did). Gotta love their customer service.

Apparently the release version is out now:
https://www.blog.google/products/android/waze-android-auto-here/
The release version seems to be the same as the last beta: 4.27.0.1

Android Auto now working with regular Waze release!

Yeah, but missing lane assist and no speeding limits is really annoying.
And the calculated arrival time is on Google maps much better than Waze. Only thing what is very cool are the speed traps in waze.

Waze has got wrong routing to me and is not a good navigation system. And i don´t like the social blabla with points and that stuff...
Maps and TomTom are much better.

FormelLMS said:
Yeah, but missing lane assist and no speeding limits is really annoying.
And the calculated arrival time is on Google maps much better than Waze. Only thing what is very cool are the speed traps in waze.
Click to expand...
Click to collapse
I think there's a lot more stuff in ways that's a cool than that. Being able to go in and edit the map and add things or remove things and adjust them is fantastic. I do a fair amount of editing when I have time. Also the other reporting has turned out to be extremely important for me and has kept me from running into rather large roadkill and other trash items on the road from people towing trucks down to Mexico here in New Mexico.
[email protected] said:
Waze has got wrong routing to me and is not a good navigation system. And i don´t like the social blabla with points and that stuff...
Maps and TomTom are much better.
Click to expand...
Click to collapse
You may want to check your ways settings and make sure that they are set correctly for you. You can also do editing in your area to adjust the way that routing happens and it'll work better.

SMS issues continue - AA is rubbish

Like so many others, I keep experiencing countless issues with AA informing me that it doesn't know how to send a text, that it's still learning of that it needs to gather more information. I'm on a Samsung S10 5G in a Kia Soul. First I tried a new cable. No help. I tried clearing the phone's cache. No help. Have tried multiple messaging apps. No help. (Currently using Pulse). Any other suggestions greatly appreciated.

How rubbish Rodney?

I don't understand your question. Its lack of consistency in doing things like simple sending/reading of SMS messages makes even the iPhone solution much more usable.

He is saying AA is crap and he is looking for a suitable working alternative.

I'm afraid I don't know how to do that. But I'm still learning *grin*
That's just it, I don't know. Are we stuck with it? Is there any app that can unify multiple apps and put them on the car's screen? I don't think so. I can't believe I'm saying this, but Apple's implementation of something is better than Google's.

In my truck not only does the factory head unit ask to read calls and text via Bluetooth but also via android auto. It could be possible that the two techs are competing and causing errors. One thing that may revel clue to or two is to park and open Matt log with your phone plugged in as you normally do and have someone send you texts and look for any errors.

mine420 said:
In my truck not only does the factory head unit ask to read calls and text via Bluetooth but also via android auto. It could be possible that the two techs are competing and causing errors. One thing that may revel clue to or two is to park and open Matt log with your phone plugged in as you normally do and have someone send you texts and look for any errors.
Click to expand...
Click to collapse
Thanks! One question: What's Matt log? AA has also started saying something along the lines of, "Sure, but first let me get some more information" - around this point the voice generally fades out and I can't here anything else, but sometimes it also continues with - "select the prompt on your device" but there's never a prompt.
With my car it only works via the steering wheel controls when the phone is connected via the USB cable. I might have to see how it works with just OK Google.

I thought this one was fixed... but every time I've tried to send a text lately "OK Google text X person" ti gives me let me gather some more information... then nothing. Am I doing something wrong, or is texting through assistant on AA broken?

Note10.1Dude said:
I thought this one was fixed... but every time I've tried to send a text lately "OK Google text X person" ti gives me let me gather some more information... then nothing. Am I doing something wrong, or is texting through assistant on AA broken?
Click to expand...
Click to collapse
mines gone back their doing this after the update about 2wks ago.

https://myaccount.google.com/devicecontacts
You should activate this option

Android auto problems w galaxy fold

I have no idea what is going one w new look version and old versions of android auto. Either way, most commands or calling a contact, get driving directions or text someone are decli ed saying something like sorry, not sure how to do that or not know how to handle requests. Kinda frustrating and settings appear to be correct as I can see music apps, google maps etc.
Any suggestions or is it an issue somewhere else. Any other android phone and AA works fine w it whether new look version or old AA version.
Tia,
Ian B

Same problems here, Android Auto is borked big time on my fold but is still OK on my Pixel 3a. Problems are:-
1) When connected to my vehicles head unit it often disconnects for no reason
2) When I get a stable connection, and ask it to "navigate to xxxx" by voice it responds that it cannot do this "while in driving mode".
3) If I ask it to make a call or send a sms it responds "sorry I cant make calls yet" or "sorry I cant send texts yet"
4) After AA has been opened (even outside the car), Google assistant will no longer make calls or send texts via voice commands. Disabling the Google app, clearing the cache doing a restart brings the assistant functionality back but only until I use AA again.
The whole thing is a complete mess and given it is intended to be used WHILE DRIVING it is a very dangerous distraction - Google/ Samsung need to get on top of this or I can see them getting sued because they killed someone.

UPDATE: Iwas running a beta of google play services, when I uninstalled that and went back to the general release version, everything seems to be working OK with Android Auto.