martin/Tracker
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
No description
3 commits 1 branch 0 tags 448 KiB
Find a file
Exact
Martin van Es d1d384ee81 Add README.me
2020-02-18 10:56:03 +01:00
.idea First commit 2020-01-29 15:35:54 +01:00
app WIP 2020-01-30 11:55:06 +01:00
gradle/wrapper First commit 2020-01-29 15:35:54 +01:00
.gitignore First commit 2020-01-29 15:35:54 +01:00
build.gradle First commit 2020-01-29 15:35:54 +01:00
gradle.properties First commit 2020-01-29 15:35:54 +01:00
gradlew First commit 2020-01-29 15:35:54 +01:00
gradlew.bat First commit 2020-01-29 15:35:54 +01:00
README.md Add README.me 2020-02-18 10:56:03 +01:00
settings.gradle First commit 2020-01-29 15:35:54 +01:00

README.md

Tracker App

A Zero-conf Location Tracker.

An Android Studio project.

Design philosophy

The idea behing Android Tracker is to have minimal configuration while building the app and Zero configuration while deploying the devices in the field. The only configuration option needed in the app is the Tracker web-server locatation update POST endpoint and salt (to prevent rogue device updates).

The app and server were originally developed for a Dutch company and have never been properly translated.

Configuration

Open app/src/main/res/values/strings.xml and update post_url to contain the URL of the post.php script in the Tracker webserver, e.g. https://tracker-web.service.tld/post.php. Update the post_salt as well.

Building

The App has been succesfully built using Android Studio 3.5.3. Target API is chosen as low as possible, so that cheap Android phones can be used to track vehicels.

Companion Webserver

The App was designed to work together with the Companion webserver https://github.com/mrvanes/tracker-web

Starting

The App is designed to be Zero-conf, which means no action is required after starting the app. It needs (hi accuracy) Location privileges, which are to be assigned manually in the Android Configuration, App Settings for the tracker app.

Once the app is started, it will try to find it's location and set up a network connection with the tracker webserver location update endpoint. As soon as this has succeeded the status icon will turn green. The status icon can be clicked to open a status windown showing debug information about the connection, status and device-id. The device-id is the unique identifier that will be used to upload status/location messages to the tracker webserver. The tracker webserver then needs to assign a vehicle to this device-id.