<uvos>
Wizzup: to be honest voicecall looks alot like bits of sphone
<uvos>
are we certain we need yet another abstraction layer here?
<Wizzup>
their tp code looks pretty good
<Wizzup>
I would just have to copy paste it basically otherwise
uvos has quit [Ping timeout: 268 seconds]
<Wizzup>
and no, not certain, but I'd like to try it out
sunshavi has quit [Remote host closed the connection]
sunshavi has joined #maemo-leste
sunshavi_ has joined #maemo-leste
sunshavi has quit [Remote host closed the connection]
joerg has quit [Ping timeout: 272 seconds]
joerg has joined #maemo-leste
Twig has joined #maemo-leste
rafael2k has joined #maemo-leste
ceene has joined #maemo-leste
<rafael2k>
so, I finally have a nice picture (without artifacts in the preview window) in qcam: qcam -r gles -spixelformat=NV21,width=1280,height=720 -platform xcb -style=fusion
<rafael2k>
now focus on an UI... I'm considering compiling gtk4 for MegaPixels... until we have a nice UI from piggz advanced camera (no code yet), or just hammer qcam to look nice in Maemo
<dsc_>
UI for the camera?
<rafael2k>
yes
<dsc_>
<== resident UI person
<dsc_>
self-proclaimed
<rafael2k>
: ))
<rafael2k>
the only shitty thing for newer 6.1 is that only rear camera is working
<rafael2k>
with my old patchset on 5.15 both cameras where working
<rafael2k>
*were
<dsc_>
finally enough those version numbers are easily confused with Qt versions
<dsc_>
funnily*
<rafael2k>
*kernel
<rafael2k>
ehehehe
<rafael2k>
at least qcam is qt 5, no matter what, no 6 in the horizon
<dsc_>
yeah, guessing from -style=fusion its a QML app?
<dsc_>
(QtQuick)
<dsc_>
oh, its also available for qtwidgets
<dsc_>
TIL
<rafael2k>
don't really understand much, it just made it work without black on black UI
<rafael2k>
For now I prefer to keep with a newer kernel in Chimera, in the spite of right now only having rear camera supported, but with proper libcamera support (including YUV, which indeed made qcam works perfectly now!)
<Wizzup>
dsc_: lowercase fine?
<Wizzup>
rafael2k: should we try to just import piggz cam now or is that a serious undertaking?
<Wizzup>
uvos: do we have an issue for the theme problem in qt5 (text contrast) ?
<rafael2k>
Wizzup: nothing to import yet... he did not release his libcamera port yet
<Wizzup>
rafael2k: oh...
<rafael2k>
this is why I was thinking that adding gtk4 to Chimaera would allow us to get MegaPixels
<Wizzup>
is qcam a gui?
<rafael2k>
yes, it is a gui
<rafael2k>
in qt
<rafael2k>
it compiles and runs fine, but not really optimized for a phone
<Wizzup>
if we can avoid gtk4 while we're waiting for piggz, that would have my preference
<rafael2k>
ok, no strong feeling here
<Wizzup>
bencoh: in fremantle->ascii this was a problem, and again in beowulf->chimaera
<Wizzup>
iirc
<Wizzup>
oh this was regarding linking over
<Wizzup>
was scrolled up
<Wizzup>
rafael2k: well it's a significant undertaking to get gtk4 in, and it's not even in the debian/devuan counter part, so I think it will be painful
<Wizzup>
and it's potentially even -more- to support right now :p
<dsc_>
Wizzup: any repo name is fine
pere has joined #maemo-leste
<rafael2k>
Wizzup: there is experimental repo for bullseye
<rafael2k>
but lets try to avoid, agree
<rafael2k>
buuuut, I don't think it will be much work
<rafael2k>
lets see if we can use piggz advanced camera or even make the buttons bigger in qcam
<dsc_>
so this camera app
<dsc_>
it can take pictures
<dsc_>
and rotate pictures that were taken
<dsc_>
thats about it, right
<dsc_>
any reason why we cant make our own Maemo Photo app
<dsc_>
:P
<rafael2k>
we already have the UI code somewhere
<rafael2k>
just the gstreamer-0.10 code is broken
<rafael2k>
(old Maemo camera UI code)
<Wizzup>
was that open source?
<rafael2k>
I remember you sent me
<rafael2k>
you or someone else
<dsc_>
rafael2k: are you testing on PP or D4?
<Wizzup>
d4 has no camera driver currently
<dsc_>
ic
<rafael2k>
yes, the UI was open source, just the gstreamer plugin was closed source
<rafael2k>
PP
<rafael2k>
someone sent me the Maemo camera code at some point... don't remember the path thou
<Wizzup>
that is VRZ_7.7.1-85_MZ609-31_1FF.xml.zip
<tmlind>
Wizzup, uvos__: for mz617 flashing just utags should in theory still be ok, you should be still be able to fastboot flash cache utagboot in fastboot mode.. in theory.. should be tested on some mostly broken donor device at some point..
<uvos__>
tmlind: sure if utags are correct
<uvos__>
if they arnt then your really stuck
<tmlind>
uvos__: hmm right, not sure fastboot erase utags works
<uvos__>
no it dose not
<tmlind>
uvos__: ok well still the same problem even if you have kexecboot flasher :p
<tmlind>
kexecboot flashed i mean
<uvos__>
sure yes
<uvos__>
thats true
<uvos__>
kexecboot itself being broken or missing isent an issue
<tmlind>
oh and i meant fastboot flash cache kexecboot above, not utagboot..
<uvos__>
yeah we understand :)
<tmlind>
thank you :)
<tmlind>
uvos__: hmm probably also recovery mode still boots even with bad utags, but i guess no way to flash anything unsigned from the stock recovery?
<uvos__>
it dident here, (enter recovery mode with correct utagboot utags that is)
<uvos__>
also idk if an upgrade would clear utags
<uvos__>
and if your on 4.1 you stuck
<uvos__>
since it wont let you upgrade the same version again
<uvos__>
(must be newer)
<uvos__>
and yes, nothing unsigned eihter
mro has quit [Remote host closed the connection]
<Wizzup>
tmlind: thanks for the info
<Wizzup>
I'm looking at adjusting flash-droid-4-fw.sh for mz609
<uvos__>
i would just perform the upgrade normaly
<uvos__>
but up to you
<tmlind>
uvos__: hmm yeah upgrade could possibly would clear bad utags
<tmlind>
heh could be tested with a $10 mz617 logic board from ebay most likely
<Wizzup>
uvos__: what is 'normally' ?
<uvos__>
Wizzup: load the zip onto sdcard
<uvos__>
enter recovery mode
<uvos__>
select zip for upgrade
<uvos__>
let it run
<uvos__>
this dose a real upgrade
<uvos__>
including running all the moto scripts
<uvos__>
(dunno what they do but they dont run if you just fastboot flash it)
<Wizzup>
uvos__: I've never done that before, let me try that :D
<Wizzup>
uvos__: the .xml file seems to just contain flashing steps though
<tmlind>
or am i confused with the device numbers again
<Wizzup>
I think so :)
<Wizzup>
I have VRZ_MZ609_1.6.0_279_1FF.xml.zip which has VRZ_MZ609_1.6.0_279_1FF.xml/allow-mbmloader-flashing-mbm.bin
<Wizzup>
but that's not mz617
<Wizzup>
I wrote to 3 people in xda-developers forum but nobody replied to my request for mz617 files
<Wizzup>
uvos__: looks like the flashing worked
<uvos__>
tmlind: yes
<uvos__>
but we had that one allready
<tmlind>
oh right, it's the mz617 that's missing..
<tmlind>
too many devices
<Wizzup>
hehe
<Wizzup>
maybe if we know someone who works at motorola
<uvos__>
could work
<uvos__>
i mean there is a chance they dont have it either
<uvos__>
they where bought 3 times and restuctured twice since then...
<Wizzup>
still
<Wizzup>
I tried to search archive.org by checksum and that also didn't surface the zip files
<tmlind>
so presumably we'd like to find a file VRZ_MZ617_1.6.0_279_1FF.xml.zip i guess
<uvos__>
so those are the full updates
<uvos__>
i quite a few of those for mz617
<uvos__>
but none contain
<uvos__>
however i kow for a fact
<uvos__>
that some partial (ota) updates did
<uvos__>
from xda forum posts
<uvos__>
*i have quite a few
<Wizzup>
there's also a file called fastboot-p2_pasteur-pasteur_mmi-user-4.1.2-9.8.2OT_127-127-release-keys-cid2-Verizon-US.tar.gz on some google drive that presumably had them
<tmlind>
oh ok
<uvos__>
we spent mutch time in this area ^^
<tmlind>
yeah i guess it will surface at some point
<Wizzup>
I still have the torrent open in case someone still has it
<tmlind>
heh ok
<Wizzup>
uvos__: ok so I rooted the mz609 but now I'm wondering why I did that at all :)
<uvos__>
Wizzup: idk
<Wizzup>
:D
<uvos__>
Wizzup: to check things in android while improveing leste support?
<Wizzup>
in any case I have 4.0.4 and it's rooted, so I have some scripts for sure
<Wizzup>
uvos__: maybe yes
<uvos__>
anyhow update was nessecaty
<uvos__>
for newer kernel
<Wizzup>
I can try kexecboot next now
<Wizzup>
uvos__: yes
<Wizzup>
presumably I -do- use the allow-mbmloader-flashing now :)
<uvos__>
yes
<tmlind>
Wizzup: if you get mainline kernel booting on mz609, can you please run two copies of memtester user space app and see if it produces memory errors?
mardy has joined #maemo-leste
pere has quit [Ping timeout: 268 seconds]
<tmlind>
something like memtester 400M & should do
<tmlind>
two instances
<tmlind>
i was not seeing errors with the android kernel on mz609, but i see them instantly with mainline kernel
<Wizzup>
tmlind: ok, will do, it might not be today, but I'll finish kexecboot now for sure
<tmlind>
ok no rush, just wondering about it
sunshavi_ has quit [Remote host closed the connection]
<Wizzup>
Writing 'bpsw' (bootloader) no such partition
<Wizzup>
FAILED (remote: '')
<Wizzup>
fastboot: error: Command failed
<uvos__>
Wizzup: mz609 dosent have bspw look at kexecboot instructions
<Wizzup>
:)
<Wizzup>
let me do that
<uvos__>
its cache :)
<Wizzup>
I didn't see it in the README
<uvos__>
hmm ok
<uvos__>
but the name of the utags files tells you
<uvos__>
should anyhow
sunshavi_ has quit [Remote host closed the connection]
sunshavi_ has joined #maemo-leste
<Wizzup>
ok, got kexecboot and its booting android
<Wizzup>
tmlind: when you say run 'two copies', what does that mean? different versions, or just run it twine?
<Wizzup>
twice*
mro has joined #maemo-leste
<rafael2k>
cant we use qtwebbrowser vkb everywhere? it is soooo good.
<rafael2k>
: )
<Wizzup>
isn't it really small?
<rafael2k>
it is very huge
<uvos__>
depends on QT_SCALE_FACTOR presumably
<rafael2k>
: )
<rafael2k>
65% of the screen approximately
<rafael2k>
I like
<uvos__>
its really small in portrait
<Wizzup>
uvos__: hm I wonder if android did something with the cache partition
<uvos__>
yes it absolutly dose
<rafael2k>
ah ok, in portrait
<rafael2k>
to watch youtube need widescreen... eheheh
<uvos__>
having kexecboot on cache breaks android (slightly)
<uvos__>
unfortionatly we have no where else to put it
<Wizzup>
uvos__: I would say android breaks kexecboot maybe
<uvos__>
no
<uvos__>
it should not
<uvos__>
it fails to mount
<uvos__>
and then just gives up and continues in degraded mode
<uvos__>
at least thats what happens on my mz617
mro has quit [Remote host closed the connection]
<Wizzup>
btw, kexecboot is upside-down for me on mz609
<Wizzup>
uvos__: ok, well, it worked first time I flashed, then it bootd to android, and now it didn't work on reboot (stuck at logo), but flashing it again worked
<Wizzup>
let me try it again :D
<uvos__>
hmm wierd
<uvos__>
worst case
<tmlind>
Wizzup: yeah i tried to get the stock kernel to rotate the fb via /sys but it was just crashing..
<uvos__>
since you are root on android
<uvos__>
just remove cache from its mounts
<tmlind>
Wizzup: hmm maybe kexecboot has some rotate support
<uvos__>
check system/etc/vold.fstab
mro has joined #maemo-leste
<rafael2k>
In portrait it is small, but I can type, it is useful (about the qtwebrowser vkb)
<tmlind>
Wizzup: maybe see kexecboot config option rotate, i think that can be added to boot.cfg, maybe that works better. it's parsed in set_fbcon()
<uvos__>
the fact that vkb is tiny in portrait and the settings pannel dosent work in portrait (on d4) is why i disabled portrait in qtwebowser initally
<Wizzup>
tmlind: it's fine, it doesn't matter @ rotate
<Wizzup>
tmlind: btw, just realised, does the hdmi port work? that could be useful for testing
<rafael2k>
I took a pic here
<tmlind>
the comment there says: Value should be 'rotate:<n>', uses degrees
<uvos__>
hdmi works
<uvos__>
(on mz617)
<Wizzup>
cool
<uvos__>
but serial is more usefull really
<Wizzup>
sure both are :)
<tmlind>
Wizzup: hdmi should work if configured so the lcd is left out of the dts for mz609 and mz617
<Wizzup>
rafael2k: and yes we might be able to have that qt keyboard in some other qt apps too, but ideally we'd really have the same one everywhere
<Wizzup>
rafael2k: yeah for me that's quite small
<Wizzup>
chalka eh
<Wizzup>
:D
<rafael2k>
it : )
<tmlind>
boot.cfg line to rotate probably needs to be FBCON=fbcon:180
<rafael2k>
it is small, but is fine, I like it
<Wizzup>
tmlind: I will try that after I've made some food, and then also try to perhaps boot the maemo kernel, see if it boots at all
<Wizzup>
(and if that works, I might try memtester)
<tmlind>
ok let's hope kexecboot rotate works :)
<Wizzup>
tmlind: still not sure what you meant with 'run two copies' though
<tmlind>
Wizzup: one memtester instance for each processor
<Wizzup>
ok
<Wizzup>
ty
<Wizzup>
one last thing, I have a -lot- of mz617s at home, well, relatively a lot
<Wizzup>
I bought this one lot on ebay for like 8 usd per piece, marked broken, and they all worked
<Wizzup>
like 10+
<Wizzup>
so I could sacrifice one for tests if it helps
<uvos__>
how is the mz609 invnetory?
<Wizzup>
lower, but I think I have one or two
<rafael2k>
Wizzup: about the vkb... of course I hope my second PP physical keyboard arrives fast (it is stuck in customs still), but the current vkb it is hard to use the terminal tbh... I'd love to have that qtwebbrowser vkb in a terminal emulator...
<uvos__>
and xt894 you have enough to use as beer costers xd
<Wizzup>
uvos__: well they're at my place but I don't consider they 'mine' :)
<Wizzup>
them
<Wizzup>
I hope we can send them to people who want to develop
<Wizzup>
or test
<tmlind>
Wizzup: oh i think the kexecboot FBCON option just appens the rotate to the selected kernel cmdline, never mind
norayr has left #maemo-leste [Disconnected: closed]
<uvos>
the volume applet is holding an exlusive grab on volum up and down
<uvos>
wich makes sense
<uvos>
so h-d cant get those keys
<norayr>
ah!
<norayr>
maybe then it worth making x11 vkb the default?
<norayr>
or invent a gesture?
<uvos>
cant have volume be both volume and keyboard
<uvos>
norayr: well for now you can just uninstall the volume applet
<uvos>
afaik it dosent work on pp anyhow
<uvos>
but yes
<norayr>
or add it to... add keyboard triggering shortcut to the maemo notification area or how is it called right of the clock?
<uvos>
you need to invent some new way to trigger the keyboard
<norayr>
well not exactly me, this is a responsible decision. if i say let's do that by swiping from down to up then after maybe it will happen that swyping is good for minimizing the app for example.
<norayr>
it must be well thought.
<uvos>
no idea
pere has quit [Ping timeout: 248 seconds]
<rafael2k>
so the volume keys for volume are not working also right. hunft
<uvos>
yes well thats because the volume applet cant detect what stream volume to use