Set a Jianlai background while keeping keys and candidates readable

Use an authorised simple image to check background application without mistaking decoration for functional keys.

1. Preserve the original appearance

Record the current theme, background and key colours, preserving the original rather than deleting personal styles for one image. Prepare an ordinary note with common characters, digits and punctuation, and confirm Jianlai is active. Change only the background image while retaining language, Chinese layout and font. If restoration is unclear, first record the name and key choices externally. Without configuration export, do not claim a full backup; a preview screenshot does not preserve every parameter.

2. Choose an authorised low-distraction image

Choose an image you made, photographed or are authorised to use, preferably a simple scene without extreme tonal changes. Preserve the original and name a working copy clearly. Avoid identity documents, private conversations or account screens as backgrounds. No unfamiliar theme package is needed, and arbitrary formats or huge dimensions are not guaranteed. Establish that the device can read the image: a listed filename is not image content. Resolve unavailable source data rather than create empty placeholders repeatedly.

3. Use the visible background controls

Find the image entry through the installed theme/background controls and select the working copy using the provided flow. Background images are published, but identical photo-library, file-provider and cropping menus are not promised across versions. Verify image identity before selection and make an informed choice about any actual access request; the exercise does not require unrestricted access to a private library. Inspect the resulting preview separately from selection. Do not claim changes to zoom, blur or opacity controls that do not exist in the current interface.

4. Inspect text against the image in preview

In preview, inspect whether labels overlap a high-contrast subject and whether candidates and the space bar remain recognisable. Available space can affect cropping; verify image identity and placement before diagnosing corruption. If the preview shows only one key set, other pages still need active-input checks. Note three concrete difficult areas instead of only a preference. Separate lettering or button shapes inside the image from real controls: a decorative icon painted on a background does not add a keyboard function.

5. Check three text groups in an ordinary note

After the actual save/apply flow, redisplay Jianlai in the note and enter the prepared passage. Inspect main labels, candidates and digits/symbols separately, verifying inserted text instead of only an attractive preview. For unclear areas, record image region and label colour before also changing font, language or layout. Actual input checks activation. A border resembling a keycap does not prove changed touch targets, and larger-looking letters do not establish improved typing accuracy.

6. Improve one difficult condition at a time

Save the original observation, then choose one available intervention: a simpler image, or only a visible foreground-colour adjustment. Changing image, size and key style together cannot establish one cause. Return to the same note and passage, comparing the three difficult areas and retaining any unresolved pages. External cropping is separate preparation; preserve a copy and record its steps instead of attributing it to automatic editing by Jianlai. Restoring the original background is valid when a photo cannot be made readable.

7. Diagnose selection, application and display separately

If the image cannot be selected, inspect source readability. If only the containing-app preview changes, check application and active keyboard identity. If the image appears but text merges with it, inspect foreground/background relationships. These are not all unsupported-format failures. Record orientation or device changes separately instead of treating different-layout screenshots as one cropping defect. Retain version, source type and control feedback; a self-made nonsensitive illustration can explain a problem without sharing a private original.

8. Restore and deliver a readable result

Preserve original and working image, restore the old background or confirm the intended new style, then type a short marker. Deliver image identity, application, checks of the three text groups, one-variable changes and restoration. Keep untested layouts and orientations pending. Explain why decoration, visible labels and actual keys need different evidence. Recheck difficult areas after image, theme or device changes. One successful image does not certify arbitrary photographs, formats and every screen on physical devices.

Related tutorials and sources

Theme comparison, Font and size.

Checked on November 15, 2026 against Apple public lookup and the official App Store information and screenshots it lists: version 1.0.5, requiring iOS / iPadOS 16.0 or later, with identity and version cross-checked against China lookup. Tasks use published capabilities; identify actual controls in your installed version. External records are acceptable. Keep expectations separate from observations; no physical-device or universal input-environment test is claimed.

Official Apple screenshot: theme editing.