Both Engadget.com and androidcentral.com are reporting that a Verizon rep has confirmed that Froyo (Android 2.2) will start to be released today (08/27/2010). Personally, I've heard wolf cried one too many times to start holding by breath now. I admit however; I'll be checking the system update menu throughout the day anyway.

When 2.2 does reach the Incredible it boasts Adobe Flash 10.1, HD 720p video recording, mobile hotspot support, and presumably the bluetooth stacks for human interface devices (bluetooth keyboards anyone?). Other 2.2 users have also reported a noted increase in speed, which while unnecessary on these already snappy phones, will be welcomed.

As of 9:23am (MST) I have yet to hear of any legitimate OTA updates happening.

**Update**
As of 10am there are rumors of people in the Pacific North West getting the update. I've only seen one person claiming they've received it though.

**Update** 
12:30 and 16 people have reported that they have it on a poll at AndroidForums.com 

**Update**
4:50 and still only a hand full of users have announced that they've received the update.

**Update**
3 days later: Android central users have tracked down the file on verizon's servers and have posted a link and instructions on how to manually update. 

**Update** 
Downloaded the file to 90% and all of a sudden my phone announced that my OTA update was available. Installing 2.2 as I type. 

The 2.2 update for Android users has been wrought with problems. As an Incredible user I've seen half a dozen or more "leaked" patch dates, that came and went with nothing to show for it. I'm not sure if they were real to begin with or just fabricated to generate clicks to the originator's blog/site. I for one am just going to stick with Verizon and HTC's original announcement stating, "We'll have it to you by Christmas". 

I'm really looking forward to it for a number of reasons. I have to say the main one is the supposed ability to connect and use blue tooth keyboards. Since I got my Incredible I stopped carrying around my laptop because I just didn't need it anymore, so having the ability to bring along a blue tooth keyboard to draft emails or blog posts would really be a great utility. 

Other phones and manufacturers seem to be having a myriad of issues as well. The 2.2 patch for the Motorola Droid doesn't even get key features of the update including most notably 10.1 flash. After some significant user backlash it was announced that 10.1 would be made available on the Android Market in the near future.

Even worse the Cliq, Cliq XT and backflip aren't even expected to get 2.2, and are still waiting for 2.1. I'm not sure which version was promised to these owners, but I'm glad not to be in their shoes right now.

I think that the way carriers and manufacturers handle these updates is going to be vital for Android's future. Too many broken promises and users will loose faith in the brand, and may drift back to an inferior, but more consistent iPhone.

**UPDATE**
2.2 did not fix Bluetooth keyboard (HID) input. I'm incredibly disappointed (pun intended)

I did an article back when they released the Nexus One contemplating it's lack of support for AT&T 3G networks or Verison / Sprint CDMA networks. Well, they appear to be trying to redeem themselves by releasing a phone compatible with AT&T and Rogers Wireless (Canada) 3G networks.

They still have a ways to go before getting me back on board. Primarily they need to include tethering support. Now I know that this is mostly because of the service providers not wanting to support the tethering, but in my opinion they should include it as a native app and let the service provider duke it out with their subscribers.

Verizon and Vodaphone versions of the Nexus One are due out "Spring of 2010" (aren't we there already?).

For the last 2 days I've been fighting with an intermittent issue where suddenly after a handful of connections my apache server would stop responding to connections. At first I thought I was running out of resources due to huge looking httpd processes, but those all turned out to be fluff. While they announced a reservation of about 300 megs per process in the end they only used a few kilobytes each. Then I realized, when the connection would start timing out, I didn't even see any new processes spawned. So the problem was outside of the server? What else is there? So I called my ISP and after spending some time on the phone with the tech, he convinced me to plug the internet connection directly into the server, bypassing the router. No longer could I cause the failure. I hammered at the site for a few minutes and to my surprise, it didn't stop working. So it turned out to be the router. Initially I figured the router just couldn't handle the requests, but it did seem very much like some under the cover security feature, like an overactive ddos prevention tool, but I couldn't find anything like that. At least until I went through each page of the router interface clicking on the help icon for each item. Eventually I came across a option titled "Disable SPI Firewall". The description read "Firewall protects your LAN against Denial of Service attacks. This should only be disabled in special circumstances." So I guess 3-5 people trying to browse a forum constitutes "special circumstances" because as soon as I selected the option, I was back in the clear.

The next step of course was to enable some ddos prevention tools directly on the server, but that wasn't all that difficult. In the end I spent two days looking in all the wrong places, and a COX business tech was the catalyst to discovering the root cause.

Tonight I'm doing some upgrades to the server to prepare for a new project. It shouldn't take more than a couple hours, but will affect all sites. Estimated starting time 9pm (EST).

Thanks for your patience,

--HexKrak

UPDATE:

All upgrades were successful. We've made the leap from Fedora Core 10 up to 12, and all services and sites are once again operational.