I thought this was the only phase it would follow, if I say okay only, it opens the search...or just okay google. Maybe google now? it is becoming a problem as my phone was on this morning on something searched I had not as it was on charger all night. Was randomly popping up seaches yesterday too. Anyone have this issue and know a way of resolving it? Makes me afraid for USC to get the 4.4 update...Thanks in advance.
Sent from my XT1055 Ghost USC (Moto X)
Ever since camera update and gnow update to take OK Google from search results my motox has been super sensitive. It will go off from nearly anything. 4.4 root.
Sent from my XT1060 using Tapatalk
Ever since I took the I 4.4 ota from Verizon. The touchless control has also been crazy sensitive too. It goes off all the time and I don't know until she says 'the command canceled'. Not sure it a factory reset would fix it but haven't been willing to try that yet. Any ideas what else might fix it from being more sensitive?
Not sure what to do but its terrible for me too on 4.4. I'm going to have to turn it off. Keeps going off all the time.
Sent from my Nexus 7 using Tapatalk 4
I've been having the same problem, phone will be in my pocket or on my desk and I will randomly hear "command canceled"
Its very annoying and happens several times a day, and nothing even close to "OK Google" is being said.
Seems to be a fairly common problem so hopefully a fix is in the works
Sent from my XT1060 using xda app-developers app
Try retaining the okay Google now command. It's important to do it in a quiet room and hold your phone at arms length.
Sent from my Nexus 7 using Tapatalk
I have read other posts here claiming that saying the training phrase more slowly helped with it accidentally turning on.
(I've had no problems myself, still on 4.2.2 with the camera update)
Sent from my XT1058 using xda app-developers app
I've had it turn on watching a trailer for a movie. Restarted the trailer and it popped up again in same spot.
Sent from my XT1056 using xda app-developers app
I've only had one "accidental" fire...
That's in quotes for a reason... My son and I were cooking on thanksgiving... My phone was in my pocket... His nexus 7 was displaying the recipe on the counter...
When the pie went in the oven...
"OK Google, set alarm for 30 minutes"
Nexus acknowledged the command and I told my son to come get me when the Alarm went off.
Obviously, he didn't need to... My phone's alarm also went off.
Sent from my MotoX, using TapaTypo
That's the odd thing, mine worked perfectly on 4.2.2 as well but ever since the upgrade to 4.4 it goes off randomly.
Of course I've tried retraining the phrase several times but it seems to make no difference.
Sent from my XT1060 using xda app-developers app
Yeah that is what's strange cuz I'm on 4.2.2 obviously since US Cellular hasn't got 4.4 yet. Even completely stock besides unlocked boot loader. Have used FXZ's in past week or two in order to lose root. Wondering if I should try a data and cache wipe. Not sure but today was actually pretty good without random searches.
Sent from my XT1055 using XDA Premium 4 mobile app
Related
sometimes when doing things my screen becomes unresponsive and i have to lock it then unlock it for it to work.... grrrr. iam running brokenout 2.0.1 on zv9..... any suggestions?
That's a revolution/gingerbread thing, it happens to all of us (some more than others) at some point. Different devices respond differently to certain roms and apps there's really nothing you can do about it.
Sent from my VS910 4G using xda premium
I've gotten the same thing a few times since I put BO 1.1 on my phone as well. It never happened before then. It could just be a coincidence, though.
Do what i did and get rid of that p.o.s. lol. I called verizon and got mine replaced with a droid 4. Some people got a razor, spectrum, bionic or incredible.
Sent from my DROID4 using xda premium
Better get used to it since you'll have that problem until the day you get rid of this "phone"
I just flashed BO 2.00 and it was happening more often. I just installed the patch hopefully this helps.
Revo #4 isn't even 24 hours old yet and the thing has rebooted twice. Screen in unresponsive plenty... Hell, the screen wouldn't even respond OOB. Vzw is sending me a Droid 4, can't wait.
xjli said:
Revo #4 isn't even 24 hours old yet and the thing has rebooted twice. Screen in unresponsive plenty... Hell, the screen wouldn't even respond OOB. Vzw is sending me a Droid 4, can't wait.
Click to expand...
Click to collapse
Good for you, wish I could get rid of my POS
osafer said:
Good for you, wish I could get rid of my POS
Click to expand...
Click to collapse
Call and complain, you never know what you could get unless you get on the phone.
Sent from my DROID4 using xda premium
Has anyone heard a popping noise when unlocking the kindle. Its happened to me a couple times now. Wonder if its software or hardware issue. Thanks
Sent from my Kindle Fire HD using Tapatalk.
I get the same thing from time to time. Doesn't seem to be an issue if the volume is turned down halfway or lower, but over about halfway and I get it.
Sent from my KFHD using xda premium
I have this issue too
a ha~ it really happen in users' hands ，software issue， I am sure.
It keeps happening to me,sort of frustrating.
Sent from my Kindle Fire HD using Tapatalk.
I was having the same issue. Turned off Dolby Digital in sound settings and seems to have fixed it.
Sent from my EVO using xda app-developers app
Of course now the volume level seems much lower. I hope they fix this issue soon since it doesn't sound nearly as good without Dolby. I sent amazon some feedback on the issue. Hopefully everyone else who has this issue will let amazon know.
Sent from my EVO using xda app-developers app
petes67bird said:
Has anyone heard a popping noise when unlocking the kindle. Its happened to me a couple times now. Wonder if its software or hardware issue. Thanks
Sent from my Kindle Fire HD using Tapatalk.
Click to expand...
Click to collapse
I get this on occasion on my rooted fire HD. It was getting me worried that there was something wrong with mine.
I had the same problem in class today. My volume was turned all the way down, and I also had it in air plane mode. It didn't happen every time I unlocked the screen... maybe four times out of ten. Enough to be very annoying
Sent from my KFTT using xda premium
I am also getting this and in fact returned my original device for that, screen bleed and one other thing that was specific to me. Unfortunately the 2nd one is doing it as well.
From the time I got my phone about once every few hours touchless control activates for no reason nothing remotely close to "OK Google now" is said. Since the update in the play store it happens around 4 times an hour, even to loud indistinguishable noise In a bar. I've tried uninstalling an reinstalling touches control to no avail, as well as re recording the phrase. I'm on stock, us cellular model, ota applied, rooted, unlocked boatloader, any one else have this problem, or a fix?
Sent from my XT1055 using xda app-developers app
I am not experiencing the issue you describe
Sorry you are having that issue. FWIW, I am not experiencing any issues like that so it sounds like something is definitely wrong with your hardware. I would try re-flashing the stock rom to see if that helps. Sorry I could not be of much more help.
I would like to avoid reflashing stock if possible, I've spent countless hours setting this phone up, I've gone 10 days without a flash ha I don't want to fall off the wagon yet even if it is just stock, I'm an ex flashaholic
Sent from my XT1055 using xda app-developers app
When I first got mine it was doing that, because I just had the launch phrase as 'OK Google', and it got a lot of false positives.
I had to wipe my phone for the update, and since I rerecorded the phrase it hasn't falsely come on once.
Try saying the phrase slower.
Sent from my XT1060 using Tapatalk
I'll give it a try,ha it's getting excessive
Sent from my XT1055 using xda app-developers app
9kracing you are a genius, re recording it very slow seemed to work for now, and it still responds when I say it fast
Sent from my XT1055 using xda app-developers app
The shorter the "activation" phrase, the more prone it is to false activation. I successfully programming it to activate off of " hey moto" but it was going off all the time in my truck while listening to the radio. "OK Google" was much better, but still regularly activated during normal conversations with friends. "OK Google now" is the best... It may trigger once a day while having conversation with friends or family, but that's it.
What do you currently have it trained as? I would first retrain it, if that failed, then uninstall the update and reinstall, again If that fails, wipe cache and reinstall the update to touchless... All else fails, back up your apps and data and restore to stock then restore apps/data and set up touchless again.
Good luck
Sent from my XT1058 using XDA Premium 4 mobile app
I can live with some false positives, but my problem is that when they happen, screen gets to sleep, but stays Unlocked, meaning that any touch on it within my pocket starts calling people and such. Anyone else with this problem? Is there a way to relock/protect screen after using touchless control?
Sent from my XT1058 using Tapatalk
I was having false positives five times per hour that's why I made this thread, but I got rid of all false positives by recording the phrase super slow, haven't had a single false start in over a week
Sent from my XT1055 using xda app-developers app
Hey S4A folks,
Haven't been in recently except now that there's news of 4.3 coming out, I've been reading up on it as, to date, I cannot download it yet.
I used Active root on MF3 when I first got the phone but have unrooted since. Here's the odd thing, tho...
The other day, my phone made a long tone/vibration. When I pulled it out of my pocket, the screen said Samsung on the top, on the bottom was a lock icon that could not be moved, and the word "Custom" was either above or below the lock, but I forget which.
I'd never seen that on any Galaxy phone I had and was wondering if anyone knew what it was.
Thanks.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
FYI it happened again this afternoon and then my phone rebooted.
Anyone else getting this type of behavior?
Sent from my SAMSUNG-SGH-I537 using xda app-developers app
Please use the "search" function....you will find multiple posts of people having the same thing.
Sent Via Smoke Signals
Hey all,
I recently (2 months ago) got a brand new HTC One. It's been great so far, love it.
Only issue I have is last week it started going to Speakerphone mode when making calls and receiving them. All I have to do is turn off the speakerphone to get it back to earpiece but it's slightly annoying.
I've tried resetting the device to no avail.
I'm running on the Rogers network in Canada running Kit Kat.
Any ideas would be great.
Thanks!
Basttrax said:
Hey all,
I recently (2 months ago) got a brand new HTC One. It's been great so far, love it.
Only issue I have is last week it started going to Speakerphone mode when making calls and receiving them. All I have to do is turn off the speakerphone to get it back to earpiece but it's slightly annoying.
I've tried resetting the device to no avail.
I'm running on the Rogers network in Canada running Kit Kat.
Any ideas would be great.
Thanks!
Click to expand...
Click to collapse
I had the same problem...it eventually got to the point where only speaker would work and not ear piece...now..the only thing that works is if I have it connected through headset...cyanogenmod fixed all my problems....any sense romss I try to use, give me the same problem...if u don't mind changing tons..jus install cyanogen...but if u find a solution, let me kno, cuz I can't find any info about it or a solution
Try deactivate chome browser and see if it solves the problem.
Skickat från min HTC One via Tapatalk 2
jonas111sanoj said:
Try deactivate chome browser and see if it solves the problem.
Skickat från min HTC One via Tapatalk 2
Click to expand...
Click to collapse
I tried that...didn't work, but may I ask why you think that?...Or some info onto why u think that
Still goes to Speaker phone even with browser deactivated. Arg. It's still under warranty but I'm nervous the ****ty refurbished phone they send me will be worse than this one.
Sent from my HTC One using XDA Premium 4 mobile app
i'm having this same issue...i looked all over the call settings and don't see a toggle that i might have accidentally switched on...anyone figure out a solution to this yet?
Sent from my Transformer Prime TF201
Everyone experiencing the issue have a custom ROM? What is it if so?
Sent from my HTC One using Tapatalk
100% stock for me.. Issue happened randomly it seemed after coming back from a trip overseas
Sent from my Transformer Prime TF201
I'm having this issue at the moment, occasionally I ring people and the speaker phone is automatically on.
First time it happened I didn't notice and someone answered as I put the earpiece to my ear, nearly burst my bl00dy eardrum!
I'm running ARHD 51.0.
Having the same issue since about 1-1.5 weeks or so. Using ViperOne 5.5.1 with latest FW and Elemental X 13 kernel.
Freakadude said:
Having the same issue since about 1-1.5 weeks or so. Using ViperOne 5.5.1 with latest FW and Elemental X 13 kernel.
Click to expand...
Click to collapse
Same here after upgrading to 4.4.2 with sense, never happened on GPE
oksagi said:
Same here after upgrading to 4.4.2 with sense, never happened on GPE
Click to expand...
Click to collapse
The weird thing is that i have been on 4.4.2 for a while now via ViperOne and this issue has just recently popped up (or so it seems to me). So not sure if this is related to sense based rom running 4.4.2. or something different.
Well I do feel slightly better that I'm not the only one. But also wished I wasn't part of this so special group. Ha!
After a little googling people seem to think it might have something wrong with the docking mechanism.
Sent from my HTC One using XDA Premium 4 mobile app
Basttrax said:
Well I do feel slightly better that I'm not the only one. But also wished I wasn't part of this so special group. Ha!
After a little googling people seem to think it might have something wrong with the docking mechanism.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Mentioning the dock makes me wonder if those who've looked thru the call settings have looked thru the dock settings to see if there is an option there to open with speaker phone on? Or in the headphone or bluetooth settings. My feeling for looking in these places is that if for some reason the device thinks it's connected to one of these devices that could be changing it's behavior? Anyway, I don't think I'm having this issue but I rarely get calls and usually when I do I use speaker phone, but I'm also pretty sure that I'm having to turn it on also.
HTC replied to someone on Twitter to boot into recovery and clear cache who also had reported the problem...they showed instructions on how to get into stock recovery and do it. I'm wondering if anyone can try that. Either stock or custom recovery.
Sent from my HTC One using Tapatalk
I'll give it a try today and get back to you on the results.
I know a full reset doesn't do the trick so it's worth a shot.
Sent from my HTC One using XDA Premium 4 mobile app
gustav30 said:
HTC replied to someone on Twitter to boot into recovery and clear cache who also had reported the problem...they showed instructions on how to get into stock recovery and do it. I'm wondering if anyone can try that. Either stock or custom recovery.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
So far so good. Tried calling home and my voice-mail and it didn't happen. It doesn't necessarily start up right away however so I'll have to keep an eye on it. I'll respond back here when/if it reappears.
Basttrax said:
So far so good. Tried calling home and my voice-mail and it didn't happen. It doesn't necessarily start up right away however so I'll have to keep an eye on it. I'll respond back here when/if it reappears.
Click to expand...
Click to collapse
And vola! It has returned. So we can wipe the "wipe the cache" fix off the board.
I have the problem randomly just satarted after 4.4.2 update. Stock unlocked phone still have it after yesterday's update.
Sent from my HTC One using xda app-developers app
qayak said:
I have the problem randomly just satarted after 4.4.2 update. Stock unlocked phone still have it after yesterday's update.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
So i guess this is a general sense 4.4.2 issue then and not custom rom, kernel, other specific. Strange that it seems to only start after a random amount of time as i deffinately did not have this issue for quite some time after upgrading to 4.4.2 based rom.