Can someone support the USB GPS

Search This thread

vdubskey

Senior Member
Aug 16, 2011
93
7
So I have my BU-353 GPS working on my Nexus 7 with the usbgps4honeycomb_beta1.apk running Timurs USBROM. I'm using it in my car as a replacement for my carpc. Does anyone know how to get the app from running in the foreground when plugging the device in or resuming from sleep? Is there a way to just having it run all the time in the background unnoticed? I would love an option in the app to enable usbgps after resume and run minimized by default.

Thanks.
 

Raztan

Member
Dec 6, 2013
47
2
Here it is.
With this new version (note that's still an early preliminary version) you will be able to specify the USB GPS connection speed and, eventually, to auto detect it. It should also, normally, better manage the USB connections. SiRF configuration has also been reactivated :)

Herbert
Thanks!, This works great on my JXD 7800, I've got a Pharos gps-500 (I think it uses the pl2303 I seen mentioned a lot)
Running Jelly Bean 4.2.2

Only issue is GPS testing app's can't read sat. But I guess the app must be a go between the dongle and the location frame work and thats why they're blind?

Other then that works great, thank you!
 

pilotedge

Senior Member
Aug 26, 2009
53
11
So I have my BU-353 GPS working on my Nexus 7 with the usbgps4honeycomb_beta1.apk running Timurs USBROM. I'm using it in my car as a replacement for my carpc. Does anyone know how to get the app from running in the foreground when plugging the device in or resuming from sleep? Is there a way to just having it run all the time in the background unnoticed? I would love an option in the app to enable usbgps after resume and run minimized by default.

Thanks.

Yea I've been after this for a while. The problem is I think that it wont stay in the background as a service so you have to restart it each time. There is a little script somewhere for starting and stopping it and I was hoping to try putting it into tasker to see if that would work. However I haven't had the time, I'm not very proficient either!!
Let me know if you have any luck.
 

vdubskey

Senior Member
Aug 16, 2011
93
7
Yea I've been after this for a while. The problem is I think that it wont stay in the background as a service so you have to restart it each time. There is a little script somewhere for starting and stopping it and I was hoping to try putting it into tasker to see if that would work. However I haven't had the time, I'm not very proficient either!!


Let me know if you have any luck.






What do you mean by script? If you mean simply launching the UsbGPS app at boot/resume then that's what im already doing. I also send a keypress to the home key and then relaunch GoneMad Music Player. Very messy and coming from my previous Windows based carpc running Centrafuse, it annoys me to no end that its not a seamless experience.



If that's not what you mean by script do you have a link?



Thanks,

Joey







Sent from my Windows Phone using Tapatalk
 

iv00vi

New member
Apr 17, 2012
3
0
Wonde Proud GM90

Hello,

I managed to grab one of the "professional grade" GPS USB mice Wonde Proud GM90. This one has an advantage of providing Dead reckoning functionality directly in the USB mouse (it has a gyro inside and there is a separate connection for the car speed pulse). I am not sure how this is done, since the device outputs NMEA stream (when connected to Windows), but I believe it is generating fake NMEA messages when there is low signal available. It is a little bit strange, that under Windows it is being reported as 03eb:6129 and under Android it is being reported as 03eb:07d2 (see below). When connecting the the GPS mouse under Windows, it does not blink the LED until the drivers are installed. When it is connected to Android, it blinks correctly right away.

I would really love to make this work in Android as a new Location provider, as I am in the search of dead reckoning (I drive a lot in between tall buildings and in tunnels).

I tried USBGPS4DROID (all versions) with rooted Android. Latest version displays single USB port, I am able to start the program, but I get the usual "Will retry 5 more times before closing" and in the end the application Stops GPS. I get nothing in the NMEA log.

I also tried to hack the app in the same way as ron.72 did here: http://xdaforums.com/showpost.php?p=40843496&postcount=143 (values for my USb GPS mouse are the same, I only changed VendorID in his diff and applied it), but without success.

Can you help? I am willing to pay if someone would make it work.

Thank you all.

USB serial monitor response is the following:
$LAD_Temper_AD,650,LAD_GyroBase_AD,200381,

Result of USB Device Info:
Device Info
Device Path: /dev/bus/usb/002/002
Device Class: Communication Device (0x2)
Vendor ID: 03eb
Vendor Name: Atmel Corp.
Product ID: 07d2
Product Name: not in db

Interfaces
Interface #0
Class: Communication Device (0x2)
Endpoint: #0
Address : 131 (10000011)
Number : 3
Direction : Inbound (0x80)
Type : Intrrupt (0x3)
Poll Interval : 255
Max Packet Size: 8
Attributes : 000000011
Interface #1
Class: Communication Device Class (CDC) (0xa)
Endpoint: #0
Address : 1 (00000001)
Number : 1
Direction : Outbound (0x0)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 64
Attributes : 000000010
Endpoint: #1
Address : 130 (10000010)
Number : 2
Direction : Inbound (0x80)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 64
Attributes : 000000010
 
Last edited:

iv00vi

New member
Apr 17, 2012
3
0
Wonde Proud GM90

Hello,

I managed to grab one of the "professional grade" GPS USB mice Wonde Proud GM90. This one has an advantage of providing Dead reckoning functionality directly in the USB mouse (it has a gyro inside and there is a separate connection for the car speed pulse). I am not sure how this is done, since the device outputs NMEA stream (when connected to Windows), but I believe it is generating fake NMEA messages when there is low signal available. It is a little bit strange, that under Windows it is being reported as 03eb:6129 and under Android it is being reported as 03eb:07d2 (see below). When connecting the the GPS mouse under Windows, it does not blink the LED until the drivers are installed. When it is connected to Android, it blinks correctly right away.

I would really love to make this work in Android as a new Location provider, as I am in the search of dead reckoning (I drive a lot in between tall buildings and in tunnels).

I tried USBGPS4DROID (all versions) with rooted Android. Latest version displays single USB port, I am able to start the program, but I get the usual "Will retry 5 more times before closing" and in the end the application Stops GPS. I get nothing in the NMEA log.

I also tried to hack the app in the same way as ron.72 did here: http://xdaforums.com/showpost.php?p=40843496&postcount=143 (values for my USb GPS mouse are the same, I only changed VendorID in his diff and applied it), but without success.

Can you help? I am willing to pay if someone would make it work.

Thank you all.

USB serial monitor response is the following:
$LAD_Temper_AD,650,LAD_GyroBase_AD,200381,

Result of USB Device Info:
Device Info
Device Path: /dev/bus/usb/002/002
Device Class: Communication Device (0x2)
Vendor ID: 03eb
Vendor Name: Atmel Corp.
Product ID: 07d2
Product Name: not in db

Interfaces
Interface #0
Class: Communication Device (0x2)
Endpoint: #0
Address : 131 (10000011)
Number : 3
Direction : Inbound (0x80)
Type : Intrrupt (0x3)
Poll Interval : 255
Max Packet Size: 8
Attributes : 000000011
Interface #1
Class: Communication Device Class (CDC) (0xa)
Endpoint: #0
Address : 1 (00000001)
Number : 1
Direction : Outbound (0x0)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 64
Attributes : 000000010
Endpoint: #1
Address : 130 (10000010)
Number : 2
Direction : Inbound (0x80)
Type : Bulk (0x2)
Poll Interval : 0
Max Packet Size: 64
Attributes : 000000010
Hi, I found this GPS mouse and I am trying again... Still willing to pay for it :)
 

Top Liked Posts

  • There are no posts matching your filters.
  • 3
    Here is a quick and dirty adapted version of BlueGPS4droid in order to read NMEA data from a file/device.
    Instead of giving the name of a bluetooth device you have to give the path of a file.
    Don't know if it will work: since I don't have any usb Gps, I cannot test.
    However it's working with plain files, so I hope it will also work with /dev/ttyUSB0.

    You should be able to see on the logcat if it recognizes NMEA sentences or not.
    If you can post a copy of the logcat it could be useful for me.

    If it's working, I will put the code in a new repository (forked from BlueGps4Droid), clean the code, re-inject other languages and advanced functionalities we have inblueGPS4droid, etc.

    How to use it :
    0) plug the GPS usb device
    1) allow GPS use, if possible (don't know if you can)
    2) enable mock locations in "Settings/Applications/Development/Allow mock locations" (It's important !)
    3) start UsbGps
    4) choose a NMEA device (device path: ako /dev/ttyUSB0 - it has to be readable ! )
    5) eventually activate "auto-enable location provider" in "location provider options" (useful if you cannot enable "Use GPS satellites" option (in step 1)
    6) start the service using the start checkbox
    7) look if something happens in the logcat...
    2
    Hi Herbert!
    If you can help me please!
    I have a tablet with Android 1.6 and USB GPS dongle DN-100 by usglobalsat.

    This is a peace of dmesg when it attached:

    usb 1-2.3: new full speed USB device using ehci_hcd and address 6
    usb 1-2.3: New USB device found, idVendor=067b, idProduct=2303
    usb 1-2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    usb 1-2.3: Product: USB-Serial Controller D
    usb 1-2.3: Manufacturer: Prolific Technology Inc.
    usb 1-2.3: configuration #1 chosen from 1 choice
    pl2303 1-2.3:1.0: pl2303 converter detected
    usb 1-2.3: pl2303 converter now attached to ttyUSB5

    If run the code:

    su root
    stty -F /dev/ttyUSB5 ispeed 38400 && cat < /dev/ttyUSB5

    see standard NMEA sentences (GGA / RMC / ...) (speed 38400 from user manual)

    But you aplication USBGPS4DROID dont install in my tablet (I think it to another version Android)
    Any idea?

    Google has changed the API used to start Android services between Donuts (Android 1.6) version and Eclair (Android 2.0).
    As bluetooth API has been introduced in the SDK with Eclair, BlueGPS4Droid was initially made for Eclair.
    When I've made the USB version, I've kept the Eclair target.

    Since I've made a BlueGPS version specifically for Cupcake and Donuts, I can also try do so for UsbGPS... (but as stated before I won't be able to test it, so...).

    You will find the sources and the APK on github : https://github.com/HvB/UsbGps4Droid - https://github.com/HvB/UsbGps4Droid/downloads

    Herbert


    If you're happy with this work, you can use the thanks button... :)
    2
    This is just an early preliminary version. Actually it assumes 4800 bps GPS (default speed for Globalsat BU-353) . The next version will have the speed option reactivated and even (if I can manage it) an auto configure option.
    If you can reconfigure your GPS to use 4800bps instead of 19200bps there is a chance it will work.
    Or you can wait for the next version and try again : since your gps is recognized, normally the next version should be able to managed it
    Herbert.

    Here it is.
    With this new version (note that's still an early preliminary version) you will be able to specify the USB GPS connection speed and, eventually, to auto detect it. It should also, normally, better manage the USB connections. SiRF configuration has also been reactivated :)

    Herbert
    1
    According your steps, gps running, but it seemed not get the data. No gps searching notification icon flashed and in the log data I don't see any thing. The information in my pm is not correct. I use the wrong device folder. But changed back to \dev\ttyUSB0, I can connect but no data.

    I don't have any usb GPS, so I cannot test anything myself! If you want something I will need a little more informations.

    So here are some little things you can do to provide more details.

    First you can verify if you receive something from your usb GPS:
    Connect your android device to you computer and open a command shell on your android device using
    Code:
    adb shell
    Then you can use
    Code:
    hexdump -c /dev/ttyUSB0
    to display what the gps is sending (replace /dev/ttyUSB0 with your usb gps dev). You should see standard nmea sentences...

    If you don't see valid nmea sentences you can use
    Code:
    stty -a -F /dev/ttyUSB0
    to obtain more informations on your dev.

    You can also verify read/write access rights of the device
    Code:
    ls -l /dev/ttyUSB0
    We need at least read access. If we don't then you will need to root the android device in order to be able to change the access rights on the dev.

    If the hexdump command works well then you can run usbGps and use the
    Code:
    logcat
    command to obtain more informations on what happens in the the usbGps app (it would help me a lot!).

    Also if usbGps doesn't work it should display a notification (not very useful but it can help a little).

    Herbert

    PS: the name of the device should really be something like /dev/ttyUSB0 with "/" not "\", so if you try to use "\dev\ttyUSB0" as your device name il will not work and it's normal.
    1
    Hi Herbert,
    On the advice of Ian Fernandez of USGlobalSat I tried your usbGPS4Honeycomb_MR1_alpha.apk application on my 7" Double Power model EM63 tablet (Jellybean 4.1.1, Kernel version 3.0.8) using their model BU-353 GPS receiver and am unable to get any response (the GPS LED never blinks and there is no recognition of a GPS on any of several GPS programs) . I am now looking into the USB lines as I connected the male cable from the GPS to the male USB cable that came with the tablet through a male-to-male USB adapter (female-female). Other than something there, or possibly a USB problem with the tablet, it appears that your app does not function on this DoPo tablet. I will keep you posted on progress.
    Jim

    FWIW on my tablet one USB port wouldn't work for t he GPS...but would work for a keyboard or thumb drive. With the GPS you HAVE to use an OTG cable. With that, I was able to get it work.