11-24-2023, 04:15 AM
(This post was last modified: 11-24-2023, 04:40 AM by Eugo.)
I've had that issue at the time. I don't remember how it got fixed, whether the next version (one before this one) fixed it, or I managed to turn that notification off, or... hmm, maybe it really doesn't suspend and I don't properly suspend it manually? As I did turn that off.
Okay, turned it on now... but while I was fiddling with the settings, doing nothing else, wireless off, blututh off, it went from 99% battery charge to 90 (87 while I was writing this paragraph). The power settings dialog showed battery life estimated at 2h 30m.
It shouldn't discharge that fast. Previously one charge held for about 40 hours.
Update: turning auto suspend on still has that bug, the notification appears, the screen lights up for a few seconds, the suspend timer resets, two minutes later it repeats.
Turned it off again.
If I try the menu which appears in the on/off button in the quick (pull-down) settings, there are options to restart or shutdown; the option to suspend is disabled, as is the log out option.
The power applet shows it's currently consuming 2,3W, which seems ridiculously high to me.
So I'm back at square one.
I don't know GnuLinux. Can you monitor the CPU frequencies?
:wq
[ SRA accepts you ]
(11-24-2023, 04:15 AM)Eugo Wrote: Update: turning auto suspend on still has that bug, the notification appears, the screen lights up for a few seconds, the suspend timer resets, two minutes later it repeats.
Turned it off again.
If I try the menu which appears in the on/off button in the quick (pull-down) settings, there are options to restart or shutdown; the option to suspend is disabled, as is the log out option.
The power applet shows it's currently consuming 2,3W, which seems ridiculously high to me.
So I'm back at square one.
I am 99% sure that your device is not suspending.
Follow these steps:
1. Open Phosh mobile settings -> Experimental features -> Enable suspend via the system menu (this will allow you to suspend from quick settings on/off button).
Don't open Phosh mobile settings after this (or if you do run the command below every time after you close Phosh mobile settings). I am quite sure that Manjaro is using version which will trigger below gsettings to "urgent" and it will breake your suspend. Issue is fixed but afaik not yet packaged to Manjaro.
2.
Code: gsettings set sm.puri.phosh.notifications wakeup-screen-triggers '[]'
3. Suspend your phone (or allow automatic suspend and let it suspend) -> make sure that the device actually suspended. If you have volume on you can try it for example pressing volume buttons (when suspended they are silent and when not suspended you should hear the volume changing sound if you have not configured it off)
(11-24-2023, 10:40 AM)alaraajavamma Wrote: Follow these steps:
1. Open Phosh mobile settings -> Experimental features -> Enable suspend via the system menu (this will allow you to suspend from quick settings on/off button).
Don't open Phosh mobile settings after this (or if you do run the command below every time after you close Phosh mobile settings). I am quite sure that Manjaro is using version which will trigger below gsettings to "urgent" and it will breake your suspend. Issue is fixed but afaik not yet packaged to Manjaro.
2.
Code: gsettings set sm.puri.phosh.notifications wakeup-screen-triggers '[]'
3. Suspend your phone (or allow automatic suspend and let it suspend) -> make sure that the device actually suspended. If you have volume on you can try it for example pressing volume buttons (when suspended they are silent and when not suspended you should hear the volume changing sound if you have not configured it off)
Okay, done so... Noted the power level at this time, will check in a couple of hours.
11-25-2023, 04:29 AM
(This post was last modified: 11-25-2023, 05:01 AM by Eugo.)
Okay, for good two hours of suspend-from-dropdown it lost only about 3%.
Still this is only marginally better
- the suspend from physical button doesn't suspend
- this suspend-from-dropdown is something I'll forget to do in a hurry
- the PowerSupply applet still shows 2,24W drain when idling with screen on
Here's what top -S says on a freshly booted idle phone:
Code: top - 11:59:07 up 2 min, 2 users, load average: 1,27, 0,75, 0,30
Tasks: 227 total, 1 running, 226 sleeping, 0 stopped, 0 zombie
%Cpu(s): 8,5 us, 1,2 sy, 0,0 ni, 89,1 id, 0,1 wa, 0,7 hi, 0,2 si, 0,0 st
MiB Mem : 1991,1 total, 870,0 free, 800,1 used, 441,1 buff/cache
MiB Swap: 2986,7 total, 2986,7 free, 0,0 used. 1191,1 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
3870 manjaro 20 0 1126216 198688 64064 S 29,2 9,7 0:35.51 phosh
3385 dbus 20 0 16464 7296 4736 S 1,6 0,4 0:04.31 dbus-daemon
3667 root 20 0 313168 10040 6784 S 1,6 0,5 0:01.69 iio-sensor-prox
7 root 20 0 0 0 0 I 1,3 0,0 0:00.55 kworker/0:0-events
3872 root 20 0 0 0 0 I 1,0 0,0 0:00.34 kworker/1:4-events
4154 manjaro 20 0 533884 26896 21248 S 1,0 1,3 0:01.47 gsd-power
4659 manjaro 20 0 12564 5888 3584 R 1,0 0,3 0:00.54 top
31 root 20 0 0 0 0 I 0,7 0,0 0:00.37 kworker/3:0-events
3704 manjaro 20 0 835908 105316 71340 S 0,7 5,2 0:03.65 phoc
849 root 20 0 0 0 0 I 0,3 0,0 0:01.07 kworker/u8:6-devfreq_wq
1067 root 20 0 0 0 0 I 0,3 0,0 0:00.34 kworker/2:3-events
3217 root 20 0 17760 6528 5632 S 0,3 0,3 0:00.09 systemd-userwor
3447 root 20 0 421472 27048 21144 S 0,3 1,3 0:01.74 NetworkManager
3580 root -2 0 0 0 0 S 0,3 0,0 0:00.24 ksdioirqd/mmc1
3607 root 20 0 397384 18968 14496 S 0,3 0,9 0:01.15 ModemManager
3719 root 20 0 0 0 0 S 0,3 0,0 0:00.13 RTW_RECV_THREAD
3721 root 20 0 0 0 0 S 0,3 0,0 0:00.01 RTWHALXT
Now if you guys notice anything awkward, let me know.
(11-25-2023, 04:29 AM)Eugo Wrote: Okay, for good two hours of suspend-from-dropdown it lost only about 3%.
Still this is only marginally better
- the suspend from physical button doesn't suspend
- this suspend-from-dropdown is something I'll forget to do in a hurry
- the PowerSupply applet still shows 2,24W drain when idling with screen on
2,24W sounds normal - I get the same. Also top seems normal.
"Suspend from physical button" - if you mean power button (which will turn screen on or off?) it does not suspend your Pinephone with Phosh. It just turns screen on or off or power on or off. There might be a way to make it suspend but afaik no-one have ever got it working.
Phosh suspend works by default so that you set the automatic suspend timer which will suspend phone in that time if you (or some app who can inhibit it like calls) don't interrupt it. Then you can sure suspend manually trough "systemctl suspend" or from the quick settings button.
"Okay, for good two hours of suspend-from-dropdown it lost only about 3%.
Still this is only marginally better"
This sounds as good as it gets if you have modem powered on. Maybe you are just getting more accurate battery percentage now  ?
(11-25-2023, 08:28 AM)alaraajavamma Wrote: 2,24W sounds normal - I get the same. Also top seems normal.
"Suspend from physical button" - if you mean power button (which will turn screen on or off?) it does not suspend your Pinephone with Phosh. It just turns screen on or off or power on or off. There might be a way to make it suspend but afaik no-one have ever got it working.
Phosh suspend works by default so that you set the automatic suspend timer which will suspend phone in that time if you (or some app who can inhibit it like calls) don't interrupt it. Then you can sure suspend manually trough "systemctl suspend" or from the quick settings button.
"Okay, for good two hours of suspend-from-dropdown it lost only about 3%.
Still this is only marginally better"
This sounds as good as it gets if you have modem powered on. Maybe you are just getting more accurate battery percentage now ?
Okay, so some of suspects are off the list.
I wish I could do an update, perhaps there's a problem which got fixed meanwhile, but can't because
„:: Import PGP key 150C200743ED46D8, "Mark Wagie <mark@manjaro.org>"?“
yields an error (key can't be imported, not on the keychain) when replied Yes, and aborts the update when No. Tried the fix as described here, bot it broke many more keys - it tries to build the keychain from scratch and fails, there are too many dead ones mentioned, on absent servers or by absent people. So I renamed the old one back and now have just the "can't update" problem.
I'll leave it manually suspended overnight, just to check. If it doesn't drain, then it's indeed the modem which stays too much on. I wanted to stay away from mmcli, but it seems one can't avoid fate, eh?
Okay, went from 100% to 65% overnight (and it was a long night ) while suspended. I'll keep it so and teach myself to manually suspend as often as I can.
The next best workaround would be suspend on power button. That would do it for me, but really don't know where to start.
If the update is now draining the battery, and before that it was not, maybe sounds like a bug, might need to report it, idk if that is kernal or upower or what. is it possible to revert back to the old update to test it out, See which packages are or not the cause then report it?
Not a manjoro user but been looking to switch to plasma but kevin sent me to pinetab furoms but idk if those options work on pinephone.
In the end, switching to Plasma Mobile is just a matter of installing the correct packages. You are running DanctNIX Arch, so I sent you to a post that gives some instructions for that distro.
You may have to install some additional packages on the PinePhone (such as plasma-dialer and spacebar, which are not relevant on the PineTab series, which does not have a modem), but basically the procedure is the same for all devices.
Now if you cannot follow such simple instructions, then Arch is probably not for you and you should reinstall from a distro image with Plasma Mobile preinstalled, e.g., the Manjaro one (which is closest to Arch) or the postmarketOS one.
|
Using too much juice since last update
