Related
I know there has been similar topics mentioned in the Vibrant Q&A and Captivate General but neither directly effect my request.
Here's the story:-
Prior to putting Froyo JPO on the SGS last week and running a stock JF3, when the phone was connected to any mains for charging as soon as the SGS was fully charged it gave a single loud 'Ping' noise and nothing further.
However, since applying Froyo JPO when I carry out the same procedure and charge the phone, as soon as it is fully charged it instead gives off a continuous loud alarm which is extremely annoying.
The only way to stop the noise is to unplug the phone from the charger which frankly at times is difficult to achieve.
Any ideas how to get it back to either the single 'ping' it used to make or stop it altogether...
If anyone is thinking "just turn off the sound" as the answer ~ I need the sound on in case I receive a phone call, email or text message.
EDITED: Sorted ~ See Page 2.
What about turning down system volume or is this classed as a notification? Fyi - not experienced this myself, but your not the first person to find issues with the battery full sound.
Sent from my GT-I9000 using XDA App
Bynar010 said:
What about turning down system volume or is this classed as a notification? Fyi - not experienced this myself, but your not the first person to find issues with the battery full sound.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
It's not really the answer as I never had to turn it down prior to Froyo JPO.
On the contrary, I would prefer the phone to carry out a single 'Ping' just to let me know the battery is charged... not the incessant non-stop noise it now makes.
this scared the **** out of me the other night as I was falling asleep. :S
remz92 said:
this scared the **** out of me the other night as I was falling asleep. :S
Click to expand...
Click to collapse
I can easily believe you.... My GrandDaughter was fast asleep right next to the charger when it went off.
I've never seen her wake up so quick!
In settings/sound scroll down to Notification ringtone, is that not the sound setting for full battery? choose a different one, then choose the original chosen one and see if its the same annoying tone. I must admit, i charge mine when i am asleep so the sound settings are all off so i haven't heard the full battery alert since updating to Froyo.
padlad said:
In settings/sound scroll down to Notification ringtone, is that not the sound setting for full battery? choose a different one, then choose the original chosen one and see if its the same annoying tone. I must admit, i charge mine when i am asleep so the sound settings are all off so i haven't heard the full battery alert since updating to Froyo.
Click to expand...
Click to collapse
No.. that's not the sound... In fact non of the supplied sounds come from Android System Sounds.
Anyway..... I think I may have found the answer ~ Under 'Feedback' de-select 'Audible Touch Tones' & 'Audible Selection'.
God knows why they are changing it but I deselected them both and noticed when I topped up the battery this time the sound changed to what it used to be... a single 'Ping'.
Further tests required to prove this.
I've been suffering with this too since going to JPO. I never had this problem on JF3 or JM1. It's been waking me every night since last week and driving me mad
I already had audible touch tones and audible feedback disabled; are you saying that you have to enable then disable them to get back to the single 'ping' sound?
EDIT: I've just noticed that you can set settings/sound notification ringtone to "silent". Maybe this will shut it up?
Nobster said:
I've been suffering with this too since going to JPO. I never had this problem on JF3 or JM1. It's been waking me every night since last week and driving me mad
I already had audible touch tones and audible feedback disabled; are you saying that you have to enable then disable them to get back to the single 'ping' sound?
EDIT: I've just noticed that you can set settings/sound notification ringtone to "silent". Maybe this will shut it up?
Click to expand...
Click to collapse
It will shut it up but it will also kill all other notification sounds.
If unticking the Audible touch tones & Audible selection does not work for you, instead of selecting Notification Ringtone to be silent instead select 'Cloud' and try again.
I'll be recharging in the next two hours so should know later tonight.
I'm sure it's the notification ringtone, i changed mine from the cloud (which was already selected and being used) to a different one and when the battery fully charged i got the tone i chose.
padlad said:
I'm sure it's the notification ringtone, i changed mine from the cloud (which was already selected and being used) to a different one and when the battery fully charged i got the tone i chose.
Click to expand...
Click to collapse
If that is the case then it would indicate prior to selecting a notification the phone uses that horrendous continuous alarm I mentioned.
We are saying selecting a notification changes the battery alarm.
I try'll selecting a different alarm and see what happens.
I experienced the same problem on my SGS after updating to FROYO. This is how I managed to solve it:
-Go to settings
-Sounds
-Notifications - Tone for notifications
-change to "bubbles" for example
I noticed that no tone was selected when I entered the tone list...
Now, when my battery is fully charged i get the 'bubbles' tone only one time so it won't force me to get up at night to pull out the charger...
Hope this helps...
Zbably said:
I experienced the same problem on my SGS after updating to FROYO. This is how I managed to solve it:
-Go to settings
-Sounds
-Notifications - Tone for notifications
-change to "bubbles" for example
I noticed that no tone was selected when I entered the tone list...
Now, when my battery is fully charged i get the 'bubbles' tone only one time so it won't force me to get up at night to pull out the charger...
Hope this helps...
Click to expand...
Click to collapse
Yes, you are correct.... It must be when after performing a Factory Reset it changes the Notification sound to No Tone which because there is nothing selected it gives off the incessant none stop alarm.
Sorted.
I hate the notification sound when the battery charge is complete and am trying to completely disable it, but I need/want the general notification sound when a text arrives at the current tone/volume.
Is this possible or are they 100% interlinked?
Any clue anyone?
mine with js3 just does a quick beep beep when it fully charged it doesnt do the notification i select in the options, they only time i hear that one is when i plug my phone into usb on my pc. sounds like i got a lucky break anyway
Hi everyone
I have a rather annoying problem. My Standard GS5 (SM-G900F, Stock Rom 4.4.2) will from time to time, play the notification tone while on a call.
It's totally random and there's nothing to notify at all as nothing shows in the bar at the top as normal. It will happen maybe 3-4 times a week, and it's getting annoying having to going through all my message apps to see if there's a new notification (when there isn't).
Is this a common thing?
it's not something i've ever encountered, no. it sounds like the most annoying thing on the planet, though.
Hello,
I've had my nexus 6P for a while now and have had this issue since day one but never really cared about it until recently. My issue is that every time i get a text , my phone gives me a double tone of what every i have set , i use just a simple tone since anything longer plays twice. Recently i have been in a few group texts and i have been getting so many in a row that its become bothersome, so i figured i would just mute the conversation so i can still be in it just not get a head ache. well that mutes one of the tones but not the second one so it seems i am getting a second notification from some thing other then the messenger app and for the life of me i cant figure it out. Does any one have any idea whats going on and how i can just get a single tone for a text
thanks
razor237 said:
Hello,
I've had my nexus 6P for a while now and have had this issue since day one but never really cared about it until recently. My issue is that every time i get a text , my phone gives me a double tone of what every i have set , i use just a simple tone since anything longer plays twice. Recently i have been in a few group texts and i have been getting so many in a row that its become bothersome, so i figured i would just mute the conversation so i can still be in it just not get a head ache. well that mutes one of the tones but not the second one so it seems i am getting a second notification from some thing other then the messenger app and for the life of me i cant figure it out. Does any one have any idea whats going on and how i can just get a single tone for a text
thanks
Click to expand...
Click to collapse
Have you try turning off notification in Hangout:cyclops:
boxcar8028 said:
Have you try turning off notification in Hangout:cyclops:
Click to expand...
Click to collapse
I did not try thatcause i disabled the app a while ago so didn't think about it
at some point of the day i noticed my notification sound no longer working.
I got all the msgs on my notification but with out sound.
turning off and on didnt fix. only the battery pull worked.
it happened like every once a day. some times I have to do battery pull twice a day.
I had this phone for a wk now.
anyone having notification sound issue?
even the turn off screen and on sound muted.
There's a few bugs, nougat is brand new, they'll fix things. My headphone kept buzzing one time until a restart
Its not just you. And I don't think its exactly something to do with Android 7.0
If you look at how your audio menu is when you change the ringer volume, you'll see that when the phone is set to vibrate, it actually MUTES the other two sliders.. it doesn't set them to vibrate. With that in mind, it seems more likely LG has a bug, than Android 7.0 having a bug.
Having this problem as well with my H910 (AT&T). It's very frustrating indeed. What's even worse is that it seems sporadic in nature, sometimes I will get a notification chime, sometimes I won't. As skyedream said, a battery pull is the only way to get consistent notification sounds, if only temporarily.
I think I get this too. Often I pull my phone out of pocket to find I had a text that I never heard.
Sent from my LG-H918 using XDA-Developers mobile app
I had this problem too yesterday where it was just frozen. Did a restart and all seemed ok after. First time that happened.
This happens to me as well. Also, I will get double notification sounds at times. Like an echo. Or, a different sound mixed with my selected sound. A reboot fixes. Have to do it a couple times a day. Very annoying.
No sound for notifications + no web video playback
I also have same issue with notifications. No pattern on what causes this, but a reboot gets rid of this (just for sometime! and the problem is back). I have also noticed apps not working smoothly and unable to play web videos including from Youtube app and Facebook App. Overall, tad disappointed with the software quality on this set.
Phone notification vibrate shuts off all other notification sounds
HikariNoKitsune said:
Its not just you. And I don't think its exactly something to do with Android 7.0
If you look at how your audio menu is when you change the ringer volume, you'll see that when the phone is set to vibrate, it actually MUTES the other two sliders.. it doesn't set them to vibrate. With that in mind, it seems more likely LG has a bug, than Android 7.0 having a bug.
Click to expand...
Click to collapse
Good call, thanks! I also notice that even though I have Sound Settings-Volume-Touch & Feedback sounds Off, I still get haptic feedback vibration on keyboard while typing this reply to you. It goes away when I go into Sound Settings-Vibration Strength, & turn slider off for Vibrate on tap. The Settings software isn't connecting the overall Volume Profile with the Vibrate Strength settings it seems. I don't know enough to know whether this is Android or LG. Under Vibrate Strength you can control notifications too, though haven't yet tested. Hope this helps til it gets fixed.
---------- Post added at 07:40 PM ---------- Previous post was at 07:26 PM ----------
DeesXDA said:
Good call, thanks! I also notice that even though I have Sound Settings-Volume-Touch & Feedback sounds Off, I still get haptic feedback vibration on keyboard while typing this reply to you. It goes away when I go into Sound Settings-Vibration Strength, & turn slider off for Vibrate on tap. The Settings software isn't connecting the overall Volume Profile with the Vibrate Strength settings it seems. I don't know enough to know whether this is Android or LG. Under Vibrate Strength you can control notifications too, though haven't yet tested. Hope this helps til it gets fixed.
Click to expand...
Click to collapse
I just tested texting...even though on quick settings slider notifications for text are grayed out, while call setting show vibrate only, in the full settings menu, under Vibrate Strength, you can slide the vibration strength up...I did this, sent myself a text, and phone vibrated the notification. I think it's messed up that I can't shut my call notification off completely, including nvibrate quickly with volume key or quick settings. Have to go into full settings menu sound & select silent. Please fix this Android/LG.
skyedream said:
at some point of the day i noticed my notification sound no longer working.
I got all the msgs on my notification but with out sound.
turning off and on didnt fix. only the battery pull worked.
it happened like every once a day. some times I have to do battery pull twice a day.
I had this phone for a wk now.
anyone having notification sound issue?
even the turn off screen and on sound muted.
Click to expand...
Click to collapse
Ya, I have the exact same problem... (I have a H990DS)
I can't seem to even fix it with a reboot.
I have emailed LG about the problem - we'll see what they say...
Digitalaks said:
I also have same issue with notifications. No pattern on what causes this, but a reboot gets rid of this (just for sometime! and the problem is back). I have also noticed apps not working smoothly and unable to play web videos including from Youtube app and Facebook App. Overall, tad disappointed with the software quality on this set.
Click to expand...
Click to collapse
I experience the same as you. I usually clear regents and then hit restart and all my notification sounds come back and videos. I'm just wondering, are you using any type of ad blocker? I use the ad block browser and I've noticed that whenever I open my browser, that's when my notifications get muted.
Issue resolved after update
Hi, looks like this issue is resolved with the update I got in January 2017 end. But not sure what caused it to fail in first place. But as of now, all is well after the update. Cheers!
I still have this problem over here on T-Mobile. Very annoying.
Anyone ever find a fix? Having these issues on a new LG V20 US Unlocked connected to Verizon.
Bumping this to see if anyone has found a solution to this. My V10 started muting notifications when the ringer volume was set to vibrate on one of its later updates. I figured it was a glitch in my phone since I didn't see anyone else complaining about it. This was one of the reasons i decided to upgrade to a V20. I was pretty surprised that it did the exact same thing and it's apparently by design. Who in their right mind would think this was a good idea?
I'm not sure of the cause, but I had many calendar reminder alarms fail to sound over several days when I got this V20. I tried different calendar apps and ended up with one called aCalendar. It works OK most of the time, but there is still a serious issue. If ANY other kind of notification happens to sound right when a calendar alarm needs to sound, the calendar will NEVER sound its reminder notification for the alarm. I've had this happen several times with incoming text or social networking message notifications. I hear those, and then the subsequent alarm that should have sounded concurrently is silent. I've had to set 2 reminders for the same important event, spaced 10 minutes apart, to try to reduce the odds of this issue hijacking an important notification. I've not seen this exact problem ever before on any Android device. My US Unlocked V20 is 100% stock. No idea what to do about it. But from what I can glean online, neither LG nor Verizon plan to push any future updates on the V20, so we're stuck.
For contact selecting unique notification tones that actually stopped working
I got this LG v20 and I loved it...still do....but... how do I keep certain text notification tones thst i select to not change back to default?...on its own? Crazy. I use zedge ap to download ringtones n notification tones. Maybe there is an issue there?
@Dkb123,
If you could please add some punctuation to your post, it might be easier to read so someone can understand your problem and help you .
I am using a rooted HTC One m10 with Viper ROM and am having the same problem. Echos notification noises, turns off alarm and notification sounds, and it is beyond annoying. I have already had to reset it twice to try to fix it and nothing has worked. I have no idea what is causing it but when I try to open my alarm app it says it was disabled and could have been caused by a system time change (which didnt happen) or battery saving (where I have it whitelisted). I will try disabling my ad-blocker. I'm not sure how those things could be connected but since it was suggested I will give it a go. I am consulting all of the developers I know about this but so far nobody has an answer. I am kind of starting to freak out because I need my phone to work. I have 3 kids under the age of 6 in school and need to know when someone has to get in touch with me. Before the last reset, I also saw that when my notification was disabled and I went back in to reenable it, it had been switched back to the sound I had selected the time before that. One more note. When I go in to check my notification noises, all of them, my ringer, notifications, and alarm, are all blank for about one half second before they repopulate and then show the correct tones. If it were as simple as it being my ROM someone would have posted it on the thread because it is a pretty big problem to have gone unnoticed. Is it possible we are all running an app or have a shared setting that is causing this to happen to only us. I had to dig pretty hard to find this thread in the first place. It might help if we posted a list of our apps, what do you guys think?
klear6 said:
I am using a rooted HTC One m10 with Viper ROM and am having the same problem. Echos notification noises, turns off alarm and notification sounds, and it is beyond annoying. I have already had to reset it twice to try to fix it and nothing has worked. I have no idea what is causing it but when I try to open my alarm app it says it was disabled and could have been caused by a system time change (which didnt happen) or battery saving (where I have it whitelisted). I will try disabling my ad-blocker. I'm not sure how those things could be connected but since it was suggested I will give it a go. I am consulting all of the developers I know about this but so far nobody has an answer. I am kind of starting to freak out because I need my phone to work. I have 3 kids under the age of 6 in school and need to know when someone has to get in touch with me. Before the last reset, I also saw that when my notification was disabled and I went back in to reenable it, it had been switched back to the sound I had selected the time before that. One more note. When I go in to check my notification noises, all of them, my ringer, notifications, and alarm, are all blank for about one half second before they repopulate and then show the correct tones. If it were as simple as it being my ROM someone would have posted it on the thread because it is a pretty big problem to have gone unnoticed. Is it possible we are all running an app or have a shared setting that is causing this to happen to only us. I had to dig pretty hard to find this thread in the first place. It might help if we posted a list of our apps, what do you guys think?
Click to expand...
Click to collapse
Hi. You posted this in the wrong area. This is for the LG V20. Try searching the HTC One M10 area for a solution. Someone there might be able to help you.
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.