Partially mitigated by the Claim button and PotentialSource (some bug fixes to come for this) so the user has to kick off the long running connect operation himself, it still seems that the actual connection operation takes an unusually long period of time - this is prior to the call to get the object list from the device at MtpDevice.Connect(RawMtpDevice)
Partially mitigated by the Claim button and
PotentialSource(some bug fixes to come for this) so the user has to kick off the long running connect operation himself, it still seems that the actual connection operation takes an unusually long period of time - this is prior to the call to get the object list from the device atMtpDevice.Connect(RawMtpDevice)