| 31 Aug 2023 |
 samueldr | system data isn't portable enough and things will break, since AFAIK they don't ship lineageos upstream | 19:11:25 |
| samueldr | * system data isn't portable enough and things will break, since AFAIK they don't ship lineageos downstream | 19:11:29 |
 atemu12 | Absolutely | 19:11:35 |
| atemu12 | Some parts are portable however such as apps, app data and other generic Android things | 19:11:58 |
| samueldr | oh, I thought you implied for "app data", but you meant "user storage" | 19:12:03 |
| atemu12 | App data is portable | 19:12:17 |
| samueldr | oh, no, in my experience the rom would bootloop | 19:12:19 |
| samueldr | like, vendor → lineageos would bootloop | 19:12:34 |
| atemu12 | Ah, I guess I never tried to go from anything other LOS | 19:13:03 |
| samueldr | or how I would phrase it would be: YMMV | 19:13:05 |
| atemu12 | Perhaps you'd want to exclude system apps in that case | 19:13:14 |
| 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 |
