cockroach has quit [Quit: leaving]
elastic_dog is now known as Guest1481
elastic_1 has joined #maemo-leste
Guest1481 has quit [Killed (copper.libera.chat (Nickname regained by services))]
elastic_1 is now known as elastic_dog
moparisthebest has quit [Ping timeout: 248 seconds]
joerg has quit [Ping timeout: 250 seconds]
joerg has joined #maemo-leste
<sicelo> yes. may take many cycles, but it'll get there
macros_2ndPC has quit [Ping timeout: 240 seconds]
shhwip has joined #maemo-leste
<shhwip> hello!
macros_2ndPC has joined #maemo-leste
<sicelo> hi
<shhwip> hi sicelo, do you use Maemo Leste?
<sicelo> sometimes. what would you like to know
<shhwip> what made you choose that OS over all the other ones?
<sicelo> um ...
<shhwip> im writing a research paper for my operating systems class and my focus is on FOSS mobile OS
<sicelo> because it's debian-based
<shhwip> do you have any issues with it?
<sicelo> no, not that i can think of.
<shhwip> what device do you use it on?
<sicelo> nokia n900, and occasionally, motorola droid 4
<shhwip> you say that you use it sometimes, does that mean its not your daily driver?
<sicelo> yes. droid 4 is more daily drivable in general, but i had to give mine away for a while
<shhwip> why do you not use maemo-leste as a daily driver? is it just the n900 hardware that gets in the way?
doc has quit [Quit: Things to do]
<sicelo> I'd say so, yes.
<shhwip> any plans to get the pinephone?
<sicelo> i was daily driving droid 4 for just over a month
moparisthebest has joined #maemo-leste
<shhwip> then you had to give it away?
doc has joined #maemo-leste
<sicelo> yes, temporarily. my mom needed a phone
<shhwip> oh! did you leave it on maemo for her?
ceene has joined #maemo-leste
<sicelo> nah, she doesn't use linux, and I'm not looking to provide tech support to anyone. i don't even have enough time now to contribute to leste
<shhwip> did you used to contribute?
<sicelo> yeah and i plan to get back to it
Twig has joined #maemo-leste
Supositware has quit [Ping timeout: 252 seconds]
<freemangordon> uvos: any idea what lid_cover_pipe in mce should be? also, isn;t it supposed to be inited to COVER_OPEN?
shhwip has quit [Quit: leaving]
<freemangordon> now this will change the things :(
uvos has joined #maemo-leste
<uvos> freemangordon: change what?
<uvos> freemangordon: this is to wake the device when the camera shutter is openend on n900
<freemangordon> uvos: sure, but it is not inited properly in our mce
<uvos> ah ok
<freemangordon> also, I am not sure this is camera cover
<freemangordon> see ts_enable_policy
<freemangordon> "if (lid_cover_state == COVER_CLOSED)"
<uvos> ok
<uvos> maybe we should initalize all datapipes somewhere centrally
<freemangordon> well, the one who creates shall inti I guess
<freemangordon> but anyway
<uvos> but they are global
<uvos> they are created in mce.c
<freemangordon> anyway, I'll try to fix that
<uvos> setup_datapipe(&system_state_pipe, READ_WRITE, DONT_FREE_CACHE,
<freemangordon> I suspect this is the reason why ts_event_control() is called in more places than in fremantle
<freemangordon> :nod:
<freemangordon> event-input shall init it
<uvos> it is inited to 0
<uvos> right there
<freemangordon> which is wrong
<uvos> sure but this is where it shal be changed
<freemangordon> should be COVER_OPEN (1_
<freemangordon> maybe
<freemangordon> the point is that change will broadly change the behaviour
<freemangordon> as now we have at least one extra ts_event_control(TRUE) call
<freemangordon> I'll have to clean-up them all
<freemangordon> ttyl
uvos has quit [Ping timeout: 264 seconds]
ceene has quit [Read error: Connection reset by peer]
_CN_ has joined #maemo-leste
arno11 has joined #maemo-leste
<arno11> Wizzup: (powercell) great !
arno11 has left #maemo-leste [#maemo-leste]
akossh has joined #maemo-leste
doc has quit [Ping timeout: 255 seconds]
doc has joined #maemo-leste
xmn has quit [Ping timeout: 248 seconds]
arno11 has joined #maemo-leste
<arno11> *polarcell
arno11 has left #maemo-leste [#maemo-leste]
victor_ has joined #maemo-leste
victor_ has quit [Client Quit]
pere has quit [Ping timeout: 246 seconds]
<Wizzup> arno11: I pushed the cmt_speech perms fix to leste-config
Pali has joined #maemo-leste
pere has joined #maemo-leste
fab_ has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
Supositware has joined #maemo-leste
ikmaak has quit [Ping timeout: 252 seconds]
ikmaak has joined #maemo-leste
Supositware has quit [Ping timeout: 250 seconds]
Twig has quit [Ping timeout: 240 seconds]
Twig has joined #maemo-leste
fab_ has quit [Quit: fab_]
_CN_ has quit [Remote host closed the connection]
fab_ has joined #maemo-leste
Supositware has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: closed]
<freemangordon> uvos: I think I fixed input-ctrl coding style, please have a look when you have som espare time
<freemangordon> tmlind: btw, I saw ants on n900 as well
norayr has joined #maemo-leste
xmn has joined #maemo-leste
elastic_dog has quit [Read error: Connection reset by peer]
Astra[m] has joined #maemo-leste
<freemangordon> Wizzup: alarm TS issue should be fixed, please test
elastic_dog has joined #maemo-leste
pere has quit [Ping timeout: 255 seconds]
Supositware has quit [Ping timeout: 246 seconds]
Supositware has joined #maemo-leste
pere has joined #maemo-leste
<norayr> Folks libnotify notifications dont trigger vibration? I enabled vibrations but dino doesnt cause vibration. I need to not miss notifs, what can i do?
<freemangordon> norayr: leste notifications daemon lacks such functionality, see backscroll for what we're going to do
<freemangordon> noraso, ht exactly vibration pattern do you expect?
<tmlind> freemangordon: sounds like some pvr bug then
<tmlind> maybe firmware?
<norayr> I dont know
<norayr> Dz once
<norayr> To notice that i got a message
<freemangordon> tmlind: mm
<freemangordon> *mhm
<freemangordon> norayr: ok, but how the system should know what kind of vibration it should play? what is dino?
<freemangordon> (that question is asked by both me and libnotify)
<norayr> Dino is a jabber client that sends notifs via libnotify
<freemangordon> like, for email we have one vibration pattern, but for sms (for example) another
<norayr> And maemo shows maemo notifications
<norayr> So system knows
<freemangordon> sure, but vibration is not part of desktop notifications specs, AFAIK
<norayr> But when does vibration happen?
<norayr> I enabled it in settings
<norayr> For a call?
<norayr> Can we add it to desktop notification spec?
Supositware has quit [Ping timeout: 240 seconds]
<freemangordon> we?
<norayr> How people are supposed to get notified?
<freemangordon> well, those specs are maintained by freedesktop org, iiuc, ask them maybe
<norayr> Understand
<freemangordon> native maemo applications use exensions
<norayr> Still lets discuss it or think
<freemangordon> sure
<norayr> Because we have libnotify
<norayr> And maemo feels it
<norayr> And i always miss notificatiions
<freemangordon> I am not saying we shall not discuss, what I am saying that vanilla desktop notifications specs does not support vibration
<norayr> Because even if i look at the droid every 10 minutes i miss
<norayr> And sometimes my internal clock doesnt work well
<norayr> And 10 is 20 or 30
<freemangordon> and in order dino to make phone vibrate, somebody shall teach it to tell maemo that it wants vibration
<norayr> And imiss important stuff
<freemangordon> norayr: got it
<norayr> But we r a linux distro, and we use desktop programs here and desktop programs use libnotify already
<freemangordon> but, libnotify does not support vibration
<freemangordon> there is no standard way an application to tell libnotify that it wants device to vibrate
<freemangordon> see the link ^^^
<norayr> But can we when showing msg about notification also vibrate ourselves? We cannot change every linux program.
<freemangordon> for every notification?
<freemangordon> maybe, but I am not convinced this is a good idea
<norayr> Since january i only use d4, i have only it and pinephone, pinephone i dont really use so i am a real case of usage
<norayr> Thank u
<norayr> Please discuss it
<freemangordon> norayr: there is no use to convince me about you having a real usecase :)
<freemangordon> I understand that
<norayr> Maybe someone else would use some mail client or something else.
<norayr> (((:
<freemangordon> the point is that when we make system-wide changes/decisions, we shall consider all possible usecases
<norayr> Sure
<norayr> I understand
<freemangordon> BTW, do you know what category dino uses when calling libnotify?
<freemangordon> norayr: BTW, it seems that dino does not use libnotify
<freemangordon> at least upstream seems to use GNotify
<freemangordon> which, seems to not even support sound
<freemangordon> gh
<freemangordon> *ugh
<freemangordon> they seem to play their own sound
<freemangordon> hmm, not reall
<freemangordon> y
<freemangordon> norayr: I think I will be able to do something these days
uvos has joined #maemo-leste
Twig has quit [Remote host closed the connection]
<freemangordon> uvos: I think we can get vibration for free, basically: https://github.com/maemo-leste/hildon-plugins-notify-sv/blob/master/lib/nsv-plugin.c#L41
norayr has left #maemo-leste [Error from remote client]
uvos has quit [Ping timeout: 240 seconds]
Supositware has joined #maemo-leste
norayr has joined #maemo-leste
<norayr> freemangordon: sorry, i am back online. thank you.
nela has quit [Quit: bye]
nela has joined #maemo-leste
Supositware has quit [Quit: Leaving.]
arno11 has joined #maemo-leste
<arno11> Wizzup: success ! latency removed: 20-30 ms in real conditions. it was tricky. Another process was the cause of latency (cmtspeech_ofono_test). And the code is not running exactly the same way for inbound and outbound calls
<arno11> few lines modified and it's ok
<arno11> but the code needs to be improved a bit
<Wizzup> arno11: ok, great, please share
* Wizzup zzz first
<arno11> yes lol
<arno11> gn
arno11 has left #maemo-leste [#maemo-leste]
fab_ has quit [Quit: fab_]
LjL has quit [Read error: Connection reset by peer]
LjL has joined #maemo-leste
akossh has quit [Remote host closed the connection]