[A7 General] jerryasher:
I have Google Maps with GPS location support on my eLocity. This is a short note describing what I put together -- I did no work here, I just found the appropriate notes left by others.

Update: Navigation works too. See below.

I had an eLocity that I put Dexter's v1.42 on. But the market on that does not show Google Maps. So I put Bestialbub's fix on top of that. And that did display google maps, so I downloaded it. However, for whatever reason, the resulting market was very unstable, and would force close, even as a background task when I wasn't using it.

But it was good enough to play with. And with it I got the fundamentals working, however, I did end up reflashing with the latest stock eLocity firmware and installing Bestialbub's market on top of that.

So I installed Google Maps on the eLocity.

The eLocity does not have a GPS, so you need some external GPS device. I used my Nexus One and an app called Bluetooth GPS Output

I believe that app cost a couple of bucks, and there are free apps that will do the samething and should work, but I found pretty good instructions on how to get Bluetooth GPS Output to work here.

What Bluetooth GPS Output does is to take the GPS information on my Nexus One and make it available over bluetooth to any connected bluetooth device that wants it.

I then basically followed the instructions from here.

Bluetooth Pair your phone and Archos tablet (I have the Archos 70 250 gb)

Open Bluetooth GPS out on your phone,and turn it on, you should see a screen showing satellite info

Archos Settings/Location and Security/Bluetooth GPS, then select my paired phone. If that is grayed out, try opening up the app on your phone before actually pairing your Archos with your phone.

Open up maps and enjoy the Navigation!

But the last step isn't that simple because the eLocity doesn't support Bluetooth GPS in the Location & security settings page.

But there are workarounds....

Similar to Bluetooth GPS Output, there are apps that do the reverse. Listen for a Bluetooth GPS Stream, and convert that into an internal android source.

And for that, I chose, an application called BluetoothGPS -- similar name, different developers.

I installed that on the eLocity.

At this point I made the eLocity discoverable over bluetooth and discovered it on my Nexus One. The two devices said they were paired but not connected. I'm not sure what that means. And still with this working, I still see on the eLocity, the Bluetooth is active but not really connected icon, while the Nexus shows a bluetooth connection has been made (though that could be indicating a connection with its dock which is 10 feet away.).

On the Nexus One to get Bluetooth GPS Output talking to Bluetooth GPS I:

Didn't do much if anything in Bluetooth GPS Output, I just started it

On the eLocity, I:

On the device's Application settings page, under development, I enabled "Allow mock locations"

I started the application Bluetooth GPS

On Bluetooth GPS's main tab, I enabled Mock GPS Provider

Bluetooth GPS presented a list box with my Nexus in it, and asked me to connect, so I did.

And on Bluetooth GPS settings tab, I frobbed some reconnect interval settings.

And with that, it basically seems to work. The connection does not seem incredibly stable, I am not sure if it's related to screen display timeouts and devices sleeping, or some other source of flakiness.

But it does seem to work.

So I took it out for a test drive, to see how well it worked. This was typical suburban driving. And only lasted about 30 minutes.

The nexus was plugged into the car, the elocity was on battery. Bluetooth on, Bluetooth GPS Output running, Bluetooth GPS running, and the map showed the current location. Great!

So I directed the map on the eLocity to take us to the post office, and ... waited ... and waited ... and nothing happened.

Aha, it needs data. So I turned on the Nexus One's wifi hotspot, connected the eLocity to that, and, ...

Success! Driving directions and navigation worked just fine, with one caveat. For whatever reason, i would tell me when I started up Navigation that if I wanted voice nav, I needed a plugin from the market, but when I said sure, go get it, the market would force close. However, voice navigation worked anyway.

During the 30 minutes I played with it, the connection between the two devices was nice and stable, and the map always displayed the right location and navigation worked as expected.

The eLocity is a very nice mapper compared to the Nexus One, for whatever reason, at equivalent zoom levels, the eLocity display shows much much more of the surrounding area than does the Nexus One. And physically the screen is about three times larger, and much easier to see in daylight (cloudy day though.)

However, the Nexus One displays a map where your current driving direction is always oriented to the top of the screen. This makes it very easy to orient where the next turn or landmark is.

Presumably because the eLocity does not have a digital compass, the eLocity always displays north to the top of the screen. This can be better at sometimes, as when you are trying to get a feel for where a very long route will take you, and worse at other times, when you're just trying to navigate through streets.

But all in all, pretty cool.

Note the Google Maps blue location dot: