Support lazy transcode via ContentResolver
Currently, when apps open HEVC files via the filesystem directly, we
delay transcoding until the first read(2). Opens via ContentResolver
doesn't have this lazy behavior.
Now, since previous cls allow the FuseDaemon access to the actual uid
used during an open from the MediaProvider, we can provide the same
lazy transcode functionality. This change populates the
original (binder) uid used during ContentResolver opens and allows the
FuseDaemon transcode lazily on first read, similar to direct
filesystem access.
Removed @Ignored tests that were failing because of the lack of lazy
functionality
Test: atest TranscodeTest
Bug: 174655855
Change-Id: I72f39d3e35b975f0a386c055cbb10b4d21c21c86
2 files changed