Notices

About this: what about adding a connect/disconnect cover action? I kinda remembered it was there, but when I went to set it a couple of days ago I only found "Exit" (which is not what I want: I want to be able to disconnect from whatsapp without having to close Mitakuuluu, I can do it with the pulley menu in the app, but it would also be useful to have super-quick as a cover action).

Make a feture request at github and i'll check this when i'll have free time

i share his opinion. i think it's more important to receive the messages correct than to have a batterielife around 3 years

I have no problem with trading a bit of battery life for a more reliable message delivery, but if the battery goes down in like 1h idle and the phone gets so hot you could boil an egg on it I don't think its a good tradeoff

@coderus - with nemo keepalive should mitakuuluu wake jolla from deep suspend periodically when on wifi?

@seiichiro0185you should expect that behaviour when application reconnects 10-20 times in a half of hour because weak connection
@egnat69 not forced, its synchronized with system heartbeat timers

Anecdotally, I was also on a train, then when I got to my destination (with good 3G), I found that the daemon was stuck at 100% cpu - killing and restarting sorted it out, but it had used a fair amount of battery on my train journey without me noticing, and hadn't fixed itself when back in an area of good reception.
I don't know how best to debug this, and whether it's a problem in Mitakuuluu or the Jolla networking implementation. Maybe stepping in and out of an elevator to simulate signal loss!

And also I still get the problem that Mitakuuluu thinks it's connected, but doesn't get messages. I have "Quit" set to the cover actions for this reason, and frequently restart in case a network transition has confused the daemon. So for me, the aggressive reconnect isn't even aggressive enough!
(Although the latest version hides the cover actions when not connected, so if it gets stuck when it thinks it's disconnected, I need to go in and quit with the pulley menu)

I should say (not for this thread to be wall-to-wall complaints) that otherwise Mitakuuluu is great, and the pace of development and bugfixes is impressive - many thanks to coderus!

A n00b question:

"Before starting new Mitakuuluu you need to shutdown existing version" What does shutting down the existing version mean? Do I need to uninstall it?

Has anybody noticed that "save chat history" is now only saving a record of the time and date of messages and not the content. Is this right or am I doing something stupid....?

You are right, I make issue to github.https://github.com/CODeRUS/mitakuuluu2/issues/150