I have been having the same problem. Incorrectly detecting inactivity
isn't the issue, it's the connection of inactivity to the Away state,
which there is no user control for. Regardless the feedback from
connected apps, Google is the one making that...