<rafael2k>
having already ip set really helped - tks
<rafael2k>
; )
<rafael2k>
I compiled the kgx terminal in a debian sid chroot
<rafael2k>
nice terminal, runs fine in maemo too
<rafael2k>
it would compile on bullseye too (not on buster, unfortunatelly)
Pali has quit [Ping timeout: 245 seconds]
<rafael2k>
btw, I see many people forcing GLES in the pinephone (for gstreamer playback, for example)
<rafael2k>
There are certainly some showstopper bugs in OpenGL (not ES) implementation, this is why enabling X accel creates trouble
<uvos>
there are shome showstopper bugs in glamors gles support too
<uvos>
so idk if that helps us any
<uvos>
stano_: the battery low notification is based on a charge percent, so it fails on d4 if its not calibrated
<Wizzup>
freemangordon: adding the networks and then using 'scan' from the control interface also works
<rafael2k>
uvos: right
<stano_>
ah ty uvos :)
<Wizzup>
rafael2k: so -devel broke wifi for you?
<stano_>
i add a voltage based beep again
<rafael2k>
Wizzup: yeap
<Wizzup>
the nightmare continous
<Wizzup>
at least in -devel it's OK to break wifi
<uvos>
hehe
<rafael2k>
:P
<rafael2k>
I can bring it up "by hand"
<rafael2k>
but the UI shows empty network list now
<freemangordon>
what device is that?
<uvos>
pp
<freemangordon>
ok
<freemangordon>
well, not "ok" , but still :)
<Wizzup>
let me check my d4
<Wizzup>
rafael2k: does the kgx terminal have virtual keyboart support like osso-xterm does?
xmn has quit [Quit: ZZZzzz…]
<Wizzup>
ok, let's see
<Wizzup>
ok, I made a mistake :)
<Wizzup>
yeah, this is terrible, so because wpa_supplicant randomly returns failure on the d4 and pp even though it works (for scanning), we cannot rely on its exit state being proper
<Wizzup>
I added a fallback, in case the control interface scan does not work, then scan using dbus (for the n900)
<Wizzup>
but since we cannot rely on its result, I made it not report failure
<uvos>
if it happens on pp too then we need to report this
<uvos>
as thats a tottaly unrelated driver....
<Wizzup>
So many fun things to report to wpa_supplicant ;)
<uvos>
yeah i thought the wierdness was just wlcore bing buggy
<Wizzup>
I don't think so
<uvos>
and wlcore is buggy but if it happens on pp too
<Wizzup>
I don't know how to fix this anymore without breaking either hidden aps, or one of the devices
<Wizzup>
freemangordon: nope, no working hidden ap with wext
<uvos>
hehe
<Wizzup>
freemangordon: well, connecting works
<Wizzup>
if set up properly
<Wizzup>
but the easy-wlan way didn't work for me
<Wizzup>
maybe it's because I had other hidden wlans in gconf
<Wizzup>
parazyd: any idea how we can modify the /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service to be n900 specific?
<Wizzup>
it's already a divert
<parazyd>
What package does it come from?
<Wizzup>
freemangordon: I see this: Jul 16 13:27:35 localhost iap_conndlg 2.88+0m5[2718]: Unable to receive reply from wpa_supplicant!
<Wizzup>
parazyd: I think libicd-network-wpasupplicant
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 268 seconds]
<parazyd>
Wizzup: Looks like you'd need some device identifier in the postinst
<Wizzup>
we don't have that I think
<Wizzup>
parazyd: how about a separate package only for this divert, and one can be for all devices, and one if for n900 component and replaces the one for all devices?
<parazyd>
one sec
<parazyd>
Yeah ok, that can work
<parazyd>
Build it from the same git repo
<parazyd>
Then in hildon-connectivity-wlan you can have a dep
<Wizzup>
well, it would have the same source package
<Wizzup>
I am not sure if it is possible to disable nl80211 in kernel but keep wext
<Wizzup>
but if it is, that might be easier than splitting up the divert stuff
<parazyd>
The divert isn't really difficult
<Wizzup>
would you be up for doing it for me?
<parazyd>
Sure, just give me the n900 contents
<parazyd>
Wizzup: ^
<Wizzup>
just put wext before nl80211
<Wizzup>
in the wpa_supplicant line
<Wizzup>
that's all really :)
<parazyd>
ok
<Wizzup>
freemangordon: I asked in #linux-wireless and there's someone asking about host mode on the n900, since he apparently did the kernel work way back for it :p
amk has quit [Ping timeout: 240 seconds]
DPA- has joined #maemo-leste
ikmaak2 has joined #maemo-leste
tg-x` has joined #maemo-leste
freemangordon1 has joined #maemo-leste
doc|home has joined #maemo-leste
rafael2k has joined #maemo-leste
obarb has joined #maemo-leste
R0b0t1 has joined #maemo-leste
mardy has quit [*.net *.split]
ikmaak has quit [*.net *.split]
sunshavi_ has quit [*.net *.split]
freemangordon has quit [*.net *.split]
R0b0t1`` has quit [*.net *.split]
tg-x has quit [*.net *.split]
brabo has quit [*.net *.split]
DPA has quit [*.net *.split]
doc has quit [*.net *.split]
rafael2k has quit [Ping timeout: 268 seconds]
amk has joined #maemo-leste
mardy has joined #maemo-leste
xmn has joined #maemo-leste
obarb is now known as brabo
diejuse has joined #maemo-leste
rafael2k has joined #maemo-leste
diejuse has quit [Ping timeout: 246 seconds]
sunshavi has joined #maemo-leste
<stano_>
is there something i can tell cpcap or whatever calibrates battery that it has just booted from an empty battery and can start counting the total charging power?
<stano_>
coulombs, whatever
inky_ has joined #maemo-leste
rafael2k has quit [Ping timeout: 255 seconds]
ikmaak2 is now known as ikmaak
mardy has quit [Quit: WeeChat 2.8]
xmn has quit [Ping timeout: 255 seconds]
n900000 has quit [Ping timeout: 268 seconds]
Pali has joined #maemo-leste
joerg has quit [Excess Flood]
joerg has joined #maemo-leste
uvos__ has joined #maemo-leste
uvos__ is now known as uvos
<uvos>
stano_: no
inky_ has quit [Read error: Connection reset by peer]
inky_ has joined #maemo-leste
Treebeard has joined #maemo-leste
Treebeard has quit [Changing host]
Treebeard has joined #maemo-leste
BenLand100 has quit [Ping timeout: 255 seconds]
Treebeard is now known as BenLand100
uvos__ has joined #maemo-leste
uvos has quit [Ping timeout: 268 seconds]
rafael2k has joined #maemo-leste
<Wizzup>
#linux-wireless is helpful so far with n900 wifi
DPA- has quit [Quit: ZNC 1.8.2+deb2~bpo10+1 - https://znc.in]
DPA has joined #maemo-leste
<sicelo>
Nice.
<sicelo>
What are some interesting points?
<sicelo>
I would like to see n900 wifi working properly in nl80211, even with iwd if possible
<sicelo>
ah, the person who talked about n900 host mode must be Paul? Yes, he, Doc, and a few others were responsible for making it happen
<sicelo>
Wizzup: if it's not too much to ask, please share the log of that wireless chat
rafael2k has quit [Ping timeout: 255 seconds]
inky_ has quit [Ping timeout: 268 seconds]
inky_ has joined #maemo-leste
branon has quit [Ping timeout: 252 seconds]
danielinux has quit [Ping timeout: 255 seconds]
joerg has quit [Read error: Connection reset by peer]