Just got my Honor 5X, but previously tested the GX8 and saw the same issue. Have also tested across stock Android, TouchWiz, and Sense, and confirmed this is an EMUI issue, so I'm hoping someone can help me fix it or work around it.
I use CarHomeUltra while driving, and the app can start/stop Car Mode, so that while active, pressing the home button takes you back to CarHomeUltra, instead of your normal homescreen.
The problem is, when this option is chosen, I get an error message that Car Mode cannot be activated because "Android HwResolver" is the default, and that I need to clear the defaults. However, when I go to "Android HwResolver" in the App settings, the "Clear Defaults" button is greyed out, indicating that there are no defaults.
This is *really* annoying, and I'm hoping someone can help.
I'm not currently rooted, but am comfortable rooting if that's the best way to resolve this.
the orange bandit said:
Just got my Honor 5X, but previously tested the GX8 and saw the same issue. Have also tested across stock Android, TouchWiz, and Sense, and confirmed this is an EMUI issue, so I'm hoping someone can help me fix it or work around it.
I use CarHomeUltra while driving, and the app can start/stop Car Mode, so that while active, pressing the home button takes you back to CarHomeUltra, instead of your normal homescreen.
The problem is, when this option is chosen, I get an error message that Car Mode cannot be activated because "Android HwResolver" is the default, and that I need to clear the defaults. However, when I go to "Android HwResolver" in the App settings, the "Clear Defaults" button is greyed out, indicating that there are no defaults.
This is *really* annoying, and I'm hoping someone can help.
I'm not currently rooted, but am comfortable rooting if that's the best way to resolve this.
Click to expand...
Click to collapse
Hi Ricky, thanks for reporting this issue. I have escalated it to the honor software team.
the orange bandit said:
Just got my Honor 5X, but previously tested the GX8 and saw the same issue. Have also tested across stock Android, TouchWiz, and Sense, and confirmed this is an EMUI issue, so I'm hoping someone can help me fix it or work around it.
I use CarHomeUltra while driving, and the app can start/stop Car Mode, so that while active, pressing the home button takes you back to CarHomeUltra, instead of your normal homescreen.
The problem is, when this option is chosen, I get an error message that Car Mode cannot be activated because "Android HwResolver" is the default, and that I need to clear the defaults. However, when I go to "Android HwResolver" in the App settings, the "Clear Defaults" button is greyed out, indicating that there are no defaults.
This is *really* annoying, and I'm hoping someone can help.
I'm not currently rooted, but am comfortable rooting if that's the best way to resolve this.
Click to expand...
Click to collapse
I'm glad I found this thread. It's not exclusive to the Honor 5X. I'm using a Mate 8 (AL10) 128gb model on T-Mobile and run into the same issue. I typically have been closing it out, anytime the prompt comes up, but seems like a Huawei thing more-so than specific to a model.
Probably in the kernel. Pry-fi (which changes your Mac address) also seems to have some problems. So does the pcap_loop command.
wimbet said:
Hi Ricky, thanks for reporting this issue. I have escalated it to the honor software team.
Click to expand...
Click to collapse
Same problem with P8Lite! Any news from the software team? Thanks
Sorry for my massive editing!
I use Car Home Ultra on my Honor 8 and ran into the same issue, albeit only after installing Android Auto.
Try this:
Install a second app that 'accesses' Car Mode.
Go through the setup process if applicable.
When prompted choose your preferred app as default.
I did this with Car Home Ultra as my main app and Android Auto as second. I was prompted for the default app a couple of times upon exciting Car Home Ultra, but finally it seems to work.
Related
Hello guys,
I am having this issue with my device - sometimes when I press the home button the Voice talk / command powered by Vlingo starts. I always press the button just once (I understand that it should happen when one double-presses the home button) and it is very annoying :-(
Note, that I have Settings/Motion/Double tap turned off as well. Is there any way to fix this or do you have any idea what may be wrong??
Thanks in advance!
Sent from my GT-I9100 using XDA App
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Chef_Tony said:
while in the motion settings, you can see the tutorial clip and that double tap has nothing to do with the home button, but with double tapping the top side of the device to start voice control instead of saying "hi galaxy". so even with that switched off, your device will react to hitting the home button twice and does not really help diagnose the initial problem.
either you have a slight hardware defect in the home button, a software issue (or maybe user error). since hardware would be more severe, let's see the software side first. what exact rom do you have? device rooted or not? anything that could mess with voice input (connected bluetooth hands free, market vlingo or other tts or stt software installed...)?
also, just to exclude user error, let another person try.
P.S. are there special circumstances when this happens? like only from deep sleep, only when charging, with a connected headset, running certain apps or whatever?
Click to expand...
Click to collapse
Hello, thanks for your reply. I am running the device with an unmodified SW i.e. stock rom (having a branded phone from orange slovakia), no rooted just some apps installed from the android market. It is XXKE4/XWKE7, running android 2.3.3. I dont use bluetooth or handset nor dock or anything like that.
The issue seems to be completely random to me, while I usually notice it during browsing web with opera, but it happens with more apps. I don't know what is tts or stt sw, nor market vlingo. If you would like to know some more details please let me know what would be relevant for you.
I already thought about the hw issue, but I am not sure if they would accept the warranty claim as it is quite random. I thought there would be some way to completely disable voice talk as I dont expect to use it anytime in the future anyway...
As of the user error, it happens both to me as well as to my gf while using the phone for common internet use.
Sent from my GT-I9100 using XDA App
ok, that gave us something to work with. for future reference, when asking a question like this, it might speed up the process by giving as much information in the initial post as possible and let me explain why:
the fact that you use your unrooted stock rom tells me, that it is not a common and maybe reported bug that comes with a custom rom, and with an unrooted device, it is rather unlikely, that you screwed up a system component like this.
bluetooth, docks and handfrees could influence the voice input and its triggering by having their own triggers, but that is not the case.
if it happens to other people with your phone as well, it excludes your personal behaviour, tremors or whatever (no offense, you never know, just to cover everything, some people are shaky).
if it happened only in a special state, like only while sleeping for a minute or while charging, it would ensure, that it has something to do with deep sleep.
about the other things: with tts i was referring to text to speech, the engine that reads out display content, like incoming calls, text messages or navigation instructions, stt refers to speech to text, like voice input, saying hi galaxy, telling where to navigate or dictating notes...
vlingo is the engine that is used for voice talk and voice command and there is also a 3rd version, that can be downloaded on the android market, coming with yet other features and having them all present and maybe screwed up settings might have influenced anything there, however, this doesn't seem to be the case either.
so this leaves few options for how to proceed. in your place i would start off with reading this thread: http://forum.xda-developers.com/showthread.php?t=1097153
it deals with home button issues and a theory on how the home button sometimes might react as much as 15-30 minutes later than initially pressed, which might coincide with an actual press and being registered as a double press (although that's a stretch at best).
and when it comes to a next step, if you made sure, that does not apply to you, i would be uncertain, which way to go. a factory reset might help, but if, after hours of setting the device up again, you realize there has not been any change, it was nothing but work. then there are 2 things left:
either flash a newer rom using odin and any rom from here: http://forum.xda-developers.com/showthread.php?t=1075278 (full guide and download links included)
OR decide to send it in for warranty first and see what's what.
flashing a rom might solve your problems but influence your warranty state, if not done correctly and cautiously, which would make sending it in risky.
sending it in first and not getting that bug recognized or repaired for free would mean you might end up with weeks without your phone and/or a huge bill and the same issue as before.
i guess i would get a usb jig, read up on flashing, try several stock roms, not root the device and see if the bug is gone, if not, flash back to stock, make sure the flashing is not traceable and then try a local store or your carrier for a hardware replacement or repair.
Hi guys and gals. I'm new here but I have reading your posts and really enjoy the info. I,just bought the gear s. Upon going through the settings I tapped the accessibility bar. There's an option for reading alerts aloud. I hit that by accident. Now the phone will not scroll on the app menu. It goes halfway and stops. It's like frozen. So in order for me to do a reset I need to get to the bottom of the app screen but it will not scroll. So I did a rebooting reset with the power button and returned it to factory but as soon as I choose the reading option it still does the same thing. Has anyone encountered this. I love the watch but even though I may not use that accessibility feature I am afraid that I may encounter other issues down the road. Thanks in advance for any insight.
I would try, but I don't want to reset my device. Sorry
No problem I appreciate the response. I picked up a new one from verizon. I went to best buy and the display gear s did the same thing. So maybe it just needs a update.
Hi,
I just purchased the LG G Watch (my first watch in more than a decade!) and am impressed overall. There is one bug which is bothering me. When I swipe down from the top to access the options there and swipe towards the right to finally reach 'Settings', and then click on it, my watch hangs for a brief moment. It brings me back to the watch face where the second and minute hands do not move at all. I again have to swipe down and go back and click on settings to actually gain access to Settings, and after that it works fine.
Anyone else suffering from this weird behaviour?
Thanks
Yes happens to me too, it's a bug.
Had hoped latest update would fix it, but no.
It's been reported numerous times in the android wear forum.
HI all... hope you can help. After doing some research, I fear I may be lost.
I have an Iconia b1-720 I use for home automation. Started getting the "unfortunately, com.android.settings has stopped". I would go away for a bit, but always come back (along with other similar warnings.
I decided to just power/volume reset to factory settings... since it's pretty easy to put the apps I need back on the device. But, while that wiped my device, now it just boots to that message immediately. If I "ok" out of it, it comes right back. Nothing I can do to make it go away.
Looked into rooting, but all the directions I found say you need to turn on developer mode in settings to be able to do that. Alas, I can't go into settings
Any help/thoughts, other than junking this?
As an FYI... I know that I can get a cheap replacement of a different model, but I can't find any of the 720's any longer. I've custom build picture frames to hold this specific device, along with a cutout for where the camera is (detects motion and turns on), so i'd love to get this working again.
Thanks for any pointers.
thomasgruver said:
HI all... hope you can help. After doing some research, I fear I may be lost.
I have an Iconia b1-720 I use for home automation. Started getting the "unfortunately, com.android.settings has stopped". I would go away for a bit, but always come back (along with other similar warnings.
I decided to just power/volume reset to factory settings... since it's pretty easy to put the apps I need back on the device. But, while that wiped my device, now it just boots to that message immediately. If I "ok" out of it, it comes right back. Nothing I can do to make it go away.
Looked into rooting, but all the directions I found say you need to turn on developer mode in settings to be able to do that. Alas, I can't go into settings
Any help/thoughts, other than junking this?
As an FYI... I know that I can get a cheap replacement of a different model, but I can't find any of the 720's any longer. I've custom build picture frames to hold this specific device, along with a cutout for where the camera is (detects motion and turns on), so i'd love to get this working again.
Thanks for any pointers.
Click to expand...
Click to collapse
Any help here? thanks!
Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Sleep mode? as in while screen is off? or another mode?
skygear said:
Sleep mode? as in while screen is off? or another mode?
Click to expand...
Click to collapse
Yes. When the screen is locked.
My phone was like that at one point, I am on Pie now and I had to go into the settings and make sure it was set to work even when the screen was off. Took a minute to find, have you checked there?
Settings/Google/Search, Assistant and Voice/Voice/Voice Match
I have. The phone vibrates when the screen is off and I say "OK Google" but is the screen remains black until I press the home button.
I'm thinking now that perhaps it has something to do with security and not with Google Assistant. I'm going to check my security settings. Maybe there's something there.
Come to think of it, I've had that happen before, not now but some time ago. I never sound effects, never really tried, somehow it just seemed to resolve itself after a while I guess. Good luck and keep us posted, you might be right in that it has to do with some security setting or something.
This? Access with voice match?
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
YrrchSebor said:
There is also that one underneath that says 'unlock with voice match', for use if you have a screen lock set up I guess. Did you try that one as well?
Click to expand...
Click to collapse
I’m sure that’s the option the OP needs to use.
I think it's a common problem with Google assistant and potentially the same as the 'voice unlock paused' issue, I've seen people complaining about both on pixel forums as well as on here (if Google can't get it right with their own phone what hope do we have!!). There were a few steps around deleting the voice model and resetting the smart lock agent (see screenshot). I did this and retrained the voice model in absolute silence which seemed to work for a bit but has since stopped. Annoyingly it doesn't seem to take into account when I'm at home and the phone is unlocked with smart lock!
xc rider said:
I’m sure that’s the option the OP needs to use.
Click to expand...
Click to collapse
OK. Here is my screenshot of the settings that I have on my phone. Access and Unlock with Voice Match are turned on.
Let me reiterate. The phone is reacting to "OK Google" on every screen so the voice match is working.
The problem is that when when I am on the lock screen and I say "OK Google" the phone vibrates, acknowledging that it heard the prompt but it does nothing until I press the home button or power button.
Have a look at this video. (I distorted for privacy reasons the audio because my phone and tablet were reacting when I was playing back the video):
https://youtu.be/fO3nsJ215eo
I have the S9+ on Rogers and thankfully, this feature continues to work flawlessly after the upgrade as I use it often in my daily work..It actually seems to be more responsive after the update.
It can be very frustrating when the feature randomly stops working but it is usually due to an update on Google's end that causes it as I can usually fix it by going through the voice setup steps after an update..
In extreme situations you may want to uninstall and then reinstall the Google app..
Had the same problem myself and fixed it, just go to app info for Google and clear the cache and clear data, worked a treat for me
Roli001 said:
Hi,
I have an S9+ with Rogers in Canada, which was recently upgraded to Android pie. Ever Since I have not been able to use Google assistant when the phone is in sleep mode. Prior to the update, I was able to say "OK Google: set the timer for xxx minutes", when the phone was in sleep mode. But now it doesn't work anymore, other than vibrating. It still works on other screens, just not when the phone is asleep.
I called Samsung but they were useless telling me that I need to press the home button and that it has always been so and that nothing changed with Android Pie but that is BS.
Can other Pie users please verify, that OK Google works on your phone when it is in sleep mode and if anyone else has the same issue as I and if you have a solution.
Thanks,
Roli
Click to expand...
Click to collapse
I'm on an S9+ with Bell in Canada and I can still unlock my device with voice when it's sleeping even though it gave me a notice that I would no longer be able to.
For some reason I've lost the ability to voice control any of my smart devices through Google Home. Seems like a related but different problem.
That, the lack of pro video mode and the brutal battery life have really turned Pie into a nightmare for me..
Hope they release fixes for these issues or I'll have to look at flashing..