doc|home has quit [Read error: Connection reset by peer]
doc|home has joined #maemo-leste
xmn has quit [Ping timeout: 245 seconds]
Livio has joined #maemo-leste
jk__000 has joined #maemo-leste
jk_000 has quit [Ping timeout: 240 seconds]
Oksanaa has quit [Ping timeout: 256 seconds]
Livio has quit [Ping timeout: 245 seconds]
Livio has joined #maemo-leste
pere has quit [Ping timeout: 250 seconds]
_inky has quit [Ping timeout: 272 seconds]
Livio has quit [Ping timeout: 256 seconds]
Livio has joined #maemo-leste
Pali has joined #maemo-leste
Livio has quit [Ping timeout: 240 seconds]
pere has joined #maemo-leste
pere has quit [Ping timeout: 256 seconds]
pere has joined #maemo-leste
pere has quit [Ping timeout: 240 seconds]
pere has joined #maemo-leste
pere has quit [Read error: Connection reset by peer]
<sicelo>
Wizzup: i have what I think is finally a proper patch for supporting n900 accelerometer over iio. Shall I do a PR against -devel, or how would you want me to privide it?
<Wizzup>
sounds good @ iio
<Wizzup>
pr against devel is fine, but do it for droid4-linux
<buZz>
droid4-linux for n900 ?
<sicelo>
Since rotation still doesn't work iirc, this isn't urgent, I guess, but it would be nice when I send it upstream to be able to say it has been tested on Maemo Leste :-)
<sicelo>
d
<sicelo>
buZz: one omap kernel now. Nice :-)
<freemangordon>
buZz: d4 and n900 have common kernel
<buZz>
ah, sweet, should we rename it to omap-linux then?
<freemangordon>
it is, already :)
<buZz>
ha!
<freemangordon>
just the repo name is still droid4-linux
<Wizzup>
right
<Wizzup>
has anyone tried the maemo keyring package from -devel?
<sicelo>
Not me. My droid 4 is moody since last few days. Refuses to charge. Maybe I shall massage it right now
<sicelo>
Or I can try vm
<Wizzup>
maybe try the d4
<sicelo>
Busy bootlooping atm, even with my power bank, which it has always been happy to use
<sicelo>
Ah, at least the android charging works
<buZz>
sicelo: tried a usbcondom on it? :)
<sicelo>
The power bank is a "condom" thingy. I guess that's why it always manages
<Wizzup>
so a random wall charger doesn't work?
pere has joined #maemo-leste
<sicelo>
My Samsung one (2A) can never charge it when battery is too low. But the cheap power bank can. Difference is clearly the data pins :-)
pere has quit [Ping timeout: 256 seconds]
<Wizzup>
weird
<Wizzup>
I've had a lot of luck with random chargers
<Wizzup>
freemangordon: shall we do the rename soon?
<Wizzup>
omap-linux?
<buZz>
sicelo: yeah, usbcondom can help a lot for such
<sicelo>
I prefer shorting the Data pins, as that will work for N900 too
<buZz>
yeah you could add a switch to it ofcourse ;)
<buZz>
or a multistep switch with some resistors even?
<sicelo>
:-)
<sicelo>
In other words, droid4 is happy with shorted data pins just as much as with unconnected pins. i.e. condom == shorted pins from d4 POV
Livio has joined #maemo-leste
<sicelo>
So shorted pins kill two birds with one stone for someone with both devices
<freemangordon>
Wizzup: no, why do we?
<Wizzup>
freemangordon: I mean rename the git repo
<Wizzup>
we don't have to, it's just more clear
<Wizzup>
github also has some renaming support in place
<Wizzup>
as in things should continue to work mostly
<sicelo>
Wizzup: keyring upgrade completed on d4 without issue
<Wizzup>
neat
<sicelo>
Mmm, so with droid4-linux, I see the beowulf branches only have debian patches. Which branch should I open MR against?
<sicelo>
I am not sure I want to play with quilt/debian patch system atm, although
<Wizzup>
neat, did you submit these as patches as well?
<sicelo>
You mean upstream? Not yet. I only finished it today. I will send it though, hopefully after someone else has tested it
<Wizzup>
check
<Wizzup>
nice work
<freemangordon>
Wizzup: I am fine either ways (repo rename)
<freemangordon>
for sure it is better name to match package, but OTOH, I think we have better things to do
<freemangordon>
Wizzup: BTW, what is the status of conversations?
<Wizzup>
the telepathy part needs more work, the accountmanager stuff isn't working as it should yet
<sicelo>
Wizzup: thanks. At least we'll now be ready for when rotation lands for N900
<Wizzup>
but there is code in place to log from various telepathy accounts
<Wizzup>
there is no abook integration yet, and conversations kind of depends on other maemo tp stuff as well (i.e. what turns on the accounts, what turns them off)
<Wizzup>
and notifications aren't in any maemo style yet
<Wizzup>
basically, what works:
<freemangordon>
yeah
<Wizzup>
1. render conversations, render contact list
<Wizzup>
2. update conversations in qt signal
<Wizzup>
3. send basic messages to existing conversations
<Wizzup>
4. log messages incoming and outgoing
<Wizzup>
-but- the tp stuff needs more work
<freemangordon>
hmm, what is "render contact list"?
<Wizzup>
main screen of conversations
<Wizzup>
I guess it uses some abook maybe
<Wizzup>
it relies on rtcom lib for this
<Wizzup>
(I think)
Livio has joined #maemo-leste
<freemangordon>
is that the 'history' screen?
<Wizzup>
It is the just the main conversations screen
<Wizzup>
if you go to launcher screen and start conversations
<Wizzup>
the screen with 'new sms' and 'new im'
<freemangordon>
is it the same as on fremantle or something new?
<Wizzup>
it's similar to fremantle, but lacks the two buttons I just mentioned
<Wizzup>
a version without telepathy is in the devel repo, so you can install it and copy over your rt-el db
<freemangordon>
ok, then you should have a list of your recent conversations bellow those 2 buttons
<Wizzup>
yes
<freemangordon>
so 'history' :)
<Wizzup>
dsc was going to add filtering based on protocol to that (irc, sms, etc)
<Wizzup>
but then he fell ill for a while, so we'll pick it up when he gets better :)
<freemangordon>
ok
<freemangordon>
I am thinking of REing osso-abook contact home applet
<Wizzup>
the one for each contact?
<freemangordon>
that way we should be able to do basically everything with a particular without having abressbook application ready
<freemangordon>
yes, that one
<Wizzup>
ok
<Wizzup>
other things we might want in te future (to re) is rtcom-presence-ui and maybe rtcom-accounts-ui
<freemangordon>
though I will finish 'me' contact first
<Wizzup>
and maybe rtcom-notification-ui
<Wizzup>
right
<freemangordon>
IIRC those were very easy
<freemangordon>
also, I think we already have some of those FOSS
<Wizzup>
rtcom accounts ui is 36K, rtcom presence ui is 80K
<Wizzup>
I think you're thinking of a specific plugin for a specific protocol
<Wizzup>
but yes
<Wizzup>
one other thing I wanted to ask
<freemangordon>
yeah, it is poissible I am mixing the packages
<Wizzup>
yeah, but it's ok, we don't need them -now-
<Wizzup>
how far did you get with the xkb stuff?
<freemangordon>
got stuck
<Wizzup>
oh and fwiw librtcom-notification-ui.so is 212KB
<freemangordon>
omg
<freemangordon>
do you know what it does?
<Wizzup>
I'd have to check, I did look around before, but not sure
<Wizzup>
it seems to do some client approving at least for text channels
<Wizzup>
I suppose it might generation hildon notification events :)
<freemangordon>
212k?
<Wizzup>
Comment=FIXME Notification UI status area plugin
<Wizzup>
mhm
<freemangordon>
ah
<freemangordon>
I know what it is
<freemangordon>
the one that's used to control online presence of your accounts
<freemangordon>
but I wonder why it is so big
* freemangordon
ckecks
<Wizzup>
isn't that rtcom-presence-ui ?
<freemangordon>
*checks
<freemangordon>
yes
<freemangordon>
no
<freemangordon>
dunno :D
<Wizzup>
:)
<freemangordon>
lemme check
<Wizzup>
there were also some shared libs that several of these use, either librtcom-accounts-ui-client0 or librtcom-accounts-widgets0