Hasta La Gadget!

Not to be outdone by its Samsung successor, the Nexus One’s getting a miniature over-the-air update as well, sending users on a mind-bending ride from Android 2.2.1 (version FRG83D) to the FRG83G build of Android 2.2.2. When they emerge thoroughly dazzled and confused on the other side, what will they find? We spoke to Google and it’s just a few bug fixes, but one of them’s rather important — this update will go down in the annals of history as the one that doesn’t inadvertently send humorous texts intended for your co-workers to your deathly serious boss. Oh, and if that sounds like something you’d like to have immediately, rather than waiting for a formal rollout, you can find the file you need at Google’s servers right now.

[Thanks to everyone who sent this in]

Nexus One gets tiny update to Android 2.2.2, fixes SMS routing issues originally appeared on Engadget on Sat, 22 Jan 2011 17:18:00 EDT. Please see our terms for use of feeds.

Permalink Android and Me  |  FRG83D update (Google)  | Email this | Comments

So it’s been a fun day of armchair code forensics and legal analysis on the web after Florian Mueller published a piece this morning alleging Google directly copied somewhere between 37 and 44 Java source files in Android. That’s of course a major accusation, seeing as Oracle is currently suing Google for patent and copyright infringement related to Java, and it prompted some extremely harsh technical rebuttals, like this one from ZDNet and this one from Ars Technica. The objections in short: the files in question are test files, aren’t important, probably don’t ship with Android, and everyone is making a hullabaloo over nothing.

We’ll just say this straight out: from a technical perspective, these objections are completely valid. The files in question do appear to be test files, some of them were removed, and there’s simply no way of knowing if any of them ended up in a shipping Android handset. But — and this is a big but — that’s just the technical story. From a legal perspective, it seems very likely that these files create increased copyright liability for Google, because the state of our current copyright law doesn’t make exceptions for how source code trees work, or whether or not a script pasted in a different license, or whether these files made it into handsets. The single most relevant legal question is whether or not copying and distributing these files was authorized by Oracle, and the answer clearly appears to be “nope” — even if Oracle licensed the code under the GPL. Why? Because somewhere along the line, Google took Oracle’s code, replaced the GPL language with the incompatible Apache Open Source License, and distributed the code under that license publicly. That’s all it takes — if Google violated the GPL by changing the license, it also infringed Oracle’s underlying copyright. It doesn’t matter if a Google employee, a script, a robot, or Eric Schmidt’s cat made the change — once you’ve created or distributed an unauthorized copy, you’re liable for infringement.*

Why does this matter? Because we’re hearing that Oracle is dead-set on winning this case and eventually extracting a per-handset royalty on every Android handset shipped. In that context, “those files aren’t important!” isn’t a winning or persuasive argument — and the more these little infringements add up, the worse things look for Google. Whether or not these files are a “smoking gun” isn’t the issue — it’s whether Android infringes Oracle’s patents and copyrights, since the consequences either way will be monumental and far-reaching. Ultimately, though, the only person who can resolve all of this for certain is a judge — and it’s going to take a lot more time and research to get there.

—
*They’re not directly comparable, but think about the Psystar case for a second. Even though Psystar desperately wanted to argue that Apple’s OS X license agreement was invalid, the judge never got there — he simply ruled Psystar wasn’t authorized to copy and distribute OS X, and swung the hammer. It really is that simple sometimes.

Android source code, Java, and copyright infringement: what’s going on? originally appeared on Engadget on Fri, 21 Jan 2011 19:15:00 EDT. Please see our terms for use of feeds.

Permalink   |   | Email this | Comments

Wow, insider tipsters are getting efficient! Verizon appears to have only just added Minimum Advertised Pricing for the Motorola Xoom to its internal systems, but already it’s been leaked out by more than one source. Android Central has the damning evidence, which lists an $800 levy for any prospective owners of the flagship Android Honeycomb device. It’s accompanied by a listing of the HTC Thunderbolt at $250, with the logical conclusion being that the Moto tablet will come unsullied by subsidies while the HTC LTE handset will probably cost that much on a two-year deal. That makes plenty of sense to us — the typical smartphone price is $200 and Verizon can point to the 4G goodness the Thunderbolt brings as justifying its $50 premium, whereas the Xoom’s cost seems to be in line with the Galaxy Tab’s pricing. Now, how about some launch dates, leaksters?

Motorola Xoom priced at $800 at a minimum, according to Verizon leak originally appeared on Engadget on Fri, 21 Jan 2011 18:41:00 EDT. Please see our terms for use of feeds.

Permalink   |  Android Central  | Email this | Comments

Well, it’s about time! We knew Sony was prepping some Reader apps to go along with its physical Pocket, Daily, and Touch Edition e-readers, and while it may have missed that December release date, the Android version of the app is now available in the Market. The free app is pretty much what you’d expect — you can log in with your username and it automatically syncs previously purchased books, and like the e-readers, it also supports ePub and PDF formats. In addition, you can easily highlight text and adjust font and brightness settings right from the page you’re reading. We downloaded the app and found it to be pretty decent, however, the Store shortcut launches within the browser rather than in the app. Ready for the twisted part? Sony has confirmed for us that the app will only work with handsets that run Android 2.2 and higher, which is incredibly ironic considering most Sony Ericsson handsets are, you know, still stuck with 2.1. Of course, it looks like that PlayStation Phone will work just fine when it’s finally released, but that’s neither here nor there — hit the gallery for a pile of screenshots of the app.

Updated: Sony just let us know that the iOS version is still pending Apple’s approval, but it should be available soon.

Sony Reader app finally available for Android, only works with 2.2 and higher originally appeared on Engadget on Fri, 21 Jan 2011 15:55:00 EDT. Please see our terms for use of feeds.

Permalink   |  The Digital Reader  | Email this | Comments

As promised, it seems that T-Mobile’s version of the Vibrant is getting Froyo today after a brutally long wait. The good news is that you won’t need to wait for a staggered rollout, apparently — but the bad news is that currently you’ll need to get it using Samsung’s Kies Mini PC app, not over-the-air. Tethered updates are always less convenient than their OTA equivalents (though Samsung continues to be particularly fond of them), and in the case of Kies Mini, there’s no Mac version, so you’ll need to be near a Windows machine to make it happen. This hasn’t been officially announced yet, though commenters over on TmoNews appear to be having luck — so if you give it a go, let us know how you fare.

Update: T-Mobile’s official FAQ on the update is up — so yeah, it’s official!

Samsung Vibrant’s Android 2.2 update now available, it seems (update: official) originally appeared on Engadget on Fri, 21 Jan 2011 15:34:00 EDT. Please see our terms for use of feeds.

Permalink   |  TmoNews  | Email this | Comments