Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2017.4.X, 2018.4.X, 2019.2.X, 2019.3.X
[Android] Input.GetKey returns false when S-Pen is being used on Samsung device
1. Open attached project
2. Build to Samsung device with S-Pen
3. Use the Pen on the mobile screen
Actual result: The pen does not work. Getting Mouse0 in Input.GetKey only at first draw call. Then you don't receive anything (Input.GetKey return false all the time you press S-Pen)
Expected result: The pen should work. When you press and hold S-Pen should get Mouse0 button pressed all the time while pressing S-Pen (Input.GetKey)
Reproduced with: 2017.4.33f1; 2018.4.9f1; 2020.1.0a4
Not reproduced with: 2017.4.32f1; 2018.4.8f1
VLNQA00219, Samsung Galaxy Note9 (SM-N960U), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00128, Samsung Galaxy Note8 (SM-N950F), Android 9, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00028, Samsung Galaxy Note4 (SM-N910F), Android 6.0.1, CPU: Snapdragon 805 APQ8084, GPU: Adreno (TM) 420
Note: Logcat attached.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Jan 17, 2020 15:13
The issue is fixed in the versions 2019.3.0b11, 2019.2.14f1, and 2018.4.13f1, and beyond.
We are still investigating the possibility of the fix being backported to 2017.4.
Dec 05, 2019 12:52
Is this also planned for 2017.4?
Nov 29, 2019 11:18
Everything works in build 14
Nov 22, 2019 11:35
Problem still exists in 2019.2.13f1.
Is it hard for you to fix this error ????
Developers, ay, where are you?
Nov 22, 2019 04:38
Same here. Can't afford losing too many players that using Samsung s-pen, still stuck at 2018.4.8f1. Tried 2018.4.12f1 and failed in case you wonder.
Nov 14, 2019 12:44
Hello! Problem still exists in 2019.2.12f1.
"Fix In Review for 2019.2" - What does it mean?
Nov 13, 2019 21:57
Problem still exists in 2019.2.12f1.
When will this be resolved?
A growing amount of users are using these pens with our apps which increases the amount of bad reviews. It doesn't feel a complex bug to resolve for you guys, so it would be great to give it enough priority. thanks.
Nov 06, 2019 08:38
Reproduced the issue on 2019.2.9f1 and beta version 2019.3.0b9.
Fixed in alpha version 2020.1.0a11.
Nov 05, 2019 12:52
Still reproducible in 2019.3.0b9.
Is there any update about this issue?
Nov 05, 2019 09:19
Reproduced with: 2017.4.34 too. No fix planned for 2017.4 ?