Identify the exact app
Record the Android device, software and app version and the smallest failing task. If one programme fails while others work, retain that scope before changing the whole player state.
Keep any developer-supported backup or account recovery information. Local data may contain preferences the service cannot reconstruct.
Read the documented difference
Google's Android guidance describes cache clearing as removing temporary data and storage clearing as permanently deleting app data. It also qualifies menu differences by manufacturer.
Its Pixel help provides a particular Apps and Storage & cache route. Do not apply that path blindly to every phone, tablet, television or Fire TV OS.
Choose the smallest justified action
A temporary-state problem may warrant a documented cache comparison. Record the original behaviour and allow the app to rebuild temporary data afterward. An initially slower launch can be part of that rebuild.
Do not assume that a button labelled clear storage is harmless because it sits beside cache. Read its confirmation and verify recovery requirements before a data-removing operation.
Repeat the same task
Use the same permitted item or interface action after the chosen change. Note whether launch, list import, playback or controls improved.
A result after clearing all data changes more than one condition; report that scope rather than claiming a specific cache defect was proven.
Preserve useful support evidence
Give the developer the app, device, exact action performed and resulting state. A sign-in screen after data removal is different from a playback failure.
No app data was changed here. The guide explains Google's documented distinction and does not guarantee a fix, restore favourites or certify any externally obtained player.
Keep storage capacity separate from working memory
A free-storage figure concerns persisted data, while working memory serves running applications. Clearing local files should not be promised as a universal cure for every crash, decoder limit or memory warning. If the app still closes during one specific operation, record that workload and message. Avoid repeatedly wiping configuration merely to increase a displayed number. A negative cache comparison is useful evidence and should lead to a narrower developer question, with the original setup preserved wherever possible. If the app returns to initial setup, report that new state explicitly instead of describing the previous playback symptom as unchanged.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Google Android storage guidance — Official current excerpt: temporary cache versus permanent app-data clear and manufacturer menu qualification.
- Google Pixel storage controls — Official current excerpt: Pixel-specific Apps, Storage & cache controls; not a universal Android TV path.
