- Aug 29, 2011
- 13
- 0
- 0
After updated my Note10+ (Exynos) to Android 10 and One UI 2.0, I found one serious problem:
Problem: When I inserted Samsung USB-C to USB-A adapter to the phone, then attach a USB drive (which work fine on the same phone when running Android 9, and the device was checked to make sure its functioning), Note10+ fail to auto-mount the USB drive. There are no response, and Samsung My Files app do not recognize the USB drive
Workaround: To make it work, I have to install Sandisk Memory Zone app from Google Play. after that, when I inserted the USB drive, Sandisk app detect the drive and I can transfer file using Sandisk app as usual. However, Samsung stock My Files app still do not show the USB drive as it should be
Another work around is to mount the USB drive with Paragon NTFS eFAT/NTFS for Android, then browse or transfer file with Total COmmander file manager. Still, Samsung My Files app do not show the mounted USB drive at all
I think there must be a bug with Samsung firmware that need to be fixed. I have reported this to Samsung Support staff over the live chat
Any friend experience the same problem? Or it is just me?
Problem: When I inserted Samsung USB-C to USB-A adapter to the phone, then attach a USB drive (which work fine on the same phone when running Android 9, and the device was checked to make sure its functioning), Note10+ fail to auto-mount the USB drive. There are no response, and Samsung My Files app do not recognize the USB drive
Workaround: To make it work, I have to install Sandisk Memory Zone app from Google Play. after that, when I inserted the USB drive, Sandisk app detect the drive and I can transfer file using Sandisk app as usual. However, Samsung stock My Files app still do not show the USB drive as it should be
Another work around is to mount the USB drive with Paragon NTFS eFAT/NTFS for Android, then browse or transfer file with Total COmmander file manager. Still, Samsung My Files app do not show the mounted USB drive at all
I think there must be a bug with Samsung firmware that need to be fixed. I have reported this to Samsung Support staff over the live chat
Any friend experience the same problem? Or it is just me?