Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.34f1
2022.3.17f1
2023.2.6f1
2023.3.0b3
Issue ID
UUM-60376
Regression
No
[Android] Input debugger shows multiple TouchScreen Remote devices with some Android Devices and the touch event is not recognised on some of the TouchScreen Remote devices
How to reproduce:
1. Open the "IN_64824" project
2. In the Build Settings "Run Device" dropdown, select the desired device
3. Press Build And Run
4. Open Input Debugger in the Window -> Analysis -> Input Debugger
5. From the "Remote Devices" dropdown, select the device
6. Unfold Devices -> Remote -> Autoconnect Player
7. Count the number of TouchScreens
8. In the "Events" press Record Frames and tap the device screen multiple times (repeat this for each TouchScreen device shown in the Input Debug window)
Expected result: There is one TouchScreen Remote device and touch events are registered in the "Events" tab
Actual result: There are two or more TouchScreen Remote devices and only one TouchScreen Remote device registers touch events in the "Events" tab
Reproducible with: 2021.3.34f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0b3
Testing environment: Windows 10 Pro
Not reproducible on: No other environment tested
Reproducible on these devices:
VLNQA00267, Samsung Galaxy S10+ (SM-G975F), Android 12, CPU: Exynos 9 (9820), GPU: Mali-G76
VLNQA00342, Samsung Galaxy Note20 Ultra 5G (SM-N986B), Android 10, CPU: Exynos 990, GPU: Mali-G77
Samsung Galaxy a32 (user reported)
Not reproducible on these devices:
VLNQA00391, Xiaomi - (M2006C3LG), Android 10, CPU: MediaTek Helio G25 (MT6762G), GPU: PowerVR Rogue GE8320
VLNQA00120, Google Pixel 2 (Pixel 2), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00178, Xiaomi Redmi Note 4 (Redmi Note 4), Android 6.0, CPU: MediaTek Helio X20 MT6797M, GPU: Mali-T880
VLNQA00489, Htc 10 (HTC 10), Android 6.0.1, CPU: Snapdragon 820 MSM8996, GPU: Adreno (TM) 530
VLNQA00494 - iPhone 14 Pro Max, 16.3.1 iOS
VLNQA00358 - iPhone 12, 14.1 iOS
VLNQA00392 - iPad (9th generation), 15.0 iOS
VLNQA00310 - iPad Pro 12.9", 13.4.1 iOS
Notes:
- Not reproducible on iOS Platform
- Also reproducible without the Input System package (this package in this case, is only used for Input Debugger)
- Galaxy Note 20 Ultra has three TouchScreen remote devices since one of them is for the stylus and Touch event is recognised when using a stylus
- On Galaxy S10 + the touch screen becomes unresponsive when entered in-game (Press Singleplayer -> pick any option -> Play the game)
User-provided workaround:
{noformat}public void Awake() {
var user = InputUser.all[0];
foreach (var device in InputSystem.devices) {
InputUser.PerformPairingWithDevice(device, user);
}
}{noformat}
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on memcpy when using ScreenCapture.CaptureScreenshot with superSize set to zero
- [URP] Package Samples - Missing scripts in Unity 2022+
- [URP][Package Samples] Continuous "Renderer at index _ is missing for camera _" warnings when opening sample scene
- [URP] Package Samples - Missing scripts in Unity 6
- [URP] Package samples - scenes using FirstPersonController not working in Unity 6
Resolution Note:
Again, InputSystem doesn't do filtering, it simply returns devices reported by Android. If you want for InputSystem to implement a filtering which devices should be ignored, consider requesting a feature request - https://unity.com/roadmap/unity-platform/gameplay (Select Input tab, and Submit a new idea)
If you want unified touch reporting, consider using https://docs.unity3d.com/Packages/com.unity.inputsystem@1.0/api/UnityEngine.InputSystem.EnhancedTouch.EnhancedTouchSupport.html
Cheers