Related
Hi,
I have a problem with Whatsapp program. It works perfectly fine when it comes to sending messages, although I have a problem with staying connected. The messages are delayed (sometimes it's even over 30 minutes) and when I simply wanna unlock my phone and text someone, the person won't receive my message until I reconnect my mobile data (grey clock icon on the left of my message). I've already seen many instructions on the net, like reinstalling Whatsapp, rebooting my phone, checking if my sync works and all that, but none of them worked for me. It really starts to annoy me, but I like this program alot and I don't want to give up on it that fast. So is there any way to force Whatsapp to stay connected full-time ?
I'm using MiniCM-2.2.0 with latest nAa Kernel.
Regards
Bump, spent the whole night browsing the net for similliar topics and found nothing...
ziemny said:
Hi,
I have a problem with Whatsapp program. It works perfectly fine when it comes to sending messages, although I have a problem with staying connected. The messages are delayed (sometimes it's even over 30 minutes) and when I simply wanna unlock my phone and text someone, the person won't receive my message until I reconnect my mobile data (grey clock icon on the left of my message). I've already seen many instructions on the net, like reinstalling Whatsapp, rebooting my phone, checking if my sync works and all that, but none of them worked for me. It really starts to annoy me, but I like this program alot and I don't want to give up on it that fast. So is there any way to force Whatsapp to stay connected full-time ?
I'm using MiniCM-2.2.0 with latest nAa Kernel.
Regards
Click to expand...
Click to collapse
well maybe you shouldn't give up on whatsapp but the ROM instead. What i mean is, maybe something inside the ROM/kernel wasn't installed properly and you could try reinstalling ROM and/or kernel... I know it's a stupid solution but it saved me many times when i couldn't find the answer anymore
bubr3g said:
well maybe you shouldn't give up on whatsapp but the ROM instead. What i mean is, maybe something inside the ROM/kernel wasn't installed properly and you could try reinstalling ROM and/or kernel... I know it's a stupid solution but it saved me many times when i couldn't find the answer anymore
Click to expand...
Click to collapse
Thank you for your reply. I already had the problem on previous ROMs (I mainly used MiniCM). Maybe I'll give GingerDX a shot. I'll tell you how it went.
Regards
Did you leave the app in background? When you leave Whatsapp, dont click back button, try clicking home button?? Dont move app to SD if you did!
Hit The THANKS Button If I Helped You!
Sent From My W8 Using Tapatalk
lucastan96 said:
Did you leave the app in background? When you leave Whatsapp, dont click back button, try clicking home button?? Dont move app to SD if you did!
Hit The THANKS Button If I Helped You!
Sent From My W8 Using Tapatalk
Click to expand...
Click to collapse
i belive that whatsapp is running in background by default, so as programs such as viber, hotmail, etc. but we all know that this can be checked under settings > applications > running applications
but i agree that moving whatsapp to SD could be the problem, although i had no problem when i moved it to SD
I didn't move it to SD card and I don't use any task killer. Process manager says it is running in the background. Still no idea how to fix it.
if it isn't because of moving to SD, and it is running in background, if it isn't because of ROM (you've said that you have used some ROMs before and that there was the same problem), if your data settings work normally (sync and stuff), if the problem persist on wifi and 3g and edge,...
it occurs to me that it can only be due to two things, maybe you installed cracked version of whatsapp due to 1-year-free expiration, or maybe something went wrong when you installed your current kernel
P.S. whatsapp is 70% of communication on my X8, and i understand you very well when you say that you won't give up on it so easily
bubr3g said:
if it isn't because of moving to SD, and it is running in background, if it isn't because of ROM (you've said that you have used some ROMs before and that there was the same problem), if your data settings work normally (sync and stuff), if the problem persist on wifi and 3g and edge,...
it occurs to me that it can only be due to two things, maybe you installed cracked version of whatsapp due to 1-year-free expiration, or maybe something went wrong when you installed your current kernel
P.S. whatsapp is 70% of communication on my X8, and i understand you very well when you say that you won't give up on it so easily
Click to expand...
Click to collapse
I didn't crack anything, I'm still on trial. If I wanted to get another free year, I'd change my phone number I also reinstalled the kernel too.
EDIT: Now it works properly on WIFI only. Still disconnects after couple of minutes on 3G.
EDIT2: It seems like reinstalling GDX and Alfs finally worked for me. Thanks for all the help guys
Another update:
after a few hours I'm back to the point where I started... the problem's still there. I'm really pissed off now -.-
ziemny said:
Another update:
after a few hours I'm back to the point where I started... the problem's still there. I'm really pissed off now -.-
Click to expand...
Click to collapse
It is only logical that Whatsapp won't implement itself right on your phone... This is all ridicoulos right know, because for as far as i know, you almost tried every solution possible, you've changed to other ROM, heck, you've even changed to other kernel and it still doesn't work.
You said it worked for a while, maybe some of the settings you've changed, and apps you've installed AFTER it was all working properly was interfering with your newly applied settings and/or installed apps
bubr3g said:
It is only logical that Whatsapp won't implement itself right on your phone... This is all ridicoulos right know, because for as far as i know, you almost tried every solution possible, you've changed to other ROM, heck, you've even changed to other kernel and it still doesn't work.
You said it worked for a while, maybe some of the settings you've changed, and apps you've installed AFTER it was all working properly was interfering with your newly applied settings and/or installed apps
Click to expand...
Click to collapse
I've installed Advanced Task Killer to see if it's the problem with Whatsapp, but it didn't block me from receiving the messages or anything. I uninstalled ATK and like an hour later, the problem occured again. I'll reinstall the kernel and the ROM again and leave it with only Whatsapp installed for a day. If that doesn't work, I might just buy an Xperia Neo V :S
Maybe it's because I connect to another network instead of my providers one ? I have data roaming enabled and stuff and I connect to Plus instead of Play (even though Play says they allow such things). Could this cause the problem ?
Or Swype Beta maybe ? I'm running out of ideas...
I just found out that when Whatsapp's not showing the "last seen" date (not connected), when I enter any website in the browser and return to Whatsapp, it shows the "last seen" properly. But I still have no idea what can this be...
ziemny said:
I've installed Advanced Task Killer to see if it's the problem with Whatsapp, but it didn't block me from receiving the messages or anything. I uninstalled ATK and like an hour later, the problem occured again. I'll reinstall the kernel and the ROM again and leave it with only Whatsapp installed for a day. If that doesn't work, I might just buy an Xperia Neo V :S
Maybe it's because I connect to another network instead of my providers one ? I have data roaming enabled and stuff and I connect to Plus instead of Play (even though Play says they allow such things). Could this cause the problem ?
Or Swype Beta maybe ? I'm running out of ideas...
Click to expand...
Click to collapse
Wait, does it work normally when you are on wi-fi? try to test whatsapp when you are strictly on wifi (wich means that you turn off celluar data, data roaming and national roaming), so that we can definitly exclude the problem of wifi.
if the problem isn't in wifi, try to connect on your providers network (PLAY) instead of other network (PLUS), and see if the problem persists
if the probelm still persists i belive there is counterinterfering with some application...
i know that i'm offering too much possible solutions, but i think that this can only be solved by method of trying out every possibility
bubr3g said:
Wait, does it work normally when you are on wi-fi? try to test whatsapp when you are strictly on wifi (wich means that you turn off celluar data, data roaming and national roaming), so that we can definitly exclude the problem of wifi.
if the problem isn't in wifi, try to connect on your providers network (PLAY) instead of other network (PLUS), and see if the problem persists
if the probelm still persists i belive there is counterinterfering with some application...
i know that i'm offering too much possible solutions, but i think that this can only be solved by method of trying out every possibility
Click to expand...
Click to collapse
As from what I see for the last 30 minutes, it's working fine on WIFI. I also tried switching to Play and disabling the roamings, but it still kept disconnecting.
The apps I have installed:
- Barcode Scanner
- Battle.net Mobile Authenticator
- Dolphin Browser
- exDialer & exContacts
- GG (Polish messenger, but I doubt it causes any errors as I just installed it recently)
- GO SMS Pro
- Real Player
- Root Uninstaller Pro (I only uninstalled DSP Manager)
- Whatsapp obviously
- ColorNote
- Nexus ICS Minimal Analog Clock
That's pretty much everything I have. I didn't change anything in the settings of GingerDX itself. I'm really helpless here...
huh, nothing from that list shouldn't interfere with anything... maybe you should put back ATK and see what exactly happens with whatsapp when it disconnects from network
i'm really running out of ideas
It's pretty simple. It's got nothing to do with your ROM, kernel, 3G or WiFi - AFAIK. Rather, I think it's to some extent do to your connectivity. The app's refresh interval apparently varies. Seems worse when you have many long threads. Deleting a few threads seems to work from time to time. I however use another android device & I assure you the problem is in no way restricted to the X8
Saipro said:
It's pretty simple. It's got nothing to do with your ROM, kernel, 3G or WiFi - AFAIK. Rather, I think it's to some extent do to your connectivity. The app's refresh interval apparently varies. Seems worse when you have many long threads. Deleting a few threads seems to work from time to time. I however use another android device & I assure you the problem is in no way restricted to the X8
Click to expand...
Click to collapse
So it's normal that I get my messages delayed by around 30 minutes or even more ? I clear my logs every day, so I think the messages should arrive like... instantly :S
ziemny said:
Hi,
I have a problem with Whatsapp program. It works perfectly fine when it comes to sending messages, although I have a problem with staying connected. The messages are delayed (sometimes it's even over 30 minutes) and when I simply wanna unlock my phone and text someone, the person won't receive my message until I reconnect my mobile data (grey clock icon on the left of my message). I've already seen many instructions on the net, like reinstalling Whatsapp, rebooting my phone, checking if my sync works and all that, but none of them worked for me. It really starts to annoy me, but I like this program alot and I don't want to give up on it that fast. So is there any way to force Whatsapp to stay connected full-time ?
I'm using MiniCM-2.2.0 with latest nAa Kernel.
Regards
Click to expand...
Click to collapse
Hi,
Do you still have the problem of the messages getting delayed?
I have the same problem since three months now I think.
I have already tried everything you guys said here.
I have no problems what so ever on WI-FI but only on 3G.
I think it has something to do with Whatsapp, maybe even with our accounts in specific.
Did you ever fix this problem?
Because I am having it on my Samsung Nexus S.
I found that when I send a message, and I am running whatsapp in the background I still woulnd't recieve the messages.
So I hope you found the solution and could maybe share? :angel:
ziemny said:
Another update:
after a few hours I'm back to the point where I started... the problem's still there. I'm really pissed off now -.-
Click to expand...
Click to collapse
try using supercharger v6 with script manager & use use multitasking settings
forum.xda-developers.com/showthread.php?t=991276
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
All righty then, I guess its me
mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.
UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.
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?
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.