Motorola Droid/Milestone w/ Bluetooth GPS

by jeremynealbrown » Wed, 14 Apr 2010 03:36:55 GMT


Sponsored Links
 Hello,

I am working on an Android 2.0 project that is going to be used in a
somewhat remote location. There will be no internet connection
available and it will be used outside of the U.S. I am considering the
option of using an external Nokia or similar GPS device as a GPS
receiver/transmitter and connecting to it for use in my application
via bluetooth.

I am looking for opinions on whether or not this is even possible, if
someone out there has attempted it or if someone has a suggestion for
some other external device that would be more fitting.

Link to possible external GPS device:
 http://europe.nokia.com/find-products/accessories/all-accessories/navigation/gps-modules/nokia-gps-module-ld-3w 

Thanks in advace,
~Jeremy

--



Motorola Droid/Milestone w/ Bluetooth GPS

by Lucian Tomuta » Fri, 23 Apr 2010 02:35:44 GMT


 I'm not sure I understand what you are after. On which phone will you run
the Android app and doesn't it have a built-in GPS?

If you intend indeed to use a Bluetooth GPS receiver then you should go for
Nokia's updated model,
 http://europe.nokia.com/find-products/accessories/all-accessories/navigation/gps-modules/ld-4w 

< http://europe.nokia.com/find-products/accessories/all-accessories/navigation/gps-modules/ld-4w> ;Other
than that it is all about opening a serial port, receiving the NMEA strings
and parsing them accordingly. Totally doable.

Best regards,
Lucian

Calling All Innovators 2010 - mobile development competition
 http://bit.ly/bUjIzf 


On Mon, Apr 12, 2010 at 6:11 PM, jeremynealbrown



>


Sponsored Links


Motorola Droid/Milestone w/ Bluetooth GPS

by faizan khan » Fri, 23 Apr 2010 03:26:06 GMT


 its very much doable.have apps running on both phones which will sync the
locaiton coordinates.bluetooth/infra red/sms anything could be used for
synching.you can even consider a desktop to sync the location coordinates :)





>>



Motorola Droid/Milestone w/ Bluetooth GPS

by Lucian Tomuta » Fri, 23 Apr 2010 03:48:01 GMT


 LD-4W is a Bluetooth GPS receiver, not a phone. Bluetooth is the only
supported bearer.

Best regards,
Lucian

Calling All Innovators 2010 - mobile development competition - 500000 USD in
prizes -  http://bit.ly/bUjIzf 







>>>



Motorola Droid/Milestone w/ Bluetooth GPS

by Nathan » Fri, 23 Apr 2010 04:40:00 GMT


 It should be possible, assuming Bluetooth on the phone can pare with
the GPS and establish a serial port profile. Then you would open and
read from the virtual serial port using the NMEA protocol.

I have no actual experience with bluetooth on Android, but this is how
it would have been done on Windows Mobile in the past. Is that
bluetooth receiver going to give you a lot off advantages over the
built in one? The built in one can use satellites and would not be
dependent on the cell network, if that's your concern.

Nathan






> >>>



Other Threads

1. Can't run emulator on MacOS :: newly created AVD not found



And just so that I am not crazy:
[...@e03077]~/Android/sdk/android-sdk-mac_x86-1.5_r2$ android list avd
Available Android Virtual Devices:
    Name: pawel
    Path: 
/Users/vps/Android/sdk/android-sdk-mac_x86-1.5_r2/.android/avd/pawel.avd
  Target: Android 1.5 (API level 3)
    Skin: HVGA
  Sdcard: /Users/vps/SDCARD.1

--~--~---------~--~----~------------~-------~--~----~

2. Best practices - looking for application design advice for a location aware app.

I am working on my first android application and am looking for some
advice on design decisions.
The main goal of the application is to display trails (like cycling/
hiking trails) near the users current location.
The user will first be presented with a mapview with markers
indicating the location of near by trails.
They can then select a trail and have it overlayed on the map.
The biggest problem right now are:
1) the database is not static - new trails will be added periodically
so a master database will be needed online.
2) trail data (gpx files) consume a lot of space, usually 50 - 300 kb
per trail, so storing all trails on the device may not be feasible.

The three main designs I see are the following:

1) Store light-weight data (like trail names, trail head location,
trail distance, etc) in a local SQLite db on the device.
   Store the light-weight data in a remote database (MySQL or DB2) as
well.
   Store heavy-data (the trail gpx files) remotely.
   New trails are added to the remote database.
   Periodically synchronize/update the local SQLite database with the
remote (master) database.
   When a gpx file is needed, transfer it and parse it to display the
overlay in mapview.
   Possibly store the 10 most frequently used trails (gpx files) on
the device to save bandwidth.

   PRO: Getting the list of nearby trails is fast and easy because it
simply queries the local SQLite database.
   PRO: Minimal amount of data is stored on the local device.
   CON: Transfering gpx files to the device + parsing them will be
time consuming and power draining.

2) Store all data remotely.
   Don't store individual gpx files - parse their data into the
database so all information needed in accessable through database
queries.
   Parsing is done on the server.

   PRO: The android app consumes little space and all processing is
done remotely.
   CON: High bandwidth use due to high number of queries and lots of
returned data (could introduce lag and be costly on the data plan).

3) Store all data (light and heavy) both locally and remotely.
   Don't store individual gpx files - parse their data into the
database so all information needed is accessible through database
queries.
   New trails are added to the remote (master) database.
   Parsing of new trail gpx files is done remotely.
   Periodically synchronize/update the local SQLite database with the
remote (master) database.

   PRO: All data is local so simply query the info needed. Good
performance and low bandwidth use.
   PRO: Synchronization can be done at any time when a WiFi connection
is available so no worry about data plan costs.
   CON: Will consume way too much space. 1000 trails could easily
consume over 100 MB.


Because the database is dynamic I see no way of avoiding having a
master database stored remotely so I image any design will have to
involve network access to a remote database at least for
synchronization purposes if nothing else.


Any advice, insight, or discussion is greatly appreciated.

Thanks!!

--~--~---------~--~----~------------~-------~--~----~

3. Text color problem in Multi Choise dialog

4. print on a bluetooth printer

5. Eclipse issues

6. no route to host Exception on Socket

7. Background Task Result Reporting Hypothetical