[Android Apps and Games] StupidIdea:
It sounds like you think I'm trying to hide something :confused: so I will try to answer it the best I can:

1) Why Gesture Control (GC) seem to ask permission more often that other apps? While hypothetical other apps require root only when user performs some particular action, GC needs root process all the time in order to get access to touch events.

2) Why GC loose root? Whenever Android decides to restart GC service it looses connection to root process, so it stops the old one and starts new one. How often it happens depend on system (available free RAM, etc.). Why don't I reuse old process? Maybe I could but its more complex and I don't really see it as a problem. GC would have "pause" during service restart anyway.

3) Why it stops working for some? Short answer - I don't know. Whenever I find something that may cause instability I fix it. Let me say that on Note 3 I can see that sometimes standard interprocess communication breaks for no apparent reason and I'm investigating why its happening and how to overcome it. While on other devices it was working for weeks without hiccup for me. So before I got Note 3 I could not even reproduce it. Is this the same problem that you are complaining about? I don't know - we will see when I fix it.

Why I don't reply to every post? I read posts and I read emails so I'm informed about problems but it takes time to respond every time especially when I cannot help just with response. I better spend my time coding then. I'm sorry if you feel like you paid for some beta quality and regret it but as I mentioned before. I cannot make a living just from Android development (I'm not even talking about hiring QA or more developers). I have full time job not related to Android and I code Android on my free time. Don't get me wrong - I'm not blaming anyone, I know I'm not good businessman, I'm just saying it openly so you know how much time physically I can spend on it. I admit I do sleep sometimes too :o or I get hyped to develop some different app but I always try to fix all stability issues that I have enough info about. I did publish free Lite version that uses same engine and should have same issues so its up to you to make educated decision to buy it or not. Please don't buy apps that do not work for you expecting that developer will fix it unless you just want to support them (do it :)).

To put it short: please don't blame me :o I'm doing my best.

1. I posted comment about log and the issue a bit lower.

2. Is this consistent, i.e. can you reproduce it? I will take a loot at it. So far no one complained about this.

3. I posted comment about log and the issue a bit lower.

There is no option for Kill App and leave it in Recents. It was requested a few times to remove killed app from recents cause it was confusing. I agreed and added it. I believe there are quite a few available options (hint: Tasker) to kill app without removing it from recents and it can be assigned to custom gestures so I don't plan to add global option for it. There are too many options already :). I would like to add customizable actions feature at some point (where each action could have options dialog) just no eta.

I have to do a couple of additional root calls on KitKat. I don't reuse single root process for these "setup" calls just because its faster to execute them in parallel. These processes spawn and die after executing the command. I don't see why it is bad other than a few more records in log. I do reuse processes later on for repetitive tasks. So when you see some ~8 records in log at same time it is normal.

Sometimes app fail to get access to touch events. Then it restarts the process and retries. This can happen ~20 times. Sometimes it helps but if not app show error message (infamous device not found). I think thats is what happened in screenshot log. I don't know yet why Android does not give me events sometimes and I cannot reproduce it easily. I know restarting whole app usually help but I feel like it is only because more time passes during app restart than that I spend retrying internally. You can try 'Restart Service' button in Advanced tab and it should "fix" it too. Let me add that it is not common problem but I have a feeling that it is happening more often on Samsung devices.

Ye, I don't like this question :o. I said I will add it like a year ago. Its not finished yet cause I was busy with other tasks and got carried away. No eta now.