Kozzm0 McAlister
Lurker
Not rooted, runs Android 11. When connected to PC (tested on ubuntu 20.014 and windows 10) set in preferences to "file transfer." "USB controlled by" setting remains on "this device," fails if attempt to switch to "connected device."
Connected device succeeds at mounting phone, and can freely navigate the filesystem remotely. However, nearly any attempt copy a file of significant size (i.e. > 1MB) from the filesystem to the connected device freezes at about 2% completion, then ends in an error. In linux this is "libmtp error: Could not get file from device." The same occurs if the device is unmounted and an adb pull is called in terminal: hangs nearly immediately and eventually fails. This doesn't happen the other direction: files from the connected device transfer successful (and quickly) to the phone filesystem.
After the error occurs in mtp, the phone filesystem is no longer browsable from the connected device, and attempting to unmount it results in "device busy" and it takes a few minutes to unmount. When remounted it is browsable again, but file copy attempts have the same result.
This occurs on different machines, and different phones transfer files correctly with those machines. This phone is new but was working properly yesterday. There is no visible damage to the phone or usb-c cable, both of which are new or nearly new. So the problem narrows down to software on the phone conflicting with the transfer.
What could that be? Which apps could do this, or result in it if disabled/depermissioned?
Connected device succeeds at mounting phone, and can freely navigate the filesystem remotely. However, nearly any attempt copy a file of significant size (i.e. > 1MB) from the filesystem to the connected device freezes at about 2% completion, then ends in an error. In linux this is "libmtp error: Could not get file from device." The same occurs if the device is unmounted and an adb pull is called in terminal: hangs nearly immediately and eventually fails. This doesn't happen the other direction: files from the connected device transfer successful (and quickly) to the phone filesystem.
After the error occurs in mtp, the phone filesystem is no longer browsable from the connected device, and attempting to unmount it results in "device busy" and it takes a few minutes to unmount. When remounted it is browsable again, but file copy attempts have the same result.
This occurs on different machines, and different phones transfer files correctly with those machines. This phone is new but was working properly yesterday. There is no visible damage to the phone or usb-c cable, both of which are new or nearly new. So the problem narrows down to software on the phone conflicting with the transfer.
What could that be? Which apps could do this, or result in it if disabled/depermissioned?
Last edited: