rinigus | mal 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 keys | 04:47 |
---|---|---|
rinigus | https://github.com/rinigus/hwcrypt is based on a tool which is a part of Android sources, so it was easy to make | 04:49 |
rinigus | mal 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 needed | 05:02 |
rinigus | I'll continue with working on overall stack and then can come back to hwcrypt binder based solution | 05:07 |
rinigus | Would 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 ram | 07:49 |
spiiroin | orange vs yellow.. but it kind of sounds it could be PatternDisplayResumeFailed ref: https://github.com/sailfishos/mce/blob/master/inifiles/debug-led.ini#L30 | 10:50 |
*** Daanct12 is now known as Danct12 | 10:51 | |
spiiroin | which 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 line | 10:52 |
spiiroin | I 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 |
rinigus | spiiroin: will try to look if I get the same. @lal883 ^ | 11:01 |
T42 | <lal883> Thanks @spiiroin, @rinigus. I am running the 32bit 4.0.1.48 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 logs | 12:28 |
rinigus | note 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 /home | 12: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 something | 13: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 Friday | 13:29 |
mal | hmm, very odd | 13: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 internet | 13:51 |
mighty17[m] | logcat - https://pastebin.ubuntu.com/p/GBCBSK3sbp/ | 13:51 |
mighty17[m] | i suppose the error is `Netd : Error adding IPv4 rule: Invalid argument` but i dont rly know | 13:51 |
T42 | <elros34> I doubt it will affect sailfish unless its issue at kernel level | 13:59 |
mal | mighty17[m]: you should be looking at journal, logcat is not that relevant for wifi | 14:01 |
mighty17[m] | @elros34 thats what im thinking, maybe i need to backport some patch to kernel | 14:05 |
mighty17[m] | mal: its still android, once it works there it will work in sfos ;) | 14:05 |
mal | oh | 14:05 |
mal | well android does things very differently to sailfish | 14:06 |
mighty17[m] | well what if its a kernel level issue? :0 | 14: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 is | 14: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 errors | 14:25 |
mighty17[m] | journalctl is better? i'd give it a go then, but then errors specific to sfos would arise | 14:28 |
mighty17[m] | if u remember the ones that happened before with me | 14:28 |
T42 | <elros34> on sailfish journalctl/dmesg will contains wifi related issues | 14:30 |
mighty17[m] | on android dmesg doesnt have anything wrong | 14: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 kernel | 14:41 |
mighty17[m] | rather than the stock 3.0 | 14: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: https://paste.ubuntu.com/p/9rfFp8WjRm/ | 15:53 |
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 it | 15:57 |
mighty17[m] | or wait this seems different | 15:57 |
mighty17[m] | `/srv/mer/toolings/SailfishOS-4.1//opt/cross/bin/armv7hl-meego-linux-gnueabi-ld: cannot open output file usergroupgen: Permission denied` sus | 15: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 |
rinigus | I made a new organization to work on encryption - https://github.com/sailfishos-encryption | 16:34 |
rinigus | moved hwcrypt and systemd-ask-password-gui over there | 16:34 |
rinigus | in addition, new repo was made with initial setup allowing you to boot into encrypted /home | 16:34 |
rinigus | you would just have to prepare /encrypted.img file (LUKS + ext4 expected) | 16:35 |
rinigus | feel free to join the fun - development / testing / issues | 16:36 |
rinigus | main repo for issues is https://github.com/sailfishos-encryption/sailfish-device-encryption-community | 16:37 |
T42 | <adampigg> rinigus: im sure we should have a project for these things ... eg sailfish-community with fpd and encryption in as a start | 17:01 |
rinigus | @adampigg: maybe. I don't mind that either... right now we have fpd, will get encryption | 17:02 |
rinigus | there is also keyboard project, but that has been for long in separate org | 17:03 |
rinigus | so, probably keyboard should stay as it is | 17:03 |
rinigus | @adampigg: I guess if we make -community, could we do it now? before encryption will start spreading? | 17:04 |
rinigus | although, 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 project | 17:06 |
rinigus | thinking 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 be | 17:07 |
rinigus | @adampigg: OK, let's make it as a separate one. we can later move if needed | 17:08 |
T42 | <adampigg> rinigus: ok, you make the project, and ill request sending fpd to it after ive taken my daughter out | 17:09 |
rinigus | @adampigg: will do | 17:09 |
rinigus | @adampigg: fun fact - sailfishos-community already taken. although the corresponding url doesn't open | 17:11 |
rinigus | mixed up - it does open https://github.com/sailfishos-community | 17:12 |
T42 | <adampigg> was about to say it opens here | 17:12 |
rinigus | go for a walk and we can discuss new name later :) | 17:13 |
rinigus | @adampigg ^ | 17:13 |
T42 | <adampigg> k | 17:13 |
T42 | <adampigg> while i fixup linux-hidl | 17: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 effort | 18: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 think | 19:14 |
T42 | <elros34> if you are only missing wifi on android then I would skip it and work with sailfish | 19:17 |
T42 | <Walid> i have problem with ril, this is logcat -b radio | 19:34 |
T42 | <Walid> https://pastebin.ubuntu.com/p/B3TPHmVrpP/ | 19:34 |
piggz | rinigus: sailfishos-ports ? | 20:18 |
rinigus | piggz: first impression is as if all ported devices are there | 20:19 |
rinigus | (rather late here, I'll better be off). let's continue tomorrow - no ideas on my side yet | 20:20 |
piggz | k, sleep on it | 20:47 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!