Making the value user-configurable would satisfy videographers needs too.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-08-11
A user who is leaving advertisement for 2nd grade app, accidentally with no shame at all, on the forums - is lame.
Keep sceen on is perfect function, has no ability to fail, ever. I have often a device in my bag or pocket with Open Camera active and set to force-on, intentionally so that I'm ready to fire rapidly. I do not want it to go off accidentally.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-08-20
did you just fart in my perfect code suggestion thread?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
instead of a FLAG_KEEP_SCREEN_ON ( https://sourceforge.net/p/opencamera/code/ci/8739313e14120a2d287e25b61b2f417762e6a352/ ) - use wakelocks to set a maximum value ("timeout") for the time a screen can be on.
If a user is leaving the device accidentally with screen-on in a bag, it will drain its battery (and run hot) until noticed.
I looked how others do it - graphenes Camera sets a countdown timer ("autoSleepTimer") of 5 Minutes after they came to a similar conclusion at https://github.com/GrapheneOS/Camera/issues/105#issuecomment-1079766915 -> "autoSleepTimer" introduced with https://github.com/GrapheneOS/Camera/commit/edd6765910464f804329055e0a2297634f078a92
Making the value user-configurable would satisfy videographers needs too.
A user who is leaving advertisement for 2nd grade app, accidentally with no shame at all, on the forums - is lame.
Keep sceen on is perfect function, has no ability to fail, ever. I have often a device in my bag or pocket with Open Camera active and set to force-on, intentionally so that I'm ready to fire rapidly. I do not want it to go off accidentally.
did you just fart in my perfect code suggestion thread?