Sunday, 2020-03-29

walidhfor camera got this error droid-hal-init: Service 'qcamerasvr' (pid 6038) killed by signal 612:04
walidhqcamerasvr can't start12:05
malif you expect help you need to provide full output of "journalctl -alb --no-pager" and /usr/libexec/droid-hybris/system/bin/logcat12:06
maland you should get those quite soon after a reboot so all messages can be seen12:09
malhmm, why is that not showing anythin from android side init in journal log12:27
walidhmal: dmesg not work properly (i used stock kernel cus its more fast)12:31
walidhthis cat /dev/kmsg
T42<elros34> walidh: kmesg is missing initial messages so how did you disable selinux? systemd-tmpfiles-setup  fails so I guess you are missing  some cgroups related CONFIG in kernel. Have you tried to chmod a+rw /dev/video*: "cannot open control fd of '/dev/video2' (Success)"13:59
walidhelros34: for selinux i added selinux=0 audit=0, also BOOTPARAM=y14:03
T42<elros34> does zcat /proc/config.gz also show bootparam enabled and /proc/cmdline have selinux=0?14:04
T42<Ori %lastname%> I need help18:12
T42<Ori %lastname%> I installed a port of sailfish os but the sensors are not working18:12
T42<Ori %lastname%> Any way to fix this? Oneplus 218:12
T42<elros34> How do you test them? There is test_sensors for low level sensors detection and csd or messwerk18:26
T42<Ori %lastname%> I tried to rotate18:54
T42<Ori %lastname%> And. I called my father18:54
T42<Ori %lastname%> No proximity18:54
T42<elros34> Ori so have you tried any of the mentioned apps? Do you have hw-settings.ini file: ?19:09
piggzmal: on the pro1, the FW prevents SSH over USB ... what config have we missed? other ports have had this?21:05
malpiggz: show output kernel checker21:07
T42<RealDanct12> @Deathmist1337, have you managed to fix ofono's error 4100 yet?21:11
T42<RealDanct12> the one that causes mobile data not to work21:11
malpiggz: how new is the kernel checker you use?21:11
piggzmal: may last year :D21:12
malpiggz: maybe update it and check again21:12
malpiggz: some netfilter options were added recently21:13
mallate last year21:13
malok, so at least no errors21:13
malwhat do you see in logs? have you tried to verify if it's a firewall issue (disable firewall in sfos to test)21:14
piggzmal: yes, i run this command to get ssh access21:15
piggziptables -A INPUT -j ACCEPT -m comment --comment "Accept all incoming"21:15
malcheck the rules for usb related things for example21:16
malto see if there is something odd in there21:16
piggzmal: does usb-moded need some config maybe...21:22
piggzto use usb021:22
piggz /etc/usb-moded/dyn-modes/developer_mode-android.ini refers to rndis021:23
walidhProblem: nothing provides bluez5-tools-hciattach needed by bluetooth-rfkill-event-hciattach-21:28
walidhwhen try to build bluetooth-rfkill-event21:29
malpiggz: where is the config repo for your device?21:29
malwalidh: which bluetooth chip does your device have, broadcom or qcom21:30
walidhbroadcom BCM4358A321:31
malbuild a bit older version of that bluetooth-rfkill-event, revision 818df19222b1997741e0268322941bb6765403f321:32
T42<adampigg> Mal
walidhmal: i reset --hard to version 818df19222b1997741e0268322941bb6765403f3 , and when rebuild it, work only when add flag --offline21:44
malor when using -b path/to/package21:46
malwhere the path is the place when you have the sources on your computer21:47
walidhin ubuntu touch we add 70-$DEVICE.rules, there is any thing similaire in sailfish21:49
malwhat does it contain?21:56
malwe have the droid udev rules which are automatically generated21:56
malwalidh: what exactly is the situation with your device?21:56
walidhwhat work : sound, wifi, vibrator, touch screen, browser, rild (make call, send sms)21:58
walidhwhat missing : camera bluetooth21:58
walidhmal: also can't fix startup wizard on first boot22:00
walidhis this help ?
malthat can help on some things but not for camera or bluetooth22:05
malwhat is the issue with startup wizard?22:05
walidhmal: size is very big, can't finish startup22:06
walidhsee this
malyou need to get logs from startup wizard, does it show the same if you start it now?22:07
T42<edp_17> Hi @elros34 : I just have checked and there is no 'POWER_SUPPLY_TYPE' when I do a 'udevadm monitor p'23:06
walidhmal: got camera work, its sensor problem missing file , i added it under /data/.stowaways/sailfishos/ (in recovery mode)23:09
T42<edp_17> @elros34 : What I spotted if the battery charge goes above 95%, the leds are blinking. (It seems correct according to the code '')23:10
walidhhow can i add it23:10
T42<edp_17> @elros34 : I have also double checked and there is no random usb events. If the device is off charger, the 'mce -Tq -l plugin*:* -l sysfs*:* -l hybris*:* -l modules/led.c:*' shows the device is discharging.23:12
T42<edp_17> However the leds are still blinking as the battery is above 96%.23:12
T42<elros34> @edp_17 what about usb status? Is detected correctly in mce? I also had no meaningful POWER_SUPPLY_TYPE so have to add it to kernel otherwise I had some usb detection issues but no like yours23:14
T42<edp_17> And the mce is constantly changing the value (0 -> 1, then back to 0) in /sys/class/misc/notification/led23:15
malwalidh: oh, you should check the other straggler files things, you are probably missing some init things23:17
malwalidh: show output of ls $ANDROID_ROOT/out/target/product/$DEVICE/root/ from your build environment23:19
T42<edp_17> The usb_status is DISCONNECTED when I unplug the cable and CONFIGURED when I plug it back in. POWER_SUPPLY_TYPE is not in the kernel at all.23:19
malwalidh: actually "ls -l $ANDROID_ROOT/out/target/product/$DEVICE/root/" is better23:19
T42<elros34> @edp_17 I don't know, maybe we are searching in wrong place23:21
T42<edp_17> @elros34 : Yeah, maybe.23:22
T42<edp_17> @elros34 : when the device is in developer mode and I do a 'systemctl status mce' there is a 'modules/battery-udev.c: udevdevice_lookup_charger_type(): unknown charger type: max8922-charger' message in there. Is this something I should fix?23:23
T42<edp_17> In the kernel I have the CONFIG_CHARGER_MAX8922_U1=y23:24
T42<elros34> @edp_17 I guess that is because POWER_SUPPLY_TYPE doesnt return POWER_SUPPLY_TYPE_USB_DCP/USB. You can check it in /sys/class/power_supply/*/uevent23:29
T42<edp_17> @elros34 : I have two chargers in there :
T42<edp_17> But none of them has POWER_SUPPLY_TYPE_USB_DCP/USB23:36
malwalidh: add these lines to your droid-hal-$DEVICE.spec file (before the last line, do not change the last line of the file)
malwalidh: then run " -d"23:37
T42<elros34> @edp_17 I would expect it in usb/uevent but like I said maybe it's not that important.23:46
T42<elros34> Have you checked in driver whether  0 > led is ignored sometimes or just something else write 1 later?23:48
T42<edp_17> I am not sure how to check but if I write anything else than 0 or 1, that is ignored.23:54
T42<edp_17> Plus if I write 0 into notification_enabled, the leds go off.23:54

Generated by 2.17.1 by Marius Gedminas - find it at!