| Wizzup | uvos: decided to get a sigma key, let's see if it arrives on time | 00:55 |
|---|---|---|
| Wizzup | usbip should work, so that's cool at least | 00:55 |
| parazyd | Wizzup, freemangordon: The newpid issue is something happening on arm but I haven't had time to investigate it well enough. | 07:14 |
| freemangordon | parazyd: ok, but it prevents new glib from entering the repos | 07:31 |
| freemangordon | what about disabling ADT temporarily? | 07:32 |
| freemangordon | just to build the package? | 07:32 |
| parazyd | What I usually did is remove/rename the tests directory in the repo. | 07:32 |
| freemangordon | shall I do that for glib and retry? | 07:34 |
| freemangordon | Also, isn't it better to spend some CPU cycles trying to find why the issue? | 07:35 |
| parazyd | AIUI it's a kernel issue and I've no time to dig into that at the moment. It's also not easy to reproduce by hand. | 07:36 |
| parazyd | So yeah, temporarily do that for glib, and at some point later we can figure it out. | 07:36 |
| freemangordon | parazyd: SIGBUS doesn;t look like kernel issue to me | 07:36 |
| freemangordon | but ok, I'll rename test directory | 07:37 |
| parazyd | I'm pretty sure it's kernel related, because we had the same issue before on the same arm64 machines that Wizzup and I had, and they were the same rootfs. | 07:38 |
| freemangordon | ok | 07:38 |
| parazyd | Only difference was the kernel. And because of this it worked on one device, but not on the other. | 07:38 |
| parazyd | Didn't manage to trace the exact setting. | 07:38 |
| freemangordon | renaming tests/control should be enough, right? | 07:38 |
| parazyd | I think the entire tests directory is safer. | 07:39 |
| freemangordon | ok | 07:39 |
| Wizzup | parazyd: so I tried newpid on the host raspi and it worked fine | 10:06 |
| Wizzup | I would still recommend building glib on the pinephone just to check | 10:27 |
| Wizzup | uvos: so I think sigmakey also provides access to some customer only firmware download place | 10:33 |
| Wizzup | uvos: if we're really lucky we might find the firmware you've been looking for there | 10:33 |
| Wizzup | https://sigmakey.com/en/supportedfeatures/help?brand_id=3&phone_id=1765 | 10:36 |
| dgamer69 | is this devuan mobile? | 18:18 |
| Wizzup | dgamer69: hi | 18:22 |
| Wizzup | this is maemo 5 (a mobile os that has existed since ~2010 or so), built on top of devuan | 18:23 |
| dgamer69 | hi | 18:23 |
| dgamer69 | that's really cool | 18:23 |
| Wizzup | how did you find us if I may ask | 18:24 |
| dgamer69 | I asked in the devuan irc | 18:25 |
| Wizzup | ah, cool :p | 18:25 |
| dgamer69 | yeah! I might try nd install this on my linux phone, when it eventually ships | 18:26 |
| Wizzup | which one is that? | 18:26 |
| dgamer69 | the f(x)tec pro 1 x | 18:26 |
| dgamer69 | idk if it will work though | 18:26 |
| Wizzup | oh, cool. parazyd has mine and was going to look at a port | 18:26 |
| Wizzup | we do't have a port yet | 18:26 |
| Wizzup | don't* | 18:26 |
| dgamer69 | ooooh | 18:27 |
| dgamer69 | but there might be something in the works? | 18:27 |
| Wizzup | just to set expectations, we support a few devices atm and are working on making the os usable as every day driver on those | 18:27 |
| Wizzup | until we hit that we might not spend -too- much time on porting | 18:27 |
| dgamer69 | gotcha | 18:27 |
| Wizzup | we'd be happy to help you try, though ;) | 18:28 |
| dgamer69 | what kind of mobile desktop enviroment deos it use | 18:29 |
| dgamer69 | I saw something that looked kinda funny on the screenshots | 18:29 |
| dgamer69 | oh and I could help report bugs | 18:30 |
| Wizzup | dgamer69: maemo is based on hildon | 18:34 |
| Wizzup | or uses hildon, really | 18:34 |
| dgamer69 | what's hildon | 18:34 |
| Wizzup | https://en.wikipedia.org/wiki/Hildon | 18:34 |
| dgamer69 | that looks really dated | 18:34 |
| dgamer69 | it looks like ios 5 | 18:35 |
| dgamer69 | is it a good user experience? | 18:35 |
| freemangordon | well, it looks like hildon :) | 18:35 |
| Wizzup | we think so | 18:35 |
| Wizzup | it's not like android/os | 18:35 |
| Wizzup | it's not like android/ios | 18:35 |
| dgamer69 | okay | 18:35 |
| Wizzup | funny that the hildon page actually doesn't have a proper maemo5 hildon screenshot | 18:35 |
| dgamer69 | well, I'm interested to try it at least | 18:36 |
| freemangordon | Wizzup: it used to have | 18:36 |
| Wizzup | well now it shows pmos :p | 18:36 |
| freemangordon | dgamer69: this https://en.wikipedia.org/wiki/Maemo | 18:36 |
| freemangordon | dgamer69: or https://maemo-leste.github.io/maemo-leste-fourteenth-update-july-august-september-october-november-december-2020.html (and older) | 18:38 |
| Wizzup | right, the news post :) | 18:41 |
| freemangordon | mhm | 18:41 |
| freemangordon | Wizzup: I had power outage again, so, what has happened with glib? | 18:41 |
| Wizzup | freemangordon: build passed, -repos did not because of udeb stuff | 18:46 |
| Wizzup | uvos: got the compass app somewhere? | 18:46 |
| freemangordon | oh, maybe I should have removed udeb stuff from debian/control too | 18:48 |
| Wizzup | freemangordon: probably | 18:51 |
| _uvos_ | hi | 19:30 |
| _uvos_ | so redgarding sphone sms | 19:31 |
| _uvos_ | im fine with either improving it and adding other protocolls or replacing it with another app | 19:31 |
| _uvos_ | if this other app becomes maemo specific i would like to keep the sms subsystem at least in its current state so that sphone on plain debain etc remains with sms support of some kind | 19:33 |
| _uvos_ | but we could just add a cmd line switch to sphone that disables rining on sms and remove the desktop file from the leste package | 19:33 |
| Wizzup | _uvos_: so I'm planning to make a separate program for sms/conversations that uses tp, so disabling sms in sphone could work | 19:38 |
| Wizzup | regarding it being maemo specific or not, I don't think it has to be, but some of it might be, but we could maybe make it possible to disable | 19:39 |
| Wizzup | I'm aiming for telepathy though, not ofono | 19:39 |
| Wizzup | baw | 19:39 |
| Wizzup | also, now that I found out that just running some simple telepathy-python program keeps telepathy-ring alive, I should see if that helps with audio routing on n900 (since then tp will be avail) | 19:39 |
| Wizzup | _uvos_: I replied wrt sms, can you check logs | 19:40 |
| _uvos_ | and no fremangordon i dont like the interdependance | 19:41 |
| Wizzup | catching up with the logs I see :) | 19:41 |
| _uvos_ | Wizzup ok id like to keep something that works on plain ofono | 19:41 |
| _uvos_ | but yeah adding disableing is no issue | 19:42 |
| _uvos_ | wrt working on sphone | 19:42 |
| _uvos_ | sure if you like | 19:42 |
| _uvos_ | my next task would be to look into moduloarizing it a bit | 19:42 |
| _uvos_ | but rn i am working on removing gconf interfaces from stuff that talks to mce | 19:43 |
| _uvos_ | or rather gconf interface usage | 19:43 |
| Wizzup | what interfaces are that? | 19:44 |
| Wizzup | btw, does your bionic still boot with latest kernel | 19:44 |
| _uvos_ | 5.15? no idea the bionic i only use with leste | 19:44 |
| Wizzup | I mean latest leste-devel kernel | 19:45 |
| _uvos_ | i think so | 19:45 |
| Wizzup | I think whatever broke my d3 also broke my bionic | 19:45 |
| _uvos_ | ill try when i get home | 19:45 |
| Wizzup | hmm let me check again | 19:45 |
| _uvos_ | accutally i think i run my own branch on it | 19:46 |
| _uvos_ | so maybe leste kern is broken | 19:46 |
| Wizzup | _uvos_: ok, also I was wondering about the compass app, got a repo somewhere? | 19:47 |
| Wizzup | and finally, I ordered the sigma key | 19:48 |
| _uvos_ | wrt mce interfaces https://github.com/maemo-leste/mce/blob/master/config/rtconf.ini | 19:48 |
| Wizzup | I hope to get it this week | 19:48 |
| _uvos_ | those | 19:48 |
| _uvos_ | Wizzup no but i can post it to git | 19:48 |
| Wizzup | do those get used by other applications? | 19:48 |
| _uvos_ | yes | 19:48 |
| _uvos_ | most anyhow | 19:49 |
| _uvos_ | nothing uses als_diables | 19:49 |
| _uvos_ | *disabled | 19:49 |
| _uvos_ | the incoveniant thing with gconf genneraly on maemo is that they used it as ipc as well as config | 19:50 |
| Wizzup | gconf as ipc is used in quite some places I think | 19:51 |
| _uvos_ | yeah | 19:51 |
| Wizzup | same is true for many status applets | 19:51 |
| _uvos_ | so now mce has dbus getter and setter methods for all of these | 19:51 |
| Wizzup | ok, but what about our other apps? | 19:51 |
| _uvos_ | and im slowly replacing it | 19:51 |
| Wizzup | also, doesn't it make sense to keep this in gconf? | 19:51 |
| _uvos_ | in other apps | 19:51 |
| Wizzup | it sounds sane to me | 19:51 |
| _uvos_ | id like all external interfaces to be dbus only | 19:52 |
| _uvos_ | config store then can be perfomed by gconf | 19:52 |
| Wizzup | those are not stateful, so you cannot change the values when mce is not running | 19:52 |
| Wizzup | uh so it would still be gconf backed but it would ignore changes? | 19:52 |
| Wizzup | (made directly to gconf) | 19:52 |
| _uvos_ | no | 19:52 |
| _uvos_ | so there is a slectable backend | 19:53 |
| _uvos_ | gconf/ini/or gsettings | 19:53 |
| _uvos_ | chaning the key there updates the value | 19:53 |
| _uvos_ | and there are dbus methods | 19:53 |
| Wizzup | ah, ok, so for maemo things wouldn't necessarily change | 19:53 |
| _uvos_ | well yes | 19:54 |
| _uvos_ | becuase i will be dropping the gconf backend | 19:54 |
| Wizzup | not for the maemo build I hope | 19:54 |
| _uvos_ | and porting the applets to dbus | 19:54 |
| _uvos_ | sure ofc | 19:54 |
| _uvos_ | gconf needs to go | 19:54 |
| Wizzup | we need to migrate to gsettings when we move to the next debian iiuc | 19:54 |
| _uvos_ | right but for mce (as its allways running and system global) dbus makes more sense | 19:55 |
| Wizzup | ok, but I don' | 19:55 |
| Wizzup | 't think it makes sense to break the interface just because, but uw, we'll see | 19:55 |
| Wizzup | s/uw/uh/ | 19:55 |
| _uvos_ | its not just because | 19:56 |
| dgamer69 | I am back | 19:56 |
| Wizzup | dgamer69: 18:36 < freemangordon> dgamer69: this https://en.wikipedia.org/wiki/Maemo | 19:57 |
| Wizzup | 18:38 < freemangordon> dgamer69: or https://maemo-leste.github.io/maemo-leste-fourteenth-update-july-august-september-october-november-december-2020.html (and older) | 19:57 |
| Wizzup | _uvos_: so on my bionic: | 19:58 |
| Wizzup | gzip: invalid magic | 19:58 |
| Wizzup | Could not uncompress initrd.gz | 19:58 |
| Wizzup | rmmod: can't unload module 'board_mapphone_emu_uart': No such file or directory | 19:58 |
| Wizzup | [...] | 19:58 |
| Wizzup | [ 25.625549] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 ]--- | 19:58 |
| _uvos__ | porting to gesettings is equvalent effort | 19:58 |
| Wizzup | sh: exec: line 1: /init: not found | 19:58 |
| Wizzup | hmm let me dig in some more | 19:58 |
| _uvos__ | porting to dbus removes a dependancy on gome tech | 19:59 |
| _uvos__ | that tends to be unstable over time | 19:59 |
| Wizzup | _uvos__: ok, nvm for now wrt bionic not working I think | 19:59 |
| _uvos__ | also gives plain debain/ini config an interface to this stuff | 19:59 |
| Wizzup | sure but it breaks existing interfaces, but this is a conversation we've had many many times in similar forms :P | 19:59 |
| _uvos__ | porting to gesettings is equvalent effort :P | 19:59 |
| Wizzup | if nothing uses the gconf interface beyond our cp applet then it's fine | 19:59 |
| Wizzup | but I am pretty sure maemo.org/packages has quite some that use it | 20:00 |
| bencoh | I'm pretty sure a lot of things use gconf | 20:00 |
| _uvos__ | maybe but either way with new debain version | 20:00 |
| bencoh | (as in, I know for sure) | 20:00 |
| _uvos__ | gconf is not an option | 20:00 |
| bencoh | what do you mean by dbus btw? does it have some kind of configuration thing? | 20:01 |
| _uvos__ | no the interface to change display brightniss is just now a dbus method | 20:01 |
| _uvos__ | not a gconf key | 20:01 |
| bencoh | ah | 20:01 |
| _uvos__ | mce stores the value elswhere | 20:01 |
| Wizzup | gconf currently is being used and it is an option, and we could replace all gconf usage with gsettings in the future, it is a possible path | 20:01 |
| _uvos__ | (either ini file or gconf atm) | 20:01 |
| Wizzup | specifically for disabling/enabling the leds I think gconf also maskes sense since it is a static setting | 20:02 |
| _uvos__ | sure it dose | 20:02 |
| Wizzup | oh | 20:02 |
| _uvos__ | and it will also be on gsettings once you implement a rtconf backent for gsettings | 20:02 |
| Wizzup | I missed the other statement | 20:02 |
| Wizzup | ok, it'd just be nice if changing the values via gconf would still work | 20:02 |
| Wizzup | (or later gsettings) | 20:02 |
| * Wizzup back to doing stuff | 20:02 | |
| _uvos__ | Wizzup: wrt the fw no way thay have it | 20:04 |
| _uvos__ | mz617 isent even unlockable | 20:04 |
| _uvos__ | so why would they have anything on it | 20:05 |
| Wizzup | they allow unlocking locked bootloaders in some devices, but not for those I think | 20:05 |
| Wizzup | it does list mz605 | 20:05 |
| Wizzup | https://sigmakey.com/en/sigma-sigma/supported-models.html?brand=3 | 20:06 |
| Wizzup | but that might not be close | 20:06 |
| Wizzup | yeah looks like that is qcom | 20:06 |
| Wizzup | _uvos__: maybe, they seem to make a living out of this stuff though | 20:06 |
| bencoh | wait, what is this magical device | 20:07 |
| Wizzup | bencoh: do you mean sigmakey? | 20:07 |
| bencoh | yeah | 20:08 |
| Wizzup | sigmakey is sw, but it requires a hw dongle to use | 20:08 |
| bencoh | I'm not certain I really understand what it is supposed to do | 20:08 |
| Wizzup | repair IMEI, unlock devices, reset lock counters, root any android in existing, etc etc | 20:08 |
| Wizzup | I think it's mostly meant for phone repair shops | 20:08 |
| Wizzup | but I got it to unlock my droid 3's | 20:08 |
| Wizzup | but since it mostly works over usb, I was hoping I could get usbip to work | 20:08 |
| Wizzup | (so we can do it remotely too) | 20:09 |
| Wizzup | I think it also has unlock code calc just based on IMEI depending on the device (should work for d3) | 20:09 |
| _uvos__ | oh did you buy it allready | 20:09 |
| _uvos__ | ? | 20:09 |
| Wizzup | yes | 20:09 |
| _uvos__ | ah | 20:09 |
| Wizzup | I ordered it yesterday night | 20:09 |
| _uvos__ | did it work | 20:09 |
| _uvos__ | oh ok | 20:09 |
| Wizzup | still waiting on dhl | 20:09 |
| _uvos__ | ok | 20:09 |
| Wizzup | anyway I'm not advertising it, it just seemed like a useful thing to have in the end | 20:09 |
| Wizzup | _uvos__: wrt my bionic, nvm for now | 20:10 |
| _uvos__ | ok good | 20:10 |
| _uvos__ | side note particularly egregious usage of gconf as ipc: the slider state is only exposed on a gconf key on leste | 20:11 |
| _uvos__ | that i also added a dbus interface to mce for | 20:11 |
| Wizzup | makes sense | 20:13 |
| Wizzup | _uvos___: lmk when you're home btw | 20:14 |
| Wizzup | uvos: I resolved my d3 problem | 20:43 |
| Wizzup | I upgraded the kernel but forgot that the new modules would not work with the older zImage I manually copied | 20:44 |
| _uvos_ | Wizzup: heh | 20:48 |
| Wizzup | yeah. | 20:48 |
| Wizzup | well that's good news | 20:48 |
| _uvos_ | yeah | 20:49 |
| _uvos_ | so have you got it booting kexecboot yet? | 20:49 |
| Wizzup | no, but that will be one of the next step(s) | 20:51 |
| Wizzup | (I didn't try yet, so no fail to report either) | 20:51 |
| Wizzup | dgamer69: welcome back | 21:15 |
| freemangordon | kona_: did you manage to package modest-providers? | 21:59 |
| uvos | Wizzup: im home | 22:12 |
| uvos | what do you want? | 22:12 |
| Wizzup | ah | 22:15 |
| kona_ | freemangordon: not yet, could work on it tonight. | 22:40 |
| kona_ | oh, wow, i'm unverified. | 22:40 |
| kona | perhaps nickserv is happy now | 22:41 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!