Appearance and recovery
Check light/dark readability in 调调 with the music theme fixed
Compare light and dark states on one track and theme, retaining page-level differences rather than ranking modes.
On this page
Compare light and dark states on one track and theme, retaining page-level differences rather than ranking modes.
1. Record theme, appearance and system state
The public description provides light/dark appearance, while the new release adds music themes. Do not merge those into one assumed switch. Record installed version, music theme, actual appearance and system state, preserving originals. Use one authorised playable local track with fixed artwork/source. If theme and appearance are unclear, establish an identifiable baseline rather than toggle everything to produce two pictures. This compares readability, not audio quality, power consumption or playback performance.
2. Choose three repeatable inspection areas
Use player title/controls, available lyrics and upcoming queue as repeatable references, noting a return location for each. Missing lyrics are missing data, not proof that dark mode erased text. Preserve queue order. An external three-row record can separate title, icon, current-line and overlap observations without an automatic comparison report. Keep device and orientation fixed: a phone player and another tablet’s lyric view are not a one-condition comparison.
3. Use only actual appearance choices
Identify real light, dark or system-following choices in the installed appearance controls. Published scope does not promise identical names or an independent switch everywhere. If appearance follows the system, record that condition without inventing an extra in-app menu. Establish one identifiable state and revisit all three references, retaining the music theme. Unavailable scheduled appearance, theme automation or independent per-page modes are not mandatory steps; follow actual controls and scope.
4. Record text/background relationships in the light round
In an identifiable light state, inspect title, artist, controls, lyric text/current line and selected versus ordinary queue entries. Record actual display rather than attribute ambient light or brightness changes to theme colours. If a region stays dark, inspect theme styling and setting scope instead of editing a screenshot to match expectations. An unchanged area is a valid observation, not proof that light appearance is absent. Distinguish global state from local colours retained by the theme.
5. Keep content fixed for the dark round
Save the light round, change only to an identified dark condition and revisit the same track, lyric passage and queue position. Inspect text, background, controls and current-item recognition without requiring a simple colour inversion. Bright artwork need not darken, and missing source lyrics are not a colour failure. Restore the sample after a natural track transition. Keep content and appearance changes separate, and leave unvisited pages pending instead of using one player screenshot to complete all three rows.
6. Keep readability preferences conditional
Record a specific personal difficulty, such as a pale icon merging with its background or unclear selection, together with device, orientation and scope. This is a readability observation, not clinical advice, accessibility certification or a universal preference. A different music theme needs another round after preserving the two appearance states. Do not also change font, artwork and brightness and attribute everything to light/dark mode. If adjustments are unavailable, return to a readable existing choice rather than invent unlimited colour/font controls.
7. Diagnose unchanged state separately from missing data
For apparently unchanged appearance, inspect selection, system-following conditions and local theme styling. For absent lyrics, inspect source data. For visible controls with silence, inspect pause/output. These are distinct diagnoses, not one dark-mode failure. Restore one condition and retain prior positions/feedback instead of reinstalling or clearing music. If automatic system state changes mid-round, record the interruption and repeat a clear comparison. Unknown scope remains pending rather than a claim that every display issue was repaired.
8. Restore the original and deliver all three comparisons
Restore desired system and app appearance and verify theme, track and queue identity. Deliver light/dark observations for all three references, pending areas, system-following scope, unchanged local styling and restoration. Explain theme, artwork, appearance and audio data separately rather than claiming a mode protects eyesight. Recheck key areas after device, theme or version changes while retaining earlier identities. Two personal rounds do not certify every page, environment or user’s display performance.
Related guides and sources
Music-theme comparison, Larger-screen available space.
Checked on November 16, 2026: Apple’s Russia lookup, cross-checked against China, lists 调调 1.0.1, requiring iOS / iPadOS 17.6 or later. The official store release notes add Home Screen widgets and music themes. Tasks follow published scope; identify controls and available choices in the installed version. Keep expectations separate from actual observations. No completed physical-device or private-server test is claimed.