Repository navigation
Conversation
…ata wait The OnePlus 7T Pro's ABL boots one header-v2 boot.img: the uncompressed Image behind ABL's "UNCOMPRESSED_IMG" tag with the DTB appended and in the v2 DTB section, the command line in the header. BOOT_METHOD=qcom-abl-v2 packs it. BOOT_IMAGES must be boot and UFS_RW userdata alone, and fastboot, flash and push refuse the method: there is no slot B of ours on that phone, and a human writes the image by fastboot after it has RAM-booted (device/hotdog/BRINGUP-M1.md). UFS can come up late there: after a RAM boot from the fastboot screen, userdata appeared 50 s after SSH, and the init's single look found no partition. INITRAMFS_USERDATA_WAIT (1-600 s) packs a limit, and the init then looks once a second with a line every 10 s, and lets the guard see the new partition before it checks it is writable. Every other phone is unchanged: the new code runs only for BOOT_METHOD=qcom-abl-v2, and without /etc/omamobile-userdata-wait the init looks once with no sleep, as before (tests/initramfs-root-policy.py checks both, and that no other descriptor packs the file). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…pycache__ A contributor's port builds its own packages with a local key (tools/local-key-init). build-inside removes the build's keyring from the image, so the phone didn't trust that key, and every refresh failed at [omamobile] with "key ... is unknown", omarchy update with it (hotdog, 2026-11-04). With --local, the key now ships as a keyring of its own (omamobile-local), which firstboot's pacman-key --populate trusts. Images built for any other channel are unchanged. phone-install-package no longer copies the laptop's Python caches: a bin/__pycache__ from a test run failed the shell's check() on the phone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- hexagonrpc 0.5.0.r20.gda7a374-2: the FastRPC file server the SLPI's sensor stack reads its registry and configuration through, with two fixes (the listener keeps serving after an unsupported method; rpcd serves /sys/project_info). device/hotdog/SENSORS-PLAN.md. - modemmanager 1.24.2-2.2: Arch's recipe with two fixes from upstream ModemManager, the netlink use-after-free (9317cbc4: it crashed on every second data connection) and the multiplexed-bearer cleanup assertion (0edcb916: it aborted at every shutdown with data on). device/hotdog/MODEM-PLAN.md. - mmsd-tng 2.6.4.r2.g3411171-1: the MMS daemon (a user service), built from a pinned upstream commit two past the 2.6.4 tag. Only omamobile-device-hotdog depends on them. The Pixels' modem stack, omamobile-mmd, conflicts with modemmanager, so no Pixel installs it; a phone that has Arch's modemmanager installed by hand would take this build from [omamobile] at its next update. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A community port of the OnePlus 7T Pro (hotdog, SM8150): the descriptor, the bring-up overlays and kernel config fragments, the plans with their runbooks and results, the device package and the camera table tools. On the owner's phone, from boot_a: display, GPU, touch, USB networking, Wi-Fi, buttons and the alert slider, haptics, the torch, all four cameras with autofocus and the pop-up, speakers, earpiece and microphones, calls, SMS, MMS and mobile data, GNSS through the modem's QMI LOC, ambient light through the SLPI, the screen off at the ear in calls, s2idle suspend and the optical fingerprint sensor. Each plan's status line and results give the kernel release and date. This phone has no stock slot: a slot switch once moved its UFS boot LUN onto mismatched bootloader firmware and took a full EDL restore, so Omarchy boots from boot_a, slot B is left as it is, and the human writes the boot image by fastboot after a RAM boot (BRINGUP-M1). slot-a-mark re-marks slot A successful in the GPT, by hand and with the owner's yes, after such a flash. Both are outside CONTRIBUTING.md §3.1 as it stands, and are the maintainer's decision; nothing here changes that section. The kernel (the SM8150 board on 7.3) is on local branches and not published yet. Nothing in this commit changes another phone. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… blanking omamobile-shell 0.2.136 takes the Mobile network page and the data tile through ModemManager, and turns the screen off at the ear in calls, only where a device package ships /usr/share/omamobile/mobile-network-modemmanager and /usr/share/omamobile/call-proximity. This package ships both, so the OnePlus 7T Pro keeps what it ran with shell 0.2.135 of the port's branch, and no other phone gets either. Also a README for the package, as the package layout asks (CONTRIBUTING §6.3): what each part is and the plan it came from. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
A community port of the OnePlus 7T Pro (
hotdog, SM8150): the descriptor, plans with runbooks and results, bring-up overlays and kernel config fragments, the device package, and what the port needs from the shared tools. Plans:device/hotdog/BRINGUP-M1.mdand the*-PLAN.mdnext to it.Commits:
BOOT_METHOD=qcom-abl-v2packs the one header-v2boot.imgthis ABL boots (Image behind ABL'sUNCOMPRESSED_IMGtag, DTB appended and in the v2 DTB section).fastboot,flashandpushrefuse it. New opt-inINITRAMFS_USERDATA_WAIT(1–600 s) for a UFS that comes up late.--local, the contributor's local key ships as its own keyring so the phone trusts its[omamobile]; no__pycache__copied to the phone.omamobile-device-hotdogdepends on.docs/DEVICES.mdrows.Nothing here changes another phone
qcom-abl-v2code runs only for thatBOOT_METHOD./etc/omamobile-userdata-waitthe init looks foruserdataonce with no sleep, as before.tests/initramfs-root-policy.pycovers the packing, the validation, and the init both ways.CHANNEL=localwith a key.modemmanageris installed by nothing but this device package. The Pixels'omamobile-mmdconflicts with it. One caveat: a phone that has Arch'smodemmanagerinstalled by hand would take this build (Arch's recipe plus two upstream fixes) from[omamobile].USB_HOST_PANIC=0init change. It's dropped here in favour of upstream's existingINITRAMFS_USB_RECOVERY=no.For the maintainer to decide: CONTRIBUTING.md §3.1
This phone has no stock slot. A slot switch once moved its UFS boot LUN onto mismatched bootloader firmware, and recovering took a full EDL restore. So here:
boot_a, and slot B is left untouched.fastboot flash boot_aafter it has RAM-booted.device/hotdog/slot-a-markre-marks slot A successful in the GPT, by hand and with the owner's yes, after such a flash. It records the sectors before and after.Both are outside §3.1 as it stands. Per §3.1, this PR doesn't touch CONTRIBUTING or AGENTS; the decision is yours.
Kernel
The kernel (the SM8150 board on 7.3, plus drivers: AW8697 haptics, s6sy761 ear detection, a fastrpc fix, the q6voice series) is on local branches and not published yet. It will follow as linux-omarchy-mobile PRs or a fork branch. Related PRs: #932 (shell, opt-in), #933 (GNSS, opt-in), #934 (libcamera sensors), #935 (Waydroid on Adreno), #936 (MMS, draft: changes every phone). This PR does not depend on them; device-hotdog 0.1.19 ships the opt-in files #932 reads, which do nothing without it.
Device and build
uname -r):7.3.0-rc6-omamobile-push1-g7539ca3e06f6(the port's local kernel, onboot_a)Checks (no phone needed)
tools/pr-check origin/mainpassestests/allpassestests/packages:omamobile-device-hotdogtest/allpassesversionbumped, and the new version is in the commit subjectCo-Authored-By:trailer, never aSigned-off-by:On the phone
INITRAMFS_USB_RECOVERY=noandINITRAMFS_USERDATA_WAIT=300replace the port'sUSB_HOST_PANIC=0and its unconditional 300 s wait);userdata. Not true for this phone: the boot image goes toboot_aby fastboot (by hand), andslot-a-markwrites slot A's GPT attributes (by hand). Linux itself writes onlyuserdata:UFS_RW=userdata, every other partition read-only, rmtfs read-only. Nothing weakens the storage guard or reads registers from userspace.tools/phone-smokereportphone-smoke: hotdog
Kernel
7.3.0-rc6-omamobile-push1-g7539ca3e06f6, tools at4b31273a, 1970-01-19T09:11Z.Packages: hyprland 0.57.0-3.3, libcamera 0.7.2-4.23, mesa 1:26.2.7-1, omacam 0.3.3-1, omamessages 0.2.2-2, omamobile-apps 0.2.3-1, omamobile-device-hotdog 0.1.18-1, omamobile-firstboot 0.1.6-1, omamobile-gnss 0.2.11-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.48-1, omamobile-owl-widgets 0.1.2-1, omamobile-settings 0.1.2-1, omamobile-shell 0.2.135-1, omamobile-voice 0.1.0-1, omamobile-waydroid 0.1.4-1, omaphone 0.2.3-1, omarchy 4.5.0-3, omatel-agent 0.2.4-3, quickshell 0.3.2.r7.g2b4501a-1
Notes on the report:
🤖 Generated with Claude Code