3787cdf982
Upgrade from 29.0.6.r14 to 35.0.2, switching to the Debian android-platform-tools source package layout which ships Debian-maintained make fragments and patch series under debian/system/. The old recipe carried a hand-maintained patch stack on top of a custom build system (rules_yocto.mk). The new recipe delegates to Debian's make fragments and applies only the OE-specific patches needed on top. Notable upstream changes between 29.0.6 and 35.0.2 (see release notes at https://developer.android.com/tools/releases/platform-tools): - adb: libusb is now the default USB backend on Linux (35.0.0) - adb: receive windowing for better throughput on high-latency links (33.0.3) - adb: graceful USB interface release on shutdown (35.0.2) - adb: wireless pairing and incremental APK installation support (30.0.0) - adb: adb transport-id for safe scripted device waits (30.0.2) - adb: fix shell exit code when device disconnects (35.0.0) - fastboot: download speed improvements up to 980MB/s on SuperSpeed+ (35.0.0) OE-specific changes: - adbd now drops privileges to a dedicated "adb" system user (matching Android's production security model); use "adb root" to escalate - adbd root/unroot/remount support added for non-Android targets - android-gadget-setup updated to mount functionfs with uid/gid ownership so the unprivileged adbd can access the FunctionFS endpoints - Depends on new android-libboringssl recipe for BoringSSL shared libraries - android-tools-adbd.service uses Type=notify so systemd waits for adbd's sd_notify READY=1 before proceeding with ExecStartPost - android-gadget-start now respects ANDROID_GADGET_UDC_DELAY (default 10s for non-systemd paths); the configfs drop-in sets it to 0 since adbd has already signalled readiness before ExecStartPost runs, eliminating the fixed delay on restart Tested on Raspberry Pi 4B (MACHINE=raspberrypi4-64) with USB-C OTG port, openembedded-core main branch, meta-openembedded master-next, kernel 6.12: - adb devices: device enumerated as 18d1:d002 - adb shell: connection as unprivileged adb user - adb root / adb unroot: privilege escalation and drop - adb reboot: device reboot via adb - adb forward: SSH tunnel through ADB verified - oe-run-native android-tools-native adb / fastboot: native host tools build Note: adbd only starts when /etc/usb-debugging-enabled exists on the target (ConditionPathExists in the service file). This is intentional — ADB is disabled by default for security. Create the file at image build time or at runtime to enable it. Requires kernel config for USB gadget support (e.g. via a .cfg fragment): CONFIG_USB_DWC2_DUAL_ROLE=y CONFIG_USB_GADGET=y CONFIG_USB_CONFIGFS=y CONFIG_USB_F_FS=y CONFIG_USB_CONFIGFS_F_FS=y Requires in local.conf for RPi4: RPI_EXTRA_CONFIG = "dtoverlay=dwc2,dr_mode=peripheral" AI-Generated: Uses GitHub Copilot (Claude Sonnet 4.6) Signed-off-by: Mihajlo Marinkovic <mmarinkovic@snap.com> Tested-by: Etienne Cordonnier <ecordonnier@snap.com> Co-authored-by: Etienne Cordonnier <ecordonnier@snap.com> Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
Layer maintainer: Khem Raj raj.khem@gmail.com