ManYue device preferences: keep distinct phone and tablet controls

A handheld phone and a tablet on a stand may need different controls without separate libraries. Use device-specific settings for a few deliberate differences, then check their local scope and any book overrides. This concerns reader preferences rather than moving files or assuming universal sync rules.

Describe the two real reading positions

Try the actual phone grip and tablet-stand position. Identify only the differences you need, such as page count or menu action. Use the same readable edition and known scene on both devices. Align source and chapter structure first so content differences do not contaminate the preference comparison.

Find the device scope in general reader settings

Inspect the device-specific switch in general reader settings, noting its initial state. Book and device controls may appear in different contexts. If absent, retain the existing defaults. Enable the scope and change one observable item, such as landscape image count, then verify it before adding further differences.

Keep a recoverable phone baseline

Use a simple phone layout and verify forward, back, zoom and menu actions. Disable unnecessary shortcut conflicts and record key values for a later reset. There is no requirement to make the phone resemble the tablet at the cost of legibility. Choose controls around the actual grip and content.

Configure the tablet one difference at a time

On the tablet, change image count or menu action and inspect the same dialogue and spread. Stand distance matters more than fitting the maximum images. Single-page reading remains valid. After each difference, check that the phone retains its baseline; shared changes call for inspecting the edited scope before blaming account records.

Check for a per-book override

A book override can mask a device default. Inspect the sample’s scope and, after recording values, temporarily disable its override if needed. If only one book behaves differently, check that book before resetting the device. Compare another entry without overrides, and infer effective precedence from observed behaviour rather than assuming every option follows one rule.

Observe behaviour after normal sync

After configuration, follow your existing sync routine and reopen the sample on both devices. Record the actual outcome rather than deriving universal sync guarantees from the feature name. For an overwritten value, note values, direction and timing, then check its scope support. Keep provider changes and file-recovery tasks outside this layout test.

Record settings before disabling or clearing

Record useful local values before disabling device preferences. Treat a separate clear-device-values control according to its stated scope rather than as an account, shelf or bookmark reset. Inspect what re-enabling does. Change one device at a time while keeping the other as a working reference.

Acceptance and everyday maintenance

Finish with usable controls on both devices, understood scope and stable reopening. Keep isolated book exceptions separate. When grip or stand placement changes, adjust only the affected options. A small set of explained differences is more maintainable than two complicated configurations whose origins are forgotten.

Related guides and sources

ManYue per-comic preferences: change one vertical comic without changing others; ManYue two-device handoff: finish one session before starting the next.

Checked on October 27, 2026: ManYue public version 2.0.3 requires iOS / iPadOS 15.0 or later. Based on the official App Store description and Apple public version lookup. Reader options depend on the installed version and current context. This article describes a checking workflow without claiming step-by-step physical-device or private-server testing, or treating development features as released capabilities.