chatty issueshttps://source.puri.sm/Librem5/chatty/-/issues2020-06-18T12:41:33Zhttps://source.puri.sm/Librem5/chatty/-/issues/354Continously tries to connect to modems every 5s causing wakeups2020-06-18T12:41:33ZGuido GuntherContinously tries to connect to modems every 5s causing wakeupsChatty tries to connect to the modem over and over again although there is none (HKS off):
```
(10:49:41) mm-sms: ModemManager found: :1.11
(10:49:41) connection: Connection error on 0xaaaae20f1610 (reason: 0 description: Could not conn...Chatty tries to connect to the modem over and over again although there is none (HKS off):
```
(10:49:41) mm-sms: ModemManager found: :1.11
(10:49:41) connection: Connection error on 0xaaaae20f1610 (reason: 0 description: Could not connect to modem)
(10:49:41) account: Disconnecting account SMS (0xaaaae20ff5b0)
(10:49:41) connection: Disconnecting connection 0xaaaae20f1610
(10:49:41) connection: Destroying connection 0xaaaae20f1610
(10:49:41) util: Writing file accounts.xml to directory /home/purism/.purple
(10:49:41) util: Writing file /home/purism/.purple/accounts.xml
(10:49:46) account: Connecting to account SMS.
(10:49:46) connection: Connecting. gc = 0xaaaae20f1610
(10:49:46) mm-sms: ModemManager found: :1.11
(10:49:46) connection: Connection error on 0xaaaae20f1610 (reason: 0 description: Could not connect to modem)
(10:49:46) account: Disconnecting account SMS (0xaaaae20ff5b0)
(10:49:46) connection: Disconnecting connection 0xaaaae20f1610
(10:49:46) connection: Destroying connection 0xaaaae20f1610
```
This wastes battery and causes unneeded disk writes although the plugin connects to the `object-added` DBus signal and can hence report new modems.https://source.puri.sm/Librem5/chatty/-/issues/6Support XEP-0352: Client State Indication2020-06-24T11:45:15ZMartinSupport XEP-0352: Client State IndicationVery important to save battery and bandwidth: If the phone is not in use, one is not interested in status changes of other users. Probably not yet in libpurple, but [the protocol seems to be simple](https://xmpp.org/extensions/xep-0352.h...Very important to save battery and bandwidth: If the phone is not in use, one is not interested in status changes of other users. Probably not yet in libpurple, but [the protocol seems to be simple](https://xmpp.org/extensions/xep-0352.html).https://source.puri.sm/Librem5/chatty/-/issues/351Stream Management (XEP-0189)2020-07-31T18:51:34ZGuido GuntherStream Management (XEP-0189)There seems to be basic support in libpurple now (https://bitbucket.org/pidgin/main/pull-requests/309/xep-0198-stream-management/diff) and the MR has by @bwildenhain that somebody is working on resumption support.There seems to be basic support in libpurple now (https://bitbucket.org/pidgin/main/pull-requests/309/xep-0198-stream-management/diff) and the MR has by @bwildenhain that somebody is working on resumption support.https://source.puri.sm/Librem5/chatty/-/issues/350Push notifications (XEP-0357)2020-06-16T15:00:42ZGuido GuntherPush notifications (XEP-0357)This will also need sever side support in e.g. LibremOne since we don't want to use FCM or similar. Ths will allow to have chatty sleep way more than it currently does.This will also need sever side support in e.g. LibremOne since we don't want to use FCM or similar. Ths will allow to have chatty sleep way more than it currently does.https://source.puri.sm/Librem5/chatty/-/issues/306Chatty wakes the CPU up constantly with XMPP account connected2020-05-26T16:58:54ZSebastian KrzyszkowiakChatty wakes the CPU up constantly with XMPP account connectedWith XMPP account active and connected, powertop shows that chatty is the most active userspace process on an otherwise idle system, which increases battery consumption. Having around 3 wakeups per second all the time looks very suspicio...With XMPP account active and connected, powertop shows that chatty is the most active userspace process on an otherwise idle system, which increases battery consumption. Having around 3 wakeups per second all the time looks very suspiciously like some timer, which should be avoided on a battery powered system.
```
5.4 ms/s 3.2 Process chatty --daemon
```https://source.puri.sm/Librem5/chatty/-/issues/291Eats cpu on start2020-08-28T11:57:43ZGuido GuntherEats cpu on startwhenever chatty starts in daemon mode it shows two processes and one eats CPU:
```
$ ps awux | grep -E '[c]hatty|[U]SER'
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
purism 1114 53.0 2.1 661412 65416 tty7...whenever chatty starts in daemon mode it shows two processes and one eats CPU:
```
$ ps awux | grep -E '[c]hatty|[U]SER'
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
purism 1114 53.0 2.1 661412 65416 tty7 RLl+ 18:18 0:01 chatty --daemon
purism 1122 0.0 0.8 428412 25188 tty7 S+ 18:18 0:00 chatty --daemon
```
i've not investigated further and it "only" goes on for a couple of seconds but it' be nicer if we could avoid that since lots of things want the CPU on device boot