NO SOUND after charging or being in silent mode

[Darkmstf]

I have SAME problem. Didnt associate it with charging - altho I did have phone charging thru day and it didnt seem to affect it. I too just had a recent system update (I usually keep my background data turned off and was only a few wks ago that I turned it on and an update got pushed). Now phone doesnt sound when ringing - nor does my music player work (that's how I've learned to test to see if I 'll be *hearing* calls or not). This will be my 2nd droid that got messed up by motorola sys. Updates. Im done with motorola. I went to verizon & they said only option was a reset which I refuse to do - again.

Only way to get phone ringing "audibly" again is to restart it - which is also slooowwww.

Sent from my DROID X2 using Droid X Forums

[Ads]

[Goose306]

I have SAME problem. Didnt associate it with charging - altho I did have phone charging thru day and it didnt seem to affect it. I too just had a recent system update (I usually keep my background data turned off and was only a few wks ago that I turned it on and an update got pushed). Now phone doesnt sound when ringing - nor does my music player work (that's how I've learned to test to see if I 'll be *hearing* calls or not). This will be my 2nd droid that got messed up by motorola sys. Updates. Im done with motorola. I went to verizon & they said only option was a reset which I refuse to do - again.

Only way to get phone ringing "audibly" again is to restart it - which is also slooowwww.

Sent from my DROID X2 using Droid X Forums

Yours is an X2... theirs is an X. The two issues are not correlated likely as you are referring to different system updates.

Any ya'll try an SBF or data wipe? I still stand by the fact you need to do this to determine the root cause of the issue and probably resolve it. Or just root it (which will probably end up in an SBF anyways if on the latest OTA) and flash a ROM. Poof! Gone! :P

Sent from my Liquid ICS

[may0799]

My wife's phone has the exact same issue, as did mine untill I flashed it to gummy. Happens almost every morning.

Sent from my DROIDX using Tapatalk 2

[riboflavins]

Yours is an X2... theirs is an X. The two issues are not correlated likely as you are referring to different system updates.

Any ya'll try an SBF or data wipe? I still stand by the fact you need to do this to determine the root cause of the issue and probably resolve it. Or just root it (which will probably end up in an SBF anyways if on the latest OTA) and flash a ROM. Poof! Gone! :P

Sent from my Liquid ICS

No, I have not rooted the phone or anything. I don't feel I should have to do that to get a properly working phone. Motorola just sucks. I am up for new contract, so I am deciding between S3, Galaxy Nexus and Droid rzhr HD, but since since the rzhr is moto, I will probably not go with that phone. And as someone else said, my music player also stops working. Basically, after I leave it on silent for a certain amount of time, all sound goes off, and the camera app doesnt work. I need to restart the phone to get it back. And someone else also said all the photos were messed up, mine did that also, in between the camera just not opening up once I leave the phone on longer.

[Goose306]

If you do not want to root I would highly recommend a factory reset/SBF to have a happy-again phone. However, again, rooting is going to make the process of getting all your apps and stuff back after an SBF or factory reset much, much easier.

Any phone can and will eventually have issues. It is a miniature computer you are carrying in your pocket all day. Besides the obvious analogy the fact is wear and tear is also very likely much higher on your phone than it is on your computer. If you get a bad update that b0rks something, you have to revert back or start fresh, just the same as a computer. A factory reset will wipe all YOUR data off your phone, making sure it wasn't a bad app or something you had done that had caused the issue. An SBF will reflash the system (similar to re-installing Windows) to make sure everything is fresh and clean on that end as well, including the base level firmware (kernel, etc... stuff you normally don't even get close to touching in Windows).

If you want to do this, I would recommend doing the SBF first, as if you are flashing the same system version on top of the same system version, there is a chance you won't lose your user data. However, regardless you may find yourself in a situation that requires a data wipe. Again, why I recommend rooting. When rooted if your phone does act up you can seemlessly back up all your apps and data, wipe/SBF, and restore and be effectively back to where you were before but about 500% faster than if you weren't rooting. There is no downside to rooting, besides the voiding of the warranty, however through the SBF procedure you can easily return it to a stock, unrooted state. And the Droid X is nigh impossible to "brick" due to its encrypted bootloader... if you screw up something to far on the system side, you just SBF, and your right back at stock again.

My two cents. I will, regardless, recommend rooting as a solution to your problem because it has been proven time and again to be a solution, and it is an extremely easy one, easier in fact than attempting to troubleshoot without root, because an SBF/data wipe when rooted is about a 30 minute procedure to get back to where you were previously, and it will fix the problem 100% of the time unless your hardware itself is broken.

However, if you would like to troubleshoot further, if you go to the Play Store and get an app called "alogcat" (free) and get a system log of the issue when its occuring, this would be extremely beneficial as to possibly helping us, as I am unable to replicate your issue. Just open the app, let it start reading the logs, get a notification or basically have it running when the issue occurs. Open the app again, hit Menu key, choose Export to SD Card (or something similar). It will make a .txt file on your SDCard in a folder called alogcat. Take the .txt file, copy and paste it to Pastebin.com - #1 paste tool since 2002! and post the link here so we can look at it and we may be able to find the source of it then.

[Impact]

Yours is an X2... theirs is an X. The two issues are not correlated likely as you are referring to different system updates.

Any ya'll try an SBF or data wipe? I still stand by the fact you need to do this to determine the root cause of the issue and probably resolve it. Or just root it (which will probably end up in an SBF anyways if on the latest OTA) and flash a ROM. Poof! Gone! :P

Sent from my Liquid ICS

Sure sounds to me like it's the same issue... Mine is an X as well, but my symptoms are identical. I've also gotten into the habit of periodically checking my music player or my camera to see if my sound is still working in case a call happens to come in.

Really frustrating. If I was the kind of person, or had the type of job, for example, where my phone was always ringing I would have thrown it out the window by now. Luckily I don't send/receive that many calls. Still very annoying when it happens, though.

I can see both sides of hte rooting argument. Lots of folks might not be that technically inclined to want to root their phone (although I'd expect most of those would also not be the types to do web searches looking for problem fixes either... ; ) I myself am not necessarily opposed to rooting my phone (Is there a thread on here that walks you through the process? I might decide to try it just to learn more about it.), since my next step will likely be to get a different phone anyway. I've recently been looking into lower-cost alternatives for plans than what I've had with Verizon, even though they seem to have the best coverage.

EDITED TO ADD THIS POINT: I'm also strongly in agreement with the statement that one should not have to go to 'extraordinary measures' to keep the basic functionality of a device working, especially one which we are paying a hefty monthy fee for the priviledge of using.

Maybe I'll try downloading the logging app and see if I can get a log on here, since no one else has done so so far.

[vlkeeney1]

I have had the same problems for months - all sounds go off, camera 'pretends' to work and only takes 'grey squares' when I go back to review the photo. I downloaded alogcat and even contacted Motorolla and sent them a log. Their answer was that they are not releasing any more updates for the Droid X so therefore they won't be fixing the problem (a problem they don't admit exists - I am the ONLY person who has complained!)!!

My phone is so unreliable now and it always seems to stop working when I need it most!! I hate to get a new phone and extend my contract even longer with Verizon - they were of NO help in trying to solve this, or any other phone problems. As usual, their only reply is factory reset!

Has anyone found the cause of the problem yet? I have a log I emailed to myself the last time it happened and don't know where to send/upload it for someone to review and possibly figure out the problem. If anyone knows how to read the log and discover the problem, please tell me how to get the log to you.

[Impact]

I never did find the cause of the problem. A couple of months ago I finally bailed on the X and also Verizon. Switched to Virgin, got a more modern, 4G phone, and am saving about 40 bucks a month. Pretty much a win all the way around. Best of luck to those of you still struggling!

[Ricowan]

The solution I ended up with was upgrading to a Galaxy S3. The DroidX was a really good phone, lasted over two year, but this G3 is the best phone I've ever had. I wouldn't blame Verizon too much on this, it's all on Motorola in my opinion.

[Fred93GT]

Write me in too for the sound and camera issues, thought it was my phone but after seeing this I realized it's the droid x in general and not specifically my phone. Getting the S3 on Monday when my upgrade is available.

Sent from my DROIDX using Droid X Forums