Without BOARD_WLAN_DEVICE, libwifi-hal's fallback returns
WIFI_ERROR_NOT_SUPPORTED from init_wifi_vendor_hal_func_table, which
causes the AIDL wifi HAL (com.android.hardware.wifi) to fail at startup:
E android.hardware.wifi-service: Can not initialize the vendor
function pointer table
E android.hardware.wifi-service: Wifi HAL start failed
The bcmdhd implementation of init_wifi_vendor_hal_func_table uses
purely generic nl80211 — it scans /sys/class/net/ for phy80211
interfaces, creates netlink sockets, and resolves the nl80211 family
ID via genl_ctrl_resolve(). There are no bcmdhd-specific IOCTLs or
vendor commands in the core startup path (wifi_initialize, wifi_cleanup,
wifi_event_loop, wifi_get_ifaces, wifi_get_iface_name); the vendor
commands are only used for optional advanced features (RTT, NAN, etc.)
that this device does not use.
- Rename product makefile: lineage_tart.mk (PRODUCT_NAME=lineage_tart)
- Update AndroidProducts.mk for lineage_tart lunch target
- Change androidboot.hardware and TARGET_BOOTLOADER_BOARD_NAME to tart
- Rename ramdisk files: fstab.tart, init.tart.rc, ueventd.tart.rc
- Update device.mk ramdisk copy targets for tart names
- Update vendor makefile reference to tart-vendor.mk
- Update extlinux.conf kernel cmdline with tart hardware ID
- Fix bluetooth device name in vendor.prop
Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
TARGET_NO_KERNEL prevented INSTALLED_BOOTIMAGE_TARGET from
being defined, breaking the target-files packaging step.
Use BOARD_KERNEL_IMAGE_NAME instead to satisfy kernel.mk.
Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
The kernel is prebuilt and boot image is assembled by mkbootimg.mk
which directly copies Image from the kernel path. Bypass LineageOS
kernel.mk with TARGET_NO_KERNEL since we handle it entirely via
BOARD_CUSTOM_BOOTIMG.
Set BOARD_KERNEL_IMAGE_NAME and TARGET_PREBUILT_KERNEL
for the prebuilt mainline 6.15 kernel Image.
Copyright (C) 2026 Brendan Szymanski <hello@bscubed.dev>
