3 ms·
(KDE dev here) It is still an issue, but it's getting better. As far as I am concerned, Ring-KDE (a phone and Skype alternative app) is still eating too much p
by Elv13 9y ago
(KDE dev here)
It is still an issue, but it's getting better. As far as I am concerned, Ring-KDE (a phone and Skype alternative app) is still eating too much power. It is a work in progress and is already much better than it was a couple months ago. Some of the dependencies my app use are also power hungry. This needs to be fixed. However it's nothing that can't be fixed. Enough profiling and powertop work will get us there.
- akerro 9y agoEx-Tox developer here: >Ring-KDE (a phone and Skype alternative app) is still eating too much power. This will always be a nature of Ring and Tox because it uses DHT network to find peers and keep connections alive, this is CPU-hungry, therefore power consuming and it won't be accepted on mobile platforms. Also losing network connectivity for 3 seconds causes the client to reconnect to the network, find peers again, messages can be lost... Matrix is the way to go.
- Elv13 9y agoNo. The way I plan to fix it is having "dht services" where you can delegate the mobile device burden to another node. As we use SIP and it supports such topology, it's not much of a problem.