Related
Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?
Maybe your Wifi/3G connexion is in sleeping mode and is too long to unsleep ? the watch can not connect so quickly ?
You sound like having BT reception issues on the phone. This behaviour might be triggered by the bluetooth interface itself (on the phone - bad design) or by bad drivers (also on the phone) or by interferences from the wifi module. Is your wifi on all the time?
Regular wifi is on 2.4GHz, the same frequency as BT. Wifi, however, uses more Rx/Tx power compared to BT so, under certain bad antenna designs, WiFi can just mess-up BT.
On my phone (Z1C) is the other way around: having BT ON will cause bad performance on 2.4GHz WiFi .... so I just stopped using the 2.4 band for WiFi.
Give it a try, Worst case scenario: use another phone.
Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!
Troxelke said:
Hi guys,
Thanks for the reply. About the first idea ... well if I have my phone on the charger and already switched on, it still happens. So there I assume the 3G / wifi connection is already on and this issue will not be due to the delay of switching the data connection on. Am I right?
Second option: my wifi is switched on all the time, you are right. I will try to experiment a little bit with it, let's see if that will make a difference. And, changing the phone ... hmmm well that would be a very high impact of course. My iNew V3 actually works very well ...
I am still a bit struggling with accepting it is my phone causing this issue ... only with the voice regocognition I have this issue ... with all other commands and apps the connection is OK! Only with the "OK google" option it says "offline" ... and immediately (I do not see the colored circle). To me it looks more like a but in the software or something, but after 3 resets of the device I also cannot believe that ...
Any more options? Thanks!
Click to expand...
Click to collapse
Update: i tried several things with the WIFI / BT settings and on/off, but no luck. I have forwarded the above issues to Google, maybe they can help me out. I will keep you informed ... in the meantime anybody else some useful tips? Thanks!!!
Troxelke said:
Hello all!
I must say, this watch is a very nice toy to play with and very handy in meetings! I have used the watch for a few days now, but I (only) have 2 issues to be solved which I cannot seem to find the answer yet:
1. The watch is connected to my phone OK (all notifications come through all the time). However, when I say "OK google" and then for instance "show me my steps" or "show me the weather", it will go to a screen saying me the connection is offline (white logo on blue background on the top of the screen). When I dismiss that message, I see that my connection is still OK! Weird .... this happens to me practically 80-90% of the times .... on a very rare occasion it succeeds to show me the info I want. By the way, my internet connection is OK at that time.
2. I have my phone also connected with BT to my Volvo V40 (2013). However, with the watch also on BT, the carkit of my Volvo is now almost useless as the voice is completely messed up (from the caller to me, and from me to the caller), sounds very intermittend or something. It seems like the BT connection is not happy with having 2 devices to be connected at the same time. My phone is an iNew V3 ... could it be something with BT profiles or versions?
I have already tried to reset the watch, re-install wear on my phone, deleted the dalvik cache (phone), un-installed apps, but no luck. Anybody have a clue on the above?
Click to expand...
Click to collapse
which phone are you using? are you on custom rom or kernel?
doki81 said:
which phone are you using? are you on custom rom or kernel?
Click to expand...
Click to collapse
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?
Troxelke said:
I am using a iNew V3 on KitKat with the 1.13 official version (however from needrom). Would that be the issue?
Click to expand...
Click to collapse
try to pair your watch with your friend phone and to check this is not a problem coming from your phone. sometimes certain kernel do have issue with some of the bluetooth device.
Hello everyone. Sorry for my English, because I am using a translator. I decided to write this post, because it happened to me the same trouble and I found her cause. In anticipation of its Nexus 6, I decided to temporarily buy fairly cheap option LG G60 (X135). When watch came to me, I noticed the same problem. I then tried to connect them to the Moto G (1st generation), and there is the same. but by chance, in the evening, in my hands was LG G90 and I connected watch to this phone. Everything works without any problem. it turns out that despite the declared characteristics (Bluetooth 4.0) in all devices, it works quite differently everywhere. I hope with Nexus no problems.
Hi all, after opening this thread I tried several things and have some new insights:
- new update (5.0.1) solved my issue with going "offline" after a voice command. Now it works perfectly! But only if I am not connected to my carkit.
- if my watch is connected and try to use the carkit the sound is still bad. So I would like to have my watch disconnected if my carkit connects:
-- this could be done by only allowing 1 device to pair with my phone and prioritize carkit to be first and watch to be second.
-- this could be done by actively unpairing the watch if I receive a call (and connect when call is over).
The first option would be the most reliable and most simple. I tried to find an app that restricts only having 1 pairing and having a prioritize option ... but I cannot find such app. People any options?
Thanks!
Hi guys, in response of the above, the app TRIGGER might do the job, but it seems closing the Android Wear app or disconnect via Bluetooth does NOT disconnect your watch! Has anybody succeeded in using TRIGGER to disconnect / connect the watch with a automatic job?
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.
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.
This has bothered me since long time, on several wear os watches. Problem is the following:
I have currently a samsung fold 4 and a samsung watch 5 pro LTE (but i've had the problem on other devices too in the past, al wear os devices).
When the watch is connected through bluetooth there is not a single issue. If i have my phone on the table for several hours, while not touching it, all notifications are instantly pushed to the watch, no delays.
However, when i leave my phone at home and going out with my watch only, it will correctly switch over to LTE connection and there the problems start. When my phone is recently used (few minutes ago) the watch can establish a remote connection. At that moment al notifications are pushed to the watch, almost no delays. However, after a while, usually within 30 a 60 minutes the notifications start to be delayed, and even the remote connection just stops (seeing the disconnected symbol on the watch). also sending messages or replying them on the watch is instantly and correct at first, but starts to fail after a while.
It seems like the google cloud sync service is killed after a while on the phone, preventing the forwarding of phone notifications to the watch over LTE (cloud sync). I tried everyting on my samsung phone, changing the battery optimizations of all samsung wearable apps and plugins, google apps, play service etc... I turned of as many battery saving features i could find on my phone, but no luck. If i leave the phone on the charger, the cloud sync keeps working for a longer time, but agian, ofter some time it will slow down, starting with unablity to reply or send messages from the watch, to complete disconnection... Al this while the internet connections on the phone and watch are rock stable...
Has anybody any clue why this happens?? Is there some trick or setting i overlooked? Does anybody know which app or service on the phone (samsung) is responsible for this google cloud sync?
again, this is not only on this phone-watch combo, i had several wear os watches from different brands in the past, but mostly samsung flagship phones. I cant believe that two samsung devices are not software optimized so these issues cant happen... I always bought LTE watches so i could go for a run or go to the gym phone free, is brilliant when it works, but VERY annoying when it usualy is not reliable.... I'm thinking even to switch to the apple camp, hoping those issues are not present on apple watch cellular... But i like samsung devices more then iphone ....
I have the EU version for 6 days now and I'm very happy with most of its features, screen, camera, speed and battery.
But I have identified 2 problems that I don't know if they have a solution.
- In Android Auto (when connecting to the car), the GPS signal is often lost or the direction of the car changes very easily, causing the maps to get crazy and constantly change the route.
-In the fb messenger, although I gave permission for the camera, when I press to take a photo and send, it does not send it, while if I select from the collection, it sends it normally
Has anyone else experienced any of these issues?
For GPS issue, try removing Location permission of android auto app in your phone.