Repository navigation
Conversation
added 4 commits
September 14, 2026 23:19
When 'iw dev' shows no interface after USB passthrough, look up the passed-through device's VID:PID in ChipsetDb and include the chipset name, driver, and notes in the DRIVER MISSING message instead of a generic hint.
- Only describe devices actually passed through (usb.isAttached). - Only append entries whose ChipsetInfo kind is WIFI (don't describe Ethernet/broadband dongles in a Wi-Fi error). - Add the trailing period only when the hint doesn't already end with one.
- EngineType: add availability helpers (rootAvailable/chrootAvailable/ rootlessAvailable) distinct from the active engine; Core gains chrootInstalled()/vmInstalled() - Onboarding: SlideEngineSelect becomes two independent checkboxes; AppIntroActivity.applyEngineFlow(Set<EngineType>) installs every selected engine; add jumpTo(Page) and fix the no-root -> rootless fallback so it lands on the VM install instead of skipping it - Dashboard: runtime selector (chroot/VM toggle) + dedicated chroot card with mount/unmount, alongside the VM card - MainActivity: unified dual-engine launch flow; drawer gating now locks root-only tools on !root, shared tools on active-engine-not-ready - Slide6Final copy reflects both engines See PLAN.md.
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
1 participant
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.
This pull request implements the groundwork for dual-engine (Root + Rootless) coexistence in the Stryker app, allowing users to install and use both engines side by side. The changes cover onboarding, dashboard UI, engine selection, and drawer/tool gating to support simultaneous chroot and rootless VM usage. The onboarding flow now supports multi-select engine installation, the dashboard displays both engines with independent controls, and runtime logic and UI gating have been updated to reflect per-engine availability and status.
Dual-engine model and runtime logic:
rootAvailableandchrootMountedstate tracking toMainActivity, and updated engine status refresh logic to distinguish between root, chroot, and VM availability. Drawer and fragment gating now lock tools based on the correct per-engine state, with user-friendly messages for each case. [1] [2] [3] [4] [5] [6] [7]Onboarding flow improvements:
Dashboard and UI updates:
Launch flow and engine selection:
Documentation:
PLAN.md, outlining the problem, goals, design, and verification steps.