Android Version of Gps Tracker Now in Google Play Store!

Finally something that has been requested for some time, the android version of GpsTracker is in the Google Play Store:

Gps Tracker on Google Play

https://play.google.com/store/apps/details?id=com.websmithing.gpstracker

This version has many significant enhancements. The most important is that it now has google play location services running in a background service. Also, location updates will restart automatically if the phone is restarted. Please download and test the app and let me know how it works! If you want to have a look at the source code, you can find it here:

https://github.com/nickfox/GpsTracker/tree/master/phoneClients/android

12 thoughts on “Android Version of Gps Tracker Now in Google Play Store!

  1. Wim Smit

    Hi,

    Apache reported an error stating that the distance was not a correct sql decimal. So just before sending the data to the sql database I inserted a str-replace. Maybe an option to do this in your version also.

    Reply
      1. Wim Smit

        [Sun Nov 16 12:48:12.764205 2014] [php5:error] [pid 31615] [client 217.120.158.143:57795] PHP Fatal error: Uncaught exception ‘PDOException’ with message ‘SQLSTATE[HY000]: General error: 1366 Incorrect decimal value: ‘1,4’ for column ‘_distance’ at row 1′ in /srv/www/htdocs/gpstracker/updatelocation.php:59\nStack trace:\n#0 /srv/www/htdocs/gpstracker/updatelocation.php(59):

        Reply
          1. Wim Smit

            Yup, the phone is located in the netherlands.
            Updating the app would also solve the problem.

            The next question will follow soon as i intend to change the route display to poly lines and add the possibility to show gpx tracks.

            thanks for the great work you’ve already done.

          2. Nick Fox Post author

            What’s troubling me about this is the following. There are 4 possibilities here:

            1) phone’s locale is European, mysql’s locale is American
            2) phone – American, mysql – European
            3) phone – American, mysql – American
            4) phone – European, mysql – European

            1 and 2 are the obvious problem but I haven’t convinced myself that a simple replace function will correctly handle those 2 use cases. One possibility that I’m thinking of is to determine the locale of the phone and send that to the web service and then determine the locale of the mysql db and then using the replace function appropriately. It’s a lot of extra work software-wise. I haven’t given it enough thought to determine if there is a better way. Let me know if you can think of something better.

            n

    1. Nick Fox Post author

      Hey Borin

      Not sure what client you are talking about. ios or android? Did you set a breakpoint and see what is happening to variables?

      n

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *


This site uses Akismet to reduce spam. Learn how your comment data is processed.