Open mattwhite7982 opened 4 weeks ago
Live boot can behave differently than native install
Have you tried a full install and faced the same? Have you noticed the boot option called "PC mode"? (May not be an option from the USB installer. However, can be added as cmdline parameter to Grub boot menu entry). Differs from booting regular mode in several ways. PC mode is expecting a mouse and keyboard. Touch input is still detected the same, handling is different.
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
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). The touchscreen acts as a trackpad, moving a cursor on the screen.
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. I tried these two roms:
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:
cat /sys/class/dmi/id/uevent
And:
cat /sys/class/dmi/id/product_name
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:
MODALIAS=dmi:bvnMicrosoftCorporation:bvr109.3748.768:bd05.04.2021:svnMicrosoftCorporation:pnSurfacePro4:pvr124000000000000000000000D0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:skuSurface_Pro_4:
Product name returned Surface Pro 4
correctly
Thank you. Can you please also grab a dumpsys input
so we can match the vendor/product/version for IDC filename?
Thank you. Can you please also grab a
dumpsys input
so we can match the vendor/product/version for IDC filename?
@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 Surface Pro 4
info provided above, so you can just copy that same info for this device.
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:
49: Intel Touch Host Controller Touchscreen
Classes: TOUCH
Path: /dev/input/event5
Enabled: true
Descriptor: e6b0fb37445093f42e9fe32813474b55b9f99d4f
Location: pci-0000:00:10.6/ithc
ControllerNumber: 0
UniqueId:
Identifier: bus=0x0001, vendor=0x045e, product=0x0c37, version=0x0100
KeyLayoutFile:
KeyCharacterMapFile:
ConfigurationFile:
VideoDevice: <none>
So this was my command via adb (after connecting to the device via Wireless adb, which I enabled in the Developer settings):
adb shell sh /sdcard/Download/create_touch_input_idc_in_data.sh -t 045e 0c37 0100
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 (v15.9.2) I have verified the file was correctly created and have the correct permission
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. creating the idc file still not fixed the problem, touchscreen still behave exactly like the touchpad
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