If a test calls test_binder_set_looper_enabled(fd, TRUE) to enable
processing of incoming data by the looper thread, the same thread
may get picked up by the next test and swallow the reply before the
transaction (for which the reply was intended) has been submitted.
Which may cause that next test to either fail or (if the transaction
was synchronous) block forever, stalling the build.
Calling gbinder_ipc_exit() makes sure that looper thread terminates
before the next test starts.
Custom device-to-protocol mapping can be provided via /etc/gbinder.conf
and the default config looks like this:
[Protocol]
Default = aidl
/dev/binder = aidl
/dev/hwbinder = hidl
Until now, gbinder_servicemanager_new_local_object() was the only
API for creating local objects. That was slightly weird because
creating local object don't have much to do servicemanager, it's
a purely local operation. All we need to know is which binder
device (GBinderIpc) the object is going to be associated with.
That's what gbinder_remote_object_ipc() is for.
This function allows to wait for servicemanager synchronously,
blocking the event loop in the process (not recommended):
gbinder_servicemanager_wait()
These two allow to follow the presence state of servicemanager
without blocking the event loop:
gbinder_servicemanager_is_present()
gbinder_servicemanager_add_presence_handler()
Note that services need to re-add their names to servicemanager
after it has restarted. This can be done by the presence handler.
