| lotheac | Thaodan: https://github.com/sailfishos/android-tools-hadk/pull/8 | 03:35 |
|---|---|---|
| lotheac | b100dian: you're right of course :) | 03:35 |
| lotheac | Thaodan: and thanks for the zypper tips | 04:04 |
| T42 | <LSolrac> Hello. Pardon me asking silly questions but, are are there ports for Sony edo devices (1II, 5II)? If so, what might their status be? | 04:05 |
| T42 | <Spidey24Z> @elros34 so i revert 0047-hybris-Do-not-SetupMountNamespaces.patch still lipstick failed because of libandroidicu.so not found here's dmesg https://pastebin.com/8z42f8XP and journalctl https://pastebin.com/CZDmmxrm logcat still not found | 05:41 |
| T42 | <elros34> what about error you had previously and failing apexd?Just fix that libandroidiscu.so, you should already know how to do this | 05:47 |
| T42 | <Spidey24Z> you said i had to revert this patch to fix apexd | 05:49 |
| T42 | <elros34> no really, anyway I just read it myself so enter_default_mount_ns still fails but no idea if apexd too ( log is too short). What did you rebuild after making changes to sources? | 05:54 |
| T42 | <Spidey24Z> i rebuild all | 05:55 |
| T42 | <elros34> what does it mean? make hybris-hal builds something? Did you package droid-hal? | 05:56 |
| T42 | <Spidey24Z> @kquote03 he build it and yes he make clean and build everything again | 05:58 |
| T42 | <elros34> so /system/bin/getprop works now or not? | 05:59 |
| T42 | <Spidey24Z> even i tried to copy libandroidiscu.so to /odm/lib64 still not found | 06:00 |
| T42 | <Spidey24Z> no it's not also logcat not found (re @elros34: so /system/bin/getpr...) | 06:00 |
| T42 | <elros34> so again what about apexd, does it exit with 1 exit code like previously? What about linker symlinks, are they valid now? Just report what changed (if anything)... | 06:02 |
| T42 | <Spidey24Z> still exit 1 and i think there's no changes | 06:04 |
| T42 | <elros34> so I guess linker symlinks are still not valid | 06:08 |
| T42 | <Spidey24Z> yes because it's symlinks to /apex/ | 06:10 |
| T42 | <elros34> have you tried to unpack/mount this problematic apexd on pc? Are other apex also ampty? | 06:23 |
| T42 | <Spidey24Z> they are mounted on lineage os without errors | 06:24 |
| T42 | <Spidey24Z> all apex in sfos is empty | 06:24 |
| T42 | <Spidey24Z> you see in log that apex mounted but nothing in apex folder | 06:25 |
| T42 | <Spidey24Z> [ 21.190904] apexd: Activated 4 packages. Skipped: 2 | 06:29 |
| T42 | <Spidey24Z> [ 21.191814] apexd: Marking APEXd as ready | 06:29 |
| T42 | <elros34> why some services which should be disabled starts in your logs? What was link your github repo? | 06:55 |
| piggz | lbt: around? | 08:36 |
| T42 | <Spidey24Z> @elros34 like what and i will disable it | 11:08 |
| T42 | <Spidey24Z> @elros34 repo https://github.com/aymanrgab/droid-config-a5y17lte.git | 11:11 |
| voidanix[m] | Thaodan: what are fimage.img001 and vendor.img001 in kumano's kickstart? starting to think these break mic in 4.4.0 | 11:16 |
| T42 | <edp_17> Hi all. Is it possible to build older releases with new targets and toolings? Example: I do have 4.3 targets and toolings. Can I build sfos 4.1 with this or I need to use the version specific targets and toolings? Thanks. | 12:06 |
| T42 | <edp_17> Another question. On OBS, if I uploaded droid-hal-$DEVICE packages for sfos 4.3, can I use them to build 4.2? | 12:24 |
| mal | I think those should work, only if some big changes happen in packaging side it would cause issues | 12:46 |
| Thaodan | mal: Do packages build locally for 4.3 already use zstd? If not that using them on 4.2 should be fine in this case. | 12:57 |
| mal | Thaodan: afaik zstd support was added in 4.4 and will be taken into use for package builds in next release after that | 13:00 |
| mal | which means no issues for now | 13:01 |
| Thaodan | ok | 13:06 |
| T42 | <edp_17> Thanks guys. It seems there is a problem with droidmedia, gmp- and gst-droid. For 4.3 we don't need to build gmp- and gst-droid but for 4.2 they are required. :) | 14:55 |
| T42 | <adampigg> *you dont need to build them, as long as you dont patch them :D | 15:12 |
| T42 | <edp_17> @adampigg : I've let OBS build 4.2 packages using the uploaded droid-hal 4.3 rpm files. Then, locally I've tried to create a 4.2 image using the OBS repo but it failed as couldn't find the gmp-droid package. This is why I think, for 4.2 gmp- and gst-droid packages should have been built on OBS. | 15:21 |
| T42 | <adampigg> sure | 15:21 |
| T42 | <edp_17> When I tried to build gmp- and gst-droid on OBS, they both went to 'unresolvable' because the missing droidmedia-devel package. (I didn't get generated when I built droiedmedia for 4.3.) | 15:22 |
| T42 | <edp_17> So, potentially it could be possible for using newer toolings and targets for building older versions but in this particular example it seems I do need to build droid-hal and droidmedia packages for the older version then upload them to OBS. Then I will be able to build a 4.2 image. I think. :) | 15:25 |
| T42 | <kquote03> hello | 15:53 |
| T42 | <kquote03> it seems /apex/android.runtime was empty | 15:53 |
| T42 | <kquote03> so we deleted it and symlinked com.android.runtime.release in its place | 15:53 |
| T42 | <kquote03> now droid-hal-init is getting killed https://pastebin.ubuntu.com/p/mM7QKgpdSN/ (output of dmesg | grep droid-hal) | 15:54 |
| T42 | <kquote03> now /system/bin/logcat executes but throws a "logcat read failure" error (re @kquote03: so we deleted it and...) | 15:55 |
| T42 | <kquote03> strace of logcat https://pastebin.ubuntu.com/p/RfwhdZ4xQx/ | 15:56 |
| T42 | <elros34> @Spidey24Z this is not up-to-date repo according to your logs | 17:53 |
| T42 | <kquote03> we're currently building on 4.3.0.15 because Ayman already had it working on hybris16 (re @elros34: @Spidey24Z this is n...) | 17:54 |
| T42 | <kquote03> so we're 100% it works.. at least that's out logic | 17:54 |
| T42 | <kquote03> so we're 100% sure it works.. at least that's out logic (edited) | 17:55 |
| T42 | <kquote03> so we're 100% sure it works.. at least that's our logic (edited) | 17:55 |
| T42 | <elros34> I am talking about outdated droid-config in github which he links me | 17:55 |
| T42 | <kquote03> Ah, sorry for misinterpreting | 17:55 |
| T42 | <kquote03> btw, we reapplied patch 0047, wtihout it droid-hal wouldnt even start | 17:57 |
| T42 | <elros34> according to logs you showed me previously droid-hal-init was started without patch | 17:57 |
| T42 | <kquote03> I will reverse it again, seems i missed that (re @elros34: according to logs yo...) | 17:58 |
| T42 | <elros34> According to @Spidey24Z it change nothing then there is no point but I didn't see full logs | 18:01 |
| T42 | <kquote03> Alright, thanks (re @elros34: According to @Spidey...) | 19:13 |
| T42 | <kquote03> btw is there a way to start apexd manually? | 19:13 |
| T42 | <kquote03> running /system/bin/apexd manually seems perfectly fine but it crashes/exits (SIGIOT) when started by droid-hal | 22:44 |
| mal | which android base? | 23:32 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!