Today is the 18th. WHERE'S MY FROYO!!!

Okay so i got sick of waiting and rooted, first off I install the Cyanogen room, and right now i am putting on skyraiders... i like it so far, but i have a feeling that i will get bored and just roll back to stock once the updates hit EVERYONE..
 
Okay so i got sick of waiting and rooted, first off I install the Cyanogen room, and right now i am putting on skyraiders... i like it so far, but i have a feeling that i will get bored and just roll back to stock once the updates hit EVERYONE..

Trust me, you wont get bored with those ROMS, you'll just want to load EACH AND EVERY ONE of their updates. Its addicting!
 
Re: Has anyone received the rumored 8/27 OTA Froyo update?

Pizza time to munch maybe when i get done the ota will be too :p lol

sent from Tapatalk
 
I have a friend who's sister has a boyfriend who's mother's brother got the OTA today. But, I am still waiting.
 
As a newcomer to this process, but not a newcomer to technology (software engineer), help me understand this process. Google develops an update to android. Then, the handset manufacturer, HTC, updates their UI layer (Sense) for a specific device to work with the new android version. Then, the carrier, Verizon, gets a chance to test/possibly modify the whole shebang to fit their network/services ... for example, to ensure that they have a hook to enable/disable wifi hotspot capability. After all that, we get it.

But, Verizon says that HTC is actually pushing the OTA for the DInc. That doesn't make sense to me (pun intended). Verizon knows their customer base.

So, what about my description of the process is wrong? Is the Verizon tech I spoke to delusional, misinformed, maladjusted, or what?

? {?
 
Can someone PM me how to RUU the phone? and also is it the official release (with the new boot screen and everything)?
 
... But, Verizon says that HTC is actually pushing the OTA for the DInc. That doesn't make sense to me (pun intended). Verizon knows their customer base.

So, what about my description of the process is wrong? Is the Verizon tech I spoke to delusional, misinformed, maladjusted, or what?

? {?

Choice B
 
As a newcomer to this process, but not a newcomer to technology (software engineer), help me understand this process. Google develops an update to android. Then, the handset manufacturer, HTC, updates their UI layer (Sense) for a specific device to work with the new android version. Then, the carrier, Verizon, gets a chance to test/possibly modify the whole shebang to fit their network/services ... for example, to ensure that they have a hook to enable/disable wifi hotspot capability. After all that, we get it.

But, Verizon says that HTC is actually pushing the OTA for the DInc. That doesn't make sense to me (pun intended). Verizon knows their customer base.

So, what about my description of the process is wrong? Is the Verizon tech I spoke to delusional, misinformed, maladjusted, or what?

? {?

That's the process as I understand it. I agree having HTC push it makes no sense. Why should they pay the bandwidth costs?

Jim :confused:
 
Last edited:
I think this thread shows a bit of insight into the approval process: Update: 2.1 OS upgrade for Rogers HTC Magic+ - Android Forums

Seems like the process COULD go something like this:
1. Manufacturer fits Android for their specific hardware, and adds their own apps and customizations
2. Manufacturer sends to Provider for approval
3. Provider adds bloatware and tests the firmware, and rejects for bugs
4. Mftr makes changes, fixes bugs, sends back to Provider
5. Provider tests, and approves
6. Approved firmware goes to Google; Google approves
7. HTC begins molasses-in-january-speed rollout (according to a @vzwsupport sweet HTC is doing the rollout)
 
i think i got one more question......if the RUU is the official 2.2 then why the hell is erryone complaining about not getting the ota or the update.zip file.....whats the issue?
 

Trending Posts

Members online

Forum statistics

Threads
956,840
Messages
6,970,270
Members
3,163,638
Latest member
Gillian Kirton