[Q] Power Off Shutdown Sound Is Missing - Droid Incredible Q&A, Help & Troubleshooting

Since upgrading to a Froyo based ROM, I noticed that my DINC no longer responds with an audible alert, when shutting down. It does issue a vibration. My memory, tells me it did sound a notification when powering down under the stock v2.1 ROM. I searched all the setup and settings menus, but cannot find anything that controls such an alert, when shutting down. I do have a fully functioning bootanimation and startup mp3 of my own. I am happy with startup animation and sound. I also remember, under the HTC stock ROM v2.1, that whenever the USB cable was either attached or disconnected, that I also received an audible alert, or notification. Now, the phone is silent when I connect or disconnect the USB cable. Is there an app or widget or system file that controls this alert. Note, I did check-off the box for Sounds/Notifications/SD card in the settings menu. It makes no difference.

To update my research, I created a Google search on "Froyo shutdown sound". There were many hits across the Froyo/Droid spectrum. Apparently, the Froyo users believe that the Froyo update has removed the notifications that were generated during USB cable activity and during phone shutdown. Many people seemed to be very glad that these "annoying" notifications were removed. Others, like me, missed hearing when the phone randomly booted while tucked neatly away in a pocket or on a counter top. I am glad that I still had the opportunity to use my own power on mp3 notification. I wish I also had the opportunity to exercise choice for these other two items, as well, oh well. Mostly, I regret having had to spend about three (3) hours doing internet search, upon search, to figure out if I was suffering from some self inflicted anomaly. It might have been nice to know, in fact, that there was an official Froyo change log that I could have consulted. All I have is conjecture and nothing is sourced to official material. Sorry for the rant.

Related

[Q] Quiet keyboard and screen lock clicks

Alright, I've spent all day searching and can't find a clear answer for what I'm looking for.
Just last night my keyboard and lock sounds are very quiet, now I've seen others with this issue, but I haven't seen anyone explain why this happens or how to fix it.
So does anyone know how to fix this, or have I missed it in my searching?
lolwut. Are you talking about the audio output from the keyboarD? Like when you type it makes that noise, and now that noise is quiet? I think its tied into your general phone sound level. Check your settings under menu-settings-language & keyboard-touch input
Yea, all sound levels are at max and the other sounds ( ringer, text, emails, ect...) still play at proper level. But the keyboard clicks when typing and the screen lock/unlock sound is still there, but just barely making any noise
nobody's got anything?
also last night to took my friend's evo and his is doing the same thing, he said he noticed it soon after the 3.70 update
This just happened to me. I fixed it with a hard reset of the phone. I had to reload the few apps I had and sync my google calendar and contacts. Back in business. Have no idea why it happened in the first place, but they are working now.
i have to say, i never really liked the hard reset idea so i never did it. today i let the battery run until it shut off the phone, i then pulled the battery, put it back in and then charged it full before turning the phone back on. and now my clicks have returned

Google talk won't play notification sound sometimes

This issue started when I first started using gingerbread roms, I'm currently using EF02plus but this started happening with EE03 based roms as well. The googletalk app, and I think the sms app as well, occasionally does not play its notification noise. While trying to pinpoint what exactly causes this to happen it never seemed to be very consistent. What happens is that if the gtalk app is left open with a conversation open the phone will not play the notification sound but only vibrate. Even when the screen is turned off. Meaning that if my phone is off and I never backed out of the conversation, the phone will silently vibrate. It does it the most under these circumstances but it seems to do this other times as well. My sister has an EVO with cyanogen and just to make sure I'm not crazy I tested the same thing on hers. It did indeed make the notification sound when the phone was turned off and every time i messaged her. However mine does not and many gtalk messages go unnoticed on my phone because it never played the notification. At first I thought it was Zedge messing up, so I added custom ringtones to the SD card in the appropriate folder. This issue is driving me nuts that I can't resolve it and will probably end up going to back to a Froyo rom in hopes of fixing it. Any input or idea would be greatly appreciated. This technically isn't really a "question" just hoping someone has the answer to why this is happening.
Most of my friends have android phones and we all use googletalk instead of normal texting, so its kind of a big deal that this app works. Again its not only when the conversation is left open but rather most of the time. It does however vibrate every time, just does not play the sound.
While messing with it I've noticed that when it successfully plays the ringtone it is accompanied by 1 long vibrate. But when it does not play the ringtone, the phone does a very short vibrate, stops, and then vibrates for longer. Its almost as if something interrupts it and stop it from playing the ringtone...
Edit: The interrupt delay between vibrates varies a lot. From a fraction of a second, to sometimes several seconds. And it only does this when it fails to play the ringtone. Otherwise its just one long vibrate.

Bugs on stock AT&T firmware (4.1.1)

I searched the AT&T Galaxy S III General forum and saw no other posts similar. Essentially, I was wondering if anyone had experienced other bugs in the stock firmware. I am not rooted and have not modified my phone's software from stock.
There are two bugs I currently have seen. One I can and will provide screenshots of. This is where during the lockscreen the formatting will be incorrect, such that the last number on the time will be small and the charging text appears on the same line. Also note that the lockscreen shortcuts at the bottom are spaced oddly. I always have five icons, yet sometimes only 3 or 4 show spaced unevenly. I can reproduce this by watching Netflix and while a video is playing, I lock the screen. When I first unlock it, this will happen. This will fix itself if I relock the screen and wake the device again.
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Anyone else noticed any bugs?
I'm fine on my phone
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I've had the second bug happen with the keyboard maybe a handful of times since I got the phone but definitely not a regular occurrence.
I wouldnt worry too much about it but if it bothers you that bad just try a factory reset.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
No problems here
Sent from my SAMSUNG-SGH-I747 using xda premium
MercilessLTD said:
The second bug is in the messaging app. Sometimes when my device falls asleep by itself while I have the keyboard up and active on a thread, and I wake it, the keyboard is unusable. I can click on the message block to bring up the keyboard, but all of my keystrokes are not entered into the message block. I have to back out of the keyboard and thread, to the thread list, then go back to the thread. My previous keystrokes are still not showing, but the keyboard will then work.
Click to expand...
Click to collapse
I've only experienced this issue that you describe. I've gotten used to it, so I'm now indifferent towards it.
I've had issues with the battery life however and how the actual "percentage" is being reported, but I think that it's just Jelly Bean that is causing the issue when my device is restored to stock setup as opposed to running ICS. Sometimes, my phone gets really warm overnight (and I can assure you that nothing is running in the background). Looking at the battery graph, I see a sharp drop within the space of about 20 minutes. This causes the back cover of my phone to be discolored. My i747 is only 5 weeks old and I'm the original owner.
phone minimizes
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Me and a few others have experienced a bug where the external sd unmounts itself at random. Mostly when the screen goes to sleep. For one freezing the MTP application with tibu solved his sd problem but by doing that you cant mount your phone to a pc. As far me nothing has helped yet. My external sd just unmounts at random and I have to remove it and put it back several times to get it to work again and sometimes and I have to format it in the pc to get it to work again. This has happened to a a lot of tmobile users. I never noticed this problem on ics so im assuming its a jb problem. Its not a micro sd card being bad because it does it with my other cards to and one is a very expensive Samsung card..
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
get2brad said:
I have an issue where my phone screen turns off when I'm it for a while (typically at work I use a wired headset). When I wake the phone up and swipe on the lock screen, the phone shows the phone "app" for a second then it jumps to the home screen (as if I hit the home button). Typically I'm unlocking the phone so I can either hit a number on the phone (like, press 1 for English) or I'm wanting to hang up. So I have to go back into the phone application to do either task.
ICS didn't do that to me.
Click to expand...
Click to collapse
I think this has happened to me once or twice. But I guess with the scarcity it's happened I thought I was bumping the back button or home button with my face, i.e. a failure of the proximity sensor to correctly detect my face.
I just started noticing the Keyboard Messaging bug myself. Wasn't sure why it was happening.
I just remembered (or refreshed my memory since my phone just started doing it) that whether or not TalkBack is off or on, my phone needs to tell me which number screen I am whenever I slide my finger across the dots at the bottom of the home screen or the app drawer. Is this a different setting I am missing or is this another bug?
I have had the messaging bug occur a couple of times. No biggee to me considering it has only happened twice in a month's time. I have seen other phones with much more persistent and annoying bugs and by comparison, this is nothing.
no problems here... i like it a lot now
Problem on Stock/root
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Luker161 said:
Hey, not sure if this is the right place for this post, but my GS3 is on stock jelly bean and rooted. For some reason I am not receiving incoming calls. I tried calling my phone from gmail and the phone rings, but nothing happens on my phone. Any ideas as to why this is
Click to expand...
Click to collapse
I'm not sure if this is the right place either, since this is generally non-rooted, although the topic doesn't specify that I suppose.
However, I would venture a guess that you may need to wipe your data and cache. Sounds like a default app issue to me.
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
No issues here.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have never had any of these issues
Sent from my SAMSUNG-SGH-I747 using xda premium
miketigerwoods said:
If I use bluetooth headphones on my walk to work, then plug in wired headphones at work, the audio plays out of the speaker.
It's really annoying because it happens every morning (as it's too early for me to remember things like that) and blasts my podcasts to my coworkers. Removing the wired headphones and reinserting fixes the issue.
Click to expand...
Click to collapse
Actually, I've had a similar issue. I use Google Play Music (as a carry-over from my Nexus S). When the first song of the playlist would finish (using the headphone jack to play through my car stereo), the second song would start on the phone speaker.
It doesn't seem to happen anymore, but it did directly after the JellyBean update.
PIN Lock Instantly with power button
I am upset that the "Lock Instantly with Power Key" option missing from 4.1.1. I have been searching for a fix, but I must be the only one annoyed by this, or I'm bad at searching.
...
I have a pin lock but am used to a 15 min delay before I need to enter the pin, and being able to push power to shut the screen off at will. That is no longer an option as it always will lock to the PIN screen if the power button is pushed. It is very annoying to me.
Another bug is the Keyboard defaulting Samsung Keyboard on reboot. Every time I restart, I have to go back into settings to select Swiftkey.

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.

Several sound issues, I believe they are related. Welp!

Some info: Pixel XL, one-year-old, rooted with Magisk, android up-to-date version 9, Build number PPR2.181005.003
Some weeks ago I started to see some weird behaviour related to sound. First, while listening to Spotify and Google Podcasts (from now on called "The Apps"), the phone would simply stop producing any sound through the headphone (or speakers when the headphones are then unplugged). A restart would fix it until the next random time it would happen again.
After a while, I've decided to factory reset the phone and reinstall the Android system from scratch and root it again (I've been doing this kind of stuff for years now, so I'm pretty knowledgeable about these procedures), to no avail. The problem was still there.
I've started to try to pinpoint what the main problem would be, and then I've started debugging other stuff. What I've found is:
- If I restart the phone and immediately try to play Spotify or Google Podcasts, it will not work and only a restart will fix it.
- If I restart the phone and wait a few minutes (around 5 minutes) everything works, until the next random failure.
- After a restart, my widgets on the home screen will take a few minutes to load (Google Calendar and The Weather Network)-- if I try The Apps before that, no sound will come out through the headphones (or speakers if I disconnect the headphones)
- Sometimes the sound will come out through the phone's speakers, even if the headphones are connected. Only a restart will fix this.
- Sometimes a loud cracking sound will come through the headphones and after that, no sound is played whatsoever by the phone -- a restart fixes this.
- Both The Apps would randomly stop playing (as if the pause button is pressed). Pressing the Play button again restores the sound, but with different volume level. If it was lower, it will become louder, and vice versa. I didn't test this without the headphones as I would need to isolate myself from the world LOL.
- No sound is produced during phone calls either. A restart fixes this until the next random failure.
- The volume indicator will randomly lag to display after pressing the volume buttons.
- The volume indicator will appear randomly and change small amounts (up or down) while I'm using the phone.
I am slowly removing less-used apps to try to pinpoint which one could be the offending factor, with no luck so far.
I've unrooted my phone today to try and see if this has any effect on those problems (no effect).
Any ideas what I can try next? Any idea what can cause these problems?
daniel3ub said:
Some info: Pixel XL, one-year-old, rooted with Magisk, android up-to-date version 9, Build number PPR2.181005.003
Some weeks ago I started to see some weird behaviour related to sound. First, while listening to Spotify and Google Podcasts (from now on called "The Apps"), the phone would simply stop producing any sound through the headphone (or speakers when the headphones are then unplugged). A restart would fix it until the next random time it would happen again.
After a while, I've decided to factory reset the phone and reinstall the Android system from scratch and root it again (I've been doing this kind of stuff for years now, so I'm pretty knowledgeable about these procedures), to no avail. The problem was still there.
I've started to try to pinpoint what the main problem would be, and then I've started debugging other stuff. What I've found is:
- If I restart the phone and immediately try to play Spotify or Google Podcasts, it will not work and only a restart will fix it.
- If I restart the phone and wait a few minutes (around 5 minutes) everything works, until the next random failure.
- After a restart, my widgets on the home screen will take a few minutes to load (Google Calendar and The Weather Network)-- if I try The Apps before that, no sound will come out through the headphones (or speakers if I disconnect the headphones)
- Sometimes the sound will come out through the phone's speakers, even if the headphones are connected. Only a restart will fix this.
- Sometimes a loud cracking sound will come through the headphones and after that, no sound is played whatsoever by the phone -- a restart fixes this.
- Both The Apps would randomly stop playing (as if the pause button is pressed). Pressing the Play button again restores the sound, but with different volume level. If it was lower, it will become louder, and vice versa. I didn't test this without the headphones as I would need to isolate myself from the world LOL.
- No sound is produced during phone calls either. A restart fixes this until the next random failure.
- The volume indicator will randomly lag to display after pressing the volume buttons.
- The volume indicator will appear randomly and change small amounts (up or down) while I'm using the phone.
I am slowly removing less-used apps to try to pinpoint which one could be the offending factor, with no luck so far.
I've unrooted my phone today to try and see if this has any effect on those problems (no effect).
Any ideas what I can try next? Any idea what can cause these problems?
Click to expand...
Click to collapse
I'm sure you have already looked into this - but just in case....make sure that the "Apps" are NOT set to Optimize Battery nor to Restrict Background Usage. There was another thread recently about a user having Spotify stop playing randomly for them and the issue was the app was set to Restrict Background Activity. Good luck!
sb1893 said:
I'm sure you have already looked into this - but just in case....make sure that the "Apps" are NOT set to Optimize Battery nor to Restrict Background Usage. There was another thread recently about a user having Spotify stop playing randomly for them and the issue was the app was set to Restrict Background Activity. Good luck!
Click to expand...
Click to collapse
Thanks for the confidence you projected on me LOL, I had NOT looked at it! Indeed, both apps are set to "optimize battery". I'll change this setting and give it a go.
Thanks!
sb1893 said:
I'm sure you have already looked into this - but just in case....make sure that the "Apps" are NOT set to Optimize Battery nor to Restrict Background Usage. There was another thread recently about a user having Spotify stop playing randomly for them and the issue was the app was set to Restrict Background Activity. Good luck!
Click to expand...
Click to collapse
I must say a LOT of the related problems are, if not completely, at least partially solved. I've seen way less problems since I disabled the battery optimization for Spotify and Google Podcasts.
Thank you so much!
I'll keep tracking them and running some more tests just to be sure, but it seems this was the main issue here.
Amazing how one single app and setting can bring a phone to an almost useless state!

Categories

Resources