That is, Android (Samsung Tablet) isn't able to see / load any storage locations served by uMTP-Responder from a Raspberry Pi 4B.
A computer reads it fine but Android won't. Have also tried writing an Android app, using MtpDevice. When calling MtpDevice.open() it will return a successful result but only after roughly 10 seconds. Nothing actually works though as asking for storage IDs returns null (again, after a long timeout). Other MTP devices like another Android device or GoPro work fine being read on Android.
Was using the latest release first but tried main just in case. Doesn't work.
That is, Android (Samsung Tablet) isn't able to see / load any storage locations served by uMTP-Responder from a Raspberry Pi 4B.
A computer reads it fine but Android won't. Have also tried writing an Android app, using MtpDevice. When calling
MtpDevice.open()it will return a successful result but only after roughly 10 seconds. Nothing actually works though as asking for storage IDs returns null (again, after a long timeout). Other MTP devices like another Android device or GoPro work fine being read on Android.Was using the latest release first but tried main just in case. Doesn't work.