HEAD UNIT: Kenwood DDX9702S
PHONE: Nexus 6P
As far as I know, everything is up to date. Everything sounds fine when I first start my car. However, once I input my first voice command (by pressing the microphone), afterwards, all audio coming out of the right side is crackly. If I restart my car, the crackling is gone. I can go hours with it sounding just fine, but once I submit my first voice command, it all goes to hell. Any ideas? I will be reaching out to Kenwood soon about it, but this brings me to my next issue...
How the hell to we contact Google for support for Android Auto?!?!
Thanks!
Sean
seanfrisbey said:
How the hell to we contact Google for support for Android Auto?!?!
Click to expand...
Click to collapse
LOL. Google doesn't provide support...
Unless you're a business with a support contract, but they may not even have that for Android Auto.
You can at least inform Google if you want. Open the AA app, hit the dots at top right and select Help and feedback, then select the Send feedback option.
mikereidis said:
LOL. Google doesn't provide support...
Unless you're a business with a support contract, but they may not even have that for Android Auto.
You can at least inform Google if you want. Open the AA app, hit the dots at top right and select Help and feedback, then select the Send feedback option.
Click to expand...
Click to collapse
I'll have to give the in-app feedback a try. Ugh...
seanfrisbey said:
I'll have to give the in-app feedback a try. Ugh...
Click to expand...
Click to collapse
If it's happening on a Kenwood HU, ask Kenwood.
mikereidis said:
If it's happening on a Kenwood HU, ask Kenwood.
Click to expand...
Click to collapse
I have. They gave me some troubleshooting steps, which require another phone to try it with. I'm swapping out this unit for a replacement anyways this weekend for another issue it is having regarding the camera input, so I'll wait until then to try anymore troubleshooting steps.
I don't have OP's issue but I got a similar one with my ddx9902s. What happens is when google now prompts are spoken (ie when reading a text message or verifying if what you spoken was what you want to send BUT not things like map navigation) I get some distortion/static. However everything else is unaffected.
Honestly not sure if it's related to this but this is the closest problem I saw. Might be an amp/cabling issue?
I have the same issue on a DDX9702S. Only affects Android Auto, not CDs, Bluetooth, or CarPlay.
Any resolution to this, or did you just exchange it?
Related
I am not sure if this is an issue or if I am just being overly picky so I figured I would ask you guys and see what your experiences are.
My GPS arrow on maps doesnt point the direction the phone is moving(top of the phone). The arrow points to the right(side of the phone.) My old Nexus 4 didnt have this issue.
Moto voice is also really quite. The voice assistant does not speak with the same volume as the rest of the phone. Even with the volume turned up the voice assistant is quite.
what do you guys think, am I just being overly picky?
I've been hoping someone would respond with help or suggestions regarding this. Sitting in front of my computer, the screen orients correctly. But when I put my phone in my car, mine does the same as yours.
blkbltwrestler said:
My GPS arrow on maps doesnt point the direction the phone is moving(top of the phone). The arrow points to the right(side of the phone.) My old Nexus 4 didnt have this issue.
Click to expand...
Click to collapse
My friends MX2 (I don't have one) has the GPS problem including the too quiet Voice Assistant. Is there a setting or method to turn up the voice?
beejaycee said:
I've been hoping someone would respond with help or suggestions regarding this. Sitting in front of my computer, the screen orients correctly. But when I put my phone in my car, mine does the same as yours.
Click to expand...
Click to collapse
l_stevens said:
My friends MX2 (I don't have one) has the GPS problem including the too quiet Voice Assistant. Is there a setting or method to turn up the voice?
Click to expand...
Click to collapse
Well maybe I will call and next week and see what their technical support says, unless someone else says this is normal.
blkbltwrestler said:
Well maybe I will call and next week and see what their technical support says, unless someone else says this is normal.
Click to expand...
Click to collapse
Just got the lollipop update and it seems to have fixed all the issues.
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
Hey, so I'm fairly new to android auto, having been in my 2016 civic for only a couple weeks. Everything is working great apart from the text message issue. Basically when I receive a text, it shows up on the home screen but when I click it, aa won't read it to me. The screen goes dark and the microphone icon goes blue as if it's trying to read it, but nothing happens and it returns to the home screen. Interestingly, if I press the microphone and use a voice command like 'read my last text message' aa says: "actually, I can't read your messages yet". Any help would be massively appreciated, it's really the only issue I've had so far with the vehicle or Android auto. Thanks.
Sorry, forgot to mention the phone is a nexus 5 with 6.0.1. The usb cord is the original that came with the phone, plugged into the usb port in the car designated for smartphone connection. Also I'm in Canada, if that matters.
Have you checked the permissions on the android app on your phone? Sounds like it doesn't have permissions to view your SMS?
Sent from my Nexus 6P using XDA-Developers mobile app
Yah I went to settings/apps/app permissions/sms and enabled all the apps in there. I also went to android auto, messenger, hangouts, Google play services, Google app, and contacts individually to make sure sms permissions were granted. I'm able to send a text from android auto, but it won't read out texts that I receive.
I'm having the same issue with my Galaxy S7 Edge running Android Auto on my Pioneer AVH-4100NEX. I went on vacation and my car sat for a while and now when I'm in Android Auto mode I can't receive and send text messages. I ask Google for the weather or to do a calculation and I get nothing. However, if I ask Google to dial someone whether in my contacts for not, it dials the number. Does this make any sense? There doesn't appear to be any official Android Auto support. I contact Pioneer and they told me my contacts weren't syncing with Android Auto which was strange enough when they said it, but given the fact that I don't get a reply when I ask GoogleNow for the weather means my contacts shouldn't have anything to do with it. Any help would be appreciated.
Thanks,
Matt
Same here: SEAT Ibiza with Full Link, Nexus 6 with 6.0.1 with SMS and WhatsApp. Could that be caused by some setting for language, text-to-speech? Everything else works fine, also sending messages.
PS: The system language ist German...
Similar.. it'll occassionaly read one message. But only one. Not always the first one per time I connect the phone to the car. Hyundai elantra 2017, vzw gs5.
Sent from my SM-T520 using Tapatalk
Made an account just so I could maybe help a few people. I'm using a Galaxy S6 with an AVH-4100NEX unit, and I was getting the same issue. Could send messages fine. Tap to read message - agonizing silence. Managed to solve it by factory resetting my device with Samsung's Smart Switch software. Backup. Reset to factory setting. Restore. Success. All the best!
**SOLVED** this problem has been driving me crazy, but I found the problem. Go to your Google Now settings, click "Voice" and turn OFF Bluetooth Headset.
Its to bad we can't have that on and use Android Auto. You have to choose either the built-in system in the car with Bluetooth or use Android Auto.
Anyways, I hope this solves your problems.
I was hoping Build A Wall's post was the fix but it didn't change anything at least for me. My GoogleNow works fine if I'm just using the phone in my hand. But ever since the end of June, when connected to my car, I can't text or ask for the weather but GoogleNow understand if I ask it to call someone or ask for directions. And even when it does work like making a call, it doesn't reply by saying "Calling Steve" like it used to. It's really weird. I'm wondering if Android Auto came out with an update and it screwed up things.
I don't think there has been another update, I just think it is primitive software that still doesn't quite work as it should. I have had similar problems that I have posted on here in that I could no longer send text messages but could still navigate etc. My situation now is that I have changed nothing on my Nexus or my car unit yet now it is working perfectly again! Hopefully, that is encouraging for you. I hope they will stabilise the software with some updates.
Sent from my Nexus 6P using XDA-Developers mobile app
@mpisani sorry that didn't work. It sounds like your problem is a little different than mine. I was having the same issues as the fiest post in this thread. It just wouldn't read my text to me, but everything else worked great.
I hope you get it figured out.
I turned off Bluetooth entirley before starting the car, it didn't help.
Having the same issue. Next text will come in, screen will show that there is a new text and from whom, but when you touch the card the microphone in the right corner turns blue while rest of screen changes tone a bit to show its in background but there is no audio of text message being read. ask google to read new texts and google says it cannot do that at this time. I'm wondering if it can tell thru gps if you are in a state that has banned all texting while driving and they are trying to cover their ass.
BuildAWall said:
**SOLVED** this problem has been driving me crazy, but I found the problem. Go to your Google Now settings, click "Voice" and turn OFF Bluetooth Headset.
Its to bad we can't have that on and use Android Auto. You have to choose either the built-in system in the car with Bluetooth or use Android Auto.
Anyways, I hope this solves your problems.
Click to expand...
Click to collapse
Thank you so much - it worked!!! My Voice commands did not work at all, no matter what I tried (which was a lot) - it just turned on, listened, turned off, repeated. This fixed it. Now I can again give voice commands, and it will read messages to me as well!
Sent from my Nexus 6P using Tapatalk
I've been having the same issues with my new 2017 Elantra. It's sporadic in reading it, sometimes it does and sometimes it doesn't. Interestingly, when reading messages it uses the other TTS service and not the one from Google Now.
Going to try the BT setting and see how it works. Also was wondering if the issue was from the SMS app.
Sent from my Nexus 6P using Tapatalk
tjk639 said:
I've been having the same issues with my new 2017 Elantra. It's sporadic in reading it, sometimes it does and sometimes it doesn't. Interestingly, when reading messages it uses the other TTS service and not the one from Google Now.
Going to try the BT setting and see how it works. Also was wondering if the issue was from the SMS app.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I don't believe it is the sms app purely because the fault is the same for me also with google hangouts which is of course a different app.
I'm really bored with it now sometimes working sometimes not no matter what solutions we come up with on here and try out.
Does Apple car play have all these issues with working just when it feels like it? Maybe we should all get iPhones so we can have software that just works as it should.
What about mirror link? Does anyone have experience with that? Or is it just music apps rather than communication like texting etc?
bradboyd said:
Hey, so I'm fairly new to android auto, having been in my 2016 civic for only a couple weeks. Everything is working great apart from the text message issue. Basically when I receive a text, it shows up on the home screen but when I click it, aa won't read it to me. The screen goes dark and the microphone icon goes blue as if it's trying to read it, but nothing happens and it returns to the home screen. Interestingly, if I press the microphone and use a voice command like 'read my last text message' aa says: "actually, I can't read your messages yet". Any help would be massively appreciated, it's really the only issue I've had so far with the vehicle or Android auto. Thanks.
Click to expand...
Click to collapse
Since this new update, my LG v10 Android Auto experience is horrible - essentially voice commands hardly every work - I'm not getting full prompts all the time (sometimes I get audio beeps before/after, sometimes just before, sometimes just after, sometimes never!). I've found I can guess at what I should be saying when it's listening for voice input to send a text, but I get zero feedback from the system. And my received texts will not read back. Very Very frustrating. As I work for a Honda dealer, our engineers have informed me it's all on Android. I think I'll fire up my iPhone today and go back to CarPlay for a while and hope the next release fixes my issues - it's just not usable in its current form.
The Bluetooth setting worked for me. Really odd fix that I would have never guessed to try. Thanks for the tip
Sent from my Nexus 6P using Tapatalk
So far, like others, that odd setting fixed it. Google Now update must have introduced it.
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.
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