I haven’t yet upgraded and am usually a “wait and watch” person. I think the key issues I look for before an upgrade are:

1. Is this upgrade really worth it? What does it do - faster? better support for an application I use? just for kicks?

2. Does the new firmware support existing applications? For instance, blackberry connect usually takes a couple of days before putting up support for new firmware. I don’t want to be in a position where I have new firmware but can’t load blackberry - I think admin has already pointed this out.

3. Does the new firmware kill an existing good application or feature. For instance, I have got my phone to have two simulteneous active connections (basically blackberry and internet at the same time), but I don’t know/ remember how I did it. I don’t want to have to reinvent the wheel on the new version - so until someone confirms that two connections work or tell me how they work, I don’t think I want to upgrade. Any help here guys?

4. General problems - This blog is usually updated with problems people are having so I make sure I update myself with that. Disconnection seems to be a problem with the new firmware for some. So need to be sure we are in a trouble free environment to upgrade.

5. Finally, I look to see if the new firmware issues resolved list is of any use to me. This could make a compelling decision to upgrade. You will find that several annoyances are eliminated. Often “make or break” upgrade decisions are taken by me on this basis.

Seems quite scientific? It’s not. Finally it’s the gut feel - should I or should I not. Presently I think it’s a NO for me principally because the firmware doesn’t seem to be faster than the previous one. I upgraded by E65 because it was slow and it really sped up my navigation experience. I don’t see that happening for E61i, so until that happens .. it’s still version v2.0633.65.01 for me!!

I am not doing any hasty update again, ever… and planning to revert to the dual band which gained popularity 5 years ago so I will not be tempted of upgrading any software.

Jean, I am in New Zealand - and I just took my phone back to the shop I bought it, they are going to send it away, apparently its just a simple software problem and is likely to only cost $45. It will come back completey formatted but luckily I backed up.

Dont think I’ll be doing a firmware upgrade again in a hurry..

Halfway through the upgrade process, my cellphone was “disconnected” from the PC even when the indicator lights said otherwise.

Now, Nothing is displayed…only the white indicator light. Anyone who knows what I should do to remedy this problem? I am in the Philippines by the way.

http://martinletis.blogspot.com/2008/02/nokia-maps-download-links.html

I thought I read that the 0538563 Product code has the same keyboard layout as the 0541667 code on another thread. It also supports the latest firmware.

I’m not so much interested in going to the latest software but seeing if I can get UTMS support working. I have the 0541667 code and from all the threads I’ve read it doesn’t support UTMS because of something in firmware version of that software. Figured I’d try changine the product code and firmware to see if it fixed the problem as long as the keyboard layout was close.

Anyone have:

Top row: Q! W% E$ R1 T2 Y3 U* I- O+ P=
Sec row: A~ S( D) F4 G5 H6 J# K_ L&
3rd row: Z X C V7 B8 N9 M0 ,; .:
Bot row: /’ @” Space ?^

(Second Char “Blue” or “Shift”)

As a keyboard layout or something close WITHOUT product code 0541667? I don’t care if it’s an exact match since I can just use the “Chr” key to for things like the “$” symbol.

I have a phone from Hong Kong that I changed to use in the US. I’ve upgraded the firmware in the past to 2.x. And had the Key’s remapped to work for US.

The problem now is that the phone won’t turn on past the white indicator light. I have nothing coming up. The firmware failed and I have nothing. I don’t care if I have to reset the phone or whatever, but I can’t even get anything to show up to even attempt this. Any help would be GREATLY GREATLY appreciated!

Thanks,

Gary