Bug #2037
Videos shot on devices running android 4.3 dont create thumbnails
| Status: | Closed | Start date: | 10/08/2013 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: | vitriolix | % Done: | 0% | |
| Category: | - | |||
| Target version: | Beta 4 | |||
| Component: |
Description
If you are in storymaker, using either the primary method of creating stories, tapping the icon inside your story, opening the camera, recording, then saving the video, it returns to the same screen and the icon has disappeared, leaving only the "tap to start capture" text. The video exists in the gallery, and can be imported. this appears to happen in all clip sections. You can "import from gallery" without problem.
This problem has been documented on a nexus 4 running 4.3 and a nexus 7 running 4.3.
Associated revisions
Fixed No Thumbnails issue for android 4.3. Issue #2037
History
#1 Updated by vitriolix over 4 years ago
- Assignee set to vitriolix
I can reproduce this on the nexus 4, will try to find the cause...
#2 Updated by vitriolix over 4 years ago
as per conversation with Brain on email, this is a bug on 4.3 with older builds of storymaker, not a regression in new nightly builds
#3 Updated by vitriolix about 4 years ago
This looks like a big in Android 4.3 that we cannot work around, looking for options but until then:
Disclaimer: I'm the developer of FX File Explorer, which is a competitor to ES File Explorer.
My understanding of this issue is that ES File Explorer DOES NOT work around it. ES appears to work, but when you reboot, your files are gone.
I have not actually tried this. This information was provided to me by the user who reported this as a bug in FX File Explorer. His post on reddit:
"EDIT: Rebooted my device and found that all ES File Explorer modified items have reset. Created files disappeared and deleted items have come back. Potential warning as ES is aggressively caching actions that aren't being written to disk"
In my estimation, the only workaround is to use root access. Any file manager with root, on a rooted device, while using it in root mode, will be able to write to the external SD card.
And here's the important bit of my reddit posting on this issue in general:
There should theoretically be NO WAY to work around this issue without root access. The underlying problem is that in Android 4.3 (at least on the GS4 G.P. Edition), an application's UNIX user id needs to be part of the group "media_rw" in order to write to the removable "external" SD card.
The "WRITE_EXTERNAL_STORAGE" permission that almost every app out there uses is inadequate. That will get your app uid added to the group "sdcard_rw", which in the case of Android 4.3+GS4 G.P.E. is only good enough to write to the built-in storage.
The "WRITE_MEDIA_STORAGE" permission is required in order to have your app uid added to the group "media_rw". The problem is that this is a system protected permission. You can put this permission in your manifest, but you won't actually be granted it unless you're a system app. (Even tested this with FX to make sure, and it fails).
I very much hope this is an oversight rather than a deliberate action. Bear in mind though that Google does not appear to like the idea of Android devices with multiple storage locations. The first (or at least first popular) device with dual storage was the HTC Incredible, which came out in April of 2010, running Android 2.1 (API level 7). Android 4.3 (API level 18) is the 11th update of the API that has NOT ADDED any support for determining the locations of other user-writable storage. App developers are currently forced to scour /proc/mounts and use device-vendor-specific APIs to determine alternate locations.
...
#4 Updated by abeluck about 4 years ago
Wow, what a bug. That's unfortunate :(
#5 Updated by baghdadbrian about 4 years ago
I believe this is fixed now. I just tested on my nexus 4 running 4.3 without any issue.