Telephony stack

Telephony on a phone passes through several layers, from the kernel up to the applications:

1. The kernel layer gives userland access to the modem.
2. The system daemon, ModemManager, gives a single interface to different modems over D-Bus.
3. Session daemons handle calls, messages and history for the user.
4. The QML plugin gives applications an interface to those daemons.
5. Applications are what the user sees.

#What SonicDE ships

SonicDE includes the parts that handle mobile data and the modem's state:

• sonic-frameworks-modemmanager, the Qt interface to ModemManager (ModemManagerQt).
• sonic-network-manager, which manages mobile connections and shows the SIM PIN dialog.
• sonic-mobile-interface, with its signal strength indicator, mobile data quick setting, cellular step in the initial setup, and detection of access point settings.

SonicDE doesn't ship the session daemons, the QML plugin, or a dialer or messaging application. They belong to upstream KDE projects, and these pages describe them so that you can see how the stack fits together.

#Similar projects

• Cellular Telephony Architecture in the Sailfish OS documentation