[OnePlus 11] kdrv3xc:
here's what progress i have made making op cam work on custom roms (well crdroid — the list of options for custom roms leaves much to be desired (which i hope to help change in the not too but probably distant future, but that's beyond the scope of this post)).

tl;dr's belong in the beginning of posts, so here it is:

i've got an almost 100% (let's call it 87%) working build of crdroid with opcam.

what doesn't work (yet):

portrait(bokeh) mode (though i have had it work rarely, but not enough for me to say it's working at all)

night mode — that just seems to get stuck, it's weird.

what pretty much works:

regular photo mode (with a caveat or two, see below)

regular photo mode front cam, actually all cams (still subject to the previously mentioned and yet to be explained caveats)

what always works:

professional mode 100% of the time every time(because it's professional...). professional mode uses the fewest sensors and algos of all the modes (because it's professional...)

burst shot works every time

videos work

all the other tertiary modes (except night)

all the filters/touch up feature work

concerning those caveats:

actually, let me start with what i found/think the issues are (...remaining issues, i'll leave the the sepolicy **** (pardon my language but neverallows can go kick rocks.) for another time because that makes me want to throw the whole thing in the river...also shared libraries, but those are much less irritating).

what issues remain i'm fairly confident in saying lie in postproc. either due to the algos not working properly, but i'm leaning towards the sensors misbehaving (if you can call them not working on a system they weren't designed for misbehaving.) causing the algos to not algo correctly.

and here's why:

photo mode: it always takes the picture, but it doesn't always process it beyond just a preview (which can't be exported or shared without digging through esoteric system file paths, and even then it's a post-procless (turns out a lot of OPcam's magic is in post-proc.) "thumbnail") if the lighting isn't up to its standards. if it's nice and bright, works like a charm. other than that you can just turn flash on and that makes it work too.

i plan to release a screen recording showing the different instances of it working and not working later on tonight (once i finish writing the book on procrastinating), and shortly after than i plan on releasing this build into the wild. though i have to clean some things up, revert my own personal customizations and figure out how to do commit messages beyond 'git commit -m '.'' or 'git commit -m 'cam stuff'', or the occasional 'git commit -m 'lfs sucks''. i'd also probably need to rebrand it in a way that would make it a little less obvious i'm totally kanging crdroid.

though it will have ksu built in to the kernel, and i prefer viper over dolby, so that's happening. gapps...maybe (it would be a nano gapps package if at all, they tend to get in the way of the build process sometimes), and a few other behind the scenes things (e.g., additional arm bins, less is more, essentially other quality of life cli/tools that devs/somewhat adept hobbyists would enjoy)

meanwhile, if anyone wants to test it out and help find/debug/troubleshoot any remaining issues message me and i'll send you a link. (i may not respond until much later tonight/tomorrow. i have to go do other things for a bit.) i think a maybe a fresh pair of eyes can hopefully see what i'm missing.

p.s actually here's a super quick screen recording i just took. i thought the first two photos wouldn't work due to being too dark and no flash enabled, but they did (note the watermark (i also forgot i had a custom watermark)...maybe i'm closer to 91% than 87%. the third picture is an instance where it did not postproc correctly (note the lack of a watermark, location and all the normal buttons being disabled). the fourth is pro mode which always works, though reminded me of an annoying bug where sometimes even when it does post-proc and save the photo correctly the camera just closes, but the photo is still exactly where it should be.

keep in mind this was just on the fly, and i'm no photographer and was pointing the camera at logcat output (a lot of red, right? don't worry about it.)

also it's a large video file so if it doesn't work here's a link:

New video by primes

photos.app.goo.gl