{ "id": "175897", "key": "TIMOB-28280", "fields": { "issuetype": { "id": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false }, "project": { "id": "10153", "key": "TIMOB", "name": "Titanium SDK/CLI", "projectCategory": { "id": "10100", "description": "Titanium and related SDKs used in application development", "name": "Client" } }, "fixVersions": [], "resolution": null, "resolutiondate": null, "created": "2020-12-10T08:45:52.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [], "versions": [ { "id": "21052", "description": "", "name": "Release 9.3.0", "archived": false, "released": true, "releaseDate": "2020-12-14" }, { "id": "21129", "name": "Release 9.2.2", "archived": false, "released": true, "releaseDate": "2020-10-29" } ], "issuelinks": [], "assignee": null, "updated": "2020-12-11T15:11:08.000+0000", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [ { "id": "10202", "name": "Android", "description": "Android Platform" } ], "description": "There is an odd behavior that we just noticed with our new test devices (e.g. Pixel 5, running Android 11): When tapping anywhere in a view, even a classic empty Ti.UI.View, there is an auditive feedback (a \"tap sound\") as well as a haptic feedback (a slight vibration) happening.\r\n\r\nSimple view to reproduce:\r\n{code:js}\r\nconst window = Ti.UI.createWindow();\r\nwindow.add(Ti.UI.createView({ backgroundColor: 'red', width: 300, height: 300 });\r\nwindow.open();\r\n{code}\r\n\r\nWe were curious and compared it with other apps as well as Android system apps and it doesn't happen there. Therefore the question, if there might be an issue with some kind of default value regarding the {{touchEnabled}} / {{touchFeedback}} that should be changed.\r\n\r\nPlease also feel free to immediately mark this as Invalid or an improvement if it's not actually a bug. Thank you for looking into this!\r\n\r\n*EDIT*: There seem to be an undocumented {{soundEffectsEnabled}} boolean property on the Ti.UI.View, but disabling it does not seem to help.", "attachment": [], "flagged": false, "summary": "Android: Auditive feedback on all views although not clickable", "creator": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "subtasks": [], "reporter": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "environment": null, "comment": { "comments": [ { "id": "457861", "author": { "name": "jquick", "key": "jquick", "displayName": "Joshua Quick", "active": true, "timeZone": "America/Los_Angeles" }, "body": "It's likely happening because touch is enabled on all Titanium views by default because that's what we document. Note that Android's native view do not have this enabled by default. Although, I've never heard or seen any touch feedback before on my devices before. I wonder if this happens if you have an \"accessibility\" feature turned on.", "updateAuthor": { "name": "jquick", "key": "jquick", "displayName": "Joshua Quick", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2020-12-10T17:26:48.000+0000", "updated": "2020-12-10T17:26:48.000+0000" }, { "id": "457862", "author": { "name": "jquick", "key": "jquick", "displayName": "Joshua Quick", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Under Android's {{Settings -> Sound -> Advanced}} section I can see checkboxes for \"Touch Sounds\" and \"Touch Vibration\". They're enabled on my Pixel 3 device but it doesn't cause sounds/vibration when I touch Ti.UI.Views with touch enabled.\r\n\r\nI'm curious if your custom theme is setting the {{android:soundEffectsEnabled}} to true on all views?\r\n\r\nHmm... I'm really curious why you're seeing this. Does it only happen on your Pixel 5?", "updateAuthor": { "name": "jquick", "key": "jquick", "displayName": "Joshua Quick", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2020-12-10T17:41:29.000+0000", "updated": "2020-12-10T17:41:29.000+0000" }, { "id": "457879", "author": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "body": "We do not use {{android:soundEffectsEnabled}}. Is there a reason to use a different \"touch enabled\" behavior compared to natively? Won't \"click\" event listeners work without it? Regarding the device: It also happens with other devices (for example if tapping between the login form and social buttons in the login view of our app. Maybe an Android 11 thing?", "updateAuthor": { "name": "hknoechel", "key": "hansknoechel", "displayName": "Hans Knöchel", "active": true, "timeZone": "Europe/Berlin" }, "created": "2020-12-11T15:09:49.000+0000", "updated": "2020-12-11T15:11:08.000+0000" } ], "maxResults": 3, "total": 3, "startAt": 0 } } }