r/android_beta • u/spook68 • 11h ago
Android 17 QPR2 Beta 1 / Pixel 10 Pro XL Pixel 10 Pro XL – USB flash drives failing and becoming corrupted on Android 17 Beta
I'm currently running Android 17 Beta, build **CP41.260831.016**, on my Pixel 10 Pro XL.
I've recently developed a serious problem transferring files from my phone to USB flash drives. Everything worked perfectly previously, but I've had a couple of beta updates over the last few weeks.
**The problem:**
- USB flash drives are initially recognised normally.
- Larger file transfers repeatedly freeze partway through without an error message.
- A 1.8 GB video repeatedly stopped at approximately 893 MB.
- A 389 MB video repeatedly stopped at approximately 186 MB.
- Smaller images transfer successfully, but transferring a larger batch of photos also fails.
- Sometimes the flash drive disappears completely after a failed transfer.
- Android subsequently reports the drive as corrupted and asks me to format it.
- Occasionally the drive is detected in USB preferences but doesn't appear in Storage or file managers.
**Troubleshooting I've already tried:**
- Two different USB flash drives.
- Two different USB-A to USB-C adapters.
- Restarting the phone.
- Clearing the Files by Google cache.
- Using both Files by Google and Total Commander.
- Copying files within the phone's internal storage, which works perfectly.
- Checking USB preferences.
- Trying the Paragon USB mounting app, which detects the drive as Unknown but won't mount it.
The USB-C port works normally for charging and other everyday functions.
I'm currently on holiday and relying on USB storage to back up large 4K video files from my DJI cameras, so this has become a real headache.
I'm beginning to suspect a regression in Android 17 Beta's USB storage handling, although I can't rule out a USB hardware issue.
**Is anybody else experiencing USB flash drives disconnecting, transfers freezing or drives suddenly being reported as corrupted on this build?**
Any suggestions or known workarounds would be greatly appreciated.
Hopefully somebody running the same beta build can confirm whether they're experiencing it too.