Open ilikpoptarts opened 7 months ago
for buttons, check getevent
to see if your device is detected, and also see if it's working
For iptsd, I suggest report bug in linux-surface/iptsd , also maybe give them your calibration result too
for buttons, check
getevent
to see if your device is detected, and also see if it's working
getevent shows this: https://text.is/83N6
while getevent is active, pressing power, or either volume buttons does not return any results
hmmm, I don't see any GPIO key here
Btw for clarity this is touchscreen in action. First swipe is nice and smooth. I release finger and swipe again, and it goes nuts. Will take it up with linux-surface https://github.com/BlissOS/bug_reports/assets/95555646/d961118d-4ec3-45cc-b07e-36938d09004e
same for me,on Surface Pro 6
The button issue seems to be caused by module loading sequence, you can try add the code below in init.sh
if [ ! $(lsmod | grep gpio_keys) ]; then
modprobe -r soc_button_array
modprobe gpio_keys
modprobe acpi:MSHW0040:
fi
like this
Works for my pro 8
And for the touchscreen, it seems that iptsd's orientation filtering malfunctions in Android so you can try set
OrientationThresholdMin
and OrientationThresholdMax
to 999
in the config file as Bliss document says
The button issue seems to be caused by module loading sequence, you can try add the code below in
init.sh
if [ ! $(lsmod | grep gpio_keys) ]; then
modprobe -r soc_button_array
modprobe gpio_keys
modprobe acpi:MSHW0040:
fi
like thisWorks for my pro 8 And for the touchscreen, it seems that iptsd's orientation filtering malfunctions in Android so you can try set
OrientationThresholdMin
andOrientationThresholdMax
to999
in the config file as Bliss document says
where the init.sh is?
The button issue seems to be caused by module loading sequence, you can try add the code below in
init.sh
if [ ! $(lsmod | grep gpio_keys) ]; then
modprobe -r soc_button_array
modprobe gpio_keys
modprobe acpi:MSHW0040:
fi
like thisWorks for my pro 8 And for the touchscreen, it seems that iptsd's orientation filtering malfunctions in Android so you can try set
OrientationThresholdMin
andOrientationThresholdMax
to999
in the config file as Bliss document sayswhere the init.sh is?
in /system/etc
Also having same two issues. Just testing the touchscreen fix now. Any tips on how to easily mount /system as rw? Last time I tried it ended up removing init.sh bricking BlissOS...
Edit: Touchscreen fix works. Much appreciated! I also have an issue where the battery sometimes isn't detected properly so shows no charge readings. Any thoughts?
The button issue seems to be caused by module loading sequence, you can try add the code below in
init.sh
if [ ! $(lsmod | grep gpio_keys) ]; then
modprobe -r soc_button_array
modprobe gpio_keys
modprobe acpi:MSHW0040:
fi
like thisWorks for my pro 8 And for the touchscreen, it seems that iptsd's orientation filtering malfunctions in Android so you can try set
OrientationThresholdMin
andOrientationThresholdMax
to999
in the config file as Bliss document says
This solved the problem with the power and volume buttons, but screen rotation still doesn't work. Any solution to this? The working condition of the screen rotation may also be related to the order of loading the drivers, in liveCD the screen rotation works fine, but when I uninstall any of the modules of surface_hid
, surface_aggregator_tabletsw
, surface_aggregator_hub
, and then reload them again, there is no way to make the screen rotation work again.
My device is Surface Pro 8
build - Bliss-Surface-v16.9.4-x86_64-OFFICIAL-gapps-20240115 Using on surface pro 6
The touchscreen behavior takes place when trying to scroll. Sometimes scroll works fine. Sometimes a tap is registered instead of initiating a scroll. And sometimes it will tap several times whilst scrolling. I have calibrated using steps in docs. ( https://docs.blissos.org/configuration/calibrate-and-configure-iptsd/ )
I would also like to report that my physical buttons, power and volume +/- do not register.