Although cross-platform GUI toolkits exist, I presume that it doesn't utilise one, and the underlying work is Camera2-specific. Would any part of the work put into Open Camera be usable when constructing a similar application for a GlibC-based (rather than AOSP's Bionic) OS, like postmarketOS? I ask because I'd like to not be forced to operate WayDroid (or the deprecated Windows Subsystem for Android) merely to be able to utilise the features of my camera.
I've tried asking for recommendations for alternative camera clients at community.spiceworks.com/t/1226828, but all I've realised is that I might need to accomplish this myself, since Open Camera is unparalleled.
👍
1
Last edit: Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-07-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2025-08-02
no
😕
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Unfortunately there was an anonymous commenter posting several repeated comments, in some cases copying from existing comments, across various threads including this one. So I suspect the notifications are genuine - someone else was posting these anonymously. I've deleted the comments, so they no longer show here. Sorry for the confusion!
❤️
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Indeed, Open Camera uses Java with the Android APIs, rather than any cross-platform toolkits.
The Camera API specific code is self-contained inside the CameraController/CameraControllerManager classes (indeed that's how it supports both the original and Camera2 APIs). Although I imagine the issue would be the large number of other Android specific APIs in use too (not just GUI, but things like image processing, launching background threads, and sadly even now file access, can be different to using the standard Java classes for this). I don't know if postmarketOS supports Java as a language, if not that's obviously even harder.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Getting Java working on non-Bionic Linux is trivial. Thanks for the run-down of the other things: I occasionally forget just how far AOSP's permissions model has drifted from other Linux OSes'.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Although cross-platform GUI toolkits exist, I presume that it doesn't utilise one, and the underlying work is Camera2-specific. Would any part of the work put into Open Camera be usable when constructing a similar application for a GlibC-based (rather than AOSP's Bionic) OS, like postmarketOS? I ask because I'd like to not be forced to operate WayDroid (or the deprecated Windows Subsystem for Android) merely to be able to utilise the features of my camera.
I've tried asking for recommendations for alternative camera clients at
community.spiceworks.com/t/1226828
, but all I've realised is that I might need to accomplish this myself, since Open Camera is unparalleled.Last edit: Mr. Beedell, Roke Julian Lockhart (RJLB) 2025-07-25
no
Thanks for the effort, @Anonymous, but that's a little unactionably nondescript.
If anyone else suddenly received lots of notifications for that message, see
sourceforge.net/p/forge/site-support/26953
.Unfortunately there was an anonymous commenter posting several repeated comments, in some cases copying from existing comments, across various threads including this one. So I suspect the notifications are genuine - someone else was posting these anonymously. I've deleted the comments, so they no longer show here. Sorry for the confusion!
Indeed, Open Camera uses Java with the Android APIs, rather than any cross-platform toolkits.
The Camera API specific code is self-contained inside the CameraController/CameraControllerManager classes (indeed that's how it supports both the original and Camera2 APIs). Although I imagine the issue would be the large number of other Android specific APIs in use too (not just GUI, but things like image processing, launching background threads, and sadly even now file access, can be different to using the standard Java classes for this). I don't know if postmarketOS supports Java as a language, if not that's obviously even harder.
Getting Java working on non-Bionic Linux is trivial. Thanks for the run-down of the other things: I occasionally forget just how far AOSP's permissions model has drifted from other Linux OSes'.