Hello,
we have conducted a re-test to investigate the issue you guys reported.
We attempted to reproduce the behavior using both the Automatic Profile and the App Specific Profile. In our test, we were unable to replicate the fault. The system is functioning correctly in both modes. Specially the App Specific Profile, we configured the inputs according to standard setup, and the controller responded exactly as programmed without any issues.
Since the hardware and software appear to be functioning normally on our end, the issues you guys are experiencing is likely related to a specific configuration or Android setting.
Troubleshooting Steps:
Please review the following support articles, as these address the most common causes for this type of behavior:
Android permissions: Accessibility Service turned off
Check that the controller works correctly in other supported apps (also in FAQs).
You can also check this FAQ - Controller button doesn´t work.
FAQs - Controllers : Carpe Iter Home
Make sure your controller firmware is up to date.
Make sure you use NGH (Controller app development is discontinued)
Make sure you are not using a key mapper
Make sure you use default keyboard (at least switch to default keyboard to check, if the issues might be caused by your specific keyboard app. Yes, that does matter in some cases).
If you have both Controller app and NGH installed, make sure that Carpe accessibility service is not enabled for both of them. Only one service can be active or the controller inputs get messed up.
If you still have issues contact our support and provide the following details in your ticket:
-
Which exact Carpe Iter controller is affected and which FW version (there are 4 controller types and 3 generations)
-
Which smart device you are using the controller with (Manufacturer, Model, Operating system version)
-
If the problem is specific to Kurviger or other supported apps are also affected. If so, which ones you tested (each supported app has also a free version, which is also supported by our controllers).
Either way, we are sorry for the trouble. Rest assured it will be solved ![]()