!UUYziobKGGxpovWyAN:nixos.org

Robotnix

242 Members
Build Android (AOSP) using Nix | https://github.com/danielfullmer/robotnix74 Servers

Load older messages

SenderMessageTime
22 Dec 2024
@countoren:matrix.orgcountoren *

im running :

$ nix-build --arg configuration '{ device="instantnoodlep"; flavor="lineage-20.0"; }' -A img --impure

getting issue patching added instantnoddlep to the supported devices:

# SPDX-FileCopyrightText: 2020 Daniel Fullmer and robotnix contributors
# SPDX-License-Identifier: MIT

# Just so we have a single place to update this
[
  "taimen" "walleye" # Pixel 2 (XL)
  "crosshatch" "blueline" # Pixel 3 (XL)
  "bonito" "sargo" # Pixel 3a (XL)
  "coral" "flame" # Pixel 4 (XL)
  "sunfish" # Pixel 4a
  "bramble" # Pixel 4a (5G)
  "redfin" # Pixel 5
  "barbet" # Pixel 5a (5G)
  "instantnoodlep"
]

where can i find the device dir updater is?

23:11:32
@countoren:matrix.orgcountoren *

im running :

$ nix-build --arg configuration '{ device="instantnoodlep"; flavor="lineage-20.0"; }' -A img --impure

getting issue patching added instantnoddlep to the supported devices:

# SPDX-FileCopyrightText: 2020 Daniel Fullmer and robotnix contributors
# SPDX-License-Identifier: MIT

# Just so we have a single place to update this
[
  "taimen" "walleye" # Pixel 2 (XL)
  "crosshatch" "blueline" # Pixel 3 (XL)
  "bonito" "sargo" # Pixel 3a (XL)
  "coral" "flame" # Pixel 4 (XL)
  "sunfish" # Pixel 4a
  "bramble" # Pixel 4a (5G)
  "redfin" # Pixel 5
  "barbet" # Pixel 5a (5G)
  "instantnoodlep"
]

where can i find the device dir updater is?
Is it a devShell?

23:11:58
@countoren:matrix.orgcountoren *

im running :

$ nix-build --arg configuration '{ device="instantnoodlep"; flavor="lineage-20.0"; }' -A img --impure

getting issue patching added instantnoddlep to the supported devices:

# SPDX-FileCopyrightText: 2020 Daniel Fullmer and robotnix contributors
# SPDX-License-Identifier: MIT

# Just so we have a single place to update this
[
  "taimen" "walleye" # Pixel 2 (XL)
  "crosshatch" "blueline" # Pixel 3 (XL)
  "bonito" "sargo" # Pixel 3a (XL)
  "coral" "flame" # Pixel 4 (XL)
  "sunfish" # Pixel 4a
  "bramble" # Pixel 4a (5G)
  "redfin" # Pixel 5
  "barbet" # Pixel 5a (5G)
  "instantnoodlep"
]

where can i find the device dir updater is?
Is it in the devShell?

23:12:19
@countoren:matrix.orgcountoren *

im running :

$ nix-build --arg configuration '{ device="instantnoodlep"; flavor="lineage-20.0"; }' -A img --impure

getting issue patching added instantnoddlep to the supported devices:

# SPDX-FileCopyrightText: 2020 Daniel Fullmer and robotnix contributors
# SPDX-License-Identifier: MIT

# Just so we have a single place to update this
[
  "taimen" "walleye" # Pixel 2 (XL)
  "crosshatch" "blueline" # Pixel 3 (XL)
  "bonito" "sargo" # Pixel 3a (XL)
  "coral" "flame" # Pixel 4 (XL)
  "sunfish" # Pixel 4a
  "bramble" # Pixel 4a (5G)
  "redfin" # Pixel 5
  "barbet" # Pixel 5a (5G)
  "instantnoodlep"
]

where can i find the device dir updater?
Is it in the devShell?

23:15:03
@countoren:matrix.orgcountoren

found it. in the lingeaos folder running it, getting everything is up to date:

$ python update_device_dirs.py --branch lineage-20.0
device/fairphone/FP4 is up to date.
device/oneplus/cheeseburger is up to date.
device/oneplus/instantnoodlep is up to date.
device/google/sunfish is up to date.
vendor/oneplus/cheeseburger is up to date.
vendor/google/sunfish is up to date.
vendor/oneplus/msm8998-common is up to date.
vendor/oneplus/sm8250-common is up to date.
vendor/fairphone/FP4 is up to date.
vendor/oneplus/instantnoodlep is up to date.

running the build command again still result with patching issues specifically over the readonly patch

23:58:03
23 Dec 2024
@atemu12:matrix.orgatemu12 countoren: You're in luck actually because oak has the same phone. It's already supported: https://github.com/nix-community/robotnix/pull/258 08:49:50
@atemu12:matrix.orgatemu12You should be able to just build it08:50:08
@atemu12:matrix.orgatemu12 Your flavour is wrong though; it's just the flavour. Version is specified using androidVersion. 08:50:26
@oak:universumi.fioak 🏳️‍🌈♥️About the aapt2 issue, I've seen that13:32:38
@oak:universumi.fioak 🏳️‍🌈♥️I think I was able to work around that by not building the Chromium Webview from the source13:34:40
@oak:universumi.fioak 🏳️‍🌈♥️It is possible to fix that specific issue but then there are other issues with the Chromium Webview builder later in the process as well13:35:30
@oak:universumi.fioak 🏳️‍🌈♥️Mainly I found out last time I was looking at it, that during past few years the build process of Chromium has changed so that it required their own distribution of Python to be able to fetch all the source code, and the "flattening" of the tree has been broken13:41:20
@oak:universumi.fioak 🏳️‍🌈♥️Then I had this idea of leveraging the stuff that already exists for building Chromium for NixOS in nixpkgs but hadn't had enough time to look on that, by default it only builds few different variants for Linux13:42:01
@atemu12:matrix.orgatemu12Honestly getting a working prebuilt webview such as mulch is much higher priority14:09:32
@atemu12:matrix.orgatemu12Ideally it'd be the mulch overlay so that it's use upgradable at runtime14:10:11
@erahhal:homefree.hosterahhal set a profile picture.18:32:01
@oak:universumi.fioak 🏳️‍🌈♥️Yeah, I think we could have both, IIRC there's already a mechanism which you can optionally use to select one of the webviews. I don't think adding prebuilt webview should anyway be that big task18:54:08
@atemu12:matrix.orgatemu12Yup, just needs to be done18:54:50
@oak:universumi.fioak 🏳️‍🌈♥️Maybe I could also have a look on adding that, but I don't have my second test phone with me now during christmast time18:54:53
@atemu12:matrix.orgatemu12We should really get the emulator to work again too18:55:18
@oak:universumi.fioak 🏳️‍🌈♥️How does it work if you build LineageOS "normally" (I mean without Robotnix)? Does it have the prebuilt webview already added in repo manifest?18:55:45
@atemu12:matrix.orgatemu12It does but I think robotnix was interacting with it poorly 18:56:07
@atemu12:matrix.orgatemu12It'd always be disabled IIRC18:56:15
@atemu12:matrix.orgatemu12So you had to use the robotnix-provided webview18:56:28
@atemu12:matrix.orgatemu12Or none at all18:56:32
@atemu12:matrix.orgatemu12I'm also not sure the LOS webview is up to date18:56:46
@oak:universumi.fioak 🏳️‍🌈♥️Yeah actually now I recall, when I was updating those flavour repo.json files, I noticed it does fetch prebuilt webview, and I had some problems with it. (To fix the problems I had to remove the repo.json and do completely clean run of the update script.)18:57:44
@oak:universumi.fioak 🏳️‍🌈♥️The problem is that if you build without any webview at all, if you want to use GApps, you can't log into your google account if you don't have at least some kind of webview18:59:00
@oak:universumi.fioak 🏳️‍🌈♥️I was wondering why does it have to fetch the prebuilt webview if it's not going to be used anyway, but I guess the reason is that it's in the LineageOS's repo manifest19:00:33
@oak:universumi.fioak 🏳️‍🌈♥️https://github.com/LineageOS/android_external_chromium-webview_prebuilt_arm64 Well it's not that old19:04:24

Show newer messages

Back to Room ListRoom Version: 6