Hello!
My DEFY suddendly stopped ringing when calls are incoming; the preview is always working, the ringer volume is loud and everything is ok.
All other media are working fine, even with the sounds.
Tried to reboot several times but nothing works.
Any hint on how to solve it?
Browsing in the forums and posting a direct question to Google did not solved the issue but found that many people using Android OS had similar problems, all caused by sound applications newly installed.
I tried unistalling the two apps I had (PowerAMP and RingDroid), first via the AppBrain web interface (issue still there); then I performed a deep clear with Uninstaller Pro unistalling even some silly apps I had on there.
Rebooted the phone and silenced via the upper button.
Then came up, in the AppBrain weblist, an application I didn't use for a long time that wasn't showing in the applist on the phone: it's "Sound OFF" (now not present in the Market...), deinstalled that one and "Shake to Mute Call".
Reinstalled my lovely PowerAMP and RingDroid.
Rebooted once more the phone and all is fine.
I still don't know what was the problem as I don't think it was kind of associations like reported in other phones forums.
Anyway I solved =)
Related
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.
i'm experiencing a complete outage of my (no root) n5x's volume, including alarm clock volume when using text-to-speech (3.9.16). this happens several times a day, usually after about an hour, but could be random, to solve it, i have to force-close tts as well as the MacroDroid app using it.
so, if you select a ringtone in settings you usually hear the tone when you tap on it - when i do so, there's no sound at all, nor if i use the volume slider.
- i use Outloud to speak notifications via tts
- and MacroDroid (or Automate-it) to speak well, things like, when i disable wifi ("wifi deactivated"..), or tells the time when the sun sets, tells time/every 15 mins., etc.
so you might guess it's the apps' fault, but it's not, i also tried automate-it app, and disabled Outloud.
- i tried everything to fix this, like: disabled battery optimization, background processes, notification priority/level, even a factory reset! nothing helped.
- i reported this issues to Google about 15 days ago.
- volume is on in settings, of course..
- (and dnd is off, as well..)
- one strange thing: i can play music using g play music
- it worked on M!
have you experienced the same?
do you have any idea to help? this is so frustrating because i used this all the time on my previous N4, and also on another LG phone, and it always worked.
P.S. I remember to have already had this issue when I used a custom rom on the N4, but don't remember what fixed it, probably used a different rom.
tia.
Google text-to-speech 3.10.10 does not fix it.
It seems to be a Nougat problem, doze or memory.
Issue is fixed on 7.1.1-dp1! :victory:
On my N910V running VRU2CPF3 CM13.0-20160724, I have noticed a very strange behavior with the Google Now app (recently re-branded as simply, the "Google" app). Immediately after a phone call (and during other circumstances I haven't identified precisely yet), the Google app will lost the ability to "hear" me, even if I press the microphone button and start talking. The "ok Google" function doesn't work during the issue either, nor can I retrain the ok google voice model because it plain doesn't register any mic input. I can make calls and people hear me fine, and I can record audio on my camera, so my microphone is working.
The issue always goes away if I reboot, but eventually comes back, even if I haven't made any calls. On one occasion, I got the mic function for the Google App back after opening my phone app, then lost it after closing my phone app. On another occasion, I got the mic function back for the Google app after uninstalling Google Chrome and Chrome Beta (per this post). I was also able to get functionality back once by plugging in an external headset and then unplugging it, and another time by force killing all open apps. All of these "fixes" failed to fix the issue this time around - strange, right? Again, reboot always gives a temporary fix, and a phone call usually (not always) causes the issue to occur. I have found at least one individual with the same issue (khalil) here
I have tried a fresh install of the system, and the issue seems to go away for hours or even days at a time, but always comes back. I froze every user installed app on my phone using Titanium backup to see if an app was the issue, but the issue persisted. However, the issue does not seem to occur when booted into safe mode (which screams of software problem). I am currently in the process of reflashing a blank system to see if the issue persists without any user apps.
This behavior is not specific to this operating system; I had a similar issue when I was on stock unrooted 5.1.1. I did not notice the issue on Jasmine rom running 6.0.1, but I also didn't run it for very long. I seem to recall having a similar issue with my Galaxy S3 on CM11 (though it was a while ago so I can't confirm the truth of this!), so I suspect that something about my setup is to blame, rather than the hardware.
One more juicy tidbit: force uninstalling the google app fixed the issue for a day, then the app started force closing on launch, and no amount of finagling would stop the force closing. For the record, I've flashed google apps mini from opengapps.
I don't know what tools to use for proper logging of hardware - ie, when an application has control of the mic or not. I suspect that the issue is coming from improper ending of microphone use state in a certain program.
Hi all,
Hoping someone brighter than me can figure this sound issue out.
THE PROBLEM:
Half of my sounds don't work, rendering my phone useless in the current state. As the title says, Ring, Notification, & Alarm sounds do not work. You know, as in the important stuff that makes your phone, a phone? And makes you wake up in the morning? None of these respective sliders under Sound & Vibration settings make any noise when making adjustments. By contrast, my Media and Call volume sliders DO make noise when adjusting. And sure enough, once on a phone call, I hear things just fine (Call). And YouTube, Spotify, et al. (Media) also work just fine.
Because some sounds work but others don't, this has to be a software issue, right? This would be easy if it was hardware and 0% of sounds worked, but nope, it's partial.
BACKGROUND:
This pixel 3 xl is relatively new to me, but has ran A10 and A11 with a few different ROMs with 100% of sound working flawlessly. But out of nowhere, sounds suddenly stopped working correctly as described above. And it didn't occur immediately or shortly after a new rom flash or update or anything like that. Just stopped working, months into a well-running ROM.
I've tried a couple different ROMs now to fix the issue from a completely clean install (/format data + flash latest google factory image as 1st step) but none have fixed the issue. Specifically, pixeldust (A11) and evolutionX (A11) were my latest troubleshooting attempts with no avail. Pixeldust was the ROM that was formerly working and then after months of 100% sounds working, suddenly stopped.
It's odd that searching throughout the ROM threads that no one else seems to be having this issue. Again, this would be easy if it was a hardware failure. But that doesn't explain how it works for Youtube/Spotify but not for other things, so it has to be software.... I think?
I figured I'd start a thread here rather than start posting in each and every ROM I've tried to troubleshoot this. Thank you!
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
xdateddybear said:
This might not be relevant because I'm using stock Android on a Pixel 4a but my notifications have gone silent and this report was the only similar search result I found. I tried changing the notification tone and none of them played a short snippet so I'm wondering if the problem is there.
Click to expand...
Click to collapse
ManImCool said:
I have not found a solution for this issue.
One thing I noticed recently is that when I'm on a call using the regular "earpiece" or whatever it's called (which works fine), if I switch to speaker phone, I can't hear anything. I have to switch back to the non-speaker ear mode and I can hear the call again.
Click to expand...
Click to collapse
I think I may have finally found the solution!! Sometimes it's the simple things in life that work, rather than reflashing a billion different ways that finally gets things working again.
In this case, I simply cleared the cache and storage for the 'Sounds' apps under Settings -> Apps & notifications -> See all apps -> Click 3 dots in upper right corner -> Show system. Then, I deleted cache and storage for TWO apps, both called 'Sounds' with 2 different icons. I'm not sure which is the system app and which is not nor do I know if clearing only one of them was necessary, but this is what has worked for me and has survived several restarts thus far. Good luck!
My Pixel 6 Pro has a similar problem ever since the Mar 5 update has been installed. Since then, every phone call I made comes with the non-stop notification tone literally every second. For now, I managed to get around it by enabling the "DND Mode", but it isn't a long-term solution.
Is there a way I can re-apply the same update? or flashing a new one would help?
To be clear, you're saying that you keep getting the notification tone even after answering the call? If so, is it the same as your ringtone?
Is your bootloader unlockable? If so, Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own).
It wouldn't surprise me if that doesn't fix the issue, however. Have you tried rebooting? Maybe clear the cache and app data for the Phone app (but then you'd have to re-customize the settings for the phone app to your preferences).
I'm not on the March update, but I also don't receive many phone calls anyway.
that notification tone, during normal time, represents incoming message. It is very short, unlike a ringtone..
Tried rebooting and clearing cache and app data of the Phone app. In fact, that notification could likely come from anything like WhatsApp, Messenger, Twitter...
I noticed that the repeating tones would not happen if the phone is on silent mode. So for now this is my workaround.
Very interesting, and strange. There have been settings in some OEM's phone apps you could enable to get notification tones at regular paces - usually once a minute - while on a phone call, but the issue on yours is only similar since it's constant / every second.
I stick with my recommendation of clearing the app cache and data for the Phone app. I also assume you're using the stock Phone app that Google provides.
In my previous phone (OnePlus 6T), the very same tone happens once in a while, but only at the moment an incoming message arrives. Pretty sure I am not getting a new message every second this time around, and I think it was triggered by apps other than the Phone app. I just noticed that the same symptom showed up when I tried to play video clips from certain apps as well.
And yes, I am using the stock Phone app.
Sounds like a factory reset and only selectively installing and configuring apps, or trying to figure out which app is causing the issue.
If you factory reset, I would first not even restore any apps at all, so you can verify if you have the same problem without any third-party apps installed at first. I would suspect you won't have issues then. And then when you install apps, do it in groups of your most important ones first, maybe at the most 10 at a time, then re-verify each time if you have the same issue or not, then the next batch of app installs. It could be a particular setting in a app as well, so it's possibly merely installing an app might not be enough, so each group of apps you install, make sure and configure them as well.
If you don't factory reset, go the opposite way, uninstall your least important third-party apps and see if the issue disappears. Keep track of which apps you're uninstalling in each group. Keep doing this in reasonably sized groups of apps until you narrow down when the problem stops happening.
Once you find which group of apps being uninstalled keeps the issue from happening, you can reinstall in even smaller batches, among the ones you most recently uninstalled, and eventually find the one causing the issue. In some ways I think it's easier to go the other way around, though, start with a factory reset.
Found the culprit!
Kind of silly: I have installed this app "Internet Speed Meter Lite" when I first started using my P6P, which is for me to monitor my real-time network usage (courtesy of that endless WhatsApp - Google Drive restoring process....). It basically refreshes itself every second and this morning I tried temporarily disabling it, the problem goes away even when the phone is not set to silent mode.
Glad I didn't have to come to the point of factory resetting the device, as I really don't want to go through the WhatsApp restoring process.
Thanks for all the input, much appreciated.