| T42 | <Umeaman> Reboot to TWRP if you have it installed. You can just boot the twrp image with fastboot. (re @Walid: i can't connect via ...) | 16:34 |
|---|---|---|
| T42 | <Umeaman> Then you can investigate some more- | 16:35 |
| T42 | <Umeaman> Then you can investigate some more. (edited) | 16:35 |
| T42 | <k1gen> I want to port Sailfish OS on Pixel 4 (google-flame), but I am having some troubles. I initialized mer-hybris repo, hybris-18.1 branch, on LineageOS wiki my device's kernel repo is LineageOS/android_kernel_google_msm-4.14, and it has only lineage-19.1 branches and higher, while device-specific configuration repo (LineageOS/android_device_google_flame) has needed lineage-18.1 branch. What should I do? | 17:12 |
| T42 | <k1gen> anyone? | 17:28 |
| mal | @k1gen if you look at the lineage.dependencies file you see it gives a dependency https://github.com/LineageOS/android_device_google_flame/blob/lineage-18.1/lineage.dependencies and then if you open that https://github.com/LineageOS/android_device_google_coral/blob/lineage-18.1/lineage.dependencies you see more including a different kernel repo | 17:36 |
| mal | so those file should give you all the information you need to create the file to local_manifests | 17:37 |
| T42 | <k1gen> mal: coral is bigger version of flame, is it ok to init coral repo? | 17:38 |
| mal | *files | 17:38 |
| mal | @k1gen you see it listed as dependency so quite likely flame repo overrides some things defined in coral repo | 17:38 |
| mal | and you check the readme in flame repo https://github.com/LineageOS/android_device_google_flame/tree/lineage-18.1 | 17:39 |
| mal | "Nothing is really here. The flame device tree files are in device/google/coral." | 17:39 |
| T42 | <k1gen> mal: could you check my local_manifest xml if I send it via pastebin? | 17:40 |
| mal | @k1gen the standard way of creating the xml file to local_manifests is to go through those lineage.dependencies files and just add everything listed there and in the files of the dependencies | 17:40 |
| mal | ok | 17:40 |
| T42 | <k1gen> thank you, didn't see that explained in hadk (re @SailfishFreenodeIRCBridgeBot: <mal>@k1gen the stan...) | 17:41 |
| T42 | <k1gen> mal: https://hastebin.com/umasitusip.xml | 17:42 |
| T42 | <k1gen> will that work with hybris-18.1 repo? | 17:43 |
| mal | should work | 17:44 |
| T42 | <k1gen> thank you! | 17:44 |
| T42 | <elros34> Does anybody have figured out how to handle flattened apex on hybris-18 or this needs to be investigated? | 18:55 |
| mal | you mean non-updatable? | 19:13 |
| T42 | <elros34> yes | 19:13 |
| mal | @k1gen in case you haven't noticed check https://github.com/mer-hybris/hadk-faq#hybris-17-1 for some extra information about building | 19:14 |
| mal | @elros34 I tried but something is wrong in the init patches we have and I haven't found a working patch yet | 19:14 |
| T42 | <k1gen> mal: it's for 17.1, isn't it? or this part applies to 18.1 as well? | 19:15 |
| mal | same applies to 18.1 | 19:16 |
| mal | well of course change the 10 to 11 in the last line | 19:16 |
| T42 | <k1gen> thanks, when should I do this? after `repo sync` or later? | 19:18 |
| mal | after | 19:25 |
| mal | before you start building, so after repo sync and before make hybris-hal | 19:26 |
| mal | and note you only do it once (unless you repo sync again which would remove the patches) | 19:26 |
| mal | and I'm talking about apply_patches.sh command | 19:27 |
| mal | and the "export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true" | 19:28 |
| T42 | <elros34> this is not needed anymore | 19:31 |
| T42 | <k1gen> why? (re @elros34: this is not needed a...) | 19:38 |
| T42 | <elros34> because it was fixed: https://github.com/mer-hybris/hybris-patches/commit/561246fe753d78f6ae4bce9e5d2ab2b89a012860. I am not aware of any other critical restricted tools which requires this env | 19:40 |
| T42 | <k1gen> so I don't need anything from faq and should go just according to hadk? (re @elros34: because it was fixed...) | 19:42 |
| T42 | <elros34> it was only about: TEMPORARY_DISABLE_PATH_RESTRICTIONS. Frankly you need much more than faq and hadk provides | 19:42 |
| T42 | <k1gen> where do I get this "much more"? (re @elros34: it was only about: T...) | 19:43 |
| T42 | <elros34> here you can find most common issues, 18 specific too: https://etherpad.wikimedia.org/p/hadk-hot | 19:43 |
| T42 | <elros34> rest in channel logs | 19:44 |
| T42 | <k1gen> `error: Unable to fully sync the tree. | 20:10 |
| T42 | <k1gen> error: Downloading network changes failed. | 20:10 |
| T42 | <k1gen> error: Checking out local projects failed. | 20:10 |
| T42 | <k1gen> Failing repos: | 20:10 |
| T42 | <k1gen> external/python/pybind11/tools/clang | 20:10 |
| T42 | <k1gen> packages/apps/Etar/external/chips | 20:10 |
| T42 | <k1gen> packages/apps/Etar/external/colorpicker | 20:10 |
| T42 | <k1gen> packages/apps/Etar/external/timezonepicker` | 20:10 |
| T42 | <k1gen> sorry for pasting more than 3 lines of text | 20:10 |
| T42 | <elros34> did you read that hadk-hot hybris18 section? | 20:12 |
| T42 | <k1gen> `hybris-18 WIP`? (re @elros34: did you read that ha...) | 20:12 |
| T42 | <elros34> yeah | 20:13 |
| T42 | <k1gen> should I start from scratch with hybris-17.1? | 20:13 |
| T42 | <elros34> or just read first point in that section | 20:14 |
| T42 | <k1gen> https://build.sailfishos.org doesnt work, use: https://build.merproject.org instead this one? | 20:15 |
| T42 | <k1gen> oh | 20:15 |
| T42 | <elros34> hybris-18 WIP -> - Do not use fetch-submodules when repo cloning repostories | 20:15 |
| mal | @k1gen as mentioned don't add fetch-submodules to repo sync | 20:20 |
| T42 | <k1gen> already, thanks | 20:21 |
| T42 | <k1gen> how do I "configure mountpoint information" in hybris/ | 20:27 |
| T42 | <k1gen> hybris-boot/fixup-mountpoints? here's my partition table: https://hastebin.com/qapazalusi.apache | 20:27 |
| T42 | <k1gen> I saw 24th line in hadk-hot but didn't understand anything | 20:28 |
| T42 | <k1gen> "aosp hack", "package partitions", "custom systemd mount units" | 20:29 |
| T42 | <elros34> did you read hadk pdf? | 20:29 |
| T42 | <k1gen> I am at the moment | 20:30 |
| T42 | <k1gen> 5.3 Configure Mountpoint Information | 20:30 |
| T42 | <elros34> so go to hybris-boot github commits history, see for example: FP3 related commit and you should know how to write it | 20:31 |
| T42 | <k1gen> this one https://github.com/mer-hybris/hybris-boot/commit/a67690fcaba9f85e8847493937412ff9f7688c95? | 20:32 |
| T42 | <elros34> or any other, just an example if you can't figure out how to write | 20:32 |
| T42 | <k1gen> let's take boot part as an example, I have boot_a and boot_b on sda6 & sda7. how do I write that? | 20:34 |
| T42 | <elros34> mal: so if I get this right flattened apexes are mounted in SetupMountNamespaces which is comented out by hybris-patches. I see only some tmpfs in /apex mounted probably by droid-hal-init which overrides my manual /system/apex -> /apex mount | 20:34 |
| T42 | <elros34> @k1gen choose one slot and use only that block device | 20:35 |
| T42 | <elros34> mal: MountExtraFilesystems mounts tmpfs to /apex by something else also because there are multiple 4xtmpfs on top of it | 20:36 |
| T42 | <k1gen> @elros34 I see some _a _b devices in fixup_mountpoints, should I just rewrite everything from my partition table in fixup_mountpoints aswell? | 20:38 |
| T42 | <k1gen> for example, oneplus3 and addison are very different | 20:39 |
| T42 | <elros34> do not add _a/_b suffix, only official devices use it | 20:39 |
| T42 | <k1gen> boot & boot_aging? | 20:40 |
| T42 | <elros34> I see no significant difference between oneplus3 and addison, only block device name | 20:41 |
| T42 | <k1gen> oneplus3 has a lot more partitions hardcoded | 20:42 |
| T42 | <elros34> yeah not all are needed and you can skip some if you know what you are doing otherwise add all | 20:42 |
| T42 | <k1gen> I will write my own fixup, could you please check it once I'm done? | 20:43 |
| T42 | <elros34> sure if you promise to read the instructions about creating fixup-mount points carefully after writing:) | 20:45 |
| T42 | <k1gen> instuctions in hadk or hadk-hot? or both? | 20:45 |
| T42 | <elros34> both | 20:45 |
| T42 | <k1gen> still don't quite understand "package all dynamic partitions" from hadk-hot | 20:46 |
| T42 | <k1gen> how do I write all dynamic partitions if _a/-b is only for official devices | 20:47 |
| T42 | <k1gen> I'm sorry if I'm being stupid, and thank you for helping me this far | 20:48 |
| T42 | <elros34> package all dynamic partitions should be explained somwhere: https://docs.sailfishos.org/Develop/HW_Adaptation/Sailfish_X_Xperia_Android_11_Build_and_Flash/ but I have never really tried it. _a/-b suffixes are not needed because of how fixup-mountpoints work just do not add them | 20:49 |
| T42 | <elros34> Your not first one struggling with fixup-mountpoints which are really easy. I wrote instruction in hadk-hot to ease understanding it but still people fails to get it. I hope you will improve instruction with your fresh knowledge after you will figure out all of this | 20:52 |
| T42 | <Mister_Magister> bruh i think everyone did at some point | 20:54 |
| T42 | <k1gen> what's `makefstab_skip_entires`? I'm completely stuck | 20:56 |
| T42 | <k1gen> either dynamic partitions are mess or I am too dumb to figure this out | 20:57 |
| T42 | <elros34> yeah dynamic partitions is a little mess, there is no even proper solution prepared for it. | 20:58 |
| T42 | <elros34> just some dirty script | 20:58 |
| T42 | <k1gen> I mainlined noname phablet to postmarketos, but never thought this was gonna be that hard | 20:59 |
| T42 | <elros34> Lack of good instruction: maybe but I can hardly see anything hard in what you are doing. You can read in droid-hal-configs.inc about makefstab_skip_entries or just use it like explained in instruction and example | 21:00 |
| T42 | <elros34> add all dynamic partitions to makefstab_skip_entires similar to: https://github.com/mer-hybris/droid-hal-sony-lena/blob/master/rpm/droid-hal-common.inc#L20. What is not clear in that? | 21:01 |
| T42 | <k1gen> where to add them and what exact partitions | 21:02 |
| T42 | <elros34> in your spec file, excatly lik ein example | 21:02 |
| T42 | <k1gen> spec file? it is going to be created later in hadk pdf? | 21:03 |
| T42 | <elros34> yes. what exactly partitions: depends on your device, search in BoardConfig*.mk or check in android | 21:04 |
| T42 | <k1gen> I will be back in 15mins, are you going to be online? | 21:05 |
| T42 | <elros34> probably I am struggling with apexes | 21:05 |
| T42 | <k1gen> gotta start from writing fixup-mountpoints, step-by-step | 21:05 |
| T42 | <k1gen> don't know what's that about, maybe something really hard | 21:06 |
| T42 | <k1gen> I'm back | 21:18 |
| T42 | <k1gen> ok, so if I have `abl_a -> /dev/block/sde4` & `abl_b -> /dev/block/sde20` I have to write `'s block/bootdevice/by-name/abl sde4 '` and then only use slot _a, right? | 21:21 |
| T42 | <elros34> yes | 21:24 |
| T42 | <k1gen> thanks | 21:25 |
| T42 | <k1gen> Elros, what to do with modemst1 & modemst2? | 21:33 |
| T42 | <elros34> what about it? | 21:33 |
| T42 | <k1gen> that's what I have for now : https://irc.thaodan.de/.imgstore/5ce5b3a1/image_2022_09_17_00_33_45.png | 21:33 |
| T42 | <k1gen> `modemst1 -> /dev/block/sdf2`, `modemst2 -> /dev/block/sdf3`. which one to write? | 21:34 |
| T42 | <elros34> both | 21:34 |
| T42 | <k1gen> ok | 21:35 |
| T42 | <k1gen> by the way, is it ok that this partition table was dumped from a13 and not a11? | 21:40 |
| T42 | <elros34> what is a11 vs a13? | 21:41 |
| T42 | <k1gen> android versions | 21:41 |
| T42 | <elros34> depends on device, some use different by-name path for different android base. If partition table changed in a13 then guess what | 21:43 |
| T42 | <elros34> btw you know that you need lineage-18 flashed before sailfish? | 21:44 |
| T42 | <k1gen> so I should flash lineage-18.1 first, then write fixup-pqrtitions? | 21:45 |
| T42 | <elros34> it's not really that important right now, you will notice if some partitions fails to mount but if you afraid of breaking device then yes you should! | 21:48 |
| T42 | <k1gen> breaking like partition-table-breaking? | 21:49 |
| T42 | <k1gen> that's bad | 21:49 |
| T42 | <elros34> or partition content is wrong one is mounted | 21:49 |
| T42 | <elros34> if* | 21:50 |
| T42 | <k1gen> may I continue writing for now and following hadk, and later change fixup-partitions if something changes in the partition table? | 21:51 |
| T42 | <k1gen> *continue after flashing lineage | 21:51 |
| T42 | <elros34> sure. I think you can even flash hybris-boot.img if you reach that stage | 21:53 |
| T42 | <k1gen> thank you, then I will continue | 21:55 |
| T42 | <k1gen> https://hastebin.com/qapazalusi.apache https://hastebin.com/uyalojigop.rust | 22:02 |
| T42 | <k1gen> oh, forgot to read instructions | 22:02 |
| T42 | <k1gen> 5.3 in hadk finished, and to follow instructions in hadk-hot it seems like I need to proceed further in pdf | 22:05 |
| T42 | <k1gen> replaced `bootdevice` with `platform/soc/1d84000.ufshc` in `fixup-mountpoints`. Elros, what to do now? I mean, I need to do something to make dynamic partitions work | 23:26 |
| T42 | <k1gen> oh, you are online | 23:27 |
| T42 | <elros34> why did you replace it? This has nothing to dynamic partitions | 23:27 |
| T42 | <k1gen> I replaced it because my device has that table. I have `block/platform/soc/1d84000.ufshc/by-name/abl sde4` now | 23:28 |
| T42 | <k1gen> notice command to dump partitions: `flame:/ $ ls -l /dev/block/platform/*/*/by-name/` | 23:28 |
| T42 | <elros34> this has nothing to command. It's all about what you have in fstab file | 23:29 |
| T42 | <elros34> because fixup-mountpoints works on your fstab | 23:29 |
| T42 | <k1gen> `cat: /etc/fstab: No such file or directory` in adb shell | 23:31 |
| Thaodan | it's the fstab in your devices source tree | 23:31 |
| T42 | <k1gen> oh, that one | 23:31 |
| Thaodan | But on the device in /vendor should also work. | 23:32 |
| Thaodan | find /vendor /system -name \*fstab\* | 23:32 |
| T42 | <k1gen> Thaodan: | 23:33 |
| T42 | <k1gen> `/vendor/etc/fstab.persist | 23:33 |
| T42 | <k1gen> /vendor/etc/charger_fstab.qti | 23:33 |
| T42 | <k1gen> /vendor/etc/fstab.sm8150 | 23:33 |
| T42 | <k1gen> /system/etc/fstab.postinstall` | 23:33 |
| T42 | <k1gen> telegram didn't apply formatting, sorry | 23:34 |
| Thaodan | it's not visible in irc anway. | 23:34 |
| T42 | <k1gen> .sm8150 is most likely it | 23:35 |
| T42 | <k1gen> https://hastebin.com/ariwutudif.sql | 23:35 |
| T42 | <k1gen> should I do something except patching before compiling everything but after fixup-mountpoints? | 23:41 |
| T42 | <k1gen> I think I should package all dynamic partitions, but don't know how | 23:42 |
| T42 | <k1gen> https://docs.sailfishos.org/Develop/HW_Adaptation/Sailfish_X_Xperia_Android_11_Build_and_Flash/ just says *ignore chapter 5* | 23:44 |
| T42 | <elros34> why don't you just use script to mount dynamic partitions and worry packaging everything about that later | 23:47 |
| T42 | <elros34> or just finally build image, don't expect you will get everything working at first boot, you can make changes on device itself | 23:47 |
| T42 | <k1gen> https://pastebin.com/TpZAdS76 this script? | 23:48 |
| T42 | <elros34> yes | 23:48 |
| T42 | <k1gen> honestly, I don't understand where it should be placed | 23:49 |
| T42 | <elros34> whether you want in droid-config/sparse but usr/bin/droid/ looks like a sane path | 23:50 |
| T42 | <k1gen> ok, I think I will figure it out little bit later | 23:52 |
| T42 | <k1gen> for now, I applied patches | 23:52 |
| T42 | <k1gen> I do not need to export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true, right? | 23:53 |
| T42 | <elros34> it's not critical | 23:53 |
| T42 | <elros34> at least on hybris-18 branch | 23:54 |
| T42 | <k1gen> where is droid-config-$DEVICE.spec? | 23:54 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
