Giters

BasicAirData / GPSLogger

A GPS logger for Android mobile devices

Home Page:http://www.basicairdata.eu/projects/android/android-gps-logger/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Import/Export of Internal Tracklist

clriis opened this issue · comments

commented

When changing devices it would be handy to have an Import/Export or Backup function of the Tracklist as it gives a very informative overview.

Meanwhile I've been trying to locate where the tracklist is stored, but with no luck. I've looked in:
/storage/emulated/0/Android/data/eu.basicairdata.graziano.gpslogger/
But it's empty
I'm using Android 12

commented

The tracklist is stored into the private app's data folder.
The app's data is not accessible by any other app for privacy reason, as per Android specification, and can be backupped and transferred to a new device using for example the backup/restore service of the Google account.

Would you like to have another method to backup/restore the tracklist?

commented

Yes.
It would make the app more agile/versatile if there was a backup/restore option for the tracklist.
The tracklist is really neat and provides a very clear overview of activities. The Google backup/restore service is not very flexible.

I've been using GPS Logger for 3 months now for Kayaking, Cycling and Hiking. It is by far the most stable and dependable tracker I've come across and I've tried quite a lot. The very small footprint on battery is another important feature.

commented

It would be great to add the feature you suggested to GPS Logger for the following reasons:

  • as you rightly wrote, the Google Backup is not very flexible
  • Google Backup it is a service that is limited to a phone upgrade
  • Google Backup has a MB limit for any app, and someone could have a bigger amount of data
  • It would be great to not be dependent on any Google service, specially for users that don't install the app using the Play Store

We leave the issue open to track a possible future implementation.

commented

As first step we should define these details:

  • What the backup should contain (Database, or maybe also the thumbnails of the tracks): if we don't include the thumbnails, they should be recreated at the end of the importation process.
  • Will the restore operation erase any content of the Tracklist before proceed with the importation of the data?
  • We should think how/where to perform the backup/restore operation, with a mock-up of the user interface
commented

Hi Graziano,
Thanks for including this request.
I got the following comments to your points:

  • For me it's enough to include the thumbs, I do not alter my routes. But maybe there are other scenarios and it would probably be "proper" to recreate them.
  • I think the restore should ADD, at least as default. But also include a SORT function for date, track name, activity (I know, this is another request).
  • The operation should be included directly in the 3-point menu.

My scenario at present is at that I got two Phones:

  • Samsung Galaxy S10e (main phone)
  • Samsung Galaxy A51

I use my S10 for logging when cycling
But when I'm seakayaking it's often 8 hours+ and I use the S10 for podcasting and photos so battery is a limiting factor. Therefore I use the A51 for logging.

It would be very neat if I could combine the tracklists created.

Kind regards
Claus Riis

commented

Would be a really nice feature.