akossh has quit [Remote host closed the connection]
ac_laptop has quit [Ping timeout: 260 seconds]
nahawand has quit [Ping timeout: 255 seconds]
nahawand has joined #maemo-leste
slep has joined #maemo-leste
joerg has quit [Ping timeout: 264 seconds]
joerg has joined #maemo-leste
antranigv has quit [Ping timeout: 264 seconds]
antranigv has joined #maemo-leste
nahawand has quit [Quit: Connection error?!]
starlight has joined #maemo-leste
akossh has joined #maemo-leste
slep has quit [Quit: Gateway shutdown]
slep has joined #maemo-leste
<sicelo>
Wizzup: maeotp doesn't build successfully for me on droid 4 and vm
<sicelo>
https://paste.debian.net/1301273/ silences the other warnings, but then the build fails with: "/usr/bin/ld: test_hmac-otp.o: in function `token_set_key': ./src/otp.c:332: undefined reference to `base32_decode'"
<sicelo>
which is weird since the header is included
<freemangordon>
this means library is missing
<freemangordon>
unless the function is inline
<freemangordon>
sicelo: also, latest ld is very picky about the order of the libs
<sicelo>
i will double check the order. i am just curious how Wizzup built it ... i started with d4, which failed, then thought he used vm/amd64, but i was getting same issues :-)
parazyd has quit [Ping timeout: 252 seconds]
parazyd has joined #maemo-leste
<sicelo>
it builds fine if the tests are removed, and the new functionality works as expected. thanks Wizzup! just need to get the thing to build fine with the tests in place
<Wizzup>
so something just needs to start ring and ring will do the rest?
<freemangordon>
even starting ring is not needed
<freemangordon>
you just need mc running
<Wizzup>
ok
<freemangordon>
which will happen as soon as there is some dbus call
<Wizzup>
yup
<Wizzup>
great
<freemangordon>
keep in mind after upgrade of tp-ring you have to restart mc (most-probably)
<Wizzup>
uvos: are you ok with my testing sphone in maemo/chimaera-experimental, merging to some testing branch and building?
<freemangordon>
I don;t know if it is smart enough to pick up the new plugin on-the-fly
<freemangordon>
Wizzup: also, I think it is better to add some env vars to etc/profile that set ring priority/mlock instead of having xsession
uvos has joined #maemo-leste
<uvos>
sure, but dont load any modules you add
<uvos>
by default
<Wizzup>
I mean in experimental?
<uvos>
yeah
<Wizzup>
ok
<uvos>
like you can add the tp module to expiramental
<uvos>
but dont load it by default yet
<Wizzup>
sure
<uvos>
also if you need to have vcm installed at build time, add it to makedepends only, so that having expiramental sphone installed dosent pull vcm and ring (thus breaking ofono)
<Wizzup>
I'll version 0.7.99.[number here] so that it's higer than the current stable
<Wizzup>
vcm won't auto start I think
<uvos>
what about ring?
<Wizzup>
that will break it when it gets autostarted, but it shouldn't get pulled in yet I think
<Wizzup>
I'll double check
<uvos>
sphone dosent really need all the depends of all the modules installed at all times anyhow, it will just refuse to load the module ofc
<Wizzup>
I'm mostly just looking to avoid building it on my d4 and bionic all the time :)
<Wizzup>
sicelo: ah yeah ok now I remember,I first had the base32 code in the gui, so I didn't add the cflags to the tests, but then I decided to move it into otp.c directly
<Wizzup>
I guess my configure just didn't build the tests
<Wizzup>
uvos: we will need to deal with the isdigit() checks in ui-dialer-gtk at some point btw
<Wizzup>
you might want to introduce a module property on what kind of calls/etc can be made (or that already exists perhaps) and based on that allow people to also type things
<Wizzup>
s/things/characters/
<uvos>
yeah the active backend needs to suply a check func tion
<Wizzup>
and some might want to prefix everything with 'sip:'
<Wizzup>
(like, well, sip)
<Wizzup>
I forgot how I dial land lines with sip, so maybe that doesn't use the prefix, but you get my point
<uvos>
nah we dont want to prefix anything
<Wizzup>
but we don't want people to type 'sip:'
<Wizzup>
I guess it could come from abook somehow
<uvos>
we can use the existing url resolving machinery of sphone to choose a backend based on the uri if it is a valid uri
<Wizzup>
there canbe multiple valid backends
<Wizzup>
I think there's also the contact chooser dialog, it might want to allow for selecting other fields than just the phone number as it does atm
<uvos>
i want to totaly remove that
<Wizzup>
what would you replace it with?
<uvos>
and just have the user use addressbook (the application)
<uvos>
we can use the exec module to open it when that butten is pressed
<Wizzup>
It should be about the same amount of code to open the abook dialog on sphone
<Wizzup>
which doesn't interfere with other things they might be doing with abook
<uvos>
yes but the abook dialogs are wose than osso-addressbook
<uvos>
and the module to do this exists allready
<uvos>
its how gnome-contacts is used with sphone
<Wizzup>
I think this will provide poor ux
<uvos>
i think die dailog has terrible ux compared to the application
<uvos>
and it adds a dependancy for very little gain
<uvos>
or negative gain imo
<Wizzup>
being able to choose a contact from some other application shouldn't bring you to the contacts application where might be doing other things already
<Wizzup>
I don't see how that would work
<Wizzup>
this only works if you assume people don't ever open the contacts for other purposes or just never use it, no?
<uvos>
not really, it works like android, the dialer application has no contacts and the contacts application is seperate
<uvos>
the only way to get to the dialer with a contact is to open the contacts applicaiton and pess on it there
<Wizzup>
but it doesn't work like maemo :)
<uvos>
the dialer is only really used if you want to type in a phone number manually
<uvos>
otherwise contacts is the point of entry
<Wizzup>
I still don't see how this works, if you're editing a contact, and want to call someone,how do select a person?
<uvos>
why would you keep the editing dialog open?
<Wizzup>
do you have to stop editing a contact?
<uvos>
yes you do on android
<Wizzup>
people make phone calls all the time as interrupts
<uvos>
this really is no problem
<Wizzup>
I think it is, because sphone can't know
<Wizzup>
it will just cause h-d to go to some app that has the edit open
<uvos>
ok so imo i would just remove the button then
<uvos>
like again android
<Wizzup>
and I also don't think that will let you pick the backend at all
<uvos>
yes it would
<Wizzup>
which osso abook does
<Wizzup>
I don't think osso addressbook the application does
<uvos>
you click on a contact field, this opens the dialer with the default backend for this field
<uvos>
then you can change it if you want
<uvos>
this is different than android
<uvos>
(and worsie imo)
<uvos>
in android every field has a backend associated
<uvos>
but we dont have this
<Wizzup>
there can be *multiple* backends for the same type is my point
<uvos>
sure
<uvos>
in android this is allso true
<uvos>
but then you just have 2 fields with the same content
<uvos>
but serviced by different backends
<uvos>
in our sheme its no problem either
<Wizzup>
that is the dialog that comes later in osso-abook dialog mode iiuc
<uvos>
since will sphone will select its perfered backend for the field
<uvos>
you can sill change it before the call
<Wizzup>
sphone should always ask
<Wizzup>
not just pick one
<uvos>
it must pick one really
<Wizzup>
not if there is a dialog like on maemo :)
<uvos>
i think this is mainly annoing
<uvos>
you have a bakcend for eatch type of uri that you use most
<Wizzup>
it's absolutely necessary to be explicit what you're calling someone with if it is unclear
<uvos>
i dont want it asking every time
<Wizzup>
like sphone can't just pick one of my xmpp accounts
<uvos>
and you can sill change the backend before the call
<Wizzup>
I guess we just disagree
<uvos>
it will pick your primary account
<Wizzup>
I'll get back to actuially getting the code in shape
<uvos>
so imo i would just pick another one if thats wrong
<uvos>
and you can choose what your primary backend is by changeing the load order (for now, we can provide some ui for this later)
<uvos>
this is exactly the same as file associations (since it uses the same machinery)
<Wizzup>
the load order would just be when they come online
<uvos>
theres a primary handler for every type
<Wizzup>
ok, but if you think about it makes no sense :)
<uvos>
and then the user can choose some other applicaiton if he wants
<Wizzup>
if I have several sip accounts registered, I don't want it to pick one to call a sip number
<Wizzup>
I want to pick the one to use
<uvos>
you yould not
<uvos>
you would pick one for sphone to suggest first
<uvos>
thats all
<uvos>
you can sill use the dropdown before pressing call
<uvos>
i dont see the problem
<Wizzup>
that would be wrong unless sphone will store that per contact for eternity and let me edit it per contact
<Wizzup>
actually in maemo it will initiate the call immediately after the dialog, you don't press dial explicitly afaik
<Wizzup>
(I will have to verify this)
<uvos>
its no different really
<uvos>
just more convieant if you have a backend you use way more than others
<uvos>
in fremantle it gives you a dialog to choose
<uvos>
sphone gives you a window to choose, with something preselected
<uvos>
its really no different than having one backend highlited in the dialog
<Wizzup>
and everything else in maemo will use the dialog
<Wizzup>
so it'll be awkward
<uvos>
well sphone dosent want to be tied to maemo like that
<uvos>
i use it outside of maemo alot
<Wizzup>
that's fine
<Wizzup>
I think we might just want to make some hildon-ui module or something so we don't need this strain/discussion every time :D
<uvos>
if you change how this works you will break it comeplealy anywhere abook is not used
<Wizzup>
not with a separate ui module I think?
<uvos>
sure but having 2 uis is pretty terrible too
<uvos>
and amounts to a hard fork almost
<Wizzup>
well, one wouldn't be enabled on maemo
<uvos>
sure but imo it needlessly splits effort
<Wizzup>
maybe, but I am not sure if we achieve what we want within the confines of what you specify
<Wizzup>
anyway it's my bday and it's sunny so I'll take a break and then get back to the tp backend
<Wizzup>
not sure if we can achieve what we want to achieve*
<freemangordon>
Wizzup: happy bday :)
<uvos>
happy bday
<uvos>
anyhow i think the main issue is that abook is somewhat defficant? it knows what type a field is but not what account its assoicated with? that cant be right presence would not work then...
<uvos>
so why cant abook just tell sphone what backend to select
<uvos>
instead of having a silly dialog to choose what sip account to use for a sip contact?
<uvos>
then you would only have to change sphones pre-selection when you want to call the contact with an account thats not the "default" for that contact
<uvos>
so per contact default
<uvos>
the global default would still be needed for the xdg-open case where you click on a phone nummber or whatever in a browser or so
<freemangordon>
uvos: I think you are missing the point on how abook works
<freemangordon>
you are choosing action there, nto a contact
<uvos>
well an action on a contact field
<freemangordon>
and each action is defined by 'from', 'to' accounts and what to do with them
<uvos>
and that field should have an assoicated account
<freemangordon>
it has
<uvos>
that abook can then tell sphone
<uvos>
so wheres the problem?
<freemangordon>
it does
<freemangordon>
as long as sphone is registered as with tp
<uvos>
if it gets it wong will will have to change it in sphone
<uvos>
but that should almost never happen
<uvos>
so i dont see Wizzups problem with this
<uvos>
freemangordon: right and it will
<freemangordon>
I didn't follow the conversation, sorry
<freemangordon>
your conversation with Wizzup that is
<freemangordon>
uvos: any idea why perf does not work on our omap kernel?
nela has quit [Quit: Ping timeout (120 seconds)]
<uvos>
no
<uvos>
it dosent work?
nela has joined #maemo-leste
<freemangordon>
cycles: PMU Hardware doesn't support sampling/overflow-interrupts. Try 'perf stat'
<uvos>
that might be true
peetah has quit [Quit: -]
<freemangordon>
or we just have the kernel config disabled
<freemangordon>
but I don't know the config option for that :)
<freemangordon>
anyway, won't play with it now
<freemangordon>
ttyl
DPA has joined #maemo-leste
brabo has quit [Ping timeout: 252 seconds]
brabo has joined #maemo-leste
<Wizzup>
uvos: I think I'll just work on the tp module first and then when the code is up to par we can look at these other things in practice
<Wizzup>
bbl
<freemangordon>
uvos: heh, seems PMU interrupt is not supported on 4430
<freemangordon>
fortunately it *is* on 3430 :)
LjL has quit [Read error: Connection reset by peer]
LjL has joined #maemo-leste
lolcat has joined #maemo-leste
lolcat is now known as lolcatw
<lolcatw>
Hello, I'm having really bad performance on the latest maemo builds on the nokia, is there a recommended build out there I should be using?
<lolcatw>
nokia n900
<Wizzup>
uvos: what tool shall I use to get the same tab/spacing that you have, keeping in mind my code is c++?
<Wizzup>
uvos: for sphone that is
<Wizzup>
lolcatw: the latest -devel image ought to be much faster
<Wizzup>
lolcatw: that will get built tomorrow, but you can add the -devel repo to get those changes now
<Wizzup>
actually I am not sure if the -devel image will get build tomorrow :)
<Wizzup>
uvos: in any case I addressed I think all the comments apart from the tabs/spaces in the pull request for sphone
<Wizzup>
uvos: please don't merge it yes, as I do want to investigate if we can just load the voicecallmanager plugin or copy the code rather than requiring voicecallmanager to run
<Wizzup>
uvos: but in this state it should be totally usable for testing
<freemangordon>
lolcatw: "really bad performance" compared to?
<Wizzup>
uvos: obviously I'll squash the changes later too, but this makes it easier to see changes
<Wizzup>
freemangordon: latest stable images are still 24 bit, old ddx, maybe even swap problem
<lolcatw>
bad performance compared to the stock image
<lolcatw>
its very very choppy, I can't even scroll down the settings
<freemangordon>
"stock image" is fremantle?
<freemangordon>
lolcatw: ^^^
<freemangordon>
like, the OS it comes preinstalled with?
<lolcatw>
yes, I believe it's known as maemo
<lolcatw>
that image works fine, but it's so outdated I can't install anything through apt-get
<freemangordon>
umm, ok. actually 'maemo' is the family, but I understand what you mean
<lolcatw>
I'm trying to run a script I made that uses nodeJS to run, it's a client for a chat I'm a member from
<freemangordon>
yes, leste is still not in par in terms of performance, though, as Wizzup said, the last week there is a big improvement
<lolcatw>
I used postmarketOS to connect but that doesn't have any GPU acceleration so it's really really slow as well
<freemangordon>
which is still not in the image
<lolcatw>
oh i see
<freemangordon>
so, as Wizzup, just enable -devel repo and upgarde
<freemangordon>
you will see definite improvement
<lolcatw>
on the "Leste" image installed on sdcard, correct?
<freemangordon>
yes
<lolcatw>
okay, many thanks, I will try that right now
<freemangordon>
however, keep in mind that fremantle runs frm onenead
<freemangordon>
*from
<lolcatw>
so that's in sources.list ?
<freemangordon>
sec
<lolcatw>
is that a bad thing
<freemangordon>
'sec' means 'wait a second'
<freemangordon>
I am searching for wiki link for you how to enable devel repo
<freemangordon>
and yes, it is something you should put in sources.list
<lolcatw>
nah, I meant you said "however, it uses onenead" as if it was a bad thing
<lolcatw>
yes thank you so much fren
<freemangordon>
no, it is not bad
<freemangordon>
it is like comparing SSD vs HDD in terms of perforamnce
<freemangordon>
so, fremantle runs on SSD, leste on HDD
<freemangordon>
so it can *never* be as fast as fremantle
<sicelo>
i'm also interested to know about the libcmtspeechdata PR, and if there's anything that needs adjusting in it
elastic_dog has joined #maemo-leste
<sicelo>
for maeotp, i think another nice thing to add would be a 'Copy' button, like what many Android OTP applications have. but I don't think I have time for that right away :-)
pere has quit [Ping timeout: 252 seconds]
<arno11>
lolcatw: btw what particular chat apps/service are you interested in ?
<arno11>
i'm asking because many popular chat apps are already working with cli through a local bitlbee server (with almost no cpu usage)
ac_laptop has joined #maemo-leste
fab_ has joined #maemo-leste
<lolcatw>
arno11: ill check out bitlbee
<lolcatw>
the only one i really care about is facebook messenger to talk to irl frens
<lolcatw>
they dont use anything else
<lolcatw>
that bridge thing looks like it would fit my needs actually
<lolcatw>
but yeah, video playback is broken on nokia n900
<Wizzup>
lolcatw: does facebook messenger have a libpurple/pidgin plugin?
<Wizzup>
lolcatw: if it still works with xmpp then it's easy
<lolcatw>
i've always had trouble making xmpp work at all
<lolcatw>
but i guess i could try and set it up for my instant messaging needs
<Wizzup>
in a week or two we'll have channels and multi-person chats worknig on leste as well for xmpp I hope
<Wizzup>
brb
<sicelo>
it stopped supporting xmpp a long time ago. there was a libpurple plugin last i checked, but i haven't used it in a long time, so not sure if it still works in 2023/4
<arno11>
it still works :)
<arno11>
it is just a bit tricky to setup
<arno11>
i mean it needs a hack to be able to connect to fb server
<arno11>
just a hexa value to change in a .so file
<sicelo>
mmm, but the plugin is FOSS, so can't the required change be done in the code? :-)