<uvos__>
so yeah there are no reasonable places to add bodge wires to get the usb pins elsewhere
<sicelo>
btw no schematics leaked?
dev has left #maemo-leste [Disconnected: closed]
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
<uvos__>
no
rafael2k has joined #maemo-leste
<rafael2k>
uvos__, it was my fault yesterday
<rafael2k>
sphone is working fine
<rafael2k>
it was just a path issue in /etc/ringtones in the package I created. I already fixed it
<rafael2k>
just the "Speaker" button is still not working, but all the rest is working fine and 100% useful!
<uvos__>
ok
akossh has quit [Read error: Connection reset by peer]
norayr has left #maemo-leste [Disconnected: closed]
<rafael2k>
libcamera sample app "cam" now output DNG, which is good as it can be converted easily to any other format
norayr has joined #maemo-leste
norayr has left #maemo-leste [#maemo-leste]
norayr has joined #maemo-leste
<uvos__>
only if all the dng metadata is correct
<uvos__>
otherwise itsostly useless non-interpretable data
<uvos__>
*its mostly
<rafael2k>
the is correct of course... it was quite a work
<rafael2k>
I hope
akossh has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: Replaced by new connection]
norayr has joined #maemo-leste
<buZz>
uvos__: does the 'recent' button on the latest -dev sphone work for you?
<buZz>
also, morning :)
<uvos__>
buZz: no idea, see recent unfortionate accident with my d4
<uvos__>
(i dont have any leste device atm)
<buZz>
ah :(
<buZz>
cant move sim&sd easily?
<uvos__>
that was the only device i have here
<buZz>
ah :(
<buZz>
well, hopefully Wizzup can bring a big pile soonish
<uvos__>
well i also have others, but they are at my place and i wont be there for a while
<buZz>
nobody there that could send one? :P
<uvos__>
maybe
<uvos__>
but it just broke so nothing organized yet
<buZz>
sicelo: they quite damaged that board while removing the shields :D
<buZz>
uvos__: right, ok, just thinking along ;)
<buZz>
i still want to take apart my d4 to try and fix the slides/hinges a bit, they feel kinda sloppy
<uvos__>
i have done that
<uvos__>
its pretty easy
<sicelo>
yes, they don't always do a good job. on their N900 teardown, they tore the ribbon
<uvos__>
you just have to bend the mettal plate on the back of the display inwards
<uvos__>
this just involves removeing the display
<uvos__>
other than fiddeling with the fragile ribbon its not very hard
<buZz>
nice
<buZz>
maybe it would be nice as a video or timelapse
<buZz>
'how to keep your 10yo phone working nicely' and end with 'and now you install maemo leste'
<buZz>
:D
<uvos__>
the d4 board is also fairly hard to unshileld
<uvos__>
with it haveing an absolutly absurd number of chips for a mobile phone
<uvos__>
and the shields being compartmentalzed
<buZz>
hmhm, would need hotair or a hotplate perhaps
<buZz>
or add bismuth solder to the shield joints :P
<buZz>
(to lower melting temp a lot)
<buZz>
i noticed sphone has 'commtest' as backend aswell, is that for trying in virtualbox?
<buZz>
or other vm
akossh has quit [Ping timeout: 272 seconds]
<buZz>
https://youtu.be/Bht-vgRVGNw <-- i was here last saturday, showed loads of people maemo leste, some even had a n900 with maemo5 on it with them :P
<Wizzup>
sicelo: does this require a different kernel module on linux?
<buZz>
some_name_here annoys me :)
<Wizzup>
sicelo: usually just PR against master
<sicelo>
no, i just made only that change, built on device, and it worked. didn't mess with kernel
<sicelo>
actually yes, different module :-)
<sicelo>
but it's a module we already build
<Wizzup>
I mean different module for the linux side (not the leste side)
<sicelo>
ah, pc side, yes too, but again, it's always there
<sicelo>
rndis_host and rndis_wlan (no idea why the wlan gets used)
<Wizzup>
ok, I think it seems simple but we seem to make sure we don't break things
<sicelo>
sure, tyt :-)
Twig has joined #maemo-leste
<sicelo>
maybe there's a way to make cdc ecm work with windows, but at least it's super hard. i didn't get very far, after spending quite some time
<Wizzup>
I think it's a fair chance, I just don't want to lock others out
pere has joined #maemo-leste
<sicelo>
one thing i couldn't figure out is - does CDC ECM work fine on macOS? what about RNDIS? i tried to ask around and couldn't find a clear answer
<sicelo>
i do expect macOS to support both however, like linux
<Wizzup>
let me see if I have it on in my gentoo kerne
<Wizzup>
;)
<sicelo>
cool
<sicelo>
at least i can also say that some android phones present themselves in rndis mode when USB Tethering is selected
<sicelo>
buZz: at least "some_name_here" is understandable. i was taken aback by "The only one.1" :-p
<sicelo>
when i poked around configfs for this issue, and met that name, i wondered if i didn't have some malware, heh
<Wizzup>
Please come up with proper descs for that too
<Wizzup>
if you can
<sicelo>
we can just use what the gadget docs show, i.e.
<sicelo>
s/The\ only\ one.1/c.1/
<sicelo>
s/some_name_here/rndis.usb0/
<sicelo>
otoh, those are fun in some way, that's why i didn't touch them
<sicelo>
(or s/some_name_here/ecm.usb0/ if we don't adopt rndis, of course)
<Wizzup>
I think saying Maemo Leste somehow might make sense, in the description?
uvos has joined #maemo-leste
<sicelo>
yes, i think we have Bar Gadget or similar for now
<Wizzup>
yeah.
<uvos>
so good/bad news on my d4
<uvos>
the 5 usb pins survived, but the ground plane that mechanicly holds the usb connector inplace totaly sheared off
<uvos>
relly the connector is extreamly well fixed to the pcb, the entire bottom surface is soldered to the board as one coninous pad
<uvos>
(thats now gone)
rafael2k has joined #maemo-leste
<buZz>
sicelo: lol yeah, there i go with 3x leste hooked up
<buZz>
uvos: some epoxy?
<uvos>
buZz: might be doable, but the connector itself is totaly demolished/ bent out of shape
<uvos>
so cant try it rn
<Wizzup>
uvos: I can send you some more if you need em
<Wizzup>
uvos: I also ordered 5x droid2's
<Wizzup>
2 white, 3 black
<Wizzup>
so if I manage to get it all home I can send you some of those, too
<uvos>
Wizzup: thats neat :). still i want to recue this one - also the immidate problem is that this is the only leste device i had with me
<uvos>
*rescue
elastic_dog has joined #maemo-leste
elastic_dog is now known as Guest3315
Guest3315 has quit [Killed (silver.libera.chat (Nickname regained by services))]
<uvos>
anyhow i would defently recomend not takeing a seat on the device while its pluged in to usb xD
<sicelo>
Wizzup: the ones that make the most sense to name are product and manufacturer, plus maybe serial number (pmOS sets it to postmarketOS).
Twig has quit [Remote host closed the connection]
<sicelo>
do we have some way to identify what device leste is running on? if so, perhaps that's where product and manufacturer could come from, maybe extending hildon-usb-gadget to accept that as arguments
<uvos>
sicelo: sure
<uvos>
the of name of the device
<sicelo>
where is it stored?
<sicelo>
ah, you mean dts
<uvos>
you can read it from /proc/devicetree or something?
Twig has joined #maemo-leste
<uvos>
cant check right now becasue - you know
<sicelo>
yes i know that one
<Wizzup>
that could work, we don't really have anything like osso productinfo atm
norayr has left #maemo-leste [Disconnected: closed]
norayr has joined #maemo-leste
norayr has left #maemo-leste [Disconnected: timeout during writing]
norayr has joined #maemo-leste
asriel has quit [Quit: Don't drink the water. They put something in it to make you forget.]
asriel has joined #maemo-leste
<buZz>
sicelo: i was thinking maybe we could use some serial per device aswell, maybe /etc/machine-id ?
pere has quit [Ping timeout: 255 seconds]
ceene has quit [Remote host closed the connection]
rafael2k has quit [Ping timeout: 272 seconds]
pere has joined #maemo-leste
mardy has quit [Quit: WeeChat 3.5]
Twig has quit [Ping timeout: 250 seconds]
ikmaak has quit [*.net *.split]
dreamer has quit [*.net *.split]
lel has quit [*.net *.split]
lexik has quit [*.net *.split]
lightbringer has quit [*.net *.split]
panzeroceania_ has quit [*.net *.split]
lightbringer has joined #maemo-leste
dreamer has joined #maemo-leste
lexik has joined #maemo-leste
lel has joined #maemo-leste
lightbringer has quit [Changing host]
lightbringer has joined #maemo-leste
panzeroceania_ has joined #maemo-leste
ikmaak has joined #maemo-leste
<buZz>
it stays so weird ; i press a button on keyb, screen turns on , button doesnt arrive to program (logical) , i press the button again , button doesnt arrive to program (ehhhh) , i press the button AGAIN , FINALLY button arrives at program
<buZz>
i guess somehow xorg doesnt realize we're 'active' ?
<uvos>
i dont use tklock
<uvos>
but freemangordon recently reorder the display depending modules in mce
<uvos>
and i can see that being a consequence of that
<uvos>
since both systemui tklock and mce redundantly implement oneclick mode
<uvos>
i assume this happens in any program
<uvos>
otherwise it could also be a bug in how hildon-desktop assings keyboard focus
<uvos>
this is also known to be buggy
<uvos>
when appications are involved that use x10 methods or do focus stealing
rafael2k has joined #maemo-leste
dev has joined #maemo-leste
dev has left #maemo-leste [#maemo-leste]
dev has joined #maemo-leste
<buZz>
uvos: no this was 'always' like this
<buZz>
at least, as long as i've been using leste :P
<buZz>
uvos: but, it wasnt locked, there was no unlocking, i just pressed a keyboard key
<buZz>
unless thats tklock who turns the screen on then?
<uvos>
no
<uvos>
tklock has a transparant window
<uvos>
that intercepts all key input
<buZz>
which turns the backlight off?
<uvos>
no
<buZz>
hmm
<uvos>
but its there when the backlight is off
<uvos>
or dim
<buZz>
ah, like that
<buZz>
sooooo, sounds like tklock could maybe improve with something like a XTest feature that 'forwards' the keys to something else?
<uvos>
no
<uvos>
tklock just has to go away
<uvos>
it has no purpose
<buZz>
ok but 'i'm not using it' doesnt really help
<buZz>
isnt tklock the slide-lock thing of maemo?
<uvos>
no
<uvos>
thats vtklock
<buZz>
they sound related? :)
<uvos>
not really
<uvos>
name only
<buZz>
Your search - "vtklock" maemo - did not match any documents.
<buZz>
meh
<uvos>
anyhow so i gues whats happening here is: while the display is off mce tells xorg to unbind all input devices, this is nesscary for pm.
akossh has quit [Quit: Leaving.]
<uvos>
you click once and mce registers that and turns on display and also tels x to turn rebind the intput devices
<buZz>
i didnt click a single time ;)
<buZz>
the 'button on keyb' i mentioned was on the keyboard
<uvos>
yes that a click
<uvos>
you click again and now tlock intercepts the keypress
<buZz>
ok :)
<buZz>
cant xorg manage the display on/off ?
<uvos>
because it dident get the first click, because it depends on what order the above happend in, wich depends on the module order in mce and how fast xorg reacts to mces commands
<uvos>
yes and it should
<uvos>
and could
* buZz
tries how this works on n900 (still on leste)
<uvos>
you could have wirtten a xorg module to do the mce lock/display behavior and that would have been way batter
<buZz>
should be the same, right?
<uvos>
but nokia are fools
<buZz>
i'm still quite confused about the role of each nokia application in this whole thing :P
<uvos>
buZz: no so on freemantle
<uvos>
mce uses a custom sysfs interface nokia hacked into the kernel
<buZz>
yeah its leste
<uvos>
to disable the input devices at the kernel level
<uvos>
also the module load order is totaly different
<buZz>
ah, leste-n900 is the same, needs 3x keypress from 'dimmed' to receiving 1 key on xterm
<buZz>
uvos: also a source of confusion for me, how can i trigger battery calibration now?
<buZz>
shouldnt it recalibrate each time after 'battery low' -> 'fully charged' ?
<buZz>
or is there a step 'below' batterylow
<Wizzup>
maybe one of these is a focus loss problem
rafael2k has quit [Ping timeout: 272 seconds]
<tvall>
random question. i have 2 bionics and only 1 spare microsd. could i shove leste in the data partition? would that anger the locked bootloader? will kexecboot find it there?