Monday, 2021-08-23

rinigusmal morning! Binder API would be nice and we could have both as well. All what is needed is a small command line tool allowing to manage and sign with the keys04:47
rinigus is based on a tool which is a part of Android sources, so it was easy to make04:49
rinigusmal I will have still to write scripts gluing it together. But if we have binder and hal tools with the same cmd line options, no changes in surrounding apps/scripts will be needed05:02
rinigusI'll continue with working on overall stack and then can come back to hwcrypt binder based solution05:07
rinigusWould have to read that newsletter explaining binder again, was a very nice description...05:08
T42<lal883> I have a Tama device which occasionally takes a while to unblank the display when I press the power button. An orange notification LED lights up (breathes) when I press the power button and after about 30 seconds screen turns on.07:38
T42<lal883> Any hint on how to debug or what does that breathing orange LED notification mean, when pressing power key?07:39
rinigus@lal883: I have not seen it for a while myself. I wonder what that orange LED means - maybe it is memory killer making its work? have you checked your device memory consumption? it seems like aosp10/aarch64 based port is using more ram07:49
spiiroinorange vs yellow.. but it kind of sounds it could be PatternDisplayResumeFailed ref:
*** Daanct12 is now known as Danct1210:51
spiiroinwhich would be unblank taking too long. which in old devices would point towards mce->kernel problems, but nowadays & depending on device type details it could be also along mce->compositor->android_hwc->kernel line10:52
spiiroinI guess severe memory starvation could be expected to cause delays in "few secs" range (need to page in stuff or stte), but half a minute. anything in logs?10:56
rinigusspiiroin: will try to look if I get the same. @lal883 ^11:01
T42<lal883> Thanks @spiiroin, @rinigus. I am running the 32bit now. Quite certain it is not the memory, some times have experienced this right after a reboot. I will check journal and dmesg the next time I get this and share. Any other logs I should look?11:22
rinigus@lal883: journal should include dmesg - assuming that the buffer was large enough. I suggest to set journal to persistent and increase ram/storage buffer to get full logs12:28
rinigusnote that this version is not supported anymore as we moved to the  new base. although, you may wish to delay the switch as I am working on storage encryption support that would probably will require reinstall or wiping /home12:29
rinigus@lal883 ^12:29
T42<lal883> @rinigus okay will try that. I can't make the switch until a few more weeks. Sounds about right to wait until encryption support. Saves me a reflash.12:49
T42<b100dian> turns out, the change I made yesterday evening that made SMSs pour in was.. switch from 4g to 3g. This can't really be an adaptation bug, can it? Most probably my carrier changed something13:15
mal@b100dian just wondering, from which country is your sim card?13:28
T42<b100dian> Vodafone Romania. Used to work till last Thursday or Friday13:29
malhmm, very odd13:30
mighty17[m]hey, can anyone here help with android, which can affect sfos port as well, so issue is im porting oreo to my device and wifi connects but shows no internet13:51
mighty17[m]logcat -
mighty17[m]i suppose the error is `Netd    : Error adding IPv4 rule: Invalid argument` but i dont rly know13:51
T42<elros34> I doubt it will affect sailfish unless its issue at kernel level13:59
malmighty17[m]: you should be looking at journal, logcat is not that relevant for wifi14:01
mighty17[m]@elros34 thats what im thinking, maybe i need to backport some patch to kernel14:05
mighty17[m]mal: its still android, once it works there it will work in sfos ;)14:05
malwell android does things very differently to sailfish14:06
mighty17[m]well what if its a kernel level issue? :014:06
T42<elros34> then you can debug it at sailfish too:)14:07
mighty17[m]i cannot seem to find the source from where it is14:07
mighty17[m]Well debugging in sailfish is fine but well I'll need to grab the Oreo hadk, isn't it better to get android working first then sfos?14:22
T42<elros34> I only meant wifi because AFAIK there is no any wifi android layer used used on sailfish. There is little  point to fight against logcat: android side errors14:25
mighty17[m]journalctl is better? i'd give it a go then, but then errors specific to sfos would arise14:28
mighty17[m]if u remember the ones that happened before with me14:28
T42<elros34> on sailfish journalctl/dmesg will contains wifi related issues14:30
mighty17[m]on android dmesg doesnt have anything wrong14:31
T42<elros34> btw do you want achieve anything special by upgrading android base?14:35
mighty17[m]nougat is gonna get outdated soon isnt it?14:41
mighty17[m]@elros34 plus with oreo im using a newer 3.4 kernel14:41
mighty17[m]rather than the stock 3.014:42
mighty17[m] * marshmallow* is gonna get outdated soon isnt it?14:50
T42<edp_17> Hi all! I am building SFOS 4.1 for N7000 (CM14.1 base) and when building droid-hal, I am getting this error:
T42<edp_17> I've updated all sub-modules, and all other modules in mw.15:54
T42<edp_17> Anyone has idea how to solve this?15:55
mighty17[m]@edp_17 for whats happened with me, i did a clean build and it fixed it15:57
mighty17[m]or wait this seems different15:57
mighty17[m]`/srv/mer/toolings/SailfishOS-4.1//opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: cannot open output file usergroupgen: Permission denied`  sus15:58
T42<edp_17> I manually built every package one by one and where it didn't build I did a clean up or deleted/re-cloned the package again. That solved all issues so far but I don't know how to solve this one. Never seen before.16:05
T42<Shirley Bell> Forwarded from unknown: 𝚃𝚑𝚊𝚗𝚔 𝚢𝚘𝚞 𝚏𝚘𝚛 𝚋𝚎𝚒𝚗𝚐 𝚜𝚘 𝚐𝚎𝚗𝚎𝚛𝚘𝚞𝚜, 𝚝𝚑𝚘𝚞𝚐𝚑𝚝𝚏𝚞𝚕 𝚊𝚗𝚍 𝚜𝚘 𝚝𝚛𝚞𝚎. 𝚆𝚒𝚝𝚑 $1000 𝚜𝚝𝚊𝚛𝚝-𝚞𝚙 𝚒 𝚖𝚊𝚍𝚎 $7000 𝚃𝚑𝚊𝚗𝚔 𝚢𝚘𝚞 𝚏𝚘𝚛 𝚔𝚎𝚎𝚙𝚒𝚗𝚐 𝚢𝚘𝚞𝚛 𝚠𝚘𝚛𝚍𝚜 𝚊𝚗𝚍 𝚋𝚎𝚒𝚗�16:30
rinigusI made a new organization to work on encryption -
rinigusmoved hwcrypt and systemd-ask-password-gui over there16:34
rinigusin addition, new repo was made with initial setup allowing you to boot into encrypted /home16:34
rinigusyou would just have to prepare /encrypted.img file (LUKS + ext4 expected)16:35
rinigusfeel free to join the fun - development / testing / issues16:36
rinigusmain repo for issues is
T42<adampigg> rinigus: im sure we should have a project for these things ... eg sailfish-community with fpd and encryption in as a start17:01
rinigus@adampigg: maybe. I don't mind that either... right now we have fpd, will get encryption17:02
rinigusthere is also keyboard project, but that has been for long in separate org17:03
rinigusso, probably keyboard should stay as it is17:03
rinigus@adampigg: I guess if we make -community, could we do it now? before encryption will start spreading?17:04
rinigusalthough, we still have mer-hybris and sailfishos. while under jolla control, maybe it is ok to make there as well.17:05
rinigus... or they will disappear in this massive hub as sailfishos?17:05
T42<adampigg> im not sure community adaptation specific parts would be easy for us to manage under a jolla controlled project17:06
rinigusthinking loud - sailfishos does not fit as it is a better and opened source implementation of fpd and other things to come :) . but not official which is probably what that sailfishos should be17:07
rinigus@adampigg: OK, let's make it as a separate one. we can later move if needed17:08
T42<adampigg> rinigus: ok, you make the project, and ill request sending fpd to it after ive taken my daughter out17:09
rinigus@adampigg: will do17:09
rinigus@adampigg: fun fact - sailfishos-community already taken. although the corresponding url doesn't open17:11
rinigusmixed up - it does open
T42<adampigg> was about to say it opens here17:12
rinigusgo for a walk and we can discuss new name later :)17:13
rinigus@adampigg ^17:13
T42<adampigg> k17:13
T42<adampigg> while i fixup linux-hidl17:14
T42<elros34> mighty17[m]  I see nothing wrong with stable but outdated android base but 3.0 > 3.4 kernel is definitely worth the effort18:45
mighty17[m]so yeah @elros34 continue android or try to get sfos working now?19:14
mighty17[m]tbh 3.4 will need more patches for 3.4 i think19:14
T42<elros34> if you are only missing wifi on android then I would skip it and work with sailfish19:17
T42<Walid> i have problem with ril, this is logcat -b radio19:34
piggzrinigus: sailfishos-ports ?20:18
riniguspiggz: first impression is as if all ported devices are there20:19
rinigus(rather late here, I'll better be off). let's continue tomorrow - no ideas on my side yet20:20
piggzk, sleep on it20:47

Generated by 2.17.1 by Marius Gedminas - find it at!