[BUG] Can't scan any document

[EmpireMatrix]

Version

Latest 1.11.4.99

What platform are you using?

Android

OS Version

Android 12 on /e/OS 2.4-S

What happened?

I can't scan any document, each time the computing part takes ages. More than it should. I just can't use the app. I haven't registered any logs unfortunately as the OSS document scanner does not recognize it as a bug. Any ways to record a log ?

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[farfromrefug]

@EmpireMatrix really sorry to hear that.
Where did you install the app from?
So the app gets stuck on a loading dialog showing "computing" ?
It is going to be hard to investigate this without the actual phone :s What s your phone model?
I am thinking it could be an issue with androidx camera

[EmpireMatrix]

Hi @farfromrefug !

Thanks for your quick response, I've installed the app from the f-droid repo a month ago. I thought it was a known bug which would be patched in the future, but it was not, that's why I finally ask here.
Ye, the app does get stuck on the loading dialogue showing "computing". It actually worked a few times, but not enough to call it operational.
I have a Samsung Galaxy S7. I'm using open camera as the main camera app. I don't know if your app is using the camera2 or camerax api.
Good evening !

[Handwork5615]

Same thing happening on iOS. Documents detection takes too much time.

[farfromrefug]

@Handwork5615 what s your device/ios version?

[Handwork5615]

@farfromrefug iOS 18.0.1 iPhone 13 pro max

[farfromrefug]

@Handwork5615 thanks will try to reproduce it. Any details you can bring to help me? Does it happen all the time? when is it triggered....
thanks

[Handwork5615]

@farfromrefug just update the app and tried it, Please check the video, is it normal? https://drive.proton.me/urls/FH1MY3RH6M#CO3LrwCbIGKx

[farfromrefug]

@Handwork5615 thé auto scan Will cancel if it does not manage to "keep" the same document for some times (like corners changing too much).
So in your video I see that as not perfect but as it is implemented ;)
Might improve thar in the future