Saturday, 2019-12-14

T42岳兴焦 %lastname% was added by: 岳兴焦 %lastname%01:10
T42Bradley %lastname% was added by: Bradley %lastname%07:32
masya_Hi. Trying to port for Xiaomi Mi A2 (jasmine_sprout) with LOS-16.0. After "make hybris-hal" get this error: FindEmulator: find: `tools/metalava/manual': No such file or directory. How to solve it?07:35
vknechtguess either it's missing from the manifests so you could add it to your local manifest, or the reference to it should be removed (not sure what best option is, probably first one)07:41
deathmist@masya_ please do "mka clean" in your HA_BUILD environment now as you probably messed things up, then follow steps in
deathmist(ignore config repo / build_packages thing for now, you'll get to it in HADK section 7.1)07:43
deathmistmasya_ also you need to run "hybris-patches/ --mb", that really needs to be in the document already07:52
deathmist@BusterBg_18 we made droid-hal build generate another set of udev rules using vendor udeventd.rc from device itself and extracted them from the built RPM to put in droid-configs, you could take a look at /vendor/ueventd.rc and check if permissions & ownerships match on some file(s) in /dev with "ls -l"08:03
deathmistyou can also try "make modules" from HA_BUILD env ofc and afterwards check output of "find out/ -name *uevent*rc"08:07
T42<岳兴焦 %lastname%> (Photo, 566x656) 🗣contact 👥联系👤: @Tinpol08:17
masya_Found a Metalava repo in /hadk/.repo/manifests/default.xml. It is commented. Trying to un-comment and resync09:08
deathmistmasya_: please just follow what I said earlier09:08
deathmistmelatava should not be needed for anything hybris-hal related, it just means you didn't apply patches09:12
riniguspketo: please add XZ2c dual for store access. device is "Xperia XZ2 Compact (h8324 / h8324)" . ssu s returns the first imei as device id.09:29
masya_Ok. Now i get this error
rinigusthere are some issues with that device still, but its unrelated to the store/ids (4g not working and a weird crash) I am waiting for logs from the user09:30
deathmistmasya_ please give full log after "mka clean" and "mka hybris-hal"09:33
deathmistalso show manifest09:34
rinigusmal & vknecht: I recompiled systemimage/vendorimage with dbus selinux patch, pulled from these images /system/etc/selinux/plat_sepolicy.cil and /vendor/etc/selinux/precompiled_sepolicy. as a result, I have now selinux set to permissive and all seems to work09:36
rinigusvknecht: I will adjust hadk docs accordingly in the systemimage/vendorimage section. just let me run a test commands first, before I make the change09:37
rinigussorry for mistake09:38
vknechtrinigus, nice... getting some progress too with latest libhybris: no crash, but lipstick doesn't seem to kick in
vknechtwonder if I need "configs: Exit unlock ui before executing startup wizard"09:40
vknechtthere's even some hwcomposer info printed from invoker09:40
rinigusnot sure which configs are you talking about... do you mean that there is some patch which you miss?09:43
rinigusvknecht: ^09:43
vknechtrather a configs submodule update09:43
vknechtjust a guess, will have to try09:45
rinigusvknecht: I guess I will have to start tracking the changes in those repos as well09:47
pketorinigus: added10:12
Mister_Magisterhi pketo10:27
riniguspketo: thank you!10:33
pketohello Mister_Magister :)10:36
Mister_Magisterpketo: u doin great job keep it up!10:44
T42<elros34> just for the record: looks like EGL_PLATFORM=fbdev must be defined even for eglfs on sunxi otherwise lipstick crash on start12:51
T42<elros34> does that updated wireless-regdb works? I had to copy regulatory.db* to /lib/firmware/ to be even loaded but it fails anyway: cfg80211: loaded regulatory.db is malformed or signature is missing/invalid13:14
rinigusvknecht: instructions are updated, should work now15:02
malhas anyone had issues with video playback on hybris-14.1/android7 base?15:17
T42<adampigg> What kind of issues?15:40
mal@adampigg it's not woeking at all, codec seems to work but then app just hangs after a few frames17:01
*** OhYash1 is now known as ohyash19:26
deathmistI assume setting installable_zip macro to 0 will disable building a zip / running the packer KS or? I use a custom installer implementation and a modified packer script and don't need any of the files/scripts from hybris-boot + those also end up on /boot on my device which seems completely unnecessary21:59
deathmistthe 3 files I'm talking about are hybris-updater-script, & update-binary provided by droid-hal-$DEVICE-img-boot RPM and them ending up on my SFOS rootfs in /boot/22:03
T42<edp_17> Good evening.22:35
T42<edp_17> @Elros, you were right about the partition mount parameters. I have removed the udev and re-run the mic. This time the led has light up and the device got a mac and ip address. I could telnet in to check the logs.22:36
T42<edp_17> Here they are:22:37
T42<edp_17> mount:
T42<edp_17> systemctl list-units -t service --all:
T42<edp_17> systemctl list-unit-files:
T42<edp_17> systemctl status -l dbus.service:
T42<edp_17> However the dbus.service is active, the command 'systemctl --user restart lipstick' gives me 'Failed to get D-Bus connection: No such file or directory'22:38
T42<edp_17> Oh, and this time I have /system mounted.22:40
deathmist@edp_17 what does your device fstab look like? I think you may still be missing a few (though I mostly have experience with LOS >=15.1)22:43
T42<edp_17> fstab:
deathmistno I mean like fstab.qcom in your device/ trees22:45
T42<edp_17> Oh, sorry. I go an check.22:45
T42<edp_17> In the $ANDROID_ROOT I have common, qcom and samsung.22:48
T42<edp_17> In $ANDROID_ROOT/qcom I have common and sepolicy22:48
T42<edp_17> In $ANDROID_ROOT/qcom/common I have a few folders and files but there is no fstab22:48
T42<edp_17> or fst.qcom22:48
deathmist@edp_17 run "find $ANDROID_ROOT/{device,out}/ -name fstab.*" and if it doesn't find it try with *.fstab instead maybe22:52
T42<edp_17> the find ... fstab.*:
T42<edp_17> The find ... *.fstab returned only one location in $ANDROID_ROOT/device/samsung/hero-common/ramdisk/recovery.fstab22:56
T42<edp_17> Which one should I check?22:56
deathmistfstab.samsungexynos8890 is the one you should look at22:56
T42<edp_17> I have 3 of them in 'out/target/product/herolte/root/'22:57
T42<edp_17> 'out/target/product/herolte/obj/BOOT/'22:57
T42<edp_17> and 'out/target/product/herolte/obj/BOOT/fstab.samsungexynos8890_intermediates/'22:57
deathmistthey all should be copies of each other, everything in out/ is copied there or generated in some other way22:59
T42<edp_17> I see. Thank you.23:00
deathmistlooks like it generated everything properly :p  can you give full journalctl -b after booting23:03
T42<edp_17> There is always --More--. How many screens of journalctl should I copy in? Thank you.23:07
deathmistdo "journalctl -b > journal.log" and grab the file instead ^^23:07
deathmistand on the device ofc NOT host @edp_1723:08
T42<edp_17> Thanks. I have ran it on the device :), now I am trying to pull to pc be able to show you.23:09
T42<edp_17> Yeah, I probably need to boot into recovery. Give me a minute.23:10
deathmistyou could also enable USB networking as per HADK 9.3.3 and copy it via SSH if you don't want to fully reboot :p23:11
T42<edp_17> It is 2.9MB I am not sure I can put this into pastebin.23:11
deathmist2.9M right after boot?23:12
T42<edp_17> Thank you, I will try 9.3.323:12
T42<edp_17> Yes.23:12
T42<edp_17> Wait a second, I do a fresh boot and grab the file again to double check the size.23:13
T42<edp_17> Now, it is 3.1 MB23:14
T42<edp_17> Nooooooo, that was the speed of the copy!! Sory!!23:15
T42<edp_17> It was 325k:
T42<edp_17> Seemingly there is a problem with the droid-hal-init.service. And the RILD.23:19
deathmist@edp_17 droid-hal-init: Failed to initialize property area <-- is your biggest issue currently, I got that fixed by just mounting /vendor but since you're on Nougat you may have straggler files in out/.../root/*property_contexts which you'll need to package in23:21
T42<elros34> I am pretty sure I mention it that you need detritus package and straggler files which you had defined earlier23:23
T42<elros34> It's need to get droid-hal-init working23:24
T42<edp_17> I remember that those straggler definitions were there before I refreshed the submodules from scratch.23:25
T42<edp_17> I go an find these in DRiim's repo because I lost them.23:25
T42<elros34> these should be detected durring droid-hal build but rpm checking for installed and unpackaged files is  currently broken. Fix is known but who knows when it will be included, hope before sailfish 423:27
T42<edp_17> I have found the straggler file definitions and added into droid-hal-herolte.spec23:29
T42<edp_17> Now I guess should re-run the Mic bit.23:29
deathmistbuild_packages -d & remember to add your droid-hal detritus package to patterns like in to get the RPM included in your images, for now you could also install it manually on the device with zypper instead of new mic image23:30
T42<edp_17> So, I do not need to re-build the stuff only install that detritus package?23:32
deathmistyep, I mean that should be the only change you did locally on build tree since the last image you currently have installed on the device? if so just copy the detritus RPM to rootfs and install manually, then reboot and give new journal probably23:33
T42<edp_17> Ok, but I still need to re-run the process to create the packages, right? (I have checked and didn't find this detritus package in the droid-local-repo.)23:37
deathmistduh you run build_packages -d to generate it now23:37
T42<edp_17> Yeah, I got that in this very moment. It is running. Sorry I am a bit dumb. 😜23:38
T42<edp_17> detritus package built, installed on the device and rebooted. Still stuck on the Samsung logo but the light is on and I can telnet into it. Fresh journalctl is here:
deathmistDHI second stage is reached now, one problem solved :)23:52
T42<edp_17> Cool. :)23:54
T42<edp_17> I cannot connect with ssh because I have no idea about the generated password. I guess the telnet is good for everything I need to alter on the device.23:55
T42<edp_17> I meant if I need to alter something...23:56
deathmistuse telnet until you get GUI, you can always "su - nemo"23:56
mal@edp_17 which hybris branch did you use (i.e. which android base)?23:56
T42<edp_17> CM-14.123:56
mal@edp_17 did you run the script mentioned here
malbased on your log you didn't run that23:57
T42<edp_17> Yes I did.23:57
T42<edp_17> I remember this and I ran that script.23:58
malreally? it doesn't show those being used, check line 2744 which only shows one .rc file in that folder23:58
mal(line 2744 in the log you showed)23:58
mal(Parsing /usr/libexec/droid-hybris/system/etc/init/servicemanager.rc took 0.00s.)23:58
T42<edp_17> I ran that once, but not every time when I re-compiled the kernel.23:58
malwhat commands did you run after running that script?23:59
maldid you run "build_packages -c"?23:59
malbefore building the image23:59
mal* -c23:59

Generated by 2.17.1 by Marius Gedminas - find it at!