Here is a simple MP3 player and now there's a reason to understand why the supplied cable has some kind of capacitor and is very short. These devices can be VERY finicky and any voltage fluctuation or difference is enough to cause issues.
Take for example the error messages from Linux Mint:
[804829.895414] usb 1-1: USB disconnect, device number 11
[806961.109030] usb 1-1: new high-speed USB device number 12 using xhci_hcd
[806961.237468] usb 1-1: New USB device found, idVendor=0781, idProduct=74f0
[806961.237481] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[806961.237488] usb 1-1: Product: Clip Jam
[806961.237494] usb 1-1: Manufacturer: SanDisk
[806961.237500] usb 1-1: SerialNumber:
[806961.239253] usb-storage 1-1:1.0: USB Mass Storage device detected
[806961.239844] scsi host9: usb-storage 1-1:1.0
[806962.237543] scsi 9:0:0:0: Direct-Access SanDisk Clip Jam PQ: 0 ANSI: 0 CCS
[806962.237901] scsi 9:0:0:1: Direct-Access SanDisk Clip Jam PQ: 0 ANSI: 0 CCS
[806962.238743] sd 9:0:0:0: Attached scsi generic sg1 type 0
[806962.239280] sd 9:0:0:1: Attached scsi generic sg2 type 0
[806962.241345] sd 9:0:0:0: [sdb] 8179712 1024-byte logical blocks: (8.38 GB/7.80 GiB)
[806962.241711] sd 9:0:0:0: [sdb] Write Protect is off
[806962.241721] sd 9:0:0:0: [sdb] Mode Sense: 00 c0 00 00
[806962.241896] sd 9:0:0:0: [sdb] Write cache: disabled, read cache: disabled, doesn't support DPO or FUA
[806962.245053] sd 9:0:0:1: [sdc] Attached SCSI removable disk
[806962.250838] sd 9:0:0:0: [sdb] Attached SCSI removable disk
[806962.544147] FAT-fs (sdb): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[807005.992800] usb 1-1: USB disconnect, device number 12
[807005.996567] sd 9:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[807005.996575] sd 9:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b ad 38 00 00 78 00 00 00
[807005.996578] blk_update_request: I/O error, dev sdb, sector 1530480
[807005.997266] sd 9:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[807005.997274] sd 9:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 00 0b ad b0 00 00 78 00
[807005.997277] blk_update_request: I/O error, dev sdb, sector 1530720
What was wrong?
It may look like a problem with your device, your OS config or even the USB port but more often than not it was the cable! I had two three-foot Tronsmart cables, 1 of them worked fine and the other didn't with this device. The way I found this out was by swapping the cables for fun and also by trying the device on other units.
When a device receives power by a pluggable USB cable you should always stick to the factory cable or use one that is the same length or shorter and of very high quality (even though these thick 18AWG gauge Tronsmart cables have worked fine for other uses!)
usb, mp, browse, filesystem, supplied, capacitor, devices, finicky, voltage, fluctuation, linux, mint, disconnect, xhci_hcd, idvendor, idproduct, mfr, serialnumber, clip, manufacturer, sandisk, detected, scsi, pq, ansi, ccs, generic, sg, sdb, byte, gb, gib, mode, cache, disabled, doesn, dpo, fua, sdc, removable, disk, fs, volume, unmounted, corrupt, fsck, hostbyte, did_no_connect, driverbyte, driver_ok, cdb, blk_update_request, dev, sector, os, config, tronsmart, cables, didn, swapping, receives, pluggable, factory, length, shorter, awg, gauge,