So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
tiagobt said:
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
Click to expand...
Click to collapse
Same here, except that I'm on a Moto X Pure 2015.
What I've just ended up doing is after dialing/answering a call, I press the power button to turn the screen off, and turn it back on to end it.
The same here. Another alternative is to manually choose "Earpiece" within in-call screen. This activates prox sensor again.
This should be considered a bug and I believe Google will make necessary adjustments in the Dialer app in this regard.
Thanks for the help, guys! The workarounds you provided do work. However, the bug is still very annoying. I've reported the bug in the AOSP issue tracker:
https://code.google.com/p/android/issues/detail?id=202776
tiagobt said:
Thanks for the help, guys! The workarounds you provided do work. However, the bug is still very annoying. I've reported the bug in the AOSP issue tracker:
https://code.google.com/p/android/issues/detail?id=202776
Click to expand...
Click to collapse
Thanks for taking care of creating an issue. I added my vote and comment.
Just voted as well...Nexus6P
This issue does not seem to present in my Samsung Galaxy S6 ... the proximity sensor works as intended during phone calls from phone.
The phone screen does not dim when the call is actually running on the watch , however the proximity sensor works as expected and dims the screens if the call is placed from the phone or transferred back to the phone from the watch......Perhaps this issue is Device specific or present in the stock versions of Android OS
Most likely related to Google's Dialer app and InCallUI app
Samsung delivers its own modified Dialer so it is possible they took care of that issue themselves.
Added new comment. Quoting.
Issue seems to be fixed after updating my Nexus 5X to MHC19J. Well, almost. Handset earpiece is forced as soon as call is connected resulting in proximity sensor being active, which is OK for handling incoming calls. Issue is with outgoing calls as when dialing, I have to wait for call to be connected before proximity sensor kicks in. Proximity sensor should kick in as soon as dialing starts, before call is connected.
Click to expand...
Click to collapse
nomad032 said:
This issue does not seem to present in my Samsung Galaxy S6 ... the proximity sensor works as intended during phone calls from phone.
Click to expand...
Click to collapse
Works also fine for my Samsung Note 4.
tiagobt said:
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
Click to expand...
Click to collapse
Same here! Huawei watch and Droid Maxx 2 running Marshmallow. I thought it was Android Wear until I stumbled upon this post. This so negatively impacts the user experience that I'm considering returning the watch.
Related
Greetings all,
I have the HTC Droid Incredible, runing Android 2.3.4, Kernel 2.6.35.13.
I would like to use Skype with wifi, but have discovered a bug. When I make a skype call, all works well on speakerphone. However, as soon as I put the phone to my ear, the proximity sensor turns the screen off, and slows down wifi considerably. This results in my skype call being ended.
I would like to fix this by setting my phone to keep wifi on like normal, even when the proximity sensor turns the screen off. I found this thread, which sounds like what I need, but there doesn't seem to be a download for my kernel version: http://forum.xda-developers.com/showthread.php?t=752856
Can someone explain to me the steps I would need to take to fix this issue?
Thank you!
Hi Everyone. I hope you could help me with my situation.
I had the watch about a month now. It was working nicely till a couple of days ago, the ok google stopped working.
When I tap the screen twice, there is a red G speak now. I cant tap on that icon. When replying a sms, the watch doesn't go into the voice recognising mode. I also tried sync with another phone.
I tried resetting to factory default. Reinstalling android wear and moto connect. Still doesn't work. I even tried the settings in Google settings, re recognising the ok google..
Running out of options.. Please help
When the red G Speak now appears do the following:
Speak.
This is the new design since Wear 2.0 Update
I spoke ...
but nothing happens...
Ferderico said:
I spoke ...
but nothing happens...
Click to expand...
Click to collapse
Strange, could your microphone have something in the little hole?
i doubt that something is stuck in the little hole at the 9 o'clock position.
cos if i tap on Speak Now - it should have some bars which emulates a sound equaliser... but in my case, there isnt.
So i suspect is a setting. ... sigh..~ btw i am using Samsung Note 4
Ok, excuse me for my upper post.
But without the further infos you have now given, i could not resist to write this.
Test the microphone with an other app.
SleepAsAndroid, LED Music Controller or any soundrecorder which uses the moto360 microphone.
Have you rooted your Samsung and are you restricting apps with xprivacy or a similar program?
If the sound test fails I think your microphone is broken...
Try this. My problem was that "OK Google" only working from Voice Settings Screen using Moto 360 with my Samsung Galaxy S4 running Lollipop. I could not get the "OK Google" feature to work anywhere EXCEPT when I had the SETTINGS/MY DEVICE/LANGUAGE AND INPUT/GOOGLE VOICE TYPING screen open on my phone. Turns out that you have to have the GOOGLE NOW LAUNCHER as the home screen software. It will not work with the TOUCHWIZ HOME as the home screen software. To change this, go to SETTINGS/MORE/DEFAULT APPLICATIONS/HOME and select GOOGLE NOW LAUNCHER.
Static sound coming out
I am having the same issue. Also I am using a custom rom for note 4. I have tried the solution above and it doesnt work. I installed the "wear audio recorder" app and I only hear static sound... Is there an app or something to see if the communication between components working?
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
I have only a small delay like 0,5s. So I think this is not normal. Are you connected by bluetooth or maybe by wifi?
I'm connected by BT. Like i mentioned all of my other notifications are working just fine. It's just the phone notification. I wiped my watch and reloaded everything so i am waiting to see if that fixed anything.
zumstin said:
I'm connected by BT. Like i mentioned all of my other notifications are working just fine. It's just the phone notification. I wiped my watch and reloaded everything so i am waiting to see if that fixed anything.
Click to expand...
Click to collapse
Update: It did not work. Sigh...
zumstin said:
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
Click to expand...
Click to collapse
I have this at times, though not always. I also get it where after I answer the call it continues to vibrate on my watch. hangouts messages do take a few seconds to push to the watch though. that said, this behavior has been consistent with my zenwatch, smartwatch 3 and my hwatch so I think it's just inherent in the platform
kellybrf said:
I have this at times, though not always. I also get it where after I answer the call it continues to vibrate on my watch. hangouts messages do take a few seconds to push to the watch though. that said, this behavior has been consistent with my zenwatch, smartwatch 3 and my hwatch so I think it's just inherent in the platform
Click to expand...
Click to collapse
Same here.
I just tested a call and it was about .5 to 1.0 seconds which is considered very good by my taste. But I did notice SMS and Hangouts does take a few seconds.
Maybe they set the priority like that on purpose.
Same problem for me...
zumstin said:
Is anyone else having a delay in phone notification? By the time my watch starts vibrating to notify me of a phonecall I have already missed the call on my phone. That's irritating. One of the reasons I got the watch was to let me know when my phone starts ringing. My emails and texts seem to be notifying me just fine. It's just the phone notification.
Ideas?
Click to expand...
Click to collapse
I am experiencing the same exact problem with my Nexus 6P - no amount of resetting seems to have fixed the problem. This has been extremely frustrating.
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
uniqueflips said:
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
Click to expand...
Click to collapse
I'm hoping with the new update to Wear announced today that it will fix the delay. Hoping....
uniqueflips said:
Anyone else figure this out without having to warranty the watch. Mine is a good 3 seconds behind with a Nexus 6. The call can go to voicemail before the watch vibrates.
Click to expand...
Click to collapse
it has nothing to do with the watch, I've got a sw3 as well that behaves the same with my 6p. previously I had a zenwatch, and it had the same delay with my n6 and later the 6p
I believe it's the android wear app itself. If you can find the AW 1.3 apk from apkmirror or the like, you should see a difference. Hopefully the new OS update will help alleviate the issue.
Same here with HW Watch Active. Phone get instant Message since Doze Settings on Marshmallow were edited, Watch still delayed...
I am having problems as well. Sometimes I would get notifications on my watch, other times the notifications would be delayed. I just tried and I am not even getting calls to my watch. I had to perform a factory restart twice now in order to get it to work. Why is that? I have a Huawei watch sync with a Huawei Mate 9. I would figure they both should work seamlessly.
any advice would be appreciated
rimz808 said:
I am having problems as well. Sometimes I would get notifications on my watch, other times the notifications would be delayed. I just tried and I am not even getting calls to my watch. I had to perform a factory restart twice now in order to get it to work. Why is that? I have a Huawei watch sync with a Huawei Mate 9. I would figure they both should work seamlessly.
any advice would be appreciated
Click to expand...
Click to collapse
Did you find a solution? I am experiencing the same issue, the incoming calls are not working and I also cant therefore receive calls directly on the watch. I am using an updated Huawei Watch with the HTC One M8, which is also updated to Android 6.0, with the latest version of Android Wear.
Cheers
Badelhas said:
Did you find a solution? I am experiencing the same issue, the incoming calls are not working and I also cant therefore receive calls directly on the watch. I am using an updated Huawei Watch with the HTC One M8, which is also updated to Android 6.0, with the latest version of Android Wear.
Cheers
Click to expand...
Click to collapse
The incoming calls seem to have fixed itself. However, what really solved the issue was that I had to make sure, on my Huawei phone, Android wear was set to close after the screen lock. I made sure that Android wear was always running in the background. Not sure if there is a similar setting on the HTC One M8, but making sure android wear was not in any power saving mode solved the problem for me.
Hope it help,
rimz808 said:
The incoming calls seem to have fixed itself. However, what really solved the issue was that I had to make sure, on my Huawei phone, Android wear was set to close after the screen lock. I made sure that Android wear was always running in the background. Not sure if there is a similar setting on the HTC One M8, but making sure android wear was not in any power saving mode solved the problem for me.
Hope it help,
Click to expand...
Click to collapse
I fixed the issue with a "wipe partition cache" procedure. Thanks
I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.
This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.
Hello, I have a big problem since the last firmware update. I woke up this morning and I had a notification to update my watch to the last firmware (1.0.9.58).
Since then, whoever is calling me, my phone replies immediately and the calls starts counting seconds (00:01 etc) and my watch doesn't ring or shows anything as its screen. In the past, the phone kept ringing and my watch too and i could see on both screens who's calling me. Now after a second, the call is replied on my phone, without touching it or something. You understand that this is extremely weird and dangerous, since i'm not always next to my phone and sometimes i'm doing stuff that I don't want a potential caller to hear... like listening to music or talking to someone else (don't think only the naughty stuff). I'm sure my phone doesn't have an issue, since i didn't change anything and i'm completely sure it's my watch, since i disabled temporarily bluetooth and my phone starting ringing for a call without answering automatically.. Can we do something about it? Did anyone notice the same behavior???
I am on the same firmware, but i have a complete opposite problem regarding calls with my GT2...since this latest update my gt refuses to connect for calls to my P30 pro...
paco8784 said:
I am on the same firmware, but i have a complete opposite problem regarding calls with my GT2...since this latest update my gt refuses to connect for calls to my P30 pro...
Click to expand...
Click to collapse
Same here.
Did someone managed to solve this issue?
iambozhinovski said:
Did someone managed to solve this issue?
Click to expand...
Click to collapse
Try to check if the smart answer (bluetooth) is enabled in your headphones mode.. if not, reset your wifi/bluetooth settings
I had the same issue and I'm using the Oneplus phone. I solve this by switching off auto-answering when the phone is connected to a bluetooth device. Hope it wokrs on your phone as well