Controller doesn't function as expected

Carpe Iter remote controllers require their companion software - NGH (Next-gen HUD) to run on your Android device to function properly. 

If your controller is connected to your Android device, you installed the NGH on your Android device and the controller is selected in NGH as the active controller, but:

A. The status icon for the controller remains red, i.e. not connected in NGH (example for Adventure Control) 

1. Close NGH (open overview of running applications - tap the square icon on the navigation bar or swipe up from bottom of the screen if you are using gesture control - swipe NGH away from the list to close it).
2. Restart your Android device (usually long press on the power button - pop-up power menu appears, select Restart (Reboot on some Android versions). 
3. Launch NGH. At each start, the NGH checks for permissions required for its correct function. If NGH ask for some permissions, grant them. If you reject some of the permissions, NGH might not work correctly.
   
4. Select Controler "None" and re-select your controller (example for Adventure Control): 

If the status icon remains red: Unpair (Forget) the controller in your Android device Bluetooth manager and re-pair it. The procedure is the same like for any other Bluetooth device. You can also refer for guidance to of this support article.  

When using multiple Carpe Iter controllers of the same type: Please make sure the one controller you plan to use is actually selected in NGH. In this scenario, you will have more than one controller of the same type listed in the NGH Controller selection overview (i.e. AdvCtrl for Adventure Control, BMCD for BMW Control, TCMD for Terrain Command). Try to choose the other controller and re-launch NGH (open overview of running applications - tap the square icon on the navigation bar or swipe up from bottom of the screen if you are using gesture control - swipe NGH away from the list to close it. Tap NGH icon to open it again). 

B. The status icon for the controller is green, but the controller still doesn't function as expected (example for Adventure Control):

    1. Update NGH

Updates are deployed via Play store. Please check details in this support article. 

    2. Update controller firmware

Controller firmware updates are deployed via NGH. Please check details in this support article. 

    3. Make sure NGH Accessibility service is running. 

How to check: re-launch NGH (NGH checks the status of the accessibility service at each launch or try to call the HUD e.g. on the Homescreen. 

If the accessibility service is off upon NGH launch, NGH will invite you to enable it via an on-screen dialogue, which will take you to the Android device Settings page for Accessibility services. 

If you called the HUD but it doesn't show, it is clear indication that the Accessibility service is disabled, even if NGH didn't complain about it at launch. Sometimes the Android operating system kills the Accessibility service only partially, which makes it appear as being enabled, but it is not fully functional. 

Even if the NGH Accessibility service appears to be enabled, toggle it off and on again in the Accessibility services menu in the Android device system Settings. This action will enforce the correct reloading of the service. You can also full-text search the Android device system menu to let you find the Accessibility service settings easily.

    4. Check that the controller is not locked manually in a specific configuration for other app than the one you are currently trying to use. 

In the default settings, the controller is set for automatic reconfiguration depending on the app showing on the screen. But this setting can be manually changed to a specific app configuration and in that case the controller will not adapt and will stay in the manually selected configuration regardless of what is being displayed on the screen. As useful as this feature is e.g. for a rally situation, it will get in the way when you forget to revert the controller to the automatic mode and will start using another app.

    5. Make sure the Controller app Accessibility service is disabled. It is recommened to uninstall the Controller app completely on other devices than CI Pad (it is preinstalled on CI Pad and cannot be removed completely). Please check this support article for details.

    6. Disable key mapper type apps. Key input overrides will make the controller malfunction.

    7. Refert to default software keyboard, if you manually changed it in your Android device system settings. Some alternative software keyboards are remapping hardware inputs, which causes the controller to malfunction. Gboard is thoroughly tested and does not cause issues.

A side note - not all apps are natively supported by our controllers. Please make sure that you are checking the controller function in one of the supported apps listed in this support article. 

If you are experiencing issues with a specific function in a specific app that should be working according to the Supported apps' overview, it is also possible that something needs a correction after the recent app update. Please report such issues to our support so that we can fix it ASAP:-)