I saw in your controlPolling fuction (timeow-0.0.10)

void manager::controlPolling(QString status){
if (status == MCE_TK_LOCKED) {
modifyProximitydState("turnOn");
} else {
modifyProximitydState("turnOff");
pressPowerTimer->stop();
// killEverybody();
}
}

Should we comment out the call to modifyProximitydState, because as far as I understand, not commenting this would cause de-registre/re-register the timenowd process with proximityd, and there are no set interval call, so the polling interval would be set to default 100ms, which consume battery a lot. And these call are not necessary as the app would only need to register to proximityd once during it lifetime (which was done in the constructor for manager) (IMO)

I have test with a dummy process for timenowd which set polling interval to the highest of 2000 ms, and the battery consumption is only about 2mA, which is very good, while with the current version of timenow, the power consumption would be 6-8mA even if I set interval to 2000. (And my typical bat. consump. is about 8mA, so which timenow it would reduce batt. life to 50%)

Could this be the culprit?

I'm trying to test but not success with building the package yet.