• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Update coming for Volume Issue

Motorola's fix will be through an update which will likely make it louder at the expense of sound clarity on a speaker that isn't in stereo to begin with. But hey, at least it's some attempt at a fix. We'll all get to see if it works after the update is out and either complain or praise it then.
 
Paycer said:
I'm talking about this thread. I never said I found the article first. I found the link after seeing a post from someone else, (no, not you).

The quote of myself is from this very thread, on this exact page. My point was that you're repeating something that's already present in this thread.
Click to expand...

You typed quite a few words to say nothing, really. How's the X? Oh, I forgot, you don't have one.:rolleyes: Gotta love people who talk smack about a phone they don't even own.
 
Only thing that sucks, is this major fix/update is going to come out after all of our 30 day return windows have expired.

With the number of real issues that need to be addressed, I wish they would just kick out what they have nailed down, and do a later update with the rest of the fixes.
 
Gareee said:
Only thing that sucks, is this major fix/update is going to come out after all of our 30 day return windows have expired.

With the number of real issues that need to be addressed, I wish they would just kick out what they have nailed down, and do a later update with the rest of the fixes.
Click to expand...

Plus 1 on that. My first X was defective and VZW ordered me a new one. I asked that the 30 day window be extended and it was. My 30 day window expires at the end of the month. If they haven't released a fix before that time, I will have to return the device or look at the Droid2 or go back to my Incredible.
 
Isn't this sort of thing covered under the 1-year manufacturer's warranty? I would think this is considered a fault of the manufacturer and nothing that the consumer could have done. Won't every owner of the X be able to get a fix or a replacement?

I'm not going to go off-topic here anymore and further degrade this thread, so you can check your PMs, TheXFactor, if you want to see anymore replies from me regarding that.
 
Jim Dawson said:
How does replacing the default sounds and audio address the low in call and navigation volume?
Click to expand...

It's not a hardware issue. I used myoutlook.com to make my wife's phone "scream". It was the loudest sound I'd ever heard coming from any cell phone. It was so loud you could hear it from outside half a block away.
 
Paycer said:
Isn't this sort of thing covered under the 1-year manufacturer's warranty? I would think this is considered a fault of the manufacturer and nothing that the consumer could have done. Won't every owner of the X be able to get a fix or a replacement?

I'm not going to go off-topic here anymore and further degrade this thread, so you can check your PMs, TheXFactor, if you want to see anymore replies from me regarding that.
Click to expand...

Flawed logic. It's not as simple as a 1 year warranty. Gareee and others (other forums) have mentioned the 30 day return policy, and it looks like the update will be released after the 30 days is up (at least for those who purchased at launch or close to it). Volume is a subjective thing so some might be satisfied with the software update while others won't. The rear speaker is not stereo, so the update has a chance to make things louder.. but can sound distorted at the same time. Ideally, we get louder without the expensive of sound quality.

So for those unhappy or have a hearing problems with the current loudness, they're basically in limbo right now. It could be that they love the 4.3" screen sans a keyboard and might have to take a chance on the update working out. Then again, maybe they might have to get the D2 (assuming good quality sound) and give up the 4.3" screen and slimmer phone.
 
so with froyo a month or so away, do we believe that there will be an intermediate OTA update to 2.1 for this? i'm not so sure.

i'll gladly wait for froyo, if it will address speaker volume, speakerphone quality, wifi connectivity, vpn connectivity, and exchange connectivity.

yeah. all that.

i mean, WTF motorola? how is this supposed to be an acceptable device in the business world?
 
john0821 said:
Flawed logic. It's not as simple as a 1 year warranty.
Click to expand...
I wasn't stating what I said as fact. I was suggesting alternative action and asking if my point was valid. There's nothing, "flawed," with asking a damn question. If anyone wanted to simply discuss the possibility of my suggestion being true, then they were welcome to.

I went ahead and very carefully re-read the warranty portion of the phone's manual, since no one has decided to give me a straight answer. The only answer I got was really just an attempt at insulting my intelligence and brushing me off.

softwarechart.png


Since things like this are worded so carefully for a reason, I guess we need to be pretty technical about this. I suppose the audio files present within the phone's operating system aren't really, "physical defects." As a result, I don't think that Motorola would agree with the argument that this should be covered under the ninety day warranty shown above. At least we know and probably don't need to bother considering it in the future.

EDIT:
matty032 said:
Which folder do you place the ringers, and notification files?
Click to expand...
I think that you can actually create, "Ringtones," "Notifications," and, "Alarms," folders on your SD card and the phone will recognize them. I read this in another thread here on the forum.
 
Paycer said:
I wasn't stating what I said as fact. I was suggesting alternative action and asking if my point was valid. There's nothing, "flawed," with asking a damn question. If anyone wanted to simply discuss the possibility of my suggestion being true, then they were welcome to.

I went ahead and very carefully re-read the warranty portion of the phone's manual, since no one has decided to give me a straight answer. The only answer I got was really just an attempt at insulting my intelligence and brushing me off.

softwarechart.png


Since things like this are worded so carefully for a reason, I guess we need to be pretty technical about this. I suppose the audio files present within the phone's operating system aren't really, "physical defects." As a result, I don't think that Motorola would agree with the argument that this should be covered under the ninety day warranty shown above. At least we know and probably don't need to bother considering it in the future.
Click to expand...

The warranty won't matter at all in this case. The software fix for the speaker is Motorola's solution. IF it doesn't work out, then those who are past their 30 day return period will take a loss on the phone. Those who didn't purchase at retail cost (renewing 2 yr contract) might profit by selling their DX, but they will take a hit when it comes to buying a new phone at full retail (such as the D2). This is the concern people have.

The warranty really only applies if there is a defect or simply put.. if it's outright broken ... as in speaker is blown, speaker is broken, display errors, faulty batteries, unresponsive buttons. And the warranty only covers an exchange of the same phone. Again they can have a new/exchanged phone, but if the software update doesn't correctly address the sound problem that some experience, then they are stuck with this phone.

I hope that this software update does correct address the problem. But the non-stereo/mono speaker isn't the best to work with.
 
john0821 said:
The warranty won't matter at all in this case.
Click to expand...
This was my conclusion exactly. Re-read my post if you didn't notice.

I agree with you entirely. It sucks but I don't think there's a lot we can do about it now. We can decide whether or not we want to continue putting up with the issue if Motorola's fix doesn't help, or we can play it safe and return the phone for another.

For those of you who decide to exchange your phone, please know that you will be charged $35 in restocking fees and cannot return the second phone. Once you make a device exchange within the thirty day period, it is final for the remainder of your current contract.

Return Policy - Verizon Wireless
www.verizonwireless.com said:
New and Certified Pre-Owned wireless devices and accessories may be exchanged within 30 days. You are permitted to make one exchange. A restocking fee of $35 applies to all wireless device exchanges (excluding Hawaii).
Click to expand...
 
Paycer said:
This was my conclusion exactly. Re-read my post if you didn't notice.

I agree with you entirely. It sucks but I don't think there's a lot we can do about it now. We can decide whether or not we want to continue putting up with the issue if Motorola's fix doesn't help, or we can play it safe and return the phone for another.

For those of you who decide to return your phone, please know that you will be charged $35 in restocking fees and cannot return the second phone. Once you make a return within the thirty day period, it is final for the period of your current contract.

Return Policy - Verizon Wireless
Click to expand...

Let me add that this only applies if you are exchanging a device for another model. If you have a problem with your current device and exchange it for a new non-defective device (same model) you are not charged a restocking fee.
 
I figured that was redundant. Someone returning this phone because of this problem is doing so to get a different phone. You know, one that doesn't have this problem... Why would someone return a phone that has a design flaw, (physical or otherwise) only to turn around and get the exact same phone? The issue doesn't seem to be present on any kind of Droid X in particular. It's supposed to be present on every model.

I think I see the confusion though. I was referring to a device exchange when I said, "return." I'll edit my previous post now and clarify, to prevent anyone from thinking otherwise if they read it in the future.
 
Maybe it's just me, but I haven't noticed any issues with the volume. Seems plenty loud for me. Perhaps it's because I'm using a custom ringtone that I created from a song? Who knows. But if you're having problems hearing the phone ring, I'd suggest choosing a loud song and using RingDroid to make a new ringtone. The notification beep is fine for me too. Obviously, others are experiencing this issue though so it's not made up. Maybe I'm just in quiet places more often...If I'd complain about anything, it'd be the vibrate isn't as strong. My old phone, which had a clamshell design, had a stronger vibration for sure that was easily detected in my pocket. I've missed a couple calls when I had it on "vibrate only" because I didn't feel it.
 
Jim Dawson said:
Since they have been distributing Froyo for awhile the volume solution probably won't be with it. God only knows when the next release will be.
Click to expand...

They have a month to figure it out which I do think it is absolutely possible. The volume issue seems to be DX specific as well. Can't be too upset when a manufacturer listens and provides support.
 
Froyo has not been distributed yet for the dx.. I'm sure we'll get a modified version of it. They could simply include louder replacements for the ringtones to correct the volume issue some people have.

I'm sure they keep delaying the froyo release date because of issues like this they want included in the fix.
 
Froyo may not be officially released for the Droid X yet, but AllDroid is still working on that dev phone and they're getting closer from what I can tell.

It's almost like a race. I'm kind of excited. :D
 
john0821 said:
They have a month to figure it out which I do think it is absolutely possible. The volume issue seems to be DX specific as well. Can't be too upset when a manufacturer listens and provides support.
Click to expand...
Yes, I misspoke when I said Froyo had been distributed already. I was thinking of the original Droid (which has phenomenal volume).
 
e5116 said:
Maybe it's just me, but I haven't noticed any issues with the volume. Seems plenty loud for me. Perhaps it's because I'm using a custom ringtone that I created from a song? Who knows. But if you're having problems hearing the phone ring, I'd suggest choosing a loud song and using RingDroid to make a new ringtone. The notification beep is fine for me too. Obviously, others are experiencing this issue though so it's not made up. Maybe I'm just in quiet places more often...If I'd complain about anything, it'd be the vibrate isn't as strong. My old phone, which had a clamshell design, had a stronger vibration for sure that was easily detected in my pocket. I've missed a couple calls when I had it on "vibrate only" because I didn't feel it.
Click to expand...

Have you tried the gps yet? lol you cant even hear it unless no one is talking and no radio...
 
You must log in or register to reply here.
Back
Top Bottom