Android 2.0 SDK Released, Google Maps Navigation Announced

stoolpigeon writes "The Android 2.0 SDK is now available from Google. This puts to bed concerns about Google not releasing the SDK or perhaps being in some kind of exclusivity deal with Verizon around 2.0. The release notes give a nice overview of what is there. Those who already have the SDK can grab the updated tools as SDK components; everyone else will pick up everything when downloading the new SDK." Relatedly, reader riffzifnab reports that Google has also announced Google Maps Navigation, a GPS application for Android 2.0 that takes voice input and integrates with internet searches and Street View.

Re:Search on your route is a great feature

[goaliemn]

It will download the data along your route, so you're good if you loose connectivity while going to your destination.

Its not the entire google database, but its a nice start.

Re:Search on your route is a great feature

[Anonymous Coward]

Google is already using their own map data (at least for US). They dropped TeleAtlas recently and NAVTEQ a year ago. In any case, they are well positioned to be a strong competitors to traditional navigation companies as well as cellphone manufacturers (NOKIA).

Re:Search on your route is a great feature

[Sparr0]

There are already PDA map applications that pre-download google maps at multiple zoom levels along your planned route.

http://fragostech.com/MaemoMapper/ [fragostech.com]

Re:droid will be mine

[Zerth]

You just need somebody to port GPSdrive or one of the other linux GPS programs and precache the maps along your route.

I don't have a linux-based phone, but I've done that on my EEE for all the regions in nearby that have crappy signal.

Open Handset Alliance

[Enderandrew]

Google does not control Android. Google can't singularly hold back an Android release. Google can't sign an exclusive deal where only one carrier gets an Android release.

Android is FOSS that is owned by the Open Handset Alliance.

Google offers various versions of Android to carriers with differing levels of Google branding, but given that the entire trunk is open to developers, AT&T has the same capability of obtaining Android code as Verizon, or any theoretical carrier.

Re:droid will be mine

[virtualXTC]

This has already been done in the AndNav1 project [andnav.org]. Unfortunately, due to licensing terms google forced them to stop development. Now they are useing open street map instead.

Re:Send route from computer to phone?

[virtualXTC]

This is available via AndNav [andnav.org] and OpenStreet Maps [openstreetmap.org] via Open Route Service [openrouteservice.org]. Sadly, development for USA navigation has been slow or non-existent despite my donation to the project.

Re:Not releasing?

[stoolpigeon]

This line from the article, "There is some speculation that Google has made an Android 2.0 exclusivity agreement of some kind with Verizon." seemed to me to imply that the sdk was not coming out because Verizon would have exclusive rights to 2.0. This seems to be supported by the fact that they now note the release of the sdk immediately after that line in the article.

I bumped across that article while reading comments yesterday in the Maemo vs. Android thread [slashdot.org].

Re:droid will be mine

[InakaBoyJoe]

In Japan, phones have been capable of turn-by-turn navigation [navitime.co.jp] for a long time. When those apps first came out, there was a lot of speculation about whether mobile phone navi would kill the standalone / built-in navigation market. The car navi folks rushed to add mobile data connectivity, so they could download the latest maps and service info [g-book.com] to compete with the "live" services offered by the mobile phones. Accessories for mounting your phone in the car in a visible position also became available.

In the end, both devices are co-existing in the market and very few people use the phone as the primary navigation device. Reasons are: (1) Inconvenience of having to launch the app, mount the phone in the car (or kill your phone's battery), and the fact that you can't use your phone. (2) Screen size. Unlike the tiny screens on North American GPS navi units, almost all units in Japan have a 5" or 7" screen. (3) The fact that most cars already have it built in anyway.

So I predict that in North America, the GPS navi units will evolve to: (1) Larger screens, (2) Data connectivity for live updates, and (3) More specialized features and improved service quality. The competition will be good. But the standalone / built-in navi devices won't just disappear.

Re:Hardware requirements for 2.0

[darthyoshiboy]

The guys at XDA seem pretty convinced that 2.0 will run on these devices no sweat. I'm pretty confident that if no OTA update happens, XDA will have my back.