| 24 Oct 2021 |
danielrf | Hope to have my personal device migrated to android 12 by end of today / tomorrow. After that, would love to hear feedback from others if they are able to successfully upgrade as well. | 20:01:41 |
danielrf | dan-v: My pixel 3 xl is on grapheneos currently. I might switch to vanilla when the Pixel 6 pro gets delivered, just to have better testing of that flavor | 20:02:52 |
danielrf | I'll probably hold off on tagging a commit for vanilla/graphenos until we have at least one other person who has successfully upgraded. | 20:04:32 |
Yuka (she/her) | building it now | 20:22:00 |
Yuka (she/her) | can probably say something tomorrow | 20:22:13 |
danielrf | Yuka (she/her): what flavor / device, and are you using any additional modules? | 20:22:47 |
danielrf | There's a couple fixes for certain modules I'm currently working on here: https://github.com/danielfullmer/robotnix/pull/129 | 20:23:03 |
Yuka (she/her) | GrapheneOS on bramble | 20:23:21 |
Yuka (she/her) | With f-droid and seedvault | 20:23:34 |
Yuka (she/her) | * With f-droid, updater and seedvault | 20:23:42 |
danielrf | OK. Perfect, i think combination should all be working | 20:23:54 |
danielrf | Let me know if not :) | 20:23:59 |
Yuka (she/her) | I also had microG until now, but wanted to give the Graphene sandboxed play services a try | 20:24:17 |
danielrf | * OK. Perfect, i think that combination should all be working | 20:28:26 |
kranzes | danielrf Can you update bromite and push to cachix? | 20:48:10 |
danielrf | kranzes: Sure, let me look into that again. I thought I ran into a build issue last time that was nontrivial, but maybe there's a fix already | 20:51:02 |
kranzes | You should consider using github actions/workflows to automatically update sources for some stuff in robotnix | 20:51:39 |
kranzes | https://github.com/Kranzes/robotnix-forklineageos/blob/master/.github/workflows/lineageos-update.yaml | 20:52:27 |
kranzes | I use this for ForkLineageOS | 20:52:36 |
kranzes | https://github.com/Kranzes/robotnix-forklineageos/commit/d2f674adb1de321e7b2122e27e09b3143e2edf9a | 20:53:44 |
kranzes | this was just commited | 20:53:47 |
kranzes | of course you will want a more useful commit msg than that | 20:54:00 |
kranzes | but yeah | 20:54:02 |
kranzes | It also updates buildDateTime accordingly as you can see | 20:54:29 |
danielrf | Yep, I'd love to have it all be automated, including the build/test cycles as well. In parallel I've been working on getting testing via cuttlefish virtual devices working | 20:56:09 |
kranzes | No idea what that cuttlefish thing is | 20:56:56 |
kranzes | danielrf I might have time tomorrow write a github workflow to automate fetching updates, comitting and tagging LineageOS | 21:14:56 |
kranzes | * danielrf I might have time tomorrow to write a github workflow to automate fetching updates, comitting and tagging LineageOS | 21:15:05 |
kranzes | Only thing i see myself struggling with is the naming of the tag and commit | 21:15:50 |
kranzes | but that's for me to figure out tomorrow | 21:15:58 |