Acknowledged

Touch events delivered to apps even when touchscreen is disabled

Hi Garmin Connect IQ Team,

Currently, there is no reliable way for an app to detect whether the device’s touchscreen is disabled (for example when the user has turned touch off in settings or enabled touch lock during an activity). The existing System.getDeviceSettings() properties like isTouchScreen and isTouchScreenActive only indicate hardware capability and not whether touch input is enabled or locked. As a result, even when the user has disabled touch, the app continues to receive and respond to touch events, which can lead to unintended interactions in sport/activity contexts.

This affects apps that rely on buttons and should respect the user’s preference or device lock during activities.

For example, for my app "Hyrox Smash", in a sweaty condition, it's quite risky to have the touch screen enabled. 

If there’s already a recommended approach I’ve missed, I’d be happy to hear about it. Otherwise, I’d appreciate you considering this enhancement for future SDK versions.

Thanks for your time and support.

Cheers,

Saeed from Multipassionate

Multipassionate
Parents
  • in reply to Multipassionate

    Please state what you think is the bug. What do you expect (with your words) when you return true in these functions and what happens instead. Also to make sure which functions are called please implement all the functions and add a log in their 1st line so you'll see which of them are actually called and in which order. Also don't forget all the functions in InputDelegate as well.

    Similarly, about isTouchScreen: show the settings enabled, what is the value, show the settings disabled, what is the value.

    Also when you post a question in the forum (especially if you state it as a bug report) add details needed to reproduce: SDK version, which physical device, what is the firmware version on it, or if it's in the simulator then state that and which simulated device it was.

Comment
  • in reply to Multipassionate

    Please state what you think is the bug. What do you expect (with your words) when you return true in these functions and what happens instead. Also to make sure which functions are called please implement all the functions and add a log in their 1st line so you'll see which of them are actually called and in which order. Also don't forget all the functions in InputDelegate as well.

    Similarly, about isTouchScreen: show the settings enabled, what is the value, show the settings disabled, what is the value.

    Also when you post a question in the forum (especially if you state it as a bug report) add details needed to reproduce: SDK version, which physical device, what is the firmware version on it, or if it's in the simulator then state that and which simulated device it was.

Children
No Data