-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 [BUG] - Surface Pro 4 Touchscreen is stuck on a mouse input #103
Comments
Live boot can behave differently than native install Have you tried a full install and faced the same? Also, You just specified "16" which is not specific enough. Please provide the full .ISO filename you are using. The EXACT .ISO filename gives us better understanding of which build may have an issue. |
For the version I've been trying to install Bliss-Surface-v16.9.7-x86_64-OFFICAL-gapps-20241012.iso And no I've not attempted to install the OS yet |
I have been experiencing the same thing, but I have installed mine with no difference. |
Same here. Stuck with mouse, no touch (rather, touch only moves the mouse cursor). Surface Pro 3. Bliss-Surface-v16.9.7-x86_64, Bliss-Surface-v15.9.2-x86_64. |
Same happens to me with a Surface Pro 2017 (5th Generation). Happens both in the live version and installed. |
I have got the same problem with a surface 4 pro, the touch screen moves the mouse cursor. Bliss-Surface-v16.9.7-x86_64, Bliss-Surface-v15.9.2-x86_64. 2024-10-12 versions Update: I just tried Bliss-Surface-v16.9.7-x86_64 2024 09 12 version, this one isn't affected touch screen is working fine |
Settings > Blissify > misc> Force mouse click as touch |
Anyone with this issue, can you please get me the results of:
And:
Looks like we need to add an IDC to override this controllers input method |
I'm encountering the exact same issue on my Surface Pro 4 (v15.9.2) Here's the output of uevent:
Product name returned |
Thank you. Can you please also grab a |
@electrikjesus sorry for late reply, I have obtained the result of dumpsys input
|
OK. Thank you for grabbing the info. Let's try this... Go grab this script: https://github.com/BlissRoms-x86/idc_script and push it to the device or download it to a USB or from the device itself, and follow the instructions. The "Example" in the readme is using the It will create an .idc for your input in your devices data folder, and should just require a reboot to test. Please let me know if it doesn't work as expected. Thanks |
@electrikjesus thanks so much that solved the "always mouse mode" issue for the touchscreen on my Surface Pro 8 running build 'Bliss-Surface-v16.9.7-x86_64-OFFICIAL-gapps-20241012'. For everyone's reference, this was my touchscreen device:
So this was my command via adb (after connecting to the device via Wireless adb, which I enabled in the Developer settings):
|
Glad to see that it worked on the SP8 as well. I tried to make it as generic a solution as possible. Once we identify all these required idc's for the Surface devices, they can be submitted here for future users so things just work out of the box for them: https://github.com/BlissRoms-x86/device_generic_common/tree/arcadia-x86/idc |
Somehow it seems to not working on my SP4 Or may be it just my installation was done inside Windows using the Windows installer found thru documentation (with R/W system enabled) and it act a lil bit funny I might have to try again with fresh installs. |
I've seen the majority of devices with this issue are on the latest Surface build also as that has updated iptsd drivers |
I have switched over a fresh installation instead of install inside Windows. |
Output for Surface Pro 5th Generation 2017 with i5-7300U and 4 GB RAM:
and
Here is the output of
|
I also have this issue with the Surface Pro 4. dumpsys input:INPUT MANAGER (dumpsys input)Input properties: Input Manager State: Event Hub State: Input Reader State (Nums of device: 12): UnwantedInteractionBlocker: Input Classifier State: Input Dispatcher State: Input Manager Service (Java) State: uevent:MODALIAS=dmi:bvnMicrosoftCorporation:bvr109.3748.768:bd05.04.2021:svnMicrosoftCorporation:pnSurfacePro4:pvr124000000000000000000000D0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:skuSurface_Pro_4:Product name:Surface pro 4After running the script i now have these two files in /data/system/devices/idc: Vendor_045e_Product_07e8_Version_0111.idc#Input device config file touch.deviceType = default touch.orientationAware = 1 touch.gestureMode = spotsVendor_1b96_Product_006a_Version_0000.idc#Input device config file device.internal = 1 touch.deviceType = touchScreen |
update: found the cause |
Description
When I go and try and setup bliss OS from a live boot USB it ends up just being stuck on a mouse input and not using the touchscreen instead, sort of like the OS thinks a keyboard is connected to my surface at all times
Reproduction steps
Screenshots
No response
Logs
No response
Category
Display
OS Version
16.x
The text was updated successfully, but these errors were encountered: