Hi everyone, I am trying to make the systemimage and I get:

carlo@ubuntu2204:~/halium$ mka systemimage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
LINEAGE_VERSION=16.0-20221118-UNOFFICIAL-flounder
TARGET_PRODUCT=lineage_flounder
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=denver64
TARGET_2ND_ARCH=arm
TARGET_2ND_ARCH_VARIANT=armv7-a-neon
TARGET_2ND_CPU_VARIANT=denver
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-6.0.8-200.fc36.x86_64-x86_64-Ubuntu-22.04-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PQ3A.190801.002
OUT_DIR=/home/carlo/halium/out
============================================
ninja: no work to do.
ninja: no work to do.
No need to regenerate ninja file
build/make/core/definitions.mk was modified, regenerating...
[235/454] including halium/libhybris/compat/camera/Android.mk ...
cat: frameworks/av/media/libmediaplayerservice/Android.mk: File o directory non esistente
[238/454] including halium/libhybris/compat/media/Android.mk ...
cat: frameworks/av/media/libmediaplayerservice/Android.mk: File o directory non esistente
[454/454] including vendor/qcom/opensource/dataservices/Android.mk ...
art/build/Android.gtest.mk:98: warning: overriding commands for target `Stripped'
art/build/Android.gtest.mk:94: warning: ignoring old commands for target `Stripped'
art/build/Android.gtest.mk:107: warning: overriding commands for target `Uncompressed'
art/build/Android.gtest.mk:102: warning: ignoring old commands for target `Uncompressed'
art/build/Android.gtest.mk:117: warning: overriding commands for target `EmptyUncompressed'
art/build/Android.gtest.mk:112: warning: ignoring old commands for target `EmptyUncompressed'
art/build/Android.gtest.mk:122: warning: overriding commands for target `Uncompressed'
art/build/Android.gtest.mk:107: warning: ignoring old commands for target `Uncompressed'
art/build/Android.gtest.mk:127: warning: overriding commands for target `Uncompressed'
art/build/Android.gtest.mk:122: warning: ignoring old commands for target `Uncompressed'
frameworks/base/Android.mk:685: warning: overriding commands for target `/home/carlo/halium/out/target/common/docs/offline-system-sdk-referenceonly/api_diff/current/index.html'
frameworks/base/Android.mk:649: warning: ignoring old commands for target `/home/carlo/halium/out/target/common/docs/offline-system-sdk-referenceonly/api_diff/current/index.html'
frameworks/base/Android.mk:729: warning: overriding commands for target `/home/carlo/halium/out/target/common/docs/offline-system-sdk-referenceonly/api_diff/current/index.html'
frameworks/base/Android.mk:685: warning: ignoring old commands for target `/home/carlo/halium/out/target/common/docs/offline-system-sdk-referenceonly/api_diff/current/index.html'
frameworks/base/Android.mk:734: warning: overriding commands for target `/home/carlo/halium/out/target/common/docs/offline-system-sdk-referenceonly/api_diff/current/source.properties'
frameworks/base/Android.mk:690: warning: ignoring old commands for target `/home/carlo/halium/out/target/common/docs/offline-system-sdk-referenceonly/api_diff/current/source.properties'
libcore/JavaLibrary.mk:160: warning: overriding commands for target `/home/carlo/halium/out/target/product/flounder/obj/EXECUTABLES/rild_intermediates/.jar'
libcore/JavaLibrary.mk:145: warning: ignoring old commands for target `/home/carlo/halium/out/target/product/flounder/obj/EXECUTABLES/rild_intermediates/.jar'
ninja: error: '/home/carlo/halium/out/soong/host/linux-x86/framework/turbine.jar', needed by '/home/carlo/halium/out/soong/.intermediates/frameworks/base/hwbinder/android_common/turbine/hwbinder.jar', missing and no known rule to make it
11:24:22 ninja failed with: exit status 1

#### failed to build some targets (42 seconds) ####

Does anyone know how to fix this?

@carlo I surrender for now. Probably some dependencies are missing.

@nvriezen I did. Thanks for the help btw, I will ask on telegram and post the answer if I find it

There is a thing I didn't see the first time. When I run breakfast flounder it sayes: Trying dependencies-only mode on a non-existing device tree. What does it mean?

@nvriezen I will try again. The script is not returning errors found anymore so I will look for red lines

@nvriezen No, telnet does not work (host closes the session)

@nero355 It "worked" but still not booting. Mabye some depencencies are missing.

@nero355 I tried but got same error, but I may be onto something. I run halium-install in verbose mode and I got this error:

D: Chosen rootfs is ../ubuntu-touch-android9-arm64.tar.gz
D: Chosen android image is ../GSI/system/var/lib/lxc/android/android-rootfs.img
D: Chosen release is ut
D: Compress images before pushing: false

I: Writing rootfs into mountable image
Formatting '.halium-install-imgs.Jb3Is/rootfs.img', fmt=raw size=3221225472
mke2fs 1.45.5 (07-Jan-2020)
Discarding device blocks: done                            
Creating filesystem with 786432 4k blocks and 196608 inodes
Filesystem UUID: 80532b4d-daba-4b3e-a4ca-92c1846aaa89
Superblock backups stored on blocks: 
	32768, 98304, 163840, 229376, 294912

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 


gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
I: Cleaning up

So the problem is that, other than the boot image, nothing is being flashed. I have no idea of how to fix this though.

EDIT: ubuntu-touch-android9-arm64.tar.gz Was corrupted LOL, I am in pain.
EDIT 2: Now halium-install is really flashing the image. Will update you as soon as I try booting it up.

@nero355 I have not yet tried that. How should I do it?

I got some more logs so you can see all that's happening:

dic 16 15:37:02 fedora kernel: usb 1-2: new high-speed USB device number 47 using xhci_hcd
dic 16 15:37:02 fedora kernel: usb 1-2: New USB device found, idVendor=18d1, idProduct=d001, bcdDevice=ff.ff
dic 16 15:37:02 fedora kernel: usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
dic 16 15:37:02 fedora kernel: usb 1-2: Product: Failed to boot
dic 16 15:37:02 fedora kernel: usb 1-2: Manufacturer: Halium initrd    gr8rFiV8US03C03C00
dic 16 15:37:02 fedora kernel: usb 1-2: SerialNumber: Halium initrd Debug telnet on port 23 on rndis0 192.168.2.15 - also running udhcpd
dic 16 15:37:02 fedora kernel: rndis_host 1-2:1.0 usb0: register 'rndis_host' at usb-0000:03:00.3-2, RNDIS device, c2:83:f6:73:cf:50
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.3123] manager: (usb0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/28)
dic 16 15:37:02 fedora colord[1762]: CdMain: failed to emit DeviceAdded: failed to register object: An object is already exported for the interface org.freedesktop.ColorManager.Device at /org/freedesktop/ColorMan>
dic 16 15:37:02 fedora systemd-udevd[9243]: Using default interface naming scheme 'v249'.
dic 16 15:37:02 fedora kernel: rndis_host 1-2:1.0 enp3s0f3u2: renamed from usb0
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9745] device (usb0): interface index 28 renamed iface from 'usb0' to 'enp3s0f3u2'
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9925] device (enp3s0f3u2): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9941] device (enp3s0f3u2): carrier: link connected
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9963] settings: (enp3s0f3u2): created default wired connection 'Connessione via cavo 1'
dic 16 15:37:02 fedora NetworkManager[1092]: <info>  [1639665422.9999] device (enp3s0f3u2): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0024] policy: auto-activating connection 'Connessione via cavo 1' (bc8c336a-c799-33eb-833a-f38be331eca4)
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0035] device (enp3s0f3u2): Activation: starting connection 'Connessione via cavo 1' (bc8c336a-c799-33eb-833a-f38be331eca4)
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0039] device (enp3s0f3u2): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0047] device (enp3s0f3u2): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0142] device (enp3s0f3u2): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0145] dhcp4 (enp3s0f3u2): activation: beginning transaction (timeout in 45 seconds)
dic 16 15:37:03 fedora avahi-daemon[982]: Joining mDNS multicast group on interface enp3s0f3u2.IPv6 with address fe80::aef4:93bf:a70f:ef26.
dic 16 15:37:03 fedora avahi-daemon[982]: New relevant interface enp3s0f3u2.IPv6 for mDNS.
dic 16 15:37:03 fedora avahi-daemon[982]: Registering new address record for fe80::aef4:93bf:a70f:ef26 on enp3s0f3u2.*.
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.0363] dhcp4 (enp3s0f3u2): state changed unknown -> expire
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1035] dhcp4 (enp3s0f3u2): state changed expire -> bound, address=192.168.2.61
dic 16 15:37:03 fedora avahi-daemon[982]: Joining mDNS multicast group on interface enp3s0f3u2.IPv4 with address 192.168.2.61.
dic 16 15:37:03 fedora avahi-daemon[982]: New relevant interface enp3s0f3u2.IPv4 for mDNS.
dic 16 15:37:03 fedora avahi-daemon[982]: Registering new address record for 192.168.2.61 on enp3s0f3u2.IPv4.
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1055] device (enp3s0f3u2): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1092] device (enp3s0f3u2): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1095] device (enp3s0f3u2): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
dic 16 15:37:03 fedora NetworkManager[1092]: <info>  [1639665423.1106] device (enp3s0f3u2): Activation: successful, device activated.
dic 16 15:37:03 fedora systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
dic 16 15:37:05 fedora ModemManager[1074]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb1/1-2': not supported by any plugin

I can see that the device is not booting and also when I try to connect via telnet the connection is dropped by the device.

@nero355 I've just tried and it did not work. Also I forgot to say that halium-install does not let me set the password.

I've managed to get some logs via journalctl:

dic 16 15:19:45 fedora gvfsd[8127]: Device 0 (VID=18d1 and PID=d001) is a Meizu Pro 5 Ubuntu Phone.
dic 16 15:19:47 fedora ModemManager[1074]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:08.1/0000:03:00.3/usb1/1-2': not supported by any plugin
dic 16 15:19:52 fedora gnome-shell[2194]: Window manager warning: META_CURRENT_TIME used to choose focus window; focus window may not be correct.
dic 16 15:19:55 fedora systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.

Also I have no idea why it gets the wrong device.

Hi everyone, I was almost successful in building for nexus 9. I am stuck on the Google splash screen and can't proceed. I tried:

sudo ip link set enp3s0f3u2 address 02:11:22:33:44:55 

But I got: RTNETLINK answers: Device or resource busy

So I decided to try with

telnet 192.168.2.15

But i got: no connection to host.

How can I get an error log?

I should also say that halium-install in my case was very fast but gave me no errors, so mabye is some bug related to that?

Thanks.

I am trying to port halium 10 to Samsung s4 international (jfltexx) and I keep getting this error when launching mka halium-boot. Any help is appreciated.

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=10
LINEAGE_VERSION=17.1-20210827-UNOFFICIAL-jfltexx
TARGET_PRODUCT=lineage_jfltexx
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.11.0-27-generic-x86_64-Ubuntu-20.04.2-LTS
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=QQ3A.200805.001
OUT_DIR=out
PRODUCT_SOONG_NAMESPACES=vendor/samsung/jf-common device/samsung/jf-common vendor/samsung/jfltexx hardware/qcom-caf/msm8960
============================================
FAILED: ninja: unknown target 'halium-boot'
22:13:10 ninja failed with: exit status 1

#### failed to build some targets (3 seconds) ####

@flohack thanks a lot, I will do. BR

@flohack Ok, thanks, now I understand better. So I will add a line that goes something like:

<project path="kernel/samsung/jf" name="android_kernel_samsung_jf" remote="LineageOS" revision="lineage-16.0" />

Thanks.

@flohack I have created the repo manifests. For example a rough manifest for jfltexx is

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="LineageOS"
    fetch="https://github.com/LineageOS"
    revision="los-16.0" />
<!--Dependencies-->
<project path="device/samsung/jfltexx" name="android_device_samsung_jfltexx" remote="LineageOS" revision="lineage-16.0" />
<project path="device/samsung/jf-common" name="android_device_samsung_jf-common" remote="LineageOS" revision="lineage-16.0" />
</manifest>

I have created it under BUILDDIR/halium/devices/manifests/samsung_jfltexx.xml

The jf-common line comes from the lineage.dependencies file.

@lakotaubp I get the same error both for nexus 9 and for samsung s4. I initially speculated that it was a nexus 9 related error, maybe due to the manifest or something, but got the same result with the s4.

I can't understand how to check the kernel config and apply the changes as shown as in the Modify the kernel configuration part of the porting guide. I guess it might not be generating since under BUILDDIR/kernel/ folder I cannot find my device. Am I missing something? I am new to the argument of porting so please be kind if this was a trivial question. Thanks!

@flohack said in Can't do: hybris-patches/apply-patches.sh --mb, I get error: the previos rebase directory exists but an mbox was specified:

git am --abort

I did a sync and it got stuck in /bionic because it had not finished last time. I entered the bionic folder and run git am --abort. Then i went in the BUILDDIR folder and rerun repo sync and it seems to have fixed the problem. Thanks a lot!!

@lakotaubp Hi, too mutch time has passed and I can't edit anymore. I don't know if an admin can modify the title now.