Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Auto Save Recordings #57

Open
1 of 3 tasks
jimsander opened this issue Nov 7, 2024 · 1 comment
Open
1 of 3 tasks

[BUG] Auto Save Recordings #57

jimsander opened this issue Nov 7, 2024 · 1 comment

Comments

@jimsander
Copy link

jimsander commented Nov 7, 2024

Bug Report

Description

Using GrapheneOS where the App is StorageScoped to "Download/FadCam"

Recordings aren't automatically saved to this folder instead have to select "Save to Gallery" in order to write them.

Steps to Reproduce

  1. Stop a Recording
  2. Select on FadCam Folder icon
  • Video file exists here
  1. View files under Download/FadCam
  • New recording doesn't exist
  1. In FadCam, select video, then Save to Gallery
  • New recording now exists in Download/FadCam

Expected Behavior

Would expect videos in the app's' Recording list to be automatically written to phone storage Download/FadCam

Actual Behavior

Recordings panel shows videos, but aren't found anywhere on phone's storage until Save to Gallery is selected

Logs

Some log snippets seem to suggest it is looking for device info to determine pathing?

235 11-07 21:06:58.260 19458 19458 W libc    : Access denied finding property "ro.product.name_for_attestation"
236 11-07 21:06:58.260 19458 19458 W libc    : Access denied finding property "ro.product.device_for_attestation"
237 11-07 21:06:58.260 19458 19458 W libc    : Access denied finding property "ro.product.manufacturer_for_attestation"
238 11-07 21:06:58.261 19458 19458 W libc    : Access denied finding property "ro.product.brand_for_attestation"
...
11-07 20:44:10.434 16926 16926 I auditd  : avc=type=1400 audit(0.0:4776): avc:  denied  { read } for  comm="app_process64" name="u:object_r:us    erdebug_or_eng_prop:s0" dev="tmpfs" ino=448 scontext=u:r:untrusted_app:s0:c21,c256,c522,c768 tcontext=u:object_r:userdebug_or_eng_prop:s0 tcla    ss=file permissive=0

Environment

  • Device: Pixel 7 Pro
  • OS: Android 15
  • App Version: 1.1.3

Additional Context

Would like to limit the scope of storage access any app.
Seems this one requires full media access.

To clarify, the actual path is not a plural Downloads as on other Android, but a singular Download

Priority

  • Low
  • Medium
  • High
@anonfaded
Copy link
Owner

Thank you for highlighting this.
I think i haven't mentioned this anywhere so some users think it's a bug. Actually this is a privacy feature so no one can access the recorded videos outside the app.

When we stop a recording, it is saved to the internal private storage of FadCam and it is only accessable from the 'Records' or folder tab in FadCam. When you select to save to gallery, then it saves to the Download folder and gallery. This will shows in the gallery 'FadCam' folder too separately.

Further more I'm planning on adding more privacy features so making it to auto save to device where anyone can access the videos, will make it less private. On Android 11 and above, google restricted the access to '/Android/data' folder so we are taking advantage of that.

And on Android 13 and above there were some issues so we tried adding more permissions and only after that FadCam was able to save videos to gallery. The logs also seem not related or necessary.

And on android 15 there was another main issue where video recording if exceeded 30/40 minutes, the app was getting killed by the system hence app would crash in-between the recording, and you are using that old version so i would suggest to try the beta version which has many improvements. Sharing the link for beta version:

https://github.com/s0llvan/FadCam/releases/tag/v1.2.0-beta

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants