snlavaiseandClaude Sonnet 5
187b52aa12
rtwo is Android 13: the generic first-stage ramdisk lives in init_boot, not boot.img, and the bootloader always assembles the initramfs from init_boot + vendor_boot regardless of what boot.img contains. So the dubai-style monolithic v2 boot.img cannot work here - keep header v4 and replace boot (kernel), vendor_boot (dtb+cmdline+initramfs) and init_boot (generic ramdisk) all with pmOS content. Combine everything learned: - header v4, append_dtb off (dtb in vendor_boot) - earlycon on the cmdline (Motorola ABL requirement, from dubai) - raw Image kernel (stock LineageOS rtwo evidence) - base 0 + explicit offsets + os_version/os_patch_level - 24 MB zero dtbo (dubai trick) - the Sony-Xperia-1-V-modelled minimal .dts (no /memory, no msm-id, no speculative regulators) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QF5HebjUsRaxbW4cBX6HJP
postmarketOS aports repository
This repository contains the APKBUILD files for postmarketOS-specific packages, along with the required patches and scripts, if any.
There are many more packages defined in the Alpine Linux aports on which these packages depend.
Helpful resources:
- Issues
- How to create a package
- APKBUILD reference
- pmaports commit style
- Approval rules
- Alpine Linux aports
- Alpine Linux package search
- postmarketOS package search
Git Hooks
You can find some useful git hooks in the .githooks directory.
To use them, run the following command after cloning this repository:
git config --local core.hooksPath .githooks