Friday, 2021-03-12

T42<BNONA_20> Fwd from Hfx: ๐›๐š๐ฌ๐ข๐œ๐š๐ฅ๐ฅ๐ฒ ๐ญ๐ก๐จ๐ฎ๐ ๐ก๐ญ ๐ข๐ญ ๐ฐ๐š๐ฌ ๐š ๐ฌ๐œ๐š๐ฆ ๐ฎ๐ง๐ญ๐ข๐ฅ ๐ˆ ๐๐ž๐œ๐ข๐๐ž๐ ๐ญ๐จ ๐ ๐ข๐ฏ๐ž ๐ข๐ญ ๐š ๐ญ๐ซ๐ฒ ๐ฐ๐ข๐ญ๐ก ๐š ๐ฅ๐ข๐ญ๐ญ๐ฅ๐ž ๐ฌ๐ญ๐š๐ซ๐ญ๐ฎ๐ฉ ๐จ๐Ÿ ๐”๐’๐ƒ200 ๐š๐ง๐ ๐ˆ ๐ ๐จ๐ญ ๐›๐š๐œ๐ค ๐”๐’๐ƒ2250 24 ๐ก๐จ๐ฎ๐ซ๐ฌ ๐จ๐Ÿ ๐ญ๐ซ๐š๐๏ฟฝ05:53
T42<BNONA_20> ๐‘๐ž๐š๐œ๐ก ๐ก๐ข๐ฆ ๐ฏ๐ข๐š ๐ก๐ข๐ฌ ๐ญ๐ž๐ฅ๐ž๐ ๐ซ๐š๐ฆ ๐œ๐ก๐š๐ง๐ง๐ž๐ฅ ๐Ÿ‘‡๐Ÿ‘‡๐Ÿ‘‡๐Ÿ‘‡๐Ÿ‘‡๐Ÿ‘‡05:53
T42<edp_17> mal: yes, I am still doing the hammerhead.07:19
T42<edp_17> @Chrisme69 : I'll find you with direct message to avoid spamming this channel with that boot issue.07:20
T42<Chrisme69> Thanks07:20
T42<Chrisme69> A lot07:21
srxlHello all! Looking to start work on a port for a device I have. I have a working (close to) mainline kernel for my device, although I can't seem to find any information on getting an SFOS build going without using Android sources. Is it possible to just build on top of a mainline kernel?08:11
malsrxl: there are at least 3 devices that boot to UI without android using a linux kernel09:14
T42<edp_17> Hi all, I have an OBS related question. How can I add a repository with a custome name? (Currently I only have latest_arm7hl but I would like to create one for sfos3.4.0.24 and another one for and some other for older versions.)10:36
techgeeksterSo I erased everything and started from scratch. It went smoothly this time until the --mic step. Error <creator>[03/12 10:32:56] : Unable to find package: patterns-sailfish-device-configuration-raphael10:37
Thaodanedp_17: You should do that per project since the repository is defined by its packages e.g. when you need to stop updating a package for version x but need to for version y.10:38
techgeeksterNote: In my .ks file it does not have the patterns-sailfish-device-configuration-raphael packege in the %packages section10:41
mal@edp_17 so you really want a testing repo?10:45
mal@edp_17 similar to this just let me know for which device you need it and I can add such a repo10:46
T42<edp_17> mal: idk I just wanted to add a separate repo for every sfos version I built.10:46
T42<edp_17> mal: yes, I'd like to something like that.10:47
mal@edp_17 that is what testing is meant for, releases from public should be made from testing repos not devel10:47
mal*for public10:47
T42<edp_17> mal: Oh, I see.10:48
malbecause that way the repos can remain intact for older releases and won't get broken if you change something10:48
malespecially when you disable build for the version you have already released10:48
T42<edp_17> mal: yes, this is what I need.10:49
malso tell me which device you such a repo and I will add it, I will be out for a moment but will add after that10:49
T42<edp_17> mal: I have project for i9100 with one repo in there latest_armv7hl. There I'd like to create a repo for,, and
mal@edp_17 I don't see such device on OBS yet at all, which vendor is that10:51
malah, looked at wrong place, will add the repo once I'm back10:52
T42<edp_17> mal: I also have a treltexx project where currently there is no repo at all. Here I'd like to add, and
T42<edp_17> mal: okay, no rush with that! Thanks.10:52
T42<edp_17> mal: plus I'd like to have two new projects (hammerhead and n7000) Can I create those somehow?10:53
malcreating new projects on OBS is limited to few people like me, I can handle those also, what is vendor of n7000?10:54
T42<edp_17> mal: Thanks! The vendor od n7000 is also Samsung10:55
T42<edp_17> mal: for the n7000 Id like to have one repo so far:
*** Mister_Magister_ is now known as Mister_Magister11:01
T42<edp_17> mal: For just in case I let you know the repos I'd like to have for the hammerhead:,,, and
T42<edp_17> Thanks for your help in advance!11:03
techgeeksterIn patterns I added sailfish-connman-plugin-suspend and now in mic it says that it cannot find it (Warning[03/12 11:27:41] : repo problem: nothing provides sailfish-connman-plugin-suspend needed by patterns-sailfish-device-adaptation-raphael-1-202103120934.aarch64, )11:28
techgeeksterDoes anyone know how can I add it?11:28
T42<zinstack625> techgeekster: you have to manually clone and compile it11:46
T42<edp_17> Another question regarding OBS. Should I add all packages that I have in local repo $ANDROID_ROOT/hybris/mw ?11:47
techgeeksterThank you. For the logs, I did it with: rpm/dhd/helpers/ --mw=
T42<edp_17> @edp_17 [Another question regarding OBS. Should I add a โ€ฆ], Or should I list all of them what I listed in _pattern/jolla-configuartion-$DEVICE and _pattern/jolla-hw-adaptation-$DEVICE and _pattern/sailfish-porter-tools?11:53
srxlmal: awesome, so it's doable! are there any resources on how to do it, or anything from those devices I can take a look at to get an idea as do how it goes?11:56
T42<zinstack625> How's the state of hybris 17?11:57
deathmist_mal: could you take a look at and fix compilation of I encountered the same ".../file.list: No such file or directory" under aarch6413:11
swanuxI'm rebuilding now, and I faced that gst-photography error that was mentioned above. I tried the recommended revert (to 20201104) but common/ is empty (so the build fails). Where should I look for common/
malswanux: how did downgrade gst-droid?13:17
deathmist_swanux: it seems to be a submodule of gst-droid and I actually had to install git on the target tooling using "sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in -y git" before I could run --gg successfully13:17
maldeathmist_: you can't really use --gg now because latest gst-droid won't work with 4.0.113:18
malor anything older either13:18
swanuxmal: I followed your description (later, as common was empty I tried from release tags also)13:19
swanuxdeathmist_: I'll try it then, thanks13:19
deathmist_right, well with my patch ( and a modified I can :)13:19
malswanux: did you follow the instructions I posted couple of days ago: go to hybris/mw/gst-droid and run "git clean -x -f -d" and then "git reset --hard 0.20201104.0" and then check that the common/ folder in there has content, then back to $ANDROID_ROOT and run rpm/dhd/helpers/ -b hybris/mw/gst-droid13:19
swanuxmal Exactly13:19
malif common folder is empty try git submodule update13:20
malif that doesn't help then I have other ideas13:20
swanuxCommon still empty13:23
malgit submodule update --init --recursive --remote13:25
malthen check git diff13:25
piggzmal: i notived ofono plugin had a mjor version jump too, for a new api level 1.2?13:28
swanuxThe first command solved it. I successfully built it. Thank you! How should I proceed? (as -gg isn't usable)13:29
malpiggz: yes13:30
malpiggz: it got support for the 1.2 version of the android radio hidl api13:31
piggzmal: could do with better support for the pinephone modem!13:32
malpiggz: what? how is that in any way related to pinephone?13:35
piggzmal: not the ril driver .. but the pinephone ofono plugin in general could do with love13:35
malyeah, probably, where is the latest version of that?13:36
piggzmal: the version we are shipping is here mostly from @neochapay13:37
piggzmal: other distros are either using modem manger, or the newer upstream ofono13:52
piggziirc, sailfish ofono is uniquely old :D13:52
T42<calebccff> Does hybris-17.1 make it to UI for anyone?14:09
T42<calebccff> o.o right14:18
malmy device has only issues with fingerprint sensor and camera14:22
malcamera I know how to make work in a hacky way14:22
calebccffmal: is it aarch64?14:25
deathmist_speaking of fingerprint and aarch64, does someone have ideas about I'm using the community fpd sources from with @rinigus' patch applied so the RPM builds pass, but now the issue appears to be with sailfish-devicelock-fpd?14:27
piggzsolution 1 seems safe14:28
malyes solution 1 looks correct14:33
T42<elros34> c option seems more correct. patterns-sailfish-device-configuration-$DEVICE will basically pull whole rootfs to your target . Why do you want to install everything in target?14:38
rinigusdeathmist_: nut why do you install like that?14:38
deathmist_ok that doesn't seem to be what I should be doing anyway; I've got "Unable to find package: patterns-sailfish-device-configuration-$DEVICE" during " --mic" on aarch64, droid-config repo at, what could I be missing? this didn't seem to happen on my previous arm32 builds14:39
rinigusdeathmist_: you have to compile it, but not install14:41
maldeathmist_: you do know about the bug with aarch64 and --mic14:41
deathmist_mal: there was an older issue which I believe was fixed (the adaptation repo being in KS, which doesn't exist for me)14:42
deathmist_that was weeks ago at this point though14:43
rinigusdeathmist_: maybe useful. this is a hadk that I am using for tama aarch64 (based on seine):
maldeathmist_: yes, my fix however broke some sed magic in and now there are no adaptation repos in .ks14:43
deathmist_mal: so what should I do, revert the patch and remove the extra repo that doesn't exist again manually?14:46
piggzrinigus: hadk as md is actually a great idea14:46
deathmist_^ +114:46
riniguspiggz: that's the one based on seine wiki; earlier one that I used for aosp9 is based on ganges. so, idea was from jolla originally14:47
rinigusand does help to keep all small details for later. already helped me few times :)14:47
maldeathmist_: hack so it works again14:49
swanuxmal: I finished repackaging with your patch. Unfortunately /system/etc/ld.config.28.txt mountpoint still doesn't exist, and lipstick still dies. Any ideas?14:55
*** techgeekster_ is now known as techgeekster14:55
malswanux: your device doesn't need that14:56
malswanux: does strace look the same?14:58
malswanux: with or without the change?14:58
swanuxwith it was just worse (even test_hwcomposer died early). Without it, it's as usual14:59
swanuxmal: This was the problem with it :
swanux(related strace -
malswanux: ok, I have an idea, copy the ld.config.txt from /system/etc to /usr/libexec/droid-hybris/system/etc/ then edit the file and add some changes there, under [system] section you see list of lines add a new line with "namespace.default.permitted.paths += /usr/libexec/droid-hybris/system/${LIB}" after those lines, then same for the [vendor] section15:10
malswanux: oops, sorry the file is /system/etc/ld.config.vndk_lite.txt15:11
malthen create a similar systemd mount service you did earlier but that vndk_lite in every filename and file content instead of 2815:12
malhopefully you understand what I tried to say15:13
swanuxmal: Yes, I got it. Just one question: in [system] and [vendor] sections is it okay if I put it at the end?15:14
deathmist_mal: what exactly broke the sed? I could attempt fixing that and make a PR15:15
malswanux: you have to put it after the other line in the section15:16
malswanux: like this
maldeathmist_: the sed assumes there is a common adaptation repo15:17
maldeathmist_: I'm considering removing the common repo from local builds completely15:18
swanuxmal: Done. Now reboot?15:20
malswanux: can you show the mount service you made15:20
malswanux: ok, and the symlink enabling that is also correct?15:21
malis so then reboot15:21
swanuxYes. ln -s to ../$FILE. Now rebooting then15:22
swanuxReboot done15:22
techgeeksterHow can I get the journal from the boot. Device stays on oem boot logo15:23
swanuxmal: That's my new mount
maltechgeekster: is telnet working?15:23
malswanux: any help with graphics side?15:24
techgeeksterA new USB Ethernet device apears in my system but I dow not get an ip15:24
techgeeksterAnd telnet does not work15:24
maltechgeekster: so what all things have you done for the device? could you push the config repo to github15:25
techgeeksterWait a sec. I'll push the Android Source and the fixup_mountpoints15:26
swanuxmal: No improvement so far. Only difference I noticed is when running /system/bin/surfaceflinger (I do it so my oem logo wont burn in) it now outputs this: WARNING: linker: /system/etc/ld.config.vndk_lite.txt:45: warning: appending to undefined property "namespace.default.permitted.paths" (treating as assignment)15:26
malswanux: show the file15:26
malswanux: ah, I think I made a mistake15:27
T42<ankaos> hฤฑ. how fix this problem?
mal@ankaos which android base?15:28
T42<ankaos> 16.0 android version15:28
maldid you apply the patches correctly?15:28
T42<ankaos> @mal [did you apply the patches correctly?], yes15:28
calebccfftechgeekster: some linux distros don't play nice with host config. try manually configuring your IP to be `` on the interface that appears, then try telnet15:29
techgeeksterOk. Will do15:30
malswanux: edit the new lines you added by replacing namespace.default.permitted.paths with
techgeekstercalebccff: I got telnet now. Thank you15:33
techgeekstermal : This is the logcat, if you can find something. I am git pushing as we speak15:35
swanuxmal: Ok, warning disappeared. Nothing on GUI front though15:36
malswanux: strace15:39
maltechgeekster: get also output of journalctl -b --no-pager15:40
techgeekstermal: This is init.log JournalCtl says No journal files were found.15:41
swanuxmal: This is for lipstick -
maltechgeekster: which kernel version does your device have?15:42
malswanux: did you remove the /usr/libexec/droid-hybris/system/lib64/ ?15:43
techgeekstermal: 4.14.8315:43
swanuxmal: Yes15:43
malswanux: add it back15:44
T42<ankaos> mal: how fix error?15:44
swanuxmal: Copying v2 to v3?15:45
malswanux: yes15:46
mal@ankaos not sure yet15:46
swanuxmal: This outputs the same -
T42<elros34> @techgeekster if you created init_enter_debug2 then to continue booting you need to follow instruction you can see when you login15:52
techgeeksterT42: I removed the init_enter_debug2, still on oem logo. New init log
T42<calebccff> weird that /etc/ doesn't exist?16:00
T42<elros34> init.log is usually useless, get journal16:00
malwhich telnet port?16:01
T42<calebccff> techgeekster: fyi, t42 is just the telegram bridge bot, the actual person is at the start of the message. For people in TG do "@USERNAME"16:01
deathmist_mal: good news is that my aarch64 rootfs.tar.bz2 at least has /var/run as a symlink. if the filesystem package install issue didn't happen to anyone else here on arm32 base either I'd say it's safe to say it was because there were too many layers of containers/chroots going on when I built the last one. btw here's the PR to fix local aarch64 community builds:16:01
techgeekster@Calebccff Oh ok. Did not knew that.16:02
techgeekster@elros34 due to not understanding irc, I am sending it again. I removed the init_enter_debug2, still on oem logo. New init log
malI'll ask again, which telnet port?16:07
T42<elros34> @techgeekster and I will repeat again get journalctl. init.log is not very useful16:07
malah, that seems 2323 probably16:08
techgeekster@elros34 Ok, what could I give that would be more useful as a log? I am now finishing the github repo
T42<elros34> type: journalctl --no-tail -f16:09
maldoes "systemctl" show anything16:11
techgeekster@elros34 This is the result that repeats itself Feb 09 21:27:23 Mi9TPro kernel: pm8150b_charger: smblib_get_prop_typec_power_role: TYPE_C_MODE_CFG_REG = 0x1016:19
techgeeksterFeb 09 21:27:23 Mi9TPro kernel: pm8150b_charger: smblib_get_apsd_result: read APSD_RESULT_STATUS stat=0x116:19
techgeeksterand Feb 09 21:28:38 Mi9TPro kernel: binder: 3452:3452 transaction failed 29189/-22, size 32-0 line 302016:20
techgeeksterThis is the whole log
T42<elros34> this log lacks early boot messages. You need to reboot and then try again so journal contains all relevant information since beginning of boot16:25
malswanux: try to reorder the search paths in ld.config file, move the libexec on first, note the need to change the assignment += and = when needed16:25
mal@elros34 persistent journal would help16:26
T42<elros34> @techgeekster or ^ but then also use -b0 argument16:26
techgeeksterOk i'll try in a bit and i'll give you the results16:27
swanuxmal: Changed the order, now I got this with surfaceflinger -
swanux(and the device got into bootloop after that)16:37
swanuxsurfaceflinger or the others?16:37
swanuxmal: From surfaceflinger -
swanuxAnd it seems the bootloop isn't because of surfaceflinger / test_hwcomposer - It occurs after ~40s from boot (probably lipstick?)16:42
T42<elros34> swanux did you mask user@100000 before testing test_hwcomposer?16:43
T42<elros34> or surfaceflinger16:43
swanux@elros34 No. Should I? (as surfaceflinger worked before, even without masking)16:44
T42<elros34> I think so otherwise you will have restarting/hanging lipstick which might interfere with your tests16:46
swanuxAnd it worked before because lipstick died at early state anyway (?)16:47
T42<elros34> didn't some of patches you use break surfaceflinger?16:49
swanuxI don't think so. I mean, at the end of the day, yeah, they did, but I think it's because what you said, lipstick is still in the game (which is good I guess). I just applied those ld.config ... things following advice from mal16:51
mal@elros34 yes, a hacky attempt at ld.config.vndk_lite.txt16:51
malswanux: wait, are you saing lipstick runs now?16:51
swanuxI don't know, but otherwise what would cause the bootloop / crash in that state?16:52
deathmist_mal: implements the cg2_bpf removal patch for hybris-16.017:20
malswanux: what do you see in logs17:39
poetasterJust helped a dev. debug for the Volla port and I'm confused.17:42
poetastershould a community port provide a writable: /system/etc/? Is that not an android thing?17:43
poetastercontext is this thread:
swanuxmal: Here is the journalctl until the first bootloop / crash -
poetastersorry, noise. context is Vollaphone. piggz ting. I'll waite.17:45
malpoetaster: I don't understand why you would need to do anything in /system/etc17:53
poetasterI don't. app called defender (hosts and cookie jar) ad blocking.17:55
malpoetaster: so what is the problem with it, too much text in that thread17:56
poetasteron the vollaphone, it's a read only file system. his app installs but fails to write (lame).17:57
poetasterI'd say, he's doing 'too much'.17:57
poetasteruserland guy says, sigh, it's not me, it's the community port.17:58
poetasterI say, you make assumptions that are not warranted.17:58
T42<elros34> depends on port but most use /system from lineage and that is mounted as read-only.17:59
malyes, very few community ports have /system as rw18:00
poetasterhmm. so he's shooting self in foot. his app will fail on many ports.18:00
poetasterI'll tell him.18:00
poetastershould I be nice about it :)18:00
poetastermal: any luck on fp2 3.4 ? I need a second device for dev work.18:09
poetastersigh: [ -f %{_a1configdir}/hosts.editable ] && echo โ€œ%{_a1configdir}/hosts.editable existsโ€ || cp %{_a1configdir}/hosts %{_a1configdir}/hosts.editable 2>/dev/null || :18:11
swanuxmal: Do the logs say something useful?18:14
malpoetaster: well the only issue is updating to 3.4.018:24
malswanux: that tell android side process are failing18:25
poetastermail: thanks. let me know if I can held.18:25
malpoetaster: there is way around it but the real reason is a kernel bug18:25
poetastermal: 'way around?'18:29
malpoetaster: I mean disable a certain feature for a certain systemd service so it won't crash the kernel18:29
poetastermal: dsme still.18:36
poetasterwhich feature?18:36
malPrivateNetwork sandboxing18:37
rinigusjust released for sony tama aosp9/arm32, thank you all for help! now just need to fix few issues with my apps and will be back with aosp10/aarch64 porting. assuming that nothing major will happen with the current release.18:37
poetasterah. remember.  turn it off :)18:38
malpoetaster: what only helps for update to 3.4.0, for 4.0.1 I need patched kernel anyway so it would better to have in 3.4.0 a kernel which would then work with 4.0.1 also18:40
poetastermal: got it, got it. I'm interested in a 3.4.018:41
malpoetaster: well it's possible to update to it if you really want, you just might need to do some extra things when updating to 4.0.1 later18:41
poetasterI don't even have SFOS on the FP2 yet. I'm running SFOS on a volla.18:42
poetasterBut i'd like to install 3.4 on an FP2.18:43
malpoetaster: I can give you a 3.4.0 image for fp2 if you really want18:43
poetasterWhy not. On top of 18, not 19, or?18:44
malit's the same base as in the instructions18:44
poetasteryou mean merproj wiki?18:45
malI need to copy the image to I made some time ago to some place18:48
poetastermal: wait. maybe it's a time waster.18:48
malpoetaster: ?18:52
poetastermal: just realized 19 is on it. I can do a 18.04.1 install on top?18:52
poetasterIt's an old phone (new battery :)18:53
malyes, you can install the old version on top of it18:54
poetasterok. will do. feed me an image.19:21
malpoetaster: did you get the private message with the link?19:38
poetastermal: yes I did.19:48
malrinigus: I pushed the fix to community fpd aarch64 PR21:03
rinigusmal: thank you very much! it should have fixed it, will be able to check tomorrow.21:29
malrinigus: I can test again also21:30
techgeekster@elros34 I did everything from scratch and even implemented some fixes from the channel logs. Still the same problem. Here is the full journal log
malI can't seem to access that paste22:11
techgeeksterLet me reupload it to my gdrive22:11
*** techgeekster_ is now known as techgeekster22:21
maltechgeekster: was that hybris-17.1?22:22
maltechgeekster: you seem to have some issue with selinux22:22
techgeekster@mal no hybris1622:22
techgeeksterI have deactivate it in the boot args22:23
techgeeksterShould I deactivate it in the kernel too?22:23
maldid you see any unpackaged files in droid-hal rpm build?22:24
techgeeksterLet me check22:24
malFeb 09 20:05:47 Mi9TPro droid-hal-init: Could not read properties from '/plat_property_contexts': No such file or directory22:24
malFeb 09 20:05:47 Mi9TPro droid-hal-init: Failed to initialize property area22:24
maldo you see that file anywhere in out/22:25
malin your build environment22:25
techgeeksterthis is the droid-hal build
maltechgeekster_: can you check if you have plat_property_contexts anywhere in $ANDROID_ROOT/out if it's there it's in some subfolder deep down there22:28
techgeekster_As far as I can see it is not found. Checking more as we speak22:29
malthis should tell if it's there: find out/ -name plat_property_contexts22:29
techgeekster_@mal returned empty22:30
*** techgeekster_ is now known as techgeekster22:31
techgeekster@mal In the whole $ANDROID_ROOT folder no results are found for plat_property_contexts22:34
maltechgeekster: so you didn't need straggler files in droid-hal spec?22:34
techgeekster@mal nope22:35
techgeeksterYou can see the files I used for the build here ( The repos are one commit behind, but mostly the same22:36
maldo you see that file on device in /system or /vendor?22:41
maltechgeekster: ^22:43
techgeekster@mal No22:43
techgeeksterneither in /system nor in /vendor22:43
techgeeksterShould I search the phone for this folder? I mean the LineageOs + SFOS combo that is installed right now22:46
techgeeksterOk wait a sec22:46
malnot sure if that is the real issue or not22:46
malbut the property area failure is a problem22:46
T42<elros34> @techgeekster check your $ANDROID_ROOT/droid-hal-$DEVICE.log. Looks like your partitioons are not mounted.22:47
malhmm, indeed no sign of system mount22:48
techgeeksterI cant see any errors of fault. Just some warning. Let me upload the file22:49
T42<elros34> also missing all hybris-16 *.rc files mentioned in hadk-faq22:49
techgeeksterOh ok. I did all the steps of the FAQ. Maybe they were not implemented? Will do those again22:51
malthe first problem to solve is the missing mounts22:51
techgeekster@elros34 This is the droid-hal-raphael-log
techgeekster@mal no such thing on the device either22:52
maltechgeekster: the problem is those other things we just noticed22:52
maltechgeekster: can you show your fixup-mountpoints changes22:53
T42<elros34> unrelated but does sailfish-browser (sfos 4.0.1) also crash for you on that google drive site or it's only my device?22:53
malI haven't tried to use that on sailfish-browser22:54
malmaybe I can test tomorrow22:54
techgeekster@mal these are the mountpoints
maltechgeekster: I think I know the problem22:55
techgeekster@mal Nothing to lose! Tell me!22:56
malcan you run "make modules" in the HABUILD_SDK where you built make hybris-hal22:56
techgeekster@mal Yes, wait a second22:56
maland show the list of modules it prints22:56
malquite sure you bumped into the issue that random devices don't copy everything automatically to out/ like .rc files and fstab file22:57
techgeekster@mal should I share the result via gdrive or pastebin?23:00
maleither is fine23:00
maltechgeekster: do you see any fstab files in out, use this: find out/ -name '*fstab*'23:05
techgeeksterYes, 5 files, 2 in hybris
malhow about init.qcom.rc23:06
techgeekster@mal No results for that23:07
maltechgeekster: ok, copy file device/xiaomi/raphael/rootdir/etc/fstab.qcom to out/target/product/raphael/root/fstab.qcom23:09
techgeekster@mal. Scratch that. One result but not in /out, rather in device/xiaomi/raphael/rootdir/etc23:10
maltechgeekster: then also run make init.qcom.rc in the HABUILD_SDK (make sure you run the needed initial stuff before that i.e. breakfast)23:10
malafter doing that go to platform sdk and use "rpm/dhd/helpers/ -d" to repackage the droid-hal rpms23:11
malthen show again the droid-hal rpm build log23:12
techgeeksterOk. Should I copy and the init.qcom.rc file?23:12
malthat make init.qcom.rc should copy it23:13
techgeekster@mal Oh ok! Will show you the droid-hal build log when it's finished23:14
maltechgeekster: you can check again if the .rc file appeared in out/23:14
techgeeksterThe script put it in hadk/out/target/product/raphael/system/etc/init/init.qcom.rc23:16
malthat is good23:17
techgeekster@mal New droid-hal build log
maltechgeekster: ok, you need to do some changes still but looking better, in the droid-hal spec you have the line with makefstab_skip_entries, in that line replace the /vendor with /23:26
techgeekster@mal I have bunch of entries, including / (%define makefstab_skip_entries / /vendor /dev/stune /dev/cpuset /sys/fs/pstore /dev/cpuctl)23:28
malremove the /vendor23:28
techgeeksterOh ok23:28
malthen rebuild droid-hal rpms again23:29
techgeeksterOkk, doing in now23:29
maltechgeekster: after you have done that also make sure you copy the .rc files mentioned here to correct place in your config repo in case you haven't done it already23:30
malthen it should be time to build a new image and see what happens23:31
mal(of course if you change config repo then first run -c)23:31
techgeekster@mal Okk. I'll do all that and inform you if I get a boot this time.23:31
techgeekster@mal Thank you very much for your time!23:32
deathmist_mal: could you review &
maldeathmist_: yeah, tomorrow23:37
deathmist_cool, those are kinda needed fixes :p23:49

Generated by 2.17.1 by Marius Gedminas - find it at!