| 1 Nov 2024 |
 eyJhb | In reply to @atemu12:matrix.org
I think I might throw it onto my daily driver FP4? Yeah? | 21:04:48 |
 atemu12 | Yup | 21:11:19 |
| 13 Nov 2024 |
|  Inayet joined the room. | 22:15:03 |
| 15 Nov 2024 |
 oak 🏳️🌈♥️ | I wonder what would be needed to get lineage-19.1 or -20.0 builds working? Does someone have a branch where the builds work? | 23:21:15 |
| atemu12 | 20 should work on master | 23:21:56 |
| atemu12 | 19 shouldn't be broken either but I didn't test it in a long time | 23:22:11 |
| atemu12 | It should definitely have worked before the LOS 20 merge | 23:22:34 |
| oak 🏳️🌈♥️ | I have Oneplus 8 Pro (instantnoodlep) and I'm running Robotnix build for lineage-19 from early 2023 and I thought it could be nice time to upgrade the version number a bit | 23:22:45 |
| atemu12 | I know that feeling ;-; | 23:22:57 |
| atemu12 | Although current LOS20 is quite up to date | 23:23:09 |
| atemu12 | (Well as up to date as Android 13 gets) | 23:23:18 |
| atemu12 | You're going to need to add it to the supported devices and run the device dirs updater though because I yeeted the hundreds of devices that I don't own | 23:24:13 |
| oak 🏳️🌈♥️ | I tried building lineage-19.1 and the build failed quite early, I then tried to patch few things and then the build was failing in some late phase of the webview, something like 80000/90000 files | 23:24:17 |
| atemu12 | Oh, yeah you're going to need to disable webview | 23:24:33 |
| atemu12 | Entirely unmaintained and wouldn't work even if it built | 23:24:48 |
| atemu12 | I've been meaning to yeet that too | 23:25:01 |
| atemu12 | And/or replace it with esay to maintain prebuilts | 23:25:17 |
| atemu12 | https://github.com/Atemu/robot-config/blob/d6c4357332d626b287e6711d622bb485a4db33ee/common.nix#L21-L23 | 23:25:52 |
| oak 🏳️🌈♥️ | When tried to make lineage-20.0 build I encountered other errors, such as the update scripts not pulling all the device and vendor files properly and I didn't yet dig too deep into it to see how to fix it. I just noticed that the repository and branch names are different when going to 20, sometimes the branch can be called linage-20 and then the script complaints it cannot find lineage-20.0 | 23:27:12 |
| atemu12 | I know ;-; | 23:27:35 |
| atemu12 | That's handled though | 23:27:39 |
| atemu12 | It works for my devices | 23:27:45 |
| atemu12 | Check whether all the source.dirs declared in the lineage.dependencies files are present | 23:28:15 |
| atemu12 | And the relevant vendor dirs for your device which is likely vendor_oneplus_instantnoodlep or something like that | 23:28:57 |
| atemu12 | (Not the vendor_oneplus, they've stopped using that in 20) | 23:29:15 |
| oak 🏳️🌈♥️ | Until lineage-19.1 all the devices were under this repository https://github.com/TheMuppets/proprietary_vendor_oneplus
but now with lineage-20 the have split the devices to separate repositories https://github.com/TheMuppets/proprietary_vendor_oneplus_instantnoodlep | 23:30:08 |
| atemu12 | Yup that's what I meant | 23:30:20 |
| oak 🏳️🌈♥️ | * Until lineage-19.1 all the devices were under this repository https://github.com/TheMuppets/proprietary_vendor_oneplus
but now with lineage-20 they have split the devices to separate repositories https://github.com/TheMuppets/proprietary_vendor_oneplus_instantnoodlep | 23:30:25 |
| atemu12 | The updater should do that | 23:30:42 |
| oak 🏳️🌈♥️ | The update script still tries to find it from the vendor_oneplus | 23:30:48 |
