UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    How enable "tap to wake" on startup

    Scheduled Pinned Locked Moved Google Pixel 3a/3a XL
    8 Posts 6 Posters 594 Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • Br1B Offline
        Br1
        last edited by

        If you already created a systemd user service to execute some commands on startup you must only add this line to bash script :

        dbus-send --system --print-reply --dest=com.canonical.Unity.Screen /com/canonical/Unity/Screen com.canonical.Unity.Screen.setDoubleTapToWakeEnabled boolean:true
        

        ^

        • Google Pixel 3a XL
        • Xiaomi MI A2
        A 1 Reply Last reply Reply Quote 3
        • A Offline
          AmauryDBZ @Br1
          last edited by

          Thanks @Br1.
          Then how to create a systemd user if not ? šŸ˜…

          L 1 Reply Last reply Reply Quote 0
          • L Offline
            lkroll @AmauryDBZ
            last edited by

            @AmauryDBZ I just put the command into a systemd service file under /home/phablet/.config/systemd/user/enable-doubletap.service

            [Unit]
            Description=Enable Double Tap to Wake on Unity Screen after D-Bus is ready
            Requires=dbus.socket
            After=dbus.socket
            
            [Service]
            ExecStart=dbus-send --system --print-reply --dest=com.canonical.Unity.Screen /com/canonical/Unity/Screen com.canonical.Unity.Screen.setDoubleTapToWakeEnabled boolean:true
            Type=oneshot
            RemainAfterExit=yes
            
            [Install]
            WantedBy=dbus.socket
            

            After that enable with systemctl --user enable enable-doubletap.service

            A H 2 Replies Last reply Reply Quote 1
            • A Offline
              AmauryDBZ @lkroll
              last edited by

              @lkroll doesn't work for me. Could it be because I have a FP4 ? (this topic is tagged Pixel 3a)

              lduboeufL 1 Reply Last reply Reply Quote 0
              • lduboeufL Offline
                lduboeuf @AmauryDBZ
                last edited by

                @AmauryDBZ said in How enable "tap to wake" on startup:

                @lkroll doesn't work for me. Could it be because I have a FP4 ? (this topic is tagged Pixel 3a)

                yes FP4 don't support double tap to wake.
                fyi persistant dt2w will be on next OTA

                A MoemM 2 Replies Last reply Reply Quote 2
                • A Offline
                  AmauryDBZ @lduboeuf
                  last edited by

                  @lduboeuf ok thanks !!

                  1 Reply Last reply Reply Quote 0
                  • MoemM Offline
                    Moem @lduboeuf
                    last edited by

                    @lduboeuf said in How enable "tap to wake" on startup:

                    fyi persistant dt2w will be on next OTA

                    Hurray!

                    Is currently using an Op5t
                    Also owns an Op1, a BQ E4.5 and an Xperia X, as well as a BQ tablet and a Pinetab2. Please, someone... make it stop.

                    1 Reply Last reply Reply Quote 1
                    • H Offline
                      h-the @lkroll
                      last edited by

                      @lkroll , @Br1

                      Thanks for your help, this works perfectly.

                      code_textphablet@ubuntu-phablet:~$ systemctl --user status enable-doubletap.service
                      ā— enable-doubletap.service - Enable Double Tap to Wake on Unity Screen after D-Bus is ready
                           Loaded: loaded (/home/phablet/.config/systemd/user/enable-doubletap.service; enabled; vendor preset: enabled)
                           Active: active (exited) since Thu 2024-01-04 15:35:53 +03; 20min ago
                         Main PID: .......
                      
                      
                      1 Reply Last reply Reply Quote 0
                      • First post
                        Last post