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

EvDO Rev. 0

I currently have the Droid which is EvDo rev. A, but I don't always have 3G. My signal strength is currently -83 dBm. I'm not sure if that answers any questions. I'm returning my 2nd Droid for the Eris due to other issues.
 
just checked mine, also says Rev. 0. But I just did a speed test with the speedtest.net app, and at a -89 dBm signal strength got the following speeds:
1484 kbps Down, 766 kbps Up
 
"Dialed in" to my phone info and see I'm also on Rev. 0.
I'm in the Cleveland, Ohio area and did the Speedtest run and got 2.42 Mb/s Down & 0.31 Mb/s Up 398 ping although it shows me in upstate Michigan ????? Switched servers to a Toledo, Ohio server and got pretty much the same numbers.
Note that these numbers were done from my work location (NO wireless ... it's turned off on the phone). My home tower must be coated with bird crap 'cuz when I'm there I get the crappy numbers you folks are reporting. Oh, and my work location is in a small city (28,000 pop) outside of Akron,Ohio (20 mi WSW) so it's not like I'm pulling from a major metro area's towers.
Verrrry interesting.

-81 dBm
 
It shows Rev 0 for me too but I think this might just be a display error. I'm in the SF Bay Area and ran a speed test just now:
d/l - 2233 kbps
u/l - 730 kbps

According to this article, my speed falls within the range of EvDO rev A.
What is EVDO? : EVDOinfo.com
 
I will, if anyone can point me to some documentation that says that the data package should be getting 3G .rev A. Otherwise it's like going to a gun fight with a knife.
 
Well I have contacted Verizon about this 3 times now and they keep telling me they will call back with an answer to the situation and 3 times now no call back. I have called every time and they keep having to restart the whole troubleshooting process. So still no answer and I dont think Verizon cares.
 
Let me throw a dagger into the heart of this problem for a second, and point out that the beast lives in the HTC Hero world still.

I don't think this beast was slain before this phone became the Eris. This exact situation exists on the Hero, and Sprint is clear when they say that it just says that, and isn't actually a problem.

Whatever is registering 0 versus A clearly is either not taking input for the difference, not updating what it displays, or is meaningless.

Either way, you ARE getting the fastest communication speeds that your phone can get. You can speed test side by side with a DROID or other smart phone, and find very similar speedtest numbers side by side, wherever you are.

I am personally assuming this to be not a problem at all, and assume 100% that either Android 2.x will "fix" it, or that it will be addressed by that time.

I don't think it's anything to worry about, given that the Hero community has the same "problem" - and it's not really a problem after all!
 
My Eris also shows Rev. 0, but the speeds I am getting on the Eris itself, the Eris tethered to my laptop using PDAnet, and my UM150 data card all indicate Rev. A speeds.

I don't believe Verizon has any Rev. 0 towers left. We travel full time, and I have seen Rev. A speeds everywhere in the western US we have been in the last year.
 
pkopalek said:
Whatever is registering 0 versus A clearly is either not taking input for the difference, not updating what it displays, or is meaningless.
Click to expand...

That might be the best explanation, but it's hard to know. Gnok31's results above seem to indicate that the info display simply does not differentiate between the two.

Have a look at this Wikipedia page on EVDO.

Note a couple things: first, it claims that Verizon's US network is 100% converted to EVDO-A.

Second, and more importantly, note that EVDO-A is superset-compatible with EVDO-0, and that neither one of them guarantee a specific bandwidth - the handset looks at the tower (forward) signal and that info is used to set the modulation format within a single short (1.667 mS) time-slot. Factor in congestion within the cell, and the measured throughput over many seconds might be relatively slow, even if each time slot is modulated at the fastest possible rate (that is, each mobile doesn't get the maximum number of timeslots that it would otherwise get if there were no other users in the cell).

So, measuring a slow throughput over many seconds isn't conclusive as to whether or not EVDO-A modulation/rate is being used - you might just be measuring cell congestion. OTOH, if you have a really good signal, say -73 dBm, perhaps the thing to do is to run your throughput tests at 4am... and only if you have a strong signal - and also only if you are sure the remote server can spit things at you faster than 3 Mbits/s.

I measured a 50 Mbyte download just now - 491 seconds. That works out to roughly 834 kbits/sec - my phone reports EVDO-0. (-73 to -81 dBm).

HTH

eu1


BTW, for what it's worth: I looked at my battery report immediately before and immediately after that long download: 94% starting, 91% ending. This isn't very scientific, but assuming that a fully charged battery could do 33 of those downloads ( 100% / 3% = 33 ), that would be 33*491 seconds = 4.5 hours. That's certainly in the "ballpark" of the Eris' advertised talk time of 3.6 hours; alternatively, if you assume that the Eris' battery has an energy capacity of 5.2 Watt-hours (1300 mAh * 4v), that sort of indicates that my handset was dissipating about 1.2 Watts during the download.

The moral of that story is that a typical WiFi radio in a AP client only uses a fraction of that power - maybe 200 mW or thereabouts.... so, if you can use WiFi instead of the Verizon Mobile Network - you'll save yourself some battery time.
 
You must log in or register to reply here.
Back
Top Bottom