I'm posting this to ***** about my experiences with a new Nokia E61, and possibly to get some feedback about fixes. Seems that info on the E61 is scattered all over the place.
Bottom line: Nokia could have delivered a truly remarkable device, but instead delivered something with quirks and idiosyncrasies such that I'm seriously thinking about returning it in the limited time I have left to do so.
There is a lot to like (or potentially like) about it - I love the GUI overall. I love the hardware. I'd rather have Symbian than PalmOS (dead end, it seems, even though I'm a real Palm fan) or Windows Mobile (tried it, hated it). Love the support for attachments, Office type apps, etc.
This might be a good faq-type-thread, unless no one else is having the same issues that me and my biz partner are both experiencing (doubtful, as we've seen other users have the same issues in postings all over the place). Then again, if you're not, I'd love to know why.
We're both on the latest, 2.x firmware.
Email
-----
The imap client is just plain busted. It crashes on some imap servers (Dovecot), and it doesn't work according to common imap standards and conventions - sent mails are not autoforwarded to your sent box, it doesn't work with "custom" imap mailbox hierarchies, etc.
Worse, the IMAP client "hangs" after a fairly short amount of time. Has something to do with bad IMAP standards implementation.
The pop client works, but it feels the need to mark messages as being read even if you're only retrieving headers.
The auto-retrieve system hangs up after running for a while, pretty much ensuring several reboots every week.
We bought this thing primarily because it had IMAP/POP support. Third party stuff like Profimail works, but is not integrated with the phone very well.
Bluetooth
---------
I consider my old SE T610 to be a "default standard" for bluetooth headsets and hands-free. It worked great, was highly configurable, etc. Given that since the T610 is so old at this point, I'd expect any new phone to do at least as well.
Nokia bluetooth for use with headsets is pretty much busted on all Nokia phones - unlike every other phone maker, a Nokia phone wants to connect to your phone all of the time. My 6230i works the same way - everything is routed to the headset, all of the time. Other phones tend to make use of the full capabilities of the device, and allow you to connect pretty much on-demand.
The bluetooth connection sometimes just drops for no obvious reason. This makes answering calls unreliable.
GUI
---
Cut and paste is not enabled in all apps. Most of the time you have it, but it is not available in a few key areas like for configuring connections and the like.
Wi-fi
----
Certain hot-spots may, depending upon unknown factors, cause the device to "white screen". Starbucks hotspots seem to be offenders, but there is no consistent cause and effect.
"SIM Registration Failed"
----------------------
In certain marginal reception areas, the phone gives you this message. A lot. If you use the subway or other trains a lot, be prepared for this.
It also seems to cause the time to reset to a previous setting. Not good for keeping appointments.
Voice/Reception quality
-----------------------
This is subjective, and I'm somewhat down on the device, but it seems below-par.
Firmware issues
---------------
Not as much as a complaint, as you kind of have to assume that you'll have issues with any "grey market" device, but Nokia really makes it especially tough.
I bought my phone from J+R, a supposedly reputable dealer. The phone came with older firmware. It worked as expected.
When I updated, I was surprised to find that non-alphanumeric keys all mapped to Arabic. Great! My biz partner found a "fix" that cannot be repeated here due to forum rules; Nokia's help forum is similarly constrained.
Nonetheless, I really believe that Nokia needs to do something to avoid this type of a mess. It is fixable with enough time and research (and the fix would scare the hell out of grandma) - this is a business/distribution/support issue, not a technical one.
My $.02. Would love to hear responses, especially if anyone has fixed some of these flaws (or knows of a forthcoming firmware update).
Thanks!
Bottom line: Nokia could have delivered a truly remarkable device, but instead delivered something with quirks and idiosyncrasies such that I'm seriously thinking about returning it in the limited time I have left to do so.
There is a lot to like (or potentially like) about it - I love the GUI overall. I love the hardware. I'd rather have Symbian than PalmOS (dead end, it seems, even though I'm a real Palm fan) or Windows Mobile (tried it, hated it). Love the support for attachments, Office type apps, etc.
This might be a good faq-type-thread, unless no one else is having the same issues that me and my biz partner are both experiencing (doubtful, as we've seen other users have the same issues in postings all over the place). Then again, if you're not, I'd love to know why.
We're both on the latest, 2.x firmware.
-----
The imap client is just plain busted. It crashes on some imap servers (Dovecot), and it doesn't work according to common imap standards and conventions - sent mails are not autoforwarded to your sent box, it doesn't work with "custom" imap mailbox hierarchies, etc.
Worse, the IMAP client "hangs" after a fairly short amount of time. Has something to do with bad IMAP standards implementation.
The pop client works, but it feels the need to mark messages as being read even if you're only retrieving headers.
The auto-retrieve system hangs up after running for a while, pretty much ensuring several reboots every week.
We bought this thing primarily because it had IMAP/POP support. Third party stuff like Profimail works, but is not integrated with the phone very well.
Bluetooth
---------
I consider my old SE T610 to be a "default standard" for bluetooth headsets and hands-free. It worked great, was highly configurable, etc. Given that since the T610 is so old at this point, I'd expect any new phone to do at least as well.
Nokia bluetooth for use with headsets is pretty much busted on all Nokia phones - unlike every other phone maker, a Nokia phone wants to connect to your phone all of the time. My 6230i works the same way - everything is routed to the headset, all of the time. Other phones tend to make use of the full capabilities of the device, and allow you to connect pretty much on-demand.
The bluetooth connection sometimes just drops for no obvious reason. This makes answering calls unreliable.
GUI
---
Cut and paste is not enabled in all apps. Most of the time you have it, but it is not available in a few key areas like for configuring connections and the like.
Wi-fi
----
Certain hot-spots may, depending upon unknown factors, cause the device to "white screen". Starbucks hotspots seem to be offenders, but there is no consistent cause and effect.
"SIM Registration Failed"
----------------------
In certain marginal reception areas, the phone gives you this message. A lot. If you use the subway or other trains a lot, be prepared for this.
It also seems to cause the time to reset to a previous setting. Not good for keeping appointments.
Voice/Reception quality
-----------------------
This is subjective, and I'm somewhat down on the device, but it seems below-par.
Firmware issues
---------------
Not as much as a complaint, as you kind of have to assume that you'll have issues with any "grey market" device, but Nokia really makes it especially tough.
I bought my phone from J+R, a supposedly reputable dealer. The phone came with older firmware. It worked as expected.
When I updated, I was surprised to find that non-alphanumeric keys all mapped to Arabic. Great! My biz partner found a "fix" that cannot be repeated here due to forum rules; Nokia's help forum is similarly constrained.
Nonetheless, I really believe that Nokia needs to do something to avoid this type of a mess. It is fixable with enough time and research (and the fix would scare the hell out of grandma) - this is a business/distribution/support issue, not a technical one.
My $.02. Would love to hear responses, especially if anyone has fixed some of these flaws (or knows of a forthcoming firmware update).
Thanks!