Android · Research guidance. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
The comparison has changed
Google describes cache as temporary app data and notes that some apps can be slow the next time they open after it is cleared. A longer first opening is therefore not, by itself, proof that the network became worse or that a support action damaged the application. The test now includes rebuilding information the app previously retained.
Use a concrete observation
Suppose an interface initially loads programme artwork or a menu again after its temporary data was removed. Record whether the delay is in opening the interface, loading account information or playing a selected programme. These are illustrative stages to observe, not a claim that every player caches the same material in the same way.
Do not escalate on the first impression
Repeatedly clearing temporary data before every trial can keep recreating the cold-start condition. Instead, allow the app to complete its normal initial loading and compare a specific repeatable action. Keep the timing and error text if the fault remains. A single general impression that it felt slower offers little evidence about which stage failed.
Protect the storage distinction
Clear storage is a separate action that Google says permanently deletes app data. It should not be used merely because cache clearing made a first launch unfamiliar. Before any action that removes local setup, establish the legitimate recovery route. Describe which button was actually pressed so a later support conversation does not confuse a temporary refresh with a reset.
Questions, answered
Does a slower first launch prove the cleanup failed?
No. Google documents a possible slower next opening.
Should Clear storage be treated as another name for Clear cache?
No. The data consequences are different.