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

2.1 OTA Beginning 5/11/2010

My phone was flawless on 1.5. The leaks have brought the following issues:

-Signal bars not accurate
-Sound dropping on the phone and can't be fixed without a reboot.
-Browser crashing
-50% without signal bug

All of these issues are present on v3 of the leak. V2 had issues with gmail images and linking to the internet from within a program. They have since been corrected.

Right. I think the previous leaks may have triggered some of these problems. The signal bars and 50% without are just bugs in the software. They don't really cause problems and they act just like some of the other problems that people had before MR2. The browser crash is more of the same. Some people have it and some don't from what I understand. The silent call or sound drop issue, as you call it, is one of the more serious problems. Nobody knows what causes it and from what I have noticed, everyone that has it started on leak 1. I may be wrong on that, I may just be noticing the most vocal.

So I'm guessing that I should try to replace the phone BEFORE getting the update...just to make sure...right? I may have to give them a call to discuss it.

Thanks for the input! :)

I don't think you should rush for a return. Wait for the OTA and see what happens. It may solve most of your problems. You've waited this long with the problems, a few more days shouldn't change anything.

The other thing I've wondered about is whether there are issues with some installed applications when the upgrade to 2.1 happens. Since everyone doesn't install the same apps it would make sense that some would have problems and others wouldn't. The only way to track that down is to uninstall all apps and see if there are problems. If not, add back one at a time until you find the problem app.

I think some members have tested that and still had the silent call problem.

i remember back in november when my phone was new, of course still on 1.5, my phone would reboot at random times. so will the other two erises in the house. im not sure if it was fixed by the MR1 or MR2 but im thinking i might be in for trouble when 2.1 hits. according to OTD's theory about "waking up" those bugs.

I wouldn't go that far. Remember, it is just a theory. :) Since the OTA is pretty much unavoidable, you can just wait and see. If you have problems, it is under warranty.

The most prominent of these seem to be:

50% without signal
Silent calls (my personal favorite)

I tend to think that the 50% without signal bug is not necessarily a "bug" but an incomplete implementation of a feature that was simply not fully cooked in the leaks.

I also think in lieu of the update fixing anything, I think the Silent Call issue will be there no matter what.

I agree, I don't think that those with the silent call problem are ever going to get rid of it. It is in the phone and most likely always has been. I think one of the new features that 2.1 provides may have just brought it to the surface.
 
i remember back in november when my phone was new, of course still on 1.5, my phone would reboot at random times. so will the other two erises in the house. im not sure if it was fixed by the MR1 or MR2 but im thinking i might be in for trouble when 2.1 hits. according to OTD's theory about "waking up" those bugs.


They may still have an MR3 (bug fix) after this rollout. This most likely isn't the end of the road, just one of the last milestones.

/speculation (but it could happen)
 
Is it just my imagination, or once again does it seem like there have been more Market updates available?......Just to taunt us with an icon up in the corner. Seems each time the OTA update winds are blowing, this happens.
 
Is it just my imagination, or once again does it seem like there have been more Market updates available?......Just to taunt us with an icon up in the corner. Seems each time the OTA update winds are blowing, this happens.
All of the app devs are making update to torture us. :)
 
They may still have an MR3 (bug fix) after this rollout. This most likely isn't the end of the road, just one of the last milestones.

/speculation (but it could happen)

I agree. I dont know about the 50% without signal bug, but I think having less signal bars is kind of a big deal.
I think knowing how much signal you are receiving at any given time is something you should expect to work. Its kind of important to know whether or not you have a signal sometimes rather than being surprised whether you can or cannot make a call, or if you will be breaking up all the time during the call.
 
So a question, if someone had the v3 leak would it be possible reflash the same leak version? I ask because if the leak and OTA are similar enough the software might block a reflash even if someone posted a link to it. But i'm not experienced enough to even know if thats possible or how it works.
 
So when are you going to give up your source?:D Inquiring minds want to know.

Oh, I think we know what his source is....

s02.gif
 
yeah i would never....and i would never pass on bum info either....

V3 and OTA are in fact the same s/w and radio version.

there MIGHT have been some very minute changes between them, but nothing noteable.
 
For those who are thinking about going to your nearest Verizon store to get a update, I just got off the phone with a friend who works at a store and he told me they do not have it as of yet. He said maybe in a few days hey might get it because of some last minute issues with the firmware.


(for what it's worth...)
I just left my local VZ store and the rep said that he doubts if many people will have it before Sat/Sun of this week. He said that they are working on correcting a few issues and that he would bank on most Eris users receiving the update between Sat and Mon.
 
So a question, if someone had the v3 leak would it be possible reflash the same leak version? I ask because if the leak and OTA are similar enough the software might block a reflash even if someone posted a link to it. But i'm not experienced enough to even know if thats possible or how it works.

It shouldn't be a problem. I reflashed V1 and V2 3 times each to test different things out.
 
i agree cause i know for absolutely positive they are the same.

from the forum, it's my understanding the check sums vary.

if true, can you speculate on the difference in check sums?

thanks,
jim

[pgh. pa., 1.5, no updates (2 erii {wife & self})]
 
(for what it's worth...)
I just left my local VZ store and the rep said that he doubts if many people will have it before Sat/Sun of this week. He said that they are working on correcting a few issues and that he would bank on most Eris users receiving the update between Sat and Mon.

I have absolutely no clue what I am talking about but it just seems to make no sense what so ever to have this "on their system", release media about it and then not have it work.
 
Wow, I didn't expect so much response to Caddy giving up the source.:eek:

I also know that if he was going to give up his source he would've already done it. But it doesn't dissolve my curiosity.:D
 
Is it just my imagination, or once again does it seem like there have been more Market updates available?......Just to taunt us with an icon up in the corner. Seems each time the OTA update winds are blowing, this happens.

I honestly think this is just responsible Dev's keeping their *products* up to date and current as more devices get rolled into 2.1.

I agree though, every time you see "update" its like could it...is it...nooooo! :D
 
At this point I can't help but think that Verizon has suspended the OTA Rollout. Here is why:

From reading these forums, as far as I can tell the only person to actually receive the OTA update is FoxCow.
He received it in the early morning hours of 5/12. Since then, nobody has received the update (and reported it here). I understand that this is a staged rollout. But a staged rollout is supposed to ramp up. Let's say they got a late start and did not actually start rolling out until midnight of 5/12. Then FoxCow was one of the lucky few to receive it in the first round. But 36 hours later there should be more reports of it. If they are doing a 10x per day rollout (like was reported, 1000 on day 1, 10000 on day 2) then about 10 more people should have reported it. Even if they are only doubling daily, the statistics say that 2 other people should have reported it by now.

My best guess is that a large enough number of the early recipients reported immediate issues (maybe along the lines of the update being completely unsuccessful) and they have decided to suspend the rollout until they figure it out, before they have a riot on their hands.

Hopefully, it is an issue with verizon's distribution method, and they can simply repackage it and try again in the next few days. Worst case would be a previously undiscovered bug in the build and they have to send it back to HTC for a bug fix, another round of testing, and they try this whole thing again a month later.

What do you think? And please correct me, if I am misinformed about the number of people who have received and reported the OTA. If you know of more people with it, please post a list.
 
from the forum, it's my understanding the check sums vary.

if true, can you speculate on the difference in check sums?

thanks,
jim

[pgh. pa., 1.5, no updates (2 erii {wife & self})]

i would say the difference is that the OTA package is built for OTA. it overwrites data. the previous leaks were full flashes that replaces the complete os.

so you have

file1
file2
file3

right

well with this update (ota and v3) out of those only file2 changed.

the ota doesnt include file1 or file3, just file 2. the leak has all the files.
 
  • Like
Reactions: 566
if true, can you speculate on the difference in check sums?

Not sure what you mean by that...
If you mean "what the actual checksum difference is" - well, one byte of code difference can make 2 checksums look radically different. That's the way MD5 checksumming is designed, so you can't tell what's changed by looking at the checksum.

If you mean "what difference in code could cause a change in checksum" we won't know that until someone who's skilled in binary comparison and machine code disassembly looks at the files. It's an educated/skilled person who can reverse engineer the code.
 
  • Like
Reactions: 566
At this point I can't help but think that Verizon has suspended the OTA Rollout. Here is why:

<snip>

My best guess is that a large enough number of the early recipients reported immediate issues (maybe along the lines of the update being completely unsuccessful) and they have decided to suspend the rollout until they figure it out, before they have a riot on their hands.

<snip>

What do you think? And please correct me, if I am misinformed about the number of people who have received and reported the OTA. If you know of more people with it, please post a list.

wouldn't we be hearing from at least someone here, or a source such as bgr/giz/tc/androidcentral that there was a issue?
 
At this point I can't help but think that Verizon has suspended the OTA Rollout. Here is why:

From reading these forums, as far as I can tell the only person to actually receive the OTA update is FoxCow.
He received it in the early morning hours of 5/12. Since then, nobody has received the update (and reported it here). I understand that this is a staged rollout. But a staged rollout is supposed to ramp up. Let's say they got a late start and did not actually start rolling out until midnight of 5/12. Then FoxCow was one of the lucky few to receive it in the first round. But 36 hours later there should be more reports of it. If they are doing a 10x per day rollout (like was reported, 1000 on day 1, 10000 on day 2) then about 10 more people should have reported it. Even if they are only doubling daily, the statistics say that 2 other people should have reported it by now.

I think you may be overestimating how many people on this part of the forum.
 
Back
Top Bottom