Database Users

Ringtone/notification volume issue

I seem to be having an issue with the notifications and ringtones on my new Moto X Pure. Ringtones are 'ascending' and start out very quiet. and some notifications seem to be the same way but the tones are so short that all that ends up happening is that you don't hear them at all. It also doesn't seem to affect every app - I don't hear anything when I get a Facebook message, but emails and texts seem fine. Is there a setting somewhere that I'm missing?

Most apps have their own sound settings. Check the apps that are giving you trouble and see if there is a setting for sending ringtones.
Sent from my XT1060 using Tapatalk

I checked everywhere to see if you can turn this off and failed. It's something that's very annoying to me

This is a serious issue ....I am considering returning the phone because I cannot even hear my notifications ...spoke to motorola and of course they said they are not aware of any issue
.....if they would acknowledge the problem and address it in a software update I wouldn't care but since they don't even acknowledge the issue ....

https://play.google.com/store/apps/details?id=com.shumoapp.disableincreasingring
That app seems to work for everything but Facebook which is fine for me. Give it a try. Hopefully once some custom roms start dropping this issue is fixed

Someone else and I are having similar issues with low volume: http://www.reddit.com/r/motox/comments/3maaw1/_/
Edit: Others experiencing the same issue on Moto's forum: https://forums.motorola.com/posts/36193b0f11
Sent from my Moto X Pure Edition with Tapatalk

mitchellaneous said:
I seem to be having an issue with the notifications and ringtones on my new Moto X Pure. Ringtones are 'ascending' and start out very quiet. and some notifications seem to be the same way but the tones are so short that all that ends up happening is that you don't hear them at all. It also doesn't seem to affect every app - I don't hear anything when I get a Facebook message, but emails and texts seem fine. Is there a setting somewhere that I'm missing?
Click to expand...
Click to collapse
I have had ring tone volume going down to zero and not being able to adjust it 3 times now. I think I just figured out that this happens when moto assist puts it into "driving" mode and I'm wearing my bluetooth headset. Only way to fix it is to reboot the phone. So annoying!
Sent from my XT1575 using Tapatalk

I don't mind the ringtone volume as much as the low notification volume. It sucks. I constantly miss messages and email. The buzz sound you get from vibrate is louder than the darn notification.

mrbracht said:
https://play.google.com/store/apps/details?id=com.shumoapp.disableincreasingring
That app seems to work for everything but Facebook which is fine for me. Give it a try. Hopefully once some custom roms start dropping this issue is fixed
Click to expand...
Click to collapse
This seems to be a good workaround. To get it to work check "New normalization method." I was also getting an annoying notification in the status bar that the app was waiting for a call. I was able to get rid of this by going into settings-apps-disable increasing ring and then deselecting "show notification." App still works.
Now onto trying to reduce the vibration intensity or pattern of this phone. If anyone knows how to do that, please advise. Also wish this phone had separate volume control for the ringtones and notifications.
Sent from my iPad using Tapatalk

I don't know how well this will be in the long run. But I disabled moto voice and restarted. The ascending issue is gone all around. . I will keep you posted and see if this isn't just a fluke
Sent from my XT1575 using XDA Free mobile app

Im not sure if this is related but Ive noticed the ringtones are coming out on both top and bottom speakers but notification tones are onlu coming out from the bottom speaker are you having the same issue?
Sent from my XT1575 using Tapatalk

The workaround I'm using is to add ~2 seconds silence to the initial portion of the MP3 file for my notification MP3s. This means that during this initial 2 seconds of an MP3, while the XT1575 volume ramps up, there is nothing playing, then the actual sound plays at full volume. Works like a charm.
I use my own MP3s for notifications and ringtones. Used an old version of Goldwave to do this (and other useful things) to the MP3s, then loaded them on to phone.

If you're rooted this is the fix I through together thanks to the help of the moto x play thread. Check it out and make sure to thank the guy who created the original file
http://forum.xda-developers.com/showthread.php?t=3218683
Sent from my XT1575 using Tapatalk

This issue is annoying to me also, moto needs to fix this quiet notification ****.
Sent from my XT1575 using Tapatalk

I had the same issue with every nexus 6 I had (3 of them, all returned). Motorola has something very wrong going on with the speaker hardware/config file.

For anyone who happened to install a custom ROM or the OTA Marshmallow update, do you still have this ascending ringtone issue? I cannot hear my notification sounds, but after installing the "Disable Increasing Ringtone" app, it seems to have helped for most notifications except for FB Chat Heads.

If your rooted, AICP http://forum.xda-developers.com/showthread.php?p=63842724 has the setting built in.
Sent from my Moto XPE

Found a fix for this if you are rooted. Worked great for me to fix this bug http://forum.xda-developers.com/moto-x-style/general/mod-disable-ascending-ringtone-t3218683

Still not fixed? Motorola you useless twats.

Not even fixed after the 6.0.1 update (Moto X Style, reteu version). Why is it so hard to give us a toggle for this... As much as I like this phone, there are a few quirks that will make me never buy anything non-Nexus ever again, starting this fall.

Phone earpiece not working after using speaker phone

My phone app messes up when I use the speaker phone. Speaker phone works, but when I turn it back off to use the earpiece, I don't get get any audio through the earpiece anymore no matter how much I toggle the speaker phone, but the speaker phone will continue to work so I'm pretty much forced to use it if I enabled it. Been doing it since I first installed the Pure Nexus ROM on marshmallow and every update since then after multiple clean installs.
I've posted the issue a few times in the Pure Nexus ROM thread with hardly any acknowledgement, so I have to think this isn't an issue with the ROM specifically.
The earpiece is very sporadic though, sometimes it will work street using the speaker phone (or a BT connection to my car or headset) and sometimes it won't. Seems to be about a 50/50 chance, so that makes it pretty weird.
I've tried using the AOSP and Google dialer/phone app with the same issue on both and made sure they were set as the phone app in the app info settings. I also uninstalled/disabled the other phone app woke using the other to ensure no conflicts occurred. Not sure what else to try.
Of course I'm rooted, running Franco Kernel and not using Xposed framework.
Any help is appreciated.

Guess no one here has any idea either?

Bump

Phone thinks it's in a phone call volume slider changes in call volume

So recently my phone has been acting strange and sometimes would not play notification sounds even though I have the volume on. Attempting to use the volume buttons defaults to changing the in call sound instead of notification/media volume.
Anyone know of this issue? I'm rooted on stock OOS with Lightning kernel v14, using Magisk with the busybox, Audo mod library, Google dialer/contacts and Viper4Android FX mod.
Thanks
Frostbiter

Did you install any of those mods recently?

Rhoban said:
Did you install any of those mods recently?
Click to expand...
Click to collapse
The most recent was the V4A and audio library mod, but I believe this was happening before I started using it.

Frostbiter said:
The most recent was the V4A and audio library mod, but I believe this was happening before I started using it.
Click to expand...
Click to collapse
You could try uninstalling those and see.

So an update to this, it appears to be a problem when I use the event slider, I use it to mute my phone during work but when I unmute it the phone thinks it is in a phone call until I reboot. If I do it for a short period of time though it doesn't seem to have an issue.

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.

Issue: No Voice Turn By Turn Navigation and 1 other small thing

Hello,
My new pixel 4xl is working great except for 2 reasons. The main one being I don't get turn by turn voice navigation. I get no voice at all when navigating. COnsidering I drive for Uber on the side this is very bad.
I checked all settings and they are all correct as far as I can tell - play over bluetooth and everything is on. Doesn't matter if I am on BT or not, nothing. I've tried rebooting of course.
Second smaller issue is no audio sound goes off when What's App messages come through. I've checked all those settings in Apps & NOtifications and they all look good. What gives?

pixelsquish said:
Hello,
My new pixel 4xl is working great except for 2 reasons. The main one being I don't get turn by turn voice navigation. I get no voice at all when navigating. COnsidering I drive for Uber on the side this is very bad.
I checked all settings and they are all correct as far as I can tell - play over bluetooth and everything is on. Doesn't matter if I am on BT or not, nothing. I've tried rebooting of course.
Second smaller issue is no audio sound goes off when What's App messages come through. I've checked all those settings in Apps & NOtifications and they all look good. What gives?
Click to expand...
Click to collapse
Try opening the Android Auto app. on your phone & check 'Driving Mode' is not selected to 'Do Not Disturb'. I had a similar problem where my Music app was not showing up & turn by turn voice navigation was muted.
After changing this setting AA now appears to work as it should. Sounds like you might have the same problem. Anyway, worth a try. Good luck [emoji106]
See attached screenshot...View attachment 4860981
Sent from my Pixel 4 using Tapatalk

Do you have captions enabled when there is voice? This may do closed captioning while silencing the volume until you adjust the volume.

Someone in the 4xl mentioned a similar issue. I think they worked out that they were on the maps beta. Coming out of that resolved the issue.