Database Info

Lost ringtones (most of them)

I noticed the problem when someone tried to call me. My phone would just vibrate and not ring. It took me awhile to narrow down the problem. It seems only the first few ringtones in the list (Alarm-****) are the only ones that work anymore. The rest are still listed but when i try to test them, they don't play. Anyone know where the default ringtones are stored or how to fix this issue? If not, I'll just have to hard reset.

issue fixed. I had selected to associate all the audio file types to my pocketmusic application. I unassociated all the file types and now it works again.

Vibrate mode stopped working!

I have the 750, upgraded to WM6.1 - however, after installing a couple of third party apps, it seems that my vibrate mode has stopped working. I disabled, then deleted all outside apps - no go. All settings are correct and I have checked everything that I can think of to fix it.
Anyone know of any problems related to the upgrade, or any other issues? Any help would be appreciated, since I love the phone, but really need the vibrate function.

Ummm, nevermind
Well, it seems that I have cleared up my own problem. I accidentally dropped the phone onto the floor from a short distance, and it fixed itself!! Hmmmmm. Clutziness to the rescue!!

MT4GS not remembering ringtones

So for a few weeks now, my phone has been unable to remember the ringtone I set for either SMS or phone calls. every time I set it it works, but as soon as I reboot the phone or unmount the sd card then remount, it forgets both tones and picks one of the songs on my sd card as the new tone.
I first noticed it after I was having some problems with btunes (my preferred music app) crashing, so I decided to clear the cache and data in Media Storage from the "Manage applications" menu. I learned to do this from the developer of another music app I had problems with, and thought it was worth a try.
ever since then, i've had the problem. I don't know why. To be fair, I MIGHT have had the problem before that, since I had only had the phone for 2 weeks at that point and didn't pay attention to it due to finals, so I wasn't doing much rebooting, and anyway the ringer volume was probably off the whole time. My memory is fuzzy about the ringtones working before that point. It was definitely happening before I rooted though, so I know that's not the problem.
anyway, help? on a side note, it always seems to automatically pick the same 2 songs for the 2 replacement ringers once I reboot. I'm not sure why, especially since they're not in the media/audio folder anywhere, and don't show up as potential ringtones when you look in any "pick ringtone" menu.

If you are rooted I would say reboot into recovery and clear dalvik-cache.
Sounds like that's where a setting is hiding.

I had this problem too when I was on Bulletproof 1.0, then when I switched to 1.1 it stopped. I don't think it was necessarily rom related, but maybe something to do with the wiping when changing roms.

I've had my (rooted stock ROM) MT4GS forget its notification settings a couple times - for me they usually stay set for a while, but after some time and/or reboots will come back wrong (not always the same wrong either- a few times it has picked notifications from my music folder, other times from the default sounds).
The problem seemed to start after I put another Android device (CM partition on my Touchpad) on my Google account, so I've been operating under the assumption that it is some kind of bug with settings synchronization. Unfortunately, it isn't very repeatable so I've never pinned the behavior down exactly.
I don't know if the issues are related, but gathering information on similar problems will hopefully let someone zero in on the issue.

the settings sync issue is worth checking, especially since I still have my Transform Ultra that I sometimes have turned on at home on wifi. I checked it, and the ringers were set on something else, So I matched them to the MT4GS and we'll see what happens.
I'm not sure that's the culprit, though, since this only happens when I restart the phone or re-mount the card. seems like settings sync wouldn't be an issue there, though I may be wrong.

I have the same issue with MT4GS and mines is certainly not rooted yet. The phone is only a couple weeks old. But its annoying. Sometimes I don't even have to reboot, sometimes it randomly just happens. IDK what to think of it.

I always shut off settings sync during setup and this used to happen to me.
Sent via smoke signal.

blackknightavalon said:
I always shut off settings sync during setup and this used to happen to me.
Sent via smoke signal.
Click to expand...
Click to collapse
You mena the initial setup of the phone? and how did you stop it?

Yeah its the google "backup my device" crap malfunctioning. Its dumb because what do u want it to backup? Texts, logs... What does it backup? Apps and bullcrap. If u want to start over, y can't I install apps individually? Or just give me the lists of crap ur gonna reinstall on my phone and let me select what I want....
Anyways, turn it off, reboot, sync, before nandroid/rom flashing and then don't use it on fresh install.
Sent from my myTouch_4G_Slide using Tapatalk

Falkner09 said:
You mena the initial setup of the phone? and how did you stop it?
Click to expand...
Click to collapse
See Etrick's post right under yours.
Sent via smoke signal.

ok, so what you're saying is, google's sync system is flawed so it periodically screws up the ringer settings on my phone, by attempting to "correct" them to the server information? why doesn't it just upload the knew info of the correct ringtone when I deliberately change it?

Falkner09 said:
ok, so what you're saying is, google's sync system is flawed so it periodically screws up the ringer settings on my phone, by attempting to "correct" them to the server information? why doesn't it just upload the knew info of the correct ringtone when I deliberately change it?
Click to expand...
Click to collapse
That's what she said... PRECISELY what I don't understand. It seems as though everythings good, you've set your phone up after a fresh install, and everytime you make changes it syncs and instead of uploading the new stuff, it downloads the old. It may be something we are doing wrong by hacking our phones and some setting somewhere is missing or a simple kernel command is confusing it or who knows... Maybe its google's fault... All I know is, its annoying. It should get rid of your issue.
On a side note, there may be some settings for this hidden in some settings you can only find via pc. Like buried in google voice or plus or chrome or some now defunct google product you can no longer log into... Perhaps some digging there. I've found little to no documentation on the phone end...
Sent from my myTouch_4G_Slide using Tapatalk

hmmm, well it can't be hacking, because this was happening before I had the phone hacked. also, oddly enough, I also have a different off line phone as a spare that's on the same android version, 2.3.4, yet does not have this problem. of course, that one's stock Android, not infected with Sense.....

Falkner09 said:
hmmm, well it can't be hacking, because this was happening before I had the phone hacked. also, oddly enough, I also have a different off line phone as a spare that's on the same android version, 2.3.4, yet does not have this problem. of course, that one's stock Android, not infected with Sense.....
Click to expand...
Click to collapse
Well... If it happened prior to hacking, then it's not google backup. So go with other possibilities... Phone is hosed... Sd card hosed... (Have u tried selecting various tones on card or in your system media folder within your phone?)... Or is that other phone ever on? Could be going back to that sync issue. Turn it on and then see if its connecting to wifi and syncing. Which ringtone r u stuck on?
Sent from my myTouch_4G_Slide using Tapatalk

My phone started doing this after I swapped SD cards with a larger one. I just had to go in, change it to something else, then change it back. Been working fine since.

Can't Answer or Make Calls

So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou

It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.

Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?

louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.

Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??

louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend

Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.

louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.

Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.

I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.

Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.

Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.

Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?

nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon

I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.

The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.

Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.

Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.

Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).

ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!

Question Microphone not working for some specific apps

Hi,
I've got a problem. Suddenly a couple of apps won't recognize any sound when using the microphone, e.g. WhatsApp. When I want to record a WhatsApp voice message the app does not record any sound. The sent message is completely silent. Strangely it does work when the screen recorder is running, presumably because the microphone is activated by the recorder. Has anybody an idea why that could happen? It worked till a couple of days ago.
I am on the current Android 12 Version on the latest patch (01.05.).
Thanks!

This is a guess. WhatsApp may have lost the "Allow Use Microphone" permission.
Newer versions of Android can revoke permissions if it wants.
Usually in Settings there is an App Permissions option. Or, long-click the icon and press the "I" for information. You may be able to view/set permissions from there.
This is only a guess - where I would look first.

Sorry, I forgot to mention, that it does have the permission to use the microphone.
WhatsApp Calls, Video recording, ... do work. The problem only occures with voice messages.
As I said, WhatsApp isn't the only App that does not work, there are a couple more, that all the sudden so not recognize the microphone anymore.

I had similar problem with my zflip 3 . I sugest you to make a diagnostic with the samsung members aplication. My secundary microphone was broken , so I had to replace the charging port card (sub pba) .

I don't have a solution but this exact thing, has just happened to me today too! You are the first person I've found with the same problem! Have you heard anything yet? Or had any luck? I've gone as far as to do a full factory reset and still nothing.

Were you able to fix it?
I'm also on Android 12.

Rayrsn said:
Were you able to fix it?
I'm also on Android 12.
Click to expand...
Click to collapse
Nope still broken. Samsung have offered to look at it under warranty but would need it for 2 weeks so I'm waiting until that's viable!