07:30 <kiva> At last I found reason for unexpected power-offs with Pinephone Keyboard, reason is simple phone side battery can go empty in whole day use, although connected with charger.

07:32 <gnarface> oh, i could have warned you about that, sorry

07:33 <gnarface> even if you have a spec charger for those things, it's easy to outrun it with regular CPU load

07:33 <gnarface> they can only pull in about 15W as a theoretical max, but i've only seen mine able to draw about 11

07:34 <gnarface> so yea, uh... keep the screen brightness low

07:34 <gnarface> sleeping it is better

07:34 <kiva> Solution 1. We need two battery indicators near clock. Solution 2. Slow down CPU that much that Keyboard battery can give enough power when 10% phone side battery left.

07:43 <kiva> My screen brightness is lowest anyway, because I like when white is not any brighter than papers near me...it would be nice if there is more brightness levels between lowest and whole black. Possible?

07:47 <kiva> Solution 3. Phone go hilbernate when only 5% battery left and wake up when Keyboard side battery has given enough power to 10%.

07:52 <kiva> My charger takes between 24.9-25.1 Watts (measuring right now), but I think connection between keyboard side and phone is much less.

07:59 <kiva> Now I miss feature from 4 core PowerPC Macs, power off cpu cores one by one.

07:59 <gnarface> the screen brightness thing is theoretically possible but afaik usually not without swapping the LCD itself for a different model; i know this only because early on there were different models of LCD in different batches of pinephones, and it started causing problems where minimum brightness would actually turn the screen off completely for some people while still be too bright for others

08:00 <gnarface> ...though some DTB changes in theory might also improve matters if it's a situation where the panel isn't being exactly properly powered - i don't know for sure that those fixes are all completely dialed in for every model, they may have just shipped some compromised middle ground

08:01 <gnarface> the problem might largely be about just finding proper specifications through some method better than trial+error

08:02 <gnarface> for some models it seems they just have a higher minimum brightness too though, so improvements aren't guaranteed

08:03 <gnarface> (their deal with the manufacturer allowed the manufacturer to swap out components "of equal value" as supply issues arose and the LCD and the RAM were two things the manufacturer was especially "fluid" about)

08:05 <gnarface> as for powering off CPU cores individually ... i believe this hardware actually does have that feature in fact... it's pretty common on ARM i'm told, but last person i heard talking about messing with that couldn't bring them back up without crashing the phone

08:05 <gnarface> some software work no doubt needs to be done in the kernel for that still

08:07 <kiva> So good old Mac OSX days 20 years ago they could do that but Linux cannot still cannot handle it?

08:07 <gnarface> heh, well ARM is still very immature on Linux... which is saying something because Linux is well ahead of BSD still

08:08 <gnarface> the best ARM support is still locked up in proprietary Google-kernel-only Android parts, but i'm told that the support we have in Linux is very much on par with Android from 10 or so years ago

08:08 <gnarface> so yea, just give it time

08:10 <gnarface> ah a PowerPC phone... now that would be something to see :)

08:10 <gnarface> i kinda feel like we might have really lost something important when Apple switched to Intel chips...

08:10 <gnarface> i didn't at the time, but i'm coming around

08:13 <kiva> We really lost when Apple moving to Intel and away from path what was built OSX 10.4. After that all with Apple going wrong.

08:24 <kiva> I think there will be huge market for small retro PowerPC-machine that "accidentally" can run Mac OS9-OSX10.4 and use old firewire hardware.

08:27 <kiva> Has anybody try SheepShaver MacOS9 emulator with Pinephone? ;)

08:32 <kiva> or Droid4?

09:00 <kiva> if somebody test, please write there how well it works: https://talk.maemo.org/showthread.php?t=101449

13:50 <uvos__> sphone theoreticly has support for dtmf, but no real backend (ie not commtest) implements support. Mainly because the d4 dosent support dtmf on a sane interface. if dtmf works on n900 via ofono dibus calls it should be trivial to implement in sphones ofono backend

13:50 <uvos__> vcm im not sure, but probubly would not be too hard either

13:51 <uvos__> point is that all the ui bits and sphone framework bits are there for dtmf

15:41 <Wizzup> does setting the screen brightness on the pinephone ewor kfo you guys?

15:41 <Wizzup> work for you guys*

16:00 <sicelo> kiva: i have considered your option one in the past ... see https://github.com/maemo-leste/bugtracker/issues/726 ... so your #1 is #2 in the first comment there. anyway, maybe someday i'll have time to implement it. not making any promises :-)

16:01 <sicelo> uvos__: seems n900's dtmf is now broken too. bitrot i guess

16:04 <sicelo> btw, something to implement in sphone - the call history should show the direction of the call (incoming/outgoing)

16:10 <Wizzup> and it should take the remote_name from the db instead of matching it to a contact I think

19:31 <sicelo> kiva: by the way, out of curiousity/interest, does the pinephone keyboard's battery actually show up in leste's /sys/class/power_supply/ ?

22:15 <uvos> Wizzup: lel died

22:16 <uvos> Wizzup: But what if the contact is renamed? @name from db

22:17 <uvos> i gues the issue you take with sphone looking up the contacts is that it can be a bit slow

22:17 <uvos> ideal solution for that would be for sphone to show the list with the db name right away and then update it as the lookups come in.

22:18 <uvos> sicelo: :\

22:45 <inky> > At last I found reason for unexpected power-offs with Pinephone Keyboard, reason is simple phone side battery can go empty in whole day use, although connected with charger.

22:45 <inky> i had to fix hw of pinephone.

22:45 <inky> shorten the diod.

22:45 <Wizzup> uvos: then the remote_name will be updated, like on maemo

22:50 <inky> here https://xnux.eu/pinephone-keyboard/faq.html

22:50 <inky> section:

22:50 <inky> Keyboard battery is charging slowly or not at all

22:50 <inky> somewhere was a tutorial with photos.

22:50 <uvos> Wizzup: dosent happen atm

22:51 <uvos> also not sure how you invision that working

22:52 <inky> https://forum.pine64.org/showthread.php?tid=16979&pid=111414#pid111414#ts

22:52 <uvos> since eds is a shared database any random application can decide to edit. So the only way i see this working is if eds gets a plugin to edit rtcom-el's database

22:52 <inky> oh kiva is not here.