Danct12 has quit [Remote host closed the connection]
Danct12 has joined #maemo-leste
xes has quit [Remote host closed the connection]
xes has joined #maemo-leste
xes has quit [Remote host closed the connection]
uvos__ has quit [Ping timeout: 252 seconds]
uvos__ has joined #maemo-leste
xes has joined #maemo-leste
xes has quit [Read error: Connection reset by peer]
xes has joined #maemo-leste
xes has quit [Read error: Connection reset by peer]
xes has joined #maemo-leste
xes has quit [Remote host closed the connection]
xes has joined #maemo-leste
joerg has quit [Ping timeout: 246 seconds]
joerg has joined #maemo-leste
macros_ has quit [Ping timeout: 250 seconds]
macros_ has joined #maemo-leste
uvos__ has quit [Ping timeout: 248 seconds]
uvos__ has joined #maemo-leste
xes has quit [Remote host closed the connection]
<freemangordon>
buZz: 144p works fine in chromium, fullscreen as well
<freemangordon>
240p too, but might not fluid at times
mardy has joined #maemo-leste
xes has joined #maemo-leste
rafael2k has joined #maemo-leste
<tmlind>
freemangordon: if you have a chance, maybe comment on the list regarding sony,acx565akm for the old omapfb? imo, we should do minimal fix, then drop the old omapfb stuff unless there's a reason to keep it still?
<tmlind>
and panel-dsi-cm too can go looks lie
<tmlind>
like
<rafael2k>
this 6.0 kernel might be worth trying in the PP, especially in PP 1.1 (Braveheart) as it clearly states it is supported
<rafael2k>
pre-compiled kernels are available here (still in the 5.19, but mostly same patchset: https://xff.cz/kernels/5.19/ )
<freemangordon>
buZz: also, make sure it plays @ 144p
<freemangordon>
so, site must be m.youtube.com
<buZz>
yeah i did
<buZz>
i'll try your plugin first
<freemangordon>
d4 just cannot handle desktop site
<buZz>
its grabbing the m.youtube already
<freemangordon>
hmm, it does not play here as well
<freemangordon>
wtf?
<freemangordon>
maybe they have changed something
<freemangordon>
buZz: oh, I know what happens
<buZz>
oh?
<freemangordon>
sometimes I have to reboot the device, otherwise, for some reason YT playback is choppy
<freemangordon>
for some reason, sometimes after reboot GPU is not in a mood
<buZz>
hmm, weird
<freemangordon>
yep, rebooting atm, lets see
<buZz>
wonder if we could detect that, beside yt playback
<freemangordon>
no idea
<freemangordon>
maybe some difference in regs
<buZz>
i wonder if its better on coldboot vs reboot
<buZz>
or the inverse
<freemangordon>
no pattern I am aware of
<freemangordon>
but, it happens occasionally
<buZz>
sometimes reboot seems to hang for me too, after motorola logo, taking a long time before kexecboot shows
<buZz>
maybe 10x longer than 'normal'
<freemangordon>
yep, after reboot it plays 240p with no issues
<buZz>
gee! , just a warm reboot?
<freemangordon>
power down
<buZz>
so , a cold boot?
<freemangordon>
yes
<freemangordon>
but I am not sure it matters
<freemangordon>
but again, no known pattern
<buZz>
weird :)
<freemangordon>
the only difference I am aware of is that it entered charge mode when it was choppy
<freemangordon>
but I doubt this is the reason
<freemangordon>
also, the whole display was full with renderning artefacts
<buZz>
the ants?
<freemangordon>
legions of them, everywhere :D
<buZz>
was your battery really low when driver initialized?
<freemangordon>
yes
<buZz>
hmmmmm :)
<freemangordon>
I think it is related
<buZz>
yeah my suspicion too
<buZz>
+spelling
<freemangordon>
git it :)
<buZz>
just like how the modem seems to behave weird at <20%
<freemangordon>
*got
<freemangordon>
and my battery is really old
<buZz>
same here\
<freemangordon>
most-probably related
<freemangordon>
will see when replacement battery arrives how it will behave
<buZz>
which battery did you order?
<freemangordon>
the one uvos is using
<freemangordon>
don;t remember the exact model
<buZz>
ah nice, i want one too
<buZz>
does it have the flex lips like d4 uses already?
<freemangordon>
no, I will have to modify
<buZz>
or would it require that flexpcb design he shared
<freemangordon>
will see if I will manage to :)
<buZz>
i was looking that we could maybe expand that flexpcb to have the connections for a thermistor too
<buZz>
and maybe make it slightly more universal
<freemangordon>
I will try to plant the whole circuitry from the old battery
<buZz>
just put the thermistor on that flexpcb
<buZz>
ah yeah , that works too
<buZz>
i'm still hunting for a new produced HV lipo that fits the case
<freemangordon>
tmlind: TBH, I don;t feel experienced enough to comment - neither do I fully understand what the issue dmitry is fixing is about, nor the follow-up discussion
<buZz>
dont pi's normally have a seperate partition with the kernel?
<norayr>
also yewtu.be, i guess this was the domain, is an invidious instance, and it has very leightweight ui, even for a computer
<norayr>
i often use it to decrease the load of the machine
<norayr>
but maybe it doesnt have 144p
<Wizzup>
freemangordon: where did you put iphbd-dkms ?
<Wizzup>
freemangordon: the raspi can't find it
<Wizzup>
it's not in the droid4 component is it?
<Wizzup>
doesn't look like it
<Wizzup>
ah nvm, it's complaining about linux headers
<Wizzup>
unsurprisingly..
<buZz>
norayr: i'd like to record using actual youtube in the background though
<buZz>
as google now -charges money- for that luxury
<buZz>
(as youtube premium, one of the features is 'background playback')
elastic_dog has quit [Ping timeout: 250 seconds]
elastic_dog has joined #maemo-leste
uvos__ has quit [Ping timeout: 268 seconds]
pere has quit [Ping timeout: 246 seconds]
<Wizzup>
apparnetly linux-headers-arm64 does not provide linux-headers? eh
<buZz>
might be the issue i saw earlier? where our kernels dont build source packages
<buZz>
imho -headers is still source
<Wizzup>
no, seems very unrelated :D
<buZz>
hehe ok
<tmlind>
freemangordon: i replied what i think is going on with the panels, maybe take a look and comment if there's any need for the old omapbf drivers in question
<tmlind>
omapfb panel drivers i mean
<buZz>
tmlind: do you have any idea if the omap gpu driver could support .icc profiles for color correction?
<buZz>
-could
<tmlind>
buZz: no idea whatsoever
<buZz>
alright :) i'll try soon
uvos__ has joined #maemo-leste
<uvos__>
buZz: the hang at the motorola logo
<buZz>
-after- the logo
<uvos__>
right also after
<buZz>
screen is black then
<uvos__>
(ie at black)
<buZz>
yeah
<uvos__>
is some bug in the stock kernel caused by the uart module thats loaded by the intercept
<uvos__>
its related to the modem
<buZz>
hmmm
<uvos__>
if the modem is busy and uses the uart the kernel hangs
<buZz>
so maybe that kexecboot kernel needs some 'ignore uarts' flag ?
<uvos__>
no
<buZz>
oh ok
<uvos__>
so the problem is that the kexec module loads a hacky uart module
<uvos__>
s/loads/depends
<buZz>
what would that need a uart for?
<uvos__>
this was done by the linageos people because there is no way to get debug output at all
<buZz>
ah
<uvos__>
while writeing the kexec module
<uvos__>
but its buggy somehow
<buZz>
but then still kinda sounds like we dont need uarts there?
<uvos__>
if the modem uses its uarts while the hacky uart module is active
<uvos__>
stock kernel crashes
<uvos__>
i "fixed" this on my device
PureTryOut[m] has quit [Quit: Bridge terminating on SIGTERM]
<uvos__>
by adding a 10 sec delay
n00mann[m] has quit [Quit: Bridge terminating on SIGTERM]
MartijnBraam[m] has quit [Quit: Bridge terminating on SIGTERM]
humpelstilzchen[ has quit [Quit: Bridge terminating on SIGTERM]
jedertheythem[m] has quit [Quit: Bridge terminating on SIGTERM]
mighty17[m] has quit [Quit: Bridge terminating on SIGTERM]
tvall has quit [Quit: Bridge terminating on SIGTERM]
<uvos__>
this ensures the modem has setteled more
<uvos__>
and the crash never happens on my device
<uvos__>
but its not really a fix
<uvos__>
fixing this problem is hard beacuse its in the module you need to get any output at all
<buZz>
cant we just remove that lineageos change then?
<uvos__>
no
<uvos__>
its required to kexec
<buZz>
aw
<uvos__>
you could remove all the debug prints in the kexec module
<uvos__>
and then not use the hacky uart module
<buZz>
yeah that was my suggestion
<uvos__>
but then you have no debug output during kexec
<buZz>
remove the dependancy
<uvos__>
so thats not great either
<buZz>
i guess, but when was last time you debugged kexec?
<uvos__>
well right now
<uvos__>
xD
<buZz>
:P
humpelstilzchen[ has joined #maemo-leste
<uvos__>
buZz: as for if omapdrm could do color transformations
<uvos__>
shure you could do it on a pvr shader no problem
MartijnBraam[m] has joined #maemo-leste
<uvos__>
thats how modesetting works
PureTryOut[m] has joined #maemo-leste
mighty17[m] has joined #maemo-leste
jedertheythem[m] has joined #maemo-leste
<buZz>
uvos__: no problem, as in no penalty in speed?
n00mann[m] has joined #maemo-leste
<uvos__>
well not zero
tvall has joined #maemo-leste
<uvos__>
but low
<buZz>
sounds good
<norayr>
people, i want to get linux-image-omap kernel sources, added deb-src
<norayr>
copied our maemo lines in sources.list, but changed deb to deb-src
<norayr>
apt-get update, apt-get source linux-image-omap doesn't get me the source.
<norayr>
i would like to get the source, change a couple of things in light meter driver source, my friend believes there is a bug there.
<norayr>
and metered light differs dramatically from other devices.
<buZz>
yeah there's no source package for the kernels i think :(
<buZz>
wish we did
pere has joined #maemo-leste
<uvos__>
norayr: just grab it off git
<uvos__>
since we have quite a few devices that are stuck with gprs/edge in most places now
<uvos>
but thats still a bug, the gconf key should not have moved in the transition to mce-rtconf, gesttings comapt work, but it probubly changed its name slightly causing this bug