sxmo: fix that sxmo_state_switch.sh was renamed upstream

hosts/modules/gui/sxmo/hooks/sxmo_hook_inputhandler.sh

@@ -53,9 +53,9 @@ handle_with() {
 #   # probably not handling proximity* correctly here
 #   case "$STATE" in
 #     *lock)
-#       respond_with sxmo_state_switch.sh set screenoff
+#       respond_with sxmo_state.sh set screenoff
 #     *)
-#       respond_with sxmo_state_switch.sh set unlock
+#       respond_with sxmo_state.sh set unlock
 #   esac
 # }
 
@@ -104,7 +104,7 @@ if [ "$STATE" = "screenoff" ]; then
       ;;
     "powerbutton_three")
       # power once during deep sleep often gets misread as power three, so treat these same
-      handle_with sxmo_state_switch.sh set unlock
+      handle_with sxmo_state.sh set unlock
       ;;
   esac
 fi
@@ -113,11 +113,11 @@ fi
 case "$ACTION" in
   "powerbutton_one")
     # power once => unlock
-    handle_with sxmo_state_switch.sh set unlock
+    handle_with sxmo_state.sh set unlock
     ;;
   "powerbutton_two")
     # power twice => screenoff
-    handle_with sxmo_state_switch.sh set screenoff
+    handle_with sxmo_state.sh set screenoff
     ;;
   # powerbutton_three: intentional no-op because overloading the kill-window handler is risky
 

hosts/modules/gui/sxmo/hooks/sxmo_hook_start.sh

@@ -24,7 +24,7 @@ systemctl --user start bonsaid
 #   swaymsg output '*' bg "$SXMO_BG_IMG" fill
 
 # To setup initial lock state
-sxmo_state_switch.sh set unlock
+sxmo_state.sh set unlock
 
 # Turn on auto-suspend
 if [ -w "/sys/power/wakeup_count" ] && [ -f "/sys/power/wake_lock" ]; then