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

    Vibration issue

    Scheduled Pinned Locked Moved Solved Xiaomi Redmi Note 9 Pro/Pro Max/9S & Poco M2 Pro
    19 Posts 5 Posters 1.7k 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.
      • stanwoodS Offline
        stanwood @beyolf
        last edited by stanwood

        @beyolf I confirm the same issue on Redmi Note 9S. Everything works well except vibrating.
        Will try to get the logs tonight.

        Edit: Is there a way to filter repowerd outputs on journalctl ? Cause there are hundreds lines available....

        Thank you !

        Redmi Note 9S Stable
        If God has a computer, it must be a GNU/Linux

        1 Reply Last reply Reply Quote 1
        • stanwoodS Offline
          stanwood @beyolf
          last edited by stanwood

          @beyolf I finally managed to generate the logs you asked for (I hope I did the right thing, my computer skills being limited...)

          The command I used was:

          journalctl -u repowerd --since 20:30

          I rebooted the device just before in order to display the repowerd boot logs.

          I hope this helps you in your investigations.

          Thank you beforehand if you can take a look 😉

          01 20:54:17 ubuntu-phablet systemd[1]: Starting monitor and control system power state...
avril 01 20:54:17 ubuntu-phablet repowerd[1465]: main: Starting repowerd 2023.07
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Failed to create LibsuspendSystemPower>
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Trying LogindSystemPowerControl
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Trying LogindSystemPowerControl
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Failed to create LibsuspendSystemPower>
avril 01 20:54:54 ubuntu-phablet repowerd[1465]: DefaultDaemonConfig: Trying LogindSystemPowerControl
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:05 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:54 ubuntu-phablet systemd[1]: Started monitor and control system power state.
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 20:54:55 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:54:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:05 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:09 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:15 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:19 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:55:59 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:56:01 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 20:58:09 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 20:58:10 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:00:15 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:00:20 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
lines 6-22/31 71%
avril 01 21:02:56 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:02:57 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:03:00 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:03:00 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:03:13 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:03:15 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:03:31 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:05:20 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:05:25 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:06:23 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:06:35 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:06:36 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.
avril 01 21:07:34 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: disable_interactive_mode()
avril 01 21:07:36 ubuntu-phablet repowerd[1465]: LogindSessionTracker: dbus_get_session_by_pid() failed: GDB>
avril 01 21:07:51 ubuntu-phablet repowerd[1465]: BinderPerformanceBooster: enable_interactive_mode()
avril 01 21:07:52 ubuntu-phablet repowerd[1465]: SensorfwLightSensor: Skip bobus value 0 from SensorFW.

          Redmi Note 9S Stable
          If God has a computer, it must be a GNU/Linux

          B 1 Reply Last reply Reply Quote 2
          • B Offline
            beyolf @stanwood
            last edited by

            @stanwood thank you very much for the logs! I will keep you in touch!

            Ubuntu Touch fan
            UT Focal port for miatoll contributor.
            Device:
            Redmi note 9 pro

            * stanwoodS 2 Replies Last reply Reply Quote 1
            • * Offline
              *Enrico13011978* Banned @beyolf
              last edited by *Enrico13011978*

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • stanwoodS Offline
                stanwood @beyolf
                last edited by stanwood

                @beyolf Thank you very much!

                I don't know if you've had a chance to take a look at these logs?
                Meanwhile, a member of the Telegram group "The UT for Miatoll Group" informed me that a developer from Spain was able to fix the problem on the Note 9 Pro (Joyeuse).
                The vibrator would already work on the "Dev" channel, so possibly the problem would also be fixed on the Curtana after the next OTA update?

                In the meantime I've created the following ticket on Gitlab:

                https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-redmi-note-9-pro/xiaomi-miatoll/-/issues/25

                Thanks and have a nice day.

                Redmi Note 9S Stable
                If God has a computer, it must be a GNU/Linux

                S B 2 Replies Last reply Reply Quote 0
                • S Offline
                  szocse1223 @stanwood
                  last edited by szocse1223

                  Hello. My phone is also vibrating. Thank you very much for your help. Have a nice day

                  stanwoodS 1 Reply Last reply Reply Quote 0
                  • stanwoodS Offline
                    stanwood @szocse1223
                    last edited by

                    @szocse1223 Oh nice. What did you do? Are you on "dev" channel?

                    Redmi Note 9S Stable
                    If God has a computer, it must be a GNU/Linux

                    S 1 Reply Last reply Reply Quote 0
                    • S Offline
                      szocse1223 @stanwood
                      last edited by

                      @stanwood
                      Yes, I have the dev version. It has been working since the last two updates. Now I have ver. 202. I hope I won't have any problems with it 😀

                      stanwoodS 1 Reply Last reply Reply Quote 1
                      • stanwoodS Offline
                        stanwood @szocse1223
                        last edited by

                        @szocse1223 Very good then!

                        So I guess there are good chances that the fix lands also for Curtana on the next OTA-5 update (I'm on stable channel).

                        Will let you know...

                        Redmi Note 9S Stable
                        If God has a computer, it must be a GNU/Linux

                        1 Reply Last reply Reply Quote 2
                        • B Offline
                          beyolf @stanwood
                          last edited by beyolf

                          @stanwood yes I took a look on the fix. Thank you for notifying me. The fix will land on OTA 5.

                          Ubuntu Touch fan
                          UT Focal port for miatoll contributor.
                          Device:
                          Redmi note 9 pro

                          stanwoodS 1 Reply Last reply Reply Quote 1
                          • S szocse1223 marked this topic as a question on
                          • S szocse1223 has marked this topic as solved on
                          • stanwoodS Offline
                            stanwood @beyolf
                            last edited by stanwood

                            @beyolf Hi, Good new, I got OTA-5 stable today on my Curtana (Redmi Note 9S) and everything's fine.

                            However, sadly, vibrator still doesn't work...

                            Edit: I did reinstall UT using UBports installer, and vibrator now magically works pretty well.

                            Update 02.nov.2024: In reality vibrator just worked at first OTA-5 reinstall boot, then no more. Tried several times to reinstall using UBports installer, also tried the dev channel, but with no effect...

                            For the rest, it runs fantastically well.

                            Many thanks !

                            Cheers, Stanwood

                            Redmi Note 9S Stable
                            If God has a computer, it must be a GNU/Linux

                            1 Reply Last reply Reply Quote 1
                            • stanwoodS stanwood referenced this topic on
                            • stanwoodS stanwood referenced this topic on
                            • stanwoodS Offline
                              stanwood
                              last edited by

                              Very good new! With a great help from Adam (from Miatoll Group), I managed to eventually fix the vibrator issue.

                              He will try to push the fix for the next OTA. So it's wise to wait a little bit.

                              For the most adventurous, this should work:

                              1. Open the terminal app, or ssh your device and type:
                              sudo mount -o remount,rw /
sudo nano /opt/halium-overlay/usr/libexec/lxc-android-config/device-hacks
                              1. add the following line at the bottom of the text:

                              #To navigate in the nano file directly by using the UT terminal, keep pressing the 3 lines on the left side and slide to "Scroll" command, then move the cursor to the right and select the down arrow

                              sudo systemctl restart hfd-service.service

                              #To save the nano file directly by using the UT terminal, keep pressing the 3 lines on the left side and slide to "Nano" command, then select "Ctrl + X" and confirm with "y"

                              1. Reboot to save the changes with:
                              sudo reboot

                              Caution: This was valid at least for 9S Curtana. I didn't test yet all the phone features, so I can't confirm that there's no regression somewhere else (even if there shouldn't).

                              Hope it could help 😉

                              Redmi Note 9S Stable
                              If God has a computer, it must be a GNU/Linux

                              K 1 Reply Last reply Reply Quote 1
                              • K Offline
                                klanko @stanwood
                                last edited by

                                @stanwood thank u very much
                                nice work
                                it worked verry well on redmi note 9 pro 😍

                                1 Reply Last reply Reply Quote 1
                                • stanwoodS Offline
                                  stanwood
                                  last edited by

                                  Fix has been officially pushed to dev channel (Thank you Adam).

                                  I therefore did close the issue:

                                  https://gitlab.com/ubports/porting/community-ports/android10/xiaomi-redmi-note-9-pro/xiaomi-miatoll/-/issues/25

                                  Redmi Note 9S Stable
                                  If God has a computer, it must be a GNU/Linux

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post