uvos has quit [Read error: Connection reset by peer]
vandys has quit [Quit: Leaving]
<sunshavi_>
df
<sunshavi_>
kbd issue. sorry
sunshavi_ has quit [Read error: Connection reset by peer]
k1r1t0 has quit [Ping timeout: 256 seconds]
k1r1t0 has joined #maemo-leste
k1r1t0 has quit [Remote host closed the connection]
k1r1t0 has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 256 seconds]
joerg has quit [Ping timeout: 268 seconds]
joerg has joined #maemo-leste
k1r1t0 has joined #maemo-leste
k1r1t0 has quit [Read error: Connection reset by peer]
k1r1t0 has joined #maemo-leste
k1r1t0 has quit [Read error: Connection reset by peer]
k1r1t0 has joined #maemo-leste
rafael2k has joined #maemo-leste
ceene has joined #maemo-leste
elastic_dog has joined #maemo-leste
elastic_dog has quit [Killed (cadmium.libera.chat (Nickname regained by services))]
<rafael2k>
tested the pigzz's pinhole... still very early stages, but he is writing in a very portable way, supporting kirigami, silica, qt-controls and uuitk
<rafael2k>
managed to compile with qt-controls and kirigami, all good
<rafael2k>
the UI seems nice, without any big issue
<rafael2k>
still very early stages... but I think we have a winner : )
<rafael2k>
btw, sometimes the ov5640 gets boged in boot with the current 6.1.3 kernel in Chimaera.. just rmmod and modprobe it starts working... still debugging the issue
<dsc_>
BlagovestPetrov4: when are you receiving the cables?
<BlagovestPetrov4>
I'm waiting for the micro usb connectors from AliExpress. Hopefully in two weeks
<dsc_>
cool, I have 2x droid4's that are 'bricked'
<uvos>
there is no reason this needs to be "hardcoded" into any config file at all
<rafael2k>
until nobody fixes it, it is a solution, even if temporary
<rafael2k>
: )
uvos has quit [Quit: Konversation terminated!]
<freemangordon>
rafael2k: what is that white stripe on top of camera application?
<freemangordon>
also, you may want to set some fullscreen flag (not sure which one)
ikmaak has quit [Ping timeout: 260 seconds]
ikmaak has joined #maemo-leste
<rafael2k>
freemangordon: good question, I'd love to get rid of it
<freemangordon>
dsc_: how do you start the application?
<freemangordon>
also, is this chimaera?
<rafael2k>
chimaera, yes
<freemangordon>
rafael2k: oops, "how do you start the application?" was pointed to you
<freemangordon>
like, do you change qt platform plugin?
<rafael2k>
ah no no
<rafael2k>
I did not change nothing
<rafael2k>
just called the app
<rafael2k>
should I try some QT switches?
<freemangordon>
no
<freemangordon>
I was thinking if you may possibly start with wrong theme or platform plugin
<rafael2k>
I could open the project in QT Creator and see if there is some stuff in the top
<freemangordon>
if you start on desktop, do you still see that white stripe?
<freemangordon>
right
<rafael2k>
need to try, did not compile on my bullseye desk yet
<rafael2k>
will do it
<dsc_>
freemangordon: its in a 'works on my machine' state currently, needs some packaging still
<Wizzup>
morning
<dsc_>
yes chimaera
* Wizzup
trying waydroid on maemo-leste to set up his bank account before the 24h expiry
mro has quit [Remote host closed the connection]
mro has joined #maemo-leste
k1r1t0 has quit [Ping timeout: 256 seconds]
pere has quit [Ping timeout: 260 seconds]
Twig has joined #maemo-leste
noidea_ has joined #maemo-leste
pere has joined #maemo-leste
<freemangordon>
Wizzup: change the bank
<Wizzup>
freemangordon: yeah I found one that isn't like this
<freemangordon>
right, that's how we shall heal them ;)
<Wizzup>
the one I am at should also offer a token
<Wizzup>
but they said 'they do not have them'
<freemangordon>
hehe
<Wizzup>
the other bank also said it but then when I insisted the 'found some'
<Wizzup>
*shrug*
<Wizzup>
brb
<freemangordon>
I still don;t get it what's wrong with OTP
<norayr>
>hildon-base : Conflicts: elogind but 246.10-2 is to be installed
<Wizzup>
norayr: yes, this is mentioned in the news post.
<norayr>
that's in emulator. trying to build something, but apt build-dep . returns that.
<Wizzup>
this is why we don't tell people to use chimaera, it's not ready
<Wizzup>
:)
<norayr>
i was able to build other things without this problem. :/
<Wizzup>
there is no workaround here
<norayr>
ok, i'll try to do something.
<norayr>
i thought this is solved.
<norayr>
because i guess this was solved on droid. and on pp.
<Wizzup>
not solved anywhere
<Wizzup>
100%
<Wizzup>
the phones are usable without elogind but it has spread as some virus to most pkgs so they now hard depend on it
<Wizzup>
so we need to accept it and also support elogind
<Wizzup>
until then, we're stuck here
<norayr>
eh. i still resist installing elogind on my gentoo. (:
<norayr>
ok will try to install dependencies somehow and build the package.
<norayr>
will ask for a repo soon. hopefully.
<Wizzup>
cool
<Wizzup>
bbl
<norayr>
Wizzup: did you notice we discussed that the volume up key is unable to trigger vkb on pp?
<norayr>
as uvos helped to find out, it gets blocked by volume applett.
<norayr>
uvos, Wizzup, right now it is impossible to write in pidgin on pp because of that. i cannot do Enter, because enter doesn't work well with old vkb backend. and new vkb backend is not triggerable.
<norayr>
can we just switch to new vkb backend and give up the old one?
<Wizzup>
norayr: what is this magical new vkb backend
<norayr>
x11 backend by uvos?
<norayr>
we have currently two backends. uvos can explain it better.
<Wizzup>
I think you lack a lot of info here
<norayr>
new backend is why we are able to write in non hildonized apps.
<norayr>
old backend is for hildonized apps.
<Wizzup>
not really
<Wizzup>
right now any gtk2 and gtk3 application will have a virtual keyboard, where they are 'maemo'ized or not
<Wizzup>
what is missing is the qt5 equivalent, which I didn't port yet
<norayr>
okay, still, right now maemo is not usable at all, since enter key is not possible. we need to do something with that.
<norayr>
look
<Wizzup>
then there is this x11 thing that is limited and has to be invoked manually
<norayr>
enter key will be possible with new uvos backend for vkb
<Wizzup>
then there is the suggestion to use at-spi2 for this, which nobody did
<norayr>
when you tap on edit box, or you trigger the vkb with the key (search on d4) you get different keyboards actually.
<Wizzup>
the reality is that using maemo leste now on a device without keyboard means you're in for a world of pain, which we know
<norayr>
so the kbd that you trigger with a hardware key has proper working enter key.
<Wizzup>
and we need the volume buttons to be the volume buttons, I'd say
<norayr>
the kbd that triggers because of the tap on the edit field - doesn't.
<Wizzup>
whatever the 'enter key' issue is, seems like a different problem
<norayr>
i know because i was using the pp with onscreen kbd, as well as d4. this bug is common to both devices.
<norayr>
if you trigger the kbd by the hardware key, the enter works.
<norayr>
uvos was saying that's because it has new, x11 backend.
<norayr>
and he wrote it. while the old code has all sorts of bugs, and kbd triggered by tap is more buggy.
<norayr>
so enter may not work there.
<norayr>
so i was typing a message, then i was coming back to edit field, then i was triggering other version of the keyboard with volume up, and then enter would work.
<norayr>
that was already very discomfort, but now it is even worse. because the new keyboard code is not triggerable.
<norayr>
not sure that the volume up is a good solution. i would prefer to not explain to my friends whom i try to convince to use maemo leste that in order to type enter they need to trigger the kbd by other key.
<norayr>
not by tapping.
ceene has quit [Remote host closed the connection]
<Wizzup>
maybe you can file a bug report for pidgin, assuming it's gtk3, and enter not working
<Wizzup>
I've never tried pidgin since I just want to use it through tp ;)
xmn has joined #maemo-leste
<norayr>
no no, it's not pidgin.
<norayr>
we duscussed it here with uvos before, last year, and year before last year.
<norayr>
my message is:
<norayr>
if i send enter by triggering vkbd by hardware key (like vol+up or search) then enter works!
<norayr>
that's not pidgin, that's vkbd, and apparently you didn't know about the issue.
<norayr>
just tried again, that's what i am saying: in maemo's xterm, in hildonized leafpad enter works.
<norayr>
in pluma it doesn't work.
<norayr>
you cannot write in pluma and send enter by vkb
<norayr>
unless you trigger the vkb by hardware key, like vol up or search on d4
<norayr>
you need to know that we have two different backends for vkb.
<norayr>
or uvos has to come to clear it up.
<Wizzup>
right, so your problem is that enter doesn't work from the normal triggered keyboard.
<Wizzup>
I think that's what I surmised earlier
<Wizzup>
in any case I never use the x11 keyboard version on my droid
<Wizzup>
so I don't know how it works differently
<dsc_>
I am running 2x droid4 with distcc for distributed compiles
<dsc_>
lel
<Wizzup>
dsc_: if you turn the screen off it disabled one core, jfyi
<Wizzup>
this is for power saving purposes
<Wizzup>
but you might want to consider keeping the screen on
<dsc_>
Wizzup: ahhhhh I was wondering why `htop` would sometimes show 1 core
<dsc_>
was thinking maybe I was starting to go crazy
<dsc_>
probably wasted a lot of time as well
<dsc_>
not knowing this lol
<Wizzup>
:(
<dsc_>
this distcc stuff is cool though
<dsc_>
cmake + ccache, distributed over multiple droid's
<Wizzup>
heh, you have multiple working ones now? :D
<dsc_>
Wizzup: Yeah I have 2, and hopefuly BlagovestPetrov4 can bring 2 others from the dead ^^
<Wizzup>
I can probably too when I get there
mro has quit [Remote host closed the connection]
<Wizzup>
usually just a wall charger is enough for me to get it working
<Wizzup>
it's weird, I've never actually bricked any
<dsc_>
it simply wont start charging when wall charger is connected
<dsc_>
:(
<Wizzup>
if you leave it there for a day or two usually magic happens still
<dsc_>
:D
<Wizzup>
alternatively you can -probably- use one of the working d4s with some battery swapping magic
<Wizzup>
but yeah
<BlagovestPetrov4>
oh, I could easily brick them :D
<BlagovestPetrov4>
yeah, that's the easiest way. I'm using the one that came with the lapdock
mro has joined #maemo-leste
mro has quit [Read error: Connection reset by peer]
<sicelo>
re: vkb - norayr and others - what about, instead of using a volume key, add a status menu item with high priority (so it doesn't get moved too far to the bottom)? it's a really ugly workaround, but in the absence of other immediate solutions ...
<Wizzup>
sicelo: how about just finding a proper solution :)
<Wizzup>
like, the at-spi module
<sicelo>
well if there's time for that, sure :-)
<sicelo>
i was just mentioning since it sounds like an immediate problem for norayr for some reason
<freemangordon>
Wizzup: or swipe bottom-up
<Wizzup>
I think ultimately we have a few things on our hand with hildon input method
<Wizzup>
one is qt5, perhaps through at-spi, the other is that we don't always want it 'over' the application
<Wizzup>
neither are simple, so I don't think it'll happen in the next week or so
<freemangordon>
umm, qt5 should not be at-spi
<freemangordon>
we already have qt4 inegration with him on fremantle
<freemangordon>
I guess we can port it to qt5
<freemangordon>
I doubt it is that complicated
<freemangordon>
but, if you promise to fix the theming, I will make qt5 him input plugin :p
<freemangordon>
deal?
<bencoh>
I got some strange usb/uart-related error after disconnecting droid4 from laptop and connecting it to some noname wallcharger: droid4:~$ dpkg -l |grep linux-image
<bencoh>
rc linux-image-droid4 5.10.9-1+2m7.1 armhf Linux kernel for Motorola Droid4
<bencoh>
ii linux-image-omap 5.18.9-2+2m7 armhf Linux kernel for OMAP devices running Maemo Leste
<freemangordon>
SetContextClientWindow() is called only in DispatchKeyEvent() :)
<rafael2k>
I'm following a bug ticket also in which chromium will be able to use pipewire (which in turn can get video from libcamera) in order I can join a webrtc call using the camera
<Wizzup>
so now we'll have to compile with qtwebengine and chromium?
<rafael2k>
tks!
* Wizzup
crawls under a bed ;)
<Wizzup>
s/with/both/
<rafael2k>
:P
<freemangordon>
Wizzup: not now, but you got the idea :p
<rafael2k>
I want my chromium working in webrtc calls with video!
<rafael2k>
eheheheh
<bencoh>
wait, does pipewire work in leste?
<rafael2k>
it is in the repo... did not tested it yet
<rafael2k>
it kind of works in bullseye
<bencoh>
don't we have pulseaudio-specific modules?
<rafael2k>
but my use case would be just for video... for audio it was a bit flacky in bullseye / chimaera
<rafael2k>
yes
<bencoh>
like the sphone volume pa plugin, or whatever that was called
<rafael2k>
pipewire can be a drop-in replacement to pulseaudio
<Wizzup>
only in the most basic setups
<rafael2k>
but I will not use pipewire for audio at this point, just for routing video
<Wizzup>
pipewire requires a lot of configuration, but yes, it's superior to pulseaudio for sure
<Wizzup>
but if we start pulling out PA now for pipewire I think our jenga mobile distro will come tumbling down :P
<rafael2k>
but in bullseye / chimaera it is a bit old... I did not like it on my desktop tbh... had some issues
<Wizzup>
(metaphorically of course)
<rafael2k>
dont do it
<rafael2k>
it is not stable enough in the old version we have right now in chimaera
<rafael2k>
but for video it can save lives, yes
<freemangordon>
ok, I will fork chromium and will try to make it work properly with him
<freemangordon>
not now
<bencoh>
rafael2k: if you really need it you could probably add it without enabling the pipewire-pulse service
<Wizzup>
rafael2k: we can package a newer one later if we want
<bencoh>
hmm, interestingly enough, the droid4 does not recognize my noname wallcharger
<bencoh>
whereas (picky) n900 does
<Wizzup>
I think fmg was working on charger patches for the kernel somewhat recently
<Wizzup>
charger detection specifically
<bencoh>
yet same wallcharger was able to power droid4 and make it boot
<rafael2k>
bencoh: lemme see if I manage to make webrtc work in chromium with the version we already have, then if we need a newer version, it should be easy to package indeed
<bencoh>
(with an empty battery)
<rafael2k>
bencoh, and I agree we should not enable pipewire-pulse
<bencoh>
Wizzup: upgraded to 6.1.0-rc8 btw (it's funny that my phone has the most recent kernel of all my devices here)
<Wizzup>
:)
<bencoh>
should dist-upgrade work for beowulf->chimaera?
<Wizzup>
ehhh... potentially :)
<Wizzup>
I did it for my phone
<bencoh>
:]
<bencoh>
any recommendation before running it?
<bencoh>
apart from /etc/no_lg_reboots*
<Wizzup>
full battrery, wifi
<Wizzup>
sry mtg
<bencoh>
let's see ...
<sicelo>
bencoh: you got it wrong ... (picky)droid4 😃
<bencoh>
haha
<bencoh>
well, n900 was supposedly picky with usb chargers back then
ungeskriptet has joined #maemo-leste
Guest5254 has joined #maemo-leste
<Guest5254>
2
Guest5254 has left #maemo-leste [#maemo-leste]
uvos has joined #maemo-leste
qrno11 has joined #maemo-leste
ikmaak has quit [Ping timeout: 260 seconds]
ikmaak has joined #maemo-leste
k1r1t0 has joined #maemo-leste
ikmaak has quit [Read error: Connection reset by peer]
k1r1t0 has quit [Read error: Connection reset by peer]
k1r1t0 has joined #maemo-leste
ikmaak has joined #maemo-leste
<uvos>
the mainline kernel on d4 dosent detect any charger at all
<uvos>
ie it dose no charge detection
<uvos>
mbm will only boot if it detects a wall charger, but thats totaly unrelated to the kernel ofc
Twig has quit [Ping timeout: 272 seconds]
ikmaak has quit [Ping timeout: 260 seconds]
inky_ has quit [Remote host closed the connection]
inky_ has joined #maemo-leste
inky_ has quit [Remote host closed the connection]
inky has joined #maemo-leste
inky has quit [Read error: Connection reset by peer]
inky has joined #maemo-leste
inky has quit [Remote host closed the connection]
inky has joined #maemo-leste
inky has quit [Remote host closed the connection]
<norayr>
when connecting to hidden wifi, maemo asks for ssid, not for password. is it normal or bug?
<norayr>
but when i enter something, it doesn't want also a password.
<norayr>
i think it asks for ssid but it treats it as password.
<norayr>
rafael2k: well, it qtwebbrowser doesn't type in pluma or pidgin. and secondly, it doesn't type in armenian. or anything other than latin.
<uvos>
pretty sure the qt keyboard has all kinds of languages
<Wizzup>
norayr: it shuld ask both, but ssid first, then it tries to find ap
<Wizzup>
if found it will ask for password
<Wizzup>
you can set it up through cpa sa well
<Wizzup>
uvos: btw I'm close to the tp module for sphone :)
<uvos>
Wizzup: weee
<norayr>
hmm
<norayr>
uvos, wow i didn't know it has.
<sixwheeledbeast>
If Hidden it would need the SSID first
ikmaak has joined #maemo-leste
<bencoh>
hmm, is that a known issue (while upgrading to chimaera)? dpkg-divert: error: 'diversion of /lib/udev/rules.d/85-input-devices.rules to /lib/udev/rules.d/85-input-devices.rules.leste-orig by leste-config-droid4' clashes with 'diversion of /lib/udev/rules.d/85-input-devices.rules to /lib/udev/rules.d/85-input-devices.rules.leste-orig by leste-config-mapphone'
<bencoh>
apparently leste-config-mapphone depends on leste-config-droid4
<Wizzup>
bencoh: well, it should be fixed, but yeah.
<Wizzup>
bencoh: but yeah I -thought- it was fixed
<bencoh>
and then let it reinstal/reconf the leste-config-droid4 package, and only after that I reinstalled the mapphone one
<Wizzup>
yeah.
<bencoh>
overall the dist-upgrade somewhat failed a few times and I fixed it by running apt --fix-broken install and re-run dist-upgrade, but overall it worked
<bencoh>
deviced rebooted properly to hildon )
<bencoh>
:)
<Wizzup>
great
qrno11 has left #maemo-leste [#maemo-leste]
uvos has quit [Read error: Connection reset by peer]