You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Typically I can disconnect and reconnect the device without unmounting aft-mtp-mount. I also can lock the device after connecting AFT.
But when I try to browse filesystem of a locked device, it not only hides all files (without even providing some README with a message about locked device), but also fails to restore files if I unlock the device (unlike GUI version), requiring me to remount.
Expected: when device is not accessible, show empty directory or README (or status or whatever) file mentioning that there is no device. If device is present, but locked, show message about locked device in the virtual file.
Ideally I also want AFT be authorized by key (like ADB) instead of by unlocked screen. But that's probably outside MTP feature set.
The text was updated successfully, but these errors were encountered:
Typically I can disconnect and reconnect the device without unmounting aft-mtp-mount. I also can lock the device after connecting AFT.
But when I try to browse filesystem of a locked device, it not only hides all files (without even providing some
README
with a message about locked device), but also fails to restore files if I unlock the device (unlike GUI version), requiring me to remount.Expected: when device is not accessible, show empty directory or
README
(orstatus
or whatever) file mentioning that there is no device. If device is present, but locked, show message about locked device in the virtual file.Ideally I also want AFT be authorized by key (like ADB) instead of by unlocked screen. But that's probably outside MTP feature set.
The text was updated successfully, but these errors were encountered: