Project

General

Profile

Additional Replicant interface on Android?

Added by E3V3A XDA almost 10 years ago

Hello,

Would it be possible to manually install only the modem/Radio part of Raplicant
to a XMM based device? (Without flashing anything.) How?

For example, we're using the I9100/T/G and some others.
But we'd like to add a Replicant based inteface, since we're not able to
locally communicate with baseband from terminal or Java, because of lack of
access to baseband interface example code from Google or Intel.

E:V:A


Replies (3)

RE: Additional Replicant interface on Android? - Added by Paul Kocialkowski over 9 years ago

You can use Samsung-RIL on top of CyanogenMod (if that's what you're asking), but you'll need to remove the proprietary RIL compatibility layer in the framework (see commits on the Replicant devices about that). You can also directly interact with the Samsung IPC protocol by using libsamsung-ipc!

Also, let's not duplicate threads about this, so please use this one for discussion about that particular topic.

RE: Additional Replicant interface on Android? - Added by E3V3A XDA over 9 years ago

I copied this from my other post, to continue discussion here.

Paul Kocialkowski wrote:

We would love to try to replace the stock or ROM based Samsung RIL Socket with Replicant. (Is there a way to do this manually?) Or better, use as an add-on interface, preferably providing the AT or RF debug output, that we so much need.

Please describe more specifically what you're trying to do. The Replicant Samsung-RIL uses an internal Samsung RIL Socket for communication with e.g. the audio module, but that's totally unrelated to the sockets the proprietary RIL is using. If you wish to communicate with the proprietary RIL, I doubt you'll find much help about it here. On the other hand, if you're interested in working with Samsung-RIL or directly the Samsung IPC protocol, here is a good place to ask details.

What is that "internal" socket you're talking about?
And how does it differ from the proprietary one?

I'm trying to first understand what is doing what (and connected where) on the current KK based AOSP ROMs for the I9100.
This has some complications, since they've changed all the sockets, devices and ports used, since GB2.3.4 days.

Specifically, we're trying to get more and better RF variables directly
from the modem, than what is currently supported by the AOS API. We're
particularly interested in getting GSM information on:

  1. Neighboring Cells (Works poorly and often not at all in the API.)
  2. Signal Strength (Doesn't work at all on some API's.)
  3. TX power (n/a in API)
  4. Ciphering Indicator (n/a in API)
  5. Timing Advance (n/a in API<17 or non-LTE connections)
  6. various MM/RRC timers (See here for a list: http://tinyurl.com/pluk9av )

We would use whichever interface could provide these items.
Thus it seem that we only have 2 choices;
(a) using the Samsung IPC or
(b) using the RIL (or modem?) debug port as is done in the Xgoldmon.
https://github.com/harpreet-s/xgoldmon

The problem with (b) is that i) we don't know how to talk to the RIL debug port
and ii) although the Modem USB port is listed in `lsusb`, we don't know how to
connect to it locally, from within phone.

RE: Additional Replicant interface on Android? - Added by Paul Kocialkowski over 9 years ago

What is that "internal" socket you're talking about?
And how does it differ from the proprietary one?

It allows communication between the RIL and other modules, such as audio. The proprietary RIL uses the same logic, but implements it using a different data exchange protocol than ours (obviously). While our protocol is documented in our code, theirs is not, though you can find a software implementation for the audio part, at hardware/samsung/ (it's libsec-ril-client).

    (1-3/3)