<Wizzup>
uvos__: so for the route module in sphone, I think apart from ringing/in-call/no-call modes, does it also need the specify what to output on?
<uvos__>
theres 2 datapipes, one for the call routing state (depending on if the backend sets the needs_route flag)
<uvos__>
and one that specifies the output sphone wants to use
<uvos__>
you just register on one or both in your route module
<Wizzup>
ok
<uvos__>
in this case only the latter
<uvos__>
since the former you can just have the pa route module do
<uvos__>
if you are going to write something thats supposed to be loaded with the pa route module
<Wizzup>
oh I see, pulse doesn't do the audio router trigger atm
<uvos__>
right
<Wizzup>
so should I just try to implement that?
<uvos__>
would be good (for the pinephone) since it would work there
<Wizzup>
it also helps on the d4 if I'd write the hypothetic reg hack
<uvos__>
anyhow your hack module needs to set its provides to something other than route
<Wizzup>
hm
<uvos__>
Wizzup: dont add the hack to the pa route module
<Wizzup>
uvos__: I am not
<uvos__>
but having the pa route module set the pa output would be good
<uvos__>
(and would work on pp, probubly)
<uvos__>
anyhow
<uvos__>
so any number of moudles can register on any datapipe at the same time
<uvos__>
but sphone will only load one module that provides route
<Wizzup>
so I can add a 'post route' that just registers the same data pipe? (and hope it executes after pa?)
<Wizzup>
right
<uvos__>
(in the module struct)
<uvos__>
so you just have to name it something else
<uvos__>
like provides: route-mapphone-hack
<uvos__>
or so
<uvos__>
then sphone will happily load both
<Wizzup>
ok
<Wizzup>
uvos__: does sphone_audio_route_t lack a earpiece mode?
<Wizzup>
or is that 'handset' ?
<uvos__>
its handset
<uvos__>
the route is expected to also set the correct mic
<uvos__>
ofc
<uvos__>
so internal mic+earpiece is handset
<uvos__>
btw
<uvos__>
you should at least check the call mode
<uvos__>
and not do anything on _NO_ROUTE modes
<uvos__>
since those would be ip calls etc that work fine with no hacks
uvos__ has quit [Ping timeout: 252 seconds]
uvos__ has joined #maemo-leste
<Wizzup>
right @ ip calls
<Wizzup>
SPHONE_CALL_WATING should that be WAITING?
<Wizzup>
in any case I have a module that works atm
<Wizzup>
well, -should work-
<Wizzup>
the mic in anything but speakerphone is still a problem of course
<Wizzup>
uvos__: ok if I push to a work in progress branch @ sphone?
<uvos__>
sure go ahead
<Wizzup>
ok
Daanct12 has quit [Quit: Leaving]
Daanct12 has joined #maemo-leste
<Wizzup>
-Werror not being on has bitten me a few times now :p
ceene has quit [Remote host closed the connection]
<Wizzup>
btw: recent contacts takes ~8s or so to load for me
Daanct12 has quit [Remote host closed the connection]
<Wizzup>
uvos__: btw, I'm up for trying to boot some android thing to dump registers to figure out what's missing, can it be done from stock or do you need to build your own kernel? (I mean I'd rather not, but I'd like to earpiece to work.)
xmn has quit [Quit: ZZZzzz…]
<Wizzup>
ok the pa side will need a bit more work, I'll get it done though
<Wizzup>
fwiw the ui has no way to switch to headphones atm
<Wizzup>
I suppose the idea is that it would be automatic
pere has quit [Ping timeout: 256 seconds]
cockroach has joined #maemo-leste
<Wizzup>
freemangordon: so current conversations with tp works for one account decently, but testing what happens if accounts go offline/online is harder
<Wizzup>
freemangordon: I suppose presence-ui is useful for that
pere has joined #maemo-leste
<uvos__>
Wizzup: sphone looks up every phone number in recents in eds
<uvos__>
if the phonebook is even vaguely large a single lookup really slow for some reason
<uvos__>
it seams way slower than it should be, but sphone could also be less dumb and only lookup the number once per number it encounters instead of once per entry
<uvos__>
if its overly bothersome you can unload the contacts-evolution module
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
xmn has joined #maemo-leste
arno11 has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
uvos__: I would think rtcom el has support for this
<uvos__>
sure you could just use the name thats in el, but then it would not follow the name of the contact if its changed or added
<uvos__>
i think sphone uses the name in el as a fallback, or maybe not i dont quite remember if i just wanted to implement that or if i have allready
<Wizzup>
I just know the rtcom example has the full names and everything from osso-abook
uvos__ has quit [Ping timeout: 240 seconds]
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 260 seconds]
xmn has quit [Ping timeout: 260 seconds]
Pali has joined #maemo-leste
<norayr>
anyone tried if pinephone keyboard works under leste?
<norayr>
other, important question: do you bootstrap devuan for each supported architecture? how? can i bootstcap it for armv5 (or what was on nokia n810)