Droid X software update?

[Stang68]

Well, either way, I'm sure it fixes something. I am just wondering why we don't have it yet.

 

[dragozoid]

Okay, my X just froze (at 80% battery life) and after doing a battery pull it's at 90%. The phone has been working great for me but there are a few little bugs that need to be worked out. This is my first time buying a phone at launch.

 

[Cory Streater]

Here is what Motorola had to say about it in their forums:

Yes -- .516 is the retail version. I'm surprised to here that someone got a .604 update today. I know a few devices may have received some test software but it would have been earlier in the week.

I am checking to make sure that there is an upgrade path for your phone when a new update is available for release. We'll figure it out.

 

[Stang68]

Yeah, my battery (along with other people) has been acting crazy. It will show me a different percentage at one point but then will shoot up to a higher one at another.

Phil: have you noticed ANY of these issues with your X after .604?

 

[Stang68]

Here is what Motorola had to say about it in their forums:

That's really interesting. I'll keep my eye on that thread, see what "Matt" has to say. Hopefully something will be addressed!

 

[nedqadams]

Okay, my X just froze (at 80% battery life) and after doing a battery pull it's at 90%. The phone has been working great for me but there are a few little bugs that need to be worked out. This is my first time buying a phone at launch.

Had the same issue. Turned the phone off and back on (no pull) and I got %20 more battery life.

 

[Stang68]

Had the same issue. Turned the phone off and back on (no pull) and I got %20 more battery life.

I am charging right now and it was sitting at 40% for way too long. Turned it off, turned it on, and the phone is reporting 80%.

WTFuk?

 

[SamMyers]

Got mine yesterday, and pretty instantly I had issues with getting Verizon's VisualVoicemail to work.

Called Tech Support, and was on the phone for almost 2 hours, after which, they assigned a "claim" number.

Got a call a few hours ago from a Tech guy (with Verizon of course), and he said that it is a known issue, and are hoping that it is addressed in the update. Which, by the way, he was surprised that my phone had not been updated beyond the factory .516.

They're going to try and push the update to my phone sometime today to see if it will fix the issue.