Sunday, 2019-09-15

T42keafu was added by: keafu01:11
T42<keafu> hello01:11
T42<enriconia> I have found the answer: just skip qt5-qpa-surfaceflinger-plugin02:22
T42<DylanVanAssche> @elros34 I found the cause of the sensor read failure.07:15
T42<DylanVanAssche> It creates the sensor correctly with input_match but the reading fails: `Aug 27 06:17:34 Sailfish sensorfwd[2504]: read(): Device or resource busy`07:15
T42<DylanVanAssche> Looks that too many `open()` calls are being made to the sensor data...07:15
T42<elros34> Maybe sensor is misconfigured so data is not available. Have updated sensorfw after I rebuild it with gyro fix?07:27
Hacker1245Hey, my friend and I are running into a problem when porting the Motorola Moto G5. The telnet connection doesn't launch when the rootfs is installed, but works fine with only the initramfs installed.07:44
T42<elros34> @DylanVanAssche: I have very little iio experience, maybe entries in scan_elements should also be enabled only for relevant channels. I wonder why scan_elements is even used if iioadapter just read directly from sysfs not from /dev/iio:deviceX07:52
T42<elros34> @Hacker1245 does device reboot? If /init-debug in rootfs is executed you should have /data/.stowaways/sailfishos/init.log07:57
T42<DylanVanAssche> @elros34 Yes I did. Sometimes the accelerometer works, but most of the time I get no data and journalctl is spammed with that error message. Other sensors are not working, they are detected though as the right sensor type.08:04
T42<DylanVanAssche> I wanted to play a bit myself with the adaptor. What's you dev setup? Do you build the adaptor only or whole sensorfw? On device?08:04
T42<elros34> I build in platformsdk or obs just/whole sensorfw-qt5.spec08:23
Hacker1245@elros34 Device is not rebooting, log is here
T42<elros34> touch  /data/.stowaways/sailfishos/init_enter_debug2 and you should have telnet at 2323. Then you can grab logs and continue booting system08:40
T42<elros34> or maybe you just used wrong port?08:41
Hacker1245I don't think my friend used the wrong port as we made a new one08:43
Hacker1245Where will the logs be?08:43
T42<elros34> I mean when device is in initramfs telnet is at 23 port but when rootfs is reached it's in 232308:44
Hacker1245Oh this08:44
Hacker1245Alright so my friend got to rootfs08:50
Hacker1245What should he do next?08:50
T42<elros34> depends of what was the issue but usually dmesg, journalctl —no-page and /usr/libexec/droid-hybris/system/bin/logcat08:52
Hacker1245So he's in the Mer debug shell, how can he continue booting?08:56
T42<elros34> init_enter_debug2 was needed to get telnet or no? If yes then instruction how to continue booting shows when you telnet to devvice08:58
Hacker1245So after continuing device stays on the OEM splash and the interface is gone09:01
T42<elros34> you can enable persistent logging so you after rebooting you would have in journalctl log from previous boot:
Hacker1245he got this after trying to run logcat10:00
Hacker1245sh: /usr/libexec/droid-hybris/system/bin/logcat: /system/bin/linker: bad ELF interpreter: No such file or directory10:00
T42<elros34> so something is wrong, grab journalctl10:01
Hacker1245Want any specific parts?10:06
Hacker1245Or the whole log10:06
T42<elros34> always whole10:06
Hacker1245that should be everything10:09
T42<elros34> doesn't looks like full journalctl also droid-hal-init is masked so there is nothing useful there10:22
Hacker1245@elros34 How can I unmask droid-hal-init and grab the full journalctl?10:29
T42<elros34> just type journalctl —no-page and make sure you have big enough buffer(I set it to infinity) in your terminal application so very early kernel messages with kernel boot params are also included. To mask droid-hal-init you created symlink right? so now remove it10:32
Hacker1245@elros34 That should be the full log10:59
Hacker1245cat: /init: No such file or directory10:59
T42<elros34> How did you disable selinux? There is no selinux=0 in kernel boot params11:07
Hacker1245Disabled audit11:09
Hacker1245And I think I did set the default boot parameter to 011:09
Hacker1245I might rebuild the kernel though11:10
T42<elros34> wrong, audit must be enabled. Check HADK 9.3.111:10
riniguskimmoli: ping regarding testing. Any progress?11:17
kimmoliwell it has been powered on...11:39
T42<elros34> Did you notice any change? I don't. BTW you can use -b for curren't boot log and -b -1 for previous boot log if your device lose connection12:00
riniguskimmoli: that's a progress, I guess :)12:05
T42<adampigg> Mal, lots pt PRs for advanced cam just came in12:59
kimmolirinigus: anyways, uploading to devaamo13:16
T42<Hpian> good13:18
riniguskimmoli: thanks! don't think its the most stable release, but let's hope its fine as it is for now13:35
T42<Hpian> good13:36
rinigus(as I had problems in the beginning. although, not on day2day)13:36
mal@adampigg I noticed13:40
T42<Hpian> good13:40
T42<Hpian> hello babys14:05
T42<Hpian> Who can tell me ,how to install sailfishos on my phone?14:06
Hacker1245what phone14:08
T42<Hpian> le 1Pro14:08
T42<Hpian> msm899414:08
T42<Hpian> 4GB+128GB14:09
T42<Hpian> moto z2 force14:10
Hacker1245follow the HADK14:18
T42Arika %lastname% was added by: Arika %lastname%16:13
T42<enriconia> mdss_mdp_overlay_pipe_setup: exceeded max mixer supported resolution 1280x-71919:46
T42<enriconia> what does it mean? (elephone trunk, msm8916, arm64, cm14.1, sfos
malwhat issue are you trying to fix?20:01

Generated by 2.17.1 by Marius Gedminas - find it at!