Evaluate more in depth the android_frameworks_opt_telephony_ril_ofono RIL
The android_frameworks_opt_telephony_ril_ofono looks interesting.
It could enable to use ofono on Android.
Updated by Denis 'GNUtoo' Carikli over 4 years ago
- Look if the BuildRilWrapper.java uses introspection to build the API between the Framework and android_frameworks_opt_telephony_ril_ofono (See the Official documentation for more background information) and evaluate how sustainable this is (how much maintenance would it need over time).
- Test it on the Galaxy SIII 4G
- See Upstream
Updated by Joey Hewitt over 4 years ago
I'm the author of this RIL. I added some detail to GNUtoo's graph, attached. (Sorry it's weird; I don't know graphviz.)
Since my repo is lacking in documentation, some notes:
I didn't want to deal with C or the rild <-> libril interface, so I implemented a Java RIL class that replaces the one that usually talks to rild. Android is directed to use my class by a build.prop.
BuildRilWrapper runs at build time, and autogenerates code to dispatch incoming method calls to the corresponding module (e.g. SmsModule.) Most methods are asynchronous and cannot run on the thread that received the method call, so a Runnable is posted to another thread that does the necessary work and then invokes the callback.
I find my way far more convenient than the Message junk, so I wonder if there is some performance reason (memory usage?) it isn't usually done this way. Or maybe it is just the legacy of starting over 10 years ago.
The target method is found by looking for a method amongst the modules with a matching signature (same argument types, except omitting the Message that is for the callback.)
Modules are methods grouped by functionality type, and correspond closely to oFono interfaces. When oFono notifies that a given interface has loaded/unloaded, we load/unload the corresponding module. When a module is not loaded and the framework requests something that is implemented in the module, BuildRilWrapper's generated code detects this condition and reports an error to the framework.
Updated by Kurtis Hanna over 4 years ago
A video presentation and the corresponding slides related to oFono in Replicant can be viewed here: https://redmine.replicant.us/projects/replicant/wiki/ContributorsMeetingJuly2019#Presentations
Updated by Kurtis Hanna about 4 years ago
xc-racer99 has been working on an oFono driver for Samsung-IPC: https://github.com/PabloPL/linux/issues/23#issuecomment-531039814
They wonder if we have plans to upstream the Samsung IPC driver.