Eris Users Rejoice!

[xx_bishop_xx]

Thats exactly what it says (time without a signal 50%) wow, insane.

Yes, I was browsing through your phone while you weren't looking.

You may want to give the ole' "Airplane Trick" a try, although I haven't read any solid proof that the 50% without signal is a battery drain at all. I could be wrong, but I just haven't seen it.

 

[Mark16q]

I finally checked for the 50% no signal thing, and sure enough, my phone indicated 50% signal loss.

but my battery life has been 2 days at least, and reception just fine to the best of recollection. So guessing that 50% thing isn't harming my phone....just a weird diagnostic that is probably wrong?

 

[xx_bishop_xx]

I finally checked for the 50% no signal thing, and sure enough, my phone indicated 50% signal loss.

but my battery life has been 2 days at least, and reception just fine to the best of recollection. So guessing that 50% thing isn't harming my phone....just a weird diagnostic that is probably wrong?

It's fairly well-known that the signal meter isn't accurate, not sure about the time without signal. That item is a detail of what is actually using your battery. Not sure about that either though, I don't have a way to quantify that one.

 

[v941726]

mine says time on: 1h 14m 23s

edit: forgot the reboot part. t w/o signal: 51%

phone is 2 weeks old. does this mean i have it?

 

[Mr.Pibb]

Is anyone really getting this update? There seems to be a total lack of "I got it" comments that we usually see. I haven't received it yet.

 

[hallstevenson]

A post over at XDA suspects they may have stopped the roll-out. They push them out in phases to judge any potential issues at a smaller scale vs hitting ALL users of a phone model all at once. It suggests there may be a problem...

 

[el viejo]

As I posted in a related thread, I received the ota update on the 29th. I was on v2.1 leak 3.

My post:

I was on 2.1v3 and received the software update this morning around 7:00am. I'm in North Texas.

Firmware version
2.1

Baseband version
2.42.01.04.27

Kernel version
2.6.29-8a03cb9a

Build number
2.37.605.4 CL 185970 release-keys

Software number
2.37.605.4

Don't have a clue what might have changed. It all seems the same as before the update.

 

[thenestor]

A post over at XDA suspects they may have stopped the roll-out. They push them out in phases to judge any potential issues at a smaller scale vs hitting ALL users of a phone model all at once. It suggests there may be a problem...

Usually they do a small number the first night/morning, then skip a day, then a large number each day after that. Seems they didn't start back up again after the "day off" this time...

 

[mortymouse]

As I posted in a related thread, I received the ota update on the 29th. I was on v2.1 leak 3.

My post:

I was on 2.1v3 and received the software update this morning around 7:00am. I'm in North Texas.

Firmware version
2.1

Baseband version
2.42.01.04.27

Kernel version
2.6.29-8a03cb9a

Build number
2.37.605.4 CL 185970 release-keys

Software number
2.37.605.4

Don't have a clue what might have changed. It all seems the same as before the update.

Any chance that you can post the update? I know a lot of people are waiting and would love to have it.

Instructions for logcat

http://androidforums.com/htc-droid-...ve-12-8mb-ota-update-today-2.html#post1036352

 

[plrock]

Will the update have a fix for speed dial? Since I updated to 2.1, speed dial does not work

 

[Frisco]

Since I updated to 2.1, speed dial does not work

Clear the data from these two areas:

Settings > Applications > Manage Applications > Dialer

and

Settings > Applications > Manage Applications > Contacts Storage

Be sure to re-sync Google stuff afterwards.

 

[el viejo]

Will the update have a fix for speed dial? Since I updated to 2.1, speed dial does not work

According to the first post in this thread, among other things:

"Enhanced Speed Dial"

I did not have a problem with speed dial with 2.1v3. Haven't really noticed anything different than prior to this last OTA.

Sorry, I can't provide the update. I just saw the update notification early in the morning and clicked to install it.

 

[erisuser1]

Can anyone provide a report that "I got it today" (Friday, July 2) ?

or "I got it yesterday" (Thu Jul 1)?

Sure seems mighty quiet around here. Either one of those reports would (sort of) confirm it is still going out.


Berry2Droid, any additional info? Still rolling out AFAYK?

I put my rooted phone on OTA-2.1 a couple of days ago, and .... nothing.

Every time I use my phone for the last couple of days, I am reminded why I rooted. Just seems slooooooooowwwwwwww, and I really miss the HTC_IME mod (speech to text) keyboard.



eu1

 

[v941726]

yeah. not a lot of "i got its". makes you wonder

 

[laurentypo]

So, my husband talked to Verizon today, and they said they have no record of any bug fix updates going out. They told him that they are working on an update, but there is no date for it.

 

[jayochs]

lol, pathetic how nobody seems to know anything. some people have already gotten the update, and verizons saying they never even heard of any updates going out? man, this is just ridiculous.

 

[v941726]

it is weird too how when i was in the local store the other day and playing with a dinc(no pun intended), and i checked the software version and it said v2.1 Update-1...hmmmmm

 

[thenestor]

Every time I use my phone for the last couple of days, I am reminded why I rooted. Just seems slooooooooowwwwwwww, and I really miss the HTC_IME mod (speech to text) keyboard.

I think you can use the htc_ime mod keyboard non-rooted. It has a different package name than the original keyboard.

 

[Hiroshika]

Actually, voice does use 3G and 1x. You're think of 3G data (EvDO).

The issue he's probably having is he's losing ALL signal. The phone will try to drop to 1x but if it's in a fringe/poor coverage area, it will drop anyways.

Could be a defective phone, defective software, or simply needs a PRL update...

This is incorrect. There is not 3G voice on verizon, only 3g data. We still use the 1x network to send texts/make calls. You CANT send a text or make a call over 3G. We have 1x, and evdo. Thats it. evdo = evoloution data only (sometimes optimized)

So therefore, when you take a call or send a text, the phone will switch over to the 1x network.

I know this is probably late, but to the guy he was replying to, your phone is fine, theres no need for a prl update or anything, and your not in a bad signal area.

 

[Frisco]

Every time I use my phone for the last couple of days, I am reminded why I rooted. Just seems slooooooooowwwwwwww..

I hear you; I have a co-worker with a very nicely running 2.1, which also ran perfectly on 1.5, as mine did. She won't root and is happy with it as it is, so we did some comparing:

Both devices shut down and left off for two full minutes, then started (we did not actually time the boot ups), mine was finished for at least 15 seconds before her's was.

First test was hitting "phone" and making a call to my other line, a Blackberry 8330; no speed dial allowed. I had the keyboard up and had entered the entire number and had just pressed the "call" green button just as her keyboard finished coming to the screen.

We performed three tests, but my favorite was the "menu test." All we did was hit "menu" at the same instant on our way through the sub menus to "manage applications" and menu again for "sort by size." It was hilarious, her non-rooted Eris was still doing the original sort, before the icons appear on the left of each app, when mine was finished and I was standing there looking at the sorted by size applications, scrolling down, etc.

"You're cheating," she said, "yous is overclocked."

Yep.

 

[Skyholder]

No update here.

 

[cmajpwc]

No update here either. I'm wondering if, since nobody really noticed a difference, the supposed bug fixes they included in the OTA didn't fix the issues, so they stopped the OTA. I think I read somewhere it was supposed to be completed by tomorrow, well, I doubt that's gonna happen. Oh well, my phone is working fine so it's not like I need this update or anything (unless it takes care of the very little lag I seem to have, of course).

 

[jpzsports]

I hear you; I have a co-worker with a very nicely running 2.1, which also ran perfectly on 1.5, as mine did. She won't root and is happy with it as it is, so we did some comparing:

Both devices shut down and left off for two full minutes, then started (we did not actually time the boot ups), mine was finished for at least 15 seconds before her's was.

First test was hitting "phone" and making a call to my other line, a Blackberry 8330; no speed dial allowed. I had the keyboard up and had entered the entire number and had just pressed the "call" green button just as her keyboard finished coming to the screen.

We performed three tests, but my favorite was the "menu test." All we did was hit "menu" at the same instant on our way through the sub menus to "manage applications" and menu again for "sort by size." It was hilarious, her non-rooted Eris was still doing the original sort, before the icons appear on the left of each app, when mine was finished and I was standing there looking at the sorted by size applications, scrolling down, etc.

"You're cheating," she said, "yous is overclocked."

Yep.

I never knew rooting would make such a performance improvement.

Few questions:

1. What ROM are you using?
2. Is the performance increase due to overclocking only or are ROMs generally faster as is?
3. Since you overclock, do you notice decreased battery life?

Thanks

 

[Frisco]

I never knew rooting would make such a performance improvement.

Few questions:

1. What ROM are you using?
2. Is the performance increase due to overclocking only or are ROMs generally faster as is?
3. Since you overclock, do you notice decreased battery life?

Thanks

You'll notice that (most) rooters have their current ROM listed below their name under "Device(s)" on the left of this page.

Mine is XTR 2.1.1.

There is a noticeable performance increase with most ROMs prior to overclocking. I have done a lot of back and forth testing and have been running Linpack's benchmarks before overclocking and after on several ROMs.

Most differences are well known, and you'll see "mflops" talked about regarding benchmark parameters. "Mflops" are "mega floating point operations per second," and give a pretty good idea how fast your CPU is running, to put it over simply.

I'm regularly getting 4.8 mflops with the XTR ROM overclocked to 710max and 710min. Prior to overlcocking XTR benchmarked at about 2. I got 3.2 on Senseable and 2.6 on Evil Eris, both overclocked at 710.

Battery life seemed to be a bit shorter running at 807 a while back, plus a bit of warmth felt through the case to my hand; that was one of the reasons I tweaked it back, the other being I saw no noticeable speed increase, even though the mflops were over 5 running it high. Battery life now seems about the same as prior to rooting.

 

[scary alien]

I never knew rooting would make such a performance improvement.

Few questions:

1. What ROM are you using?
2. Is the performance increase due to overclocking only or are ROMs generally faster as is?
3. Since you overclock, do you notice decreased battery life?

Thanks

+1 to Frisco's response above. I would like to add a few comments too: many of the custom ROMs are a bit more responsive for even more than just overclocking. The ROM "cooker" (developer) might remove bloatware (that consumes memory and CPU resources), do several optimizations that I won't pretend to fully understand (deodexing, zip-aligning, etc.), as well as supporting the just-in-time (JIT) Dalkit compiler.

You should be aware the the JIT compiler will not make everything faster on your phone. The linpack performance tool does seem to "benefit" from seeing/using the JIT compiler and will therefore report MFLOP scores accordingly (in conjunction with your overclocking, of course). Not everything does or will benefit from the JIT compiler. It is hoped that Froyo 2.2 will make the performance improvements affect a wider-range of applications on the phone.

As far as battery life goes, you actually can go either way on this one. If you have your phone set to overclock all of the time, then yes, your battery life will suffer. You can (and should) use and adjust your overclocking profiles to underclock while asleep or idle. This underclocking will almost certainly give you better battery life than before (it has for me)--even if you are overclocked higher than stock while the phone is in use. Your mileage will vary, of couse, so take the above as my two-cents. [also, if you do overclock, don't forget to put in a temperature failsafe setting so you don't fry your phone].

Cheers!