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
I expected that photomanager could be used to view a picture stored on my OTG storage device.
Actual behavior
When I try to view a picture from my OTG device with A photomanager, the app opens but the picture is not shown. A plain white background shows instead.
from "a photo manager"-s directory-picker OTG directories with images (=i.e. from a usb-memory-stick attached to the android device) are initially invisible because these are not in in the media database because the the usbstick is not permanently available.
If you create a logcat as described in #118 we can see what exactly happens.
Do you have the same problems with other gallery apps?
It wasn't from a third party file manager per say. I just plugged in my OTG device and explored it directly from the option proposed on my notification panel and open a picture from the storage with AphotoManager. However, I tried with some file managers that I could access the OTG storage from and both gave different results.
On Amaze File Manager It says photo not found.
On Anexplorer It opened another picture.
I tried more tests and it showed photo not found when I accessed the OTG from my device default manager to view the the storage which is downloads. However I discovered that Aphotomaanager will show a blank screen if a picture has been accessed from the storage with another gallery app. Like Camera roll or simple gallery.
Expected behavior
I expected that photomanager could be used to view a picture stored on my OTG storage device.
Actual behavior
When I try to view a picture from my OTG device with A photomanager, the app opens but the picture is not shown. A plain white background shows instead.
Environment
Android Version : Android 7.0
A Photo Manager Version(Betta117.2-0.7.0-1800406-debug.apk)
Affected Module:
The text was updated successfully, but these errors were encountered: