[Q] Camera forceclose - No lastpass - Only updated - One (M8) Q&A, Help & Troubleshooting

Hello everyone,
I am having some troubles with stock Camera. It randomly forcecloses when launched.
It doesn't happen always, it actually happens rarely, but sometimes it did while I was in need of a quick pic.
It happens both in landscape and in portrait mode, even if launched with quick setting (volume down button).
I've looked for similar issues around xda and the web; most of them were solved in Lastpass settings, which I don't have.
This is happening recently; before Christmas I updated my firmware to 3.28.401.7 and flashed Android Revolution 22.1 and everything works fine since then except, occasionally, camera.
How can I fix this?
Thank you

Couple folks have reported camera force closed issues due to the "Ok Google" being enabled for any screen, conflicting with the Sense camera.
In the Google app, tap the 3-line menu button (upper left), go to Settings>Voice>"Ok Google" Detection, and verify the "From any screen" option is OFF.
Could be something else causing the issue, but this is what came to my mind.

redpoint73 said:
Couple folks have reported camera force closed issues due to the "Ok Google" being enabled for any screen, conflicting with the Sense camera.
In the Google app, tap the 3-line menu button (upper left), go to Settings>Voice>"Ok Google" Detection, and verify the "From any screen" option is OFF.
Could be something else causing the issue, but this is what came to my mind.
Click to expand...
Click to collapse
The option is already OFF and I've had this issue since before I updated the Google app.
Thank you for your support though.

I thought that this could fix with the first eventual update. It did not.
Any tips?
Please!

Related

say "google" doesn't activate voice search?

Hi guys:
I have noticed a weird thing, I know there's a feature that you can say "google" after holding the home button and drag it to the google icon to activate the voice search. It works fine on me for a while, but I realized that after a while it doesn't work. Moreover, after a reboot, it would work again. Regular voice search still works fine by pressing the microphone button. Anyone know what's going on? I am on stock jellybean btw, but only rooted.
So it only works every now and again?
Also dragging any of the soft buttons up opens google now.
I have the same issue. The hotword option just randomly disappears. If you go into Google Now/Settings/Voice, the option to toggle it off and on is even gone. When you reboot it comes back, but then randomly disappears again at some point.
I had the same problem and realized i had the language under Google Now/settings/voice/language set to English (Australian).
After changing it back to Default-English (US), I have been able to consistently see the "say Google" option in the main Google Now page.
I have exactly the same problem, the language is always English (US), it still randomly disappears.
http://forum.xda-developers.com/showthread.php?t=1769846
Do you use Light flow? I have noticed toggling "Accessibility" off and on when Light flow glitches out for me, or using Swype seems to kill hotword detection. Rebooting always seems to bring it back though
Sent from my Galaxy Nexus using XDA
I use both, light flow and Swype Beta. Which is killing the hot word detection ? How are they interfering anyway :s
I know from reading the issues log Light flow uses the Accessibility service. When you toggle Accessibility on and off, hotword detection disappears. It will just say "Search" in Google Now instead of Search or say Google. Dont know why but try it and youll see best way to avoid it is to not toggle that or just reboot after it happens
is there a good replacement for light flow ?
PeritoX said:
I use both, light flow and Swype Beta. Which is killing the hot word detection ? How are they interfering anyway :s
Click to expand...
Click to collapse
I only use lightflow, not swype, so I am sure lightflow will interfere for sure.
the same problem in here
just got an update of lightflow - we'll see how it rolls
anyway google now 'google' saying works only when EN(US) is set as language
what is more - i see that any internal integration (e.g. saying 'set timer for 10 minutes') works as well only when the overall system language is set to EN(US)
I noticed this last week also. When it wouldnt respond to saying "Google" it didnt say "Search, or say Google" in the textbox on the voice Search (Google Now) page.
I uninstalled Lightflow and not had any issues since.
I've noticed that the hot word and hot word option only appears when you have English us set.
Change to English uk and they both don't work, also the other hot word functions, send email etc don't work as well.
Disabling light flow and restarting the phone fixes it.

OK Google hotword detection doesn't work.

OK Google hotword detection doesn't work at all for me. I can manually select the microphone in Google Now and voice search works, but it doesn't detect OK Google. Furthermore I can't set up OK Google hotword detection from any screen. I can get to the screen where it says to say OK Google three times, which I do, but nothing at all happens. Audio History is on, language is English (US). I don't see any setting on the phone or in Google that would seem to block it.
Weirdly this post was originally only going to be about setting up the hotword detection from any screen, I've never been able to set that up, but at the very least, detection from Google Now worked fine. But just testing it when typing this post up, I realized that even that doesn't work anymore, but it did like a week ago.
I'm rooted but basically stock, no custom recovery. Only change would be deleting a couple stock apps and adding back/home/menu softkeys at the bottom of the screen. What gives? Anyone have an idea?
Simple as disabling on screen phone in settings
I had the same problem and disabling on screen phone in settings fixed it instantly.

[Q] Problems with 5.1.1

My watch was working perfectly before the 5.1.1 update, but ever since the update, it is slow to wake, unable to swipe away cards from the watch face without opening them, the touch sensitivity is TERRIBLE....have to swipe over and over to get it to register, and for notifications I am unable to select "ALL"...can only select "priority" and "none".
Is anyone else having these problems?
5.1.1 problems are being discussed here if you're not aware:
http://forum.xda-developers.com/zenwatch/general/android-5-1-1-ota-files-online-t3109484
No problem in starting a new thread, though.
nhpilot43 said:
Is anyone else having these problems?
Click to expand...
Click to collapse
I noticed that the touch screen seems derpy to me too. Something is definitely weird with the toggle shade thingy. I'm having the same problem with selecting "all". You can get it, but you have to find the exact spot below and to the left and tap frantically like a dozen times. I reccomend using the test app in developer settings and open the touch test. It will display a small grid and it will trace all your touches. Don't worry if it says fail. Just notice whether or not its tracking your finger. To get it to pass you have to turn the lines green by swiping in a certain direction. Mine tracks perfectly so, for me at least, the hardware is fine. Definitely a software issue.
-Andy
Sent from my Apple Newton.
Yesterday I installed the Android M preview on my phone, and so I had to do a reset on my watch. Now all of the touchscreen wonkiness has gone away, and it's working fine!
Before I was unable to get the app list to appear by swiping from the right, but only by tapping once. Also, I couldn't swipe in the center of the screen in the mode selector shade, but only above or below the row of icons. Now that's all working as well.

Can't see full screen in Google Maps

Is anyone else having the issue of their on screen nav buttons cutting off part of the google maps screen? When I'm navigating I can't see the ETA section or hit the 'X' to close navigation. Really annoying. I'm wondering if it's a maps app issue or possibly the ROM I'm using somehow. I'm on the latest ICE custom ROM. Also, it might be related, but when the pop up asking which app i want to use for various options pops up (ie when I click a number to call it asks if I want to use phone or skype) I can't click on the 'Just Once' or 'Always' option because it makes me hit the nav keys (even though I am hitting the 'Always' selection). Thanks for any help.

Tilt-to-wake broken in recent update

Recently (last week or two) tilt-to-wake has stopped working, and the option to enable it no longer exists on the on-watch settings menu.
The toggle for tilt-to-wake is still present in the Wear OS phone app (under Advanced settings) but even when on, the tilt-to-wake functionality no longer worked. The only way to wake the watch is to tap the screen or press the side-button.
Anyone else noticed this? It is driving me mental!
Cheers
Uhh... scratch that. After rebooting watch, new Google App was installed and it is back to working as normal! Should have tried that first.

Categories

Resources