| Wizzup | freemangordon: could you perhaps make a -dbgsym pkg of osso-abook? that would help here | 00:01 |
|---|---|---|
| Wizzup | I can reproduce any time I think by just requesting a new 2fa sms | 00:01 |
| Wizzup | freemangordon: maybe the problem is that I am looking up a 'telephone number' when it really is like a name | 00:02 |
| freemangordon | Wizzup: there is dbgsym package | 00:22 |
| Wizzup | what is the name? | 00:22 |
| freemangordon | libosso-abook-dbgsym | 00:22 |
| Wizzup | what the | 00:23 |
| Wizzup | ok | 00:23 |
| Wizzup | yeah it is there | 00:23 |
| Wizzup | weird | 00:23 |
| Wizzup | so what should do, fix the crash when a non-number is used in the lookup? | 00:23 |
| freemangordon | what is th eissue? | 00:24 |
| freemangordon | like may I have the backtrace? | 00:24 |
| freemangordon | if there is a problem in osso-abook I will fix it | 00:24 |
| Wizzup | it is above | 00:25 |
| Wizzup | so frame 10 is log_event | 00:25 |
| Wizzup | where it tries to look up through conv_abook_lookup_tel | 00:25 |
| Wizzup | with telno "Apple" | 00:25 |
| Wizzup | (because this is the ID we get for incoming sms as remote_uid) | 00:25 |
| freemangordon | yeah, but bt is withoug debug symobols | 00:26 |
| Wizzup | but if you want I can get you more context | 00:26 |
| Wizzup | ok | 00:26 |
| Wizzup | I will do it gain | 00:26 |
| Wizzup | sec | 00:26 |
| freemangordon | yeah, please | 00:26 |
| Wizzup | 30s | 00:26 |
| Wizzup | what do you need from ne specifically now? | 00:27 |
| Wizzup | I have the same backtrace | 00:27 |
| freemangordon | with sbgsyms installed? | 00:29 |
| freemangordon | *dbgsymc | 00:29 |
| freemangordon | aaah | 00:29 |
| Wizzup | freemangordon: https://pastebin.com/raw/53XiPCc1 | 00:29 |
| freemangordon | that's enough, thanks | 00:30 |
| Wizzup | it's same the as what I said, but yes :) | 00:30 |
| freemangordon | this one has function parameters | 00:30 |
| Wizzup | yup | 00:31 |
| Wizzup | but I thnk the main param is 'Apple' as phone_number :D | 00:31 |
| freemangordon | mhm | 00:32 |
| freemangordon | Wizzup: this https://github.com/maemo-leste/osso-abook/blob/master/lib/osso-abook-util.c#L438 | 00:48 |
| freemangordon | should be EBookQuery *qs[3]; | 00:49 |
| freemangordon | if you are on a hurry, please fix it, otherwise I will fix it tomorrow | 00:50 |
| Wizzup | no hurry | 00:55 |
| Wizzup | ty for looking at this hour | 00:55 |
| inky | freemangordon, Wizzup, folks, i think you didn't mention libpurple. | 03:58 |
| inky | it is used at least by pidgin and finch. | 03:59 |
| inky | it is written in c. | 03:59 |
| inky | it has lots of plugins. | 03:59 |
| inky | mam plugin works well, there is http_upload plugin too. | 03:59 |
| inky | omemo plugin stopped working after upgrade of prosody and some pep changes a couple of years ago, and nobody from omemo plugin (lurch) people took a look even. i also commented there in the issue. | 04:01 |
| inky | today i think essential functionality is | 04:02 |
| inky | * user avatars | 04:05 |
| inky | * muc avatars | 04:05 |
| inky | * mam and muc_mam | 04:05 |
| inky | * carbons | 04:05 |
| inky | * http upload | 04:05 |
| inky | * omemo | 04:05 |
| inky | (if omemo is hard to fix then there is gpg and otr) | 04:05 |
| inky | also jingle is supported by pidgin, only need to mention turnserver ip in configuration. | 04:05 |
| moparisthebest | what kind of jingle though? today modern XMPP clients auto-discover stun/turn server and all support e2e encrypted webrtc calls (audio-only or audio+video) between each other, and if you have more than 1 device connected, they all ring when you get a call | 04:08 |
| unic0rn | are you folks using any "serious" (more advanced than leafpad) editor on d4/n900? not in docked mode, just for some random scripting on the go | 06:43 |
| unic0rn | so far I've figured that SciTE, which I haven't used in around 2 decades I think, works reasonably well | 06:44 |
| unic0rn | https://i.imgur.com/35UtLug.png | 06:44 |
| unic0rn | menu and tab bar can be hidden, so there's that. I just find nano to be too limited configuration-wise, and vim is unusable on such keyboard | 06:46 |
| unic0rn | https://leste.maemo.org/File:Droid4_htop.jpg - this makes me wonder, is it possible to set the base16 palette in default xterm to solarized? | 07:32 |
| unic0rn | because that htop is clearly using solarized palette | 07:32 |
| freemangordon | Wizzup: neither valgrind, nor asan or -fstack-protector-strong are catching the issue, I'll just push the change without confirmation this is a proper fix | 07:40 |
| freemangordon | my gut feeling tells me it is, but tools don,t confirm. Well... | 07:40 |
| Wizzup | freemangordon: thanks, will test | 10:20 |
| Wizzup | inky: libpurple you can try to use through haze | 10:20 |
| Wizzup | freemangordon: yes, now I got my 2fa sms | 10:41 |
| Wizzup | 43038|3|11|1717144824|1717144822|1717144822|1|0|0|0|0|ring/tel/account0|<SelfHandle>|Apple||Your Apple ID Code is: xxxxxx. Don't share it with anyone. @apple.com #xxxxxx|Apple | 10:42 |
| Wizzup | looks OK I suppose @ group_uid | 10:42 |
| Wizzup | although I think that the group_uid isn't just 7 digits/characters if it's a name apparently | 10:42 |
| Wizzup | so they only do that for phone numbers | 10:42 |
| Wizzup | why I still don't understand | 10:42 |
| Wizzup | freemangordon: btw I do see this: | 10:44 |
| Wizzup | [D] [::0] setChatState: remote_id: "Apple" | 10:44 |
| Wizzup | [W] [::0] tp-qt 0.9.8 WARN: TextChannel::requestChatState() used with no chat state interface | 10:44 |
| Wizzup | we might not want to do chat state if the CM doesn't suport it (i.e. sms) | 10:44 |
| freemangordon | well, ring is always-online account | 10:58 |
| freemangordon | ah, got it | 10:58 |
| freemangordon | ok, will have a look | 10:58 |
| Wizzup | freemangordon: https://telepathy.freedesktop.org/doc/telepathy-qt/a09024.html#acc72c0d00da25eebe5cecf607be974ca | 11:01 |
| Wizzup | I think that will do it | 11:02 |
| freemangordon | mhm | 11:05 |
| freemangordon | Wizzup: https://pastebin.com/pZEAicZG , do you want to test it or I shall make a new release? | 11:15 |
| Wizzup | new release sounds good | 11:23 |
| Wizzup | ty | 11:23 |
| freemangordon | Wizzup: please upgrade and test | 11:35 |
| Wizzup | freemangordon: will do | 11:43 |
| Wizzup | freemangordon: seems resolved | 11:53 |
| unic0rn | I've noticed that picking the sms option on the contact page fails when there's no country code. also, I assume the fact both conversations and dialer don't recognize contacts by number is just TODO | 12:15 |
| unic0rn | regarding country code, when I think about the original number could be missing country code and have some spaces at the same time. I was just testing contacts import | 12:16 |
| unic0rn | ended up converting every number to the same format | 12:16 |
| Wizzup | numbers are recognized by contacts just fine for me | 12:23 |
| Wizzup | I don't know about spone but it also works for me in matching | 12:24 |
| uvos | sphone uses a fuzzy matching stratagy for phone numbers provided by ebook it handles missing contry codes etc | 12:42 |
| uvos | not sure if it handles space or - delimited numbers | 12:42 |
| amunizp | Hello, hoping an n900 user is around here. I am a bit fearful of ruining the n900 could I check that I understood the installation process correctly? I added my understanding on the talk page of the wiki. https://leste.maemo.org/Talk:Nokia_N900 | 12:48 |
| dsc_ | lots of n900 around here :) | 12:50 |
| dsc_ | n900 users* | 12:50 |
| Wizzup | amunizp: did you also mail the ml recently? | 12:53 |
| amunizp | I did! though I thought I had botched the registration! | 12:54 |
| amunizp | Sorry I am refreshing my memory on IRC use. | 12:56 |
| Wizzup | I will also reply on the ml with a bit more detail, but, if you have a pin set on fremantle it will probably also affet leste | 13:00 |
| Wizzup | but you can tell leste not to care about ti by removing some script/file | 13:00 |
| Wizzup | but with a micro usd cable and microsd card you can boot to leste without affecting fremantle at all, too | 13:01 |
| Wizzup | s/usd/usb/ | 13:01 |
| amunizp | Wizzup: thank you! | 13:04 |
| amunizp | I will look out for your email. damned be the day 10 years ago when I thought of leaving the pin on a phone I was not going to use. | 13:05 |
| freemangordon | amunizp: well, in theory you should be able to set new pin if you boot another os and have CAL tool around | 14:04 |
| freemangordon | if you swear you did not stole the phone, I will provide more details :) | 14:05 |
| freemangordon | Wizzup: umm, what is the issue with PIN? | 14:05 |
| amunizp | freemangordon: OK so following the instructions of using an existing freemantle | 14:05 |
| Wizzup | he forgot his lock code | 14:05 |
| Wizzup | I just replied to the ml | 14:05 |
| amunizp | freemangordon: I swear! | 14:05 |
| freemangordon | ah, not SIM PIN | 14:05 |
| amunizp | yeah it is not a sim pin it is the n900 password. | 14:06 |
| freemangordon | ok, sec, I will provide details how to bypass from leste | 14:06 |
| Wizzup | so I just did this on the mailing list, but you can check my answer | 14:06 |
| Wizzup | freemangordon: even if he stole it, as long he wants to run leste on it :D | 14:06 |
| Wizzup | I think that's a legit reason to steal a phone :D | 14:07 |
| dsc_ | o/ | 14:07 |
| freemangordon | wow | 14:07 |
| freemangordon | well, yeah, ok | 14:07 |
| freemangordon | :D | 14:07 |
| amunizp | haha | 14:07 |
| freemangordon | Wizzup: ah, sorry, didn;t read the whole mail | 14:08 |
| Wizzup | no worries, you might have better instructions | 14:08 |
| amunizp | OK so I would rather have leste running on it than the original maemo that is not supported. | 14:08 |
| freemangordon | amunizp: yeah, what Wizzup said on ML | 14:08 |
| freemangordon | amunizp: you need fremantle to install u-boot | 14:08 |
| freemangordon | well, you can flash if from leste too I guess | 14:09 |
| freemangordon | or by using flasher | 14:09 |
| amunizp | freemangordon: they way you are saying it it seems best to keep a dual boot? | 14:09 |
| Wizzup | my suggestion was to first boot leste using the quick method, which doesn't touch the emmc at all | 14:10 |
| Wizzup | then fix the lock code, and then you can make a choicer: | 14:10 |
| Wizzup | choice* | 14:10 |
| Wizzup | 1. keep fremantle fully intact and just have a boot loader that let's you choose on boot | 14:10 |
| Wizzup | 2. potentially nuke booting fremantle and just write the bootloader over where the fremantle kernel might be | 14:11 |
| amunizp | Wizzup: thanks I assume there is no efficiency gain other than the slight nuicance of choosing OS on boot? | 14:11 |
| freemangordon | amunizp: https://github.com/maemo-leste/libdevlock/blob/master/devlocktool.c | 14:11 |
| Wizzup | yeah, none | 14:11 |
| freemangordon | amunizp: you can run devlocktool from leste and change your lock code | 14:12 |
| freemangordon | in theory at least | 14:12 |
| freemangordon | or enable/disable/etc | 14:12 |
| freemangordon | oh, it requires the old code | 14:13 |
| freemangordon | well, you can hack it | 14:13 |
| freemangordon | by commenting the https://github.com/maemo-leste/libdevlock/blob/master/libdevlock.c#L492 | 14:13 |
| freemangordon | Wizzup: btw, I think we shall change that to use some other storage if there is no cal | 14:14 |
| freemangordon | any idea what to use? | 14:15 |
| Wizzup | I think we discussed it in the past, I honestly don't really care | 14:18 |
| freemangordon | also, I see some unreleased commits in sphone, why is that? | 14:18 |
| Wizzup | well not every commit needs to be ready for release | 14:18 |
| Wizzup | I think current master doesn't compile on some MATRIX user const | 14:19 |
| freemangordon | ok | 14:19 |
| Wizzup | I would personally probably just not use cal and use something like pam or so | 14:19 |
| Wizzup | but mostly I don't care much about it yet atm :D | 14:19 |
| freemangordon | yeah :) | 14:19 |
| dsc_ | i made the app nobody was waiting for | 14:21 |
| dsc_ | a remote for kodi | 14:21 |
| dsc_ | yes I will work on conversations again now | 14:22 |
| Wizzup | dsc_: let me help you package it | 14:22 |
| Wizzup | I have kodi at home (as you know) :D | 14:22 |
| dsc_ | Wizzup: its nice controlling kodi from d4 keyboard :) | 14:23 |
| arno11 | i use kodi a lot too (for kids). that's really useful | 14:24 |
| amunizp | 3. Turn off Nokia N900,insert the SD Card with the image mentioned above, issue the following command on PC sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l and connect Nokia N900 to the PC | 14:24 |
| amunizp | the above is wrong right? I need to have the nokia connected? | 14:24 |
| inky | moparisthebest: true, no omemo in jingle | 14:25 |
| arno11 | Wizzup: i pushed pierogi btw | 14:25 |
| amunizp | ~/Documents/n900$ sudo ./0xFFFF -m test/u-boot-2013.04-2.bin | 14:31 |
| amunizp | sudo: ./0xFFFF: command not found | 14:31 |
| amunizp | andres@amunizp-Apollo:~/Documents/n900$ ls | 14:31 |
| amunizp | 0xFFFF dist.zip u-boot-2013.04-2.bin u-boot-2020.12-pali.bin | 14:31 |
| Wizzup | amunizp: is this the statically built 0xffff? | 14:35 |
| Wizzup | and no, you run it before the n900 is connected and then connect it | 14:35 |
| Wizzup | like the wiki says | 14:35 |
| Wizzup | amunizp: is it https://maedevu.maemo.org/images/n900/tools/0xFFFF ? | 14:36 |
| Wizzup | amunizp: are you on a musl libc distro? | 14:36 |
| amunizp | I do not know what statically built means but yes its the one I downloaded. | 14:36 |
| amunizp | https://leste.maemo.org/Nokia_N900 | 14:36 |
| amunizp | Ubuntu distro. | 14:36 |
| Wizzup | strange. | 14:36 |
| amunizp | I just downloaded. CD to the folder and ran the command. I am guessing I don't need to isntall any extra library? | 14:37 |
| freemangordon | Wizzup: is it 32 or 64 bits? | 14:38 |
| amunizp | 64 bit | 14:38 |
| amunizp | $ uname -a | 14:38 |
| amunizp | Linux amunizp-Apollo 5.15.0-107-generic #117-Ubuntu SMP Fri Apr 26 12:26:49 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux | 14:38 |
| Wizzup | 64 bit | 14:38 |
| Wizzup | so this must be some /lib/ld-linux.so or whatever name mismatch | 14:39 |
| freemangordon | amunizp: did you chmod a+x? | 14:39 |
| amunizp | freemangordon: I most certainly did not. | 14:39 |
| freemangordon | :) | 14:39 |
| Wizzup | I don't think this matters does it? | 14:40 |
| freemangordon | sure it does | 14:40 |
| Wizzup | then you get eperm | 14:40 |
| Wizzup | not file not found | 14:40 |
| freemangordon | no | 14:40 |
| freemangordon | oh, right | 14:40 |
| freemangordon | ldd 0xFFFF gives 'not a dynamic executable' | 14:41 |
| freemangordon | amunizp: ubuntu 22? | 14:41 |
| Wizzup | yes it's static | 14:42 |
| Wizzup | this is abour /lib/ld-linux.so or something | 14:42 |
| Wizzup | sorry visitors | 14:42 |
| amunizp | $ chmod a+x 0xFFFF | 14:42 |
| amunizp | andres@amunizp-Apollo:~/Documents/n900$ sudo ./0xFFFF -m test/u-boot-2013.04-2.bin | 14:42 |
| amunizp | 0xFFFF v0.8 // Open Free Fiasco Firmware Flasher | 14:42 |
| amunizp | Error: Cannot open image file test/u-boot-2013.04-2.bin: No such file or directory | 14:42 |
| amunizp | Error: Cannot load image file test/u-boot-2013.04-2.bin | 14:42 |
| amunizp | $ sudo ./0xFFFF -m u-boot-2013.04-2.bin | 14:42 |
| amunizp | 0xFFFF v0.8 // Open Free Fiasco Firmware Flasher | 14:42 |
| amunizp | Error: Nothing to do | 14:42 |
| amunizp | freemangordon: ubuntu 22 I just recently updated. | 14:42 |
| amunizp | I did $ chmod a+x 0xFFFF | 14:43 |
| freemangordon | yeah, seems recent ubuntu does not report permission denied | 14:43 |
| freemangordon | my laptop is with ubuntu 22, will try in a minute | 14:43 |
| Wizzup | freemangordon: so your chmod a+x did help btw | 14:43 |
| Wizzup | per his above report | 14:43 |
| freemangordon | mhm | 14:44 |
| amunizp | Yes it did! one step forward. I will add it to the wiki if that is OK. | 14:44 |
| Wizzup | yes sounds good | 14:44 |
| Wizzup | please do | 14:44 |
| freemangordon | hmm, on my ubuntu 22 I get permission denied | 14:44 |
| freemangordon | amunizp: maybe you run it from wrong current directory | 14:44 |
| freemangordon | anyway | 14:45 |
| freemangordon | still worths adding chmod a+x 0xFFFF to wiki | 14:45 |
| freemangordon | Wizzup: did you manage to debug calls audio issues on d4? | 14:46 |
| amunizp | I am guessing chmod a+x 0xFFFF does not need sudo? | 14:47 |
| freemangordon | no | 14:47 |
| freemangordon | unless you wget'ed it as root | 14:47 |
| amunizp | I did not. | 14:48 |
| freemangordon | no sudo needed for chmod then | 14:49 |
| amunizp | does the u-boot-2013.04-2.bin need to be in a "test" folder? | 14:49 |
| freemangordon | no, but you should provide the correct path to the flasher | 14:50 |
| amunizp | $ sudo ./0xFFFF -m test/u-boot-2013.04-2.bin | 14:51 |
| amunizp | 0xFFFF v0.8 // Open Free Fiasco Firmware Flasher | 14:51 |
| amunizp | Error: Nothing to do | 14:51 |
| amunizp | $ ls | 14:51 |
| amunizp | 0xFFFF dist.zip test u-boot-2020.12-pali.bin | 14:51 |
| amunizp | Seems the path is correct still says there is nothing to do. | 14:51 |
| amunizp | Does having nothing to do mean I am ready to plug in n900? | 14:52 |
| freemangordon | you are missing -f | 14:52 |
| freemangordon | see https://leste.maemo.org/Nokia_N900#Bootloader_.28U-Boot.29_setup | 14:52 |
| freemangordon | sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -f | 14:53 |
| freemangordon | see th '-f' at the end | 14:53 |
| amunizp | ahh! | 14:53 |
| freemangordon | but, did you read the warning? | 14:53 |
| freemangordon | "(Be careful though. This will replace the existing fremantle kernel. Only do this if you do not care about the existing maemo installation or you know how to recover from this condition)) " | 14:53 |
| amunizp | but that is only if I do the last bit right? | 14:54 |
| freemangordon | yes | 14:54 |
| freemangordon | but you have to tell the flasher what to do, right | 14:54 |
| freemangordon | -m points to the binary, not what to do with it | 14:54 |
| amunizp | OK so I want the -l not -f | 14:54 |
| freemangordon | yes | 14:54 |
| freemangordon | or maybe -l -b | 14:55 |
| freemangordon | I forgot the details | 14:55 |
| amunizp | $ sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l | 14:55 |
| amunizp | 0xFFFF v0.8 // Open Free Fiasco Firmware Flasher | 14:55 |
| amunizp | Not a local device | 14:55 |
| amunizp | Waiting for USB device... | 14:55 |
| freemangordon | ok, now connect the device, while pressing... ummm... f? key? or u? | 14:55 |
| freemangordon | amunizp: wiki is pretty detailed, just follow it | 14:57 |
| amunizp | ??? wiki says -l (not -b) and nothing about holding a key https://leste.maemo.org/Nokia_N900#Quick OK here we go. | 14:58 |
| amunizp | $ sudo ./0xFFFF -m test/u-boot-2013.04-2.bin -l | 14:59 |
| amunizp | 0xFFFF v0.8 // Open Free Fiasco Firmware Flasher | 14:59 |
| amunizp | Not a local device | 14:59 |
| amunizp | Waiting for USB device... | 14:59 |
| amunizp | Found USB device: RX-51 (0x421:0x1c7) in RAW disk mode | 14:59 |
| amunizp | USB device product string: N900 (Storage Mode) | 14:59 |
| amunizp | USB device serial number string: 372041756775 | 14:59 |
| amunizp | Detected USB device: RX-51 | 14:59 |
| amunizp | Error: Cannot find id for mmc block disk device | 14:59 |
| amunizp | Error: No device detected | 14:59 |
| amunizp | OK second time it did something! | 15:00 |
| amunizp | I updated wiki with the result. Thank you for your help @freemangordon and @Wizzup ! I will tidy up the wiki in a moment typsetting got messed up. | 15:11 |
| amunizp | hummm screen is very dim .. can't read it. | 15:13 |
| amunizp | oh wow lots of apps! | 15:19 |
| amunizp | OK screen went blank I assume that is the thing @Wizzup mentioned before about it being slow the first few boots. I have updated https://leste.maemo.org/Nokia_N900#Quick please review to see if it helps or hinders! | 15:31 |
| Wizzup | (sorry, still have people over, will try to get back to you, but looks like you got it running) | 15:33 |
| Wizzup | arno11 has a bunch more speed tweaks | 15:34 |
| freemangordon | amunizp: don't forget to expand rootfs | 15:34 |
| amunizp | freemangordon: Increase filesystem size | 15:56 |
| amunizp | Run the following script: /etc/expandcard.sh is this done inside the n900 ? I guess I need to use a terminal app that should be installed? | 15:56 |
| amunizp | humm for now I simply have the phone on some sort of standby wit the front LED blinking even when the power is removed. I can't seem to boot the n900. | 15:59 |
| gnarface | does it have enough charge? | 16:04 |
| gnarface | (random guess) | 16:09 |
| Wizzup | front light blinking makes me think it's turned on | 16:11 |
| Wizzup | when you say power removed, does that mean battery removed? | 16:11 |
| gnarface | i was just thinking that a pinephone boot-looping from too low battery charge could have the same symptoms, depending on what's installed | 16:14 |
| Wizzup | I haven't had this problem as long as I provide enough power | 16:16 |
| gnarface | yea, could be a symptom of a weak charger | 16:16 |
| gnarface | or a dead battery | 16:16 |
| gnarface | hypothetically | 16:16 |
| gnarface | (dead/heavily worn battery) | 16:16 |
| gnarface | like maybe if it had been sitting without a charge for too long? | 16:17 |
| gnarface | could be software too, i dunno | 16:17 |
| amunizp | power removed means unplugged. | 16:22 |
| amunizp | It was bootin g up before with the pin code. and it booted up once I selected SD. | 16:23 |
| amunizp | I then unplugged it from computer and that is where things went blank. | 16:23 |
| amunizp | OK /afk | 16:24 |
| gnarface | see if it works if you keep it plugged in to a power source maybe... | 16:26 |
| arno11 | amunizp: yes you have to run expandcard.sh from n900 | 16:52 |
| arno11 | you don't need any additional tool to install | 16:52 |
| arno11 | you already have all usual linux tool installed in Leste img | 16:53 |
| arno11 | you should dist-upgrade to -devel btw | 16:54 |
| arno11 | and white blinking LED is normal, it just means your screen is OFF | 16:54 |
| arno11 | and Leste running | 16:55 |
| arno11 | later i can privide you few tweaks to improve performance if you want | 16:55 |
| arno11 | *provide | 16:56 |
| arno11 | (you absolutely need to reboot after running expancard and avoid to connect to WiFi during the first boot) | 16:58 |
| unic0rn | Wizzup: conversations matched contact to a number when another message arrived, existing conversation was showing the number (messages were from before contact import), then it refreshed | 16:58 |
| arno11 | (you absolutely need to reboot after running expancard and avoid to connect to WiFi during the first boot) | 16:58 |
| arno11 | *sorry for double msg | 16:58 |
| arno11 | bbl | 16:59 |
| unic0rn | Wizzup: as for sphone, it's not matching the incoming call, nor recents. number has + with country code, then the rest. no spaces or dashes, just digits | 17:00 |
| unic0rn | basically, I made sure the number in the contact is written exactly the same as the one displayed when the contact is unknown | 17:01 |
| Wizzup | this might be due to my recent changes sicne you're on devel | 17:01 |
| Wizzup | I think with some of my fixes it gets better, but I'm still working on these | 17:01 |
| Wizzup | give me a day or two | 17:01 |
| moparisthebest | inky: actually OMEMO can be used to secure the keys for webrtc calls | 17:01 |
| unic0rn | no rush, I'm not using it for incoming calls anyway, just reporting when I find something | 17:02 |
| unic0rn | moparisthebest: not sure if anything changed, or if it was my setup, but for me OMEMO with 2 devices was a pain. always ended up seeing only half of the conversation on one of them when using the other one | 17:05 |
| moparisthebest | I think some early clients had that problem but not for years now | 17:06 |
| unic0rn | I suspect it's by design, and if so, it's well. suboptimal. | 17:06 |
| unic0rn | that was maybe... within last 2 years or so | 17:06 |
| moparisthebest | Though very possible pidgin is stuck 15 years in the past as it often is :'( | 17:06 |
| unic0rn | one client was conversation on android | 17:06 |
| unic0rn | the other didn't really matter, various | 17:06 |
| moparisthebest | Conversations 100% doesn't have that problem | 17:07 |
| unic0rn | pidgin, some macos-specific one | 17:07 |
| unic0rn | well it did for me | 17:07 |
| unic0rn | server was prosody | 17:07 |
| moparisthebest | The other will matter a lot if it doesn't encrypt for conversation's OMEMO key | 17:07 |
| unic0rn | ah, right. | 17:07 |
| moparisthebest | For the other try Dino, gajim, movim etc | 17:08 |
| unic0rn | I think I did actually try dino | 17:08 |
| unic0rn | dino, pidgin, and at least one else | 17:09 |
| unic0rn | but good to know it was client-specific issue | 17:09 |
| unic0rn | although maybe prosody config had a hand in this as well | 17:10 |
| amunizp | OK phone off with blinking light when not charging: I vaguely recall this happening and me needing to remove the battery and start over. | 20:25 |
| amunizp | OK good news! took battery out and the n900 boots up. Bad news it boots and asks for the pin again. It did not offer me to boot into the sd card. | 20:28 |
| dsc_ | Wizzup: https://git.kroket.io/sander/maemo-leste-kodi-remote | 20:41 |
| dsc_ | do the thing pls ;p | 20:41 |
| arno11 | amunizp: unfortunately it seems you didn't see my previous msg :( | 20:42 |
| arno11 | *msgs | 20:42 |
| arno11 | btw you need to keep your keyboard opened before pressing the power button | 20:43 |
| arno11 | to show the uboot menu | 20:44 |
| arno11 | white LED blanking is normal when your screen is OFF | 20:44 |
| dsc_ | arno11: pls test ;p https://git.kroket.io/sander/maemo-leste-kodi-remote | 20:45 |
| arno11 | *blinking | 20:45 |
| arno11 | dsc_: omg ! seems really cool | 20:47 |
| arno11 | my son currently uses kodi, let's try | 20:48 |
| dsc_ | ^^ | 20:48 |
| dsc_ | just pushed another commit because it wouldnt compile | 20:50 |
| dsc_ | this also works fine on desktop lol | 20:51 |
| arno11 | ok | 20:51 |
| dsc_ | cmake -Bbuild . | 20:52 |
| dsc_ | make -Cbuild -j1 | 20:52 |
| arno11 | ok | 20:53 |
| dsc_ | `sudo apt install -y curl nmap` too | 20:54 |
| dsc_ | (for auto-discovery) | 20:54 |
| arno11 | ok | 20:55 |
| arno11 | dsc_: sorry, got lot of missing deps, building now | 21:32 |
| Wizzup | please keep track of missing deps | 21:32 |
| Wizzup | we can use those when packaging | 21:32 |
| arno11 | ok no probs | 21:32 |
| dsc_ | the bulk of it should be defined here: https://git.kroket.io/sander/maemo-leste-kodi-remote/src/branch/master/debian/control | 21:33 |
| dsc_ | but maybe its still missing something | 21:33 |
| Wizzup | in that case arno11 can do cd maemo-leste-kodi-remote ; sudo apt-get build-dep . | 21:35 |
| * Wizzup should get a honorary DD title | 21:35 | |
| dsc_ | https://git.kroket.io/sander/maemo-leste-kodi-remote/src/branch/master/debian/rules#L12 | 21:35 |
| dsc_ | i dont know what `dh_installxsession` is but it probably shouldnt be there | 21:35 |
| sicelo | amunizp: I guess we can assume you didn't steal the device 😀 | 21:37 |
| sicelo | so we can share with you that it can be recovered. have a look at n900-rescueOS ... iirc it has a password feature | 21:38 |
| arno11 | dsc_: i stopped building @25% (too heavy for my N900 lol) | 21:41 |
| arno11 | sorry i just have my n900 around | 21:42 |
| arno11 | but seems to build fine | 21:42 |
| arno11 | i doublechecked and your control file is ok with deps | 21:43 |
| arno11 | (i just forgot to check before...) | 21:44 |
| dsc_ | hehehe | 21:44 |
| dsc_ | ok | 21:45 |
| arno11 | i' ll try to build again this time at 805MHz, just for fun and to see if n900 is still responsive | 21:49 |
| arno11 | dsc_: arghh really to much, i can't build but the good news are that N900 is still usable even on heavy heavy load with no freeze or reboot | 21:58 |
| * sicelo still hasn't tried overclocking his N900 | 21:59 | |
| arno11 | too bad | 21:59 |
| arno11 | :P | 21:59 |
| arno11 | sicelo: you can safely use boost mode if you set cpufreq powersaving mode first and then set max freq to 720 first and then ondemand mode | 22:01 |
| arno11 | and if it doesn't reboot, 805 or 850 are possible | 22:02 |
| arno11 | but i wonder why it doesn't work with higher freqs: on fremantle my device is stable @1GHz and works @1.1GHz but immediately reboot @900 with Leste | 22:05 |
| arno11 | ofc with similar voltages | 22:06 |
| arno11 | but honestly now, with last tweaks, overclock is only useful for video or other heavy loads | 22:07 |
| d4dsc | next step is water cooling | 22:43 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
