I just downloaded the source, set break points to step through the control flow in the debugger and see how the app works where im interested in modifying it. when i attach the debugger to the process on my samsung galaxy s20, it crashes.
I'm a little out of my depth here with java and android. im primarily a c++ dev. A little help understanding control flow and getting the debugger to work?
My primary field is graphics, so i was hoping to make a better night shot with some black magic.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2024-09-04
My goal is to do some spatial temporal depth and color spells from the necronomicon or something. Im only interested that one part of the application😁
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not sure why it might crash. I usually start debugging by running Open Camera in debug mode from Android Studio (shift+F9).
Note that renderscript in deprecated in Android now, so although that's what currently used by Open Camera for things like NR mode, I'll be switching it over (first Java, then maybe with native code if necessary), see the HDRProcessor.use_renderscript flag.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2024-09-05
vendor.samsung.hardware.camera.provider has some seemingly proprietary methods causing errors.
I am investigating to see what keeps happening to produce the error and how i can check and disable that behavior when it fails. I think it might be from someone backdooring my test phone, but idk. FBI might not like me, and some hackers certainly dont.
also wow at letting people without accounts anon post. i didnt realize i wasnt logged in. lol....
But yeah, im investigating and seeing if i can write a fix in to it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just downloaded the source, set break points to step through the control flow in the debugger and see how the app works where im interested in modifying it. when i attach the debugger to the process on my samsung galaxy s20, it crashes.
I'm a little out of my depth here with java and android. im primarily a c++ dev. A little help understanding control flow and getting the debugger to work?
My primary field is graphics, so i was hoping to make a better night shot with some black magic.
My goal is to do some spatial temporal depth and color spells from the necronomicon or something. Im only interested that one part of the application😁
I'm not sure why it might crash. I usually start debugging by running Open Camera in debug mode from Android Studio (shift+F9).
Note that renderscript in deprecated in Android now, so although that's what currently used by Open Camera for things like NR mode, I'll be switching it over (first Java, then maybe with native code if necessary), see the HDRProcessor.use_renderscript flag.
vendor.samsung.hardware.camera.provider has some seemingly proprietary methods causing errors.
I am investigating to see what keeps happening to produce the error and how i can check and disable that behavior when it fails. I think it might be from someone backdooring my test phone, but idk. FBI might not like me, and some hackers certainly dont.
also wow at letting people without accounts anon post. i didnt realize i wasnt logged in. lol....
But yeah, im investigating and seeing if i can write a fix in to it.
My other samsung phone is telling me adbd W timed out while waiting for FUNCTIONFS_BIND, trying again.
this is a little confusing. will return to this tomrrow after i nap.
Is there a stack trace for the crash? Does Open Camera crash even when not running from the debugger (or even from Android Studio at all)?