Friday, 2024-05-10

T42_<Shigenta> Heya! Porting SailfishOS on Redmi 4X, got a problem with building packages
T42_<Shigenta> It says that ".mb2/spec" doesn't exist, although it does09:41
malyou seem to have the sources on another disc which is not available in all environments?10:44
malhow did you mount the disk to sdk?10:59
T42_<Shigenta> yep, cuz i dont have enough space on my ssd (re @SailfishFreenodeIRCBridgeBot: <mal>you seem to hav...)11:53
T42_<Shigenta> sudo mount --bind /media/files /srv/sailfishos/sdks/sfossdk/mnt/files11:53
T42_<Shigenta> sfossdk11:53
T42_<Shigenta> sudo mount --bind /mnt/files/ $PLATFORM_SDK_ROOT/sdks/ubuntu/mnt/files11:54
T42_<Shigenta> and then ubu-chroot (re @SailfishFreenodeIRCBridgeBot: <mal>how did you mou...)11:54
mal@Shigenta I have something like this at the end of .hadk.env: sudo mount --bind /parentroot/some_folder "/home/some_user/some_other_folder"12:10
malthat is the way it has access to the content from another disk12:11
malthen you use that /home/some_user/some_other_folder as $ANDROID_ROOT12:11
T42_<Shigenta> oh, so i should bind it to folder in home and use it as android root?12:15
T42_<Shigenta> alr12:15
T42_<Shigenta> -bash: cd: /home/shigenta/harddrivelink/SailfishSantoni/hadk/: No such file or directory12:18
T42_<Shigenta> its empty in platformsdk12:20
malyou are sure all paths are correct? and you don't get any error when entering plaform sdk?12:35
T42_<Shigenta> oh, wait, parentroot (re @SailfishFreenodeIRCBridgeBot: <mal>@Shigenta I hav...)12:36
T42_<Shigenta> now it works12:37
T42_<Shigenta> thanks12:38
T42_<Shigenta> anyway, build still fails
maldo you have this in your spec: %define droid_target_aarch64 112:41
T42_<Shigenta> which one spec? (re @SailfishFreenodeIRCBridgeBot: <mal>do you have thi...)12:41
T42_<Shigenta> droid-hal? droid-config?12:41
malnote that it should be added before last line12:42
malthat line in the file should be: %include dhd/droid-hal-device.inc12:43
malso add it to any place before that12:43
mal*the last line should be12:43
T42_<Shigenta> another error
T42_<Shigenta> i see something about dtbo - los 16.0 kernel for my phone doesnt have dtbos (re @Shigenta: another error https:...)13:01
maldtbo is optional when device needs it13:01
malyou need to add straggler_files define for the files, something like this but different paths
T42_<Shigenta> what about other errors? (re @SailfishFreenodeIRCBridgeBot: <mal>dtbo is optiona...)13:02
T42_<Shigenta> alr (re @SailfishFreenodeIRCBridgeBot: <mal>you need to add...)13:02
T42_<rosettanongrata> don't reply please13:09
T42_<rosettanongrata> looks bad on the irc side13:09
T42_<Shigenta> oh, alright13:09
T42_<rosettanongrata> same with editing. thanks13:09
T42_<Shigenta> again error
malcheck the build log mentioned in that13:42
maljust to be sure, for which sailfish version are you building?13:42
malcheck if all of those packages are in droid-local-repo13:43
T42_<Shigenta> latest one (re @SailfishFreenodeIRCBridgeBot: <mal>just to be sure...)13:43
T42_<Shigenta> ig13:43
T42_<Shigenta> ig thats why it fails13:44
malalso make sure you use correct submodule revisions13:44
malfrom there is the part "Recommended revisions: using latest (default) instead following may cause issues"13:44
maladd these lines to droid-config spec
malthen " -c" and then again " -v"13:46
T42_<Shigenta> now i dont really understand why it fails13:58
T42_<Shigenta> wait, after running it second time, for some reason it didnt fail14:01
T42_<Shigenta> hm14:01
malI think it got confused the first time but later in the builds removed the problematic package on line 82 in that log14:04
T42_<Shigenta> another error14:46
malwhat do you have in droid-hal to cause that15:36
malshow the droid-hal spec15:36
malwhy that _unpackaged_files_terminate_build?15:49
T42_<Shigenta> it fails without it (re @SailfishFreenodeIRCBridgeBot: <mal>why that _unpac...)15:49
T42_<Shigenta> /sdcard is not packaged15:51
T42_<Shigenta> and /bugreports15:51
malwhy didn't you add those to straggler_files?15:52
mallike the other files15:52
T42_<Shigenta> hm15:52
T42_<Shigenta> alright15:52
malthat is the point of straggler_files, if there are extra files that are not packaged by default then you add those to straggler_files so it builds without issues15:53
T42_<Shigenta> alright15:53
malit packages those to a package which can be then included in patterns if needed15:53
T42_<Shigenta> understood15:53
T42_<Shigenta> anyway, it didnt help15:55
T42_<Shigenta> same error15:55
malstill not sure how you have /usr/lib/systemd/system in droid-hal15:56
maloh, wait, some issue with droidmedia maybe, did you verify the submodule versions like I suggested earlier?15:57
T42_<Shigenta> oh, i dont even know how lol15:57
T42_<Shigenta> this is my first time doing anything with submodules15:57
mal there is the part "Recommended revisions: using latest (default) instead following may cause issues"15:58
malbtw, you should build
malbut back to submodules, you go to for example rpm/dhd folder and there check git log to see which revision it uses15:59
T42_<Shigenta> i guess its b29f356 for dhd16:02
malif it's different from that that hadk-hot says, then in rpm/dhd folder run "git reset --hard 960d6af" also do the similar (using the revisions from hadk-hot) for the other ones mentioned in hadk-hot, like external/droidmedia, hybris/droid-configs/droid-configs-device and hybris/mw/sensorfwd16:02
T42_<Shigenta> alr16:03
T42_<Shigenta> and then just rebuild everything?16:03
malin case of droidmedia, if it's different then you should in HABUILD run make droidmedia (after the usual things before that) to rebuild droidmedia16:04
T42_<Shigenta> alr16:04
malso the env where you ran make hybris-hal before16:04
T42_<Shigenta> also, after reset --hard i should git pull --force?16:04
T42_<Shigenta> also, i dont have hybris/mw/sensorfwd16:08
malanything related to sensors in that hybris/mw folder16:11
T42_<Shigenta> there are only community-adaptation, droidmedia-localbuild, mce-plugin-libhybris, pulseaudio-modules-droid-hidl, pulseaudio-modules-droid-jb2q and qt5-qpa-hwcomposer-plugin16:12
malok, then skip that16:12
T42_<Shigenta> alr16:13
T42_<Shigenta> also, can i put export RELEASE= in .hadk.env?16:22
malI think so16:24
T42_<Shigenta> still fails16:34
malyou mean still those /usr/lib/systemd/system in droid-hal ?16:35
maland you did rebuild droid-hal?16:36
T42_<Shigenta> yeah16:36
T42_<Shigenta> yep16:36
maland you are sure rpm/dhd submodule is in correct revision?16:36
T42_<Shigenta> yes16:37
T42_<Shigenta> 960d6af16:37
malcan you show the build log for droid-hal-version16:42
T42_<Shigenta> oh wait, should i rebuild everything from 7.2.1?16:44
T42_<Shigenta> or only droid-hal and configs16:44
maldepends on what you change16:45
T42_<Shigenta> i mean, i only did git reset in droid-hal, configs and droidmedia16:46
T42_<Shigenta> so i rebuild only droid-hal, configs and droidmedia16:46
malcheck manually the content of droid-hal rpm16:46
T42_<Shigenta> hadk/rpm?16:48
T42_<Shigenta> grepped 'system' in all files in hadk/rpm
T42_<Shigenta> and systemd
malI mean the rpm files you built. those are under droid-local-repo17:10
T42_<Shigenta> oh17:10
malbut you can also show droid-hal build log17:10
malit should be in $ANDROID_ROOT17:10
malas a workaround edit this line in (in rpm/dhd) and make it like this: %{_unitdir}/*17:39
malthen rebuild droid-hal rpms and try again17:39
T42_<Shigenta> alright17:40
T42_<Shigenta> should i create fork for that later?17:40
malI'll probably fix that in that repo17:40
malif it helps with your build17:41
malstill not sure why nobody else has had such issues, at least I haven't heard of any17:41
T42_<Shigenta> hm17:41
T42_<Shigenta> ig it worked17:45
T42_<Shigenta> since its now "creating droid users and groups"17:45
T42_<Shigenta> ive got zip17:52
T42_<Shigenta> i should just flash it?17:52
T42_<Shigenta> also - for some reason only old twrp works, new ones are failing on installation script17:57
malyes, that is known issue with new twrp versions18:09
T42_<Shigenta> well, got this in dmesg
T42_<Shigenta> also, after it reconnects - yellow led is lighting18:54
T42_<elros34> you must  telnet toevice and seewhat is going on according  to hadk instructions19:03
T42_<Shigenta> yeah, but it doesnt connect19:04
T42_<Shigenta> and i cant even ping
T42_<elros34> did you try relevant for your case advices  from following link?
T42_<elros34> do you use correct telnet port?19:08
T42_<Shigenta> 232319:08
T42_<Shigenta> i already said that i cant even ping this address19:09
T42_<Shigenta> i see that in ifconfig
T42_<elros34> did you try init_enter_debug2?19:23
T42_<Shigenta> what is it?19:24
T42_<Shigenta> and how can i try it lol19:24
T42_<Shigenta> oh, i see it on that page you gave me19:24
T42_<Shigenta> gimme a minute, i'll try it19:24
T42_<Shigenta> still the same thing - i cant connect with telnet, ifconfig shows the same thing19:27
T42_<Shigenta> but now it stays on 'init-debug in real rootfs'19:28
T42_<Shigenta> well, configuring usb networking as descibed here( worked19:32
T42_<Shigenta> but without init_enter_debug2 it refuses to connect19:37
T42_<elros34> not a big deal, something fails or mess up connection. With that file you can still continue booting19:39
T42_<Shigenta> alr19:39
T42_<Shigenta> well, got that in init.log
T42_<Shigenta> and that in dmesg
T42_<Shigenta> and that after 'echo "continue" >/init-ctl/stdin'
malyou have telnet after that?19:59
T42_<Shigenta> nah19:59
T42_<Shigenta> after that last line in second dmesg telnet dies19:59
T42_<elros34> you need journal logs20:05
T42_<Shigenta> alr (re @elros34: you need journal log...)20:05
T42_<Shigenta> got something20:07
T42_<elros34> this is only 2 seconds, you need whole boot log. See instruction I linked and enable persistent logging20:12
T42_<Shigenta> alright20:12
T42_<elros34> don't forget about disabling audit, I think it's in same  section20:13
T42_<Shigenta> do i need RateLimitInterval=0?20:19
T42_<elros34> maybe you need maybe you don't:), you will see20:21
T42_<Shigenta> anyway, i insert it lul20:22
T42_<Shigenta> well, i got journal logs20:26
T42_<Shigenta> buut, its unreadable20:26
T42_<Shigenta> can i send it as a file?20:27
T42_<Shigenta> even tho i added audit=020:30
T42_<elros34> is first 60-90s really that noisy?20:30
T42_<Shigenta> yeah20:32
T42_<Shigenta> oh, i cant post screenshots here20:32
T42_<elros34> check what fails first20:33
T42_<Shigenta> well, how? (re @elros34: check what fails fir...)20:33
T42_<Shigenta> its barely readable lol20:33
T42_<Shigenta> the only thing i can see why it cant boot MESSAGE=/bin/sh: can't open '/usr/bin/droid/': No such file or directory20:35
T42_<Shigenta> but i dunno20:35
T42_<elros34> not a problem, it's optional file, keep searching:) systemctl output could gives some pointers too20:36
T42_<Shigenta> systemd-tmpfiles-setup.service: Failed with result 'exit-code'20:39
T42_<Shigenta> droid-hal-init.service: Failed with result 'exit-code'20:39
T42_<elros34> most important is droid-hal-init,  first one is probably because of some missing kernel changes, probably not very important20:41
T42_<Shigenta> Sending signal 9 to service 'hwservicemanager' (pid 4372) process group... HYBRIS: killing PID instead20:42
T42_<Shigenta> critical process 'hwservicemanager' exited 4 times in 4 minutes20:43
T42_<Shigenta> Could not read message from init: Invalid argument20:43
T42_<Shigenta> Could not read message from init: No such file or directory20:43
T42_<Shigenta> ig its cuz of hwservicemanager20:46
T42_<Shigenta> because i cant find anything else lol20:46
T42_<elros34> btw did you add hybris-16 (or whatever version you use) related changes from hadk-hot/faq?20:49
T42_<Shigenta> yep20:49
T42_<Shigenta> you can even check my repo
T42_<elros34> another can of worms is logcat20:50
T42_<Shigenta> i should try to get logcat?20:50
malis which android base is what?20:51
T42_<elros34> you can. Without seeing logs I can not advice you anything better.20:51
T42_<Shigenta> its android 9.0(los 16.0)20:51
malis selinux related things correctly done?20:51
T42_<Shigenta> ig?20:52
T42_<Shigenta> in defconfig?20:52
maldid you follow the instructions in
T42_<Shigenta> yep20:53
T42_<Shigenta> oh, wait20:53
T42_<Shigenta> i should check something20:54
maldo you have the hwservicemanager failure mentioned in that?20:54
T42_<Shigenta> i cant even run logcat lol20:55
T42_<Shigenta> /bin/sh: /usr/libexec/droid-hybris/system/bin/logcat: not found20:55
T42_<Shigenta> but yeah, ig i have it20:55
T42_<Shigenta> since it fails as seen in journal logs20:55
maldo you now have  telnet now after you continue boot?20:56
T42_<Shigenta> no i dont lol20:57
malhave you tried masking usb-moded?20:57
T42_<Shigenta> nah20:57
T42_<Shigenta> systemctl mask usb-moded?20:58
malusing: ln -s /dev/null /etc/systemd/system/usb-moded.service20:58
malyou don't have systemd running yet when you have stopped the boot20:59
T42_<Shigenta> ln: /etc/systemd/system/usb-moded.service: File exists21:00
T42_<elros34> systemctl mask should be good too21:00
T42_<Shigenta> anyway, after systemctl mask usb-moded telnet still dies21:00
malhave you tried masking droid-hal-init.service also?21:23
T42_<Shigenta> no21:23
T42_<Shigenta> i'll try it rn21:24
T42_<Shigenta> oh21:30
T42_<Shigenta> only after masking both droid-hal-init and usb-moded telnet didnt die21:31
T42_<Shigenta> got journal logs21:33
malalso check output of systemctl and systemctl-user to see which systemd service work and which don't21:34
T42_<Shigenta> alr21:35
T42_<Shigenta> but now i see that it skips files i put like it was said in hadk-faw Unable to read config file '/usr/libexec/droid-hybris/system/etc/init/hwservicemanager.rc': Skipping insecure file21:35
T42_<Shigenta> and in the end it spams binder: 2909:2909 transaction failed 29189/-22, size 0-0 line 301521:36
T42_<elros34> what permission you set to that rc file? have you tried removing/commenting out usb*rc files according to same linked instruction instruction21:37
T42_<Shigenta> what permissions i should set to these rc files?21:38
T42_<Shigenta> nah, i havent21:38
T42_<Shigenta> they're all 077721:40
T42_<elros34> for sure they shouldn't, nothing set it like that21:42
T42_<elros34> did you copy files manually?21:42
T42_<Shigenta> yeah21:44
T42_<Shigenta> it should be 0644?21:45
T42_<elros34> see /system/ (etc) or something like that21:46
T42_<elros34> but probably like you said 64421:46
T42_<Shigenta> alr21:48
T42_<Shigenta> ig it should work now21:55
T42_<Shigenta> since droid-hal-init works21:56
T42_<Shigenta> and hwservicemanager too ig21:56
T42_<Shigenta> how can i check is hwservicemanager works? ig it is, since i dont see it crashing in journalctl21:59
T42_<elros34> pgrep -af servicemanager to see whether it's up but whether it works you need logcat22:03
T42_<Shigenta> empty output22:04
T42_<Shigenta> also, now i have logcat, but it says 'logcat read failure'22:09
T42_<Shigenta> logcat
T42_<Shigenta> after the last line in logcat it said 'read: unexpected EOF!'22:19
T42_<Shigenta> also, droid-hal-init works for about 10-20 seconds and then crashes22:21

Generated by 2.17.1 by Marius Gedminas - find it at!