humpelstilzchen[ has quit [Ping timeout: 264 seconds]
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
mardy has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
mighty17[m] has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
mglbg[m] has joined #maemo-leste
tvall has joined #maemo-leste
jeder[m] has joined #maemo-leste
humpelstilzchen[ has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
Livio has quit [Ping timeout: 255 seconds]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
xmn has quit [Ping timeout: 244 seconds]
buZz has quit [Ping timeout: 244 seconds]
buZz has joined #maemo-leste
buZz is now known as Guest5428
pere has quit [Ping timeout: 252 seconds]
<freemangordon>
tmlind: I looked in the code and WDS is already created by qmimodem/gprs.c
stintel has joined #maemo-leste
<freemangordon>
it turned out there is a nasty bug the qmimodem code
<freemangordon>
qmi_service_create_shared() is not written very well... to say at least
<freemangordon>
it checks if a service of type 'type' is already created and if not, it creates one. *but* service creation is async, so while creation is going on, if another qmi_service_create_shared() call happens, we stil don;t have created service and another create_service() call is made. etc.
<freemangordon>
Wizzup: ^^^ is the reason for missing contexts end client ids exhaustion
<freemangordon>
if a rainy day happens while I am on holiday I will fix it, if not - when I am back.
<Wizzup>
good sleuthing
[TheBug] has quit [Changing host]
[TheBug] has joined #maemo-leste
Danct12 has quit [Quit: Leaving]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
BlagovestPetrov[ has quit [Quit: You have been kicked for being idle]
pere has joined #maemo-leste
<tmlind>
freemangordon: unless we kick the usb qmi modem on n_gsm wds notifications, the usb qmi modem won't notice any changes
Pali has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
akossh has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
Livio has joined #maemo-leste
DPA- has quit [Quit: ZNC 1.8.2+deb2+b1 - https://znc.in]
DPA has joined #maemo-leste
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
yanu has quit [Remote host closed the connection]
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
Livio has quit [Quit: leaving]
dev has left #maemo-leste [Disconnected: Replaced by new connection]
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
<dsc__>
I updated conversations with support for sending multi-line messages and (optionally) forcing send when Enter/RETURN is pressed.
<dsc__>
and the text on the button 'Enter' has been changed to 'Send' as per the rest of the world
<sunshavi>
dsc__: quite nice. What I missed on old fremantle is an api for sending sms's from the cli. There was a python script. But that python script is disconnected from the database
<dsc_>
sunshavi: yes I'd also want this, for now I'm focussing on fundamentals but eventually we can support such features
<sunshavi>
nice. Now I am using an xdotool script that send the text to the conversation window and press the send button (with xdotool) also on freemantle
yanu has joined #maemo-leste
<dsc_>
lol :D
<dsc_>
yeah, there will be an API eventually
<dsc_>
'our conversations' is made with Qt, so its easy to spawn up a HTTP server (for e.g. a JSON API) in the same process, or we provide CLI flags for it, or ... <insert solution>
<dsc_>
whatever the implementation, it will be trivial
<dsc_>
actually, a websocket server would be fancy (and more suited than push/pull)
<dsc_>
I mean, more suited than polling
uvos has joined #maemo-leste
<dsc_>
so with Python you could connect to ws://127.0.0.1:8395 (conversations) and issue commands like 'sendSMS' or 'listContacts' etc.
<dsc_>
but for now not relevant as I'm still implementing basic features
<Wizzup>
telepathy could also just be the api?
<dsc_>
Wizzup: the issue is rtcom registration right
<Wizzup>
no, conversations will get all tp messages and handle them
<Wizzup>
and log them
<dsc_>
hmm
<dsc_>
direct communication with TP would be fine but I think we should create a small wrapper python script for it, so people dont get exposed to dbus internals and lose all hope in humanity
<dsc_>
just a simple api that allow people to do `send_message(protocol_type, recipient, message_body)`
<dsc_>
it might even already exist
<Wizzup>
tp scripts for this exist fwiw
<Wizzup>
but yeah
<sunshavi>
Rigth. That would let us send sms's from ssh when phone ir charging some meters away from us
<Wizzup>
there are scripts to do this with tp
<Wizzup>
with my new incoming tp code we'll just find it
<Wizzup>
we can test it later
vagag has joined #maemo-leste
vagag has left #maemo-leste [#maemo-leste]
<Wizzup>
dsc_: yes @ wrapper script btw
<Wizzup>
let's look at it once we have a mvp
Daanct12 has quit [Quit: Quitting]
Danct12 has joined #maemo-leste
<dsc_>
yupyup
norayr has left #maemo-leste [Error from remote client]
xmn has joined #maemo-leste
norayr has joined #maemo-leste
Livio has joined #maemo-leste
Livio has quit [Changing host]
Livio has joined #maemo-leste
Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
<sicelo>
Pali: nice re:u-boot + n900. i saw the recent commits
<Pali>
Recently I sent patches which extend CI tests for UBI booting.
<Pali>
But UBIFS on top of UBI is still broken on n900 and qemu, no idea why.
<sicelo>
i have a question regarding bq24150 - what exactly is `charge_current` for in sysfs? it's writable, but i don't seem to notice any specific differences
<Pali>
Interesting is that UBIFS is working fine on other bigendian powerpc board (with Freescale P2020 CPU).
<Pali>
So soemthing has to be terible broken in u-boot.
<sicelo>
re: UBIFS, yes i read the comments. btw, recent kernel spams dmesg with nonstop `MTD device '%s' is NAND, please consider using UBI block devices instead`. but looks like this can be resolved by disabling some MTD stuff in config
<sunshavi>
Pali: I also see the messages on the u-boot mailing list. And Tony answer