Nokia N97 firmware update 1.1 is live

[Thanks, serie-N.it for the changelog]
firmware posts



For most Pre owners, updates to the operating system happen silently and with little drama -- just the way Palm and the average user likes it. For the more inquisitive of us, though, Palm is offering a detailed breakdown of how the updates get pushed down to the phone and under what circumstances. For starters, you've got to be on EV-DO or WiFi, because 1xRTT (in addition to being ridiculously slow) would block incoming calls when active. Furthermore, you've got to be rocking at least 30 percent of your battery juice. Unless you update manually, the phone will check all by itself every 7 days, and if it finds something, it'll grab it within 2 days during periods when you're not using your data connection (wouldn't want it ruining the user experience, after all). The download typically gets dropped into non-user accessible storage, but apparently, Palm has a contingency plan in place if an update is truly massive -- if that happens, it can steal some user storage with your permission. As we've mentioned, once you have the download, the phone requires that you install it within 7 days; if you don't, it'll auto-install the next chance it gets. Quite a process, isn't it?
We don't have confirmation whether BlackBerry connectivity is in there, but that rumored new firmware release for the X1 is apparently out and about. It's supposed to make the phone generally more responsive -- we always like to hear that -- but you'll also get a brighter keyboard backlight, improved messaging, and better signal strength. In other words, they seem to have hit a bunch of things that we wouldn't imagine could be fixed with a firmware update alone, so we're counting our blessings -- as long as this doesn't think they're allowed to slack on getting that X2 to market, that is.
An incredible way to start the weekend, Storm owners: Verizon is finally pulling the trigger on a firmware update, which will be available to all comers starting on Sunday at 3PM Eastern time. If that's too much trouble, you'll alternatively be able to sit back, chill, and wait for the over-the-air version to hit, which should follow on at 10PM. Verizon tells us that it'll be releasing 4.7.0.148, as rumored -- just a tiny bump from the failed build 141 that had been rumored before that, but all told, far, far too long since the last official update was rolled out. We can only assume this has been tested better than a NASA launch at this point, so you're on notice, guys.
The link appears to have been pulled for the moment, but HTC briefly offered a promising firmware update for AT&T's Fuze that brings a variety of goodies to the carrier's branded version of the Touch Pro. Among other things, you get AKU6, a new version of Voice Command, PTT button reassignability (because -- let's be honest -- not many people are using PTT on this device), an FM radio app, improved TouchFLO performance, and faster GPS locking. Again, the link's currently dead -- but here's hoping it comes back shortly (or at the very least, before the Fortress drops).
After delays, multiple false alarms, and staggered launches, we'll admit: our patience is being tested with this whole Android 1.5 situation on T-Mobile USA's G1, and we imagine there are plenty of users who feel the same way. Previously, it took root access -- a process many lay users would rather not undertake -- to shoehorn 1.5 onto an official carrier-branded unit, but we now finally have a legit, signed build that'll install without any hackery whatsoever. This release will give you all the splendors 1.5 has to offer, preserve myFaves access, and requires little more than a file copy to your microSD card plus a couple key combinations to install, so it's pretty much a must-have if you're tired of waiting for T-Mob to do its thing. Now on to Donut, eh?
So there's a new build of the 9530's firmware floating around; this is pretty much a weekly occurrence and not necessarily anything to get terribly excited about (though we're sure the more enterprising Storm owners out there are going to want to upgrade). Here's the thing, though: we've recently been told by a very well-connected source that Verizon rejected 141 because of one issue alone, and was already testing a replacement for it that was "still in the 140 range." That would mean that it'd have to be somewhere between 142 and 149 -- and yes, fellow mathematicians, 148 meets that requirement. Given the countless delays and the fact that Verizon has already rejected at least two firmwares, we wouldn't count on this happening any time soon -- if at all -- but it's a nice, hope-filled target to shoot for.





