xmn has quit [Ping timeout: 272 seconds]
xmn has joined #maemo-leste
<inky> kiva the app was fcamera. and it brought custom camera drivers.
xmn has quit [Quit: Leaving]
xmn_ has joined #maemo-leste
xmn_ has quit [Ping timeout: 245 seconds]
xmn_ has joined #maemo-leste
_whitelogger has joined #maemo-leste
_whitelogger has joined #maemo-leste
coffeecreature has left #maemo-leste [So long!]
vectis_ has joined #maemo-leste
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
System_Error has quit [Remote host closed the connection]
_whitelogger has joined #maemo-leste
_fab has joined #maemo-leste
ceene has joined #maemo-leste
xinomilo has joined #maemo-leste
kiva has joined #maemo-leste
<kiva> dsc_: so six step with pre defined values and predefined fade value would one solution and another solution would be stepless bar and fade speed value calculated from how many values are for use.
<kiva> inky: yes fcamera was that app.
<sicelo> BlessN900 was also a thing, and worked the same way
<kiva> Do I remember right Bless900 used fcamera driver?
<sicelo> iirc yes
<kiva> So Bless900 for Leste?
<sicelo> the fcamera drivers are not available for use with mainline
<kiva> but source is?
kiva has quit [Ping timeout: 240 seconds]
kiva has joined #maemo-leste
kiva has quit [Quit: Client closed]
Twig has joined #maemo-leste
<sicelo> dsc_: left review on the status-area-applet-battery MR
Livio has joined #maemo-leste
FANTOM has quit [Ping timeout: 244 seconds]
narodnik has quit [Quit: WeeChat 4.6.3]
narodnik has joined #maemo-leste
Livio has quit [Ping timeout: 264 seconds]
<dsc_> sicelo: ty
<Wizzup> freemangordon: great, ty
FANTOM has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
System_Error has joined #maemo-leste
System_Error has quit [Ping timeout: 264 seconds]
Livio has joined #maemo-leste
narodnik2 has quit [Ping timeout: 244 seconds]
System_Error has joined #maemo-leste
ceene has quit [Ping timeout: 252 seconds]
<dsc_> my pinephone survived the night without power
<dsc_> from 90% to 20%
<dsc_> wifi disabled, with conversations
<Wizzup> you can also use loginctl suspend to s2r
<Wizzup> with the right setup the modem will wake it up if there is a call/sms, but we never tried to do that yet
leste has quit [Remote host closed the connection]
<dsc_> Wizzup: preferably this suspend thing is an option in the dropdown menu that happens when you press the physical power button
<dsc_> however, since its all gtk I'm not particularly motivated to look at that
<dsc_> ill try suspend though
<dsc_> Wizzup: what email client do you use on Leste
<Wizzup> modest, the built in
<Wizzup> dsc_: no probably suspend would happen automatically once we have inhibitor locks or some kind
<dsc_> alright
Livio has quit [Ping timeout: 264 seconds]
arno11 has joined #maemo-leste
arno11 has quit [Quit: Leaving]
xmn has quit [Ping timeout: 248 seconds]
vectis_ has quit [Ping timeout: 272 seconds]
arno11 has joined #maemo-leste
pere has joined #maemo-leste
arno11 has quit [Quit: Leaving]
vectis_ has joined #maemo-leste
<freemangordon> dsc_: actually it is xml and dbus
<dsc_> do I understand correctly we need a mechanism to auto-suspend when the screen has been blanked for X amount of time?
<freemangordon> I meant that you can easily add button in powerkey menu
<freemangordon> I am not sure we shoud auto-suspend
<freemangordon> *should
<dsc_> ok
<freemangordon> maybe someone can run AI on that repo and ask it to generate documentation
<dsc_> freemangordon: btw, now that you are here
<dsc_> Qt apps with QtQuick scenes seem to render at 25 fps for me, and with QT_QUICK_BACKEND=software, it renders at 125fps
<dsc_> this GPU rendering also seems to introduce some stuttering at times
<dsc_> do you think this is Lima or our Qt maemo integration?
<freemangordon> most-probably it is HW sync
<dsc_> (this 125fps I dont understand btw, because QML scenes are vsync'd, and pinephone refresh rate is not 125fps)
<dsc_> (but probably due to how I measure things)
<Wizzup> freemangordon: dsc_: no, I don't think we want a human triggered s2r and I also don't think we should want that in general unless we have the right wake up in place and also the proper inhibit suspend locks
<Wizzup> dsc_: there is a mesa env var for vblank override
<dsc_> yes I found it
<dsc_> I tried vblank_mode=0 IIRC
<freemangordon> Wizzup: I didn't say we shall add such entry for everyone, it is for dsc_ to experiment if wants
<dsc_> yes, thanks :)
<freemangordon> BTW it is chatgpt that pointed me to that link :D
<dsc_> freemangordon: what do you mean with HW sync btw
<freemangordon> vsync
<freemangordon> do we know what is panel refresh rate? or it is cmdmode panel?
<dsc_> 60hz it seems
<freemangordon> dsc_: could you run glmark2 to see what it will show?
<freemangordon> glmark-es2 that is
<freemangordon> maybe you should have to build it from the repo
<dsc_> well, my issue with glmark2/glxgears is that it starts in landscape mode, which is laggy by default (on pinephone)
<dsc_> (even with orientation lock)
<freemangordon> no way
<freemangordon> why would it rotate?
<freemangordon> also, I guess you can force-rotate h-d
<dsc_> I think it rotates because the application window has not communicated it supports potrait
<dsc_> (but thats just guessing)
<freemangordon> I see
<freemangordon> you can force-rotate through h-d.ini
<dsc_> ah
<freemangordon> if you start it via osso-xterm, that may explain it
<freemangordon> I wonder why is osso-xterm blacklisted
<dsc_> suppose I need to restart hildon
<dsc_> how to?
<dsc_> ah just killall
<freemangordon> killall hildon-desktop
<freemangordon> omg 14 years ago
<dsc_> it still goes into landscape
<freemangordon> how do you start it?
<dsc_> via ssh, and also osso-xterm
<freemangordon> hmm
<dsc_> or ehm, "X terminal"
<dsc_> yes
<freemangordon> does ctrl-shift-r work?
<freemangordon> oh, no keyboard :)
<freemangordon> sec
<dsc_> xdotool search --name "glxgears" windowactivate --sync key ctrl+shift+r
<dsc_> we shall try
<dsc_> nope
<dsc_> ctrl-c worked, it closed it :P
<dsc_> oh wait
<freemangordon> no, you should send that to h-d
<dsc_> it magically rotated after ctrl-c
<freemangordon> or h-h
<freemangordon> yeah, to h-d
<freemangordon> try:
<freemangordon> dbus-send --system --type=signal /com/nokia/mce/signal com.nokia.mce.signal.sig_device_orientation_ind string:'portrait'
<dsc_> xdotool search --name "glxgears" windowactivate --sync key ctrl+shift+r
<dsc_> ^-- this works, just need to "alt-tab" it
<freemangordon> ok
<dsc_> ok so, 45fps in portrait
<dsc_> 17fps in landscape
<dsc_> the landscape is expected (on pinephone)
<freemangordon> mhm
<dsc_> but I think 45fps is too slow
<freemangordon> it is
<freemangordon> d4 does ~ 80 on glmark2-es2
<dsc_> do you want me to look with renderdoc
<freemangordon> you run glmark2-es2, right?
<dsc_> no glxgears
<dsc_> ill try glmark2
<freemangordon> no, forget about glxgears
<freemangordon> yes, do glmark-es2
<freemangordon> keep in mind mail400 is not the best gpu around :)
<freemangordon> hmm, I shall run glmark on my tabletg
<dsc_> well yeah
<freemangordon> not now though, have to do some cooking, bbl
<dsc_> I see a horse and a box, they render at ~45fps
<dsc_> yeah its not smooth
<dsc_> glmark2-es same story
<Wizzup> freemangordon: pinephone has a higher res than most of our devices
<Wizzup> imo portait performance is more than acceptable for me in the pp
<dsc_> portrait works great, very smooth
<dsc_> (hildon, that is)
<freemangordon> Wizzup: sure, portrait perf is ok
<freemangordon> 45fps *is* ok
<freemangordon> but, this is what n900 does :)
<freemangordon> or even more
<Wizzup> not at 720p :p
<dsc_> its the irregular stalls that bother me, which is prevalent when scrolling through lists @ QtQuick
<freemangordon> IIRC glmark score on n900 is 36 or somesuch
<Wizzup> r w/e the res is
<Wizzup> pp is 1440x720
<freemangordon> so?
<Wizzup> the n900 fits in that almost four times
<freemangordon> so? it is still the same fps
<freemangordon> no matter the reasons :)
<Wizzup> sure
<dsc_> i dont understand how hildon can be so smooth, but a very simple QML scene renders at 25fps
<freemangordon> hildon is optimised
<dsc_> i think hildon runs at a locked 60hz
<dsc_> it feels really smooth
<freemangordon> also, are you sure you don;t use qwidget?
<dsc_> I made a test QML program with a moving rectangle + fps counter
<freemangordon> if you embed qml (so qgraphicsscene or something like that) in qwidget, then you kill the perf because it has to do readback
<dsc_> yes I do that
<dsc_> but I also tried the other one, QML as application window
<dsc_> the first one is QML inside QtWidgets
<dsc_> first one = 25fps, 2nd one is ~45fps
<freemangordon> I admit I don't know how qml works
<dsc_> so you're saying it readsback
<dsc_> i think thats very likely
<freemangordon> so, the first one does readback
<freemangordon> also, maybe there is something with modesetting driver
<freemangordon> maybe it does not do double-buffering
<dsc_> because QtWidgets is painted via CPU, so if we have a QML scene rendered with the GPU, it will still have a CPU readback
<freemangordon> that kills the performance
<freemangordon> you should do everything on GPU
<freemangordon> keep in mind mali is tiled GPU
<freemangordon> (also)
<dsc_> with Qt6 I can render to an OpenGL texture and do something with that
<dsc_> (i am already very familiar with that offscreen Qt6 stuff)
<dsc_> they introduced a new system called RHI
<dsc_> I am using it for https://godotwebview.com/
<freemangordon> so, glReadPixels is your enemy (as is glFlush())\
<freemangordon> we have qt6 in maemo
<freemangordon> afaik
* freemangordon is back to cooking
<dsc_> suppose renderdoc will show those calls
<dsc_> I should check
<freemangordon> dsc_: rendering to texture does not hlp much if you want CPU to access it
<dsc_> why should the CPU access it?
<freemangordon> it still has to wait fpor rendering to finish so your texture to be ready
<dsc_> hildon can just show a texture or no?
<dsc_> :p
<dsc_> or ehm, QtWidgets will have a QOpenGLWidget
<dsc_> (but then perhaps we'll have the same issue)
<dsc_> anyway, not important now
<dsc_> side-note: QT_QUICK_BACKEND=software also feels faster in the VM
<freemangordon> feels?
<freemangordon> start h-d with G_MESSAGES_DEBUG=all CLUTTER_SHOW_FPS=1
<dsc_> freemangordon: is there a way to drop into a shell with a key combination for the VM
<dsc_> SSH not working anymore, and hildon-desktop partially came up it seems
<dsc_> nvm, Ill mount the qcow2 disk to fix the VM
<dsc_> how do you start hildon-desktop with such env. vars?
<dsc_> ah, /etc/X11/Xsession.post/20hildon-desktop
<dsc_> idk where FPS ends up, I tried searching
<dsc_> or logs in general
<dsc_> ETA systemd :P
<freemangordon> dsc_: from ssh, stop h-d (with dsmetool) and then just start it from there
Pali has joined #maemo-leste
_fantom has joined #maemo-leste
FANTOM has quit [Ping timeout: 244 seconds]
akossh has quit [Ping timeout: 272 seconds]
narodnik2 has joined #maemo-leste
akossh has joined #maemo-leste
<dsc_> pinephone+leste works pretty well must say
<dsc_> im going to install postmarketOS and see what they are up to
<sicelo> you'll need to decide on a UI :-)
<sicelo> forget Plasma ... it's painful on the pinephone
<sicelo> at least that's the general opinion. it does work though
<sicelo> on pp the winner is sxmo, or if you want something more conventional, Phosh
<dsc_> ok, ill try sxmo :)
<sicelo> haha, someone won't touch gtk with a ten-foot pole :p
<dsc_> sicelo: hey, im using Ubuntu on my desktop :)
<sicelo> my problem with sxmo is that it causes nearly 100% constant cpu load on N900. yes N900 is super weak, but it runs Leste without issues. So I guess/assume that whatever is killing the N900 will be killing beefier devices too (just it won't be obvious)
<dsc_> sicelo: but seriously, I kind of skipped this whole Pinephone stuff past 5 years, people are complaining about things etc. but when I try Leste right now, I mean it works pretty good \o/
<dsc_> maybe I am easily impressed, this is why I want to try other distros
<dsc_> to see whats the status there
<sicelo> PP is great device, I think :-)
<dsc_> yes
<sicelo> i guess people are just more used to Android/iOS
<Wizzup> dsc_: don't forget that leste works smooth on the PP where most Oses do not
<Wizzup> sxmo might, but phosh and plasme are pretty slow on it
<sicelo> btw gtk is dropping gles2 support, worsening the PP's woes
<dsc_> yes I read about it
apac has joined #maemo-leste
arno11 has joined #maemo-leste
<Wizzup> sicelo: gtk4 or what?
<Wizzup> sicelo: dpesm
<Wizzup> sicelo: doesn't lima support opengl?
<Wizzup> but yeah gnome folks will do gnome things, they also plan to drop X no :)
<dsc_> no its the hardware, mali 400
<Wizzup> dsc_: are you sure?
<dsc_> this GPU cannot support opengl3 because its missing some features
<dsc_> yes
<Wizzup> I didn't see anyone say opengl3
<Wizzup> I just saw opengl :)
<dsc_> but fear not, there is now https://github.com/kkofler/gtk :P
<Wizzup> pretty sure lima exposes opengl 2.o0
<dsc_> yes it does, but gtk4 went to opengl / es 3.0
<Wizzup> that'd dumb
<Wizzup> that's dumb
<dsc_> they did it though
<dsc_> :p
<dsc_> they killed the pp!
<Wizzup> being dumb hasn't stopped gnome before :D
<dsc_> (and quite a large amount of devices tbh)
<Wizzup> OpenGL version string: 2.1 Mesa 22.3.6
<Wizzup> (PP)
<dsc_> yup
<Wizzup> back in an hour or so
xinomilo has quit [Quit: Leaving]
_fab has quit [Quit: _fab]
Livio has joined #maemo-leste
pere has quit [Ping timeout: 252 seconds]
Livio has quit [Remote host closed the connection]
Livio has joined #maemo-leste
arno11 has quit [Quit: Leaving]
apac has quit [Ping timeout: 268 seconds]
Twig has quit [Remote host closed the connection]
ceene has joined #maemo-leste
vectis_ has quit [Ping timeout: 252 seconds]
Livio has quit [Ping timeout: 264 seconds]
pere has joined #maemo-leste
sfa has quit [Ping timeout: 265 seconds]
akossh has quit [Quit: Leaving.]
pere has quit [Ping timeout: 265 seconds]
Pali has quit [Quit: Pali]