| T42 | <the_hiktor> mal, does real device nodes changes with android version ? | 06:34 |
|---|---|---|
| T42 | <the_hiktor> i am planning to use a10 firmware | 06:34 |
| T42 | <nc1x72> mal, no errors. However, it seems like the previous attempts which started vibrator on max strength damaged the hardware. I have flashed stock Android 15 and noticed it doesn’t vibrate either. I’ll have to open it and try to fix it. | 07:06 |
| mal | @the_hiktor those should not change | 13:19 |
| T42 | <the_hiktor> uhmm... about the fixup mountpoints what should i do ?? | 17:36 |
| T42 | <the_hiktor> should i continue with the guide normally from here ? | 17:36 |
| T42 | <the_hiktor> https://hadk.sailfishos.org/android/#building-relevant-bits-of-your-android-base | 17:36 |
| mal | did you figure out what you had to add to fixup? | 17:58 |
| mal | can show what you got? | 17:58 |
| T42 | <SimplyNicoo> Hoping this is the right place to ask.. hello ! im working on my first build. Im at the getting in stage but I havent been able to get telnet. my device uses boot.img and init_boot.img but i didnt notice any documentation on hadk about init_boot. my device restarts every 60 seconds and has no usb/telnet even though I've configured it . is there anything I should check for in my build? | 21:08 |
| T42 | <SimplyNicoo> Hoping this is the right place to ask.. hello ! im working on my first port. Im at the getting in stage but I havent been able to get telnet. my device uses boot.img and init_boot.img but i didnt notice any documentation on hadk about init_boot. my device restarts every 60 seconds and has no usb/telnet even though I've configured it . is there anything I should check for in my build? (edited) | 21:08 |
| T42 | <elros34> did you use a16 branch of hybris-boot? https://piggz.co.uk/sailfishos-porters-archive/index.php?log=2026-02-03.txt#line48 | 21:21 |
| T42 | <the_hiktor> mal, im still trying to figure out 🥲 | 21:23 |
| T42 | <the_hiktor> https://hastebin.com/share/uwevubanig.javascript | 21:24 |
| mal | @the_hiktor it would look similar the one for pdx235 but with the device nodes that you see in that paste of course, easy way is to just add such mapping for all the partition like done in the other ones based on the information in your paste | 21:28 |
| mal | @elros34 I should try to get that integrated into master next week, almost all other a16 changes are in, except droidmedia which only works with older a16 revisions and I need to fix it for lineage 23.2 | 21:30 |
| T42 | <SimplyNicoo> I used A15 since thats what my device is running (i think thats 22.2) (re @elros34: did you use a16 bran...) | 21:32 |
| T42 | <elros34> I think you should still try a16 branch, it has needed changes for init_boot | 21:33 |
| mal | that a16 branch also includes changes needed for a15 | 21:33 |
| T42 | <SimplyNicoo> ouuu! okay :) thanks ill give it a shot. (re @elros34: I think you should s...) | 21:33 |
| mal | but that 60 second reboot suggests usb setup failure | 21:35 |
| mal | anyway with the a16 branch of hybris-boot you should get init_boot image and then we can debug more if it still fails | 21:36 |
| T42 | <SimplyNicoo> oh im already on the A16 branch hmm | 21:44 |
| mal | did you flash both images? | 21:46 |
| mal | hybris-boot.img and hybris-init_boot.img, how about vendor_boot if you have one? | 21:46 |
| T42 | <SimplyNicoo> Yes, its just rebooting every 60 seconds and not getting telnet. I hadnt flashed vendor boot though (re @SailfishFreenodeIRCBridgeBot: <mal>did you flash b...) | 21:47 |
| T42 | <the_hiktor> mal, sorry if this feels dumb but what should i do to get that fixup file should i steal it from somewhere 😅 | 21:48 |
| T42 | <the_hiktor> its just the beginning and this guide makes me feel retarded enough to hate myself 🥲 | 21:48 |
| T42 | <elros34> it's that on purpose. Weak porters will give up | 21:49 |
| T42 | <elros34> if you don't give up you will laugh later how easy it was:P | 21:50 |
| mal | @the_hiktor the paste you showed has for example this line "abl -> /dev/block/sde8" (and because of the paths are checked from /dev/block/bootdevice/by-name/) which then in fixup becomes: -e '%s block/bootdevice/by-name/abl sde8 ' \ | 21:51 |
| mal | sorry, it becomes this: -e 's block/bootdevice/by-name/abl sde8 ' \ | 21:52 |
| mal | do you understand the logic now? | 21:52 |
| mal | make sure the first part matches what you see in fstab, I think on many device metadata partition uses different path | 21:54 |
| T42 | <the_hiktor> @elros34 this is just sad nothing more to be said | 22:54 |
| T42 | <elros34> be strong:) You are not the first one which couldn't get it. I bet some porters who finished port couldn't do it second time without help. If you still don't know how to prepare fixup then past your fstab | 22:57 |
| mal | would be good if anyone had ideas how to improve hadk in that part | 22:57 |
| mal | maybe it needs some example how to fix one line? | 22:58 |
| mal | but the existing fixup entries should usually give quite good examples already how those should look and when comparing the things seen in device fstab and /dev output it should be doable to see the logic | 22:59 |
| T42 | <elros34> mal: I have some instructions in https://sailfishos.wiki/books/hardware/page/hadk#bkmrk-%C2%A0-2 and https://sailfishos.wiki/link/20#bkmrk---fixup-mountpoints- with simple instructions but you know my english is not so good so it's probably not good enough for offcial hadk docs | 22:59 |
| T42 | <the_hiktor> im already taking detailed notes for future maybe some day it becomes something 🥲 | 22:59 |
| mal | @elros34 hadk is now open source so you could make a PR and then we can optimize the instructions in there | 23:00 |
| mal | I find it a bit odd that it needs that long explanation so maybe something a bit shorter would be better, need to think a bit | 23:02 |
| T42 | <the_hiktor> i think some poetry might help | 23:03 |
| mal | but that reminds me, I should look into replacing the mount service generator so it would use paths automatically which can be used by systemd, not the same like we do with fixup but with different paths | 23:03 |
| T42 | <the_hiktor> @elros34 https://github.com/GloboPatro/android_device_xiaomi_surya/blob/lineage-18.1/rootdir/etc/fstab.qcom | 23:05 |
| T42 | <the_hiktor> my problem is constructing the fixup 🥲 | 23:06 |
| T42 | <the_hiktor> i dont know how it looks like | 23:07 |
| T42 | <elros34> so in $ANDROID_ROOT/hybris/hybris-boot/fixup-mountpoints find for example vayu https://github.com/mer-hybris/hybris-boot/blob/master/fixup-mountpoints and copy/edit it to surya | 23:11 |
| T42 | <elros34> then from your fstab https://github.com/GloboPatro/android_device_xiaomi_surya/blob/lineage-18.1/rootdir/etc/fstab.qcom#L40 most of your by-name paths looks like /dev/block/bootdevice/by-name/ | 23:12 |
| mal | @the_hiktor you still didn't figure out the logic from my earlier example? | 23:13 |
| mal | so "abl -> /dev/block/sde8" in ls -l /dev/block/bootdevice/by-name/ becomes this: -e 's block/bootdevice/by-name/abl sde8 ' \ | 23:13 |
| mal | your fstab shows the /dev/block/bootdevice/by-name being used | 23:14 |
| T42 | <the_hiktor> not that i didn't git it yet , but i cant think if i didnt apply first | 23:16 |
| T42 | <the_hiktor> also that fixup file seems to contain some unrelated devices | 23:17 |
| T42 | <the_hiktor> i dont get it, whats the point of keeing them ? | 23:17 |
| T42 | <elros34> its one file to rule them all (ports) | 23:20 |
| mal | yeah, it's a bit bad design to have all devices in one file, instead of some adaptation repo | 23:22 |
| T42 | <the_hiktor> it looks that some devices with maintained ports missing from there 🫤 | 23:23 |
| mal | yes | 23:24 |
| T42 | <the_hiktor> like davinci and miatoll | 23:24 |
| T42 | <the_hiktor> but why ? | 23:24 |
| T42 | <elros34> PR to add new devices are not really accepted anymore unless it's official device | 23:26 |
| mal | I have been too lazy to merge those | 23:27 |
| mal | sorry | 23:27 |
| T42 | <the_hiktor> oh... i dont like how things going in here 😂 | 23:28 |
| T42 | <elros34> mal: It's your call but wouldn't worry/waste time about it at all. Open PR is still useful if somebody wants to continue the port | 23:30 |
| mal | well lazy might not be the best way to put it, just too many things to do | 23:34 |
| T42 | <the_hiktor> so should i do a clean fixup without those devices or just ignore them | 23:38 |
| T42 | <the_hiktor> mal, why working alone ? | 23:40 |
| mal | you can ignore the other devices in fixup and just add your device as first there | 23:43 |
| T42 | <the_hiktor> ok 👍 | 23:43 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!