Develop Bugs

TIP: How to disable the "OK Google" toast

This has been covered in multiple threads but there seems to be a constant confusion on how these steps are actually performed. Here are the steps to disable the "OK Google" toast message on any Android Wear wearable with a stock face.
Notes:
- These steps were performed on a freshly reset/paired watch. I thought I captured the "paired" message but was too slow.
- Apparently I can't say "OK Google" without sounding like I'm also eating a banana. Sorry.
1. Once you've paired your watch and have access to the clock, speak, "OK Google".
2. Clear the "listening" microphone screen with a swipe.
3. Turn your display off.
4. Turn your display on again and repeat until the message goes away (should be 5 times).
http://www.youtube.com/watch?v=V7uPqO-X1iw

This works for me, but only for a day or so. Since I don't use the command all that often (since apparently I only have a speech impediment when I speak to Google), is there ANY way of disabling this permanently? I'll root my watch (LG G Watch R - they have to figure out a better name for that), I'll ROM it, whatever. I just use a very minimal (like Movado minimal) face and the ok Google appearing or me having to day ok Google a bunch of times every day is really, really grating on my nerves.

Zebov said:
This works for me, but only for a day or so. Since I don't use the command all that often (since apparently I only have a speech impediment when I speak to Google), is there ANY way of disabling this permanently? I'll root my watch (LG G Watch R - they have to figure out a better name for that), I'll ROM it, whatever. I just use a very minimal (like Movado minimal) face and the ok Google appearing or me having to day ok Google a bunch of times every day is really, really grating on my nerves.
Click to expand...
Click to collapse
some patterns i've noticed:
- when you change watch faces it comes back
- when an update is pushed, it comes back (watch or android wear)
i haven't noticed that it comes back without one of these occurring.

640k said:
some patterns i've noticed:
- when you change watch faces it comes back
- when an update is pushed, it comes back (watch or android wear)
i haven't noticed that it comes back without one of these occurring.
Click to expand...
Click to collapse
I've had the same face on for weeks, and it was last updated weeks/months ago.

Note 4 Suddenly Having a Multitude of problems. Hardware Issue?

Hello, I have had my Note 4 for quite some time now and have not had any issues with it up until the last month or so.
At first it started out as just a hiccup every now and then, an example would be when I play music via bluetooth to my Jeep CD Player, I would sometimes have to turn bluetooth off then back on to get it to connect or reconnect.
Now things are getting out of hand. Here is a list of problems I have on a daily/hourly basis and seemingly at random times. I cannot reproduce any of these problems (except the NFC problem) on demand.
I have noticed that rebooting the phone will clear up these issues (except NFC) for a short time, SOMETIMES. Other times a reboot does nothing to help the situation.
Keyboard Lag
Sometimes when I press the keys the phone vibrates indicating a key press and magnifies the key that is being pressed, but fails to enter anything in the text box/input field. For the record I am using Swiftkey. I have noticed that this happens most often when I open an app via "popup notification." For example, if I were to receive an IM or SMS I would tap on the notification that pops up, which then switches to/opens the corresponding app. It is then I will more often than not have this issue. To remedy this I have to close and re-open the app, sometimes several times causing the keyboard to open and close, several times... Sometimes when I TAP a key, the phone will behave as though I have held the key down or performed a "long press." This issue is not exclusive to the keyboard, it often happens anywhere on the screen and with any app, usually indicating that I have been "long pressing" for about 1-2sec at a time.
NFC Does Not Work
One day while I was at work I attempted to add the office printer via NFC. To my surprise I was unable to turn on NFC via the "quick settings" drawer. In the quick settings panel the NFC icon would light up, as if it were turning on, and then just turn right back off again, this happens consistently. I went into setting to enable NFC that way and I am stuck with a slider that is actually in the "on" position but greyed out, I am unable to interact with it.
Bluetooth Connectivity
I have a JVC CD player in my Jeep, I often use YouTube or Google Play Music when I drive. Usually I do not have any problems connecting to the CD player at first, but after about 30-60sec of playback the audio goes blank. The app says that it is still playing however no audio can be heard. Then it will suddenly come back on after about 5-10sec, and here is where it gets strange. After the audio comes back on after this "hiccup" the playback is fast, as in it is playing at 2X's it's normal speed, makes the vocals sound like chipmunks. This will continue indefinitely until I turn on the screen, unlock the phone, then shut the screen off. Then the audio goes on playing fine. This happens with both YouTube and Play Music, while using YouTube the video gets sped up as well. I also experience issues with connectivity where sometimes at random the phone will just disconnect from the CD player, and refuse to reconnect until I have rebooted the phone, or if it does reconnect I get no audio until the phone is rebooted. I notice that this ONLY happens when connected via bluetooth. If I turn bluetooth off while this is happening music will play over the phone's speaker perfectly normal. My CD player has a hands free feature, and I do not seem to have any issues with phone calls, it's only with music playback do I have problems.
Originally I thought it was my CD player acting up, however in light of the other problems, and the fact that I tested it with my tablet and two of my friend's phones without issue, I don't think the CD player is the problem.
Sluggish/Glitchy UI
Sometimes when the phone really freaks out, the UI behaves very strangely. Sometimes notification Icons will hover above the running app, other times the whole screen will lock in place for a few seconds. Sometimes if the screen is locked up, I will shut it off, then turn it on, shut it off, turn it on. However as I press the power button to turn the screen on and off, nothing is happening, the screen just stays black while the "back" and "recent apps" buttons light up at the bottom. Then when the screen does finally come back in it will flash on and off quickly in accordance with how many times I pressed the power button. While all this is happening, if I hold the power button to turn the phone off, the power/reboot menu will appear without incident. Sometimes when I am swiping to unlock the phone, it does not register the full swipe. Basically it acts/appears as though I lightly touched the screen and moved my finger a half inch even though I have drug my finger all the way across the screen. To remedy that issue I have to SLOWLY drag my finger across the screen and then it unlocks without incident. I have also noticed that when I go to "swipe away" a notification, especially one that has "information" in it, it will swipe off the information but leave the notification there and display the app name the notification was from. An example would be, if I just installed an app (for example YouTube) from the Play Store, the notification will say "YouTube has been successfully installed." When I swipe either left or right to remove that notification, a "white ghost box" or "overlaying top layer" with the "successfully installed" text in it will slide away. However it leaves behind a green box/notification that says "Google Play Store" and that remains until I shut the screen off and turn it back on.
NFC Will Not Turn On
I simply cannot get NFC to turn on, the slider is in the ON position but is greyed out as I mentioned earlier. I would post a picture but I guess there is a 10post rule before I can do that. I have given up on NFC, mostly because I rarely use it, so it's really not that big of a deal.
Initializing the Camera
I use an app called "Telegram" instead of SMS messaging, thus I use Telegram to share pictures with friends. Sometimes, again I am not able to reproduce this problem on demand, the problem comes and goes seemingly at random. The camera will take more than 30-60sec to initialize, while I am waiting for it I am stuck with a black screen. If the camera doesn't initialize, shutting the screen on then off will take me back to the telegram app. I never get an error message or anything. Other times when I try to use the camera it pops on instantly and works flawlessly. Originally I thought this was a problem specific to telegram, however in the name of science I tested it with the default camera app and get the same results.
USB File Transfers
I'm not really sure this is specific to my phone, but whenever I transfer files from my PC to the phone or from the phone to PC, it is PAINFULLY slow. It's even painfully slow when the PC just displays what is in the folder. However I can't say for sure this is related because I never attempted to transfer files until I started having these issues, at which point I thought it would be a good idea to start backing things up.
Gets Stuck in 3G Mode
This happens rarely, not even sure that it's related but I felt that it was worth mention.
What have I done to try to remedy this problem you ask?
So far I have performed a non-root ADB nandroid backup, just in case factory resetting the phone didn't work.
I have factory reset the phone 2 times, I see no improvements.
I have cleared out my SD card/removed SD card
I removed and/or shut off bloatware apps (Yes I tested the phone without removing/disabling bloatware, still having the same issues)
Wiped cache via Recovery
I am not sure what else I can really do to fix the phone, I am starting to think that this is a hardware issue. I should mention that there was no significant event that I feel would cause these malfunctions. System update installed and worked perfectly up until this last month, I have not dropped the phone from significant height, the phone has an otterbox anyway. I have not gotten the phone wet, it has not been left outside, this phone has not seen any abuse what-so-ever. I just started having these problems out of the blue and they seem to be getting progressively more frequent and longer lasting. If I don't get any ideas from here I am going to try to get Verizon to replace the phone via insurance, however I don't have high hopes for that because I have grandfathered unlimited data and this is not the "original" phone that I had when I added the insurance option, so I am not sure it's covered.
Does anyone have any ideas on what could be causing this or anything I can do to correct it or try to troubleshoot it?
Any help is greatly appreciated!
Phone Information is as follows:
Samsung Galaxy Note4
Model: SM-N910V
Android Ver: 5.0.1
Baseband Ver: N910VVRU2BOG5
Build#: LRX22C.N910VVRU2BOG5
HW Ver: N910V.05
Verizon Wireless
Non-Root, Default Launcher, Not modified in any way.
I realize that this is a long post but whenever I ask for help I like to be detailed. If I left out any information that might be helpful please let me know.

Unfortunately, it looks very much like components on your logic board are going bad. Sometimes a few specific things will go bad that don't actually make the phone unusable, but make it act similar to what you are explaining. It wouldn't be worth the money you'd have to pay someone to track down the bad components and replace them. If you really like the note 4, I would just make a full backup with kies while you can, buy a new phone and restore your backup.

All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk

outcasted2003 said:
All of Kies backups do NOT restore to a new phone! Only contacts, messages and call logs will restore on a new phone. Use Samsung Smart Switch or Helium. Good luck
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
I see. I didn't know that because I've always restored my backups to the same phone. Thanks for the info.

Google Now Can't use microphone sometimes - no other mic issues

On my N910V running VRU2CPF3 CM13.0-20160724, I have noticed a very strange behavior with the Google Now app (recently re-branded as simply, the "Google" app). Immediately after a phone call (and during other circumstances I haven't identified precisely yet), the Google app will lost the ability to "hear" me, even if I press the microphone button and start talking. The "ok Google" function doesn't work during the issue either, nor can I retrain the ok google voice model because it plain doesn't register any mic input. I can make calls and people hear me fine, and I can record audio on my camera, so my microphone is working.
The issue always goes away if I reboot, but eventually comes back, even if I haven't made any calls. On one occasion, I got the mic function for the Google App back after opening my phone app, then lost it after closing my phone app. On another occasion, I got the mic function back for the Google app after uninstalling Google Chrome and Chrome Beta (per this post). I was also able to get functionality back once by plugging in an external headset and then unplugging it, and another time by force killing all open apps. All of these "fixes" failed to fix the issue this time around - strange, right? Again, reboot always gives a temporary fix, and a phone call usually (not always) causes the issue to occur. I have found at least one individual with the same issue (khalil) here
I have tried a fresh install of the system, and the issue seems to go away for hours or even days at a time, but always comes back. I froze every user installed app on my phone using Titanium backup to see if an app was the issue, but the issue persisted. However, the issue does not seem to occur when booted into safe mode (which screams of software problem). I am currently in the process of reflashing a blank system to see if the issue persists without any user apps.
This behavior is not specific to this operating system; I had a similar issue when I was on stock unrooted 5.1.1. I did not notice the issue on Jasmine rom running 6.0.1, but I also didn't run it for very long. I seem to recall having a similar issue with my Galaxy S3 on CM11 (though it was a while ago so I can't confirm the truth of this!), so I suspect that something about my setup is to blame, rather than the hardware.
One more juicy tidbit: force uninstalling the google app fixed the issue for a day, then the app started force closing on launch, and no amount of finagling would stop the force closing. For the record, I've flashed google apps mini from opengapps.
I don't know what tools to use for proper logging of hardware - ie, when an application has control of the mic or not. I suspect that the issue is coming from improper ending of microphone use state in a certain program.

Delayed Notifications In Android P

First off, I disabled adaptive battery in Android P. Ever since the upgrade from 8 to 9, I noticed that notifications are right around 5 minutes late. I have a couple time-sensitive apps that I need notifications right away. Gmail and another app for my home automation. In Android 8, the were flawless. However, ever since going to 9, not so much.
I also noticed that when I delete messages in the gmail app for gmail and an IMAP email server I have it does nothing with the messages on the server. I login to webmail from a computer and the messages are still in the Inbox.
Anyone have any ideas? I am going to try a wipe again to see if it resolves the issues, but I am out of ideas. I had the above issues in Android 9 beta as well. I would downgrade and it fixed them.

I have the same thing and it turns out it is a common issue with Pie. I have not found a solution yet. I have read all kinds of things people have tried and nothing seems to help. Sorry that I can't be more positive. Hopefully Google will figure something out and fix in an update.
Here is a two page post I started about the issue but there are also many others online describing the same thing:
https://forums.androidcentral.com/android-pie/904647-notifications-delayed-stopped.html

My thought is that the delayed notifications are due to Android Pies implementation of adaptive battery. Maybe try excluding the apps you want to receive notifications from in a timely manner?
Sent from my Pixel 2 XL using XDA Labs

You don't happen to have data saver in the quick tiles turned on by accident do you? That does prevent notifications from getting pushed. Both my parents had this on and a bunch of notifications came through after turning it off. I made sure to remove it from even being an available option.
Sent from my Pixel 2 XL using Tapatalk

been fighting with this issue as well, but it only seems to be gmail, and a couple other apps, my sms notifications seem to come through fine, at least as far as I can tell. I've turned off adaptive battery etc, nothing seems to make a difference. sometimes i can turn my screen on and all the notifications will come flooding in, other times they come through 10ish min later.

yes i have also these issue
and i opened thread on these https://forum.xda-developers.com/pixel-2-xl/help/gmail-sync-problems-pie-t3839357
also i tried many apps, but instead of gmail but yet i didn't find any solution

Triscuit said:
My thought is that the delayed notifications are due to Android Pies implementation of adaptive battery. Maybe try excluding the apps you want to receive notifications from in a timely manner?
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for the suggestion but that is one of the first things I tried. No difference.
EeZeEpEe said:
You don't happen to have data saver in the quick tiles turned on by accident do you? That does prevent notifications from getting pushed.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Made sure it was off early on. No change.
The best way to describe my issue is that once the screen times out and has been off for at least about 5 minutes, notification sounds are delayed. It is sort of like the phone goes into a deeper sleep or something and then the problem arises. As soon as I use my fingerprint to wake the phone, all notifications blast through.
The delay can vary. Sometimes it is only 15 minutes or so, but often it is much longer. It is almost like once in a while an app wants to call home or something and to do so wakes up the phone just enough to allow some notifications through.
There also seem to be some issues with individual apps and notifications that may be fixed when a developer updates their app for Pie. For example, most apps notify immediately when the screen is on or within that first 5 minutes or so after the screen goes off. But since installing Pie, Kuna always has a delay of 5 to 10 minutes before notifying. Kuna does this 100% of the time. In fact if I have the phone awake, looking at the screen when walking out the front door, when the motion sensor is triggered, immediately there is a notification icon. But the sound notification is always delayed. This seems like an issue with Kuna and they are well know for being very slow with updates and fixes but eventually they do fix things. But the notification sound delays described in this thread do indeed seem like a system issue with Pie. Hopefully enough people will have the issue that Google will figure it out and fix.

I am having same issues after updating to Android P. At first, notifications came late about 5 min, but then they started to vary some coming in 15-30 minutes later. Can't figure out what is causing the time difference but either way I can't find a fix. I spoke with Google support and they had no fix as well.

sammys8 said:
I spoke with Google support and they had no fix as well.
Click to expand...
Click to collapse
Did Google give you any indication they were aware of the issue and trying to fix?

Will_T said:
Did Google give you any indication they were aware of the issue and trying to fix?
Click to expand...
Click to collapse
Nope, they didn't mention anything about existing issues or being aware of the issue.

Any one found any solutions or fixes? I feel like my notifications are becoming even more delayed now and have also realized I'm not getting a lot of various notifications at all (through many different apps).

I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.

3yoders said:
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
Click to expand...
Click to collapse
Just updated some settings, now we wait and see if these buried settings fix my delays.. here's to hoping! :good:

3yoders said:
I am guessing you all are aware of this, and have tried, however I just found this recently and thought I would share for anyone that doesn't know.... Settings > Apps and Notifications > Advanced > Special App Access ..... Lots of options here with one of them being battery optimization for individual apps. After I upgraded to P, hardly any of my frequently used apps were given full battery use. Haven't played with all the other options there, however just granting apps full battery seemed to help me out.
Click to expand...
Click to collapse
One of the first things I tried was giving full useage, (no battery optimization) for all apps that I want notifications from. Did not help. Many other apps are still being optimized. I thought I had previously found a way to turn off all battery optimization but because I do have many apps in that list that are being optimized, I obviously did not. Right now I can't find a global setting to turn off battery optimization even though I thought I did before?

So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand. Even after going through all the battery save features and making sure this app is exempt from them, it still happens if the screen is off, or my phone is off the charger. super annoying. wish there was a fix for this already!

pvtjoker42 said:
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand. Even after going through all the battery save features and making sure this app is exempt from them, it still happens if the screen is off, or my phone is off the charger. super annoying. wish there was a fix for this already!
Click to expand...
Click to collapse
Verizon sent me a replacement because of this problem. I was apprehensive, but got a very nice re-furb. Still have the same problem, but I got a phone that is indicated as Verizon on the LG site. In developer mode, the bootloader unlock button works. I guess everything isn't bad. I sure hope Google straightens this out soon.

pvtjoker42 said:
So I noticed this morning, that the main app/notification that's super delayed (5-10min after the event should have triggered) it doesn't happen when my phone is plugged in or i have the screen on in my hand.
Click to expand...
Click to collapse
This happens only with Gmail on my phone - WhatsApp and Messages send instant notifications. Messages isn't optimized, the other apps are.
I can live with that, no big deal. Perhaps disabling battery optimization for Gmail would fix this, though.

Interesting note: I was talking to YouMail support today about something else but I asked about an issue where I get an email and transcript of a new voicemail but when I go to the YouMail app that voicemail is not shown until I drag down from the top of the screen to refresh the list. Support told me they are aware of this but can not do anything because it is a problem with the "latest Android version causing delay". So it is becoming a more widely known issue and hopefully Google will fix soon.

Thanks for all the feedback. Speaking of delay, I think I have tried just about every fix here and then some and still no luck. Wiping the phone did nothing as well. At this point, I would almost like to revert back to v8 to get this fixed.

I tried this supposed fix, (reply #51). https://forums.androidcentral.com/a...ifications-delayed-stopped-3.html#post6355714
No idea if it worked for me as when you restart the phone you need to do it again and less than 30 minutes after I went through the steps, my Pixel2 got the October update for Pie and required a restart!

OK Google with screen off

I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.

This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?

Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.

tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.