Hi,
I would like to ask about the Multi Cam Access, Main/Wide/Tele.
Do this depend exclusively from the phone's manufacturer?
AFAIK, some allows the access, i guess to the API to 3rdP Apps, others do not, but IDK whether OCam can access them at all or not.
Also read about CameraX API, is Mark working also on this?
Would this help on access the whole pack of back cams?
Any link to clarify this questions is welcomed
Thank you
Last edit: ZAlex 2026-03-26
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, yes it depends on the manufacturer. Open Camera supports all the relevant APIs (accessing multiple cameras, automatically switching via zooming in and out; accessing specific "lenses") but some manufacturers still don't expose to third party applications via the Android API.
I did look at CameraX a few years ago, but I don't think it would help here (CameraX still uses the Android API).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also,
I've forgotten to mention, my current device it's: RealMe 14 Pro+ | RUI6 | A15
There's a GCam, AGC 9.0 that it's capable to access all 3 back cams.
Would be related to the fact that it shares internal components/signatures with the OS?
BTW,
It resets the app itself to interchange between one and another, so if you're on Tele x3, you can go to Main without the restart, being mostly useless for video recording.
Last edit: ZAlex 7 days ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What are package names (multiple apks in one release)? »
Why are different package names needed?
Package names are usually needed to access all cameras and/or to enable features like Google Lens.
Some brands (eg: OnePlus, Samsung, etc) restrict access to all cameras. They have a "whitelist" of apps (package names) that can access those cameras, so modders release their versions with package names that are on those lists.
For example, OnePlus usually allows org.codeaurora.snapcam (sometimes referred to as "snap"), so that's what's usually recommended for OnePlus devices:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not quite sure what methods that the GCam ports use, but I note they have the advantage that there are many versions of these often tailored made/supported for specific devices, In theory there are hacky backdoor methods that work on some devices, but will break or give buggy behaviour on other devices - the link above is indeed useful, so yes that explains why they need different versions.
Renaming the package name requires some kind of development tools (either rebuilding from the source, or possibly there are some tools/methods that claim to work on the APK but I don't have experience of them).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2 hours ago
Generally speaking, someone would have to look into this, starting with the simplest things—like changing the “applicationId” to begin with.
You might as well ask the modders how they figured it out.
Maybe someday someone will do something about it.
Hi,
I would like to ask about the Multi Cam Access, Main/Wide/Tele.
Do this depend exclusively from the phone's manufacturer?
AFAIK, some allows the access, i guess to the API to 3rdP Apps, others do not, but IDK whether OCam can access them at all or not.
Also read about CameraX API, is Mark working also on this?
Would this help on access the whole pack of back cams?
Any link to clarify this questions is welcomed
Thank you
Last edit: ZAlex 2026-03-26
Hi, yes it depends on the manufacturer. Open Camera supports all the relevant APIs (accessing multiple cameras, automatically switching via zooming in and out; accessing specific "lenses") but some manufacturers still don't expose to third party applications via the Android API.
I did look at CameraX a few years ago, but I don't think it would help here (CameraX still uses the Android API).
With all of your experience, in your experience have you found anything that could mitigate the possibility of tampering?
Thanks Mark,
I've read the "blocking" is because of security, "as always...", but I don't see any difference accessing just Main Back/Front or all of them.
A toggle in Dev Options would be enough to allow 3rdP for those interested on it.
So,
A Call for All!!
To press Brands on the Feedback / SSNN to allow 3P access to whole pack of cams or improve their Cam Apps!
BTW,
If a Brand does that having a good Cam pack, I guess they would sell many more phone units.
Thanks
Also,
I've forgotten to mention, my current device it's:
RealMe 14 Pro+ | RUI6 | A15
There's a GCam, AGC 9.0 that it's capable to access all 3 back cams.
Would be related to the fact that it shares internal components/signatures with the OS?
BTW,
It resets the app itself to interchange between one and another, so if you're on Tele x3, you can go to Main without the restart, being mostly useless for video recording.
Last edit: ZAlex 7 days ago
https://www.celsoazevedo.com/files/android/google-camera/troubleshooting/
What are package names (multiple apks in one release)? »
Package names are usually needed to access all cameras and/or to enable features like Google Lens.
Some brands (eg: OnePlus, Samsung, etc) restrict access to all cameras. They have a "whitelist" of apps (package names) that can access those cameras, so modders release their versions with package names that are on those lists.
For example, OnePlus usually allows org.codeaurora.snapcam (sometimes referred to as "snap"), so that's what's usually recommended for OnePlus devices:
I've seen this on Celso Acevedo's, but I was not aware about this as an access to all the options, instead as something to check all the variants.
This would be an option maybe.
IDK whether we can rename OpenCamera and try whether gets full acces.
It would be great if works!
Last edit: ZAlex 7 days ago
I'm not quite sure what methods that the GCam ports use, but I note they have the advantage that there are many versions of these often tailored made/supported for specific devices, In theory there are hacky backdoor methods that work on some devices, but will break or give buggy behaviour on other devices - the link above is indeed useful, so yes that explains why they need different versions.
Renaming the package name requires some kind of development tools (either rebuilding from the source, or possibly there are some tools/methods that claim to work on the APK but I don't have experience of them).
Thanks for the support as for the OCam App.
I'll keep an eye on those options.
Thanks
Generally speaking, someone would have to look into this, starting with the simplest things—like changing the “applicationId” to begin with.
You might as well ask the modders how they figured it out.
Maybe someday someone will do something about it.
A long time ago, someone did something with OpenCamera - but that’s a different story
https://www.celsoazevedo.com/files/android/open-camera/