[BUG] importing Backup

[b-m-f]

it seems like the folder where a backup is created is not accessible anymore, as it is a system folder.

Any way to have a file picker integrated to choose which backup should be loaded?
Could also be used to export the database to a specific directory.

Its been a long time since I have worked on an Android App.

Can someone give me an estimate of the complexity of this? If it is an easy fix I could try fixing this, but the Devtool setup will take me some time.

[gerhardol]

The biggest problems in changing this is the Google requirements:
https://developer.android.com/training/data-storage#scoped-storage
Storage is therefore in app private storage for newer Android versions.

One way to implement export without changing storage is to implement sharing and use something like Solid/Amaze file manager to store the file.

[nottheend]

I think it is is a serious bug, because ultimately breaks the whole purpose of bugs. Please prioritise

[gerhardol]

The file is stored in the app private storage, it does not have privileges to store it somewhere else. This follows Googles requirements, how they want it to work.
You can move the file after exporting.

[nottheend]

Thank you, I appreciate the response.
I can confirm that it works fine for me to move the exported file freely. Export works.

Unsolved issue:

On my new phone, I didn't find any possibility to write the existing backup file to the private storage of the app.

An idea to work around this is having an activity launcher in the app (not sure if the wording is correct), where the existing backup file can be 'shared with' and then with RunnerUp app.

Or another idea is to declare in Android manifest (again guessed wording) that RunnerUp is able to open the filetype of the backup file. So that the file moved to new phone can be 'open with RunnerUp'.

Is the issue which I am facing clear?

[gerhardol]

Backups are restored with Google backups when you restore a backup.
If you install in some other way, settings and activities are not included.

A share could be used, then you need some Solid Explorer Save to "receiver".
Not too hard, but requires users to actually have a relevant way to share installed.

Restoring is harder, there are too many "interested" receivers by default already.

What about including the full path to the restore/export path?

[webeule]

First of all, thanks for this cool app!!!

I just started to setup a new phone with android 15 and want to ask what is the way to transfer the backup from my old phone?
The files app on the new phone is not able to copy the file to the folder mentioned in the first comment of this thread.
I understand that this is an android restriction, but other apps provide the option to import from a directory the user can select. An example is AntennaPod, which is also open source. May be you can copy it from there...

[gerhardol]

You can restore the app from the old phone using the Google backup. (Not sure if this is only possible when setting up the new phone or not.)
This should be implemented with choosing where to export to and import from, not implemented.

[webeule]

Ok, but I do not use google backup. I think this is the advantage of an app like yours, so that you are not bound to such kind of a service.
So I would really appreciate if you can implement such kind of functionality. The best would be if you simply can specify where the database is located.

[gerhardol]

I agree, but I have not just got time to fix this.
(Updating to next Andrid version is always highest priority, as that is required to publish in some months, but it is also the most boring...)

[webeule]

ok, I understand, I used usb debugging (with adb) to push the old DB to the new device and then imported it by using the maintenance function

[patricktokeeffe]

Same issue here, but I was able to copy the old DB to the correct folder using just file transfer (mtp) mode.

(thanks for the great app!)

[rovjuvano]

You may be able to copy the DB into the files directory by dragging between a split screen without any need for a USB cable or PC.

At least with the AOSP Files app on GrapheneOS, the ⋮ menu has an option to open a new window. Open the app switcher, hold the app icon, then select Split Screen and choose the second Files app. With the two file managers open, navigate to the two directories, select the files to copy by holding them, then hold again and drag them to the other window. Voilà. YMMV with other file managers or distributions of Android.

Discovered this after wanting to undelete an entry after accidentally discarding it from the save screen by pressing the back button. Allow file app to write in Android/data dir (#1302) · Issues · CalyxOS / calyxos · GitLab