What will next firmware release for N900 brings? That is common question asked by too many people. Some of them wants impossible things, some wants magic, some mention realistic things. But what really will be included? That’s other story…

I can write what I found in bugtracker (numbers at the end are internal build numbers):

  • bug 3675: backup will loop nearly infinitely for directories containing pairs of symlinks that do not point to descendants because backup is following them — 2009.47-5
  • bug 3728: Modest reports email username / password incorrect when it is correct — 2009.43
  • bug 3762: Performance is unusable on IMAP accounts with a large number of messages in one or more folders (e.g. INBOX) — 2009.46-16
  • bug 4851: libosso assumes that all ARM platforms has VFP instructions. — 2009.50-5
  • bug 4917: wdgt_va_full_12h_time, wdgt_va_12h_hours should be replaced by wdgt_va_full_12h_time_am/wdgt_va_full_12h_time_pm and wdgt_va_12h_hours_am/
  • bug 4976: Add option in modest to add/not add new contact when replying to mail — 2009.50-7
  • bug 5161: Fix some compilation warnings in GNOME version — 2009.46-16
  • bug 5309: Don’t show “Update All” if no updates are available — 2009.45-14
  • bug 5314: Easy to enter ~ ^ ‘ ` ” symbols with 3rd row of special character view — 2009.44-5
  • bug 5315: 3 Mobile SIM card rejected — 2009.47-20
  • bug 5341: Can’t disable email notification – makes notification unusable if you receive lots of mail — 2009.50-7
  • bug 5343: “More…” applications launcher does’t allow scrolling — 2009.44
  • bug 5347: address book cannot import vcards from benq/siemens phones properly — 2009.47-17
  • bug 5384: Confusing empty window shown after deleting unavailable catalogue — 2009.45-14
  • bug 5388: Allow keyboard input to jump to an entry in a list (“type ahead”) — 2009.51-8
  • bug 5413: microb doesn’t trigger onchange — 2009.46-2
  • bug 5415: Contact widgets move to active desktop after merge — 2009.45-8
  • bug 5493: When ISO sensitivity is set to automatic, ISO EXIF value in resulting image is 0 — 2009.47-17
  • bug 5505: DTMF tones are not sent through SIP — 2009.43-2
  • bug 5518: Bluetooth DBUS UI dialogs – wrong args in the example code — 2009.47-5
  • bug 5523: High latency between UI and SIP events being sent — 2009.45-7
  • bug 5527: Page is not rerendered when JavaScript actions increase page length — 2009.46-9
  • bug 5545: Artifacts (visual noise) when tapping screen in Screen Calibration — 2009.46-16
  • bug 5597: First Synchronization between N900 and Exchange 2003 Server always fails — 2009.49-5
  • bug 5601: libsdl: Task switcher area can be a dead area — 009.47-17
  • bug 5602: IP address field in WiFi advanced settings partially hidden (“Recuperar automáticamente direccíon IP” string too long) — 2009.44-5
  • bug 5603: Vertical photos from other devices should fill more space when shown in portrait. — 2009.43-2
  • bug 5605: “Already at minimum / maximum font size.” not translated — 2009.44-5
  • bug 5607: Call forwarding settings not being saved — 2009.46-5
  • bug 5626: Button style in Bluetooth file receive applet is wrong — 2009.47-5
  • bug 5633: No hint that it is impossible to paste an strings containing non-numeric characters into a phone number field — 2009.44-5
  • bug 5676: Audio does not sync with video (and is ultimately unsyncable) — 2009-44.4
  • bug 5687: “Update” progress bar pane misaligned — 2009.45-14
  • bug 5688: Improve zooming — 2009.46-9
  • bug 5694: Application Manager moves to background after start when quickly clicking — 2009.46-5
  • bug 5725: docpurge is not aware of /opt — 2009.46-7
  • bug 5744: Volume slider doesn’t notice when you plug in headphones — 2009.45-7
  • bug 5761: Bluetooth GPS reconnect dialog refuses to go away after clicking “No” — 2009.47-5
  • bug 5768: Inconsistent layout on similar Sharing/VOIP applets — 2009.45-7
  • bug 5857: Inconsistent keyboard behaviour when configuring a static ip address — 2009.42-7 (not included in 42-11)
  • bug 5868: Games do not respect master volume (“sound effects” enabled though) — 2009.51-5
  • bug 5870: Long emails can’t be read – distorted output on screen after scrolling — 2009.50-7
  • bug 5879: Media player track search only matches the beginning of title/artist — 2009.42-9 (not included in 42-11)
  • bug 5911: Shaking device switches between landscape and portrait modes — 2009.47-9
  • bug 5945: URL proposals in browser disappear after some hours — 2009.50-7
  • bug 5948: N900 needs to be rebooted if media player fails to play video (h264dec) — 2009.45-7
  • bug 5972: Race condition with hardware shift key — 2009.46-7
  • bug 5993: Home view blurs on triple-tapping the launcher grid icon — 2009.47-17
  • bug 5998: Skype does not allow entering DTMF tones — 2009.44-2
  • bug 6004: N900 sometimes ignores USB data cable — 2009.46-16
  • bug 6017: Clicking the dashboard icon highlights it but does not open the dashboard — 2009.51-8
  • bug 6039: Hanging application menu requires system reboot — 2009.46-5
  • bug 6060: Application manager finishing an installation in background blocks keyboard input — 2009.51-8
  • bug 6100: The menu item “copy” in the browser menu does not work — 2009.46-2
  • bug 6107: Background image settings not restored — 2009.43-9
  • bug 6138: Skype Support>Report problem leads to an error page — 2009.47-17
  • bug 6139: skype: Call does not support DTMF tones — 2009.47-17
  • bug 6203: Rotation in 42-11 is not as smooth as in 41-10 for some third party apps — 2009.47-23
  • bug 6261: Delete dialog text missing a space — 2009.42-5 (not included in 42-11)
  • bug 6268: The required #include directives are not documented for Hildon — 2009.51-8
  • bug 6269: Can’t reuse the name of a bookmark that has been deleted — 2009.50-7
  • bug 6349: New email notification leads to blank email instead of email itself — 2009.47-23
  • bug 6361: ‘base’ and ‘more’ applications are visible sametime (messed) — 2009.51-8
  • bug 6470: Charger not recognized when plugged in when in Touch & Key lock — 2009.42-2 (not included in 42-11)
  • bug 6530: Drops WLAN connection to Linksys WRT610N after 10-15 minutes — 2009.48-5
  • bug 6544: USA localization displays distance in kilometers — 2009.49-2
  • bug 6570: Double-tapping “Inbox” sometimes opens ’empty’ Inbox — 2009.46-16
  • bug 6612: File manager fails to show folder sizes beyond 999,9 MB — 2009.45-14
  • bug 6622: nokia messaging doesn’t synchronize selected imap folders — 2009.45-7
  • bug 6669: Browser window checkerboards and repaints when navigated to from multi-task view — 2009.47-5 probably fixed it
  • bug 6675: after failed pairing to bluetooth car kit bluetooth can’t be turned on — 2009.51-0
  • bug 6752: Low power/battery beep does not sound if you’re on a call — 2009.46-5
  • bug 6770: Can’t delete route waypoints in Map application — 2009.47-1
  • bug 6771: Currently active connection should be first in Connections list — 2009.42-7 (not included in 42-11)
  • bug 6792: FM radio transmitter does not play while USB cord is connected — 2009.51-5
  • bug 6807: Wrong default region in E-mail accounts dialog — 2009.48
  • bug 6811: Incorrect entries in the Birthday Smart Calendar — 2009.42-7 (not included in 42-11)
  • bug 6877: Pin / lock code entry dialog reveals digits on backspace — 2009.43-9
  • bug 7027: Changing to next week is very slow — 2009.42-7 (not included in 42-11)
  • bug 7067: gtk-icon-theme-name unset — 2009.43-5
  • bug 7073: Changing password on Exchange 2007 makes MfE go crazy — 2009.42-5 (not included in 42-11)

Impressive list isn’t it? I have to admit that this shows me one thing — integration of Maemo5 in OpenEmbedded will be done sooner then later. Why? Because I want to get such stuff as fast as possible without waiting for official firmware releases.

Will all those bug fixes end in next firmware? No idea as this is not granted:

(Note: 2009 is the year, and the number after is the week.)

A future public update released with the year/week later than this internal build version will include the fix. (This is not always already the next public update.)

Please verify that this new version fixes the bug by marking this bug report as VERIFIED after the public update has been released and if you have some time.

To answer popular followup questions:

  • Nokia does not announce release dates of public updates in advance.
  • There is currently no access to these internal, non-public build versions.

And one more thing — xulrunner 1.9.2 (version used by Firefox 3.6-pre) was tested on N900 and may land in one of next releases (rather not first one).

What will next firmware release for N900 brings?

17 thoughts on “What will next firmware release for N900 brings?

  • 19th December 2009 at 00:17

    Wow, this is indeed very impressive. This is one of the reasons why Maemo is simply great, despite not being “mass-market ready” just yet.

  • Pingback:uberVU - social comments

  • 19th December 2009 at 17:39

    I do wish Nokia did incremental updates “as they are fixed” though.

    I know it has more potential for odd configuration bugs, but its something Linux users have been doing for ions so why is Maemo so different? I do not want to a) have to wait for a full firmware release b) have to completely reflash my root partition, simply to get bug fixes.

  • 19th December 2009 at 21:06

    Alex: I think Nokia will stay with firmware releases, as they put a very strong focus on carefully testing the software they release. Simple spoken: Nokia prefers paying employees and shareholders instead of paying victims of exploding devices.

  • Pingback:Che cosa vedremo nella prossima versione del firmware di N900?

  • 20th December 2009 at 10:28

    nonsupport 3g video call and MMS. Just fix previous firmware bug?

  • 20th December 2009 at 18:24

    I think the list of bugs itself says something about “careful testing”. While some of those bugzilla entries are feature requests, most are defects.

    • 25th December 2009 at 21:27

      Good said cahup!

      Especially when many of feature requests reported in Maemo bugtracker should be done on designing stage. After some days of using N900 I see that designers never ever used phones newer then Nokia 5110/3210 ones (or any PDA).

  • 20th December 2009 at 18:52

    Thanks for that list! Of course bugs.maemo.org is only one feedback channel for Nokia, hence there will be other bugs fixed too, plus the PR1.1 release might include new features too (as portrait browsing was announced at the Maemo Summit)…

  • 21st December 2009 at 02:06

    Some of those bugs have been fixed already but i understand that we will still have to wait until they release a new firmware in a couple of months. That is why i dont understand the comments that say that this is so great about Maemo.

    • 25th December 2009 at 21:23

      Sure, would be nice to have access to packages built for internal builds but I also understand the way which Nokia works.

      What is good in Maemo5 is that most of components are open and their source code is available. This allows anyone to grab sources and build packages. Sooner or later I plan to do some builds for my own use.

  • 22nd December 2009 at 17:29

    What are these “impossible things”? Video call functionality, despite there is front looking camera? USSD menu? MMS? These are the crucial things I can’t find in any roadmap.

  • 27th December 2009 at 07:17

    Some of the things in the list is pointless…I never have any issue.

    • 27th December 2009 at 10:14

      romanianusa: I would not agree with your thinking. For some people those bugs were so important that they reported them. Nice to see them fixed, but the amount of not fixed ones is still high.

  • 2nd January 2010 at 16:49

    I am going to sale my N900 if not support MMS and Vidio call as they still make us legacy.

    Strang, very bad from Nokia again!!!

  • 10th January 2010 at 20:57

    I wish I could get the new update now, as bug 5315 prevents me from using my phone/subscription and no one did inform about this when I bought the phone (quite bad by Nokia), I really wish that there was a way for us normal people to access the updates a lot faster, I can’t just wait 6 months for an update release and pay for a subscription that I can’t use.

  • 12th January 2010 at 12:50

    bug 3675 isn’t actually fixed. a specific victim hacked around the fact that backup is still horribly broken. and in fact these breaks do happen in the real world.

    bug 5343 is not fixed in 51-1, it’s hopefully fixed in the following major update.

    bug 5505 isn’t currently marked as resolved. I’ve had DTMF seem to work sometimes and drop out at other times, so I’d leave it in the “kinda works” state.

    bug 6807 isn’t currently marked as resolved.

Comments are closed.