Wednesday, 2023-05-17

CarbontatedCaffeineIs this a ngfd problem?00:00
malprobably many issues00:07
malngfd and some others can be probably fixed by something like the symlinks in lib and lib64 folders are probably needed, you need to find the targets for the symlinks on your device00:08
maldid you yet check what the vendor partition contains on your device?00:09
CarbontatedCaffeineThe targets being, the libraries?00:10
CarbontatedCaffeine"did you yet check what the vendor partition contains on your device?" Uhh it isn't mounted00:10
mallike I said before, try mounting it manually and see what it contains00:10
CarbontatedCaffeineI still don't know whether I need it or not00:10
malthat is why I asked you to check what it contains to see if it's needed or not00:11
malyou need to find where the actual file in those symlinks are on your device00:11
malso for example "find / -name"00:11
CarbontatedCaffeine"/system_root # mount /dev/block/bootdevice/by-name/vendor_a ./vendor/ mount: /system_root/vendor: wrong fs type, bad option, bad superblock on /dev/sda31, missing codepage or helper program, or other error.        dmesg(1) may have more information after failed mount system call."00:12
CarbontatedCaffeine"/ # find / -name find: /sys/kernel/slab/L2TP/IPv6: No such file or directory find: /sys/kernel/slab/L2TP/IP: No such file or directory /system/apex/ /system/apex/ /system_root/system/apex/ /system_root/system/apex/"00:13
malso you have the target in that list, the system one, of course pick the correct lib vs lib64 to correct symlink00:14
CarbontatedCaffeineSorry, can you explain that to me a little simplier00:16
CarbontatedCaffeinelike how do I symlink these two, and how do I make the changes stick using the source code.00:17
mal"mkdir -p /odm/lib64" then "cd /odm/lib64" then "ln -s /system/apex/"00:18
malsimilar to the other symlinks but different filenames00:18
malyou can create the symlinks in correct folders in sparse as usual00:19
mallater when you have first tested those on device00:19
malof course when creating those in sparse don't use absolute path when doing that cd /odm/lib6400:19
malwhich should be obvious00:19
CarbontatedCaffeineOh, it's that easy?00:31
CarbontatedCaffeineWhat does sparse mean?00:32
malhybris/droid-configs/sparse folder in your sources00:39
malit's where all kinds of configuration and other stuff is added00:39
malit's part of the droid-configs repo00:39
CarbontatedCaffeineAh, cool00:40
malI'll go offline now00:41
CarbontatedCaffeineI'm looking through my journal, but I can't find lipstick, thanks for your help00:41
CarbontatedCaffeinehave a good one00:41
malyou might need libui_compat_layer which is an optional library built in habuild_sdk and packaged in droid-hal00:43
malsince log says it can't find gralloc and that is the way for devices without gralloc library00:44
malso you can test if that helps with lipstick issue, so "make libui_compat_layer" in habuild_sdk and then the usual -d00:45
malbut first test the symlinks for the other issues seen in log like ngfd00:45
CarbontatedCaffeinethe journal is extremely large00:46
CarbontatedCaffeinea lot of things seem to be working now00:46
CarbontatedCaffeineThe status LED is now stuck white00:46
CarbontatedCaffeinewhich I think is good00:46
malyou can check what is working and what is not by checking output of "systemctl" and "systemctl-user"00:46
CarbontatedCaffeineoh cool00:46
mallatter can also be systemctl --user depending on which environment you use, I think telnet needs systemctl-user00:47
CarbontatedCaffeineFailed to connect to bus: No such file or directory00:47
CarbontatedCaffeineboth give me this00:48
malok, maybe user session is not running00:48
malyou mean also for just systemctl?00:48
CarbontatedCaffeinesystemctl works fine00:48
CarbontatedCaffeineWould you like to see the journal00:48
malit tells in there is user session is running00:49
malwell I won't be looking at logs for quite many hours so maybe try checking what is failing and test the things I mentioned00:49
CarbontatedCaffeineAlright, thanks00:49
maland checking channel logs for errors can also help00:50
malyou can search channel logs here
CarbontatedCaffeineEven better00:53
CarbontatedCaffeineI've been using that actually00:53
CarbontatedCaffeinevery good, sometimes00:53
CarbontatedCaffeinelots of reading to do then00:54
CarbontatedCaffeineHey everyone, I have some great progress to report to you03:20
CarbontatedCaffeineI have /vendor mounted now03:20
CarbontatedCaffeineI also added the symlink to for odm/lib64 to sparse in droid config03:21
CarbontatedCaffeinewhich worked out of the box03:21
CarbontatedCaffeineIs there anyone currently online that may be able to help debug, thanks.04:06
T42<Mister_Magister> @b100dian how's your port coming along?06:28
T42<b100dian> Debugging the fingerprint sensor. I have in my todo also: wifi drivwr consumes more battery and video playback is interrupted with a hardware error. But it should boot, have all these if I make a new install image, plus video recording07:41
T42<b100dian> Also I have trouble booting twrp currently so manual installation may be needed if thats also your case too
T42<b100dian> Nfc, Mtp, Fm radio, actdead, and other device specifics like 90Hz display is not yet looked into.07:50
CarbontatedCaffeineHello, might anyone know what is wrong here, I feel stuck currently:
CarbontatedCaffeineI don't have a GUI yet11:41
malyou need to provide journal log11:42
CarbontatedCaffeineOf course11:42
CarbontatedCaffeinehere is journal11:55
malsomething went really wrong, droid-hal-init is not even starting12:10
malwhich android base is that? I forgot12:11
CarbontatedCaffeineMay I say that droid-hal-init hasn't ever started12:23
CarbontatedCaffeineI saw some people in logs say you didn't need it? But I was skeptical12:23
malthat one of the most critical processes12:24
malno way to get UI working without12:24
maldo you have that somewhere on device?12:26
CarbontatedCaffeineGive me a tick to check12:26
CarbontatedCaffeinein many places, as seen here12:28
CarbontatedCaffeinedo I need to make another symlink?12:28
malno symlink should be needed for that12:32
malyou probably need to strace droid-hal-init12:33
malis for example /system/lib64/ normal file?12:33
CarbontatedCaffeineEXECUTABLE "droid-hal-init": library "" not found12:34
malI said no symlinks for those, the issue is something else12:35
CarbontatedCaffeineIt was before you responded12:36
CarbontatedCaffeineI was merely curious12:36
malthat is why I asked you to strace droid-hal-init12:37
CarbontatedCaffeineI did12:37
malwhere is the output then12:37
CarbontatedCaffeineOkay, I removed my symlink12:37
CarbontatedCaffeineand rebooted12:38
CarbontatedCaffeineheres the output12:38
malis /system/lib64/ normal file?12:39
CarbontatedCaffeine"/system/lib64/" is a symlink12:39
CarbontatedCaffeineI can confirm12:39
CarbontatedCaffeineusing "ls" shows it as cyan,'12:40
malwhere does it point?12:40
maluse ls -l12:40
T42<k1gen> didn't enter this room for a while, and when I decide to check on it, I see mal doing God's work here again, helping some guy :D12:40
CarbontatedCaffeine"/ # readlink -f /system/lib64/  /system/lib64/"12:41
T42<k1gen> CarbontatedCaffeine: you know, I was in your place couple months ago :)12:41
CarbontatedCaffeineWhat the hell :skull:12:41
CarbontatedCaffeineIT'S A SYMLINK TO A SYMLINK12:41
CarbontatedCaffeine"CarbontatedCaffeine: you know, I was in your place couple months ago :)" If you mean having mental breakdowns every couple of hours12:41
CarbontatedCaffeineI have been working on this point, every day, for a WEEK12:42
T42<k1gen> no, I mean being constantly helped by mal and elros :)12:42
CarbontatedCaffeine1 week anniversary today.12:42
CarbontatedCaffeine"no, I mean being constantly helped by mal and elros :)" I'm quite an annoyance12:42
CarbontatedCaffeineI know12:43
T42<k1gen> I'm sure I was one too12:43
CarbontatedCaffeineAnyway, uhh so I gotta figure this out12:43
CarbontatedCaffeinewhich is the real libc.so12:43
malCarbontatedCaffeine: it took me months to get my first device to boot to UI but that was very long time ago and things are easier now usually12:43
T42<k1gen> yeah, there's also sound up ahead :)12:44
CarbontatedCaffeineMeh, gui will allow me to sleep easy12:44
CarbontatedCaffeinefor a while12:45
T42<k1gen> it won't, I had gui but no sound for a while12:45
CarbontatedCaffeineI can't find the real libc.so12:45
CarbontatedCaffeinethey're imposters12:45
CarbontatedCaffeine"/system/apex/" is real12:47
CarbontatedCaffeine"lrw-r--r--    1 root     root            46 Jan  1  2009 /system/lib64/ -> /apex/"12:48
CarbontatedCaffeineoh it is just a symlink to that one12:48
CarbontatedCaffeineI see12:48
malbut different path12:48
malrun "ln -s /system/apex /apex"12:49
CarbontatedCaffeineI shouldn't question12:49
malother path is /apex other is /system/apex12:49
malyou see the file is in /system/apex/ but symlink points to /apex/
CarbontatedCaffeineRebooted, it's still complaining about not found12:51
CarbontatedCaffeineOh, it's because /apex already exists12:52
CarbontatedCaffeineso it just places a new symlink in /apex/apex12:52
malah, what is what we want12:53
malso is /apex a folder or symlink?12:53
CarbontatedCaffeinea folder12:53
malI meant that we want /apex to point to /system/apex12:53
CarbontatedCaffeineand the command put a symlink called apex, into that folder12:53
CarbontatedCaffeineyes, I know you did12:54
malremove the /apex folder and create the symlink12:54
CarbontatedCaffeineokay, done12:54
malother option is to bind mount /system/apex to /apex, we'll see which way we should go12:54
malbut symlink for now12:54
CarbontatedCaffeineboth work as well as each other right?12:55
CarbontatedCaffeineHold up, something isn't right12:55
CarbontatedCaffeine"/ # ls /apex/   "12:55
CarbontatedCaffeineThat's not apex?12:56
malremove the symlink and create the folder again12:56
malthen run "ln -s /system/apex/ /apex/"12:57
CarbontatedCaffeinechecking again once rebooted12:57
CarbontatedCaffeinefixed, but new issue12:58
CarbontatedCaffeineI'm not how to explain this one12:59
CarbontatedCaffeinethe end part13:00
CarbontatedCaffeine"write(2, "cannot locate symbol \"_ZN3fmt2v6"..., 123cannot locate symbol "_ZN3fmt2v68internal10basic_dataIvE23zero_or_powers_of_10_32E" referenced by "/sbin/droid-hal-init"...) = 123"13:00
T42<b100dian> `fmt::v6::internal::basic_data<void>::zero_or_powers_of_10_32` says demangler.com15:37
T42<b100dian> Maybe you can grep for your string to find which .so has that symbol..?15:52
CarbontatedCaffeineI'll give that a try thanks21:19
CarbontatedCaffeineit references the error is coming from "/sbin/droid-hal-init"?21:24
CarbontatedCaffeineI'm not sure where to go from here21:41
CarbontatedCaffeineheres the strace for droid-hal-init currently21:43
maljust to be sure, you have correct android base version flashed on the device before you installed sailfish?21:44
CarbontatedCaffeineAndroid 11 (Lineage)21:47
CarbontatedCaffeineWould it be a good idea if I re-flash it?21:48
CarbontatedCaffeinejust in case21:49
CarbonatedCaffeineIt bootloops forever now, I have no idea how I got it cooperate the first time22:19
CarbonatedCaffeineone step forward, 15 steps backwards22:21
CarbonatedCaffeinedoing touch /data/.stowaways/sailfishos/init_enter_debug2 allowed it to boot22:31
CarbonatedCaffeinebut not into the rootfs obviously22:31
CarbonatedCaffeineif I delete it again22:32
CarbonatedCaffeinelets see22:32
T42<elros34> init_enter_debug2 boots to rootfs just stop booting system22:33
T42<elros34> there is even instruction shown when you telnet with thta file what to do to continue booting22:33
CarbonatedCaffeineDo you remember when I was having problems with that22:34
CarbonatedCaffeineI wasn't able to telnet when I did that22:34
T42<elros34> That way of preventing system start is very usefull for bootloops because you can run journalctl -f or dmesg -w, continue booting and see what fails22:35
CarbonatedCaffeineelros34: I can't get into the system22:35
CarbonatedCaffeinelike I said22:35
T42<elros34> no idea what does it mean "you can't get into system"22:36
CarbonatedCaffeineno telnet22:36
CarbonatedCaffeinethe problem I had last time when making that file22:36
T42<elros34> yeah but you were using wrong telnet port or didn't set inet address for usb iterface. Never showed any log of what you have done so just guessing22:37
CarbonatedCaffeineI told you22:37
CarbonatedCaffeineit wasn't working22:37
T42<elros34> you think this is first device with telnet issues. I had this and many before you had this too22:38
CarbonatedCaffeineAre you having MY issue?22:38
T42<elros34> I even had some mainline which loose conection very few seconds so run this ip route/set commands in loop22:39
CarbonatedCaffeineIt gets to the rootfs22:41
CarbonatedCaffeinebut crashes straight after that22:42
T42<elros34> the point is if you do not know how to fix something then show your logs, host dmesg from connecting device, ifconfig output, ip route.. commands and so on. "Doesn't work" is not usefull at all22:42
CarbonatedCaffeineHow am I supposed to show my logs if I can't get any22:43
T42<elros34> on your host/pc22:44
CarbonatedCaffeineI don't know how to do that, I don't route ips22:45
CarbonatedCaffeineor whatever22:45
T42<edp_17> Don't you have dmesg, journal or whatewer on your host that shows what's happening when you try to connect?22:46
T42<edp_17> Is that a linux system?22:47
T42<edp_17> Then you should have some those I wrote.22:47
T42<elros34> what are you talking about run: 'dmesg -w' connect device, run ifconfig  commands from hadk-hot->halium instruction ip route/address and again ifconfig22:49
T42<edp_17> I used this to bring up the usb network, then I was able to telnet to the device:
CarbonatedCaffeineI tried to do that omg22:51
CarbonatedCaffeinethat didn't work22:51
T42<elros34> and again "didn't work". Are you going to show anything I asked or not?22:52
T42<elros34> fair enough. Sorry if I was rough. We can not communicate so somebody else will probable help you better/faster22:54
T42<edp_17> I had a device where I wasn't able to bring up usb network, chosing a different android base has solved the problem for me.22:57
CarbonatedCaffeineMan, I'm not starting all over again22:57
CarbonatedCaffeineIf I have ta do that, then I'm kinda done23:05
malI don't understand why usb networking would suddenly stop working23:16
malalso there is almost never need to start all over again23:16
CarbonatedCaffeineHi, sorry I got frustrated. I took the time to read the init docs and I was able to enter the phone again via telnet.23:17
CarbonatedCaffeineWhat logs can I get23:29
maljournal log of course, if not possible then dmesg23:30
CarbonatedCaffeineDmesg is the best I have currently23:35
T42<Mister_Magister> @b100dian since flashing anything on recend devices is massive pain in the butt i think it will be good idea to change the sfos image to more official one like in fxtec in future23:46
T42<Mister_Magister> where you just fastboot all the partitions23:46
malhow far does the device boot?23:55
malif that from before systemd is up and if you continue to boot causes reboot first thing to do is to mask droid-hal-init23:56

Generated by 2.17.1 by Marius Gedminas - find it at!