-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document the FAQ #3
Comments
Why don't you use as a base? |
Q. is device X supported? A. Not right now, Initially we will prototype the base for the hammerhead device and once base is stable enough we will add support for more devices.
|
Q: Why is systemd involved ? A: Some hardware functionalities (rild, sensors...) are provided by Android services, which must be started at boot time. Therefore an integration in the init system is needed. |
Q: The component X is common to all distributions; why not include it in Halium ? A: Each distribution has its own way of integrating and building its components. Most of the time, the same upstream is already used, so the efforts are already mostly shared. Moreover, Halium wants to address a well identified target, i.e. the hardware abstraction layer using the Android drivers. |
Q: Why don't we enhanced Mer Project instead of creating a new one? |
Q: Which community are involved in Halium Project ? A: Plasma Mobile, LuneOS, UBports, just missing yours ! |
Q: Why didn't we enhance the Mer Project instead of creating a new one? A: The mer project is not comparable with ours. Mer is an os core, while Halium is only a HAL. Mer will run on a halium adaption just fine. |
There are too many questions, and we need to document them on website and docs.
The text was updated successfully, but these errors were encountered: