Okay Google hotword detection not working properly - Nexus 6P Q&A, Help & Troubleshooting

Like the title says, hotword detection used to work great, but in recent months seems to have gotten broken. I'd say it only works 30-40% of the time, where it used to be 90-95%. Even when it does detect the hotword, it will frequently fail to do anything. It will make the sound acknowledging that it is listening, but nothing will come up on the screen.
I've attempted to retrain/delete the voice model, tried reflashing the stock image. I'm trying to determine if it's something specific to my phone, or if this is a wider issue with the current build of Android. Based on how it fails to do anything, I'm suspecting this is a software issue rather than a hardware issue.
I'm down for any suggestions. This is a feature I use a ton, and would love to get it working again.
On a side note, I used to be able to long press the phone button on my wired headphones to activate the okay Google feature, but around the same time this stopped working, I lost the ability to do that. Anyone know why?

Related

[Q] Phone sensors unresponsive for a few secs when receiving call.

Hello everyone. I've done a few searches on here but haven't found this exact problem. Relevant details without extra background info are in bold.
My wife and I each got an S4 with Sprint's recent BOGO promotion. My phone has had no issues. It came with MDL in the box, which I updated to MF9 via OTA, flashed TWRP via Heimdall in Linux, rooted, and installed the hotspot mod.
Her phone - completely stock MF9 and new from the store - has had problems, one of which I've so far been unable to fix. (How I wish it were mine. I develop for Android, but this is much more of a pain for her.) Hers already had MF9 at the store. It had the Google Services Framework/Core Apps runaway process issue with heat/battery drain from the start - which I fixed. However, it also has unresponsive sensors for ~3 seconds when receiving a call. It's almost as if there's some lag in activating the sensors. The phone is otherwise snappy with no other lag noted.
- Hard reset has been tried.
- The touchscreen is unresponsive during this time, though the display functions.
- The gesture for answering (when enabled) also does not work.
- We haven't tried enabling the home key to answer, but this will be next.
I've seen this before with Android a good while back. It was an inherent problem with Gingerbread on many phones. Haven't seen it pop up in Jellybean at all. In trying to diagnose, I've ensured that all bells and whistles are turned off. No air gestures are on.
We'd really like to get it working as it should. Has anyone else experienced this? Any advice?
Many thanks!
I believe this is more of a stock software issue. I have had the issue since day one.
When I turned off svoice and some of the other added features most of the lag disappeared. Svoice is pretty good at creating lag as far as ive seen.
Voice response seems to create th lag as it is awaiting a voice command from you.
This is what I have noticed anyway.
Sent from my SPH-L720 using xda app-developers app

Backdrop Not Activating Automatically

Has anyone else had an issue where the backdrop refuses to kick in automatically after the preset time? It simply won't activate for me on its own (neither daydream nor color works). If I manually start it from the settings menu it will launch. I've tried rebooting the device and it still won't work. Any ideas?
UPDATE: I've been doing some troubleshooting, and after uninstalling Plex and rebooting, backdrop starting working again. I then installed Plex again, and it briefly worked, but then stopped.....so I'm wondering if Plex is causing the issue. I suppose the next step is to leave Plex uninstalled for a while and see what happens.
I have the same problem. What happens is the screen just goes black when it is supposed to go on. Like you I can run it manually through the settings. I don't even have Plex installed so I have no idea why it stopped working. I can't understand how there is no simple way to restart the player too...
Based on my experiences so far, it appears that Google rushed this unfinished prototype out to the market. I have so many little problems and find that video playback is choppy at times. This thing needs some attention quickly.
arecad said:
I have the same problem. What happens is the screen just goes black when it is supposed to go on. Like you I can run it manually through the settings. I don't even have Plex installed so I have no idea why it stopped working. I can't understand how there is no simple way to restart the player too...
Based on my experiences so far, it appears that Google rushed this unfinished prototype out to the market. I have so many little problems and find that video playback is choppy at times. This thing needs some attention quickly.
Click to expand...
Click to collapse
I agree. It definitely seems pretty buggy at this point.
So far, in my case though, it's been running much better since I uninstalled Plex. Also, I was having an issue with the microphone on the remote controller REALLY sucking. It would hardly ever work properly. It would regularly not pick up any of what I said or pick up only the first word or so. BUT, since uninstalling Plex, the microphone has been working perfectly. It's like night and day. I'm going to keep monitoring it, but it seems like Plex was definitely causing this problem for me in addition to my backdrop problem.
With all of that said, perhaps you installed a different app that's causing problems for you?

SM-N900W8 & CM11 M12 bugs and issues :(

I have a Canadian Note 3 (SM-N900W8), it's KNOX 0x0 rooted and I have CM11 M12 installed. I have been using only the M builds since I got this phone, I didn't even set up Touchwiz when I got it, I rooted and installed Cyanogenmod out of the box.
Now, with the new CM12 builds coming out, what happened to CM11, are they going to fix the remaining issues? Or did they just bail on legacy KitKat users because I'm having TONS of problems and I don't want lollipop, it runs like absolute crap for the nightlies right now and CM11 M12 isn't much better. Bluetooth takes a couple of attempts to connect, when it does my phone runs super slow to the point it force restarts. For instance, if I'm driving around, listening to music on the car stereo, pull over some where, find a new album on Google Music, start playing that, it's all good, do this a few times, every time I use my phone it gets slower and slower until it force restarts and then bluetooth has trouble connecting again. I've tried this on a few other vehicles of different brands and aftermarket stereos and it's the same result.
Audio is all funky when bluetooth is on too, it sounds like robots for the system sounds and if bluetooth drops while it's connected the music starts playing from the phone and sounds all roboty. I always do clean flashes too and the latest Paranoid Android GAPPS every time I reflash, the ROM is fine out of the box, works flawless for the first few days but after awhile, it becomes so bad I have to backup, wipe, reflash, and start over for another few weeks.
Another issue is somewhere between M8 and M12 one of the builds corrupted my SD card, I tossed in a second new card, it was corrupted again, FutureShop won't give me another one and said my phone is breaking them so I'm SD-less right now.
There are also quite a few apps that force close, but always at random, it's never when doing the same thing over and over, for instance, I can be scrolling through G+ and it tells me settings has stopped working, wasn't even using settings, didn't even have it open, haven't clicked it since booting my phone, just randomly stops working for no reason, this also happens all the time with the Camera, it says it just stops working when I haven't even used it and then if I try to use it, it says the camera is disconnected and won't work until I reboot.
I turn my phone off every night while it's charging and turn it back on every morning so every morning it gets a fresh restart, and I have to restart my phone probably 5ish times a day, if I'm using bluetooth more then normal then there's quite a few more unintentional reboots in there as well.
The last issue, which is a known issue is NFC not working, is there a fix for this yet? I kinda miss this feature and with how flawed CM11 is getting I don't know where to turn since they always seemed to be the most stable out of everything I've tried.
Any before anyone says Temasek's CM builds, I tried it, the final for CM11, it was worse then M12, it's exactly the same as M12, but every issue happens more frequently. Also, the pull down menu (when pulling down from the top right to show toggles), the bottoms of the last row was cut off so it didn't look very appealing either, it also used WAY more battery life, I usually get a full day out of one charge, so around 18 to 20ish hours on one charge, with temaseks cm11 I had to charge my phone half way through the day, sometimes my phone would just die on me without me knowing, the battery usage was always Android System.
A new problem that just happened lastnight was Google Keyboard was deleted and only the voice search would work, but "voice search can't be reached" so I couldn't search for another keyboard app from the playstore. I also used the stock GAPPS so AOSP keyboard is replaced with Google Keyboard, I had to reflash again this morning because I couldn't figure out the keyboard thing, there wasn't even a keyboard under languages in settings so I had no options to pick which keyboard to use. When I reflashes this morning I used the Modular GAPPS to it keeps the AOSP Keyboard just in case this happens again but I'm getting really tired of only having a reliable phone for a few weeks.
So, are there any fixes for these issues?
Bluetooth taking multiple attempts to connect
Bluetooth forcing random reboots
Bluetooth making audio from device all funky and sounds like a robot
Corrupting SD cards
Random system apps stopping without me even using or opening them
Google Keyboard vanishing
Are there any stable ROMs I could try for the HLTE? Maybe one that has working NFC? I'm almost thinking of going back to stock *throws up in mouth* but I don't know what else to do with how many bugs there are and Lollipop is only getting worse with the issues.
I'm also trying to avoid Lollipop because everything is white, Note 3 is an AMOLED display, each pixel illuminates on it's own so white screens use WAY more battery life then black ones which was a feature of Temasek's CM11 that I liked, had the option in settings to make everything black like the good old days.
So guys? Really out on my luck here, not sure what the next step is, any fixes for these problems? Any other ROM's I could try? Would flashing a new recovery and reflashing CM11 M12 fix some of these issues? I'm using Xiaoli CWM v6.0.4.7(20140125). Would the fact that KNOX isn't tripped have something to do with this? I really don't understand why there aren't more posts for these issues which leads me to believe I'm one of the only ones experiencing them.
Any help or suggestions would be greatly appreciated
EDIT:
I forgot to mention that when recording audio or video, it's as if the mic gain is set on full so even the slightest sound is pure distortion, normal talking volume and it clips, I found an app that lets me choose between the mics and when I pic the external mic, it's all muffles as if something is covering it but my phone wasn't in a case while I was testing so I'm not sure what the deal is there but I can't record any decent audio with this and when I record in 4K using Cinema FV-5, all the videos turn out looking like Anaglyph 3D but all pink and green, it's really weird and I don't understand why, but 1080p at 60fps works fine.
I am on CM12 and luckily have had no issues at all. I came from KK 4.4.4 and still have the NB7 BL and modem. I tried one of the guys slim ROMs alpha builds but had issues (probably operator error) but I've tried Bluetooth, GPS, WiFi , LTE etc and everything is good. Not sure what to tell you. I do however always wipe internally and d/l all my apps again through WiFi. A bit cumbersome I know but it won't give me any residual data.
Sent from my SM-N900W8 using XDA Free mobile app

Nougat update bug with smule app

I love the new update but it has made my experience with smule a living hell. It was working perfectly last night before the update then right after that's when I noticed issues with the app. Whenever I record the audio is skipping and stuttering and I am unable to record any songs. All of the other apps I have used have worked fine it's just this one app in particular that I am having an issue with. I tried uninstalling then reinstalling and the problem still persisted. I use this app often and i really hope I can fix it soon. I also tried clearing cache and data and that didn't work either. If anyone could help me i would really appreciate it thank you
You Aren't The Only One
I'm experiencing the same thing you are with Smule. Maybe it's compatibility changes after the update to Nougat. Smule needs to fix it asap
However, I feel it might take a awhile. It took them so long to get phones on sync with audio and now they have to start over. S8 Samsung users in the future will not be pleased if this is still a problem. Maybe we could find something in our settings that would help besides the application itself.
Here is some quick fix i found myself incidentally..
while recording if you realize the mic is not working, immidiately lock the screen then unlock it, the mic will be working after 2-3 second, sometime it takes to do another lock and unlock, then you can restart the song and mic will be working properly... this will continue for several song until th problem recur, then lock and unlock your phone again. for now this fix works for me

Audio Crashing

I apologize if this ends up being long winded, I want to lay out all the details.
So I recently purchased (what I had believed to be) second hand Nexus 6P. It is in perfect physical condition however, no signs of ever being used. Battery is great, performance is great, speakers are great, camera amazing, and screen is perfect. However two odd things started to occur which I believe stems from the same issue. When hanging up phone calls the hanging up process would hang for a long while and either eventually hang up or the system would soft reboot. After reboot notifications are still set to priority only "call management", although it is easy to adjust and bring it out of that. However no audio/mic works at all (Play Music and YouTube give an error that they cannot play). No audio from speaker, or from headphone jack. I could however connect to a Bluetooth speaker and audio plays just fine. I then went to do a proper shutdown of the phone (using the power button menu), and when I manually booted it back up all audio works find again. I plug in headphones and start listening to music on Play Music. After a while however, playback fails and all the audio on the phone is once again dead...queue soft reboot. And repeat the whole process again. If I'm listening to headphones and I do anything to activate the microphone, audio crashes and go through the whole process again.
So I decided to make sure it was all up to date all the way to OTA 7.1.2. Once I did and I tested, the same issues above occurred over time. So then I thought maybe if I used Nexus Root Toolkit and did a full manual wipe and reinstall of 7.1.2 factory image from Google. Phone issue initially went away, but audio playback through headphones persisted and eventually the phone issue manifested itself again.
Today I decided that I do a full wipe again and try and install Pure Nexus 7.1.2, non rooted with BeanGapps and vender image (following the entire process here to a T.) I have not been able to replicate phone issues, however the audio playback and headphones issues are easily repeatable.
TL;DR - So this leaves me with a few things;
1. I can use the phone by never connecting it to external audio source perfectly fine, no problems at all.
2. Phones calls may sometimes get stuck at hanging up, and the result is a crashed audio system.
3. The only way to temporarily solve this issues is to shutdown via holding down lock button and Power-off using the menu that appears. And then manually starting the phone back up again.
So I'm not sure if this is a hardware or software issue. The fact that it persists between full wipes and reinstall of different roms makes me think it to be hardware. Although the temporarily fix of proper shutdown and manually start back up makes me think the OS/Kernal is somehow "clearing a buffer" or something in it's proper shutdown process. Which without doing leads to the audio system being completely down. Therefore on soft/dirty reboots the audio system is still down.
As an added bonus my sim card was a Micro SIM, before I opted to take the scissors to it instead of buying a nano sim. It works (so I thought), it just doesn't fit in the tray quite right. I tested recently with a proper nano sim from a different phone, and everything worked perfect. Then I swapped my franken sim back in and...it worked perfectly fine.
I did search for this issues in previous posts but all I could find was this. The issue (s)he describes is exactly the same issue as me, but his/her solution does not seemed to have worked. I am inclined to try doing a full wipe again and flashing completely stock older version though.
Any help, suggestions, etc are greatly appreciated. And thanks to the developers of Pure Nexus, it seems to be very polished and I'd love to use it daily driver.
Since you are having the issue after a clean install of stock and a clean install of Pure Nexus I don't see how it could be anything but a hardware issue. You could try to flash a custom kernel if you really think the kernel is an issue but I doubt that it will do much good. You could also try a clean flash of a different rom (I recommend Dirty Unicorns which is very smooth and stable) but again I doubt that it will do much good since you seem to have a hardware issue. You might have bad memory which is getting cleared when you reboot the phone.
I fear you may be correct. When you talk about bad memory, I don't want to misconstrud what your trying to say. Would there be a buffer for the DAC for example that is bad? Or do you mean the RAM or the flash memory itself?
It is very disappointing. This phone is perfect otherwise. I'd like another 6P, but I am concerned I then get one with battery issues.

Categories

Resources