| bencoh | Wizzup: hmm, what do ifconfig/wpa_cli say? | 00:03 |
|---|---|---|
| bencoh | oh and, I just saw wpasupplicant and friends got an upgrade today when updating repos ... I hope it doesn't enable the interface now | 00:05 |
| Wizzup | bencoh: it doesn't enable the interface | 00:06 |
| bencoh | then if you were still able to connect, it means the applet didn't disable it (?) | 00:07 |
| bencoh | are you able to reproduce it? | 00:07 |
| bencoh | oh and, I might have an idea | 00:08 |
| bencoh | apparently the wifi.sh script doesn't get a parameter from the applet, but instead toggles the interface based on its current status | 00:09 |
| bencoh | so if the interface was disabled manually (not updating the applet status), then you tried disabling it from the applet ... | 00:09 |
| bencoh | it will actually enable it (I think) | 00:09 |
| uvos | bencoh: maybe try /dev/rfkill (isent in leste kernel you need to compile a kernel with support for this) then nothing can unblock the interface except your widget | 00:10 |
| Wizzup | bencoh: I was connected to a wifi ap when I tried to disable it | 00:10 |
| Wizzup | uvos: I don't think we necessarily want rfkill? | 00:10 |
| uvos | Wizzup: why not? | 00:10 |
| uvos | Wizzup: the widget is to disable wifi no? | 00:10 |
| uvos | i thought | 00:10 |
| bencoh | Wizzup: can you reproduce it? | 00:11 |
| Wizzup | bencoh: I think maybe the iaps were cached | 00:12 |
| Wizzup | that's why they showed up in the scan dialog | 00:13 |
| Wizzup | I suppose I could flush more quickly | 00:13 |
| Wizzup | probably should | 00:13 |
| bencoh | Wizzup: did you really manage to connect though? | 00:13 |
| uvos | the widget is just bringing down the wlan0 interface or? | 00:14 |
| bencoh | uvos: ifconfig wlan0 0.0.0.0 down | 00:15 |
| uvos | dose that even prevent scanning? or monitor mode for that matter? | 00:16 |
| bencoh | I think it should, unless I missed something | 00:16 |
| bencoh | at least I don't get any scanning result after ifconfig down from the connections dialog | 00:17 |
| bencoh | uvos: is rfkill even supported by our driver(s) | 00:17 |
| bencoh | ? | 00:17 |
| Wizzup | bencoh: I think so, kinda weird | 00:18 |
| Wizzup | uvos: it does prevent scanning | 00:18 |
| uvos | bencoh: probubly | 00:18 |
| uvos | bencoh: not that i tried | 00:18 |
| uvos | Wizzup: why would that be wierd? | 00:18 |
| Wizzup | uvos: because the interface is down and wpa_supplican cannot use it | 00:18 |
| uvos | Wizzup: that dosent disable scannin per say | 00:18 |
| Wizzup | uvos: try it | 00:18 |
| uvos | wpa just dosent use down interfaces | 00:19 |
| Wizzup | it doesn't work | 00:19 |
| uvos | right but is that wpa | 00:19 |
| uvos | or kernel interface | 00:19 |
| uvos | im not so sure | 00:19 |
| Wizzup | pretty sure it's kernel iface | 00:19 |
| uvos | ok | 00:19 |
| uvos | i dont see why you think rfkill is wierd | 00:19 |
| bencoh | he was referring to the fact that he still connected, not to rfkill :) | 00:20 |
| uvos | oh i missread | 00:20 |
| uvos | nvm then | 00:21 |
| lel | MerlijnWajer closed an issue: https://github.com/maemo-leste/bugtracker/issues/353 (ScummVM segfaults on launch) | 01:20 |
| stanr | 5.11.22 #1 seems very stable. congratulations to the fixers. | 04:12 |
| stanr | i understand C++ about as well as a dog understands a vacuum cleaner | 06:04 |
| stanr | and all i can do is bark angrily at it | 06:04 |
| stanr | figured it out. larger font theme 0.1 working on pc, not on maemo-leste version yet | 08:06 |
| mighty17[m] | `glmark2 Score: 22` ok this is really bad i get better results with 1.17 + wayland | 08:07 |
| stanr | what device | 08:10 |
| mighty17[m] | Samsung Galaxy Tab 2 | 08:14 |
| mighty17[m] | with --fullscreen i get `glmark2 Score: 74` | 08:15 |
| stanr | what cpu/gpu is that? | 08:15 |
| mighty17[m] | Omap4430 | 08:15 |
| mighty17[m] | Sgx540 | 08:15 |
| stanr | cool | 08:15 |
| mighty17[m] | cant understand why without fullscreen its so bad | 08:16 |
| stanr | i think xorg is doing an extra copy | 08:16 |
| stanr | due to compositing | 08:17 |
| mighty17[m] | https://pastebin.ubuntu.com/p/mHCcJz6FGZ/ logs for both | 08:18 |
| stanr | under hildon, you should be able to disable compositing in windowed application with ctrl-shift-n | 08:20 |
| mighty17[m] | no keyboard | 08:30 |
| mighty17[m] | wiki.postmarketos.org/wiki/Samsung_Galaxy_Tab_2_7.0%22_(samsung-espresso3g) its a tab | 08:30 |
| stanr | i got glmark2-es2 24 yesterday i think | 08:32 |
| mighty17[m] | what device? | 08:32 |
| stanr | droid4, omap4430 | 08:33 |
| mighty17[m] | oh i use droid4 rootfs :P on the tab2 | 08:33 |
| stanr | not under hildon | 08:33 |
| mighty17[m] | very similar devices | 08:33 |
| mighty17[m] | not under hildon > then what? | 08:34 |
| stanr | xorg + openbox | 08:34 |
| mighty17[m] | and maemo? | 08:34 |
| stanr | yes | 08:34 |
| stanr | you can switch WM's without restarting x | 08:34 |
| mighty17[m] | wow thats new | 08:35 |
| mighty17[m] | any pics? | 08:35 |
| stanr | not really, they're just programs running in x | 08:35 |
| stanr | it looks like openbox | 08:35 |
| mighty17[m] | one can theme openbox :) | 08:36 |
| stanr | to switch to openbox i do | 08:37 |
| stanr | /usr/sbin/dsmetool -k /usr/bin/hildon-desktop | 08:37 |
| stanr | sleep 2 | 08:37 |
| stanr | openbox-session& | 08:37 |
| mighty17[m] | openbox wouldnt work well for me, no hw keyboard | 08:37 |
| stanr | they can be purchased | 08:37 |
| stanr | then to restart hildon i just killall openbox && sleep 2 && /etc/X11/Xsession.post/20hildon-desktop | 08:37 |
| mighty17[m] | i mean yes but i dont hv any reason | 08:38 |
| mighty17[m] | openbox-session& > pretty simple :D | 08:38 |
| mighty17[m] | i still hv to try gdm | 08:38 |
| stanr | a computer without a keyboard is like a horse without legs | 08:41 |
| mighty17[m] | haha | 08:41 |
| mighty17[m] | virtual keyboard is good for me :P plus its a tab like lol | 08:42 |
| meldrian | Are there additional sources for the maemo leste package manager besides the ones already present after flashing the sdcard? | 10:33 |
| uvos | no | 10:34 |
| uvos | but apt has all of debian | 10:34 |
| sicelo | meldrian: you can also add/enable the -devel repository, but expect the unexpected, like you would with Debian Sid, for example | 10:45 |
| meldrian | Thanks. expect the unexpected. I like that. | 10:49 |
| uvos | the -devel repo dosent conatin anything for ham | 10:50 |
| uvos | afaik | 10:50 |
| uvos | everything there is in extras anyhow so its not affected | 10:51 |
| Wizzup | mighty17[m]: how far did we get with support your device btw? what are the next steps? | 11:53 |
| Wizzup | uvos: the -devel repo can contain stuff for ham, but I only do that for some not-well-working stuff | 11:54 |
| uvos | Wizzup: but thats in extras-devel | 12:01 |
| uvos | i dont thing we document extras-devel anywhere | 12:01 |
| uvos | *think | 12:01 |
| uvos | or not? | 12:02 |
| Wizzup | not sure | 12:02 |
| Wizzup | btw, wifi changes should be in stable | 12:02 |
| uvos | Wizzup: good | 12:02 |
| uvos | Wizzup: no issues since you implmented the workaround | 12:02 |
| uvos | btw did you test if this happens on other devices besides the d4? | 12:03 |
| uvos | just in case the driver is a fault | 12:03 |
| Wizzup | do you mean the wpa interface randomly returning that it could not actually start a scan>? | 12:07 |
| uvos | yes | 12:07 |
| Wizzup | Not really, but it's also hard to debug. | 12:08 |
| Wizzup | uvos - the module still logs that though (when it fails) | 12:08 |
| Wizzup | so you can grep daemon.log | 12:08 |
| Wizzup | grep for 'try_scan_wpa_control' | 12:09 |
| Wizzup | Looks like the last time I had it was on July 3 | 12:09 |
| uvos | i dont really have a device with wifi i could try except another mapphone | 12:10 |
| Wizzup | I'm saying you could also grep on your d4 for the message to see if it still happens too | 12:10 |
| uvos | the n900 igues | 12:10 |
| Wizzup | I can try other devices, yeah, I suppose | 12:10 |
| uvos | but it shares a driver | 12:10 |
| Wizzup | I am not too worried since the scan still seems to work, it's probably something in wpa supplicant socket handling for the most part | 12:10 |
| uvos | ok | 12:10 |
| Wizzup | (or a scan already happening, which is also not too bad, but it can't be the cause for all of them) | 12:11 |
| uvos | could also be that kernel driver returns failure and then dose the scann anyhow | 12:11 |
| uvos | confuseing wpa | 12:11 |
| mighty17[m] | Wizzup: we were on making a wiki page :P | 12:20 |
| mighty17[m] | so far droid4 rootfs is working great for me | 12:20 |
| mighty17[m] | and another thing is omap2plus defconfig somehow doesnt work for me | 12:20 |
| sicelo | you can diff omap2plus with yours, and see what the differences are | 12:23 |
| mighty17[m] | right now cant do anything, sdcard issues still not fixed | 12:24 |
| mighty17[m] | not mmc issue but getting a reader | 12:25 |
| Wizzup | ok | 12:27 |
| Wizzup | so ongoing on your side it sounds like :) | 12:27 |
| uvos | we could take on his device instead of mz609 if we want a tablet i gues | 12:28 |
| uvos | i dont relish the thought of not having a serial port tho | 12:28 |
| uvos | motorola devices are pretty mutch optimal in this regard | 12:28 |
| uvos | mighty17[m]: you could try and compile omap2plus with just omapdrm built in instead of a module | 12:29 |
| Wizzup | I think mz609 is not a bad target | 12:29 |
| uvos | and see if it spits out any errors | 12:29 |
| Wizzup | apart from the flashing stuff | 12:29 |
| uvos | mz609 has not flashing issues | 12:30 |
| uvos | thats mz617 | 12:30 |
| Wizzup | ok, so what's wrong with mz609 then? | 12:30 |
| uvos | where can i buy one? | 12:30 |
| uvos | (they are rare) | 12:30 |
| uvos | mighty17[m]'s samsung tablet is common as mud | 12:31 |
| Wizzup | wait, didn't I send you a mz609? | 12:31 |
| Wizzup | I am confused now | 12:31 |
| uvos | Wizzup: its mmc dosent work | 12:31 |
| uvos | it discards all wrights remember | 12:31 |
| uvos | *wirtes | 12:31 |
| Wizzup | I remember | 12:31 |
| Wizzup | I am trying to understand if the mbm allow flashing stuff is for the mz609 or not | 12:31 |
| Wizzup | I keep confusing the codenames :) | 12:31 |
| uvos | mz609 (the small tablet) works great | 12:32 |
| uvos | we have permissive mbm | 12:32 |
| uvos | and kexecboot and everything ready | 12:32 |
| uvos | thanks to tonys work | 12:32 |
| Wizzup | ok, so that's something I can try next week when I get back to croatia then | 12:32 |
| uvos | right | 12:32 |
| Wizzup | uvos: ah I see, the 11 mz617 are harder to flash | 12:33 |
| uvos | yes | 12:33 |
| mighty17[m] | you could try and compile omap2plus with just omapdrm built in instead of a module > uvos omapdrm needs to be a module for hildon/pvr to work | 12:42 |
| uvos | mighty17[m]: right but this would be without pvr just to debug | 12:42 |
| mighty17[m] | samsung tablet is common as mud > indeed like it used to be top 10 in LineageOs at one time :P | 12:43 |
| uvos | mighty17[m]: i guessing that maybe your linux cant find its modules due to your block device issues | 12:43 |
| uvos | mighty17[m]: if you compile in omapdrm this gives the kernel a chance to complain and you to read the error | 12:43 |
| mighty17[m] | right but this would be without pvr just to debug > uvos im missing a sdcard reader so i cant change the modules (/lib/modules/5.11.0) | 12:43 |
| uvos | your not supposed to change that | 12:44 |
| uvos | just compile a new tag | 12:44 |
| mighty17[m] | oh ok like that | 12:44 |
| mighty17[m] | also bootloader issue | 12:44 |
| uvos | and then modules_install creates a new directoy called 5.11.0-akhfshgkjhjdsah | 12:44 |
| uvos | just copy that into /lib/modules with leste | 12:45 |
| uvos | yeah bootloader issue is another thing | 12:45 |
| mighty17[m] | for now i will modify it in omap2plus | 12:45 |
| Wizzup | any idea what the easiest way would be to get a sfos device? to inspect the audio stack and such | 16:08 |
| buZz | https://en.wikipedia.org/wiki/Sailfish_OS#Hardware_overview | 16:28 |
| bencoh | we could easily download an image I guess | 16:31 |
| buZz | there's a nokia n950 port, lol | 16:33 |
| buZz | the unobtainium | 16:33 |
| bencoh | some leste devs own n950 :) | 16:33 |
| bencoh | (well, they own a n950 unit, at least) | 16:34 |
| parazyd | Yeah fmg has one that I know | 16:34 |
| parazyd | Though more or less it's the N9 | 16:35 |
| bencoh | yeah | 16:35 |
| parazyd | That said | 16:37 |
| parazyd | Wizzup: You can run sailfish on the N9 | 16:37 |
| parazyd | Wizzup: https://wiki.maemo.org/Sailfish | 16:38 |
| buZz | its maybe bad marketing to post tweets as maemo leste that display 'posted with twidere on android' | 16:40 |
| buZz | ;) | 16:40 |
| parazyd | Who's to say I'm not using Anbox :p | 16:41 |
| buZz | right, but couldnt you spoof it? :P | 16:42 |
| parazyd | dunnp | 16:43 |
| parazyd | dunno | 16:43 |
| Wizzup | I guess the pinephone might run it, but also I'm just mostly searching for where pulse config files come from | 16:44 |
| Wizzup | how they build the rootfs etc | 16:44 |
| buZz | ah hmhm | 16:45 |
| Wizzup | maybe jusa will still reply, who knows | 16:45 |
| buZz | did you see https://sailfishos.org/develop/hadk/ ? | 16:45 |
| Wizzup | the pdf seems helpful | 16:47 |
| Wizzup | android/hal might be quite different though, but we'll see | 16:47 |
| Wizzup | buZz: 14.9 | 16:48 |
| Wizzup | 14.9 AudioFor audio, Sailfish OS uses PulseAudio as the main mixer. For audio routing ohmd is used.TODO: Add info about audio routing configuration TODO: Add more info in general | 16:48 |
| Wizzup | ;) | 16:48 |
| buZz | :) | 16:48 |
| bencoh | (talking about anbox, I couldn't get it to work on droid4) | 16:51 |
| bencoh | (I always eventually have some anbox/android-related process stuck at 100%cpu for ages) | 16:52 |
| parazyd | bencoh: It won't work with pvr | 16:53 |
| bencoh | oh, seriously? :( | 16:53 |
| parazyd | And I think 32bit in general, it's a bit messy | 16:53 |
| parazyd | Yeah | 16:53 |
| bencoh | well, no need to try then | 16:53 |
| parazyd | No | 16:53 |
| parazyd | It works well on the Pinephone | 16:53 |
| parazyd | (with additional zram) | 16:53 |
| bencoh | Wizzup: something tells me telepathy is too high level for the sailfish hw adaptation guide btw | 16:54 |
| bencoh | since telepathy sits on another abstraction layer (they leverage the android RIL) | 16:54 |
| Wizzup | bencoh: this is about pulse though, but yeah | 16:55 |
| bencoh | oh, pulse/ohmd, right. n900 uses ohmd as well | 16:55 |
| Wizzup | bencoh: it won't currently work with pvr at least | 16:55 |
| Wizzup | bencoh: the n900 does? I forgot about that | 16:55 |
| bencoh | it does, I never really understood what it did though | 16:56 |
| Wizzup | I see it now | 16:56 |
| Wizzup | I think I have most of what I need, I was just searching for jusa's advice/blessing :p | 16:56 |
| Wizzup | I'll continue later today or tomorrow, work took over | 16:56 |
| bencoh | :) | 16:56 |
| Wizzup | https://web.archive.org/web/20200815080328/https://wiki.merproject.org/wiki/Nemo/Audio this page describes a lot | 16:56 |
| Wizzup | I just don't know how up to date it is (I had to port the cmtspeech to newer pa for example) | 16:56 |
| bencoh | oh, right, nemo basically went the same way 5~10y ago | 16:57 |
| bencoh | wait, so ohmd is the one reading xpolicy.conf?! | 16:58 |
| Wizzup | wiki.merproject.org is also down | 16:58 |
| Wizzup | bencoh: I need to verify that, I think that's pulse | 16:58 |
| Wizzup | (I'd try harder to answer the q, but need to get back to work :) ) | 16:58 |
| bencoh | (same tbh :D) | 16:59 |
| Wizzup | bencoh: it is pulseaudio-policy-enforcement that does it | 17:00 |
| Wizzup | https://github.com/maemo-leste/pulseaudio-policy-enforcement | 17:00 |
| Wizzup | https://github.com/maemo-leste/pulseaudio-policy-enforcement/blob/leste/examples/xpolicy.conf | 17:00 |
| Wizzup | (i think) | 17:00 |
| bencoh | ah, thanks | 17:02 |
| Wizzup | sicelo: I suppose a nemo n900 image would work just as ewll | 17:23 |
| stanr | i see maemo scummvm is using the oldstyle /opt install directories. is there something i can read to understand the reasoning for this? | 18:20 |
| stanr | iirc it was to allow large apps to go to a larger partition than system programs | 18:21 |
| buZz | i think there's still debate about a second partition like MyDocs | 18:21 |
| Wizzup | yes, it has not been ported over not to use /opt | 18:21 |
| Wizzup | that's the only reason | 18:21 |
| Wizzup | we don't optify at this point | 18:21 |
| stanr | thanks | 18:21 |
| tmlind | uvos: so i tried your suggestion of fastboot flash mbmloader mbmloader.bin on mz617 and yeah it works | 20:19 |
| tmlind | uvos: i also extracted mz615 and mz616 motoboot files and they too are flashable on mz617, but do not allow flashing utags partition | 20:20 |
| tmlind | i just used these for mz617 for reference to extract motoboot: | 20:21 |
| tmlind | bin="motoboot.bin" | 20:21 |
| tmlind | dd if=${bin} bs=1 skip=$((0x400)) count=$((0x80070 - 0x400)) of=allow-mbmloader-flashing-mbm.bin | 20:21 |
| tmlind | dd if=${bin} bs=1 skip=$((0x80400)) count=$((0x8a8e0 - 0x80400)) of=mbmloader_ns.bin | 20:21 |
| tmlind | dd if=${bin} bs=1 skip=$((0xa0400)) count=$((0xaaef0 - 0xa0400)) of=mbmloader_hs.bin | 20:21 |
| tmlind | the filename and offsets are slightly different for mz615: | 20:22 |
| tmlind | bin="motoboot.img" | 20:22 |
| tmlind | dd if=${bin} bs=1 skip=$((0x400)) count=$((0x80070 - 0x400)) of=allow-mbmloader-flashing-mbm.bin | 20:22 |
| tmlind | dd if=${bin} bs=1 skip=$((0x80400)) count=$((0x8aef0 - 0x80400)) of=mbmloader_ns.bin | 20:22 |
| tmlind | dd if=${bin} bs=1 skip=$((0xa0400)) count=$((0xaaee0 - 0xa0400)) of=mbmloader_hs.bin | 20:22 |
| Wizzup | that's good news... right? | 20:23 |
| tmlind | then the mz617 motoboot has no mbm or mbmloader at all | 20:23 |
| tmlind | Wizzup: well no, the motoboot files just contain yet another version of mbm and mbmloader, they are not really allow-mbmloader-flashing-mbm.bin files | 20:24 |
| Wizzup | hmm | 20:24 |
| tmlind | it seems that some earlier firmware might still contain the allow-mbmloader-flashing-mbm.bin, otherwise utags needs to be installed with dd on a rooted system | 20:25 |
| uvos | tmlind: just to carify the first ofsets are for mz616 not mz617 as you wrote right | 21:02 |
| uvos | otherwise the rest of what you said makes no sense | 21:02 |
| uvos | i wonder what they needed motoboot for if it contains just another mbm, its not bit identical to regular mbm.bin right? | 21:03 |
| tmlind | uvos: sorry yeah for mz616 | 21:20 |
| tmlind | uvos: yeah no idea what the motoboot really is, maybe it's needed to update the partition tables? | 21:20 |
| tmlind | anyways sleepy time here, ttyl | 21:23 |
| Wizzup | gn | 21:24 |
| freemangordon | parazyd: BTW, may we have my tp-glib memleak patch somehow? | 21:37 |
| freemangordon | either through devuan or leste repos? | 21:38 |
| parazyd | freemangordon: I think we decided to compile all of telepathy ourselves, at least for beowulf | 22:26 |
| freemangordon | but, do we compile it? | 22:27 |
| freemangordon | as I still see a memleak with valgrind | 22:27 |
| parazyd | No, not yet | 22:27 |
| parazyd | Shall I set it up? | 22:27 |
| freemangordon | yes, but no hurry | 22:27 |
| parazyd | ok, added for morning todo | 22:28 |
| freemangordon | :) | 22:28 |
| stanr | now one droid4 is hijacking the wlan connection of another and grabbing the same IP addr | 22:42 |
| stanr | if one disconnects a wifi manually, leste reconnects | 22:43 |
| stanr | seems that the user has indicated "stay offline" if disconnecting a wifi | 22:43 |
| stanr | which the system should respect | 22:43 |
| stanr | i'll set it to 'always ask' | 22:44 |
| stanr | but an unintended disconnection - lost connection is a different case! | 22:44 |
| stanr | THAT should trigger a reconnection attempt! | 22:44 |
| stanr | or we should have an option on internet connections to 'attempt reconnection to lost wifi' | 22:45 |
| stanr | yeah i had two droid4's both thinking they had the same IP addr on wlan | 22:46 |
| parazyd | Maybe you forgot to change one of their hostnames? | 22:49 |
| stanr | ah that's it | 22:50 |
| uvos | stanr: you moved the sdcard from one droid 4 to another and now both have the same mac address as the mac addres travels with the sdcard/nvs | 23:00 |
| stanr | ohhh | 23:00 |
| stanr | how do i reset it? | 23:01 |
| uvos | stanr: you follow your own damn instructions https://leste.maemo.org/Motorola_Droid_4#Using_a_configured_Leste_sdcard_in_a_different_Droid4 | 23:02 |
| sicelo | Wizzup: sfos device -> droid4 has a working, old port | 23:03 |
| uvos | sicelo: that uses android hal | 23:03 |
| sicelo | Wizzup: n900 nemo image -> that works too. phone calls worked ootb | 23:03 |
| sicelo | uvos: he asked about an sfos device? no? | 23:04 |
| uvos | sure but one that uses android hal for audio is very likely not what he wants | 23:04 |
| stanr | mac address appears to be in /etc/udev/rules.d/70-persistent-net.rules | 23:04 |
| uvos | no | 23:04 |
| uvos | its in nvs | 23:04 |
| sicelo | < Wizzup> [16:08] any idea what the easiest way would be to get a sfos device? to inspect the audio stack and such .... he's got million d4 :) | 23:04 |
| uvos | thats just the interface name based on mac | 23:04 |
| stanr | ok thanks | 23:05 |
| uvos | yeah i know what he said, but a sfos device that uses android hal is unlieky to be very helpfull | 23:05 |
| uvos | the n900 nemo is a mutch better suggestion | 23:05 |
| sicelo | Wizzup: you ported cmtspeech to newer pa - you did this in your recent work? | 23:07 |
| Wizzup | sicelo: re: cmtspeech, I didn't do much, I only ported the nemo module to newer PA | 23:09 |
| Wizzup | sicelo: I tried to find the nemo n900 image but couldn't find it | 23:10 |
| Wizzup | sicelo: uvos: yeah, preferrably not with android hal stuff | 23:10 |
| sicelo | let me check. i downloaded it in second half of 2020, so should be available somewhere | 23:11 |
| uvos | did nemo drop support for n900? | 23:11 |
| uvos | (just curious) | 23:11 |
| sicelo | yes, they did - and soon died too, but getting revived now | 23:13 |
| Wizzup | what soon died too? | 23:13 |
| sicelo | http://releases.nemomobile.org/releases/0.20130620.0.1/images/ | 23:13 |
| sicelo | Nemo eventually kinda died. It's back now, but mostly seems to be quite different from what it was in the start | 23:14 |
| uvos | heh armv7hl | 23:16 |
| uvos | do we really have to specify little-endian | 23:16 |
| uvos | who runs arm in big-endian mode :P | 23:16 |
| parazyd | sicelo, uvos, Wizzup: https://wiki.maemo.org/Sailfish | 23:17 |
| parazyd | Wizzup: You got an N9, right? | 23:17 |
| Wizzup | yes, it didn't have a link to the nemo images | 23:17 |
| Wizzup | yes, I have a N9 here somewhere | 23:18 |
| Wizzup | but this is fine, I don't necessarily want to boot it on my n900 (i might) | 23:18 |
| Wizzup | I just need to poke at the image | 23:18 |
| parazyd | The wiki link is for N9 | 23:18 |
| parazyd | ah crap the link is dead http://www.mediafire.com/download/zj4q8ai80xg41iu/sailfishos_n9_1_0_0_5.tar.bz2 | 23:19 |
| Wizzup | the link sicelo posted also has n9 images I think | 23:19 |
| parazyd | Maybe it's still possible to build it | 23:19 |
| Wizzup | well n950 anyway | 23:19 |
| Wizzup | parazyd: I don't want to invest that much time in it | 23:19 |
| Wizzup | I think I have what I need: to peek inside the pulseaudio config files | 23:20 |
| Wizzup | the rootfs probably has tools to also let me poke around the rpm database | 23:20 |
| sicelo | btw now you're working with PA12 you said? or 14? | 23:21 |
| uvos | Wizzup: maybe the vbox sfos image is even better | 23:21 |
| uvos | since its newer | 23:21 |
| uvos | https://sailfishos.org/wiki/Sailfish_SDK | 23:21 |
| Wizzup | uvos: no, that doesn't contain the n900 stuff :p | 23:21 |
| Wizzup | uvos: not sure if I linked this earlier https://git.sailfishos.org/mer-core/voicecall | 23:21 |
| uvos | oh ok | 23:21 |
| uvos | i thought you where after the genreal pa setup | 23:22 |
| Wizzup | I am, but the n900 is still easier to use here I think | 23:22 |
| Wizzup | since the modules I am working with are basically what is in this image | 23:22 |
| sicelo | (ah, i see Leste has PA12 - was looking at my sid laptop) | 23:22 |
| Wizzup | sicelo: yeah, sfos is on pa14 now | 23:23 |
| uvos | ok | 23:23 |
| uvos | idk if we want to do waht the n900 stuff you linked back when did | 23:23 |
| uvos | since it looks specific to the n900 hardware mixer controles | 23:23 |
| Wizzup | can you be more specific? | 23:24 |
| Wizzup | oh that part, well, that's just one part of a lot of this | 23:24 |
| uvos | well it fiddels with mixer values directly if i read it correcly (i only glanced at it) | 23:24 |
| uvos | i know | 23:24 |
| Wizzup | if I can the other stuff going soon, that'll already be great | 23:24 |
| uvos | well i suspect you know what you are doning | 23:24 |
| uvos | so carry on | 23:24 |
| Wizzup | uvos: that's kind, I am not always sure ;) | 23:24 |
| Wizzup | I am sure things changed since nemo 2013 times, but the modules seem to be mostly the same otherwise | 23:25 |
| Wizzup | and the sfos stuff is not documented at all, compared to the nemo/mer audio, but I assume it's mostly the same | 23:25 |
| Wizzup | so for making policies, tagging apps and moving them to certain sinks, all that stuff, I think we're good with the current approach | 23:25 |
| Wizzup | then the switching we can do with UCM probably, but I imagine that might not be a super tricky change | 23:25 |
| uvos | so do you want to import voicecallmanager? | 23:33 |
| Wizzup | uvos: not sure, but if it does a lot of heavy lifting for us, it could be useful, I haven't looked that much at it | 23:53 |
| Wizzup | It seems to be a background daemon, if I understand correctly, not a UI | 23:53 |
| uvos | yes | 23:53 |
| uvos | it looks sorta like the mce call module as a deamon | 23:54 |
| uvos | expanded a bit | 23:54 |
| uvos | also replaces some stuff also in sphone | 23:55 |
| uvos | like the rinnger | 23:55 |
| sicelo | (i was just watching the pp hwkb video by Martijn. is it just me, or with phone keyboards, you're better off with n900-droid4 size kbd, where you use only two fingers? looks to me like the pp keyboard is too big for easy "two finger" typing, and too small for all fingers) | 23:55 |
| sicelo | anyway, still nice to have any keyboard :) | 23:55 |
| Wizzup | sicelo: yes, more like psion keyboard (thumb typing) | 23:56 |
| Wizzup | uvos: ok, good to keep in the back of our head, I don't know how much it depends on other sfos stuff | 23:56 |
| uvos | Wizzup: idk if its usefull, except the abstraction that allows you to use ofono or telephathy thats need | 23:57 |
| uvos | *neat | 23:57 |
| uvos | Wizzup: otherwise, if we use ofono direclty we have everything i provides in other places, as far as i can tell from a brief survay of the modules | 23:57 |
| Wizzup | uvos: in the long term I don't think we want to rely solely on ofono - for sip we will have telepathy | 23:59 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!