Wizzup | arno11: got a new polarcell n900 battery :) | 00:04 |
---|---|---|
Wizzup | sicelo: if I plug in a new battery in n900, will the calibration figure that out eventually? | 00:15 |
sicelo | yes. may take many cycles, but it'll get there | 06:35 |
shhwip | hello! | 06:43 |
sicelo | hi | 06:55 |
shhwip | hi sicelo, do you use Maemo Leste? | 07:01 |
sicelo | sometimes. what would you like to know | 07:01 |
shhwip | what made you choose that OS over all the other ones? | 07:02 |
sicelo | um ... | 07:02 |
shhwip | im writing a research paper for my operating systems class and my focus is on FOSS mobile OS | 07:03 |
sicelo | because it's debian-based | 07:03 |
shhwip | do you have any issues with it? | 07:05 |
sicelo | no, not that i can think of. | 07:25 |
shhwip | what device do you use it on? | 07:26 |
sicelo | nokia n900, and occasionally, motorola droid 4 | 07:40 |
shhwip | you say that you use it sometimes, does that mean its not your daily driver? | 07:40 |
sicelo | yes. droid 4 is more daily drivable in general, but i had to give mine away for a while | 07:41 |
shhwip | why do you not use maemo-leste as a daily driver? is it just the n900 hardware that gets in the way? | 07:44 |
sicelo | I'd say so, yes. | 07:46 |
shhwip | any plans to get the pinephone? | 07:47 |
sicelo | i was daily driving droid 4 for just over a month | 07:47 |
shhwip | then you had to give it away? | 07:48 |
sicelo | yes, temporarily. my mom needed a phone | 07:49 |
shhwip | oh! did you leave it on maemo for her? | 07:50 |
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 | 07:52 |
shhwip | did you used to contribute? | 07:53 |
sicelo | yeah and i plan to get back to it | 07:54 |
freemangordon | uvos: any idea what lid_cover_pipe in mce should be? also, isn;t it supposed to be inited to COVER_OPEN? | 08:23 |
freemangordon | yeah: https://github.com/community-ssu/mce/blob/88a69e02c61e24aa272e1f63971e03424c051b09/event-switches.c#L507 :( | 08:34 |
freemangordon | now this will change the things :( | 08:34 |
uvos | freemangordon: change what? | 08:41 |
uvos | freemangordon: this is to wake the device when the camera shutter is openend on n900 | 08:41 |
freemangordon | uvos: sure, but it is not inited properly in our mce | 08:43 |
uvos | ah ok | 08:44 |
freemangordon | also, I am not sure this is camera cover | 08:44 |
freemangordon | see ts_enable_policy | 08:44 |
freemangordon | "if (lid_cover_state == COVER_CLOSED)" | 08:44 |
uvos | ok | 08:45 |
uvos | maybe we should initalize all datapipes somewhere centrally | 08:45 |
freemangordon | well, the one who creates shall inti I guess | 08:46 |
freemangordon | but anyway | 08:46 |
uvos | but they are global | 08:46 |
uvos | they are created in mce.c | 08:46 |
freemangordon | anyway, I'll try to fix that | 08:46 |
uvos | setup_datapipe(&system_state_pipe, READ_WRITE, DONT_FREE_CACHE, | 08:47 |
uvos | https://github.com/maemo-leste/mce/blob/f941e5fbd51f9245776d023fbc6fb56b4d4b8901/src/mce.c#L546 | 08:47 |
freemangordon | I suspect this is the reason why ts_event_control() is called in more places than in fremantle | 08:47 |
freemangordon | :nod: | 08:47 |
freemangordon | event-input shall init it | 08:47 |
uvos | it is inited to 0 | 08:47 |
uvos | right there | 08:47 |
freemangordon | which is wrong | 08:47 |
uvos | sure but this is where it shal be changed | 08:48 |
freemangordon | should be COVER_OPEN (1_ | 08:48 |
freemangordon | maybe | 08:48 |
freemangordon | the point is that change will broadly change the behaviour | 08:48 |
freemangordon | as now we have at least one extra ts_event_control(TRUE) call | 08:49 |
freemangordon | I'll have to clean-up them all | 08:49 |
freemangordon | ttyl | 08:49 |
arno11 | Wizzup: (powercell) great ! | 09:06 |
arno11 | *polarcell | 09:43 |
Wizzup | arno11: I pushed the cmt_speech perms fix to leste-config | 10:35 |
freemangordon | uvos: I think I fixed input-ctrl coding style, please have a look when you have som espare time | 14:55 |
freemangordon | tmlind: btw, I saw ants on n900 as well | 14:56 |
freemangordon | Wizzup: alarm TS issue should be fixed, please test | 15:04 |
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? | 16:10 |
freemangordon | norayr: leste notifications daemon lacks such functionality, see backscroll for what we're going to do | 16:15 |
freemangordon | noraso, ht exactly vibration pattern do you expect? | 16:24 |
tmlind | freemangordon: sounds like some pvr bug then | 16:26 |
tmlind | maybe firmware? | 16:26 |
norayr | I dont know | 16:33 |
norayr | Dz once | 16:33 |
norayr | To notice that i got a message | 16:34 |
freemangordon | tmlind: mm | 16:36 |
freemangordon | *mhm | 16:36 |
freemangordon | norayr: ok, but how the system should know what kind of vibration it should play? what is dino? | 16:37 |
freemangordon | (that question is asked by both me and libnotify) | 16:38 |
norayr | Dino is a jabber client that sends notifs via libnotify | 16:38 |
freemangordon | like, for email we have one vibration pattern, but for sms (for example) another | 16:38 |
norayr | And maemo shows maemo notifications | 16:38 |
norayr | So system knows | 16:39 |
freemangordon | sure, but vibration is not part of desktop notifications specs, AFAIK | 16:39 |
norayr | But when does vibration happen? | 16:39 |
norayr | I enabled it in settings | 16:39 |
norayr | For a call? | 16:39 |
norayr | Can we add it to desktop notification spec? | 16:39 |
freemangordon | we? | 16:40 |
freemangordon | https://specifications.freedesktop.org/notification-spec/notification-spec-latest.html#hints | 16:40 |
norayr | How people are supposed to get notified? | 16:40 |
freemangordon | well, those specs are maintained by freedesktop org, iiuc, ask them maybe | 16:40 |
norayr | Understand | 16:40 |
freemangordon | native maemo applications use exensions | 16:40 |
norayr | Still lets discuss it or think | 16:41 |
freemangordon | sure | 16:41 |
norayr | Because we have libnotify | 16:41 |
norayr | And maemo feels it | 16:41 |
norayr | And i always miss notificatiions | 16:41 |
freemangordon | I am not saying we shall not discuss, what I am saying that vanilla desktop notifications specs does not support vibration | 16:41 |
norayr | Because even if i look at the droid every 10 minutes i miss | 16:42 |
norayr | And sometimes my internal clock doesnt work well | 16:42 |
norayr | And 10 is 20 or 30 | 16:42 |
freemangordon | and in order dino to make phone vibrate, somebody shall teach it to tell maemo that it wants vibration | 16:42 |
norayr | And imiss important stuff | 16:42 |
freemangordon | norayr: got it | 16:42 |
norayr | But we r a linux distro, and we use desktop programs here and desktop programs use libnotify already | 16:43 |
freemangordon | but, libnotify does not support vibration | 16:43 |
freemangordon | there is no standard way an application to tell libnotify that it wants device to vibrate | 16:43 |
freemangordon | see the link ^^^ | 16:44 |
norayr | But can we when showing msg about notification also vibrate ourselves? We cannot change every linux program. | 16:44 |
freemangordon | for every notification? | 16:44 |
freemangordon | maybe, but I am not convinced this is a good idea | 16:45 |
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 | 16:45 |
norayr | Thank u | 16:45 |
norayr | Please discuss it | 16:45 |
freemangordon | norayr: there is no use to convince me about you having a real usecase :) | 16:45 |
freemangordon | I understand that | 16:46 |
norayr | Maybe someone else would use some mail client or something else. | 16:46 |
norayr | (((: | 16:46 |
freemangordon | the point is that when we make system-wide changes/decisions, we shall consider all possible usecases | 16:46 |
norayr | Sure | 16:46 |
norayr | I understand | 16:46 |
freemangordon | BTW, do you know what category dino uses when calling libnotify? | 16:49 |
freemangordon | norayr: BTW, it seems that dino does not use libnotify | 16:50 |
freemangordon | at least upstream seems to use GNotify | 16:52 |
freemangordon | which, seems to not even support sound | 16:52 |
freemangordon | gh | 16:54 |
freemangordon | *ugh | 16:54 |
freemangordon | they seem to play their own sound | 16:54 |
freemangordon | hmm, not reall | 16:56 |
freemangordon | y | 16:56 |
freemangordon | norayr: I think I will be able to do something these days | 16:57 |
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 | 17:32 |
norayr | freemangordon: sorry, i am back online. thank you. | 19:24 |
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 | 22:20 |
arno11 | few lines modified and it's ok | 22:24 |
arno11 | but the code needs to be improved a bit | 22:28 |
Wizzup | arno11: ok, great, please share | 22:55 |
* Wizzup zzz first | 22:55 | |
arno11 | yes lol | 22:56 |
arno11 | gn | 22:56 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!