Blikje has quit [Remote host closed the connection]
Blikje has joined #maemo-leste
LjL has quit [Quit: Scappò via con la paura di arrugginire. Il giornale di ieri lo dà morto arrugginito. I becchini ne raccolgono spesso fra la gente che si lascia piovere addosso.]
LjL has joined #maemo-leste
xmn has joined #maemo-leste
<Wizzup>
uvos: I think the droid3 just boots for my on new kernel
<Wizzup>
it has the usual freezes though
Daanct12 has joined #maemo-leste
Daanct12 has quit [Read error: Connection reset by peer]
Daanct12 has joined #maemo-leste
xmn has quit [Ping timeout: 256 seconds]
xmn has joined #maemo-leste
mardy has joined #maemo-leste
joerg has quit [Ping timeout: 276 seconds]
joerg has joined #maemo-leste
Daanct12 has quit [Ping timeout: 244 seconds]
Daaanct12 has joined #maemo-leste
sicelo_ has quit [Ping timeout: 256 seconds]
ceene has joined #maemo-leste
<uvos__>
devel time for the kernel then
<uvos__>
did we complain on linux-omap about the oops allready
<uvos__>
seams to happen on any omap then with the serial ports suspended
sicelo_ has joined #maemo-leste
<tmlind>
uvos__: please do, oops trace and how to reproduce easily would be great to debug this
<tmlind>
i tried to reproduce reboot with serial ports idled but did not see any oopses in logs, i can see reboot occasionally fail sitting in some stuck state possibly in the bootloader
Daaanct12 has quit [Remote host closed the connection]
ceene has quit [Ping timeout: 276 seconds]
mardy has quit [Quit: WeeChat 2.8]
mardy has joined #maemo-leste
pere has quit [Ping timeout: 244 seconds]
xmn has quit [Ping timeout: 240 seconds]
sicelo_ has quit [Ping timeout: 256 seconds]
sicelo_ has joined #maemo-leste
<Wizzup>
uvos__: I also think I see better battery life
<Wizzup>
uvos__: wait, ok, maybe I didn't properly test 5.18 on droid3
pere has joined #maemo-leste
joerg has quit [Remote host closed the connection]
joerg has joined #maemo-leste
joerg has quit [Remote host closed the connection]
<uvos__>
tmlind: ok will do!
joerg has joined #maemo-leste
joerg has quit [Remote host closed the connection]
joerg has joined #maemo-leste
joerg has quit [Remote host closed the connection]
<tmlind>
uvos__: thanks!
ceene has joined #maemo-leste
sicelo_ has quit [Ping timeout: 256 seconds]
sicelo_ has joined #maemo-leste
<Wizzup>
root@devuan-droid3:~# uname -a
<Wizzup>
Linux devuan-droid3 5.18.9 #1 SMP PREEMPT Tue Jul 5 19:41:44 UTC 2022 armv7l GNU/Linux
<Wizzup>
uvos__: works for me, but still loads of freezes/resets
<Wizzup>
[ 13.116180] Hot plug detection already enabled
<Wizzup>
there are also errors for emif_probe and for omap-aes
<Wizzup>
I don't know how relevant those are
<Wizzup>
it looks like the modem status awake/asleep comes from me turning the screen on/off
<uvos__>
we dont use emif
<uvos__>
unless tmlind added it recently
<Wizzup>
probably the mce mapphone module
<uvos__>
im suprized it tires to probe
<Wizzup>
in any case yeah the modem doesn't work yet afaik
<uvos__>
tmlind: comment? ^^
<uvos__>
afaik adding the emif binigns to dts breaks on mapphones for unkown reasons
<uvos__>
so we just leave it alone to how mbm/stock kernel sets it up
<uvos__>
ah d4 also has the omapdrm trace
<Wizzup>
oh yeah, there's also this:
<Wizzup>
[ 9.597930] abe_cm:clk:0060:0: failed to enable
<uvos__>
the drm trace sounds not very serious but we should check if it happens on mainline
<Wizzup>
right
<uvos__>
and report if so
<Wizzup>
I'm not going to look very hard at the d3 atm now, but will/can later
<uvos__>
btw
<uvos__>
actually i imagined seeing the ants with the 5.18
<uvos__>
now that im payin
<Wizzup>
yeah, things look a bit different
<Wizzup>
first time that a kernel upgrade yields free improvements huh ;)
<uvos__>
*attention it dosent seem to happen
joerg has joined #maemo-leste
_inky has joined #maemo-leste
sicelo_ has quit [Ping timeout: 244 seconds]
sicelo_ has joined #maemo-leste
_inky has left #maemo-leste [#maemo-leste]
ceene has quit [Ping timeout: 276 seconds]
<Wizzup>
not sure what others think of this, but I think we have two gpio's in the back of most mapphones
<Wizzup>
I think on the bionic we could use that for a keyboard, perhaps even use gpio-i2c or something
sicelo_ has quit [Ping timeout: 255 seconds]
<Wizzup>
i2c-gpio is what I mean*
sicelo_ has joined #maemo-leste
ceene has joined #maemo-leste
<mglbg[m]>
for the n900, what do i do if i want to turn the screen on when slide is open and off when slide closed? dont mind writing some bash, I just cant find where to look, older forum posts refer to unavailable /sys/devices/platform/slide... kind of locations. any ideas?
<mglbg[m]>
i guess i could get some examples from the keyboard backlight, but the search was unfruitful for now
ceene has quit [Remote host closed the connection]
<buZz>
mglbg[m]: yeah i want similar on d4 aswell :)
<sicelo_>
maybe something in mce config? at least my fremantle n900 works like that. i don't think scripts are the correct solution
<sicelo_>
if uvos__ doesn't have solution for you right away, submit a github issue. for script, you could unlock the device via dbus, and your script could be activated via evdev ... i think the sliders are visible there on both n900 and d4
<mglbg[m]>
how do i reach the mce config? meh this sounds a bit too far for me now sadly as i do not know what you are talking about .. looks like i need to be signing up for github..
xmn has joined #maemo-leste
<sicelo_>
/etc/mce/mce.ini
<mglbg[m]>
thamks, ill check it out
<sicelo_>
so you're both saying sliding keyboard up doesn't unlock the device in the default config? if so, it could be a regression, or our wiki is wrong and needs updating. it currently states "Additionally, if your device has sliding keyboard (like the Nokia_N900 and Motorola_Droid_4), then opening the keyboard will also unlock the device. Closing the keyboard will lock the device again, but only if you
<sicelo_>
have not interacted with the screen since the last slide up."
<sicelo_>
i might be wrong, but i think you should get the desired behavior by setting AutolockWhenSlideOpen to 0 in /etc/mce/mce.ini
uvos__ has quit [Ping timeout: 276 seconds]
<sicelo_>
ah .. yes i don't know mce anymore as it has undergone a lot of changes.
<mglbg[m]>
thanks guys, i tried the UnlockOnSlide in the .d/99- file, does not seem to work yet, trying to figure out if this is due to this setting or some other system changes
<uvos__>
mglbg[m]: that setting is int the lockGeneric section or?
<uvos__>
mglbg[m]: that only applies if you use lock generic
<uvos__>
mglbg[m]: so tklock allways unlocks on slide open
<uvos__>
mglbg[m]: if you want the device to allso allways lock on slide closed you can use lock generic for this
<uvos__>
if for some reason it dosent unlock when you slide it open with the default config that is a bug
<uvos__>
but i kinda doubt it since eveytone would have complained about that
<uvos__>
(and it still works here)
<mglbg[m]>
yeah unlock no problem it is about turning off the sreen when sliding in
<buZz>
yeah 'locking' when closing, thats something maemo 5 did on n900 quite well
<mglbg[m]>
ok, ill check out the tklock
<buZz>
but havent had similar on maemo 7 yet
<bencoh>
buZz: "locking" when closing only happened if no event (keyboard/touchscreen) happened meanwhile
<bencoh>
(i.e slide open, have a quick look at the screen without touching anything, slide close)
<buZz>
indeed, but on maemo7 thats not happening
<bencoh>
(on maemo5 I mean)
<buZz>
maybe it always thinks something happened?
<Wizzup>
uvos__: yeah I think we can move to -devel today
sicelo_ has quit [Ping timeout: 264 seconds]
<bencoh>
buZz: could be yeah
uvos__ has quit [Ping timeout: 276 seconds]
sicelo_ has joined #maemo-leste
uvos has joined #maemo-leste
<uvos>
lock on close is an issue with the button layout on d4
<uvos>
you cant have it lock on close if nothing was pressed and have the volume buttons work
<uvos>
as the volume buttons and the lockslider are on the same input device on d4
<uvos>
so yes that dosent work and is a known issue
<uvos>
allways locking on closed is something lock generic can do
<uvos>
here you can put that into /etc/mce.ini.d if you want this behavior
<sicelo_>
< uvos> lock on close is an issue with the button layout on d4 <-- does it work at least for n900?
<uvos>
no its disabled everywhere to avoid filtering away the volume buttons on d4
<uvos>
i need to rewrite mces intput pipeline to make it work again
<buZz>
ahh
sicelo_ has quit [Ping timeout: 244 seconds]
yanu has quit [Ping timeout: 264 seconds]
pere has joined #maemo-leste
<rafael2k>
hey, can anyone remind me again how to set a volume key to open the vkb?
<rafael2k>
it is in transitions.ini if I remember
<Wizzup>
damnit I have a pulse dial phone at home now
<Wizzup>
but I can't send '#', so I can't dial into work meetings
mardy has quit [Ping timeout: 244 seconds]
<buZz>
-pulse- phone :D
<buZz>
lol, in .bg again Wizzup ? :D
<Wizzup>
nope, amsteradm
<Wizzup>
it has a nice sticker on it with feuerwehr and polizei numbers ;)
sicelo_ has joined #maemo-leste
<buZz>
:D
<rafael2k>
you can just play the tones
<rafael2k>
with an outsiđe speaker
<rafael2k>
coupled with the phone
<Wizzup>
not sure if the grandstream ata will turn the pulse dial into dtmf in the call too
<Wizzup>
I'll have to check
<Wizzup>
anyway offtopic :p
<Wizzup>
but fun
<rafael2k>
941 Hz + 1477 Hz
<rafael2k>
can use csound and maemo, and put the speaker close to the phone
<rafael2k>
pulse is pulse, not DTMF
<rafael2k>
just play the tones from any other device
<rafael2k>
:P
<Wizzup>
oh heh
Daanct12 has joined #maemo-leste
<rafael2k>
I used this in a "locked" (with key) phone in the past... you can just tap the hook to create de pulses - but not to create DTMF... ehehehhe
<Wizzup>
so you're suggesting to generate the dtmf tones on my end?
<rafael2k>
ATDT vs ATDP
<rafael2k>
:P
<Wizzup>
the numbers as dtmf tones?
<rafael2k>
better not to mix I think
<rafael2k>
you can try
<rafael2k>
once the call is established via pulse, you can certainly switch to DTMF later
<rafael2k>
which will be heard by a third party PABX
Danct12 has quit [Ping timeout: 240 seconds]
<Wizzup>
right
<Wizzup>
that's what I mean
<rafael2k>
right, it will work, indeed
<rafael2k>
you can get an acoustic coupler and feel like in the early 80's
<rafael2k>
:P
norayr has left #maemo-leste [Disconnected: Received SIGTERM]
<Wizzup>
heh
<rafael2k>
sorry, this is mid 70's
<rafael2k>
you will also get for free a 1200 baud (software) modem if you wish to
Twig has joined #maemo-leste
Danct12 has joined #maemo-leste
Daanct12 has quit [Ping timeout: 240 seconds]
<Wizzup>
hehe
norayr has joined #maemo-leste
<buZz>
so is 5.18.latest on hold?
<Wizzup>
buZz: no
<Wizzup>
it works in -experimental
<buZz>
ooo
<Wizzup>
I will push to -devel today
<buZz>
sweeeet
<buZz>
i'll port my bermbom mods :P
<mglbg[m]>
<uvos> "http://uvos.xyz/maserati/90-lock..."; <- thanks! this is one step further, the display goes off, but the led starts growing brighter white and the screen pops on again...
<uvos>
mglbg[m]: heh it actually suffers from the same issue as autolock
<uvos>
since the d4 now accepts the slider key as a valid event
<uvos>
closing the slider also wakes it again
<uvos>
so yeah
<uvos>
thats also broken for the same reason the other lock on close is broken
norayr has left #maemo-leste [Error from remote client]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: closed]
<rafael2k>
but sometimes simple interfaces are good too
<rafael2k>
indeed sicelo
<rafael2k>
settings are different, as it should be
<sicelo_>
the adp1653 is the driver on the N900 uvos
<rafael2k>
cho 1 > /sys/class/leds/white\:flash/flash_strobe
<rafael2k>
this is the flash_stobe in the in PP
<rafael2k>
all also available tru V4L
<rafael2k>
the LED framework overlap with V4L framework
<rafael2k>
as far as I can see
<uvos>
right as i said often a device is exposed automaticly in the other framework of you register it with one
<sicelo_>
rafael2k: really don't feel bad. the PP is doing the right thing, to the best of my knowledge. i have followed a little bit of the development around its flash :-)
<uvos>
if the frameworks overlap in feature set
<uvos>
also you can implement a v4l device in terms of a led class driver
<Wizzup>
rafael2k: so for this to be a generic interface there needs to be a way to query what the purpose of LEDs is
norayr has left #maemo-leste [Disconnected: Received SIGTERM]
<Wizzup>
and sysfs doesn't really do that
<Wizzup>
afaik
<uvos>
the point is that just a led class driver
<uvos>
is not sufficant
<Wizzup>
this could just as well be the led on some other part
<sicelo_>
n900 camera has been popping dmesg errors in recent kernels, and i hope to fix that. at least i found reloading the driver makes the errors go away. maybe you can help with getting pics out of it as you seem to know a lot about this stuff
<rafael2k>
I thought Pavel made it work
<rafael2k>
:P
<sicelo_>
yes he did. even took pics (matrix style - green)
<rafael2k>
the made a leeeenghty presentation
<sicelo_>
but he doesn't have time for N900 in general anymore
<rafael2k>
He mentioned in libcamera list it is in his top priority
<sicelo_>
hehe, when? and what?
<rafael2k>
today
<sicelo_>
n900 camera?
* Wizzup
bbl
<rafael2k>
yeap
<rafael2k>
and he says he uses Mobian on the PP, and Maemo in Droid 4 and N900 btw
<rafael2k>
"I'm actually using Leste on Droid4" ...
<sicelo_>
rafael2k: i was completely confused earlier when we were talking about horses ... but now looking at the list i see what you meant :-D
<rafael2k>
ehehehe
<rafael2k>
that iconic image came to my mind... this is why I answered "yes"
<sicelo_>
one person i know would really like to see n900 camera working (and mapphones) is Laurent
<sicelo_>
*with libcamera, that is
mardy has quit [Ping timeout: 276 seconds]
<rafael2k>
cool
<rafael2k>
he understands _a_lot_
mardy has joined #maemo-leste
norayr has joined #maemo-leste
<rafael2k>
libcamera is the place to implement all these ISP pipeline setup madness
mardy has quit [Ping timeout: 276 seconds]
norayr has left #maemo-leste [Disconnected: Received SIGTERM]
norayr has joined #maemo-leste
<sicelo_>
Wizzup: updating droid 4 kernel shortly. how's the stability, i.e. likelihood of unexpected reboots?
<sicelo_>
hmmm, died while updating. nice
<sicelo_>
ok it didn't. just screen went black and wouldn't react to powerkey for a while
<sicelo_>
Wizzup: does this come with your calls hack ootb? or something needed? i have a call to make tomorrow, so i could test with it perhaps
<uvos>
no hacks
<uvos>
very stable so far
<uvos>
not a single reboot in 1week
<sicelo_>
alright
norayr has left #maemo-leste [Error from remote client]
<Wizzup>
sicelo_: no calls hacks
<Wizzup>
like uvos said
<sicelo_>
alright. i'll use earphones then
<uvos>
earphones?
yanu has joined #maemo-leste
uvos has quit [Ping timeout: 240 seconds]
sicelo_ has quit [Ping timeout: 244 seconds]
sunshavi has quit [Ping timeout: 246 seconds]
xray256 has left #maemo-leste [WeeChat 2.3]
norayr has joined #maemo-leste
xmn has quit [Ping timeout: 276 seconds]
sunshavi has joined #maemo-leste
xmn has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: Received SIGTERM]