No, they have an, apparently, quite nice internal tracker that is well triaged and managed (you can see references to internal tickets in the Alias field). My point is that a "high" priority on bugs in bugzilla don't necessarily reflect the bug priorities on the internal tracker. Many bugs have submitter-set "high" priorities, which have nothing to do with any real priority.

See bug #630 for some background, but Andre has been working his way through the entire almost-4000-bug bug-list and triaging each and every one of them (which includes linking them to internal bugs and reporting back any relevant information from them), and working on changing the way Nokia engineers do business with relation to bugzilla. So while things are looking up moving forward, a "high" priority in bugzilla shouldn't necessarily be taken as an indicator of any internal priority.

Apparently the tinymail threads are crashing for some reason or another, it's being worked on and some of the fixes should have made it into the svn. johnx compiled it yesterday, and I'm certain he'd be willing to share a binary if you asked.

rtcomm was upgraded with Diablo, just the Telepathy plugins didn't make it in. I hear this could've had something to do with Nokia not having talked to those providers yet. Not really sure, though.

I personally don't have a lot of problems with volume and VoIP, but, yeah, the volume as a whole for the entire platform is a little low for what the hardware is capable of.

This one has been covered a lot already. But I'll explain it again here. Major code changes are frozen 2-3 months before the release, and merging with the latest Firefox code is a non-trivial task, which means there was not enough time to merge with one of the RC releases (and definitely not with the final release) and the code that was available to make the timeframe simply wasn't worth "upgrading" to. Unfortunate, yes, but those are the facts.

Now, from what I can tell a lot of the big Diablo bugs have been fixed internally, so if you want try your luck with the svn (which, actually, I think was merged with trunk a week or two ago) I'm sure you'll find it to be quite a bit nicer (probably want to install osso-software-version-rx*4-unlocked for the non-strict dependencies, first, though).

Yes, that's why the AGPS support is beta, and doesn't ship with Diablo. . . .

Is that top consumption? Because top consumption is entirely meaningless. Install htop and get back to me on that one.

Yes, icd underwent a fairly significant upgrade (WiMAX stuff) and didn't seem to get enough testing before it hit release. Saved connections seem to be a problem, and it sometimes crashes out and the GUI wont be able to reconnect to it for some reason.

. . . and yet, I've found Diablo to be a net positive overall. Application manager is much more usable, overall system stability is improved here, virtual input methods are much more consistent system-wide, and much of the phantom typing in the fkb and vkb seems to have been eliminated.

The thing to keep in mind for Diablo, though, is SSU. The good news is that a lot of the issues seem to be getting fixed internally, and all that's needed is a couple of SSU pushes to get them to us (well, or you can try out the svns for the open stuff if that's your thing)—no waiting 4 months for another big firmware release.