Saturday, 2019-10-19

xreactx[m]__ qt5-qpa-surfaceflinger-plugin fails to build... buy why?00:26
T42<birdzhang> @xreactx[m] you can skip it, it's no longer needed00:56
xreactx[m]__ok, whats replacing it?00:57
T42<birdzhang> qt5-qpa-hwcomposer-plugin01:13
Thaodanmal: I have no issue with -b. I prefer it and was annoyed by the asking to build the pkg I've asked for it to build.01:56
xreactx[m]__what would cause an "updater process ended with ERROR: 7" when installing SFOS in twrp?03:16
xreactx[m]__before that it says "failed to extract filesystem!"03:17
T42<Akatsu %lastname%> SSH uses same ip like telnet or different?06:27
T42<Akatsu %lastname%> i have init-degug in real rootfs and have no idea how to enter ssh/telnet now06:33
lbtPSA: / going down for maintenance07:49
deathmistxreactx[m]__: TWRP's tar binary is broken and has a memory leak on many devices now, I've just opted to use "/system/bin/toybox tar" instead like so:
deathmistyou can replace the tar line in hybris-boot's if you want to go that route, another way is by using tar from SFOS' busybox binary from out/08:53
deathmistsometimes even downgrading TWRP a bit helps so you can try that first if you want08:54
vknechtgrrr, QImage loadData not able to handle NV12 QVideoFrame data... is that expected ?09:02
vknecht^ abranson ? :-)09:03
deathmistxreactx[m]__: if you opt to use my solution obviously use "/system/bin/toybox tar -xj -f $FS_ARC -C $FS_DST" instead for the line as I've made a custom installer solution and changed A LOT of things :p09:06
deathmistmal: I'll try minimer too as I get no UI during boot either and test_hwcomposer still segfaults but now the 32-bit lib is present and it at least seems happy about that09:10
deathmistmal: it seems I've also forgotten how to enable networking over telnet as I've not had to do this for many months at this point xD I need it to install "qt5-qtdeclarative-qmlscene" and I don't want to make new build just to get a single package installed09:45
vknechtmultimedia-private & qt_imageFromVideoFrame() works :-)10:35
T42<adampigg> vknecht: does that pass harbour ?11:20
vknechtseems so11:20
vknechtstill have to battle to get orientation information from metadata :-/11:21
vknechthopefuly should be easier and more complete from c++ side than from qml...11:23
malThaodan: I tried -b and it didn't ask anything11:24
deathmistmal: look like I also can't package the 32-bit to my dcd sparse files as it causes "nothing provides needed by droid-config-cheeseburger" during mic build :/11:41
maldeathmist: did it actually help?11:43
deathmistlipstick still didn't start but test_hwcomposer didn't say anything about it missing anymore, still segfaulted tho. now gonna try out minimer or sohuld I give strace for stuff?11:47
malmaybe strace11:48
malnot sure if that lib is compatible or not11:49
deathmistmal: here's strace again for test_hwcomposer I also modified lipstick.service to output strace to a file in a similar fashion
deathmistmore specifically, I changed ExecStart line to "ExecStart=/usr/bin/strace -f -o /sdcard/lipstick-strace.log /usr/bin/lipstick $LIPSTICK_OPTIONS --systemd"  and grabbed log after rebooting to TWRP12:06
maldeathmist: looks like it crashes at the same place as before12:29
deathmistdamn. could it be something to do with the EGL libraries "not existing" as in they're just named differently on my device?12:47
deathmiste.g. it's looking for "/system/lib/egl/" but it's "/system/lib/" on my phone and also stuff like "/vendor/lib/egl/" vs "/vendor/lib/egl/"12:48
maldeathmist: hmm, does it find the egl libs or not? if not then add some symlink13:03
piggzmal: did you find that silia config?13:05
malpiggz: sorry, not yet, I out most of today13:09
T42<Akatsu %lastname%> how can i add libminsf to build?13:26
T42<Akatsu %lastname%> i executed ` make -j4 libdroidmedia minimediaservice minisfservice libminisf` and it shows that it builds something13:26
nitin03device xiaomi poco f113:41
nitin03base lineage 16.0....already build sfos zip without any critical errors and flashed it but device not booting... checked dmesg on host13:42
nitin03but it is showing up same as android13:43
nitin03and check lsusb android shows up  iSerial                 3 d4df6fef13:47
nitin03but on sfos nothing shows up13:48
nitin03device is getting stuck on boot logo and stays there for 1 to 3 minutes then reboots and gets stuck at boot log again and it is going on and on13:50
deathmistnitin03: check if "/data/.stowaways/sailfishos/init.log" exists from TWRP and adb shell13:51
nitin03ok wait a minute13:51
deathmistit's probably a misconfigured defconfig or boot cmdline13:51
nitin03yes there is a init.log file13:51
deathmistcan you put up a paste of it?13:52
nitin03should i pull it and share it13:52
nitin03   init.log13:54
T42<Akatsu %lastname%> (Photo, 1280x471) Do i have toi add every missing file under straggler_files ? I mean ones which arent dirs13:55
nitin03deathmist   init.log13:56
deathmistah, it can't setup rndis on interface usb0 or rndis0 which are the very common ones for devices (mine is usb0)13:57
deathmistcan you link your defconfig? it doesn't look like it even has a USB interface (probably missing options)13:58
nitin03any way to tackle this13:58
deathmistnitin03: look like your device uses configfs. you can attempt to use my defconfig changes for telnet (SD835 SOC on hybris-16.0 too): while making sure they stick in .config too (find out/ -name .config)14:06
nitin03thank u..i will get back to u14:07
deathmistthen "mka hybris-boot" habuild env obviously, flash and boot new image => get init.log again unless you can telnet in with "telnet 2323"14:08
nitin03can i send u direct msg next time?14:08
nitin03thanks , I will check it...and i should check .config file in KERNEL_OBJ of my target device14:10
nitin03if these changes are there or not?14:11
deathmistyes, then you know if the changes are actually in the new hybris-boot.img you're going to flash14:11
nitin03thank you so much...i will get back to u14:12
T42<Akatsu %lastname%> any idea why it does not detect tools after build packages run? i get zypper/sb2/mb2 not found even if i had it working yday14:28
T42<Akatsu %lastname%> probably im idiot trying execute something from platform sdk inside of habuild14:29
xreactx[m]__now I'm getting ended with ERROR 614:45
deathmistxreactx[m]__: check /tmp/recovery.log, it'll tell what's actually going wrong14:46
xreactx[m]__one place i failed to look14:46
xreactx[m]__i think I know whats going on... i'm going to try something and report it later15:00
T42<Akatsu %lastname%> why i get these sailfishOS binaries like minisf compiled under codename/system instead of codename/root/system?15:26
T42<Akatsu %lastname%> It cannot find them15:26
vknecht@Akatsu %lastname%: that's part of droidmedia, did you build it ? it's section 13.2 of hadk pdf15:29
T42<Akatsu %lastname%> yes15:35
T42<Akatsu %lastname%> i see that its part of system android build15:35
T42<Akatsu %lastname%> but we arent flashing new base right? only sailfish rootfs which sits on /data15:36
T42<Akatsu %lastname%> (Photo, 1280x486)
vknechtnot sure what you mean ; when you build droidmedia package, its rpm put in droid-local-repo and integrated in sfos image when you build it15:39
T42<Akatsu %lastname%> ok, wrong i didnt do 13.2 part i have finished on 9 or so15:39
T42<Akatsu %lastname%> now i probably have it die on droid-hal-init15:42
T42<Akatsu %lastname%> after masking init phone somehow reboot into fastboot from telnet15:46
deathmist@Akatsu does the device reboot with it unmasked too? if not then you really don't need to mask because you don't get any android side stuff up e.g. graphics and whatnot15:53
deathmistI say try to get a "journalctl -b" log, maybe dmesg15:53
deathmistwith DHI unmasked if it doesn't make the device unstable15:53
T42<Akatsu %lastname%> i tried to run init by hand and im not sure but it looks like its not mounting partitions well15:55
deathmistshow your device fstab, it's in your android_device_* repo somewhere15:55
deathmistand output of mount after init has ran15:56
T42<Akatsu %lastname%>
T42<Akatsu %lastname%> dmesg | grep "mount" is enought?15:57
deathmistmake sure droid-hal-init has executed, then output of just "mount" command, nothing else15:58
T42<Akatsu %lastname%> how can i bring it back after masking?15:58
deathmistunmask => systemctl unmask droid-hal-init (or if you can't then remove the service symlink from /etc/systemd/*)15:59
T42<Akatsu %lastname%> i made it via ln -s16:00
deathmistbut you'll have to reboot too obviously to make it run16:00
deathmistyou can run DHI only once16:00
T42<Akatsu %lastname%> mount only shows me mount on /data16:01
T42<Akatsu %lastname%>
T42<Akatsu %lastname%> I do have mounts done in fixup-mountpoints16:02
deathmistthis was on 15.1 base right? you can add a system.mount unit for systemd so that gets taken care of: (NOTE: the ../ lines aren't content, it's a symlink to the file outside .wants dir and obv change device path)16:05
T42<Akatsu %lastname%> yes 15.1 base16:06
T42<Akatsu %lastname%> i will try soon. what about these libminisf which i pointed before? where do they need to be standard /system or inside rootfs system?16:09
deathmistabout the other patitions, you'll likely need to add some straggler files in dhd spec file for /dsp /firmware /persist dirs at least and "-detritus" pkg in dcd patterns (change cheeseburger to your codename obviously)16:10
deathmistSFOS doesn't touch your /system, idk what you are trying to do with libminisf right now16:12
T42<BusterBg_18> deathmist: did you got GUI to start on 16.0?16:23
deathmistBusterBg_18: nah, both test_hwcomposer and lipstick fail still16:23
deathmistdroid-hal-init is fine tho16:24
deathmistthere's also minimer in faq-hadk, but I've not tried the new image I built yet16:25
deathmistI forgot how to get networking via rndis on the device so I just made a new image in the end lol16:26
T42<BusterBg_18> I didnt know that you could get networking on a device using rndis:016:27
deathmistxreactx[m]__: have you figured out the "set_perm" function issue yet on the script?16:30
deathmistno clue how ET_PERMISSIONS% got expanded into that, it was an issue back in 2015 and the line should be something like set_metadata("/tmp/", "uid", 0, "gid", 0, "mode", 00755); instead now16:37
deathmist oh it does an Android version check and should ONLY use set_perm if < 4.4, no clue how that got into your script16:42
T42<BusterBg_18> I took logs once more, I dont see any changes from yesterday dmesg journalctl16:44
deathmistxreactx[m]__: you sure you have that "ANDROID_VERSION_MINOR := 0" line in your hybris/hybris-boot/ ? I can only think of it failing if that was not set for 9.016:46
deathmist@BusterBg_18 do a "find / -name plat_property_contexts", for me I had to do "ln -s /system/etc/selinux/plat_property_contexts /plat_property_contexts"16:49
deathmistthen reboot, get new journal16:51
T42<BusterBg_18> I got find: /sys/kernel/slab/L2TP/IPv6: No such file or directory16:53
deathmistok, do "find / -name plat_property_contexts 2>/dev/null" instead to hide all the useless stuff16:54
deathmistwait, nothing else then?16:54
T42<BusterBg_18> I also gotfind: /sys/kernel/slab/L2TP/IPv: No such file or directory16:55
T42<BusterBg_18> running 2>/dev/null returns nothing16:56
deathmistright. well, in that case run "find out/ -name *property_context*" on your hadk source tree, it should return some file in the root/ dir16:57
deathmist@BusterBg_18 looks like you'll also need straggler files too + mount units for /system and /vendor just like I did. check out & while ofc adapting for your partitions, device codename in files etc17:01
T42<BusterBg_18> Well It didnt fount anything either17:03
T42<BusterBg_18> I do have straggler files tho17:03
deathmistonce you've done the changes in the last msg I sent rebuild hybris-hal, build_packages -d & build_packages -c, then new mic build and flash the new build17:10
deathmist@BusterBg_18 you may also need to regenerate kickstarts, check hadk pdf for regular build steps :p17:25
T42<BusterBg_18> No prob :p17:25
T42<DylanVanAssche> My magnetometer is working now in sensorfwd (scaling overide was needed for the IIO sensor).17:36
T42<DylanVanAssche> However, the X value is a factor 10 too small (in comparison to the Xperia X) and the Z value is a factor 60 too big (in comparison to the Xperia X). Is that 'normal' that this kind of sensor is way off between devices?17:36
deathmist@BusterBg_18 I'm looking at the changes and I think you already made a mistake on the mount units: the "What=" like should have a full valid path to your partition in it (e.g. "/dev/mmcblk0p79" or something), not something like "/mmcblk0p79" as that doesn't exist on your device17:37
T42<BusterBg_18> You are right, I was missing /dev17:38
T42<BusterBg_18> I forgot about how it was shown on init17:39
deathmistyou can check that those paths exist on the device as it's booted currently still right? I think those are the same even in TWRP17:40
T42<BusterBg_18> Yep I just checked on telnet and they exist17:43
deathmistonce you boot the new image get output of "mount", it should now show your /system and /vendor etc nicely mounted18:03
T42<BusterBg_18> indeed: /dev/mmcblk0p79 on /system type ext4 (rw,relatime)18:09
T42<BusterBg_18> /dev/mmcblk0p80 on /vendor type ext4 (rw,relatime,data=ordered)18:09
deathmistalright, nice. now check systemctl status droid-hal-init18:11
deathmistit'll probably still fail, you can give updated journal again18:11
T42<BusterBg_18> systemctl18:12
deathmistDHI definitely failed, probably since it's still missing /plat_property_contexts. try "find / -name *property_context* 2>/dev/null" on the device this time18:13
T42<BusterBg_18> Yay, it now shows something: /vendor/etc/selinux/vendor_property_contexts18:14
T42<BusterBg_18> /system/etc/selinux/plat_property_contexts18:14
deathmistprogress :) now ln -s /system/etc/selinux/plat_property_contexts /plat_property_contexts18:14
deathmistand reboot18:14
T42<BusterBg_18> Should I ignore the vendor one?18:15
deathmistthe filename is not "plat_property_contexts" which is what it's looking for in last journal so yes18:16
T42<BusterBg_18> Well so now im running journalctl -alb --no-pager but the output is bigger than what putty shows18:20
deathmistcheck DHI status again18:20
T42<BusterBg_18> Ok, here is it
T42<Akatsu %lastname%> @deathmist how im supposed to write mount for vendor if i have it inside /system ?18:25
deathmistwell you don't need it then18:25
deathmistyou only need vendor mount if you have a newer device with treble support18:25
T42<Akatsu %lastname%> well i might get treble on it in future18:26
T42<Akatsu %lastname%> (Photo, 353x105) very likely18:27
T42<BusterBg_18> If people managed to do it for xiaomi_kenzo I think its possible for a lot of devices18:28
deathmist@BusterBg_18 how about journalctl? systemctl is quite useless especially if stuff fails18:30
T42<Akatsu %lastname%> its just tons of work for them18:31
jellyponyHello everyone. I'm building SFOS for nitrogen (mi max 3). Hybris is 16. Got fail in droid-hal-init. I figured out that it is because /system cant be mounted. It seems like it is because fstab.qcom of my device don't have /system in it. What is an appropriate way to fix this? Just manually add it there and rebuild hybris-hal?18:34
jellyponymy fstab.qcom:
T42<Akatsu %lastname%> @deathmist can i create these two mount files inside rootfs or do i need to create image with them?18:35
deathmistjellypony: check previous channel logs from me today, I listed a mount unit for /system which you'll need too18:35
deathmist@Akatsu sure, you can make them on the phone (omit sparse/ from paths in that case) but changes to droid-hal, spec or pattern files needs an image rebuild18:36
deathmistyou only needed the one for /system and the ../ one is a symlink18:37
T42<BusterBg_18> I had to use microsofts telnet client for me to get the full output18:37
T42<Akatsu %lastname%> i did that and still i see no result sadly18:40
deathmist@Akatsu no /system mounted after restarting or systemctl start system.mount? did you change the device path to match your /system partition?18:44
T42<Akatsu %lastname%>
deathmistdidn't I say ../ is a symlink?18:47
T42<Akatsu %lastname%> uh im idiot once again18:47
deathmistthe whole entry is a symlink to the file outside the .wants directory, this is how systemd works on every machine18:47
T42<Akatsu %lastname%> i have to symlink from system to local-xxx rite?18:47
deathmistremove the old file with literal "../" in it and "ln -s ../system.mount /lib/systemd/system/"18:48
T42<BusterBg_18> deathmist: do you dual boot sailfish and lineage?18:54
deathmistI do, for now even if my SFOS side is broken on 16.0 I can just switch boot target to LineageOS and at least have alarms etc working properly without having to wipe everything and set something else up18:55
T42<Akatsu %lastname%> and still i get no system mounted18:56
T42<BusterBg_18> I saw your boot switcher on your git that why I ask, much prettier than just flashing boot backup (thats what I do)18:57
deathmist@BusterBg_18 you should start checking channel logs between me and mal from yesterday as you seem to be in the same situation, specifically the ld.config.28.txt thing etc and see if they help you get further and have DHI not fail18:58
deathmistit's basically just a glorified dd command switching between boot.img backups in a flashable zip :) (tho I do other fixups for SFOS side too which I revert/apply depending on target)19:00
T42<Akatsu %lastname%> DMESG from mounting19:03
T42<Akatsu %lastname%> function not implemented looks weird19:04
T42<Akatsu %lastname%> it doesnt even want to mount by hand19:07
T42<Akatsu %lastname%> mount -t ext4 /dev/block/mmcblk0p27 /system19:08
deathmist@Akatsu cuz you don't have the filesystem enabled in kernel also do "chmod 644 /lib/systemd/system/system.mount", not sure how you created that file but you definitely did it in a weird fashion. also does /dev/block/mmcblk0p27 exist or is it /dev/mmcblk0p27 ?19:08
jellyponydeathmist: so for me line "what=dev/sde21" should look like "what=/dev/block/mmcblk0p77"19:10
jellyponyAm i right?19:10
T42<Akatsu %lastname%> again you are right, /dev/block/mmc* is symlink to /dev/mmc19:10
T42<Akatsu %lastname%> just ran ls -l19:10
deathmistdo you even have a /system directory then? what is the error it gives when you mount manually?19:10
deathmistjellypony: look about right, tho I think /dev/mmcblk0p77 would also work fine :) (check on device with ls /dev/mmcblk0p77 to make sure it exists)19:11
T42<BusterBg_18> Will do, Im just going to first setup a clean lineage to use, afterall sirius its my only device atm19:11
T42<Akatsu %lastname%> made system with mkdir, used `mount -t ext4 /dev/mmcblk0p27 /system` no single msg appear, and its still not mounted19:11
deathmistso you didn't have /system then? what does "mount" command output now? how about echo $? after you mount /system by hand?19:12
T42<Akatsu %lastname%> when i have no system inside rootfs and i do command mentioned before i get `mount: /system: mount point does not exist.`19:13
deathmistwell obviously since it needs a directory to exist so it can mount it19:14
T42<Akatsu %lastname%> thats why i made system directory with mkdir19:15
T42<Akatsu %lastname%> and it gave no error but not mounted at same time19:15
deathmisthow are you checking if it's not mounted? ls /system? and you still haven't give me output of "mount"19:15
T42<Akatsu %lastname%> i check by mount and ls -l, secundo19:16
T42<Akatsu %lastname%>
deathmistkeep /system created and reboot now, the system.mount unit should do it's work unless you're missing something else maybe in kernel defconfig19:21
T42<Akatsu %lastname%> i miss autofs419:21
T42<Akatsu %lastname%> do you recommend to get all warnings done?19:22
T42<Akatsu %lastname%> halium have nice auto fixing script19:22
T42<Akatsu %lastname%> mka hybris-boot will be enought?19:23
deathmistyep and flash hybris-boot.img to boot partition after to check, .config in out/ is also useful to see if your options actually get set in boot image19:24
deathmistI reckon the halium config option fixup script could easily be adapted to also work with mer-hybris defconfig changes. some of them rely on specific kernel version etc too tho which could be more difficult to detect in some cases. all the data is here tho
deathmistalso all of those still don't even guarantee working telnet because of configfs vs old android USB method of doing stuff etc, a bunch of stuff is very kernel and device specific19:29
T42<Akatsu %lastname%> thats same for halium, even with their script we have to look at specific parameters like config_dummy not being modified19:37
T42<BusterBg_18> I want to give halium a try just for ubports, but being stuck with either 5.1 or 7.1 is a bummer19:39
T42<Akatsu %lastname%> i got like 2 devices to boot ubports on 7.119:40
T42<Akatsu %lastname%> having it working is different story19:40
T42<BusterBg_18> So it also requires more modifications? I thought it was build and good to go like GSIs on Android19:42
T42<Akatsu %lastname%> not really19:42
T42<Akatsu %lastname%> for example audio is issue sometimes19:42
T42<Akatsu %lastname%> ril/modem19:42
T42<Akatsu %lastname%> however getting device to boot os is much easier19:43
T42<Akatsu %lastname%> i have phone on msm8916 and with newest device tree i have issues with modem so i get audio ripped too, mer-hybris init changes even blocked executing init files because ro.hardware was definied as unknown, i had to make dirty-hacks on it.19:44
T42<BusterBg_18> That explains why I don't hear about any device having usable ubports19:48
T42<Akatsu %lastname%> one Xperia seems to be in pretty good shape19:48
T42<BusterBg_18> I bet that Xperia is suzu/X19:51
T42<Akatsu %lastname%> yas19:52
T42<Akatsu %lastname%> `[  412.866692] EXT4-fs (mmcblk0p27): mounted filesystem with ordered data mode. Opts: (null)` and still nothing, is it even normal?19:54
deathmistnormal message, I don't understand how /system still could not be mounted, check systemctl status system.mount19:56
T42<Akatsu %lastname%> `system.mount: Unit is bound to inactive unit dev-block-mmcblk0p27.device. Stopping, too.`19:57
maloh, that should not have block in it, show your fixup-mountpoints file19:58
malalso fstab from your device repo19:58
T42<Akatsu %lastname%> i have pasted all possible mountpoints in it19:59
T42<Akatsu %lastname%>
T42<Akatsu %lastname%>
malshow the file /lib/systemd/system/system.mount from your device20:01
T42<Akatsu %lastname%>
T42<Akatsu %lastname%> ignore first i made it symlink already20:02
T42<Akatsu %lastname%> wait20:02
maland that was made automatically?20:03
malor did you somehow manually edit that?20:04
malbecause that shouldn't have block/ in the "What" part20:04
T42<Akatsu %lastname%>
T42<Akatsu %lastname%> i changed it to /dev20:06
T42<Akatsu %lastname%> because one inside block was just symlink20:06
T42<Akatsu %lastname%> ok20:07
T42<Akatsu %lastname%> something is wrong20:07
T42<Akatsu %lastname%> gonna change again20:07
T42<Akatsu %lastname%> seems like it works20:10
T42<Akatsu %lastname%> at the end i needed to fix autoFS4 for it anyway20:10
T42<Akatsu %lastname%> for what do we have fixmountpoints if we have to deal with it inside sailfishOS?20:15
deathmisthadk pdf chapter 5.3 explains this20:18
malyou have data partition as something else than ext4?20:19
deathmistmal: hist last mount output shows it at least as ext4
T42<Akatsu %lastname%> is it normal to have plat and nonplat_property_contexts instead of property_contexts ?20:29
malyes, new android bases have different names for contexts files20:30
T42<Akatsu %lastname%> and this should work then?20:30
T42<Akatsu %lastname%> do i have to do manual booting on rest partitions on which android-hal-init failed to get it working?20:31
malwhat do you mean?20:31
malyou can check if those mount services have correct device node20:32
T42<Akatsu %lastname%> i get errors on odm, android-hal-init strace shows me errors about not being unable to open or find file20:32
malif not then something is wrong in your build, based on the fstab and fixup those should have been ok, unless it find wrong fstab, can you check output of make hybris-hal what it says after "/data appears to live on"20:35
T42<Akatsu %lastname%> I will look on that tomorrow20:37
T42<BusterBg_18> mal: I dont have a ld.config.28.txt on my device instead its called ld.config.vndk_lite.txt, should I just change
T42<BusterBg_18> The contents of that are similar to the ones in ganges and cheeseburger21:42
malI think the didn't mount it properly so for now try remounting /system manually as rw, backup the original file and the edit it as mentioned earlier (add the lines with libexec in ganges repo to your file) in /system and the remount as ro again and it hopefully helps21:57
T42perrsona1234 was added by: perrsona123422:10
T42<perrsona1234> Hi all22:10
T42<perrsona1234> I have a question. In Your opinion: is Sailfish more mature than Ubuntu Touch?22:12
T42<perrsona1234> Because I'm currently thinking about buying a "new" phone, because I badly damaged my current one.22:12
T42<BusterBg_18> would this work out?
T42<BusterBg_18> It seems that ld.config28 and vndk_lite are more different after all22:26
mal@BusterBg_18 not sure if you need that or not, depends on what the actual error you have is22:29
T42<BusterBg_18> well, DHI is failing
T42<BusterBg_18> I was trying th ld.config stuff to see if it would help22:33
mal@BusterBg_18 can you check the /usr/libexec/droid-hybris/system/etc/init/servicemanager.rc file for a line with selinux_stubs22:58
malalso did you check if out/ has any files related to fstab and ueventd*.rc23:00
malthere are several things that can be wrong23:01
T42<BusterBg_18> I have setenv LD_PRELOAD /usr/libexec/droid-hybris/system/lib64/libselinux_stubs.so23:02
*** jellypony1 is now known as jellypony23:03
T42<BusterBg_18> And ueventd.rc is present under out/*/sirius/root23:07
jellyponydeathmist: oh shi~ its booted23:10
jellyponybut no gui and no open ports on
jellyponymal: Hi! Can you help me? What exactly can cause this? Device probably booted (it vibrates!!!) after few changes in systemd via telnet (mounting /system). But now there is no gui and i cant get any access to it. There is only IP i can ping and all it ports are closed.23:16
mal@BusterBg_18 check output of "make modules" (same environment where you run make hybris-hal) and see the output for fstab or ueventd*23:19
maljellypony: the ip is and port 232323:19
jellyponyit was...23:21
T42<BusterBg_18> I dont see fstab or ueventd when running make modules23:22
maljust to be sure, what kind of changes did you do to kernel defconfig, go to the kernel source directory (somewhere under kernel/ in ANDROID_ROOT) and run "git diff" and show the output of that23:25
T42<BusterBg_18> But thats just the most recent change isnt it?23:30
malyou had some older changes you commited to git already?23:33
T42<BusterBg_18> Yes23:34
malwhat device was that again?23:34
malI used to remember what device everyone had but not anymore23:34
jellyponymal:I used nmap. The only IP is No open ports D:23:35
T42<BusterBg_18> xiaomi_sirius23:36
maljellypony: so .15 doesn't work?23:43
jellyponyno :c23:45
maldoes the device show anything in host dmesg, some usb related messages?23:49
jellyponymal: yes!
malto me that suggests it rebooted after 30 seconds23:55
malhmm, actually the timestamp is missing from the disconnect but I assume it's close to the next line23:56
jellyponymy bad23:57
maljellypony: which android base?23:58
jellyponyhybris 1623:58

Generated by 2.17.1 by Marius Gedminas - find it at!