Database Users

[Q] How do I stop this sound?

My phone is not rooted. This just started this week. I have not adjusted any settings for quite a while so I am pretty sure I did not do anything to cause it.
Since getting my Note 3 in October I use the voice method of inputting text for email and sms quite often. When starting a message where I want to voice inpput, I click the microphone button and speak what I want to send. Works well for me. Thursday the phone started making a loud, very annoying, beep type sound whenever I launch this by clicking the microphone. It happens even when the phone is in silent mode. I checked the sound options in the phone settings and everything is set as it has always been. All system and keyboard sounds are turned off. I also tried another keyboard app rather than the phone default and it is the same with that.
Does anyone have an idea why this started and how to silence it? Thanks!

I guess this is not an issue for others here. I did find the exact problem on another forum and it started for him just a few days ago also. So maybe something updated automatically that caused this. We will see if more people start complaining about it. By the way we have tried a few different suggestions, including resets, but nothing turns off the noise yet.
0n edit: I looked at my apps to see what recently updated. One of the recent updates was to Google Search. I uninstalled all the updates to Google Search and the problem is gone. So it is a bug in the most recent update to Google Search that turns on that sound with no way to turn it off.

OK Google very flakey

For some reason when I'm trying to use ok Google on any screen it is very spotty if it works or not. Occasionally it will work, but most of the time it just doesn't do anything. I have any screen turned on and I also have it turned on so that should detected when the screen is off. Very rarely do either of these work, & I have to go back to the home screen and hit the microphone for it to work. Anyone know how to fix this? I have tried retraining a couple of times also.

Google App --> Settings --> Voice --> "OK Google" detection --> Retrain voice model

The service that does that apparently gets killed after a while, requiring a reboot. It's happened to me a bunch of times, for more than a year now, since the N6. It happens with other random stuff too. The N6 has a "safety" (according to a Moto rep at their forums) feature that rings the first 2 seconds or so of a phone call or alarm/timer at very low volume before it rings at full volume. Also for when you switch to speakerphone. Whatever service causes this behavior does get killed as well after a while, and the N6's alarms and rings sound off at full volume immediately, until after a reboot.

Honestly...Google Now has gotten so unreliable for me I've stopped using it. It used to be flawless...but I feel like the more they add to it the worse it gets. I don't know. Maybe it's just me.

isimme said:
Google App --> Settings --> Voice --> "OK Google" detection --> Retrain voice model
Click to expand...
Click to collapse
I mentioned that I already tried that
tropazr said:
Honestly...Google Now has gotten so unreliable for me I've stopped using it. It used to be flawless...but I feel like the more they add to it the worse it gets. I don't know. Maybe it's just me.
Click to expand...
Click to collapse
Yes, the Nexus 5 was much more reliable.

nav no longer mutes audio

for some reason recently my google maps and waze no longer mutes the audio of any music playing when it gives turn by turn directions. it used to work just fine, whenever it would start the give directions it would mute my music. any one else have this problem ...or have a fix?

Waze should still have a configuration setting to mute it; Maps this seems to be an app change as I noticed this as well. There is a setting once you are in a route where you can set it to mute during calls, I have not found any other option for muting.

weird. this is a recent thing for me. i never had to make any change in any app or do anything before. this really just started happening about a week ago for me.

Incoming Calls / Black Screen ?

Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?

This happened to me today too.

Hello, me too! Oreo Beta 2

Anyone ?

going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.

Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.

It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store

In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1

Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.

going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.

I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.

DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.

Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.

Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.

Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk

rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.

I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk

I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.

bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?

Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.

[WORKAROUND FOUND] After May updates, notification sound vol controlled by media vol

I've had my Mi A1 for over a year now and have almost always had it on vibrate, so all calls/notifications cause the phone to vibrate, but any media that gets played will be at the volume set for media.
Over the past couple of weeks though, notifications (not sure about calls, don't get many of them) will play the notification sound at the volume set for media. I can only get them to shut off if I mute the media volume. I've tried changing the volume for both media and ringing, and restarting the device, but to no avail. I either have to leave it muted and miss notifications, or leave it unmuted and get a jumpscare each time (it also plays notifications when I'm on a call, and you can imagine the jumpscare I get with my phone at my ear and a sudden loud notification).
I recently started using Bose QC35 ii headphones through Bluetooth with my phone, but I don't think that has anything to do with it because it was working fine with them before.
I've searched Google for this kind of issue but couldn't find anything other than standard instructions on adjusting the volume. Does anyone have any ideas on how to resolve this (without doing a full reset of the phone, hopefully)?
EDIT: this is a stock ROM, I've never flashed anything new on it

freddo63 said:
I've had my Mi A1 for over a year now and have almost always had it on vibrate, so all calls/notifications cause the phone to vibrate, but any media that gets played will be at the volume set for media.
Click to expand...
Click to collapse
So I solved this by going into Settings > Accessibility > Vibration and turning Ring & notification vibration off, restarting, and then on again. I was able to use the Pushy app to send test notifications so that I didn't have to wait for a friend to send me a message or something of the sort. My vibration mode now works as intended (not sure about calls, I don't know how I can test those without having a friend call me), and loud notifications according to the volume set for the ringer.

So as it turns out, today I once again got sound notifications, despite having set my phone to vibrate only. What could be resetting the sound profile like this (note that the ringer volume is still at zero) that the notifications play sound at the media volume? Anyone have any idea on this?

freddo63 said:
So as it turns out, today I once again got sound notifications, despite having set my phone to vibrate only. What could be resetting the sound profile like this (note that the ringer volume is still at zero) that the notifications play sound at the media volume? Anyone have any idea on this?
Click to expand...
Click to collapse
Why not just set them individually, it won't take long, when I first got my A1 I did just this.
Each time I got a notification I just pulled down and pressed the notification and customised it, most I turned off, the rest I either set to vibrate, a custom sound or left as it was.
Calls are easy to take care of, set ring volume to zero and it only vibrates.
For me:
I want a sound when I get a SMS.
I want a custom sound when I get a call.
I want no notification of gmail, (it would be going off constantly)
I only want Vibrate from WhatsApp messages.
Can't think of others but I think everything else is silenced.
If that is no good try "Volume butler" which will add a seperate volume control for notifications, not used it myself but it should do the trick: https://www.guidingtech.com/separate-ringtone-notification-volume-android/

kudos1uk said:
Why not just set them individually, it won't take long, when I first got my A1 I did just this.
Each time I got a notification I just pulled down and pressed the notification and customised it, most I turned off, the rest I either set to vibrate, a custom sound or left as it was.
Calls are easy to take care of, set ring volume to zero and it only vibrates.
If that is no good try "Volume butler" which will add a seperate volume control for notifications, not used it myself but it should do the trick: https://www.guidingtech.com/separate-ringtone-notification-volume-android/
Click to expand...
Click to collapse
The only downside of doing them individually is that I can't turn them all back on with one setting, as on some infrequent occasions I do want to hear them because I be expecting a message and not necessarily feel the phone in my pocket. and it seems I have to wait for the actual notification to come up? (can't seem to find the setting under the standard notifications settings menu).
I'll have a look at Volume butler, but it sure is disappointing that this would break when it was a nice feature to use.

This seems to be a general Android bug with some bluetooth devices: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/

BtB said:
This seems to be a general Android bug with some bluetooth devices: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/
Click to expand...
Click to collapse
Wow, thank you so much! I now at least know it isn't a unique issue for me, and have an idea of what causes it.

freddo63 said:
Wow, thank you so much! I now at least know it isn't a unique issue for me, and have an idea of what causes it.
Click to expand...
Click to collapse
You're welcome, and seems that possibly if you unpair your BT device and reboot, you could get your notifications back to normal, but then you don't have your headset available...
Since the issue started outside of a system update, there is a chance it was introduced by a Google App or Play Services update, in which case hopefully Google will fix it soon since it's affecting a lot the Pixel phones.

BtB said:
You're welcome, and seems that possibly if you unpair your BT device and reboot, you could get your notifications back to normal, but then you don't have your headset available...
Since the issue started outside of a system update, there is a chance it was introduced by a Google App or Play Services update, in which case hopefully Google will fix it soon since it's affecting a lot the Pixel phones.
Click to expand...
Click to collapse
Ah, I forgot to mention that I have a workaround for this that I came across in one of the dicussions somewhere. Inside Settings > Google > Search, Assistant & Voice > Notifications I can turn off notifications for Google completely. I've also turned off Google Assistant under Settings > Google > Search, Assistant & Voice > Google Assistant. I don't remember which of those actually resulted in the behavior not returning, but I'm pretty sure I don't need either, so I'm OK with it for now. (actually, do Google Security notifications come under the Google app or some other one?)
PS: reboot is actually not necessary, it seems force stopping Google Assistant or Google resets the notification settings (but yes, I want my headset hahaha).

Seems it's been fixed by Google: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/

BtB said:
Seems it's been fixed by Google: https://www.androidpolice.com/2019/...s-with-duplicate-alerts-and-ignored-settings/
Click to expand...
Click to collapse
Thanks! I will "just sit tightly" (as it says on the update) :laugh: as I wait for the update.