Repository navigation
Conversation
|
@Somnius thank you. This is the change we agreed on #266, kept to husky's descriptor, with One thing CI caught: the husky package carries its own copy of the descriptor (
I've checked that with those, the package test passes on top of #285. If you'd rather push them yourself, that works too. Before I merge, please paste the Thanks also for tracking the long wait down to the portal and filing it separately. I've answered that on #277. |
|
Landed on main as 43223ce (squashed, authored by you), with the edits I described in my last comment. Thank you. |
|
@derekross here is the phone-smoke: huskyKernel
Packages: hyprland 0.56.2-5.1, libcamera 0.7.2-4.22, mesa 1:26.2.4-1.4, omacam 0.3.3-1, omamessages 0.2.1-1, omamobile-apps 0.2.2-1, omamobile-device-husky 0.1.7-1, omamobile-firstboot 0.1.2-1, omamobile-keyring 20261026-1, omamobile-mirror 0.1.1-1, omamobile-omarchy 0.1.31-1, omamobile-owl-widgets 0.1.2-1, omamobile-shell 0.2.100-1, omaphone 0.2.2-1, omarchy 4.0.6-1, omatel-agent 0.2.4-1, quickshell 0.3.2.r7.g2b4501a-1 The report names three kinds of new dmesg error: Local things on this boot that are not in main: a local service that sets the slot B successful bit in devinfo, a compositor background colour in I haven't filmed this boot, so I still can't say the frame stays up until Hyprland draws. |
|
@derekross a follow-up to my smoke report: I filmed a reboot of the same setup (husky package 0.1.7,
The video is 50 s long and I can send it if you want to see it. |
…#278) The Pixel 8 Pro's VENDOR_CMDLINE gains splash (with the Plymouth words from raven's tested line), so the shared init draws the static Omarchy frame at boot. quiet is left out, so the kernel text stays available during bring-up; removing splash brings the init text back. Maintainer edits at merge: the package's copy of the descriptor follows device/husky/device.conf (its test requires them to match), the comment line is wrapped, and the package version is 0.1.6. Closes derekross#278 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@derekross this is the husky-only
splashchange from #266.One line in husky's
VENDOR_CMDLINE, and the comment above it:You asked for
splash. I also added raven's Plymouth words next to it (plymouth.graphical,plymouth.force-scale=1,vt.global_cursor_default=0), because that is the line I tested the whole day, and I didn't boot withsplashalone. If you want onlysplashI'll cut the rest, but then it's an untested line. I left out raven'squiet, its console font and itsregulator_ignore_unused.What it does: the shared
initramfs/initseessplashin/proc/cmdline, writes/splash.bgra.gzto/dev/fb0right away and sends its own status lines to kmsg instead of tty0. The frame is made at image time bybin/omamobile: the logo from the Omarchy Plymouth theme (/usr/share/plymouth/themes/omarchy/logo.png, from theomarchy-settings4.0.6 package) centred on#1a1b26at husky'sPANEL_SIZE1344x2992, 16,084,992 bytes raw and about 19.7 KB gzipped.Getting the text back: drop
splashfrom the line and reflash, then the init's status lines show on tty0 again. Kernel messages weren't on the 8 Pro's screen before either:/proc/cmdlineon my phone ends up withconsole=null(the bootloader adds it), andconsole=tty0from our line is there too, but I haven't checked what that shows on this panel, so I won't promise more than "the init text comes back".Tested on my 8 Pro, slot B, kernel
7.3.0-rc6-omamobile-push1-g5899fec2bd28:/proc/cmdlinehas the new words, Plymouth started at 3.36 s and quit at 4.84 s, the display unit was up at 4.47 s and sddm at 4.85 s, and the video shows the Google logo, the Omarchy splash for about 8 s, a few seconds of plain dark navy, then the lock screen.That is not a test of this line alone. The boot also had three local things on the phone that aren't in this PR: the
plymouth-quitretain-splash drop-in (copied by hand from the raven/cheetah package; it'll be its own PR for the husky package), a user portal override, and a compositor background colour. What the screen shows between Plymouth quitting at 4.8 s and Hyprland starting is untested without the drop-in. I can flash this line alone and add that boot here if you want.Checks I ran:
tests/device-overlayspasses (the descriptor parses; its dtc part skipped, no dtc here),tests/images-layoutskipped for lack of AOSP mkbootimg.The long black wait after the splash before the lock screen is not from this line, it's #277.