<humanbeta>
bug report: With Pinephone volume settings get lost in restart, after restart volume always in maximum.
<buZz>
used to be the same on droid4 , reboot always reset the volumes to whatever was default
<humanbeta>
so it does not read saved volume setting..or does it even save?
<buZz>
i believe it wasnt saving them at the time, not sure if thats implemented currently
<buZz>
really should dig up my d4 and retry :)
<humanbeta>
Maemo 5 with N900 saves and it have even different volume setting for phone calls.
<humanbeta>
so that make me think feature request: add volume slider to sphone for save earpiece volume.
<humanbeta>
with Maemo 5 I used volume buttons during call to set earpiece volume and it saved it automatically.
<buZz>
i dont think it's sphone's role to do so, but just normal OS
<humanbeta>
if OS saves volume settings for each apps then it is OS.
<buZz>
its not a app volume, voice volume is a seperate mixer setting, see 'alsamixer' or 'pavucontrol' output
<buZz>
the audio path of calls is a seperate hw path for audio
<Wizzup>
I think the status area saves and should restore
<Wizzup>
or maybe it's pulse
<humanbeta>
but I think phone call volume in phones are special situation. Maybe best would be save call volume settings in addressbook so you can set it for best for every caller.
<buZz>
humanbeta: either way, the mixer is in alsamixer/pavucontrol for you to change ;)
<buZz>
you could likely force it to a setting in /etc/rc.local with some command i guess
<buZz>
i havent seen any phone saving 'call volume per number' :) but that would be a fun feature yeah
<humanbeta>
Maemo Leste should have something that any another phone OS does not have.
<humanbeta>
ok..it has already something, but..
<humanbeta>
something that every user understand.
<humanbeta>
but first things first, volume settings have to work during call.
<buZz>
they do, open alsamixer ;)
<buZz>
or pavucontrl
<buZz>
control*
<humanbeta>
yes I have pavu control, but how to make shortcut to desktop, now I have to go debian-folder and start it..it is not easy when you speak in phone.
<humanbeta>
if volume buttons are not possible to do that how about some keyboard buttons?
<humanbeta>
btw..it would be nice write SIM–pin code (in start up) with keyboard too (you can do that with PostMarketOS).
akossh has quit [Ping timeout: 255 seconds]
xmn has joined #maemo-leste
<humanbeta>
btw..does Maemo use both GPU cores and acceleration of Pinephone in programs in Debian folder?...text rendering has someting badly wrong when testing with Hardinfo or even simple with UXTerm.
<humanbeta>
badly wrong when speaking speed.
<Wizzup>
what do you mean 'badly wrong' ?
<humanbeta>
very slow speed in text rendering.
<Wizzup>
is it better in portrait mode?
<Wizzup>
I think there is still some slowdown in landscape mode due to everything needing to be rotated
<humanbeta>
is hardware rotate only in closed source Mali drivers?
<Wizzup>
I don't think it has something to do with the closed source drivers, but rather glamor
<Wizzup>
I don't have more info/details, others might
Daanct12 has quit [Quit: WeeChat 4.1.1]
<buZz>
imho, pinephone's GPU speed was always a bit 'meh'
<buZz>
compared to droid4 or n900
<humanbeta>
but anyway X Terminal what comes with Maemo Leste has much faster text rendering than UXTerm or Xterm in Debian folder.
<humanbeta>
they had come from default repository.
<humanbeta>
buZZ: I afraid that open source Mali drivers, Lima drivers, does not use full potentional of GPU. And if Maemo does not use full potentional of those drivers..it would be problem. I remember that problem with OQO handhelds..they had quite good Silicon Motion Lynx3D+ GPU, but nobody ever made good accelerated Linux drivers although Silicon Motion
<humanbeta>
gave all info.
<buZz>
humanbeta: from all i saw, the pinephone just has a A64 soc with a pretty old/basic mali version
<buZz>
plus a -way- too high resolution display for that gpu
<buZz>
also; mali is just the -3D- gpu
<buZz>
not the 2D one
<Wizzup>
humanbeta: the lima drivers are very unlikely the problem
<Wizzup>
did you try it in portrait like I asked?
<humanbeta>
Wizzup: some how I did not get UXterm and Xterm to start to portrait...X Terminal of Maemo rotate well..it was not slow in first place.
<humanbeta>
buZz: Actually AllWinner has dual core Mali version with nice dual alpha layer 2D rotate and zoom mixing add on, but it might be hard to use in normal X11 use.
pere has quit [Ping timeout: 255 seconds]
<buZz>
humanbeta: i know the mali400, its in many socs
<humanbeta>
do you know can it speed up with 16 bit per pixel mode? Actually how many real colors Pinephone LCD can show?
<freemangordon>
humanbeta: bad performance in landscape mode is because modesetting/glamor rotate via SW
<freemangordon>
this has nothing to do with maemo
<freemangordon>
or GPU being slow
<freemangordon>
you can compare dragging desktop views landscape vs portrait
<freemangordon>
maybe open a bug against modesetting driver
uvos__ has joined #maemo-leste
<freemangordon>
also, unfortunately 16bpp is a nogo
<uvos__>
true but i mean the pinephones gpu is still pretty slow, its fillrate is bearly faster than the sgx in d4 and it pushes way more pixels
<freemangordon>
lots of 'modern' programs/frameworks assume 24bpp
<freemangordon>
uvos__: right, but it is fast enough to do 60fps in portrait vs 15fps in landscape, because of SW rotation
<uvos__>
resotring volumes is the resposablility of pulse
<uvos__>
and it works fine on d4
<uvos__>
should work on pp too
<uvos__>
the issue on d4 previously was that one of the mixers had an invalid name
<humanbeta>
and nobody tried to use of hardware rotate in start up to change coordinates (of course portrait would be then slower)
<uvos__>
causeing the saveing to error out
<uvos__>
humanbeta: ?
<humanbeta>
uvos: has anybody tried use hardware rotate of AllWinner?
<uvos__>
the way rotation should work in glamor is that the randr extentions sets a transformation matrix on every x surface and then glamor renders every surface on its side via ogl, dosent work on gles however
<Wizzup>
weren't a lot of patches submitted for glamor gles a few months ago?
<freemangordon>
humanbeta: it does not seem that modesetting supports HW rotate :(
<freemangordon>
unless that has been fixed recently
<freemangordon>
Wizzup: yeah, I gess we shall upgrade xorg at some point
<freemangordon>
*guess
<freemangordon>
uvos__: glamor on lime should use GL, not GLES
<freemangordon>
*lima
<maxwelld>
m commandline.
<maxwelld>
can someone who built qwebbrowser patch it also in a way that it would open the link it gets as a commandline argument? when clicking a link in somewhere, lets say this chat, it opens qtwebbrowser for me (dont remember if i edited something for that by hand or just made sure this is the last installed browser) but when opened it just opens blank page. i guess it has no code to open a link it gets fro
humanbeta has quit [Quit: Client closed]
ceene has quit [Ping timeout: 260 seconds]
brabo has quit [Remote host closed the connection]
fab_ has joined #maemo-leste
uvos__ has quit [Ping timeout: 240 seconds]
uvos__ has joined #maemo-leste
akossh has joined #maemo-leste
arno11 has joined #maemo-leste
uvos__ has quit [Ping timeout: 252 seconds]
uvos__ has joined #maemo-leste
uvos__ has quit [Ping timeout: 264 seconds]
slep has joined #maemo-leste
uvos__ has joined #maemo-leste
pere has joined #maemo-leste
uvos__ has quit [Ping timeout: 260 seconds]
arno11 has left #maemo-leste [#maemo-leste]
pere has quit [Ping timeout: 268 seconds]
sch has quit [Ping timeout: 276 seconds]
Incredia_ has joined #maemo-leste
dos1 has joined #maemo-leste
dos has quit [Ping timeout: 252 seconds]
lel has quit [Ping timeout: 252 seconds]
Incredia has quit [Ping timeout: 252 seconds]
dos1 is now known as dos
danielinux has quit [Ping timeout: 252 seconds]
lel has joined #maemo-leste
danielinux has joined #maemo-leste
<buZz>
maxwelld: alas qtwebbrowser is just a sdk example, not really a full browser :(
<maxwelld>
yeah i know... i guess it is possible to modify it to use argc/argv and pass it to the rendering engine by default.
<buZz>
sure, have at it :D
<buZz>
quite sure there's nothing changed to the upstream sdk example
<dsc_>
i am working on improving jib a bit, ill make sure to handle that use-case
<dsc_>
its considered alpha still, needs UX improvements
<dsc_>
but you can try it out
<maxwelld>
isn't it on repos?
<maxwelld>
is there a repo i can add? how does it work on d4?
<Wizzup>
it's in extras, but I think dsc didn't yet add a X-Maemo... entry and a desktop ico
<Wizzup>
n
<buZz>
thats not needed when you dont run maemo ;)
<maxwelld>
good it is in extras.
<maxwelld>
Wizzup, i am trying to build pango, libadwaita, gtk4 to build latest dino, since this dino has lots of bugs.
<maxwelld>
if i succeed i'll ask for repos, hope you are ok with it.
<Wizzup>
I am not sure if gtk4 apps will look any good currently
<maxwelld>
you cannot imagine how buggy this dino is.
<Wizzup>
I can I think, I use it daily on my laptop
<Wizzup>
I bet it's very power hungry too
<maxwelld>
i actually use d4, so i need communication. everybody around uses omemo, otherwise i would be fine with pidgin.
<maxwelld>
yes, it is very power hungry. both old version and new version.
<maxwelld>
i carry powerbank with me, my battery is also not in good shape.
<Wizzup>
we have an open funding goal to add omemo to tp
<Wizzup>
in case anyone is interested
<maxwelld>
i don't think i am the best person for that.
pere has joined #maemo-leste
<Wizzup>
freemangordon: I wonder if we maybe want to run tracker only when phones are connected to external power
uvos__ has joined #maemo-leste
Juest has quit [Read error: Connection reset by peer]
fab_ has quit [Quit: fab_]
<freemangordon>
Wizzup: why?
<Wizzup>
because it drains battery in these semi corrupt states
<freemangordon>
isn't it better to just fix the issue?
<uvos__>
sure
<uvos__>
but i think at the very least it should be removed from the metapackages until it works
<freemangordon>
it is in -devel
<uvos__>
even in -devel
<freemangordon>
and -devel is meant to break your devce
<freemangordon>
*device
<uvos__>
havin pm broken in devel for long lengths of time has the issue of masking subsiquent issues intrduced
<uvos__>
that can be quite hard to find
<uvos__>
so its not great
<uvos__>
even in devel
<freemangordon>
tracker seems to have issue that is easily reproducible on Wizzup's device
<uvos__>
it happens on my device too
<freemangordon>
ok, then please, either attach gdb or provide logs
<freemangordon>
disabling tracker will not help to move ahead
<uvos__>
its not so easy to repduce sometimes it just gets into states where it uses to mutch cpu
<uvos__>
but its qute random
<freemangordon>
I am sure that high cpu usage is because it crashes
<uvos__>
it dosent crash
<freemangordon>
how do you know?
<uvos__>
pid dosent change
<freemangordon>
I think on Wizzup's device it crashes
<freemangordon>
otherwise it does not affect battery
<freemangordon>
at least here
<uvos__>
powertop lists it as a lot of wakeups/S
<freemangordon>
tracker wakes-up every 30 seconds
<uvos__>
causeing the device to use ~400mw
<uvos__>
but its not wedged or anything
<freemangordon>
BTW, when we you 'tracker', what exactly do you mean
<freemangordon>
because there are couple of processes involved
<freemangordon>
tracker-miner, tracker-fs, etc
<freemangordon>
*when you say
<uvos__>
have to check witch process it is
<uvos__>
its allways the same one
<freemangordon>
ok, that might be the one starting the other, the other crashes and 'the one' restarts the other, etc
<freemangordon>
thus high CPU usage
<freemangordon>
do you have any idea how to repro?
<freemangordon>
did you do tracker reset perhaps?
Juesto has joined #maemo-leste
arno11 has joined #maemo-leste
Juesto is now known as Juest
* freemangordon
copies 7GiB of music to his d4
uvos__ has quit [Ping timeout: 252 seconds]
uvos__ has joined #maemo-leste
uvos__ has quit [Client Quit]
uvos__ has joined #maemo-leste
<dsc_>
all CC0 licensed
arno11 has left #maemo-leste [#maemo-leste]
<Wizzup>
freemangordon: agree trying to fix it is better
<freemangordon>
Wizzup: you can enable logs
<freemangordon>
see TRACKER_USE_LOG_FILES
<freemangordon>
and also "tracker daemon --set-log-verbosity"
<Wizzup>
ok
<Wizzup>
will do (later tonight)
<freemangordon>
maybe there are more logs
<freemangordon>
but loets start with those
akossh has quit [Ping timeout: 245 seconds]
akossh has joined #maemo-leste
akossh has quit [Quit: Leaving.]
uvos__ has quit [Ping timeout: 252 seconds]
<Wizzup>
freemangordon: is there a place to set TRACKER_USE_LOG_FILES ?
<Wizzup>
23:23 < freemangordon> see TRACKER_USE_LOG_FILES
<Wizzup>
so I need to set this in /etc/profile.d ?
<Wizzup>
freemangordon: btw, I think wlan fails to connect frequently from UI because while scan is going, it shows networks, user selects, then we connect, but then when we start the next scan we clear all networks
<Wizzup>
I think the idea is that it doesn't remove the network we're trying to connect to, but I don't think that happens in practice