cockroach has quit [Quit: leaving]
zhxt has joined #maemo-leste
belcher has quit [Ping timeout: 258 seconds]
xmn has quit [Quit: ZZZzzz…]
belcher has joined #maemo-leste
joerg has quit [Ping timeout: 252 seconds]
joerg has joined #maemo-leste
zhxt has quit [Ping timeout: 260 seconds]
mardy has joined #maemo-leste
<freemangordon> n900, gtkperf, with traces removed, 2D slowpath rendering:
<freemangordon> Total time: 62.33
n900 has quit [Quit: WeeChat 2.3]
n900 has joined #maemo-leste
pere has quit [Ping timeout: 260 seconds]
zhxt has joined #maemo-leste
pere has joined #maemo-leste
<Wizzup> freemangordon: sweet
sunshavi has quit [Ping timeout: 258 seconds]
sunshavi has joined #maemo-leste
_inky has quit [Ping timeout: 260 seconds]
inky_ has joined #maemo-leste
inky has quit [Ping timeout: 258 seconds]
Pali has joined #maemo-leste
_inky has joined #maemo-leste
<lel> MerlijnWajer closed a pull request: https://github.com/maemo-leste/leste-config/pull/25 (Various leste-config changes)
<Wizzup> uvos: when we go for drmfb on n900 we might need to revert the changemode directfb maybe
uvos has joined #maemo-leste
<_inky> https://forum.pine64.org/showthread.php?tid=9444 hope leste will work after flushing like that from the internal emmc.
<_inky> you cannot imagine how much i hope pinephone will become usable under maemo. i believe it can, if the gfx issues get fixed. because droid4 is very usable for me.
lexik_ has joined #maemo-leste
lexik has quit [Ping timeout: 264 seconds]
<_inky> and i have two friends that have pinephones, and pinephone is slow under plasma and phosh, but will be very fast under maemo.
Twig has joined #maemo-leste
<uvos> thb i think even if the gfx issues are fixed by disabeling glamor (which is likely) i would not call leste very usable on pp until we improve the quality and functionality of him
<uvos> i honestly cant use the bionic in ernest
<uvos> even though it works slightly better than the d4 generally
<uvos> Wizzup: what changemode for driectfb?
<uvos> Wizzup: i dident add anything
<uvos> besides once ddk1.17 works i intend to drop driectfb...
<Wizzup> aha
<uvos> because charging sdl works fine on kms/drm on ddk1.17
<uvos> what else would you want directfb for?
<Wizzup> fair
<uvos> btw we should activate charge-mode on the deivces
<uvos> atm its not even in devel
<Wizzup> ok
<uvos> it hasend caused me any trouble and mce-battery guard has the unforitonate side effect that if you do manage to get well below the theshold voltage mce will shut the device down just as it boots with usb plugged in
<uvos> without charging mode
<uvos> with charging mode the device will hang around there ofc
<uvos> probubly should add something to charging-sdl that prevents the device from booting to the default runlevel until the battery is at least 3.5V
<Wizzup> do we have a pr to enable it?
<uvos> no
<uvos> and some runlevel
<uvos> and the cmdline on n900
<uvos> (somehow)
<uvos> *and some metapackage
<uvos> cmdline needs softlevel=charge-mode
<uvos> i dont think cmdline on n900 is controled by a package?
<uvos> same problem with pp
<uvos> but pp dosent have battery-guard either
<uvos> both would need testing first
<Wizzup> _inky: pp with keyboard would be nice to support, but fixing lima really isn't our prio atm I think
<Wizzup> also the battery life is kind of a problem for me personally
<uvos> do wie sleep with crust at all atm?
<Wizzup> only if you invoke it manuall
<Wizzup> y
<Wizzup> in any case I don't think hibernate-ram is a way to use a phone
<Wizzup> but yeah
<uvos> yeah its not ideal
<uvos> you could make it suspend to ram for 50 of 60s of a minute or soemthing and have the deamons download new ip messages/emails etc during the 10s
<uvos> wich is how android works on platforms that cant do runtime pm
<uvos> but yeah
<Wizzup> I don't know how you will listen to music that way
<uvos> yeah you would need a concept of wakelocks like android
<Wizzup> right, but then the battery would drain like razy
<Wizzup> my point is mostly I'm not happy with the big power usage
<Wizzup> but yeah it's still a cool device.
<Wizzup> I'm sure we'll get to support it more when we get our other devices usable for daily usage
<uvos> well d4 sleeps exactly never when you play music
<uvos> on leste
<Wizzup> It does for me I'm pretty sure
<uvos> on android it seams to use the m3 cores
<uvos> or something
<Wizzup> I am pretty sure the ret count increases
<uvos> what do you play?
<uvos> 44khz flac?
<Wizzup> opus files
<uvos> ok
<uvos> maybe its my files/codec
<Wizzup> in any case yeah I don't get ~24 hours of music playback time
lexik_ has quit [Ping timeout: 260 seconds]
lexik has joined #maemo-leste
<_inky> can i disable glabor myself or some package has to be rebuilt?
<_inky> glamor*
xmn has joined #maemo-leste
<_inky> > but fixing lima really isn't our prio atm I think
<_inky> Wizzup: what i wonder is if other pinephone communities do some work or request something from lima or mesa, that we can benefit, or we live in a different world because of x11?
<Wizzup> I think we live in a somewhat different world
<Wizzup> I don't think disabling glamor helps with anything
<Wizzup> on the pp
juiceme has joined #maemo-leste
Blikje has quit [Ping timeout: 265 seconds]
<_inky> the pinephone pro's video is different, i guess the same as on pinebook pro. i have a pinebook, so i probably can test maemo, hildon somehow on it.
<_inky> and we can know how it'll work on pinephone pro.
<_inky> i guess i can just write some ARM image to sdcard and boot.
<_inky> hopefully.
<_inky> it's a pity, these gfx problems, because the only lightweight distribution that exists for pinephone is maemo, others are very heavy.
<Wizzup> iirc that has a mali-t, so the driver might work better too
<Wizzup> _inky: we'll get there, we just don't have infinte time
<_inky> i didn't know that time may help, i thought gfx drivers or userspace are very specialized thing, and nobody except the writers can contribute.
<Wizzup> the mali-t driver is developed more actively afaik
<_inky> i guess, it works not bad on my gentoo on pbp, has some issues under my favourite windowmaker, but works much smoother under enlightenment.
<_inky> on x11 without wayland i mean.
<_inky> i don't compile wayland.
<Wizzup> isn't panfrost the driver for mali-t?
<Wizzup> in any case you can try to get people to help fix the things, I just don't think we (core folks) currently can
<Wizzup> we really should focus on other stuff
<Wizzup> there might just be a way we can use it better, and perhaps newer mesa and X will also help
<Wizzup> I didn't bring my pp with me on this trip so I can't help there
<Wizzup> you can contribute by making it easy for the developers to reproduce the bug(s)
xmn has quit [Ping timeout: 264 seconds]
zhxt has quit [Ping timeout: 260 seconds]
uvos has quit [Read error: Connection reset by peer]
uvos has joined #maemo-leste
<sicelo> _inky: maybe see how sxmo handles x11, then check if any of what they do can help leste. Seems sxmo users are happy with what they get out of it
<sicelo> Yeah i like enlightenment. I wanted to try it on n900 with wayland
pere has quit [Ping timeout: 265 seconds]
<_inky> yes i have sxmo in emmc
<_inky> it is very useful.
<_inky> sicelo: i did not know they use x11.
<sicelo> Hehe, I mentioned it the other day but no one noticed. What do you the the X in sxmo means ;-)
<sicelo> s/do you/did you think/
<_inky> oh. great. i didn't know that. (:
<_inky> well xmo works perfectly ok with xorg then.
<_inky> sxmo
<_inky> never noticed any problems. may be they just use more up to date software stack, because they use alpine or manjaro.
<_inky> hmmmm.
<sicelo> So it might give you hints on how to improve stuff for leste support
<_inky> interesting if i can get it compiled on devuan and replace hildon default start with sxmo to check.
_inky has quit [Ping timeout: 258 seconds]
<freemangordon> ok, pvr mesa segfaults :)
<freemangordon> will continue on Sunday, bb
_inky has joined #maemo-leste
pere has joined #maemo-leste
_inky has quit [Ping timeout: 258 seconds]
_inky has joined #maemo-leste
Blikje has joined #maemo-leste
<uvos> i really dislike gtk
<Wizzup> uvos: yeah, also why I'd prefer to go conversations in qt
inky_ has quit [Ping timeout: 252 seconds]
_inky has quit [Ping timeout: 260 seconds]
<uvos> yeah anyhow, almost finished with sphone moudlarsation now.
inky_ has joined #maemo-leste
<uvos> architecturally i borrowed the datapipe concept from mce (altho implementation differs slighty) as an exmple it works like this now when a call comes in:
<uvos> some plugin that has called sphone_comm_add_backend gets a call and creates a CallProperties struct and kicks it down the call_new_pipe pipe
<uvos> optionally some plugin that has registerd a filter on that pipe adds stuff to CallProperties->contact struct with name image etc
<uvos> and it lands in the ui
<uvos> the ui then kicks the call stuct back down a call_accept_pipe when it wants
<uvos> just an example
<uvos> but everything works like this now
<Wizzup> check
_inky has joined #maemo-leste
Twiggy has joined #maemo-leste
Twig has quit [Ping timeout: 258 seconds]
mardy has quit [Quit: WeeChat 2.8]
akossh has joined #maemo-leste
Twiggy has quit [Remote host closed the connection]
xmn has joined #maemo-leste
BenLand100 has quit [Ping timeout: 258 seconds]
BenLand100 has joined #maemo-leste
BenLand100 has joined #maemo-leste
BenLand100 has quit [Changing host]
DPA has quit [Ping timeout: 260 seconds]
vectis has quit [*.net *.split]
peetah has quit [*.net *.split]
tmlind has quit [*.net *.split]
vectis has joined #maemo-leste
peetah has joined #maemo-leste
tmlind has joined #maemo-leste
DPA has joined #maemo-leste
Pali has quit [Ping timeout: 260 seconds]
uvos has quit [Ping timeout: 260 seconds]