| 31 Aug 2023 |
 samueldr | but also LineageOS derived to LineageOS will fail in my experience | 19:13:21 |
 atemu12 | Not in mine | 19:13:31 |
| atemu12 | I've ported app data between LOS versions and devices | 19:13:42 |
| samueldr | your mileage varied differently :) | 19:14:02 |
| samueldr | so, the gist of it is: have contingency plans! | 19:14:14 |
| atemu12 | Problem is that there isn't really an alternative? | 19:14:47 |
| atemu12 | Android backups suck | 19:14:50 |
| samueldr | exactly: there aren't | 19:17:28 |
| samueldr | titaniumbackup (root required) is what I've used to work around that situation | 19:17:44 |
| samueldr | but you can restore bootlooping data with that | 19:17:57 |
| atemu12 | It has the same problem though? | 19:18:10 |
| atemu12 | It too simply copies the app's state dir and apk | 19:18:23 |
| samueldr | yes, because it's not the mechanism, but data being in a broken form, that makes the thing break | 19:18:25 |
| samueldr | so in the end when I had to, I restored stuff without picking system stuff, and had to reconfigure only the system | 19:18:43 |
| samueldr | so all my app state was okay | 19:18:49 |
| atemu12 | Yeah, system stuff can sometimes be non-portable | 19:19:27 |
| atemu12 | Many of the settings are indeed possible though | 19:19:36 |
| atemu12 | * Many of the settings are indeed portable though | 19:19:42 |
| atemu12 | In my most recent endavour, I was able to restore all of the system settings | 19:20:02 |
| atemu12 | That was LOS20 from one device to another though | 19:20:13 |
