Start with evidence
Run the tests that separate the likely branches
Decision table
What the observation changes
ObservationWhat it meansNext action
Faster cable improves the same local transferThe supplied USB 2 cable was the bottleneck.Use the faster rated cable for data-heavy workflows.
No improvement with known-good high-speed pathCable alone does not explain the result.Check host/storage and exact phone capability for the workflow.
Connection drops rather than merely runs slowlyA USB 2 rating does not explain instability.Test connectors/host ports and another known-good cable.
Sequence
Work from reversible checks to escalation
- 01
Confirm the cable is the original in-box cable.
- 02
Use the same local file/host for comparison.
- 03
Swap only the cable first.
- 04
Separate data speed from charging behavior.
Likely areas
Keep these branches separate
Included USB 2 cableHost portStorage/source bottleneckNetwork/cloud transfer
Repair boundary
When to stop changing settings
If multiple known-good direct paths fail to enumerate or disconnect, use Google support/hardware diagnostics.