Check Jianlai piano sound, haptics and text insertion separately

Compare sound and haptics with a few nonsensitive keystrokes, changing one feedback condition per round.

1. Choose a suitable ordinary setting

Official screenshots present piano sound and haptics. Choose a time and place where observation will not disturb others. Open an ordinary saveable note, confirm Jianlai types normally, and record device class, version, theme and input language. Use a few nonsensitive characters, not real accounts, passwords or working messages. Preserve the original volume and feedback settings and identify their state before changing them. Do not jump to maximum volume: comfortable listening and clear records are more useful than loudness for separating feedback types.

2. Identify actual sound and haptic controls

Find settings explicitly related to key sound, piano sound or haptics, and inspect their labels and states. The screenshot supports those feedback capabilities, not identical timbres, intensity levels or a complete playable instrument in every version. Use only real options; do not invent mixing, recording or export. Read any actual additional requirement and record your choice. This task does not prescribe Full Access universally for every feedback function or infer privacy data flows from one switch.

3. Establish three baseline observations

With the original state intact, enter the sample and record text insertion, audible key sound and perceived haptics separately. They may differ; visible text does not establish the other two. If noise or device placement makes perception uncertain, record that limitation rather than the expected result. Music or a notification is not proof of key piano sound simply because it coincides with typing. Keep the sample small and fixed so the next round isolates one feedback condition.

4. Change sound alone in the same note

Save the baseline and change only one identifiable sound option, retaining haptics, theme, language and note. Enter the same characters and check both key-related sound and document text. Follow actual timbre labels without reporting precise frequency or tuning accuracy without measurement. If headphones or another output are connected, record the audible destination; an icon change is not heard evidence. For silence, preserve conditions and result before changing volume, permissions and theme together and losing the baseline.

5. Check haptics in a separate device-specific round

Save the sound round, restore an identifiable sound baseline and change only one available haptic option. Enter the same sample, recording haptics, audio and text separately. A click heard is not proof of a felt response. Hardware and system conditions vary; this task promises no identical effect across all iPads or accessories. Leave unsupported or uncertain conditions pending. Do not strike the screen harder to manufacture sensation, or change grip and settings together and claim a single cause.

6. Record system state separately from keyboard feedback

For an optional comparison of mute, volume or other system feedback state, finish the current round and record the original before making one reversible change. System and Jianlai options need not correspond one-to-one; Apple’s system-keyboard behaviour is not every third-party keyboard’s promise. Use the same sample and retain actual perceptions, then restore everyday settings. This observation measures neither audio latency, battery consumption nor haptic strength. One subjective impression is not a universal rule for every device model.

7. Diagnose silence, absent haptics and absent text separately

For silence, inspect selected sound state, extension identity, system volume and actual output. For absent haptics, inspect that option and device conditions. For absent text, inspect focus, candidate confirmation and field type. These are different paths, not one reinstall requirement. Change one condition while retaining failures and an original-state sample. Another keyboard sounding does not prove identical permissions or settings apply to Jianlai. Version, state, nonsensitive characters and observations can begin a report without sharing private input.

8. Restore suitable feedback and deliver three results

Restore desired sound, haptics and system volume, then reopen the note and enter a short marker. Deliver baseline, sound, haptic and any optional system rounds with text, audible and tactile results in each. Explain that piano feedback is not a recording tool, and audible response does not verify haptics. Keep unobserved devices and additional levels unknown. Recheck after relevant system, device or theme changes. A few keystrokes do not physically certify every feedback combination, accessory and long-term stability.

Related tutorials and sources

Languages and input, Input-boundary diagnosis.

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: piano sound and haptics.