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

Notifications and waking up scrren

Scheduled Pinned Locked Moved Support
9 Posts 2 Posters 663 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.
    • S Offline
      saveurlinux
      last edited by saveurlinux 12 Jul 2020, 16:08 6 Dec 2020, 19:33

      On stable channel as on RC 2020-W49
      my Nexus 5 scree doesn't wake up:

      • when alarm ring up
      • when I'm receiving calls
      • when plugin usb cable on
      • or when I'm receiving message.
        Is there a way to configure screen to wake up in this cases ?
        however the phone vibrate and the indicator light flash up.
      1 Reply Last reply Reply Quote 0
      • S Offline
        saveurlinux
        last edited by 7 Dec 2020, 16:19

        this are the repowered logs just after receiving an email

        2020-12-07T17:18:01.645791+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_requestSysState(:1.39,usensord,1)
        2020-12-07T17:18:01.647678+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_requestSysState(:1.39,usensord,1) => 408
        2020-12-07T17:18:01.647881+01:00 ubuntu-phablet repowerd[1818]: DefaultStateMachine[c2]: disallow_suspend
        2020-12-07T17:18:01.647911+01:00 ubuntu-phablet repowerd[1818]: LibsuspendSystemPowerControl: disallow_suspend(DefaultStateMachine)
        2020-12-07T17:18:01.647932+01:00 ubuntu-phablet repowerd[1818]: LibsuspendSystemPowerControl: exiting suspend
        2020-12-07T17:18:01.707716+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_setScreenPowerMode(:1.80,on,4)
        2020-12-07T17:18:01.709290+01:00 ubuntu-phablet repowerd[1818]: DefaultStateMachine[c2]: handle_notification
        2020-12-07T17:18:01.709315+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: proximity_state()
        2020-12-07T17:18:01.792157+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: schedule_synthetic_initial_event(), state=near, delay_ms=500
        2020-12-07T17:18:01.852581+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_requestSysState(:1.77,media-hub-playback_lock,1)
        2020-12-07T17:18:01.854114+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_requestSysState(:1.77,media-hub-playback_lock,1) => 409
        2020-12-07T17:18:01.957121+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: handle_proximity_event(near)
        2020-12-07T17:18:01.957235+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: proximity_state() => near
        2020-12-07T17:18:01.957260+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: enable_proximity_events()
        2020-12-07T17:18:02.036477+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: schedule_synthetic_initial_event(), state=near, delay_ms=500
        2020-12-07T17:18:02.036625+01:00 ubuntu-phablet repowerd[1818]: DefaultStateMachine[c2]: disallow_suspend
        2020-12-07T17:18:02.036645+01:00 ubuntu-phablet repowerd[1818]: LibsuspendSystemPowerControl: disallow_suspend(DefaultStateMachine)
        2020-12-07T17:18:02.102145+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: handle_proximity_event(near)
        2020-12-07T17:18:02.102203+01:00 ubuntu-phablet repowerd[1818]: DefaultStateMachine[c2]: handle_proximity_near
        2020-12-07T17:18:03.667497+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_clearSysState(:1.39,408)
        2020-12-07T17:18:06.234163+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_clearSysState(:1.77,409)
        2020-12-07T17:18:06.246285+01:00 ubuntu-phablet repowerd[1818]: DefaultStateMachine[c2]: allow_suspend
        2020-12-07T17:18:06.246327+01:00 ubuntu-phablet repowerd[1818]: LibsuspendSystemPowerControl: allow_suspend(DefaultStateMachine)
        2020-12-07T17:18:06.246361+01:00 ubuntu-phablet repowerd[1818]: LibsuspendSystemPowerControl: Preparing for suspend
        2020-12-07T17:18:06.431023+01:00 ubuntu-phablet repowerd[1818]: UnityScreenService: dbus_setScreenPowerMode(:1.80,off,4)
        2020-12-07T17:18:06.434094+01:00 ubuntu-phablet repowerd[1818]: DefaultStateMachine[c2]: handle_no_notification
        2020-12-07T17:18:06.434134+01:00 ubuntu-phablet repowerd[1818]: UbuntuProximitySensor: disable_proximity_events()
        2020-12-07T17:18:20.713101+01:00 ubuntu-phablet repowerd[1818]: UPowerPowerSourceAndLid: change_device(/org/freedesktop/UPower/devices/battery_battery), type=
        battery, is_present=1, state=charging, percentage=30.00, temperature=26.30
        2020-12-07T17:18:20.720477+01:00 ubuntu-phablet repowerd[1818]: UPowerPowerSourceAndLid: change_device(/org/freedesktop/UPower/devices/DisplayDevice), type=ba
        ttery, is_present=1, state=charging, percentage=30.00, temperature=0.00
        
        F 1 Reply Last reply 9 Dec 2020, 09:03 Reply Quote 0
        • S Offline
          saveurlinux
          last edited by 7 Dec 2020, 16:50

          maybe that can help
          looking at /var/log/syslog when receiving a mail I've got this:

          Dec  7 17:49:21 ubuntu-phablet kernel: [95246.227889] max17048_work: rsoc=0x6737 rvcell=0x0C72 soc=52 v_mv=3982 i_ua=-439717 t=276
          Dec  7 17:50:03 ubuntu-phablet kernel: [95287.939597] max17048_work: rsoc=0x6826 rvcell=0x0C78 soc=53 v_mv=3990 i_ua=-439108 t=276
          
          1 Reply Last reply Reply Quote 0
          • F Offline
            flohack @saveurlinux
            last edited by 9 Dec 2020, 09:03

            @saveurlinux Seems your proximity is always near. Can you test it with doing a phone call, does it turn on/off your screen properly when moving away/to your head?

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

            S 1 Reply Last reply 9 Dec 2020, 10:48 Reply Quote 0
            • S Offline
              saveurlinux @flohack
              last edited by 9 Dec 2020, 10:48

              @flohack Thanks, for replaying,
              When giving a call, the screen turn off just after clicking on calling green button and never goes on after.
              When receiving a call, the screen in off, after manually turn on pressing power button I can answer the call then the screen goes off immediately.

              Maybe an hardware problem ?

              S 1 Reply Last reply 9 Dec 2020, 11:48 Reply Quote 0
              • S Offline
                saveurlinux @saveurlinux
                last edited by 9 Dec 2020, 11:48

                @saveurlinux I've tryed the sensorsstatus applications and looking at proximity, it does return "No data available"

                S F 2 Replies Last reply 12 Dec 2020, 07:54 Reply Quote 0
                • S Offline
                  saveurlinux @saveurlinux
                  last edited by 12 Dec 2020, 07:54

                  @saveurlinux I've installed /e/ android alternative to give tried https://e.foundation/, it's a very nice work they have done to.
                  With /e/ screen wake up when alarm ring-up but none when receiving mail.

                  1 Reply Last reply Reply Quote 0
                  • F Offline
                    flohack @saveurlinux
                    last edited by 12 Dec 2020, 09:50

                    @saveurlinux Yeah sensorstatus is a bit broken for proximity still. Thats why I asked about the call. Unfortunately I am not sure whats going on, it works on other N5s very well, I would suspect a hardware issue, maybe you can try to test it with an Android app?

                    My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                    S 1 Reply Last reply 13 Dec 2020, 17:28 Reply Quote 0
                    • S Offline
                      saveurlinux @flohack
                      last edited by 13 Dec 2020, 17:28

                      @flohack Thanks, for replying, seem to be an hardware issue. Is it possible to disable this sensors as it send back wrong information ?

                      1 Reply Last reply Reply Quote 0
                      7 out of 9
                      • First post
                        7/9
                        Last post