<Wizzup> freemangordon: is it possible to configure where the sent emails go in modest?
<Wizzup> I might try to add that
<Wizzup> (they go into a different dir than thunderbirds)
ceene has quit [Remote host closed the connection]
ceene has joined #maemo-leste
zhxt has joined #maemo-leste
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
R0b0t1` has quit [Ping timeout: 252 seconds]
zhxt has quit [Ping timeout: 245 seconds]
mardy has joined #maemo-leste
zhxt has joined #maemo-leste
pere has quit [Ping timeout: 252 seconds]
R0b0t1` has joined #maemo-leste
pere has joined #maemo-leste
Twig has joined #maemo-leste
xmn has quit [Quit: ZZZzzz…]
Pali has joined #maemo-leste
inky_ has joined #maemo-leste
_inky has quit [Ping timeout: 268 seconds]
zhxt has quit [Ping timeout: 265 seconds]
_inky has joined #maemo-leste
uvos has joined #maemo-leste
<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)
<uvos> and the way als works has changed
<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.
<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
<uvos> this elemitates the flicker effect from changing brightness levels whilest in a train or whatever
<uvos> if you dont like the way this works you can add NoAlsLowering=0 to the [DisplayBrightness] in your 99-user.ini
<uvos> to get the old behavior
<Wizzup> the flickering effect we have in brightness is related to a gconf bug, no?
<Wizzup> s/gconf/gtk/
<uvos> Wizzup: no
<uvos> Wizzup: the flikering effect with the brightess adjusting slider is a gtk2 bug
<uvos> but i mean the fact that the display will flicker back and fourth between brightess values quickly when als changes alot
<uvos> aslo this change dosent change the way the slider works ofc
<uvos> it can still lower the brightness
<uvos> als cant lower the brightness while the display is on
<Wizzup> I see
<Wizzup> makes sense
<uvos> parazyd: while reviewing https://github.com/maemo-leste/leste-config/pull/25 please also decide if pp also needs battery-guard
<uvos> Wizzup: oh btw
<uvos> any idea what the powersaveing thing in the display control pannel applet is supposed to do?
<uvos> it sets a gconf key in /system/osso/dsm/display/ that mce has never actually read
<Wizzup> what key is that
<uvos> /system/osso/dsm/display/enable_power_saving
belcher_ is now known as belcher
<Wizzup> grep doesn't find anything in my local repos
<uvos> ok ill just comment out the button for now with a TODO: where should this go
<Wizzup> hmmm
zhxt has joined #maemo-leste
<uvos> interesting
<uvos> no its unrelated
<uvos> looks enable_power_saving is supposed to change how cabc works
<uvos> ill coment it out with a TODO and link the commit to https://github.com/maemo-leste/mce/issues/27
<uvos> iirc the problem with this was the lack of hw with wokrking kernel api to test it with
_inky has quit [Read error: Connection reset by peer]
zhxt has quit [Ping timeout: 245 seconds]
zhxt has joined #maemo-leste
_inky has joined #maemo-leste
<sicelo> Wizzup: tmlind: i see some omap_hsmmc commits referencing wl1251. just wondering if N900 will not be affected in one way or another
zhxt has quit [Ping timeout: 245 seconds]
<Wizzup> we passed the ngi dapsi evaluation and proceed to the second round (funding)
<Wizzup> plan is to see if we can find people that can help with the telepathy and conversations stuff, also gtk3/qt5
pere has quit [Ping timeout: 245 seconds]
<MartijnBraam[m]> \o/
<MartijnBraam[m]> pmos passed too, fun feedback
<Wizzup> yay :)
elastic_dog has quit [Ping timeout: 246 seconds]
elastic_dog has joined #maemo-leste
<sicelo> those are great news for both projects :-)
<sicelo> am i allowed to ask what the pmos project is about, MartijnBraam[m] ? or it's the OS as a whole?
<MartijnBraam[m]> the OS as a whole, we got the funding to do general maintenance
<sicelo> cool
<parazyd> MartijnBraam[m]: Congrats!
<parazyd> uvos: ACK, will review later today
<MartijnBraam[m]> the leste grant was specifically for the vpn stuff?
<parazyd> First part. Second part is Telepathy and protocols (Signal, Jami, Matrix, XMPP)
<MartijnBraam[m]> oh neato
<Wizzup> that and conversations/sms/chat ui
<MartijnBraam[m]> I thought xmpp already worked in the old maemo?
<uvos> old maemo is closed soruce
<uvos> parazyd: thanks :)
<MartijnBraam[m]> right, ofcourse
xmn has joined #maemo-leste
inky has joined #maemo-leste
<bencoh> xmpp on fremantle (specifically in rtcom) isn't that great btw
<MartijnBraam[m]> the only xmpp i've used on maemo was the gchat support, worked fine at the time
<bencoh> integration is great, but a few things made it kinda quirky, compared to pidgin
<bencoh> iirc the way it handles channels (ie leaving channel when closing the window, afair) made it quite non-practical for instance
<bencoh> (at least that's what I remember)
<Wizzup> that should be quite easily solveable
<bencoh> yeah
<Wizzup> (were it not for the fact that it's not foss)
<Wizzup> but _we_ can fix that
<bencoh> well, not on fremantle, since it's closed-source
<bencoh> but yeah
<bencoh> exactly :)
inky_ has quit [Ping timeout: 245 seconds]
<bencoh> I find it interesting that they'd sponsor vpn-related work first, and that communication would come second only
<Wizzup> that is how we laid it out
<bencoh> ah, alright
<Wizzup> we and that for with good reasons, first is that osso-abook was nowhere near done at that time
<Wizzup> second is that the tor/wg is neat, and the call was aimed at privacy/security
uvos has quit [Ping timeout: 245 seconds]
<bencoh> it sure is neat :)
<Wizzup> and it was not really dependent on other parts being finished
<Wizzup> I mean also a good fit for the call
<MartijnBraam[m]> wg is brilliant
<bencoh> which reminds me ... is wg part of devuan-stable?
<bencoh> (I thought it only landed in latest debian)
<Wizzup> it is definitely in backports, I need to check (and update instructions potentially)
<bencoh> ah, backports
<bencoh> alright :)
<Wizzup> yeah... good point
<bencoh> we'd probably need to import it in leste's repos then
<bencoh> in some way or another
<bencoh> at least for the beowulf dist
Danct12 has quit [Quit: Quitting]
<Wizzup> bencoh: yeah
<freemangordon> great!
xmn has quit [Remote host closed the connection]
xmn has joined #maemo-leste
xmn has quit [Client Quit]
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 245 seconds]
xmn has joined #maemo-leste
Danct12 has joined #maemo-leste
Danct12 has quit [Client Quit]
uvos has joined #maemo-leste
dgamer69 has joined #maemo-leste
<dgamer69> hello everyone, I am back
<dgamer69> and still compiling
<dgamer69> finished compiling
<tmlind> sicelo: i think n900 has wl1251 on spi so not affected by mmc changes
<sicelo> ah great then. indeed.
<dgamer69> golly gee whiz
<dgamer69> the 3d acceloration thingy didn't work
<dgamer69> *acceleration
<freemangordon> install virtualbox
Twig has quit [Ping timeout: 265 seconds]
Danct12 has joined #maemo-leste
<dgamer69> I can't
Twig has joined #maemo-leste
dgamer69 has quit [Ping timeout: 245 seconds]
<sicelo> or be patient ... i was running leste vm without accel too, on 4th gen i5. at leat *I* still found it usable
<sicelo> ymmv
dgamer69 has joined #maemo-leste
dreamer has quit [Ping timeout: 250 seconds]
dreamer has joined #maemo-leste
_inky has quit [Ping timeout: 245 seconds]
_inky has joined #maemo-leste
<Wizzup> the sigmakey is just a random smartcard reader with sim card
<Wizzup> lol
<Wizzup> ok
Danct12 has quit [Quit: Quitting]
<uvos> not uncommon in hardware drm devices
<Wizzup> yeah but it just kinda sticks out :P
<Wizzup> nice to have a generic smartcard reader at least
inky has joined #maemo-leste
inky_ has quit [Ping timeout: 245 seconds]
_inky has quit [Ping timeout: 245 seconds]
<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?
<uvos> parazyd: no adding the module to mce and speifcing a voltage is enough
<uvos> parazyd: really its about how the pp behaves
<uvos> parazyd: ie when dose the kernel perfom a low voltage shutdown, and what voltage results on the battery
<uvos> and what voltage if any is required to perform lower end callibration
<uvos> configuration should be based on these things
akossh has joined #maemo-leste
<uvos> btw parazyd
<parazyd> ok
<uvos> you mentiond at some point that brightness on the pp was non linear
<uvos> and als dident work so well because of this
<parazyd> hmm I don't exactly remember
<parazyd> I know it works though
<parazyd> Brightness control, that is
<uvos> if the pp reacts poorly please also ajust these values to taste
<uvos> (as the defaults are mapphone optimized)
<parazyd> Will do
<parazyd> Thanks for the reminder
_inky has joined #maemo-leste
pere has joined #maemo-leste
dgamer69 has quit [Ping timeout: 265 seconds]
dgamer69 has joined #maemo-leste
uvos has quit [Ping timeout: 245 seconds]
uvos has joined #maemo-leste
Twig has quit [Ping timeout: 245 seconds]
l_bratch has quit [Remote host closed the connection]
l_bratch has joined #maemo-leste
dgamer69 has quit [Ping timeout: 245 seconds]
avoidr has quit [Ping timeout: 265 seconds]
avoidr has joined #maemo-leste
mardy has quit [Quit: WeeChat 2.8]
<uvos> who is halftux?
<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)
<uvos> he is maintainer of the mihphoto leste pacakge but currently not reponsive in this role.
<uvos> so was wondering how to contact him
<sicelo> there should also be an email in the commits. i have his other email around somewhere, but what does "not responsive" mean? :-/
<uvos> dosent react to an open pr, dosent react to an email
<uvos> with a month ish lead time
l_bratch has quit [Quit: Leaving]
l_bratch has joined #maemo-leste
Langoor_ has quit [Ping timeout: 252 seconds]
uvos has quit [Remote host closed the connection]
uvos has joined #maemo-leste
<Wizzup> btw - I don't get the charging led pattern on the n900
<Wizzup> uvos: I have his email, maybe ping him on the pr?
<uvos> is it enabled?
<uvos> could you give me mce log?
<uvos> use openrc to stop mce
* Wizzup makes a note to do that tomorrow
<Wizzup> btw, something I was wondering about, I wonder if it makes sense to set up syslog in such a way that it is much easier to share debug logs
<Wizzup> we could have /var/log/maemo/daemons/mce.log
<uvos> and run it with mce --verbose --verbose in a "su -" (ie clean env) root shell
<uvos> Wizzup: not usefull without makeing mce verbose
<uvos> in this case at least
<uvos> but yeah sure
<uvos> anyhow do that and then plug the charger in and out a couple of times with some time in between, 2 min should od
<uvos> *do
<Wizzup> why with time in between?
<uvos> to see if udev is reporting events
<uvos> er upower
<uvos> mce will log when it gets upower events
<uvos> but they come in infrequently
<Wizzup> running now
<uvos> also make sure the pattern is enabled in the first place :P
<Wizzup> it is
<Wizzup> uvos: it seems to get the messages right away
<Wizzup> but it only seems to change patterns on charger off it seems
<Wizzup> hmm: mce: LED pattern PatternBatteryCharging deactivated
<uvos> ok
<uvos> no idea who should be starting the pattern
<uvos> maybe the upower module
<Wizzup> mce
<uvos> i mean in mce
<Wizzup> oh
<Wizzup> btw: PatternBatteryCharging = true
<uvos> yeah sure log also registers it mce: led-dbus: PatternBatteryCharging enabled
<uvos> hmm
<uvos> something is off here
<uvos> mce: pattern: PatternError, active: 0 comes from led-lysti
<uvos> (grr annoying legacy modules that dont annouce what module the log statment comes from)
<uvos> but the patterns are registerd twice for some reason
<uvos> nvm
<uvos> its just really verbose
inky has quit [Ping timeout: 265 seconds]
_inky has quit [Ping timeout: 245 seconds]
<uvos> its there
<uvos> maybe check if it executes this via gdb
<uvos> if you actviate the pattern via dbus dose it show?
<Wizzup> sure, let me try
<Wizzup> do you have a way to do it handy?
<Wizzup> ah: dbus-send --system --type=method_call --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.req_led_pattern_activate string:"PatternCommunicationIM"
<uvos> yeah
<uvos> also check the policy in mce ini
<uvos> looks like it has policy 4: only show pattern if the display is off, or if in acting dead
<Wizzup> that is fine I think
<uvos> sure if your not expecting to see it while the display is on ;)
<Wizzup> I am not
<Wizzup> hm the ts on my n900 is not happy atm
<Wizzup> (was updating)
<Wizzup> ah, dist-upgrade was required to remove the old rotation support
<Wizzup> I don't see anything when I try to activate the pattern I think
<Wizzup> wait..
<Wizzup> manually activating it works
<Wizzup> and it disappears on display on, and then comes back when display goes off
<Wizzup> so something just doesn't trigger it I think in mce upower
<uvos> Wizzup: ok so the dbus call results in the exact same datapipe call here: https://github.com/maemo-leste/mce/blob/abc429bef65971274d3fea45cc73ced4d617757e/src/modules/led-dbus.c#L101
<uvos> not sure why that would be
<Wizzup> I can step through it later if you'd like
<Wizzup> at least I got my droid3 static kernel to boot, tomorrow I will try to load kexecboot
<Wizzup> the display not turning on has me a bit worried that my config isn't ok yet though :P
<uvos> ok
<uvos> well some progress at least
<Wizzup> yeah
<uvos> wait lol
<uvos> that execute_datapipe is bullshit
<uvos> USE_CACHE
<uvos> its retiggering the last input pattern
<uvos> which is null in this case
<Wizzup> ah
<Wizzup> good eye
<uvos> ok ill fix it tomorrow
<Wizzup> cool
uvos has quit [Ping timeout: 265 seconds]
Pali has quit [Ping timeout: 245 seconds]
belcher has quit [Ping timeout: 264 seconds]
belcher has joined #maemo-leste