Hi guys,
Updated to 10n and rooted recently.
Been having a bunch of issues that I didn't have with 10h stock. Trying to figure out if they are common issues for everyone.
OK Google detection from any screen used to work reliably, even in the lockscreen while locked. Now it stops working until I open the Google search app. Then it works from any screen for a little bit and stops again.
Are others having this issue as well?
Thanks
Never mind. Turns out it was an issue with the Google search app. An update released today fixed the problem
Related
Hi there.
I am pretty new here & didn't read up on billboards yet, but I had something very strange happening to me yesterday. The phone automatically downloaded a 'Google Voice Search'-update and since it's installed, I keep encountering problems.
The most annoying one - the camera doesn't work anymore. If I click on the icon, the screen just turns black and remains like that until I either hit the HOME button - or if I wait long enough - I get an Force close-popup.
Furthermore, after calls, the screen also turn dark sometimes, but turn back on after a while. Other that that, everything works fine as before.
Am I the only one?
Does anyone know whether it's update-related or whether it's just a coincidence. Everything else works fine, so I doubt it's something else.
Is there a way to reinstall the camera app without having to flash the phone. As I said, I am a newy & don't want to end up with a brick.
The malfunction started only yesterday after the auto-update. I am on a Spanish GSM network, but I guess that's not of much relevance. The phone is running Gingerbread 2.3.4.
Tks for any suggestions.
t.
Hey people of XDA!
I've got a weird problem with my Google Maps app. Every time I rotate the map and touch the compass button to restore it to north pointing up, it doesn't fully rotate, it takes multiple presses, and stops every 0.5s ish. The same thing happens with the My Location button.
Here is a video link:
Does anyone have any ideas? It never happened before I rooted and now it always happens despite what rom I use, I'm using ViperOne 3.5 at the moment. I've tried literally everything! Different firmware, Android 4.2.2/4.3, full wipe and flash of roms.
The actual compass and GPS work perfectly fine too.
Thanks in advance!
Update: I've been testing previous versions of Google maps and it's only been happening from v7 onwards. I've downgraded to v6.14.4 and everything is working perfectly as it should.
Guess I'll stick with this until there's a fix for this rare bug.
Must be someone having the same issue?
My bad I posted in wrong thread
Jaspal93 said:
My bad I posted in wrong thread
Click to expand...
Click to collapse
Lol, anyway I found the issue...
I usually use the developer options to set the animations on 2x, I like animations
It turns out it was the animator duration scale. I set it back to 1x and maps is working perfectly just like before, running v7.5.0 right now.
Just thought I'd keep this updated incase anyone else ran into the same problem.
For some reason, tilt to wake stopped working. I have no idea why. It was working fine yesterday morning in the metro, but stopped working during the day. The watch is paired with a HTC One M7, running a stock Sense ROM. I've converted the phone to GPE back in December and the watch worked well, but now I reinstalled a stock ROM because GPE was draining my battery real quick and, again, the watch worked well for a couple of days, but now, nope. I tried resetting the watch, but no result. Is there any other way to figure out what the problem is without reinstalling every piece of software? I mean, I'd like to test the sensors to see if they have a problem or smth and if they turn up to be good, well, I might contact Google cuz something's not working. Yes, the tilt to wake option is enabled in the companion app.
So, does anyone have an idea of what I can do? I couldn't find any info on any forum
Thanks in advance :3
Hi to everyone,
Lately I began to experience a weird issue on my OnePlus 3T. More precisely the GoogleNow application starts by itself when the phone is off. It wouldn't be a problem if it weren't talking after it registerd the voice around. Google previously eliminated the unlock of the phone with the voice recognition feature so I suppose it's a bug in OxygenOS. Has someone else experienced this ? Any solution ?
P.S. Sometimes I use Google Now therefore I prefer it to be enabled.
Sometimes not even fully saying OK Google will still activate it. Like"OK G..."
tzbigworm said:
Sometimes not even fully saying OK Google will still activate it. Like"OK G..."
Click to expand...
Click to collapse
The funny part - the "OK Google" doesn't work when the phone is off. I tried several times without success.
Hi All,
I just recently encounter the following error on my Huawei P9 Plus, when I use an application that requieres the need to record (Shazam, cámara, sleep as Android) I pop up message appears showing that "com.android.googlequicksearchbox:interactor" will not be able to record right now, I read in other forums that the main problem is with the OK Google functionality to identify in any screen, if I turn it off the message disappears, the thing is that I use the OK Google functionality heavily, so the solution does not work for me, I have cleaned the cache of the apps, uninstalled and installed and even wipe cache partition with no help...
Anyone with the same problem?
This just recently started, noticed it yesterday
I have attached a image for your reference.
Same thing happened to me. In order to resolve this, i've disabled the "Ok Google" detection from any screen.
Somehow with recent updates of Google Play or whatever it is might have triggered this error.
Clear cache & Reset Factory doesn't solve this either.
I got the same problem on P9 lite. With some search I found that almost all the guys reporting this error seem to be using Huawei phones. I would also like to see a fix, hope someone comes up with something like disabling "ok Google" detection when another app starts recording audio.
Seems to be due to an update with the Google app, as it happened to me all of a sudden (a few months back), without any changes other than app updates. All i've managed to find on it are from fellow Huawei users as well.
For a phone that is aiming at other, more established, flagships, they really do seem to **** up on the little details (not counting the 'shoot with a DSLR and claim it's a P9' debacle or the more recent emmc/ufs outright lie, which aren't so 'little'). After paying so much, why should I have to choose between having OK Google available on all screens (as it was designed to be), but have to deal with error messages, or disable the feature (basically making it next to useless) just to clear the errors?