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

Samsung Galaxy Note 10+ (snapdragon) stock cam doesn't generate proofs, and sharing proofs crashes #79

Open
shayaknyc opened this issue Aug 31, 2021 · 6 comments
Assignees

Comments

@shayaknyc
Copy link

Just updated to the latest release apk on my phone. Needed to force stop, clear cache and clear data to get it to even function. Doesn't detect photos taken with the phone's stock camera app, when sharing the photo just taken from stock cam with Proofmode, it says no proof generated. If I take a photo with a 3rd party app, and share the photo from stock gallery to proofmode, it gives me the option for basic or robust, tapping on either the first time, nothing happens, if I try to share the same photo again to proofmode, it gives me the option again for basic or robust, but on the 2nd attempt, shows that the app FC'd. Any ideas?

@n8fr8 n8fr8 added this to the Winter Sprint 2022 milestone Feb 3, 2022
@n8fr8
Copy link
Member

n8fr8 commented Apr 27, 2022

@shayaknyc
Copy link
Author

Ok, far more stable now. Can at least force generate a proof and can send basic and robust. However, there doesn't appear to be an actual proof generated when the photo is taken, only when tapping the generate button. This feels like it's not working properly......

@n8fr8
Copy link
Member

n8fr8 commented May 16, 2022

Yes, there seems to be an issue with the Galaxy devices in general, regarding the callback/event notification to ProofMode of when new photos and video are available. Working on it...

@shayaknyc
Copy link
Author

Cool, thanks for the update!

I'm no developer, but I think I read somewhere in the changelog that the image/video detection is based on scanning the DCIM folder? If that's true, I wonder if it's related to requesting extended storage permissions?

@n8fr8
Copy link
Member

n8fr8 commented May 16, 2022

That is one technique that is used. There is another where the OS itself is supposed to trigger "jobs" to process new media being available, but it seems like one of those features that doesn't work as expected across different flavors of Android.

@shayaknyc
Copy link
Author

shayaknyc commented May 16, 2022

Yeah, short of a wholesale reboot of the phone, the new media trigger rarely works on my samsung device. For example, if I used termux to download a video using yt-dlp (the fork of youtube-dl), I have to MOVE (not copy) the file to another directory using a file manager to "trigger" the scan of new media. IDK what's up with Samsung specifically, but that trigger rarely works.....

EDIT: I do use an app called FolderSync, that, until I gave it full storage permissions, it wouldn't detect new files in a watched directory to sync either. Once I was able to give it full storage perms, the app worked perfectly. Perhaps that's an alternative route to use.....

@n8fr8 n8fr8 self-assigned this Jun 7, 2022
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