Question Issue with NTFS Support on OnePlus 10 Pro with Latest Firmware

[meliorus]

Hello everyone,

I've encountered an issue with my OnePlus 10 Pro and was wondering if anyone else has experienced something similar. On the latest firmware, my phone does not detect an M2 drive when connected via USB 3.2. On previous versions of the firmware, the drive was visible and I could transfer data at speeds of 150-200MB/s, which was perfect for making backups.

I've tried installing NTFS handling apps from Google Play, but that hasn't solved the problem. The drive is then visible, but the transfers are very slow, which makes file transfers difficult.

Has anyone else encountered this issue on the latest firmware? Is there any way to resolve this issue, or is it a matter of a firmware update?

 

[meliorus]

Ok. I solve this problem. OnePlus support NTFS, but if you are have runing devloper mode then mount disk is not work.

 

[goodmaker]

Hello, on Oxygen OS 13.1, in Developer options, allow the option "Force allow apps on external" and you can use normal the M2 drive connected via USB.

 

[Some_Random_Username]

Hello everyone,

I've encountered an issue with my OnePlus 10 Pro and was wondering if anyone else has experienced something similar. On the latest firmware, my phone does not detect an M2 drive when connected via USB 3.2. On previous versions of the firmware, the drive was visible and I could transfer data at speeds of 150-200MB/s, which was perfect for making backups.

I've tried installing NTFS handling apps from Google Play, but that hasn't solved the problem. The drive is then visible, but the transfers are very slow, which makes file transfers difficult.

Has anyone else encountered this issue on the latest firmware? Is there any way to resolve this issue, or is it a matter of a firmware update?

I've been hitting similar issues with other drives not being visible at all (external HDD formatted in NTFS, USB key formatted in FAT32) on pretty much all 13.1 builds, and I'm flabbergasted that disabling the developer options as a whole worked around them? That said, upon investigating a bit more the matter I found that the root cause of the issue is having the "Disable permission monitoring" option being enabled.