<dsc_>
arno11: i shall look into it with a n900 (because this only happens on n900?)
arno11 has joined #maemo-leste
<arno11>
dsc_: not sure it is n900 specific
<arno11>
Wizzup: hm, i don't see any dialog missing.
<arno11>
@no 3D, why it is a problem with qt5 ? i can't get it: it is known to be buggy on many devices.
<dsc_>
arno11: just so I have a good understanding, every Qt5 takes about 20 sec to startup
<dsc_>
and this is on a n900
<arno11>
yes
<dsc_>
did you try launching without the virtual keyboard support
<dsc_>
this needs an env. variable
<arno11>
yeah, already tried
<arno11>
the vkb seems not related to this issue
<dsc_>
ok
<dsc_>
arno11: so, wizzup uses daedalus on droid4 extensively, and does not report 20sec boot times for qt5 apps
<dsc_>
else we would have mentioned it
<dsc_>
else he*
<dsc_>
so perhaps it is n900 specific?
<dsc_>
(trying to understand the issue)
<arno11>
maybe n900 specific, or maybe it is simply not noticeable on d4
joerg has quit [Ping timeout: 276 seconds]
joerg has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
System_Error has joined #maemo-leste
_fab has joined #maemo-leste
Livio has joined #maemo-leste
_fab has quit [Quit: _fab]
akossh has joined #maemo-leste
arno11 has left #maemo-leste [#maemo-leste]
Madda has quit [Ping timeout: 272 seconds]
Madda has joined #maemo-leste
_fab has joined #maemo-leste
<sicelo>
freemangordon: yay, upower folk merged the UPower patch(es).
Livio has quit [Ping timeout: 264 seconds]
Livio has joined #maemo-leste
<sicelo>
odd - leste vm can 'see' my laptop's modem, but for some reason activating it just doesn't work, even via direct dbus calls
pabs3 has quit [Read error: Connection reset by peer]
pabs3 has joined #maemo-leste
<Wizzup>
dsc_: re: launch slowness, I am not sure if it is a regression
<Wizzup>
dsc_: and it's 20 seconds, it's cold boot 10-12, and warm boot 5-6 seconds
<Wizzup>
but there are ways to make the cold boot faster
<Wizzup>
and yeah that's on n900 specifically
<Wizzup>
sicelo: re: modem, is it a usb modem?
<sicelo>
internal modem connected via usb, yes.
<Wizzup>
what kind of modem is it?
<Wizzup>
and this is with qemu, right?
<sicelo>
Bus 001 Device 004: ID 0bdb:193e Ericsson Business Mobile Networks BV N5321 gw
<sicelo>
and yes, leste vm on qemu
<crab>
hi all - im trying to set up voip on my n900 using the SIMPLE(haze) voip account thing from the settings menu. Is this working as far as people know?
<Wizzup>
haze does not do voip, you need to use telepathy-rakia
<crab>
sweet, thanks ill give that a try.
<Wizzup>
sicelo: ok, any nothing in qemu about usb sped mismatches or whatever?
<sicelo>
oh, mmm. let me check. dmesg i guess?
<Wizzup>
or qemu stderr
pere has quit [Read error: Connection reset by peer]
pere has joined #maemo-leste
<sicelo>
doesn't seem to have any mismatches
gnarface has quit [Ping timeout: 276 seconds]
<sicelo>
it's not an ofono issue, because even with MM doesn't work - in fact MM doesn't even manage to register the modem at all
<sicelo>
but the modem works fine on the host, with either ofono or MM
<Wizzup>
and it's released properly on the host side?
<sicelo>
yes, actually while qemu is running, the modem is not visible to host
gnarface has joined #maemo-leste
pere has quit [Read error: Connection reset by peer]
pere has joined #maemo-leste
pere has quit [Read error: Connection reset by peer]
pere has joined #maemo-leste
<crab>
Wizzup: hmm. i installed that from apt and i now see the sip sofia option in accounts but im still not having much luck getting it to sign in. is that the correct approach?
<crab>
ooh we may have lift off...
mkf has joined #maemo-leste
<mkf>
hello.
<Wizzup>
crab: cool, what did you have to try?
<crab>
i think setting the transport to auto got it connected
<crab>
i can see it as an endpoint in asterisk
<crab>
but i cant get it to ring, and i cant seem to find a working dialer but progress is progress.
<Wizzup>
sphone should work if you use telepathhy
<Wizzup>
are you set to online?
<n900>
yeah i have the green dot
<n900>
sphone tries to start but seems to just crash out
<Wizzup>
crash out, how?
<n900>
so the screen goes black, i see "sphone" in the title bar
<n900>
and then that just disappears and im back to the wallpaper.
<Wizzup>
this is when you are being rang, or just when you try to start sphone?
<n900>
when i try and start sphone
<n900>
(sphone dialer to be specific)
<Wizzup>
that seems... bad :)
<Wizzup>
that's why ringing doesn't work for sure
<crab>
perhaps im missing something
<Wizzup>
maybe go offline, start sphone, go back online, see if things change?
<Wizzup>
crab=n900 yeah?>
<crab>
yeah
<Wizzup>
k
<crab>
i installed "telepathy-rakia" but it didnt seem to pull in any package called telepathy
<crab>
do i need to install that separately?
<Wizzup>
I am surprised that wasn't installed laready
<Wizzup>
you configured the account using the accounts ui, right?
<crab>
yeah
<crab>
im pretty confident its connected to the server ok
<crab>
because when i toggle it offline and do "pjsip show endpoints" in asterisk i can see the server says its gone
<crab>
and i toggle it back online, and it connects
<crab>
so that bit works
<Wizzup>
ok, it seems like the main issue is in sphone currently, is it running? 'ps xua | grep sphone' ?
<crab>
but there is clearly not something 100% right with the other bits of the stack
<crab>
yeah nothing is running.
<Wizzup>
ok, please start it from terminal: 'sphone -v'
<crab>
ill try and start it from the terminal and see if i get any interesting errors
<Wizzup>
also - is this chimaera or daedalus?
<crab>
chimaera
<Wizzup>
chimaera or chimaera-devel?
<crab>
just chimaera i think
<Wizzup>
ok, I think this is the problem
<crab>
ok cool
<Wizzup>
please upgrade to chimaera-devel - we never moved the sphone with vcm to stable in chimaera
<Wizzup>
(it's default in daedalus)
<Wizzup>
I think we should just move it over
<crab>
right apologies for these dumb questions, but this stuff confuses me a bit. i know i should probably re-flash the sd card, but im too lazy to do that.
<crab>
in my sources.list i have some devuan repos and the maemo one
<crab>
can i change the latter from chimaera to chimaera-devel and dist upgrade or will that be futile?
<crab>
and do i need to change the devuan repos too?
<Wizzup>
no, you copy he lines with maedevu ... chimaera
<crab>
i assume this is just a maemon thing
<Wizzup>
and make a new line
<Wizzup>
and then change chimaera to chimaera-devel
<Wizzup>
so that you have both
<crab>
heh
<crab>
i think i understand
<Wizzup>
and yes, then dist-upgrade
<crab>
thanks - thats in progress.
<crab>
heres another question that has me a bit confused,
<crab>
the usb0 interface has an ip address which appears to be hardcoded in the 192.168 range.
<Wizzup>
yes, it's a static assignment for when you connect to pc
Livio has quit [Ping timeout: 264 seconds]
<crab>
is there a way to change that address (other than poking it with ip) ?
<Wizzup>
there is, but I wouldn't unless your specific home subnet matches that one
<crab>
my home subnet *doesnt* match that one which is why i want to poke it!
<crab>
to be honest its not that important - the wifi on this works very well unlike my zaurus
<Wizzup>
I don't think you want it to match your home subnet
<crab>
but i have recently set up some of the machines in my flat so they are very cdc_ether friendly and it might be fun to give the n900 the same love.
<Wizzup>
so you have a switch or router that does ip over usb and you want to ues it in dhcp mode or somrething?
<crab>
aah, but i have some nice config cooked up so the usb port on the linux box is in my bridge.
<crab>
i generally dont use dhcp
<crab>
but with the bridge slaac configures the ipv6 side
<Wizzup>
ok, well, I think you can just grep -r for the in /etc and find it
<Wizzup>
for the ip in /etc*
<crab>
i tried that but i couldnt find it in there anywhere!
* crab
has another look
<Wizzup>
let me see
<Wizzup>
h, it's in /usr/lib now for some reason
<Wizzup>
see
<Wizzup>
/usr/lib/ke-recv/pcsuite-disable.sh
<Wizzup>
/usr/lib/ke-recv/pcsuite-enable.sh
* Wizzup
bbl
<crab>
sorry i found it
<crab>
i was messing late last night when i should have been in bed. goodness knows what i was doing.
<Wizzup>
it should be the pcsuite-enable script
<crab>
hmmmm actually i dont find it - i see lots of "192.168" but not "192.168.42.2"
<crab>
anyway ill have a look in there
<crab>
aah /usr
<sicelo>
should be in /etc/network
<crab>
i think Wizzup is correct.
<crab>
it is in /usr/lib/ke-recv
arno11 has joined #maemo-leste
<crab>
i dunno if i want to change it or not
<crab>
its a very complicated (imho) shell script but its also 99% comments.
<crab>
however i think that a debian style usb0 config file in /etc/network/interfaces.d would be a bit user friendlier in my entirely unsolicited (but humble) opinion.
<sicelo>
indeed, i see it
* sicelo
always thought it was in /etc/network :-D
<sicelo>
anyway, makes sense to me having it in ke-recv
<crab>
well i guess the intended use case is to work with that pcsuite software
<crab>
they never imagined that people with actual linux knowledge would be plugging the phone into linux boxes
<crab>
which is incredibly ironic as i still regard the n900 as the greatest "*nix nerd" phone ever made.
<sicelo>
you can just modify ke-recv to suit your needs ... we don't use PC Suite
<crab>
yeah i will prob. give that a try at some point.
mkfx has left #maemo-leste [Disconnected: Replaced by new connection]
mkfx has joined #maemo-leste
mkfx has left #maemo-leste [#maemo-leste]
mkfx has joined #maemo-leste
<sicelo>
Wizzup: please create and give me access to firmware-librem5-wlan in leste/*
xmn has quit [Remote host closed the connection]
<Wizzup>
sicelo: ok, do we want it in upstream-forks perhaps, or?
<sicelo>
i guess any, as long as it'll be available by default in images (once they become available).
<sicelo>
fwiw, i'm packaging it slightly differently from how mobian does it ... they include FW for the PPPro's camera sensor. i dropped that
<sicelo>
i guess leste-upstream-forks, seeing as droid4-linux is there too
<Wizzup>
yeah, ok
<Wizzup>
I'll make it now
<Wizzup>
done
<sicelo>
tyvm
<sicelo>
i've pushed. you can let me know if there's anything else that i'll need to do
<sicelo>
I guess when built, it can/should go to a "librem5" repo/component
System_Error has quit [Ping timeout: 264 seconds]
<Wizzup>
I think that is specified in the debian/control file
<Wizzup>
bbut imo we can just keep these kind of packages in main
<Wizzup>
we mostly used the component to ensure specific leste-config-pkg's were installed
Livio_ has quit [Remote host closed the connection]
Livio has joined #maemo-leste
<arno11>
dsc_: nice, qt keyboard works well with telegram-desktop :)
Livio has quit [Ping timeout: 264 seconds]
<Wizzup>
sicelo: sweet, sry, some things came up, shall I build it for daedalus-devel or daedalus-experimental?
_fab_ has quit [Quit: _fab_]
Twig has quit [Remote host closed the connection]
arno11 has quit [Ping timeout: 265 seconds]
arno11 has joined #maemo-leste
<sicelo>
i'm not sure what's best :-)
<sicelo>
i guess -experimental to be on the safe side
<Wizzup>
sicelo: building for -devel
<Wizzup>
:)
<Wizzup>
ah, need to chagne the repo url for it (I moved upower to uptsream forks)
<sicelo>
cool.
<sicelo>
updated MR for mce, https://git.maemo.org/leste/mce/pulls/64 - needed since upstream requested a change in the variable name holding the capacity_level (originally used `supply_level`)
<sicelo>
i've been using this trio of patches (upower, mce, status-area-battery) for quite a few weeks already, so i'm quite confident that they are fine and safe for -devel. that said, if anyone experiences any kind of regression, please do not hesitate to ping me
<sicelo>
debian's debian/control doesn't have the direct polkitd dep ... only has libpolkit-gobject-1-dev. maybe polkitd is already hard-depended by some other core package
<Wizzup>
works now
<sicelo>
still got a D4 where you had to displace upower binary?
<sicelo>
easy way to see if it's worth testing this upower on it is `cat /sys/class/power_supply/battery/capacity` ... if it's 0% or non-existent, then you can put the new features to the test
<Wizzup>
no, but I have a friend who has issues with this on his d4 :)
<Wizzup>
do we still need to set the config keys to disable ths hutdown
<Wizzup>
the shutdown
<sicelo>
yes,
<Wizzup>
but as I understand it, the voltage reading/estimation helps, right?
<sicelo>
1) from the voltage, we estimate a very rough percentage that we can use to display a battery icon. doesn't affect shutdown
<sicelo>
2) from capacity_level, we can inform mce that the battery is empty, and mce will request the shutdown (upower will not be requesting any shutdowns anymore with the posted config)
<sicelo>
for people/devices who don't have capacity_level, or prefer to use voltage, mce already understood how to shutdown based on a specific voltage
<Wizzup>
ok
<Wizzup>
building leste-config now
fmg_d4 has joined #maemo-leste
<sicelo>
ideally you also need to review mce ( https://git.maemo.org/leste/mce/pulls/64 ) because that's key to shutting down at the correct time (especially if you need/want to use capacity_level)
joerg has quit [Remote host closed the connection]
joerg has joined #maemo-leste
<Wizzup>
I will do it, but was waiting to see if uvos would pick it up, but he seems preoccupied, so maybe he doesn't mind.
<Wizzup>
left a comment (looks good to me)
Pali has quit [Quit: Pali]
arno11 has quit [Quit: leaving]
joerg has quit [Remote host closed the connection]
<sicelo>
so in sphone i guess someday we still need to add, for the vcm module, a way to choose an account (ring vs. rakia) for placing an outgoing call
<sicelo>
i see conversations has it
<Wizzup>
I think that is there now
<Wizzup>
in some crude form
<Wizzup>
go to the dialer screen, and then click on the 'backend' button
<Wizzup>
it should give you a list of available backends
<sicelo>
unless N900 screen is too short, i don't have it