Difference between revisions of "User:Wizzup/Telepathy"
| Line 11: | Line 11: | ||
It is not clear to me what adds the initial "sms" account, but there must be something that configures this account initially. | It is not clear to me what adds the initial "sms" account, but there must be something that configures this account initially. | ||
= Logging = | |||
Fremantle logs using the <code>rtcom-eventlogger</code> package, to a SQLite3 database stored at <code>/home/user/.rtcom-eventlogger/el-v1.db</code> - all communication related events end up here. | |||
The actual logging to the database is done (as far as I understand) by several different processes: <code>rtcom-call-ui</code> and <code>rtcom-messaging-ui</code>. These both interface with telepathy and log to the database as appropriate. (This is visible by looking at <code>/proc/pid-of-program/fd</code> on Fremantle - it will show that both programs have a fd open to the database) | |||
Telepathy does come with a program called "Telepathy Logger" which can log to various database formats (and I guess just log all messages), and it also provides a way to read (not just write) log events. I am not sure if this is useful for us, but we could take a look later. For now, I believe our replacement programs for the call and messaging UI will have to log on their own. | |||
= SMS = | = SMS = | ||
| Line 31: | Line 39: | ||
<code>ConnectAutomatically</code> seems to suggest there is no specific program that starts telepathy-ring (just MC itself), as long as the account is requested (I guess?) by something. | <code>ConnectAutomatically</code> seems to suggest there is no specific program that starts telepathy-ring (just MC itself), as long as the account is requested (I guess?) by something. | ||
= Presence and online accounts = | |||
<todo> | |||
= Fremantle (rtcom) = | = Fremantle (rtcom) = | ||
| Line 38: | Line 50: | ||
= Further reading = | = Further reading = | ||
* https://www.aosabook.org/en/telepathy.html | * Nice resource on telepathy architecture: https://www.aosabook.org/en/telepathy.html | ||
* rtcom-eventlogger API docs: http://maemo.org/api_refs/5.0/5.0-final/eventlogger/ | |||
Revision as of 12:13, 11 January 2022
This page contains my (personal) notes on how Telepathy (and to some degree rtcom) works, in general, and how it works on Fremantle, and how we plan to make it all work.
Accounts
Accounts are stored in /home/user/.rtcom-accounts/accounts.cfg on Fremantle, and HOME/.local/share/telepathy/mission-control/accounts.cfg normally in Telepathy.
It looks like Telepathy mission-control (MC) is the one that actually manages the accounts, and mc-tool can be used to manage the accounts. This means that likely there are no other tools that read accounts.cfg on Fremantle, and everything that lists/adds/removes accounts goes through Telepathy MC.
telepathy-ring accounts
It is not clear to me what adds the initial "sms" account, but there must be something that configures this account initially.
Logging
Fremantle logs using the rtcom-eventlogger package, to a SQLite3 database stored at /home/user/.rtcom-eventlogger/el-v1.db - all communication related events end up here.
The actual logging to the database is done (as far as I understand) by several different processes: rtcom-call-ui and rtcom-messaging-ui. These both interface with telepathy and log to the database as appropriate. (This is visible by looking at /proc/pid-of-program/fd on Fremantle - it will show that both programs have a fd open to the database)
Telepathy does come with a program called "Telepathy Logger" which can log to various database formats (and I guess just log all messages), and it also provides a way to read (not just write) log events. I am not sure if this is useful for us, but we could take a look later. For now, I believe our replacement programs for the call and messaging UI will have to log on their own.
SMS
telepathy-ring is used to communicate with the modem through ofono. This account has the following options set on my device:
[ring/tel/ring] manager=ring protocol=tel param-account=ring Enabled=true HasBeenOnline=true ConnectAutomatically=true AutomaticPresenceType=2 AutomaticPresenceStatus=available Profile=tel NormalizedName=<SelfHandle>
ConnectAutomatically seems to suggest there is no specific program that starts telepathy-ring (just MC itself), as long as the account is requested (I guess?) by something.
Presence and online accounts
<todo>
Fremantle (rtcom)
Further reading
- Nice resource on telepathy architecture: https://www.aosabook.org/en/telepathy.html
- rtcom-eventlogger API docs: http://maemo.org/api_refs/5.0/5.0-final/eventlogger/
