Long delay

[philipp-schmidt]

I'm experiencing a very long delay (about 8, up to 15 seconds) in any action of the plugin in KP2A. When opening a password entry, the inputstick connection dialogue (the one saying USB OK, BT OK) only appears delayed. After waiting out the delay I am then able to select the plugin actions. When clicking on any of the type actions, the text is only getting typed with a delay as well. The typing itself is fast and works fine.
The dialogue does get closed delayed as well when I'm leaving the entry.

I tried reinstalling the plugin. Did not help.

The plugin worked fine for me for almost a year. The problems started recently. Any idea what could cause this?

[philipp-schmidt]

I'm also not sure if the problem is the plugin or KP2A itself, as the plugin itself works fine. It just seems like KP2A submits the actions with delay.

[philipp-schmidt]

I can also comfirm that the App 'USB Remote' works just fine with no noticeable delay and connects almost instantly when clicking 'Connect'.

[inputstick]

Have you installed any new apps recently? A while back, one of users reported that "Asus Auto-start Manager" was blocking communication with InputStickUtility. This is most likely not the case here, but maybe some other app is causing this problem?
What kind of device do you use? Have you experienced this problem on any other device?
I've just verified that on all of my devices everything works correctly (using latest versions of InputStickUtility, KP2A and the plugin).

[holygoatnickels]

I have a Samsung Galaxy Note 4, & a Galaxy J3 using Verizon. Both with the latest KP2A & InputStick apps installed, and are both have the same problem. They delay for the menu items from the plugin is about 20-30 seconds, and the delay once I select sending something to IS is about another 20-30 seconds.
The Note 4 I have wiped about 3 weeks ago. the J3 I just wiped a few minutes ago and the issue persists.
Is there a way to get logs for KP2A or the InputStick plugin to do more troubleshooting?

[philipp-schmidt]

Sorry for my late response. I was experimenting around as well. I figured it works fine the very first time you fire up KP2A (after restarting for example). Killing the service in the background also seems to fix the problem for one iteration. So the problem might be the proper closing of the connection.
I was trying to enable the developer toast messages, but it's quite hard to sort out the messages with this amount of delay. I would be interested in getting my hands on some logs as well!
Reinstalling any of the involved apps did not help.
I am using a Samsung Galaxy S7 with Android 7.0

[philipp-schmidt]

Is there any way to resolve this? The inputstick right now is useless to me with these issues.

[inputstick]

In that case I'll add an option to force stop the KP2A plugin service once an entry is closed. Unfortunately I'm still not able to reproduce the issue on my hardware. Sorry about the delay.

[inputstick]

I've changed the InputStick connection service to run as foreground service. It will now display notification when running. There are three buttons on the notification (when expanded): "force stop" (service should be stopped once you close an entry in KP2A), "test" (type "test") and "show log" (log is created each time service is started, it is not stored anywhere).
I also had a chance today to briefly test it on S7 running Android 7: worked just fine.
Please let me know if it solves the issue on your devices.
signed .apk file:
https://drive.google.com/file/d/0B2RufT7QrvYGa2JMZ1BkMU80bEU/view?usp=sharing

source:
https://drive.google.com/file/d/0B2RufT7QrvYGZE1SQmQ2bmQ3NDQ/view?usp=sharing

[philipp-schmidt]

I was running it for a few days now and it works! Whenever I get a weird behaviour (which recently got less likely somehow), killing it solves the problem. Next time the problem occurs I might be able to post the log. I set the app to only connect once and keep the connection now, which helps a lot. Thank you very much for this patch and your time!

[inputstick]

After investigating this more closely I think I've identified what is causing the problem: once the plugin connects, next broadcast from KP2A gets delayed. What makes it difficult to observe/recreate is that the delay can vary (in my case: from 1-2 seconds usually, what goes unnoticed, up to 10 seconds sometimes) and it will be noticed at a different moments depending on plugin configuration and what actions you select in KP2A.
Solution: once background service is started, it should register itself for receiving broadcasts from KP2A. Surprisingly, it receives all broadcasts without any delays. Looks promising after brief testing.
I'll try to implement this ASAP, but please keep in mind that some significant changes will be necessary.

[inputstick]

This took a while, but I think that the delay issue is now entirely solved. Here's download link to new version:
https://drive.google.com/uc?id=0B2RufT7QrvYGZ3FsNjFjaDFlY0E&export=download
if I won't find any problems within next 2-3 days I'll upload new version to Google Play.
Please let me know how it works on your devices.

[philipp-schmidt]

The first impression is very good! I will test it for some time and check back on you if I find anything of importance. Thank you again for the dedication you show for this plugin with those ongoing enhancements. If you could use any help in a future project, I'd be glad to help if I can!