-
Notifications
You must be signed in to change notification settings - Fork 43
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
How to run servicemanager in non android OS #91
Comments
If no one is running a service manager for you, you would have to do it yourself. Unit tests contain a few very primitive implementations of various servicemanager binder APIs, like this one for example. Those would give you a very rough idea how it could be done with libgbinder. It's not that hard, really, especially the early simple servicemanager APIs like the one called "aidl" in libgbinder. Writing a real servicemanager (e.g. the one accessible via zero handle) would require a few changes in libgbinder, at least to provide an equivalent of ProcessState::becomeContextManager and keep an internal reference to the local servicemanager object (no more than one per binder device). AFAICT becoming the context manager is a one-way thing, i.e. there's no way to stop being the context manager. I can imagine a function like |
This would be helpful. |
In case of android, servicemanager run as separate service during boot.
In case of non android OS, how to run service manager using libgbinder?
The text was updated successfully, but these errors were encountered: