ege

joined 1 year ago
[–] ege 3 points 10 months ago

It is maintained by one of the old contributor/maintainer (they still contribute to the Tachiyomi app). I can say that it is the same trustworthiness as before because volunteers (so pretty much the same people) were also maintaining the old extensions repo. It is not easy to access those people directly from the contributors section in the repository, they also cleared the commit history (I think it is to protect from DMCA), so I won’t link a profile directly, but you can get an idea by examining the people on the project’s Discord. You can also review the code of the extensions you will use, the compilation process is quite transparent thanks to GitHub Actions and you will need to trust the extension again after the new extension updates and when it's time to update, you can review the source code again. I hope I explained it clearly enough. If I said something that was not clear, I can elaborate.

[–] ege 9 points 1 year ago
[–] ege 1 points 1 year ago
[–] ege 2 points 1 year ago* (last edited 1 year ago) (2 children)

Yes, I wish you had quoted the entire text.

Data

The private app data in /data/data/ or /data/user/*/ that stores your app preferences, login info, databases, etc. This is the most important part to restore apps potentially with their state preserved.

Requirements:

⚠️ Root required for backup & restore

⚠️ Shizuku mode (ADB access) cannot read/write at these path

Nowhere in my instructions did I say that I used this feature (“backing up app data”) or that it should be used. You do not need root to backup SMS/MMS & call logs & APKs & external data (Android/data) / expansion (Android/obb) / media (Android/media) of the apps installed… I have also stated many times that I use the in-app backup/export method for application data.

[–] ege 1 points 1 year ago (4 children)

I does not require it. I don’t have root.

https://swiftapps.org/faq#appparts

[–] ege 5 points 1 year ago* (last edited 1 year ago) (7 children)

I use DivestOS which is based on LineageOS and these have SeedVault integrated in it as a backup solution, but since it doesn’t work well I’ll tell what I do (If your OS has Google’s backup solution, it works well to a certain extent, but there are times when it cannot restore things like call log/sms even though it backs them up).

  • I backup apps, SMS/MMS and call logs with Swift Backup
    • Since I don’t have many applications, I examine each application one by one to see which data can be transferred and in what way.
    • I backup data of the apps like Aegis, NewPipe etc. to their respective Android/media folder, which means I basically export Aegis’ backup file into /storage/emulated/0/Android/media/com.beemdevelopment.aegis/backups, with this way, I can back up and restore the media along with the APK of the application using Swift Backup. If you find this step unnecessary/complicated, you can create a folder called Backups anywhere and put all your backup files there.
  • I backup files and folders with Syncthing, it basically sync’s 2 directories between 2 devices and I sync all my folders into my PC with some ignore rules (for example, to avoid synchronizing the .thumbnails folder unnecessarily). Also if you stashed all your backups/exports into some folder, it will also sync.
  • Technically there is no need for a non-APK backup for applications that have their own cloud based backup mechanism or are cloud-based.

When I take these backups, I can completely restore the phone to its previous state even after factory settings. Of course, for a cleaner start, sometimes I don’t sync some folders back or don’t reinstall some applications. To do this the way I want, I reinstall and restore data of the applications one by one.

[–] ege 1 points 1 year ago

IzzyOnDroid only offers 32-bit versions for some applications (well, universal ones in some applications if the size is small enough but still does not makes sense if your device is 64-bit imo).

https://gitlab.com/IzzyOnDroid/repo/-/issues/371#note_1361378432