Develop Bugs

Sound mutes after 1 day, only soft-reset solves this

I have a problem that more people seem to have, according to the search. I couldn’t find the “audio” tab in my Bluetooth-settings, so that didn’t help me.
The problem is as follows. After 1 day the sound on my compact III mutes, including vibration. Sometimes it's after 12 hours, sometimes after 2 days, there's no distinct pattern to be recognized. Also, it doesn't seem to matter if you use the phone or not, since it sometimes is alright at night and the sound is muted the next morning. This is for all sound-events (warnings, incoming call notifications, messages, mp3 etc), however, you can make a call without any problems and hear what the other person is saying. Once you’ve hard-reset the device everything is back to normal.
It does get annoying however, since I regularly miss calls due to this bug.
I had the same problem on my Vario in the past. So I’m guessing it’s somewhere in the software I use, but apart from Total Commander and TomTom6 I haven’t installed any third-party apps.

Yup i've been having a slight problem with the sound. I thought it was like the endless knackered M500's that orange used to send me which had speaker failure after about 10minuites! (Swear they kept sending me the same 2 faulty phones - I had 5 in 5 days once!) But a play in the bluetooth seems to get it working again.
The other annoying thing is that if you leave the power management at the default settings then occasionally the screen blanks without being able to get the backlight on again - so now I have to manually turn of the screen. Stil aint much of a problem - ive had a normal days use, 2 hours of radio play, bluetooth and wi-fi on all day and still have 35% battery - wehay!
Hopefully there'll be a patch soon to sort out he glitches.

I forgot to mention I had the exact same problem on my mda Vario also. I always thought it was a problem with that specific piece, but apparantly not.
Could it be the vibrate.cab that I'm using to produce vibrations when you use the phonepad? Or should I really do some further research in the bluetooth-department?

Same problem here.
Phone becomes completely silent after 9 hours in standby mode.
I need to reset it to get back sound
Does someone know what is going on here ?
Please advise. Thank you.

I seem to experience no problems the past couple of days (fingers crossed). I used the 'speed up your WM5' tweak where you set the Glyphcache to 32768. After I reduced it to 16something the problems seem to have disappeared.

I noticed that this problem happens when for example email is automatically checked during night. If email comes in (and is not read immediately) the phone will start notifying in background.
Notifications are kept and only a program like "check notifications" will delete them manually. But still if you delete them, the phone then needs a reset
to work properly again.
This is not a memory issue, it has to do with the notifications.
I do not know how to solve it.

phone stops ringing after a split second

i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help

Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300

Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.

[Q] A Couple VERY Weird Glitches Occuring (Need help!)

Hey all,
So I'm posting this thread regarding a couple pretty weird glitches and bugs occurring on my G3, 3 specific ones.
The first: (Probably the least serious but still REALLY annoying) At EXACTLY 12:00AM every night no matter what timezone I set the phone to (I'm in AU on the AEST GMT+10 timezone but it does this at the same time on any timezone) the phone will switch it's WiFi off automatically without warning, reason or explanation. It just goes off and then I have to manually turn it back on. Sure I could use an app such as Tasker or AutomateIt to turn it back on but I don't see why this is occurring in the first place?
The second issue (Most recent): Lately after updating to the V20E firmware for my D855 I've noticed that a graphical glitch (Specifically related to the colour Blue) occurs when there are fast moving elements on my phone's screen (Such as when I move a chat head around on my phone from Messenger, or when I'm scrolling Facebook or my App Drawer fast, there's just a blue box around whatever object/s appear to be moving on my phone's screen. I've not dropped the phone at all, and it has only been present since updating from the V20D ROM. Not sure what could be causing it.
The third and by far the MOST ANNOYING of the issues I'm having, is that for no apparent reason, whenever I am listening to Music with the stock Music player, and I lock the screen (The screen goes off) about 5 seconds later weird stuff starts to happen..
The song will pause, play or even stop completely, seemingly on its own. The "phone" will change songs, artists and sometimes complete albums and playlists completely by itself, with me doing nothing but staring at the lock screen (It keeps doing it until I re-enter the Music app, then when I lock the phone the whole cycle just repeats itself.)
I've done some looking around and careful observations on the phone itself, and it seems that before the weird stuff starts happening to my music, the phone opens Voice Mate by itself, and then if I'm not present, it apparently closes it and then that's when the stuff happens. I've tried everything I can on a non-rooted phone to stop this. I've tried re-installing the Music app, Uninstalling all updates to the Voice Mate and it's packages to the factory version, force-stopping Voice Mate, everything and no matter what I do the phone still opens Voice Mate and the weird stuff starts happening (It's like it's taking commands from Voice Mate to do something but I'm not even doing anything ) It's been doing this since I got my phone when it came with Android KitKat 4.4 (I was on the D10M ROM until I moved to the D20D Android L ROM) and I moved ROMs doing a completely fresh start ( I factory wiped the phone and then upgraded via a CSE flash and put all my stuff back on it manually) and I would've thought a completely fresh start would have fixed it but apparently not... Either it's a bug that's been present for a while, or it's something deeper than the ROM.
So yeah some pretty weird issues, if someone knows what could be causing them, please let me know, especially if you know a way to solve them.
Cheers guys.

I'm having a very similar problem with regards to #1 but it's doing it with Bluetooth for me!
At midnight on the dot, it will disconnect my connected Bluetooth devices. It doesn't shut Bluetooth off, it just drops the connection. I posted about it here: http://forum.xda-developers.com/verizon-lg-g3/help/bluetooth-disconnects-midnight-t2973187

Your phone sound possessed! Call 1-800-Exorcism now.
You right, weird/unusual.

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!

Android 11 random absent notification sounds / notification issues

Hello,
since the update to Android 11 on my S20 (SM-G980F/DS) the notification sounds are randomly silent.
This means sometimes (i would say in three cases out of ten) the logo of the app (problem with multiple apps) just appears on the Always On Screen. No Animation, no sound, no vibration. I could not identify any pattern or make it reproducable. Of course I tried several reboots, updated to newest version and double checked silent / do not disturb modes.
I've got the problem since the first day of the update, so around one week...
I'm thankful for any advice!

0mrwhatsupguy0 said:
Hello,
since the update to Android 11 on my S20 (SM-G980F/DS) the notification sounds are randomly silent.
This means sometimes (i would say in three cases out of ten) the logo of the app (problem with multiple apps) just appears on the Always On Screen. No Animation, no sound, no vibration. I could not identify any pattern or make it reproducable. Of course I tried several reboots, updated to newest version and double checked silent / do not disturb modes.
I've got the problem since the first day of the update, so around one week...
I'm thankful for any advice!
Click to expand...
Click to collapse
and your Do not disturb mode is off? check and see if it is scheduled or not