ChanServ changed the topic of #robotnix to: Robotnix: || Channel logs:
Kranzes has joined #robotnix
<Kranzes> Hey there!
<Kranzes> i am trying to build LineageOS for my phone and im trying to figure out what i need to do to end up with a standard installable/flashable lineageos zip that should be something like ""
<Kranzes> I just end up getting the signed target files and ota update zip files
<Kranzes> i assume that i dont just flash the OTA zip
<Kranzes> from what i can see on the lineageos wiki i need to run something like this:
<Kranzes> which i dont think is being ran when running the release script
<Kranzes> do i need to manually add that part to the release script or am i going about this completely wrong
<danielrf[m]> Kranzes: Hi, welcome!
<danielrf[m]> ota_from_target_files is actually run as part of the release script
<danielrf[m]> Sideloading the ota file generated by the release script should work
<danielrf[m]> The filename doesn't exactly match what lineageos produces because I tried to keep things consistent with the vanilla/grapheneos flavors
<Kranzes> i see
<Kranzes> i was also wondering, if i should disable seedvault that comes with lineageos and use the one from robotnix that is newer
<Kranzes> and if i can disable the chromium webview from lineageos and use the bromite one from robotnix
<danielrf[m]> sure!
<danielrf[m]> You'd likely need to set source.dirs."packages/apps/Seedvault".enable = false; to disable the one included from lineageos
<danielrf[m]> Robotnix also uses its own chromium webview instead of relying on the prebuilt one from LineageOS
<danielrf[m]> But you could enable the bromite one instead if you'd like
<danielrf[m]> I didn't realize the seedvault included in LineageOS is a few months old
<danielrf[m]> Currently, we replace some components from upstream flavors by default
<danielrf[m]> Usually because they are prebuilt and I'd like to build them from source: kernels in vanilla/grapheneOS, webview, etc
<danielrf[m]> but we might consider doing this for seedvault by default as well
<Kranzes> alright so in the webview module i disable chromium and enable bromite right?
<danielrf[m]> I'd like to get some automated tests working before I start ripping out apps from upstream flavors and replacing them with my own copies
<Kranzes> do i also disable apps.chromium?
<Kranzes> or is that something else
<danielrf[m]> Kranzes: yes to both
<Kranzes> what would happen if i enable bromite webview but disable apps.bromite ?
<Kranzes> or are they not related
<danielrf[m]> you can either enable the app or the webview--they're mostly independent
<danielrf[m]> However, they get built in the same nix derivation (except bromite), so if you mix/match you wouldn't be able to use the cachix binary cache
<danielrf[m]> I typically enable/disable the app/webviews together
<Kranzes> is the apps module not a webview?
<Kranzes> is it the proper browser?
<Kranzes> or what
<danielrf[m]> yes
<danielrf[m]> it's the browser app
<Kranzes> i see, then i will disable it!
<danielrf[m]> gotta step off the computer for a bit, but hope it works for you!
<Kranzes> yup, have a good evening!
<Kranzes> I have just thought of a cool and simple module you could add to robotnix, a wireguard kernel module support for android, take a look at "Method B" here:
<ajs124> iirc that doesn't work for android 10+ anymore
<Kranzes> why wouldnt it?
<Kranzes> hm
<ajs124> because it modifies the android tree, which isn't possible anymore in those releases
<Kranzes> then how would you make something like that work? becuase all it really does is execute a script that adds the wireguard kernel module to whatever kernel is being used in the build
<ajs124> I seem to remember that you can patch the kernel source easily with robotnix
Kranzes has quit [Ping timeout: 240 seconds]
Kranzes has joined #robotnix
Kranzes has quit [Client Quit]
Kranzes has joined #robotnix
Kranzes has quit [Quit: Connection closed]
<danielrf[m]> Last I checked, wireguard would require root being available to use the kernel module
<danielrf[m]> Although I do remember some effort to integrate it into Android properly without requiring root, perhaps like the openvpn support currently in android
<danielrf[m]> If that ever gets released I'll definitely include it in robotnix
<danielrf[m]> Also: the `kernel.patches` option currently in robotnix only works for vanilla and grapheneos
<danielrf[m]> Since vanilla/grapheneos build the kernel outside the rest of the Android build system
<danielrf[m]> Although it's still trivial to patch a kernel integrated into the andoid build via `source.dirs."path/to/kernel/source".patches`