04:25 <missMyN900> the stock minimal brightness on the Pinephone is way too high. After some trial and error I finally managed to lower the brightness with redshift (which I use on my computers to reduce blue light in the evening)

04:26 <missMyN900> I mean the brightness with status area applet, of course

04:28 <missMyN900> smplayer froze multiple times for some reason during opus playback

04:28 <missMyN900> (with mplayer as backend)

04:28 <missMyN900> using mplayer from the terminal app I did not experience this problem with the Opus files

04:29 <missMyN900> I think I also experienced some general Hildon/X freezes

04:30 <missMyN900> the audio experience still stucks on the PP

04:31 <missMyN900> status area volume applet still does not work

04:31 <missMyN900> with devel enabled (after rebooting)

04:31 <missMyN900> and updating sinks.ini (after rebooting, again)

04:31 <missMyN900> pavucontrol-qt is useless because you can't scroll to access the lower output sink, which happens to be the relevant one...

04:32 <missMyN900> only pavucontrol (GTK3) works

04:32 <missMyN900> however, I discovered that it is also not a good idea to leave pavucontrol running because it causes high CPU usage

04:33 <missMyN900> the application itself uses 22% but pulseaudio usage for some reason jumps from 8 to 20% as well

04:33 <missMyN900> and Xorg also uses a lot of CPU when pavucontrol is running

04:35 <missMyN900> hmm

04:35 <missMyN900> according to pactl info: Default Sink: alsa_output.0.HiFi__hw_PinePhone_0__sink

04:35 <missMyN900> looks like it was not a good idea to change sinks.ini

04:36 <missMyN900> and this is with a fresh install (05-29 image with devel enabled)

08:02 <Wizzup> 23:57 < missMyN900> norayr: I have an excellent porting suggestion for you: desktop command execution widget!

08:02 <Wizzup> didn't sicelo do thta?

08:03 <Wizzup> missMyN900: that's a lot of interrupts

13:18 <_uvos_> intterupts whilest on ac power dosent tell us mutch

13:18 <_uvos_> some drivers ajust behavior

13:19 <_uvos_> crust allows suspend & reaction to modem, not the same kind of pm as omap afaik

13:19 <_uvos_> that widget is in the repo allready

13:19 <_uvos_> try QT_SCALE_FACTOR=1.5 pavucontrol-qt -platform xcb -style fusion

13:20 <Wizzup> right, omap pm is different

13:22 <_uvos_> i gues you could try implementing some kind of ip push notifications on the crust uc

13:23 <_uvos_> to further paper over the pm gap on pp

13:24 <humpelstilzchen[> iirc wifi can not wakeup the PP from crust. Only the modem, rtc and a few others

13:24 <_uvos_> that (or mp3 decoding) would also be really neet on omap4's cortex m4 cpus

13:24 <_uvos_> which you can use for anything

13:25 <_uvos_> humpelsilzchen: ok not sure what crust has access to in hw

13:25 <_uvos_> on omap4 the equivalent can access any bus iirc

13:26 <_uvos_> and could directly talk to the wifi chip

13:27 <_uvos_> this would involve the linux driver somehow handing hw resources over to the uc firmware.. diffiult

13:27 <_uvos_> but possible

13:42 <Wizzup> are there hidden services for devuan repos?

13:42 <Wizzup> i.e. like https://onion.debian.org/

13:45 <Wizzup> ah they do

13:47 <Wizzup> ok, I'm able to update using only tor for devuan and maemo repos

13:49 <bencoh> nice

13:49 <bencoh> :)

18:56 <missMyN900> alright, so looks like I finally got the status menu volume applet to work

18:56 <missMyN900> changed the sink to the "default sink" in the pactl info output

18:56 <missMyN900> and rebooted and now I can see the slider in pavucontrol responding to the slider in the status area

18:57 <missMyN900> but the sink suggested in that GH issue with "platform-sound" definitely does not work

18:57 <missMyN900> maybe it worked on older images or maybe it does on older (distro edition?) 2/16 GB PPs but it certainly doesn't with my setup

18:59 <missMyN900> _uvos_: I doubt crust depends on the modem. Remember, the A64 is a tablet SoC (that is also used in SBCs such as the Pine A64 and laptops such as the original Pinebook)

19:00 <missMyN900> the majority of A64 devices does not have the Quectel/Qualcomm modem

19:01 <missMyN900> the same applies for the other SoCs supported by Crust, which are settop box SoCs that are used in SBCs (except for A83T)

19:03 <humpelstilzchen[> missMyN900: (slider) cool, what exactly did you write in the file and maybe you should add that to the ticket

19:03 <missMyN900> humpelstilzchen[: [9:35:34 pm] <missMyN900> according to pactl info: Default Sink: alsa_output.0.HiFi__hw_PinePhone_0__sink

19:03 <missMyN900> I put that sink in sinks.ini

19:04 <missMyN900> I did not have time to test it yesterday, so I just powered off the PP for the night

19:04 <missMyN900> and booted it up today and now it seems to be working

19:04 <missMyN900> still need to test with (s)mplayer though

19:25 <Wizzup> missMyN900: check @ getting it to work

19:25 <Wizzup> missMyN900: I think crust depends on the modem to wake it up is the point

19:27 <missMyN900> it is working with mplayer!

19:28 <missMyN900> this is a big improvement

19:32 <missMyN900> Wizzup: most A64 devices do not even have a modem. Crust runs on the Allwinner AR100 (an OpenRISC microcontroller) of the Allwinner SoC.

19:33 <missMyN900> "Similarly, Crust is the lowest-level firmware component that runs on $FRUIT (Banana, Orange, Lichee) Pi single-board computers and other Allwinner-based devices, such as the Pine64 Pinebook and PinePhone."

19:34 <missMyN900> "Note that Crust only provides the mechanism for deep sleep. It does not dictate any system sleep policy. Specifically, Crust does not decide when to go to sleep; the Linux kernel or userspace does that. And with one exception (listening for IR remote control key presses), Crust does not decide when to wake the system up, either; the hardware, as programmed by Linux, does that. Crust is designed to be a mostly-invisible

19:34 <missMyN900> implementation detail of the Linux power management interface."

19:34 <humpelstilzchen[> check /sys/class/wakeup

19:34 <humpelstilzchen[> there are a lot wakeup sources

19:37 <missMyN900> humpelstilzchen[: ok but my point is crust does not depend on the modem. And I don't think that ML should rely on the modem since it would be nice if the pm transferred to the Pinetab, which does not have a modem

19:38 <missMyN900> furthermore, it would be nice if the pm still worked properly with the modem kill switch enabled (or the modem otherwise turned off) on the PP

19:38 <humpelstilzchen[> missMyN900: if in doubt just use the rtc to wakeup

19:39 <missMyN900> humpelstilzchen[: are you saying there is a manual way I can put it into deep sleep?

19:40 <humpelstilzchen[> you might want to keep the modem wakeup source enabled for e.g. wakeup when there is a call.

19:40 <humpelstilzchen[> missMyN900: manual way see https://wiki.pine64.org/wiki/Crust

19:41 <missMyN900> it uses systemd though :/

19:41 <missMyN900> oh there is non-systemd option

19:42 <missMyN900> so basically I can just experiment with this?

19:43 <humpelstilzchen[> sure

19:43 <missMyN900> interesting :)

19:43 <missMyN900> I am also interested in the unofficial modem "firmware"

19:44 <missMyN900> it can lower the Quectel A7 frequency to 100 MHz from 800/400 MHz

19:44 <humpelstilzchen[> missMyN900: you can also spy on e.g. sxmo how they are using it: https://git.sr.ht/~mil/sxmo-utils/tree/d2d06ef65ac63af41516d334cd8a5446a0f20cc3/item/programs/sxmo_screenlock.c

19:44 <missMyN900> so they are doing all this stuff from userspace?

19:44 <missMyN900> I thought I would have to become a kernel hacker to do this myself

19:45 <humpelstilzchen[> the kernel part is mostly done it seems

19:46 <humpelstilzchen[> firmware: You are talking about https://github.com/Biktorgj/pinephone_modem_sdk I guess.

19:46 <Wizzup> missMyN900: the point is that crust without any way to wake it up on action doesn't help

19:46 <missMyN900> yes

19:47 <missMyN900> is there a way to use the power button to wake it up?

19:47 <humpelstilzchen[> I can't say anything about it, since I don't have a sim in the PP, but I've installed the open firmware. GPS still works

19:47 <humpelstilzchen[> power button is already active wakeup source

19:47 <missMyN900> so it is already going to deep sleep?

19:47 <missMyN900> when the screen is locked?

19:47 <missMyN900> battery life does not seem to reflect that...

19:48 <humpelstilzchen[> no, leste does not do that yet. You still need to manually start the crust sleep

19:48 <humpelstilzchen[> but you can that with the simple echo mem > /sys/power/state

19:49 <missMyN900> oh but I can just put it in suspend and it will already automatically wake up when pressing the power button?

19:50 <sicelo> Yes

19:50 <missMyN900> why didn't anyone tell me this before? :D

19:51 <missMyN900> it is working!

19:51 <missMyN900> I did it over ssh and then the command appears to "hang" (since it has already gone into deep sleep)

19:51 <missMyN900> and when I press the power button the command "returns"

19:53 <humpelstilzchen[> wakeup crashes my pp from time to time. Had no chance to debug that yet. Also I still have not soldered myself a pp debug cable yet

19:54 <humpelstilzchen[> also you might want to disable some wakeup sources in /sys/class/wakeup/ or the PP will just randomly wakeup

19:54 <missMyN900> the entire device or just X/Hildon?

19:55 <humpelstilzchen[> ?

19:55 <missMyN900> can you still access it over SSH?

19:55 <missMyN900> when that crash occurs?

19:56 <humpelstilzchen[> no network, no x, nothing.

19:56 <missMyN900> so kernel panic?

19:56 <humpelstilzchen[> I guess so

19:57 <missMyN900> maybe you could add some logging code that executes on wakeup?

19:57 <humpelstilzchen[> the notification led is white, everything else is dark. The only thing I can do is long press the power button until it turns off

19:57 <missMyN900> hmm noti LED is always white when it turns off

19:57 <missMyN900> it always takes a little while for the LED to turn off

19:58 <humpelstilzchen[> does not help since a flush is needed to write the disk. I will solder myself a serial debug cable one day

19:58 <missMyN900> hopefully it will get fixed upstream

19:59 <missMyN900> there may be people experimenting with this with SBCs (such as Pine A64)

20:06 <missMyN900> if anyone wants to get a quick list of the PP wakeup sources, this is the easy way to get it: "cat /sys/class/wakeup/*/name"

20:46 <missMyN900> humpelstilzchen[: one question that I have been wanting to ask (somewhere) but forgot to is, does the alternative modem firmware work with ofono too?