deathmist | about to test memless haptics on OP5, wish me luck (fingers crossed) | 00:10 |
---|---|---|
deathmist | hmm seems the vibrator driver didn't make it into kernel due to OF_SPMI not enabling => QPNP_VIBRATOR_MEMLESS is never built. | 00:29 |
deathmist | changing it to just SPMI worked in Kconfig, now then I don't have linux/qpnp/vibrator.h in my kernel tree includes that is used by the driver and simply changing it to qpnp-haptic.h did not work at all :/ | 00:37 |
deathmist | reading about QPNP_HAPTIC: "It uses the android timed-output framework." wonder if I could somehow hack QPNP_VIBRATOR into my kernel for memless haptics to become a possibility | 00:40 |
deathmist | main reason I'm even trying is that it seems Qt5 haptics native plugin seems to not work on specific boots now for me on 16.0 (e.g. pulley menus / mce config vibrate command doesn't work) while keyboard taps for example still function normally | 00:41 |
T42 | <elros34> afaik pulley menu use ngf plugin not qt | 08:59 |
deathmist | huh, could be the other way around then. the Qt5 component app haptics all also worked when others didn't so that would make sense actually | 09:06 |
deathmist | found this in journal: "ngfd: libprofile: session bus connection requested while blocked" that would explain it, any clue? journal https://dpaste.de/5T4e/raw logcat https://dpaste.de/rTWX/raw | 10:27 |
deathmist | btw this is with all memless crap reverted, just using ngfd-plugin-native-vibrator & qt5-feedback-haptics-native-vibrator installed | 10:30 |
deathmist | writing msec values to /sys/class/timed_output/vibrator/enable makes the device vibrate. maybe jusa could take a look | 10:33 |
T42 | <elros34> start ngfd in more verbose mode, iirc -vvvvv | 10:35 |
deathmist | wow so starting it manually now makes it work wth :( guess I'll edit the service file to get verbose logs | 10:39 |
deathmist | new journal https://dpaste.de/FVzm/raw (ngf init logs) and followed journal during pulley menu pulls & app close from home screen https://dpaste.de/uXbO/raw | 10:52 |
deathmist | hold on new journal link was some logcat I didn't even look, just a sec | 10:56 |
deathmist | https://dpaste.de/qTNG/raw <-- ngf init logs journal | 10:58 |
T42 | <elros34> maybe this is related to your kernel driver: tfa98xx and q6core_get_service_version: Failed to get service size | 10:58 |
deathmist | starting it manually after boot works tho :/ | 11:00 |
T42 | <elros34> firmware for tfa98xx is loaded after ngfd is started so that could be related | 11:06 |
deathmist | yep, I added a "ExecStartPre=/bin/sleep 1" to the service unit and after 4 consecutive reboots it has always worked... what else could I do? | 11:06 |
T42 | <elros34> maybe create udev rule for tfa98xx so ngfd will wait for it but I am not sure it's sane approach. I use such a rule for sensorfw | 11:10 |
T42 | <austroloid> hello, have a problem with media music playing along during notification sounds in loudspeaker i guess its due to output-speaker+wired_headphone where should it be changed | 12:30 |
rinigus | pketo: please register on the store side device "Xperia XZ3 (h9436 / h9436)". for some reason, it was able to access store already. imei (x2) detected correctly, as wifi and bt. | 17:13 |
rinigus | pketo: I would expect that XZ2 dual sim and XZ3 single sim would work as well. but those have not been tested in the wild yet | 17:14 |
rinigus | pketo: corresponding devices are "Xperia XZ2 (h8266 / h8266)" and "Xperia XZ3 (h8416 / h8416)" | 17:17 |
rinigus | I expect that xz2c will come as well, as one user has already ordered it. but that will have to get working as well before (maybe touchscreen requires some extra tuning) | 17:18 |
KALUBE | Can anyone offer any theories on treble porting? I seem to be stuck dealing with Android Verified Boot | 17:59 |
KALUBE | I've flashed a stock vbmeta image with --disable-verity --disable-verification which should let any old boot image work without verification, the phone hangs on the splash screen for 5 seconds or so before rebooting | 18:04 |
KALUBE | This is my defconfig, mer_verify_kernel_config is happy with it. https://git.io/JeyFM | 18:06 |
T42 | <elros34> does it use system as root? | 18:21 |
KALUBE | @elros34 yes | 18:32 |
KALUBE | I've just been reading into this https://source.android.com/devices/bootloader/boot-image-header#implementation | 18:32 |
KALUBE | I'm guessing hybris-boot is building a "legacy" boot image that doesn't work with system as root | 18:33 |
T42 | <elros34> did you reverted commit in kernel which adds skip_initramfs? | 18:33 |
KALUBE | no? | 18:33 |
T42 | <elros34> so revert f26d3c76d3764c2d3b542eb8f0aa9ee7dc47233c and c3c2e99fcc3ed20ab49b482bdc102ebb8037ebd6 otherwise hybris-boot script will be not used at all | 18:35 |
KALUBE | in my kernel? | 18:36 |
T42 | <elros34> yes: https://github.com/sailfish-oneplus6/android_kernel_oneplus_sdm845/commits/hybris-16.0/init/initramfs.c | 18:36 |
KALUBE | @elros34 that fixed it! Thank you so much :) | 18:54 |
KALUBE | now we get to fix telnet | 18:55 |
T42 | <elros34> so how log now it takes before it reboots? do you have anything in host dmesg | 18:57 |
KALUBE | @elros34 stole some defconfig options from Deathmist, have telnet working now getting system/vendor mounted and we're off! | 19:01 |
T42 | <elros34> great, for system you need %define makefstab_skip_entries / in droid-hal-$DEVICE.spec before last %include | 19:03 |
KALUBE | Cheers | 19:08 |
KALUBE | @elros34 how can I make droid-hal generate systemd mount units for /system and /system_root? Those folders don't exist on my device by default | 19:19 |
T42 | <elros34> it should be done automatically, check droid-hal-$DEVICE*rpm if not show you droid-hal-$DEVICE.log | 19:22 |
mal | show the fstab file which is somewhere in your android device repo | 19:26 |
KALUBE | @elros34: here's my droid-hal-device log https://pastebin.com/y0wqiA4Y | 19:27 |
KALUBE | mal: this is fstab https://git.io/JeyAT I have added an entry for boot so that fixup-mountpoints would work | 19:28 |
T42 | <elros34> use make modules | grep fstab and then build it if fstab is found | 19:30 |
KALUBE | that command has no output | 19:33 |
T42 | <elros34> ok so you copy your fstab* to /out/target/product/$DEVICE/root and build droid-hal again | 19:34 |
T42 | <elros34> you need also custom vendor.mount so add /vendor to makefstab_skip_entries and add this to sparse https://github.com/sailfishos-oneplus5/droid-config-cheeseburger/blob/master/sparse/lib/systemd/system/vendor.mount | 19:37 |
T42 | <elros34> use correct partition for your device and add symlink to it in local-fs.target.wants/ | 19:38 |
KALUBE | Got it | 19:42 |
KALUBE | @elros34 wouldn't duplicating vendor_a as vendor in fixup-mountpoints make it generate the right mount unit? | 19:46 |
KALUBE | Does seem to be a bit less clean though | 19:47 |
T42 | <elros34> what do you mean? you should have partitions without _a/_b in fixup. You need custom vendor.mount because it needs to be mounted before /vendor/firmware_mnt /vendor/dsp and so on | 19:52 |
T42 | <elros34> makefstab helper script just doesn't create correct mount unit | 19:53 |
KALUBE | ah ok thanks | 19:55 |
mal | KALUBE: you need also "%define makefstab_skip_entries /" to droid-hal spec | 20:01 |
mal | maybe, need to verify that | 20:01 |
KALUBE | Yeah I have that too, thanks | 20:01 |
mal | KALUBE: hmm, have you tried removing it? | 20:02 |
mal | KALUBE: I mean if you don't get the proper system_root mount then maybe you need it | 20:03 |
mal | https://github.com/mer-hybris/droid-hal-device/blob/master/helpers/makefstab#L145 | 20:03 |
KALUBE | I have it added and system.mount and system_root.mount both look good | 20:04 |
mal | KALUBE: you really shouldn't need to add those at all, both are added automatically if you have correct things in droid-hal spec, in this case makefstab_skip_entries / probably prevents the automation from working | 20:07 |
mal | like shown in the link I just gave | 20:08 |
mal | now that I think of it "%define makefstab_skip_entries /" should only be used in official device which have rpm packaged android system libs | 20:08 |
KALUBE | I haven't defined them manually they are being built automatically and end up in droid-hal-device.rpm | 20:08 |
mal | KALUBE: so what is then the problem | 20:09 |
piggz | mal: porting a large qqc2 app to sailfish is quite an undertaking! | 20:10 |
mal | piggz: heh | 20:10 |
KALUBE | No problem, I removed / from %define makefstab_skip_entries and it still generated the mount units so all is well | 20:11 |
mal | ok | 20:11 |
KALUBE | build_packages.sh -i fails with: repo problem: nothing provides droid-hal-enchilada-detritus needed by pattern:jolla-hw-adaptation-enchilada-1-1.noarch | 20:12 |
vknecht | mal, what about suzu with pie and droid-system, should it skip_entries for / or /system (like official port), or neither ? currently fighting with that... with aosp8 base I did use neither, but didn't have droid-system (it used aosp /system) | 20:12 |
mal | vknecht: I assume that doesn't use / for system mount in fstab? or does it? | 20:13 |
vknecht | it uses /system, afaics https://github.com/sonyxperiadev/device-sony-loire/blob/p-mr1/rootdir/vendor/etc/fstab.loire | 20:14 |
mal | so if you use rpm packaged system partition then you of course skip the mount | 20:15 |
vknecht | ok thanks | 20:18 |
KALUBE | lipstick is failing with EGL Error : Could not create the egl surface: error = 0x3001 | 22:11 |
KALUBE | journalctl: https://paste.opensuse.org/38106199 | 22:11 |
KALUBE | Any ideas | 22:13 |
KALUBE | ?* I have also tried test_hwcomposer, I will upload the log for it too | 22:14 |
KALUBE | This is the result of strace test_hwcomposer: https://paste.opensuse.org/9595919 | 22:16 |
mal | which android base? | 22:16 |
mal | maybe you need to try test_hwc2 if the device is very new? | 22:16 |
mal | did you use it correctly "EGL_PLATFORM=hwcomposer test_hwcomposer" or same with test_hwc2 | 22:17 |
KALUBE | yes I did, will try test_hwc2 thanks | 22:21 |
KALUBE | test_hwc2: test_hwc2.cpp:288: int main(): Assertion `eglGetError() == EGL_SUCCESS' failed. | 22:21 |
KALUBE | I forgot to add WANT_ADRENO_QUIRKS could that be the issue? | 22:21 |
mal | not at this level yet | 22:22 |
KALUBE | hmmm ok | 22:22 |
mal | so maybe something is wrong with the android side, did you do things according to the android base specific instructions in faq? | 22:22 |
mal | what ever android base you use | 22:22 |
KALUBE | I'm using LOS16 base, this is my manifest https://github.com/sailfish-oneplus6/local_manifests/blob/master/enchilada.xml | 22:25 |
KALUBE | system and vendor are both mounted properly | 22:25 |
KALUBE | Sorry I just pushed, that local_manifests repo was out of date | 22:27 |
mal | did you do what faq told to do when porting 16 base? | 22:41 |
KALUBE | yeah, I have these: https://github.com/sailfishos-oneplus5/droid-config-cheeseburger/tree/hybris-16.0/sparse/usr/libexec/droid-hybris/system/etc/init | 22:42 |
mal | wasn't there already a cheeseburger port? | 22:42 |
deathmist | mal: he's doing OnePlus 6 (enchilada) | 22:43 |
mal | ok | 22:43 |
KALUBE | the hadk says to copy the files I linked | 22:43 |
mal | deathmist: maybe you can help him? | 22:44 |
deathmist | mal: we've been trying ever since he got telnet working ;) we got ld.config mount unit, DHI starting and stuff in fstab mounted including proper /system_root and /system | 22:51 |
KALUBE | minimer outputs Cannot find EGLConfig, returning null config | 23:22 |
KALUBE | and then the same EGL Error : Could not create the egl surface: error = 0x3001 | 23:22 |
T42 | <elros34> did you mask user@100000.service and reboot before trying minimer or test_hwc2? you should also check /usr/libexec/droid-hybris/system/bin/logcat to see whta fails | 23:30 |
KALUBE | @elros34 logcat is full of this: https://pastebin.com/etMkx2RH | 23:36 |
KALUBE | I will try masking user and test hwcomposer | 23:37 |
mal | deathmist: KALUBE what do logs say? | 23:37 |
T42 | <elros34> @KALUBE: reboot and and try again so logcat will contains also early boot messages | 23:42 |
mal | also dmesg | 23:42 |
KALUBE | dmesg: https://paste.opensuse.org/37748893 logcat: https://paste.opensuse.org/99407695 | 23:52 |
KALUBE | the permissions of /dev/ion were wrong, and my ueventd.rc file is nowhere to be found in my source tree (except in out/target/product which is very odd) I modified the udev rules based on IRC logs which removed that error from logcat | 23:53 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!