Thursday, 2023-07-27

CarbonatedCaffeineelros34: I have generated a much larger log from "usr/libexec/droid-hybris/system/bin/logcat" -
CarbonatedCaffeineCurrently the display doesn't want to work, and Mal has suggested it could be something to do with "vndservicemanager".01:01
CarbonatedCaffeineI had tried running "binder-list" which Mal also suggested me to run. But running this provides no results (As in after I press enter I get a blank line and that's it).01:03
CarbonatedCaffeineHere is a more verbose output of `binder list` -
*** phlixi is now known as Guest708901:58
*** phlixi_ is now known as phlixi01:58
*** phlixi is now known as Guest709402:55
*** phlixi_ is now known as phlixi02:55
T42<elros34> I think you were suppose to run it with /dev/*binder* arguments. Do you have only /dev/hwbinder? Do you run it after whole system is up?07:42
T42<elros34> about logs, problem is not that you generate to short logs but to get them as soon as possible to not loose anything. Another point is to show command you are using so it's clear whether you are starting logcat as root or as user. But I repet instruction which you were supposed to read07:49
T42<elros34> btw you can safely disable vendor.time_daemon in /usr/libexec/droid-hybris/system/etc/init/disabled_services.rc so it will not generate spam in logcat07:54
CarbonatedCaffeineelros34: Hey, thanks for the reply.12:00
CarbonatedCaffeine"I think you were suppose to run it with /dev/*binder* arguments" It took me a while to figure this out. I tried `binder-list /dev/hwbinder` without any results again.12:02
CarbonatedCaffeine"Do you have only /dev/hwbinder?" I will have to check later on12:03
malbinder-list -d /dev/binder12:03
CarbonatedCaffeine"Do you run it after whole system is up?" Yes I do12:03
CarbonatedCaffeineOkay :thumbs_up:12:03
CarbonatedCaffeine"to get them as soon as possible to not loose anything" How could I go about generating these logs as quickly as possible? Thanks12:05
CarbonatedCaffeineMal: No results again.12:06
CarbonatedCaffeine"/ # binder-list -d /dev/binder"12:10
CarbonatedCaffeine"/  #"12:10
malnow try the other /dev/*binder*  devices12:12
CarbonatedCaffeine"ls /dev | grep binder" gives me binder, binderfs, hwbinder and vndbinder12:17
CarbonatedCaffeinenone of them have results12:17
CarbonatedCaffeinebinderfs is empty12:17
malis droid-hal-init running?12:20
CarbonatedCaffeinegive me a second, I'm transfering a log to my computer12:21
CarbonatedCaffeine"loaded active running   droid-hal-init"12:23
CarbonatedCaffeineDoes this mean something is off?12:23
CarbonatedCaffeinepastebin didn't like the large file12:34
T42<adampigg> I edit the files and bind mount over them (re @TheVancedGamer: works there)13:39
T42<DaveLFT> Is there any port for Asus zenfone Max pro M2 X01BD14:28
T42<TheVancedGamer> @adampigg I tried fixing the need to edit the files, fyi.14:36
T42<adampigg> That will be nice to have (re @TheVancedGamer: @adampigg I tried fi...)14:41
mal@TheVancedGamer did the more simple pulse separator code work?15:05
tigranHi guys, is WSL suitable for porting?15:10
T42<k1gen> tigran: why do you want linux on a phone if you don't even have linux on desktop?15:14
tigranI actually dual boot, but at the moment I have stuff running on Windows that I don't want to lose15:16
tigranbut why does that even matter? I'm just asking a simple yes/no question..15:17
T42<k1gen> I know that wsl didn't work a year ago. I don't think anything changed15:18
tigranI see, thanks15:19
maldifficult to say if it can be made to work, wouldn't linux virtual machine be easier, assuming that works15:19
T42<elros34> @CarbonatedCaffeine: it's very simple, you reboot device, telnet as soon as possible and run quickly logcat (as root).If that is not enough to catch early logs because of spam failure then you can stop booting in init-script, telnet and run logcat when droid-hal-init starts15:22
T42<elros34> Also I asked about your changes so it would be easy and fast to check them all but you refuse so: did you copy selinux files (not symlinks) to /etc/selinux? What other selinux changes did you make?15:25
T42<elros34> or show the repo if you have it uploaded15:31
*** tigran_ is now known as tigran16:50
T42<TheVancedGamer> mal: sorry, was busy, will try to get hold of someone with an X2316:55
T42<TheVancedGamer> mal: something went wrong, it's segfaulting :P17:11
T42<TheVancedGamer> mal: nvm, works17:19
T42<TheVancedGamer> need to test with spaces now, will edit my own policy :P17:19
T42<TheVancedGamer> mal: done,
tigran_Guys so I ran the sfossdk command and it outputted some pretty strange lines and I just want to be 100% sure that everything is fine:18:07
tigran_    Failed to create bus connection: No such file or directory18:07
tigran_    DBus unavailable, falling back to libssu18:07
tigran_it's pretty weird since dbus is present in my system18:07
tigran_but anyway, will it work just as fine?18:07
T42<elros34> I think this is fine18:08
tigran_what about this?18:08
tigran_    mount: /srv/sailfishos/sdks/sfossdk/proc/sys/fs/binfmt_misc: mount(2) system call failed: Too many levels of symbolic links.18:08
T42<elros34> ignore18:08
tigran_       dmesg(1) may have more information after failed mount system call.18:08
T42<elros34> not sure but you will see if you have any issues:) Is that on wsl?18:09
tigran_no, I did save my work and reboot and I'm on opensuse right now18:10
tigran_dmesg doesn't have anything useful either, guess I'll just cross my fingers and proceed18:12
T42<elros34> sure don't bother:P18:12
tigran_Well I was following the tutorial and it told me to restart sfossdk after editing ~/.bashrc and this time it started with no errors18:24
tigran_Do I copy repo from ~/bin to /bin? Or do I add ~/bin to my PATH?18:44
tigran_Is it used by scripts? If not, I can just type `~/bin/repo` instead of `repo`18:45
T42<elros34> you use repo only to download sources18:50
tigran_Alright, thanks18:51
*** tigran_ is now known as tigran19:50
tigranGuys, hi again, I've got yet another question.. in the ~/hadk/.repo/local_manifests/$DEVICE.xml file, if the version is 17.1, do I type "LineageOS/android_kernel_VENDOR_DEVICE" in the name field or "CyanogenMod/android_kernel_VENDOR_DEVICE"? Thanks in advance20:48
tigranTried it with "LineageOS/..." and it seems to work20:51
malwhich device do you have+21:08
maltigran: ^21:09
tigranI'm porting it to my older phone, Mi Note 3 (xiaomi/jason)21:19
tigranIf things go well I might as well also port it to my current one which is a Xiaomi Redmi Note 11 Pro 5G (I think it was called xiaomi/peux)21:22
tigranor veux21:23
tigranAlmost 40 minutes and it's at 8% and it's 1:29 AM over here, looks like I have to let it download overnight. I'm going afk. Bye guys!21:29
T42<elros34> tigran: you must find what sources were used to build lineage for that device and use them. It can be android_kernel_vendor_device but doesn't have to be. Follow lineage.dependencies files:
T42<elros34> it doesn't even have to be, use one which works best for your device22:01

Generated by 2.17.1 by Marius Gedminas - find it at!