| 23 Aug 2021 |
 danielrf | pie_: Hey, that's great! Just let me know any questions you may have, either about the current organization of the robotnix modules, or if you'd like me to elaborate more on particular github issues. | 19:07:29 |
 pie_ | Sure thanks, the next thing for me is trying to get a beefy machine from somewhere - a teammate has offered one up, we'll see how that goes. | 19:10:26 |
| pie_ | danielrf: if you have any recommendations for how i should start learning my way around the project that would be cool i guess | 19:30:35 |
| danielrf | assuming you're familiar with the nixos module system (see the NixOS docs if not), the entrypoint default.nix includes all the modules/flavors. Probably the three most "core" modules are modules/base.nix, modules/source.nix, and modules/release.nix | 19:32:59 |
| danielrf | The source module is one I'd love to see made generic (https://github.com/danielfullmer/robotnix/issues/115). It'll be useful for fetching kernel sources using the "repo manifest" | 19:35:28 |
| danielrf | The giant build step is build.android, specified under modules/base.nix, it uses a slightly more generic mkAndroid function defined in the same file | 19:36:29 |
| danielrf | and then modules/release.nix is in charge of the final steps (signing target files, generating img / ota files) | 19:37:00 |
| danielrf | Walking through those files (plus maybe a flavor so see how certain options are set) should hopefully be enough to understand how it builds end-to-end. | 19:38:41 |
| danielrf | And of course, reading any relevant docs you see (e.g. https://source.android.com/setup/build/building). | 19:41:48 |
| 25 Aug 2021 |
| danielrf | Tagged and pushed grapheneos-2021082501. Tested on crosshatch | 21:37:03 |
|  mjolnir banned  matthewcroughan - nix.zone (<no reason supplied>). | 22:03:11 |
| 27 Aug 2021 |
|  duairc joined the room. | 13:10:21 |
| 29 Aug 2021 |
|  vika (she/her) 🏳️⚧️ joined the room. | 09:46:15 |
|  CRTified joined the room. | 23:02:24 |
| 1 Sep 2021 |
 hmenke | I've switched to sandboxed Google Play Services to test it out. My conclusion: 5/10. | 06:58:10 |
| hmenke | Actually microg has the much better UX because it has a nice GUI overview of which applications use Google Play Services. | 06:58:55 |
| hmenke | The downside is that microg requires signature spoofing which is a security risk. | 06:59:18 |
| hmenke | Also when switching from microg to sandboxed Google Play Services, most apps that use Play Services have to be reinstalled because they fail to request a new FCM token. | 07:00:15 |
| hmenke | This way I also found out that Seedvault + Nextcloud is major garbage. Seedvault doesn't do incremental backups and when a backup has failed and is restarted Nextcloud just deletes everything that's already on the server. | 07:01:49 |
 volfyd | Wow good to know re: nextcloud | 14:56:55 |
 ajs124 | Nextcloud being a POS in general is sadly nothing new, but good to know that you can't even store files in it properly -.- | 15:00:01 |
 cde | fwiw seedvault does do incremental backups | 15:21:33 |
| cde | there's two types of android backups - 'full' and 'kv'
kv = key value, those are entirely incremental | 15:21:47 |
| cde | seedvault takes the backup data android gives it (i.e. the os / framework), encrypts it and passes it to the chosen storage location. | 15:22:33 |
| cde | but nextcloud has definitely had issues, there have been many reports and I've seen that too.
We've tried to fix some of those bugs, it works a lot better now than it used to when it was initially added. | 15:23:11 |
| cde | In reply to @hmenke:matrix.org
This way I also found out that Seedvault + Nextcloud is major garbage. Seedvault doesn't do incremental backups and when a backup has failed and is restarted Nextcloud just deletes everything that's already on the server. this is bad and shouldn't happen normally, would you mind filing a bug with some more details? | 15:24:06 |
| hmenke | You're right, Seedvault does incremental backups, I used the wrong term. What I meant was that Seedvault doesn't do snapshots, so I can't go back to older backup. | 15:27:32 |
| cde | ah yes. that's still an open issue. | 15:32:33 |
| hmenke | * This way I also found out that Seedvault + Nextcloud is major garbage. Seedvault doesn't do ~~incremental backups~~ snapshots and when a backup has failed and is restarted Nextcloud just deletes everything that's already on the server. | 15:51:59 |
| hmenke | * This way I also found out that Seedvault + Nextcloud is major garbage. Seedvault doesn't do incremental backups snapshots and when a backup has failed and is restarted Nextcloud just deletes everything that's already on the server. | 15:52:18 |
