| Wizzup | freemangordon: is it possible to configure where the sent emails go in modest? | 02:31 |
|---|---|---|
| Wizzup | I might try to add that | 02:31 |
| Wizzup | (they go into a different dir than thunderbirds) | 02:32 |
| uvos | so mce update is comeing down the pipe that: adds the new dbus interfaces (ofc untill you unload the rtconf-gconf module in favor or rtconf-ini or -gsettings the gconf interfaces will remain and both update the other) | 11:17 |
| uvos | and the way als works has changed | 11:18 |
| uvos | so since iio-sensor-proxy only brodcasts changes instead of x samples per second (and thats all it can do since it wants to save a bounch of power by using hw triggering where available) there was no way to really filter it. | 11:19 |
| uvos | so i now implemented the method android used to use =<2.3: the display is only allowed to increase in brightness while it is on, and can only return to a lower brightness though a display off -> display on cycle | 11:21 |
| uvos | this elemitates the flicker effect from changing brightness levels whilest in a train or whatever | 11:22 |
| uvos | if you dont like the way this works you can add NoAlsLowering=0 to the [DisplayBrightness] in your 99-user.ini | 11:22 |
| uvos | to get the old behavior | 11:22 |
| uvos | parazyd: please review https://github.com/maemo-leste/leste-config/pull/25 | 11:38 |
| Wizzup | the flickering effect we have in brightness is related to a gconf bug, no? | 11:39 |
| Wizzup | s/gconf/gtk/ | 11:39 |
| uvos | Wizzup: no | 11:39 |
| uvos | Wizzup: the flikering effect with the brightess adjusting slider is a gtk2 bug | 11:40 |
| uvos | but i mean the fact that the display will flicker back and fourth between brightess values quickly when als changes alot | 11:40 |
| uvos | aslo this change dosent change the way the slider works ofc | 11:41 |
| uvos | it can still lower the brightness | 11:41 |
| uvos | als cant lower the brightness while the display is on | 11:41 |
| Wizzup | I see | 11:46 |
| Wizzup | makes sense | 11:46 |
| uvos | parazyd: while reviewing https://github.com/maemo-leste/leste-config/pull/25 please also decide if pp also needs battery-guard | 11:49 |
| uvos | Wizzup: oh btw | 12:00 |
| uvos | any idea what the powersaveing thing in the display control pannel applet is supposed to do? | 12:01 |
| uvos | it sets a gconf key in /system/osso/dsm/display/ that mce has never actually read | 12:02 |
| Wizzup | what key is that | 12:02 |
| uvos | /system/osso/dsm/display/enable_power_saving | 12:02 |
| Wizzup | grep doesn't find anything in my local repos | 12:09 |
| uvos | ok ill just comment out the button for now with a TODO: where should this go | 12:10 |
| Wizzup | hmmm | 12:11 |
| Wizzup | https://git.sailfishos.org/lpotter/mce/blob/d29be0ee51d5b4fd939a8946b5da626987dca16a/modules/powersavemode.h#L35 | 12:11 |
| uvos | interesting | 12:11 |
| uvos | no its unrelated | 12:15 |
| uvos | looks enable_power_saving is supposed to change how cabc works | 12:16 |
| uvos | ill coment it out with a TODO and link the commit to https://github.com/maemo-leste/mce/issues/27 | 12:18 |
| uvos | iirc the problem with this was the lack of hw with wokrking kernel api to test it with | 12:21 |
| sicelo | Wizzup: tmlind: i see some omap_hsmmc commits referencing wl1251. just wondering if N900 will not be affected in one way or another | 13:29 |
| Wizzup | we passed the ngi dapsi evaluation and proceed to the second round (funding) | 13:55 |
| Wizzup | plan is to see if we can find people that can help with the telepathy and conversations stuff, also gtk3/qt5 | 13:55 |
| MartijnBraam[m] | \o/ | 14:07 |
| MartijnBraam[m] | pmos passed too, fun feedback | 14:07 |
| Wizzup | yay :) | 14:21 |
| sicelo | those are great news for both projects :-) | 14:40 |
| sicelo | am i allowed to ask what the pmos project is about, MartijnBraam[m] ? or it's the OS as a whole? | 14:42 |
| MartijnBraam[m] | the OS as a whole, we got the funding to do general maintenance | 14:42 |
| sicelo | cool | 14:44 |
| parazyd | MartijnBraam[m]: Congrats! | 14:50 |
| parazyd | uvos: ACK, will review later today | 14:50 |
| MartijnBraam[m] | the leste grant was specifically for the vpn stuff? | 14:50 |
| parazyd | First part. Second part is Telepathy and protocols (Signal, Jami, Matrix, XMPP) | 14:51 |
| MartijnBraam[m] | oh neato | 14:52 |
| Wizzup | that and conversations/sms/chat ui | 14:53 |
| MartijnBraam[m] | I thought xmpp already worked in the old maemo? | 14:55 |
| uvos | old maemo is closed soruce | 14:57 |
| uvos | parazyd: thanks :) | 14:58 |
| MartijnBraam[m] | right, ofcourse | 14:58 |
| bencoh | xmpp on fremantle (specifically in rtcom) isn't that great btw | 15:20 |
| MartijnBraam[m] | the only xmpp i've used on maemo was the gchat support, worked fine at the time | 15:21 |
| bencoh | integration is great, but a few things made it kinda quirky, compared to pidgin | 15:21 |
| bencoh | iirc the way it handles channels (ie leaving channel when closing the window, afair) made it quite non-practical for instance | 15:21 |
| bencoh | (at least that's what I remember) | 15:22 |
| Wizzup | that should be quite easily solveable | 15:22 |
| bencoh | yeah | 15:22 |
| Wizzup | (were it not for the fact that it's not foss) | 15:22 |
| Wizzup | but _we_ can fix that | 15:22 |
| bencoh | well, not on fremantle, since it's closed-source | 15:22 |
| bencoh | but yeah | 15:22 |
| bencoh | exactly :) | 15:22 |
| bencoh | I find it interesting that they'd sponsor vpn-related work first, and that communication would come second only | 15:23 |
| Wizzup | that is how we laid it out | 15:24 |
| bencoh | ah, alright | 15:24 |
| Wizzup | we and that for with good reasons, first is that osso-abook was nowhere near done at that time | 15:24 |
| Wizzup | second is that the tor/wg is neat, and the call was aimed at privacy/security | 15:25 |
| bencoh | it sure is neat :) | 15:25 |
| Wizzup | and it was not really dependent on other parts being finished | 15:25 |
| Wizzup | I mean also a good fit for the call | 15:25 |
| MartijnBraam[m] | wg is brilliant | 15:25 |
| bencoh | which reminds me ... is wg part of devuan-stable? | 15:26 |
| bencoh | (I thought it only landed in latest debian) | 15:26 |
| Wizzup | it is definitely in backports, I need to check (and update instructions potentially) | 15:26 |
| bencoh | ah, backports | 15:26 |
| bencoh | alright :) | 15:26 |
| Wizzup | yeah... good point | 15:26 |
| bencoh | we'd probably need to import it in leste's repos then | 15:27 |
| bencoh | in some way or another | 15:27 |
| bencoh | at least for the beowulf dist | 15:27 |
| Wizzup | bencoh: yeah | 15:29 |
| freemangordon | great! | 15:32 |
| dgamer69 | hello everyone, I am back | 16:28 |
| dgamer69 | and still compiling | 16:28 |
| dgamer69 | finished compiling | 16:34 |
| tmlind | sicelo: i think n900 has wl1251 on spi so not affected by mmc changes | 16:35 |
| sicelo | ah great then. indeed. | 16:46 |
| dgamer69 | golly gee whiz | 16:47 |
| dgamer69 | the 3d acceloration thingy didn't work | 16:47 |
| dgamer69 | *acceleration | 16:48 |
| freemangordon | install virtualbox | 17:00 |
| dgamer69 | I can't | 17:08 |
| sicelo | or be patient ... i was running leste vm without accel too, on 4th gen i5. at leat *I* still found it usable | 17:15 |
| sicelo | ymmv | 17:15 |
| Wizzup | the sigmakey is just a random smartcard reader with sim card | 19:57 |
| Wizzup | lol | 19:57 |
| Wizzup | ok | 19:57 |
| uvos | not uncommon in hardware drm devices | 20:05 |
| Wizzup | yeah but it just kinda sticks out :P | 20:06 |
| Wizzup | nice to have a generic smartcard reader at least | 20:06 |
| parazyd | uvos: The leste-config changes look good. I can test the battery guard on the Pinephone in the coming days. Is it enough to enable it like this in mce or I need some more things? | 20:14 |
| uvos | parazyd: no adding the module to mce and speifcing a voltage is enough | 20:15 |
| uvos | parazyd: really its about how the pp behaves | 20:15 |
| uvos | parazyd: ie when dose the kernel perfom a low voltage shutdown, and what voltage results on the battery | 20:16 |
| uvos | and what voltage if any is required to perform lower end callibration | 20:16 |
| uvos | configuration should be based on these things | 20:16 |
| uvos | btw parazyd | 20:19 |
| parazyd | ok | 20:19 |
| uvos | you mentiond at some point that brightness on the pp was non linear | 20:20 |
| uvos | and als dident work so well because of this | 20:20 |
| parazyd | hmm I don't exactly remember | 20:20 |
| uvos | i dehardcoded the brightness values see https://github.com/maemo-leste/mce/blob/abc429bef65971274d3fea45cc73ced4d617757e/config/mce.ini#L321 | 20:20 |
| parazyd | I know it works though | 20:20 |
| parazyd | Brightness control, that is | 20:20 |
| uvos | if the pp reacts poorly please also ajust these values to taste | 20:20 |
| uvos | (as the defaults are mapphone optimized) | 20:21 |
| parazyd | Will do | 20:21 |
| parazyd | Thanks for the reminder | 20:21 |
| uvos | who is halftux? | 23:34 |
| sicelo | a great dev from maemo days. iirc a lot of his applications were qt. he's also member of the maemo community ev. he was in this chan a while ago (maybe we lost him during libera move ... can't remember now) | 23:45 |
| uvos | he is maintainer of the mihphoto leste pacakge but currently not reponsive in this role. | 23:48 |
| uvos | so was wondering how to contact him | 23:49 |
| sixwheeledbeast | https://talk.maemo.org/member.php?u=59527 | 23:49 |
| sicelo | there should also be an email in the commits. i have his other email around somewhere, but what does "not responsive" mean? :-/ | 23:50 |
| uvos | dosent react to an open pr, dosent react to an email | 23:51 |
| uvos | with a month ish lead time | 23:51 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!