Related
I run ViperROM 2.5.0 (Android 4.4.3). I looked and maps was last updated August 26. I definitely used it since then and it worked just fine.
In fact, now that I think about it, maps was working YESTERDAY! I was on the road and navigated to Supercuts to get a hair cut.
What did I do since then? Nothing! Played a game, viewed news in my HTC Blinkfeed, and showed someone pictures from Gallery to Chromecast on my TV.
I woke up and today I'm going somewhere to meet up with family for lunch and I thought I'd see how much time it takes to get there. Soon as I hit directions it says "Unfortunately, Maps has stopped."
I have tried to clear data from Settings -> Apps -> Maps. No luck. I've uninstalled and reinstalled. No luck.
I'm running the same version of Viper with the most recent version of Maps & I'm not having any issues.
I wasn't having any issues either. I've had 2.5.0 since it came out. I went halfway across the United States and back with no problems.
Oh yeah, I think I had this problem once before. I just remembered how to "fix it". Turn off Google Now.
Running completely stock and maps has been crashing a lot the past 4 days. Happens when I hit the directions arrow by the search box, where history is found. Then fails to report when I choose that option.
Sent from my 831C using XDA Free mobile app
As title says I can't get the navigation cards to appear. They used to work initially on the original LG G Watch but since upgrading to the G Watch R I can't seem to get it to work. I say "OK Google navigate to ..." And it starts the app on my phone just fine but nothing pops up on my wrist. Am I missing something?
Same problem for me. Android 5.0.2. Latest Maps, latest Android Wear.
Same was here..
After i bought my watch it was on Android 4.4, after setup it with the phone it was updated automaticly to 5.0.1 and my navigation doesn't work. But today i've reset my watch and setup up again, and navagitaion works just fine. Maybe after system upgrade of the watch is good to do factory reset to effect of the new android.
Thanks for the reply lostindark, was hoping that would work for me but unfortunately it didn't. Just tried it and it still does the same thing. Just to confirm, you just tapped the reset from the settings menu on the watch right? I did that and it didn't work, then I also cleared the data on the wear app, re-paired the watch and still didn't have any effect Does the same thing mentioned in the OP, works fine on the phone and starts the maps app there but no cards on the watch.
Sorry to heat this, i reset my watch only through settings and notting more but it was worked for me. After the reset and pairing again android wear app put other apps automatically on my watch after that everything works just fine.
Thanks anyways for the suggestion mate, I ended up getting a Nexus 6 today and it is working just fine paired with this phone. Must have been something with my OPO but I have no idea what since it was 100% stock other than root.
Sent from my Nexus 6 using Tapatalk
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.
Everything was perfect until i decided to upgrade to a device with Android 10. Android auto is preinstalled in that version and I can't install the apk (no reason though) in order to use android auto in my car.
I live in a country where android auto is not officially launched and by using the apk method in older versions, I could bypass the check. Now that has changed since it's preinstalled and it says that I live in a country where android auto doesn't support.
Is there any workaround for this ?
Thanks
The only thing I can tell is that I also live in a country where AA apk is not available in the Play store and I had to sideload it from Apkmirror. I am still on Android 9.
But, a friend of mine, which recently bought a Samsung S20 Ultra with Android 10, is able to use the built-in AA, besides the fact that officially AA is not available in our country.
You should know that, in Android 10, you won't find an icon for AA apk, because there isn't one. Due to the fact that AA is part of the operating system, it is not possible to start it manually, but it will be automatically activated when the phone is connected to the car's infotainment system, supporting AA. If you try to connect your phone wirelessly from the first time, it probably won't work. For the first connection and settings, you should use an USB cable.
Sent from my SM-N975F using Tapatalk
coolgus said:
Everything was perfect until i decided to upgrade to a device with Android 10. Android auto is preinstalled in that version and I can't install the apk (no reason though) in order to use android auto in my car.
I live in a country where android auto is not officially launched and by using the apk method in older versions, I could bypass the check. Now that has changed since it's preinstalled and it says that I live in a country where android auto doesn't support.
Is there any workaround for this ?
Thanks
Click to expand...
Click to collapse
Simple solution... use VPN and set it up to a country where AA is supported(mocked location)... or use apkmirror or Aurora store(aka free Google play, use XDA search for thread )
SOLVED
It was simpler than this, for whatever reason the usb cable only charged the device not giving a data connection and without having an option to change this. Tried 2-3 cables and one of them did the trick, everything was sorted out.