The E90 Communicator hits v300!

Hi all,

Well, the fun just keeps on coming...

I think I may have been the first to send this news to Steve yesterday, and boy do I regret it! I have just spent the last 4 hours at the Nokia repair centre here in South Africa raising hell, and it looks like there is nothing they can do.

The new version will not work with the latest version of Blackberry, and there is no way to revert to a previous firmware. Having spoken with Nokia (and logged a call with Finland) it appears that blackberry will not get any new versions for the E90.

What a horrible situation - our corporate standard across 4000 employees and 76 countries is blackberry, though many people run Nokias because they believe they are superior phones (I was one of those).

It now appears that the new firmware has turned my E90 into a lavishly expensive brick (so I'm with you timsalmon ), as without the corporate solution for contacts, mail, and calendar, it is pretty useless.

Nice one Nokia - 😡

Any advice out of the swamp would be well appreciated.

Cheers,

Mark.

Unregistered wrote:I now compared my N82 running Maps2 side by side with E90 running maps 1.2. The feature they deleted was called Route to and Route from. While I dont begrudge the Maps people making a buck, I think its sneaky offering a feature and then disabling it later (when they realise they arent getting as many subscriptions as they wanted, or anticipated) The dishonesty in this is that, the guy testing the phone in the shop buys the phone with the feature (even possible as a result of the feature. It then gets disabled a year later - essentially breaking faith with the original deal) What aggrieves me even more is Nokia's apparent complicity in this. Or was the deal from the start that they would pull the functionality as soon as Nokia have sold enough of the model and don't need the promise of this functionality to sell the phone anymore? Not good. This is cheating. I, for one, wont upgrade.

Here's how you do it with the new interface:

Click on a point
Select 'Add to route'
Press Options>Show route

Sorted.

NickAnstee wrote:I tried to update my E90 last night, multiple battery in/out cycles etc and it is still broken, I gave up at about midnight. All previous updates have run smoothly up until Wednesday when I was updating my N96, I was prompted to update NSU to the latest version, not sure that has got anything to do with it.

Anyway not sure what to try tonight, I will leave the battery out all day and see what happens. At the moment I get a slight flicker in the screen after the battery in/out cycle and a very faint, non backlit Nokia screen but it doesn't proceed further it goes from 15 min to the battery in/out cycle screen.
Nick

I was having the same problem, and so I moved to a different computer that also had Nokia PC Suite installed, and then I noticed it was a later version of the suite. Whether or not that made the difference, it upgraded my E90 first time. The version that worked was 7.0.8.2 (and the one that didn't was 6.82.23.2).

So check if you need to update the PC Suite.

timsalmon wrote:Yes, tried all the usual S60 tricks. Thanks though.

I do remember Steve L writing about this state-of-phone some time ago where he said 'don't panic' and had some pointers for rescue, but can't seem to track the article down in the forum using the obvious search phrases. Anyone?

Tim

It was http://www.allaboutsymbian.com/support/item/When_everything_goes_horribly_wrong_in_Nokia_Software_Update.php

slitchfield wrote:It was http://www.allaboutsymbian.com/support/item/When_everything_goes_horribly_wrong_in_Nokia_Software_Update.php

No joy, I'm afraid. The logo appears but NSU won't 'find' the E90 however long I wait it seems. Tried all sorts of combinations and repetitions, also on a PC running XP. Looks like if it's awaiting instructions, there's no way to defibrillate.

Thanks anyway for finding the link.

Tim

OK, THE BAD NEWS BITS...

1) No, I was as right as I knew I would be - there is STILL no Video Ringtones, in this Firmware. Nokia, hang heads in shame - I use this to play a movie maker based slideshow of each of my contacts, taht pans between a shot of them, and then a shot of thoer company. A la how my E51 did things, and all the work I put into making these videos in the first place. Oh well.

2) Not sure if this is something new, but now, in my Dialled numbers list, I have an entry for every single call to the same number I make - that is to say, if I call a number, and it is engaged, and I ring it again, and so on, then it is list ten times in my Dialled list. Before, I seem to think (and could be wrong), that it was just listed ONCE, but with a number at the end signifying how many times it was actually dialled. But this could well be wrong, as it's from memory.

3) Geotagging still not built in - so you will still need to download Location Tagger folks. In fact, I am starting to think this new FW is nothing more than a Bug Fix release, barring one or two new items. Certainly Nokia have NOT created it from a "What's missing at the minute, that all the other handsets around it already have" perspective.

3) It's possible they have done something with javascript/java apps in this FW, as I now cannot get the java Applet 'Mail by Google' to work (note: this is simply the individual version for GAFYD users, of the normal Google Mail java applet. I now get the following error, when I try and run it (even after a clean install):

"Network Error: java.lang.illegalStateException: This method is not supported in com.nokia.mid.ui.FullCanvas"

In terms of the Good Points of this new Firmware, it's too early to say, as os far, i notice nothing different, other than the usual clean install speed boost any wipe would do. But I am sure that overall, it's a good thing, this new firmware, right folks...? *lol*

Not noticed anything at all yet, but as the days roll on, hopefully more will transpire.

My upgrade went without a hitch, im on a generic uk mocha product code from the post in the forum (previously 552464). It installed fine first time, no lock up issues at all...

Glad the recent calls list is now showing all attempts, as if you phoned a contact cards house number, then mobile, then went to redial, it would redial the mobile one, and thus your attempt to dial the house number for that card would be obscured in the list...

My gprs seemed a little faster last night, not tried 3g or 3.5g yet...

Although, on a pop3 mailbox, i seem to have an issue deleting emails which i didnt have before. Eg, i cant delete them? Anyone else got that?

Ive also had the device conk out when trying to download catalogues (once in quick office, and once in the download application), which hadn't occured before.

Bluetooth to the pc works fine still, im sure when i sync to the car it will be fine to.

There was a changelog for the last firmware update im sure.

Oh, and the nokia pc suite link was dead as a dodo last night on the UK nokia site. 7.0.7.0 was linked, but file not found. Goto the US site and got version 7.0.8.2 no problems (and at 1.1mb/sec, woohoo)

On a Vodaphone supplied E90, can only be updated to v7.40 😞

Is there anyway around this?

hi steve! just updated my phone with the v300 firmware. can't seem to find any cosmetic change in the music player though...any input on this? all in all, things seem quite the same except for the flip transition which has gotten quicker 😉

shadamehr wrote:OK, THE BAD NEWS BITS...

3) It's possible they have done something with javascript/java apps in this FW, as I now cannot get the java Applet 'Mail by Google' to work (note: this is simply the individual version for GAFYD users, of the normal Google Mail java applet. I now get the following error, when I try and run it (even after a clean install):

"Network Error: java.lang.illegalStateException: This method is not supported in com.nokia.mid.ui.FullCanvas"

I have the same problem. Tried with a fresh install of a latest gmail app, but still the same error. 😞

what do you mean with cosmetic update for music player and new download!
Do you perhaps have a screenshot?

Is is known when the official changelog will appear because I got so many apps on my phone and don't like to update and have some work setting them all up again (even after backup from card some still need to be reinstalled...) but I really want to have the latest version ofcourse

hi Liquid Li0n,

I would stay away from this upgrade - it does very little real in the way of performance enhancement, and it harms more than it heals...

Mark.

I have read here that someone elles has the same glitch as me, flash player has reverted to version 2 since the upgrade and my front speaker has stopped working..... any ideas please😡

If I read all this, especially machone's post, I will just wait for a newer release then the v300

thx already

Another POOR new thing I find, is how it handles text messaging, and the stand-by screen.

Previously, as best I recall it, if you were IN your Inbox, browsing through messages, and you clicked on one of them, and chose to reply, then once your message was sent, the place you got 'dropped back to' was where you were before-hand - namely in the Inbox screen.

On the other hand, if you used a keyboard shortcut for example, to create a brand new text message from scratch, then once it was sent, you got dropped back to the standby screen.

With me so far...?

Well, with v300, I now find that just about everything I do messaging wise, now drops me back to the Standby screen, and this is not the correct methodology.

For example, just now, I received a message from my girlfriend. but being busy, I just clicked the hang up button to get the notification off the screen, and have it wait in my Inbox unread for me.

So when I later now went into the SMS Inbox, I opened up her message, from the Inbox. I then clicked reply. And when it was sent, I got dropped back, NOT into the Inbox, as the previous firmware would have done, but instead, back to the standby screen.

This is NOT Series 60 adopted methodology or correct behaviour?

As I recall it, if a user was in the Inbox folder, and opened a message and replied to it, once sent, you got dropped back to the Inbox folder.

Now, for me at least, I find that if I respond to messages from inside the Inbox folder, I nevertheless now get dropped right to the Standby screen, once it is sent.

Can anyone else test this and confirm if it does it for them please?

But it's mighty frustrating, if you were wanting to respond to a lot of messages in your Inbox, as you get dropped out of it to the Standby screen instead after each response is sent off.

Doh.

There seem to be quite a lot of people experiencing glitches. None of which show up here.

How did you get your data back on? PC Suite restore? Card? I'd love to know, to build up a picture of whct could be going wrong here. Gut feel says that old v210 system files are getting in the way of v300 firmware, but.....

I ain't touching this firmware, what with all the issues. They still haven't fixed the Call Log Icons. All calls in the recent call lists will be shown as a mobile call (the icons anyway) and it really bugs the hell out of me to have to go into contacts and find the correct number to call (did I call him on his fixed line or his mobile line first 3 hours ago ... hmmmm)

slitchfield wrote:There seem to be quite a lot of people experiencing glitches. None of which show up here.

How did you get your data back on? PC Suite restore? Card? I'd love to know, to build up a picture of whct could be going wrong here. Gut feel says that old v210 system files are getting in the way of v300 firmware, but.....

Steve,

It's not so much GLITCHES that I am seeing or reporting, but feature changes for the worse, or problems that arise.

Such as:

1) Change of java somehow so that the java "Mail by Google" application no longer works (this simply being the same as the java Gmail app, but the one made for GAFYD users).

2) Reply to a message, and now you get dropped back to Standby screen once it is sent, rather than the Inbox where you last were, as for all other Symbian phones, and the prior firmware.

3) Huge battery drain compared to prior firmware - no idea what or why, it's just going down fast fast now.

And whatever other ones I have reported during this thread, that I may forget.

In terms of how I backed up, I did this:

1) Sync'ed contacts using the Switch utility, over to a clean N82.

2) Did the firmware update on the E90, leaving it out of the box clean.

3) Sync'ed my contacts back over from the N82 via BT, using the Switch utility again.

4) Set up manually, all my settings, menu layouts, tones etc.

5) Manually installed those couple of apps, that did not self install straight from memory card. That is to say there weren't many installed anyway.

So overall a pretty clean way of doing things, minus the odd app. already on the card, such as Google Maps.

Hope this helps.

Does anyone else gets an error message when trying to start the java gmail client software?

regards,
jeran

Jeran wrote:Does anyone else gets an error message when trying to start the java gmail client software?

regards,
jeran

Erm yes...

The guy in the post immediately before yours - namely ME.

Just like I said *lol*

Albeit, for me, it's the "Mail by Google" java app, not the "Google Mail" one, but it's simply the same thing, but the version for custom domain GAFYD users.

The only resolution, from all the research I have done, is an update to it, by Google themselves, as it seems this "update, so fix" cycle seems to have been running since the 6630 days.

Alternatively, if you can find somehow, the actual .jar file itself, you can do a manual install using that, as it's only the self-contained symbian installer java download that fails. Apparently, if you find a link for the base .jar file only, you can install that, and then it does work.

I have no chance of that, needing the "Mail by Google" .jar, but you might have more luck, only needing the standard "Google Mail" .jar file

Just want to say what was my experience..

Upgrading from 210 to 300 went wrong the first time.. It said to remove the battery and try again. Second time it worked just right. Got my backup on my SD card and restored it in a minute or so.

Switching screens is faster now but i must admit i feel as someone else did that battery life is shorter now. don't know why.. i'll try to test it better.

i don't experience problems when replying an sms. when sent, i just find myself back in my inbox folder!

as others said, flash now says v2, don't know why!

I'm an italian user with italian nobrand moka e90.

I want to update the firmware to the v300.34.84 but the Nokia Software Updater shows the following:

Nokia E90 (RA-6)
Firmware version
Current:7.40.1.2
Update:7.40.1.2

Therefore I cannot update to the latest firmware. Not even the 210.43.75.
Anything I do wrong? I have updated it before from the 7.24.... Thanks, Sandra

Hi,

Some of you may have been reading my posts in this thread, and I thought I would post to let all know how the saga ended.

Since blackberry connect not working for me is a complete show stopper (my company would require that I get another phone and trash the E90), I had only two choices:

1. Get a newer version of blackberry.
2. Revert to a previous firmware.

Regarding (1), I logged a call with Nokia, and received a response from finland via our local Nokia centre to this effect: it is unlikely that there will be a newer blackberry release, so either live with the new firmware and no blackberry or downgrade to an earlier firmware!. (I did not think this was possible).

This left me with no option but (2), so I took the phone to a nokia care centre, and instructed them to downgrade the firmware, but not before telling them that if they killed the phone, I would expect it to be fixed or replaced.

Sure enough, on trying to revert to the 210 firmware, they killed the phone. I expect either my existing phone back with 210 firmware, or a new phone, today.

Having lived with the new firmware for a few days, I can honestly say that there is nothing tangible contained in it which makes it worth the upgrade, and in fact it seems to introduce a whole new set of bugs and issues which were not present in the very stable 210 version.

If you had upgraded to Maps 2, via download, then you will have the same version that is included in the new firmware, and all of the performance gains mentioned in the forum are so minor that the could easily be a consequence of reflashing the phone and "starting over."

I am at a loss for words at Nokia's actions in removing support for Blackberry: I can understand them not doing any future development, but removing support for existing users is in extremely poor taste.

Clearly Nokia are moving in the direction of direct support for MS Exchange as a corporate solution (see the press release here) but they could have kept existing users happy whilst doing so. An absolutely fundamental flaw of "Mail for Exchange" is that it requires a corporate exchange server to be exposed to the internet, and no corporate IT department in its right mind would allow that.

So, in summary, my message to Nokia is:" How can such a brilliant company make such an incredibly stupid decision?":con?

Regards,

Mark.

Woh... just a minute...

I was minded to post right at the start, setting a few things straight, but held of. Now however a little "Balance brought to the Force" might be called for.

I fully sympathise with your frustrations, but I see things in a VERY different light to you.

You see, your issue is very much like my issue relating to Gmail Java App no longer working.

So let me indicate a few things...

Why these relevant applications are not working, are on a fundamental level, simply because of changes in the firmware. At a very base level this could be something entirely as simple as the actual version NUMBER itself being reported to the relevant application (in your case Blackberry Connect). This, after all, being how Firefox add-ons are often restricted when a new update to Firefox comes out, and the ONLY thing stopping existing apps working, is the fact that they are hard coded to a version number - not at all for any actual compatibility issues.

So whatever the case, whether it be because of something as simple as a version number change, or because of any actual changes to code in the firmware, nevertheless, we have to accept that this can be the consequence of new firmware.

And from various forums I have read, and items I have googled, this has indeed always been the issue with Blackberry Connect software... when a new Firmware comes out, a new version needs to be written - clearly one hopes, as soon as possible.

Now, this is where things get a bit more vague... The software you refer to... well for me, I find it listed on the RIM site, as if RIM were the author, not Nokia.

And if that is the case, then the onus is on RIM to release a newer version, not Nokia.

But if RIM are merely hosting this app on behalf of Nokia, then nevertheless, I am not for one single second convinced that even a call-back from Nokia Finland telling you that there will be no more versions of it, is anything at all likely to be true.

You clearly say yourself that vast amounts of people rely on this. And let's face it, this is not an N series device - this is the Flagship Nokia Enterprise users device here, the E90, so the very device one would expect Blackberry Connect users to use.

So one call, no matter how high ranking, from Finland, does absolutely NOTHING to convince me, even if it IS Nokia who have the right to answer the question and not RIM, that there will really not be another version.

It sounds far to implausible to be true.

So summarising:

1) Unfortunate the end result is (for both of us, in our own ways), this is a fair and understandable outcome of a new Firmware update. That is to say, that it means a new version of the apps we both need, need to be produced.

2) It is not clear entirely to me, that Nokia even have the right or ability to tell you there will be no more Blackberry Connect, as I always thought this was for RIM to release. But even if that is not the case then see (3) next...

3) Even after a high level call-back from Nokia Finland, assuming they even are the ones to issue the software, then I am anything but convinced that there will be no more Blackberry Connect software for the E90 - the Flagship Nokia Device for Enterprise Users, with a qwerty keyboard.

So I think there are a few errors in the story. Though of course, let me be CLEAR - your suffering is far more than mine, if you rely on Blackberry Connect for your email, I readily understand that. My loss of the Gmail Java app is a mere inconvenience by comparison.

And in terms of the benefits this new Firmware brings, I'm minded to be with you here, in that I don't really make use of Flash that much etc, so the apparent cons, outweigh the pros, for me.

But for many or even most, the new benefits will likely outweigh the downsides, one would think.

Whatever the case though, I hope you get your issue resolved soon, and be sure to keep us updated as to what results mate...

Very quick question:

is anyone of you getting the right Flash Lite version? (v3)?

Mine seems stuck to v2.0! I'm getting this info by entering the flash player in the multimedia menu and then selecting the about menu.

Also, when playing youtube videos, seems slower than before!

Thanks

HI Iposted above on the same topic but no response:con?

I just saw Nokia site has a new bb connect sw.

Nokia S60 BlackBerry Connect 4.0 vers. 8.23.1(.SISX, 2,89 MB)

NOTE: You need software version 300.34.84 on your device. This client is for BlackBerry Connect 4.0. You may use the BlackBerry Connect Desktop software for your PC (see below) to provision your phone but it is not necessary because BlackBerry Connect 4.0 is able to perform Over The Air Enterprise Activation.

reading the description it says it is for 300.34.84

Let us know if this works with the 300.34.84

The link is at businesssoftware.nokia.com/blackberry_downloads.php

This is a very good piece of news! Anyway, sorry if i insist on this, is anyone getting FL3.0!?:frown:

How can you tell? The Flash Player in 'Media' isn't the same thing. Flash Lite 3 is something that's more low level, as I understand it.

I've always thought that FL and Flash Player were the same thing, sorry for my misunderstanding!