Verizon Wireless XV6700 Firmware Update Released... Sort Of

[Raphael Salgado]

<div class='os_post_top_link'><a href='http://www.pdaphonehome.com/forums/showthread.php?t=74909' target='_blank'>http://www.pdaphonehome.com/forums/...ead.php?t=74909</a><br /><br /></div>A few folks over at PDAPhoneHome.com's forums have been on a round-the-clock watch as UTStarcom posts a page and links to the long awaited firmware update for the Verizon Wireless XV6700 Pocket PC Phone. Unfortunately, the file is currently corrupted and quite short at under a megabyte. Perhaps someone is uploading it over a 1xRTT connection, or this is just Verizon's second stage of torture. :roll:<br /><br /><img src="http://www.pocketpcthoughts.com/images/web/2003/salgado-20060620-xv6700.jpg" /><br /><br />At least <a href="http://www.utstar.com/pcd/downloads/APAC_VZW_20720_200_11000_Ship.exe">this</a> is the official download link until it's mirrored on <a href="http://dts.vzw.com">Verizon's Data Technical Support (DTS) website</a> as well. Stay tuned, folks... there's finally a light at the end of the tunnel for the forsaken Verizon XV6700 user.

[blazingwolf]

It's about time. This is one of those things that I dislike about Verizon so much.

[runbuh]

What's up with the corrupted update files lately? First the 8125, now the XV6700. I guess we can just shake our heads and laugh at Cingular and Verizon, both of whom ultimately customized/tested the file package we're all trying to download.

[inteller]

i thought we had figured out binary ftp transfers back in the 20th century.

apparently not.

[bigray327]

Looks like they finally updated it.

I'm goin' in, cover me.... :-)

[smittyofdhs]

looks like it's completly uploaded to the link, the final size 39.5 megs. Anybody ready to install it?

[bigray327]

No issues with the installation. My Sprite backup restored with no problems. I know that's not advisable, but I did it anyway.

Life is good.

[Foxbat121]

i thought we had figured out binary ftp transfers back in the 20th century.

apparently not.

The problem is that they are not using FTP in both cases but rather web upload which is a big problem for partial files. In 8125's case, some ppl can't even get the correct file a day after because their ISP also caches the corruptted files.

[blazingwolf]

No issues with the installation. My Sprite backup restored with no problems. I know that's not advisable, but I did it anyway.

Life is good.

And? Did they give us the goods or what?

[blazingwolf]

Well, I guess I will answer myself. Yes the do seem to have given us the goods. This update even allows you to be connected to WiFi with the phone on. :D Color me happy.

[q-live]

can anyone tell me if it fix sound issues with bluetooth and headset.... also did it fix the camera shutter speed problem?????

[Kevin C. Tofel]

I had no issues with the installation, my Exchange e-mail is getting pushed down just fine and there's what I think is an added bonus: I don't remember having Voice Speed Dial (http://jkontherun.blogs.com/jkontherun/2006/06/xv6700_firmware_1.html) before the upgrade. It appears there now and although it isn't as "intelligent" as MS Voice Command, it does allow for voice speed dialing and launching apps by voice.

[smittyofdhs]

we also have the ability to display the time or the battery icon on taskbar via a registry change thanks to AKU2.2

What to change is here...
http://blogs.msdn.com/windowsmobile/archive/2006/04/28/586453.aspx

[ctmagnus]

we also have the ability to display the time or the battery icon on taskbar via a registry change thanks to AKU2.2

What to change is here...
http://blogs.msdn.com/windowsmobile/archive/2006/04/28/586453.aspx

Bookmarked! (For when I get my new device, that is.) I simply cannot live without the clock in the title bar, as I stopped wearing a watch well over a year ago due to the fact that I always have one Windows Mobile device or another with me, and the time was always in the titlebar in pre-WM5 devices.

[smittyofdhs]

we also have the ability to display the time or the battery icon on taskbar via a registry change thanks to AKU2.2

What to change is here...
http://blogs.msdn.com/windowsmobile/archive/2006/04/28/586453.aspx

Bookmarked! (For when I get my new device, that is.) I simply cannot live without the clock in the title bar, as I stopped wearing a watch well over a year ago due to the fact that I always have one Windows Mobile device or another with me, and the time was always in the titlebar in pre-WM5 devices.

here's how it works now (at least on Verizon xv6700 with AKU2.2)....

By default, the today screen will look normal as it has since WM2003. The time will be on the taskbar and the date plugin on the today sreen will consists of one line that includes the day and date.

By changing the above registry key and doing a soft reset, the today screen will look like AKU2 which has a battery icon on the taskbar and the date plugin now is 2 lines and includes day &amp; date on one side, and time on the other.

As far keeping the date in ALL apps, you can still check to have the time display on the taskbar while in apps other then the today screen.

I have mine setup so that it displays the battery icon on the taskbar while on the today page, but then shows time on the taskbar while in any oter app.

[ctmagnus]

As far keeping the date in ALL apps, you can still check to have the time display on the taskbar while in apps other then the today screen.

I have mine setup so that it displays the battery icon on the taskbar while on the today page, but then shows time on the taskbar while in any oter app.

Hmm... Cool. Thx. 8)

[rstric]

Thanks for the notice on the new ROM! I have not seen update anywhere else. The reason it was so important was because my 6700 would no longer sync with my work's exchange server. I forgot the error code now, but it would not give me permission to sync up. This occured to everyone I know that was running a 6700. Nevertheless, I was up a creek and everything I read to fix it would not work; until, I downloaded the new ROM. Magically, it made everything good and my 6700 now syncs with the exchange server.

I do have a question though. I now have to use a Strong password anytime my phone is not used for 30-minutes. That option, or requirement came up when I was inputing all my information for the exchange server.
That is a royal pain. I can't seem to turn it off. It is not the PIN.
Has anyone experienced this and is there a work around?

Thanks for your help!
RS

[patrol7]

My update installed very smoothly.

To reply to "rstric" I believe that forcing the password is part of the MSFP update. After the MSFP update to my Treo 700W which I had before the VX6700 it forced a password on the device as part of the Exchange Policies. The box is grayed out so you are unable to disable it. You can however change it to Simple PIN with a 4-8 number password and change the time to 24 Hours. This will force a password if the device has been unused for 24 hours or more or on a soft reset.

The MSFP update to my VX6700 did the same thing. It did not force the password until I set up my Exchange account then brought up a window that said it was part of the exchange security policy. It didn't require it prior to the update.

It's not that bad set to 24 hours....It's seldom that I don't use it for 24 straight hours. And set to Simple PIN it brings up a little keypad to enter on the screen by thumb.

[Janak Parekh]

To reply to "rstric" I believe that forcing the password is part of the MSFP update. After the MSFP update to my Treo 700W which I had before the VX6700 it forced a password on the device as part of the Exchange Policies.
To be precise, MSFP doesn't require a password -- rather, it enables a system administrator to set policies on your device. There is no workaround for it, by definition, if you sync to an Exchange server with the policies set. You'd need your sysadmin to change settings on the Exchange server if you wanted to circumvent it.

--janak

[rstric]

thanks for the reply. the news is not the greatest, but it does explain things.

I suppose the security is set high on the server end, because I can not change the strong password or time limit either.

not a chance of cooperation from IT either. it just makes hard to fiddle with a strong pw every 30 minutes, especially to make a call in the car.

wish there were a better way.
thanks rs

[Janak Parekh]

wish there were a better way.
The only "better way" would require circumventing the security mechanisms MS put in place, and that would, of course, have Pocket PC lose its value proposition to enterprise customers.

In other words: not likely. :( Maybe biometric-enabled Pocket PCs will be eaiser for IT to enforce strictly and be convenient for users, but they're no biometric-enabled Pocket PC Phones out there.

--janak