Monday, 2021-09-13

rinigusKeto: I wonder how it is resolved for Tama devices - we switched from AOSP9/32-bit to AOSP10/64-bit. I don't remember any complaints from those who stayed on AOSP9/32bit version. but maybe they are minority and don't expect that store would work08:10
piggzrinigus: yeah, I was wondering about your case with that08:11
rinigusssu s gives Xperia XZ2 (h8216 / h8216), for example. there are more in that family08:12
riniguspiggz: I know that it had to be enabled, but that's all I know about it regarding 64bit version08:12
Ketorinigus: the only problem is that it shows apps that have 32bit package available, and if some don't have 64bit available, then the install will fail for those08:16
piggzah, so it will install the correct arch08:21
rinigusKeto: true, that's exactly what happens11:29
T42_<Donald Wysocki> Forwarded from unknown: https://t.me/joinchat/MUP1XAQw5WMxMzM011:49
atlochowskirinigus probably most of Tama users don't use Jolla store but Openrepos12:43
rinigusatlochowski: could be. but we can install apps from the store as well - it is just sometimes we get an error if the installed app is not available in correct arch. I presume that correctly configured store would not show them12:44
atlochowskiI get it. I just wrote the reason why Tama users doesn't complain. Fo sure it's better when it's configured for 64bit for current port.12:47
rinigus:)12:49
stephgI just bought a 10iii :)13:12
piggzstephg: long time!13:24
T42_<lal883> I had earlier dropped a message here that a Tama device was not turning the screen ON some times when pressing the power key, but was showing a breathing Yellow/Orange notification LED indefinitely. Turns out it was because of the SD card, and removing/reinserting it fixed the problem.13:28
stephgpiggz: yeah, hope you and yours all ok13:35
stephgsame to everyone here too obvs13:35
rinigusI wonder whether we have some trick to mark a file as %config(noreplace) in droid-config sparse? otherwise I am getting encryption (sfos-open edition) setup reset on every OTA :(14:08
piggzrinigus: maybe move the dynamic part which changes into another file?14:38
riniguspiggz: yes, was thinking the same. will create config.ini that will be dynamic14:39
ThaodanMaybe split the dynamic and the static part up?15:35
rinigusThaodan and piggz: I ended up filling /etc/.../config.ini from devices.ini and having config.ini reflecting current state of filesystems (encrypted, plain, or reset). here, "filling" means that keys defined in devices.ini will be copied to config.ini iff they are missing there.16:00
riniguswhich allows to define new devices if needed, but would keep user config intact16:01
rinigusmal: I wonder whether you checked/asked about Device /dev/sailfish/home does not exist... message?16:02
malrinigus: not yet16:07
piggzrinigus: whats the current state? suitable for testing? what should I read?16:24
riniguspiggz: should be suitable for testing17:28
rinigushttps://github.com/sailfishos-open/sailfish-device-encryption-community README and Setup.md17:29
rinigusthe issue with OTA is fixed, just rebuilding package in OBS AOSP10 Tama17:30
rinigusall required packages are listed in Setup.md . I will work on hwcrypt and its integration to GUI. currently plain text passwords should work17:31
riniguspiggz: ^17:31
Thaodanrinigus: install package provided configs to /usr/lib not etc that solves it and follows similar changes in systemd and co17:44
rinigusThaodan: for reference, we are talking about https://github.com/sailfishos-sony-tama/droid-config-sony-tama-pie/blob/hybris-10/sparse/etc/sailfish-device-encryption-community/devices.ini17:48
rinigusit feels strange to me to have it in /usr/lib, although I follow your thought17:49
rinigusright now I have that file as distro-provided and config.ini as a local mod. both are in /etc. but may get confusing to some. as well as having some in /usr/lib in my mind17:50
piggzrinigus: thx ... just been fighting with my internet/dns ... severl reboots of the mesh network, on the grounds that "the nas never fails" (which runs the dns) ... and, it turned out to be the NAS!18:10
piggzrinigus: flypig was pursuaded to submit to chum18:26
riniguspiggz: nice! we still have to generate this package list for all to see. and openrepos integration became rather quiet...18:28
riniguspiggz: are you reviewing flypig submission? or should I take it?18:28
piggzyeah, was thinking about the integration...18:28
piggzi already reviewed and added18:29
rinigusnot sure we can do much on our side - waiting for basil response ... I'll ping in the thread18:30
piggzrinigus: libargon2 move to chum?18:44
riniguspiggz: we have it there already. it was a part of keepass packages18:45
rinigusso, for simplicity, I just nicked it from chum18:45
piggzok, i already depend on chum in device adaptation18:45
riniguspiggz: I think it is a good idea. how did you add that? community-adaptation fork?18:46
rinigusmaybe I should do the same and allow users to install from there directly18:47
piggzrinigus: you made me think there.....18:51
piggzas it turns out, tinyxml2 is static, so only a build dep, so i dont need to install the repo18:51
riniguspiggz: if all goes well, we can move these -open dependencies to :common. but making it all work  would have to be first18:58
piggzrinigus: was about to say that! it seems like most could live in common18:58
riniguspiggz: hwcrypt got updated. fixed a bug and added one command for it. but don't rush to update it yet - maybe something more will be needed.19:01
itexhello, i have a question, when i am making the local manifest file, i have replaced cynogenmod with lineageos but it does not seem to work, I have not idea what I should write it to19:04
itexhere is my file https://0x0.st/-xJB.xml19:05
T42_<elros34> itex: open your device repo github page, find correct branch you want to use then add other device specific repos according to lineage.dependencies file19:12
itexthank you19:12
T42_<elros34> like https://github.com/LineageOS/android_device_samsung_zeroltexx/blob/cm-14.1/lineage.dependencies19:12
T42_<elros34> you will find similar file in that zero-common repo too19:13
riniguspiggz: just be aware that /home will be formatted during the next boot after install of encryption packages. so, if you have some data there - move it away first19:22
piggzrinigus: i need to re-flash and change to home_open anyway19:25
piggzrinigus: do youwant this for instructions? https://paste.mozilla.org/XX3HYQA319:26
riniguspiggz: yes, sure! PR? or I just paste it in?19:27
piggzjust paste it in19:27
riniguspiggz: done and available at github repo. thanks!19:34
itexhmm does they ask you to test the android rom just to see if everything works? or flashing lineage os is required?20:03
T42_<elros34> both20:12
malrinigus: I didn't yet find the exact place where that message is triggered, I'm check more tomorrow20:13
itexok20:13
itexthe thing is that i am struggling to find the official version 15.1 for my pĥone20:22
T42_<elros34> 15.1? in your manifest file I saw 14.1. If unoffical provide sources then should be fine too20:56
piggzrinigus: all changes in, will test image tomorrow21:25

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!