<stano>
wow /sys/class/power_supply/battery/voltage_now is giving me 3229000 and no beeps or shutdown
<stano>
this is with the EB41 on droid4. maybe firmware is still confused from experimental battery.
xmn has quit [Quit: ZZZzzz…]
<stano>
darnit i missed the shutdown, now i have to recharge to full, then discharge to full, then recharge to full again to calibrate battery monitor
<Wizzup>
morning
<stano>
morning Wizzup
<Wizzup>
I will look at the n900 wifi stuff today, I just need to set up my power supply and such
Guest166 has joined #maemo-leste
pere has quit [Remote host closed the connection]
Guest166 has quit [Quit: Client closed]
<stano>
what hardware are most leste-users running right now and what are you hoping them to be running it on in near future Wizzup ?
<Wizzup>
We don't really do analytics
<Wizzup>
I'd say the n900 and droid4 are common, pinephone also somewhat
<Wizzup>
I think those are also a good first bet in the near future.
mardy has quit [Ping timeout: 268 seconds]
mardy has joined #maemo-leste
xmn has joined #maemo-leste
inky__ has joined #maemo-leste
inky_ has quit [Ping timeout: 246 seconds]
inky has quit [Ping timeout: 268 seconds]
inky has joined #maemo-leste
mardy has quit [Ping timeout: 255 seconds]
inky__ has quit [Read error: Connection reset by peer]
inky__ has joined #maemo-leste
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 245 seconds]
mardy has joined #maemo-leste
<stano>
looks like linux might be possible on Tegra X1 tablets
inky__ has quit [Read error: Connection reset by peer]
<stano>
anyone using leste on a tablet yet?
inky__ has joined #maemo-leste
<Wizzup>
I had/have it working on the pinetab
linmob has quit [Quit: No Ping reply in 180 seconds.]
linmob has joined #maemo-leste
<stano>
well the google pixel c would be another potential candidate, as it uses the 'X1' cpu which has linux support (same cpu as jetson nano) but i don't see anyone with a working display driver for that tablet screen
<stano>
they can be had around 110 euro
<stano>
deliver around 500 nits brightness with a very powerful gpu, which also has linux drivers
<bencoh>
regarding pulseaudio / calls / automatic switching ... what kind of automagic does pulseaudio do anyway?
<Wizzup>
I think pulseaudio can act on plug events for headphone and such
<Wizzup>
it can also cork streams if certain types activate
<Wizzup>
e.g. just having mumble running can break your browser audio
<tmlind>
mighty17[m]: in the pwm timer case, the timer is just feeding the programmed clock rate to the connected device, maybe that's considered sufficient for a backlight
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 255 seconds]
<mighty17[m]>
where do u get programmed clock rate
<uvos>
check the rate on android?
<uvos>
either by reading in the vendor kernel or by dumping the corrisponding registers
<Wizzup>
the internet said it might be related to WNM being enabled in debian, but I am not sure if it was disabled previously or if it is only enabled now
<Wizzup>
also I wonder if we can undo changing the mac addr of the n900
<Pali>
in 2.6.28 kernel both wl1251 and wl1271 are handled by wl12xx kernel driver... later in kernel ňsupport for wl1251 was forked/moved into wl1251 driver and wl1271 and new chips stays in wl12xx driver
<Wizzup>
parazyd: ok, where did we get the newer version from?
<Wizzup>
ioctl[SIOCSIWSCAN]: Inappropriate ioctl for device
<sicelo>
*is
<Wizzup>
<3>CTRL-EVENT-SCAN-FAILED ret=-1
<Wizzup>
sicelo: are you sure we used wext?
<sicelo>
yes we must use wext
<sicelo>
what starts wpa_supplicant for us (Leste)?
<Wizzup>
sicelo: I don't see wext working
<Wizzup>
sicelo: via dbus I think
<sicelo>
i'll test my old debian sid install in a moment
<sicelo>
and if luck permits, i can try out a Leste image too
inky_ has quit [Ping timeout: 246 seconds]
inky has joined #maemo-leste
<Wizzup>
usbnet should work
<sicelo>
the images in question are the ones in phoenix.* ?
<sicelo>
ah, i see they're the same
<Wizzup>
sicelo: yes, the images are also broken
<Wizzup>
and any update to older images will also break
<sicelo>
sure. i'm downloading newest
<Wizzup>
I checkedps xua before I upgraded, and wext was not first, btw
<Wizzup>
so I am pretty sure we were *not* using wext before
<Wizzup>
sicelo: let me know, I'm going to do something else for a bit
<Wizzup>
but I think we'll have to either bisect wpa_supplicant (and build our own with a fix), or rebuild kernel with the wl1251 code changed to debug what it thinks is 'invalid'
<uvos>
did you strace the ioctl that returns EINVAL?
<n900000>
fastboot: error: cannot get boot partition size
<uvos>
might need flash:raw
<uvos>
altho i dont think d4 needs that
<uvos>
are you sure its a d4? :P
<n900000>
lol it absolutely is
<uvos>
hm ok wierd
<uvos>
anyhow flash:raw
<n900000>
flash:raw works
<uvos>
hmm something is wrong here
<Wizzup>
uvos: sicelo: parazyd: yeah so via dbus scanning in wpa_supplicant works
<uvos>
its fastboot flash devtree device_tree.bin
<uvos>
btw
<Wizzup>
also on newer wpa_supplicant
<Wizzup>
and wpa_cli's 'scan' not working is true for both versions
<Wizzup>
the only reason I upgraded to newer wpa is because the dbus interface does funky stuff with hidden APs
<uvos>
n900000: could you ppaste your mbm version
<sicelo>
Wizzup: ah, great then
<n900000>
everything is working up until fastboot erase data
<n900000>
Erasing 'data' FAILED (remote: 'no such partition')
<n900000>
fastboot: error: Command failed
<n900000>
sure no prob, how do I get it?
<Wizzup>
sicelo: problem is not solved
<Wizzup>
but some more info was gathered
<uvos>
sry its userdata
<uvos>
n900000: second line in fastboot mode
<n900000>
ah ok
<uvos>
eg 0a.77
<uvos>
also fastboot oem fb_mode_clear
<n900000>
got it, I just rebooted and it's giving me the red motorola logo
<uvos>
great
<uvos>
so mbm is happy
<n900000>
and it booted into android
<uvos>
ok
<uvos>
great
<uvos>
now flash utags again
<uvos>
(i assume you flashed kexecboot to bspw allready
<uvos>
)
<n900000>
kexecboot is already flashed unless the above overwrote it, yup
<uvos>
no
<uvos>
ok reboot into fastboot again
<uvos>
and flash utags again
<n900000>
should I let android boot up fully before going back into fastboot? It's at that red spinning logo
<uvos>
should not be stictly nesscary but you might break android if you just shut it down during inital boot
<n900000>
nvm the android setup booted up fine
<uvos>
ok
<n900000>
ok mbm is
<n900000>
0A.77
<uvos>
ok thats fine
<uvos>
now flash utags
<n900000>
done
<n900000>
reboot?
<uvos>
yes
<n900000>
eyyyyy
<n900000>
it worked
<uvos>
great
<n900000>
ok let me put in my sd card
<n900000>
this pin thing is very annoying btw
<uvos>
yes
<n900000>
perfect, booting in leste now
<n900000>
any idea what went wrong? I more or less copypasted the wiki instructions
<n900000>
also thanks a ton, I love the leste community
<uvos>
proububly just a single bit that got flipped in your download or inital flash
<uvos>
so some partition failed signature varfication
<n900000>
gotcha just bad luck then
mintphin has quit [Quit: This computer has gone to sleep]
<n900000>
I have 2 more droid 4's we'll see how those go when I flash them later
<n900000>
Oh wow the capacitive buttons work
<uvos>
idk why everyone is so supprized by this :P
<stano>
what's the actual mapping of those buttons?
<uvos>
?
<uvos>
the keycodes?
<n900000>
pretty much exactly what you'd think
<stano>
to keyboard, or some hildon function?
<n900000>
home is multitasking back is back etc
<stano>
if the back is 'Esc' it solves one of the big SDL problems
<n900000>
also going from PMOS to leste surprises you with how much polish leste has. The hardware acceleration definitely helps too
<uvos>
no back is f8
<stano>
k
<uvos>
i just wrote a driver that makes those keys a keyboard
<uvos>
with f6,7,8 and xf86search
<uvos>
they are xgrabkey'd by hildon
<Wizzup>
ok, I have something that works on the n900, but now to see if it still works with hidden APs
<freemangordon>
uvos: f7/f8 are reserved
<freemangordon>
for volume keys
<freemangordon>
so please, do not reassign that to anything else
<uvos>
nope
<uvos>
we are going xf86volup down
<stano>
the back closes sdl apps but f8 doesn't close the same app on desktop. <confused>
<uvos>
im sorry
<uvos>
anyhow yes i want ot change the d4 keys anyhow
<freemangordon>
uvos: where do you do that?
<uvos>
i think they should be home menu etc
<uvos>
freemangordon: change the keys?
<uvos>
in dts
<stano>
i am so happy it closes the apps
<stano>
thanks uvos
<freemangordon>
using f7/f8 for other functions but volume
<uvos>
having the android keys be f* was silly in retrospect
<stano>
all kinds of things use f7/f8
<sicelo>
freemangordon: i'd let it go :)
<freemangordon>
volume/zoom
<n900000>
Wizzup I was having wifi problems with the latest leste image last night and now I'm having the same thing on the droid 4
<freemangordon>
stano: no, OS uses those all over the p[lace
<stano>
xf86volup / down seems right to me
<n900000>
n900 was just giving me a black pane when trying to scan networks
<freemangordon>
sicelo: we can;t because it is not volume applet only
<uvos>
freemangordon: yeah your never going to have the volume keys be f7/f8 on all devices ever
<uvos>
freemangordon: anyhow lets not get into this
<uvos>
yes i intend to reassing the android keys
<freemangordon>
uvos: lets not go into this now, but we'll have to soon or later
<stano>
i don't see the argument. volup/down buttons shouldn't be mapped to f7/f8
<uvos>
stano: the problem is not should
<freemangordon>
stano: did you use maemo before?
<Wizzup>
n900000: the n900 wifi problem is very specific
<uvos>
the problem is that its hardcoded for lots of platforms to be xf86volup and xf86voldown
<uvos>
like x86 etc
<stano>
seems good to me to have them xf86volup/voldown
<uvos>
so unless we want to pach lots of input dirvers
<uvos>
its just not going to happen
<Wizzup>
n900000: what are you seeing with the d4?
<freemangordon>
ok, lets have a separate discussion on that in 2 weeks (I am MIA starting Sunday)
<freemangordon>
but the so-called "volume keys" on android have much more functions on maemo
<uvos>
they have several funcitons on android too
<uvos>
and this isent about android
<Wizzup>
we had this discussion before I think
<n900000>
Wizzup I don't know if its a problem exactly, but it took a few mins after setting up the connection to actually connect.
<freemangordon>
uvos: yes, we discussed a bit
<uvos>
Wizzup: yeah
<n900000>
and thanks for working on the N900 issue, I reverted back to the 6/27 image for the time being
<freemangordon>
and I still miss the answer to the question - what will happen if you press volume keys on the BT headset?
<Wizzup>
freemangordon: can you test hidden ap stuff tonight or tomorrow for me?
<sicelo>
Wizzup: what did you find (n900 wifi)
<freemangordon>
actually parazyd tested on android and the rezult was - nothing happened
<Wizzup>
I forgot why I switched to scanning using wpa control interface rather than dbus
<freemangordon>
Wizzup: sorry, no, too late here already
<uvos>
freemangordon: sure thats a stiky situation, we could have the volume applet only react to the dbus singals
<parazyd>
Yeah
<uvos>
and then since we want the dbus signals to be sent by mce
<uvos>
we can have mce filter out bt devices
<parazyd>
I can do further tests if needed
<freemangordon>
uvos: but really, lets not discuss now
<Wizzup>
parazyd: hidden ap ones?
<uvos>
freemangordon: sure
<freemangordon>
volume ones :)
<parazyd>
But on my.bt headaset nothing happened
<parazyd>
Wizzup: bt headphones
<Wizzup>
ok
<Wizzup>
well I'm close to ready to just stop working on hidden ap and at least restore normal func
<freemangordon>
why is that?
<Wizzup>
the amount to which this broke everything is just insane
<freemangordon>
what is "this"?
<Wizzup>
working on the hidden ap stuff
<freemangordon>
wpa_supplicant?
<Wizzup>
that's one of it yeah
<n900000>
sorry dumb question, on the n900 is there a key combo for Tab? Or am I forced to use the onscreen one in osso-xterm?
<Wizzup>
sicelo: plain and simplem the wpa control interface 'scan' never works on the n900
<uvos>
we should fix that really
<Wizzup>
sicelo: it does something different from the dbus scan interface
<uvos>
Wizzup: did you mail the list?
<freemangordon>
Wizzup: did you try wext driver?
<Wizzup>
freemangordon: yes, that does not work at all
<Wizzup>
uvos: wpa_supplicant? no
<freemangordon>
hmm, it used to
<uvos>
yeah we should ask for advice i think
<Wizzup>
we don't even have wext enabled
<Wizzup>
(in kernel)
<freemangordon>
anyway, I am too sleepy now to produce anything sane
<freemangordon>
so... good night guys
<uvos>
gn8
<n900000>
also sxiv works great on leste, even full screening. keyboard mapping and be remapped to work on the hardware keyboards too. I like it better than mihphoto
<n900000>
What do you guys use for web browsing?
<uvos>
firefox-esr
<uvos>
works really well on d4
mintphin has joined #maemo-leste
<uvos>
(not on n900 ofc)
<Wizzup>
parazyd: shall we enable WEXT in kernel?
<n900000>
how about the poor n900 with it's 256mb of ram lol
<n900000>
the freemantle browser is actually really fast on simple webpages
<uvos>
your kinda sol on n900 relly surf at least starts but its too mutch for it
<parazyd>
Wi
<uvos>
maybe you would have luck with link2 or dillo or something
<parazyd>
Wizzup: I lf it's needed, sure
<parazyd>
wft keyboard, sorry
<sicelo>
Wizzup: i guess if you have nl80211 working with dbus, and that's what Leste uses, then no need for WEXT
<n900000>
yeah I expected as much, all I really need is newsboat and it works fine though
<Wizzup>
sicelo: until everything works (e.g. hidden aps), we can't say it works
<Wizzup>
wpa_supplicant acts differently over dbus than it does over control interface
<n900000>
sorry more dumb questions, is video playing hardware accelerated on any of these?
<uvos>
no
<sicelo>
okay. wext is definitely far more reliable - actually 5.14 has wext enabled for the n900
<uvos>
hardware decoding works nowhere (pp maybe?)
<uvos>
hardware presentation sorta works
<uvos>
on d4 i have gotten it to work only in firefox
<n900000>
pinephone has that new gstreamer patch
<n900000>
hopefully we can have an mpv build that accelerated on the pp
<n900000>
For music I'm using MOC on the n900
<uvos>
anyhow hardware prestation performance is broken by the pvr setup being broken (x clients (no the comp manager) are copying frames on cpu)
<n900000>
with alsamixer to mute the external speaker
<n900000>
ahh ok, sounds like a ton of work to even attempt doing
mintphin has quit [Quit: This computer has gone to sleep]
<Wizzup>
sicelo: I wonder why we have it disabled then
<Wizzup>
parazyd: can you add WEXT for a -devel kernel for n900?
<Wizzup>
maybe look at the defconfig sicelo mentions
<sicelo>
yes i saw. that's why i think if it worked with nl80211 + dbus, no need to change. nl80211 is the better option long term, of course
mintphin has joined #maemo-leste
<Wizzup>
yes, but hidden ap does not work due to the scan dbus scans work in wpa_supplicant
<Wizzup>
due to the way dbus scans work*
<Wizzup>
I don't know what to do here really
mintphin has quit [Client Quit]
<uvos>
i mean if it works for sicelo on sid with wpa_cli then we just need to figure out what the diff is between that and us no?
<Wizzup>
could be wext
<uvos>
sounds like its wext
<uvos>
yeah
<Wizzup>
yeah, but also wpa_supplicant being such a mess in some things
<Wizzup>
parazyd: yes, I think WEXT is needed
mintphin has joined #maemo-leste
<uvos>
we could also check what changes if anny are in the wl1251 driver between 5.6 or what we have on n900 atm and 5.13 or whatever sicelo used with sid
<uvos>
sicelo: ^^^
mintphin has quit [Client Quit]
mintphin has joined #maemo-leste
<Wizzup>
my memory is so hazy, I don't even recall why we wanted the newer wpa_supplicant
<Wizzup>
good we have irc logs
<bencoh>
because new is better, and red is faster!
<sicelo>
:-)
<uvos>
heh
<uvos>
i think Wizzup was encountering a bug iirc
mintphin has quit [Quit: This computer has gone to sleep]
mintphin has joined #maemo-leste
uvos has quit [Ping timeout: 245 seconds]
<Wizzup>
yeah but I don't recall what
<Wizzup>
sicelo: with wext, can you check if you can connect to hidden wlan?
<sicelo>
i can try, but tomorrow. have to turn myself in now. didn't have success booting debian - i really don't know why recent kernels are hit-and-miss with booting. the same kernel can boot one moment, and not boot the next :-/
<Wizzup>
ok
<Wizzup>
I'm building libicd-network-wpasupplicant 0.1.9 now
<Wizzup>
let's hope it doesn't break wifi for folks in devel, but fixes it for n900 folks
diejuse has joined #maemo-leste
stano has quit [Ping timeout: 265 seconds]
stano has joined #maemo-leste
<Wizzup>
freemangordon: hmm, I believe that if we pass all the hidden SSIDs as arguments to the dbus scan call, maybe the hidden ap stuff can work over dbus too
<Wizzup>
I think if we want to see why the cmd one fails vs the dbus one, we can look at these calls:
<Wizzup>
ret = wpa_supplicant_trigger_scan(wpa_s, scan_params);
<Wizzup>
in both wpa_supplicant/scan.c and wpa_supplicant/dbus/dbus_new_handlers.c
<Wizzup>
could maybe use wpa_scan_clone_params
mintphin has quit [Quit: This computer has gone to sleep]