search

redfish64 / TinyTravelTracker

Private Android GPS tracker
GNU General Public License v3.0
135 stars 31 forks source link

Automatic Nightly Backups #14

Open markwaters opened 8 years ago

markwaters commented 8 years ago

Firstly , I have been using Tiny Travel Tracker for about a month and love it! Thank you so much for writing it.

My phone got wet yesterday and has died , the latest backup I have is from about 5 days ago.

Could backups be automated ?

xloem commented 8 years ago

I agree, it would be great to be able to at least save the backup to sdcard every night

ilf commented 8 years ago

I think this is the job of a backup app like Titanium Backup.

xloem commented 8 years ago

I'm interested in automatically uploading the gps data elsewhere. At the moment it is stuck inside the app. [edit: yowch! and titanium backup requires root. I run linux single-boot which odin doesn't run on, so it's hard for me to root my phone]

ilf commented 8 years ago

The data is not "stuck", it's in /sdcard/Android/data/com.rareventure.gps2/files/gps.db3

xloem commented 8 years ago

Thanks, that's really helpful.

It's not really a replacement for the easily-readable XML file though. Even running the db3 through sqlite the fields are still binary blobs.

redfish64 commented 8 years ago

Although that file on the sdcard contains the points, without the private key, which is stored on the internal flash disk, it cannot be decrypted. You either need to backup the points through the settings menu in the app, or backup both the external memory, and the internal settings (which holds the key).

I believe Titanium backup would work for the latter but I have never used it, myself.

On Mon, Feb 29, 2016 at 5:43 PM, xloem notifications@github.com wrote:

Thanks, that's really helpful.

It's not really a replacement for the easily-readable XML file though. Even running the db3 through sqlite the fields are still binary blobs.

— Reply to this email directly or view it on GitHub https://github.com/redfish64/TinyTravelTracker/issues/14#issuecomment-190148707 .