| Ingvix | I've been wondering a bit how does one go about trying to make a port with postmarketos kernel. Like I know how to get the kernel sources and sfos rootfs but I'm not quite experienced enough to know how do I sort of put in the glue and stuff them into the device | 00:51 |
|---|---|---|
| Ingvix | so that it would actually work, that is | 01:00 |
| *** kimmoli_ is now known as kimmoli | 03:45 | |
| kquote03 | Thaodan: Is there a way to ignore this dependency? Because it seems to be needed for only Android < 8 | 07:37 |
| T42 | <elros34> if you looks at commit history then building older version of ril-binder-plugin might help but why did you even build it again? | 08:14 |
| kquote03[m] | T42: because building --mic failed and it mentioned something about ofono | 08:15 |
| T42 | <elros34> I meant that you had working image previosly so there was no point to build any of middleware package anymore | 08:17 |
| kquote03 | i am building again because i forgot to specify android_major_version | 08:19 |
| T42 | <elros34> yeah but you forgot it in droid-config so you should only rebuild droid-config | 08:19 |
| kquote03 | i did | 08:19 |
| kquote03 | but then when building with --mic, it failed | 08:20 |
| T42 | <elros34> ok anyway, I just want to be sure that you did not waste time rebuilding mw all the time | 08:21 |
| kquote03 | nah im wasting time building --mic all the time :P | 08:22 |
| T42 | <elros34> that also can be avoided usually. You can copy built packages to device and install them manually | 08:24 |
| T42 | <sturai> Hi, I am interesting in installing SFOS in one of my devices. I have a Redmi Note 9 pro from Xiaomi and also another Xiaomi Mi A3 that I have read there is some recent work on it. Another device that I have is a Huawei P8 lite 2017 that I've found as listed at https://wiki.merproject.org/wiki/Adaptations/libhybris. I would like to now if I could try SFOS on any of this devices before I buy a Sony 10 ii or iii in the near future. Thanks. | 08:42 |
| kquote03[m] | can you install LOS on this device? | 08:43 |
| kquote03[m] | s/LOS/LineageOS/, s/this/these/, s/device/devices/ | 08:43 |
| kquote03[m] | you dont need LOS, I think vanilla android can work fine too btw | 08:44 |
| T42 | <sturai> I have just installed LineageOS and at this precise moment is at 90% doing the update to latest version of LineageOS. | 08:46 |
| kquote03[m] | T42: which version of Lineage? | 08:47 |
| kquote03[m] | you need 17.1 or older | 08:47 |
| T42 | <sturai> I flashed https://github.com/MasterAwesome/android_device_xiaomi_laurel_sprout/releases/tag/v10.1.0 | 08:48 |
| kquote03[m] | alright good they have a lineage 17.1 branch | 08:49 |
| kquote03[m] | Start by reading the pdf | 08:49 |
| kquote03[m] | https://sailfishos.org/content/uploads/2021/06/SailfishOS-HardwareAdaptationDevelopmentKit-4.1.0.0.pdf | 08:50 |
| kquote03[m] | should be mostly straight forward, but if you get stuck dont shy from asking for help | 08:50 |
| T42 | <sturai> Thank you | 08:51 |
| T42 | <sturai> I will try. It would be great that I can start using SFOS. | 08:52 |
| kquote03[m] | T42: I wouldn't say that you will immediately start using it (depends entirely on your skill+luck) | 08:52 |
| T42 | <sturai> haha | 08:52 |
| kquote03[m] | plus most likely there will be stuff like audio, cellular, etc that will require manual intervention | 08:53 |
| kquote03[m] | but if you persevere, you can get it working good of course. | 08:53 |
| T42 | <sturai> I had read yesterday about this try. Let's see. (re @SailfishFreenodeIRCBridgeBot: <mint[m]>Good evenin...) | 08:54 |
| kquote03[m] | T42: All in all, good luck! | 08:55 |
| T42 | <sturai> It's a good encouragement to read that with perseverance it could work good. That's a start. | 08:55 |
| kquote03[m] | if others can port it, then why cant we? | 08:56 |
| T42 | <sturai> Well, about the Huawei P8 lite that is listed on https://wiki.merproject.org/wiki/Adaptations/libhybris | 08:59 |
| T42 | <sturai> Wouldn't it be easier to do it to that model? I would quickly think that devices listed on libhybris wiki would be some kind of download and flash ready. Or to be listed there does not assure anything? | 08:59 |
| T42 | <elros34> If device is there then it should be ready to at least try. I suggest you to search for existing port on xda or other places if there is no link at mer wiki | 09:00 |
| T42 | <elros34> I think somebody worked with mi a3, search for droid-config-<device codename> on github then maybe you will find some instruction and persone who maintain it | 09:04 |
| T42 | <sturai> Thank you Elros. I have to decide between a Huawei that is listed but unlocked...with the unlocking process being unknown to me, but with Huawei I think it implies a hard process with physical intervention on the phone, not just fastboot and so on...and on the other way a Xiaomi that I have just installed Lineage OS on it. | 09:08 |
| T42 | <sturai> Yes, I started the week finding https://github.com/Sailfish-OS-Mi-A3 but I didn't know a lot about flashing and so on. I have just flashed LineageOS to the Mi A3 but I didn't know how it went with SFOS. Actually LineageOS for the MiA3 wasn't exactly an official port...so I thought it related to the SFOS porting outside the Sonies, including the Tamas | 09:08 |
| T42 | <sturai> Thank you Elros. I have to decide between a Huawei that is listed but unlocked...with the unlocking process being unknown to me, but with Huawei I think it implies a hard process with physical intervention on the phone, not just fastboot and so on...and on the other way a Xiaomi that I have just installed Lineage OS on it. | 09:10 |
| T42 | <sturai> Yes, I started the week finding https://github.com/Sailfish-OS-Mi-A3 but I didn't know a lot about flashing and so on. I have just flashed LineageOS to the Mi A3 but I didn't know how it went with SFOS. Actually LineageOS for the MiA3 wasn't exactly an official port...so I thought it related to the SFOS porting outside the Sonies, including the Tamas. I mean that these Xiaomi ports of SFOS are Community community...efforts. (edited) | 09:10 |
| T42 | <elros34> so based on mi-a3 repos it's far from ready to use | 09:12 |
| T42 | <sturai> 😐 | 09:17 |
| T42 | <sturai> Well, I was expecting this...sadly. Would you think it would be easier to try on the Huawei P8 lite even if some things doesn't work. I am interesting in trying the interface before I decide if I will go for a Sony or Volla X for Xmass...or the Black Friday that is nigh. | 09:17 |
| T42 | <sturai> Anyway to involve myself a bit on the porting to A3 would be a interesting journey. | 09:17 |
| T42 | <sturai> Anyway to involve myself a bit on the porting to A3 would be a interesting journey. But as a enrichment process. (edited) | 09:18 |
| T42 | <sturai> Anyway to involve myself a bit on the porting to A3 would be a interesting journey. But as a enrichment process more than a efficient one (edited) | 09:18 |
| T42 | <sturai> Anyway to involve myself a bit on the porting to A3 would be a interesting journey. But as a enrichment process more than an efficient one. (edited) | 09:18 |
| T42 | <sturai> Thank you for your warm responses. | 09:19 |
| T42 | <elros34> no idea which device will be easier, make sure the one you choose have well working lineage os <= 17 otherwise it will be harder | 09:23 |
| T42 | <sturai> Gracias | 09:24 |
| T42 | <oMinimalist> [jolla-3.4.0.24|https://releases.jolla.com/releases/3.4.0.24/jolla/armv7hl/] Valid metadata not found at specified URL | 09:34 |
| T42 | <oMinimalist> How I can get which release still under https://releases.jolla.com/releases/ ? | 09:34 |
| T42 | <elros34> I think 3.4 should still be fine, maybe some temporary issue? What are you trying to achieve? | 09:45 |
| T42 | <oMinimalist> Unable to find pattern: Jolla Configuration cancro (re @elros34: I think 3.4 should s...) | 09:53 |
| T42 | <elros34> you need to be more verbose of what you are trying to do. I guess you are making sfos image? Then pastebin whole output from mic | 09:55 |
| T42 | <oMinimalist> I build sfos image, now this is the repo of ks file . : https://irc.thaodan.de/.imgstore/198ec636/file_2890.jpg | 09:57 |
| T42 | <oMinimalist> https://irc.thaodan.de/.imgstore/d6c74ca8/file_2891.jpg | 09:58 |
| T42 | <elros34> next time use paste services | 09:58 |
| T42 | <elros34> and past full output including command you are executing. Did you run mic manually?. Why do you build such an old release? You have defined 3.1 instead 3.4 release in one url | 10:01 |
| T42 | <oMinimalist> Sorry. I can't find 3.4 release of https://releases.jolla.com/releases/ | 10:04 |
| T42 | <oMinimalist> yes, manully, just like https://gitlab.com/sailfishos-porters-ci/cancro-ci/-/blob/master/run-mic.sh (re @elros34: and past full output...) | 10:05 |
| T42 | <elros34> did you build manually droid-hal/config and other packages because you only have local repo defined | 10:09 |
| T42 | <elros34> also you can't mix up jolla 3.1 with other 3.4 repos | 10:09 |
| T42 | <oMinimalist> Yes , I have done it. (re @elros34: did you build manual...) | 10:17 |
| T42 | <elros34> did you use latest droid-config/hal submodules? That will probably do not work, you will have to downgrade. I will ask again why do you build such an old release if you already build packages then why not update port to 4.2? Building old release is always pain because you need to build proper version of many packages | 10:19 |
| T42 | <oMinimalist> Because the android-base of cancro which on the github is too old. I can't update it for latest sdk. | 10:22 |
| kquote03[m] | I now get this error when running --mic https://susepaste.org/40822108 | 10:24 |
| T42 | <elros34> @oMinimalist sure you can, latest sailfish works fine with cm/lineage 11-17 android bases fine | 10:26 |
| kquote03[m] | here's droid-hal-a5y17lte.log https://susepaste.org/99220229 | 10:27 |
| Ingvix | so anyone around that has experience with porting sfos on mainline kernel? I'd be sort of in the need of light guidance on what parts to I could possibly skip following the hadk doc while having already tailored kernel for the device and what I might need to do differently | 10:36 |
| Ingvix | or do I even get to skip anything other than maybe some kernel configuring | 10:38 |
| piggz | Ingvix: yes, pinephone port | 10:38 |
| piggz | also, another dev did a generic x64 port | 10:38 |
| Ingvix | ah, nice | 10:39 |
| piggz | Ingvix: in summary, you can skip the hal/dhd parts, and have to build your own kernel ... do the droid-config parts and specify in there your kernel package ...the rest is quite similar | 10:39 |
| piggz | Ingvix: on pinephone, we build all packages, including the kernel on OBS | 10:40 |
| piggz | https://build.sailfishos.org/project/show/nemo:devel:hw:pine:dontbeevil | 10:40 |
| Ingvix | hmm, what do mean by all packages? | 10:41 |
| Ingvix | all the base system packages? | 10:41 |
| piggz | Ingvix: no, just the middleware/configs ... base packages are supplied by jolla | 10:42 |
| kquote03[m] | which dir does --mic install rpms to? | 10:42 |
| Ingvix | I see | 10:42 |
| Ingvix | well, thanks for the tips. I'll see how far do I get with this and ask if I face any issues | 10:43 |
| piggz | sure | 10:44 |
| kquote03[m] | alright i renamed the file it was complaining about and rebuilt --configs. now it works | 10:49 |
| kquote03[m] | logcat works | 11:32 |
| mal | I have ported sailfish to qualcomm device with mainline kernel | 11:36 |
| Ingvix | alright, so I can also be bothering you if I happen to face issues | 11:50 |
| kquote03 | logCAT output https://susepaste.org/18567826 | 11:59 |
| T42 | <elros34> have you checked that ueventd*rc is in out/target/product/$DEVICE/root/ according to porting notes? | 12:04 |
| Thaodan | Ingvix mal: he could also have some ideas: https://twitter.com/calebccff/status/1450987497295683591 | 12:08 |
| kquote03 | elros34: I ran `make modules ` , i then searched for 'fstab' and 'uevent' but found nothing. https://susepaste.org/75446784 | 14:23 |
| kquote03 | is there a way to change the permission of /dev/*binder* before droid-hal-init loads? | 14:31 |
| T42 | <elros34> there other steps to do like searching for ueventd in device/*/* or on device /vendor itself. Have you tried it also? | 14:34 |
| kquote03 | oh i havent | 14:34 |
| kquote03 | ill try now | 14:34 |
| T42 | <elros34> frankly I am not sure what usually set /dev/*binder permissions | 14:36 |
| kquote03 | that's ok because it seems to be the effect of another issue | 14:36 |
| kquote03 | anyways i found ./device/samsung/universal7880-common/ramdisk/ueventd.samsungexynos7880.rc | 14:37 |
| kquote03 | ill copy that to out/target/product/$DEVICE/root/ and rebuild kernel, correct? | 14:37 |
| T42 | <elros34> no, droid-hal | 14:38 |
| kquote03 | alright thanks | 14:38 |
| T42 | <elros34> I am not sure that it will help for binder, did you update your droid repos on github? | 14:40 |
| kquote03 | no, but i can now | 14:40 |
| kquote03 | Alright I updated my git repos | 14:58 |
| kquote03 | here's droid-hal | 14:58 |
| kquote03 | https://github.com/kquote03/droid-hal-a5y17lte | 14:58 |
| kquote03 | does ofono-ril-binder-plugin not being build have anything to do with the error? | 15:06 |
| kquote03 | wait wut | 15:07 |
| kquote03 | ah nvm i thought it was gonna build, but it failed with the same conflict. I tried building ofono-ril-plugin manually but it failed | 15:07 |
| T42 | <elros34> build 2 comits older ofono-ril-binder-plugin instead. Are you sure that ypu pushed everything to github, I do not see sparse/selinux | 15:20 |
| T42 | <elros34> sparse/etc/selinux* | 15:21 |
| kquote03 | omg i put the sparse folder on hadk\hybris\droid-configs | 15:25 |
| kquote03 | holy #### i think i messed up everything | 15:27 |
| kquote03 | omggg github is down | 15:38 |
| kquote03 | welp, guess it's my fault for not hosting my own gitlab | 15:39 |
| kquote03 | github undown | 15:42 |
| kquote03 | alright i update the config repo | 15:46 |
| kquote03 | ill try rebuilding the rpms | 15:46 |
| T42 | <elros34> I think you need to replace symlinks form sparse/etc/selinux with actual files: https://github.com/kquote03/droid-config-a5y17lte/blob/master/sparse/etc/selinux/minimum/contexts/files/file_contexts | 15:51 |
| T42 | <Stellar_Eagle> https://github.com/SailfishOS-MI-A2/local_manifests/wiki/Build-notes-SFOS-4.0.1-hybris-16.0-armv7hl gives a clue about gst-droid commands that can successfully be used by changing HEAD for ofono-ril-plugin and gst-droid, below where it says "if --gg gives problem....". By suitably segmenting the given command I could build the above and rootfs but not gmp-droid on 4.2.0.21 for an aarch64 device. But the device has only custom roms supp | 18:27 |
| T42 | <Stellar_Eagle> https://github.com/SailfishOS-MI-A2/local_manifests/wiki/Build-notes-SFOS-4.0.1-hybris-16.0-armv7hl gives a clue about gst-droid commands that can successfully be used by changing HEAD for ofono-ril-plugin and gst-droid, below where it says "if --gg gives problem....". By suitably segmenting the given command I could build the above and rootfs but not gmp-droid on 4.2.0.21 for an aarch64 device. But the device has only custom roms supp | 18:28 |
| kquote03 | elrso34: Alright I fixed it and pushed changes. Turns out I had to get the files from my device. | 20:24 |
| kquote03 | I will rebuild only droid-hal for now | 20:25 |
| kquote03 | oh and droid-configs as well... common sense | 20:32 |
| Thaodan | rinigus: https://github.com/mer-hybris/android_kernel_sony_msm/commits/hybris-sony-aosp/LA.UM.7.1.r1_bluetooth_test | 22:36 |
| kquote03 | Hello | 23:12 |
| kquote03 | I have reinstalled, I still get the same binder error | 23:13 |
| kquote03 | btw what is the proper way to start droid-hal-init manually? | 23:17 |
| kquote03 | new logcat https://susepaste.org/68613259 | 23:44 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
