| mal | did you add the correct things to sparse, the rc files | 00:06 |
|---|---|---|
| jellypony | mal: No. There was no error, so i decided not to add it. Is it bad? | 00:10 |
| jellypony | mal: oh,sorry. Misunderstood. I though youre talking about straggler files | 00:13 |
| jellypony | I added mount modules for system and vendor to sparse | 00:14 |
| jellypony | That all | 00:14 |
| mal | jellypony: do you have these https://github.com/sailfishos-oneplus5/droid-config-cheeseburger/tree/hybris-16.0/sparse/usr/libexec/droid-hybris/system/etc/init | 00:19 |
| mal | you will need those | 00:19 |
| jellypony | mal: D: | 00:22 |
| jellypony | no | 00:22 |
| jellypony | mal: I tell you more. My sparse only contains "/var" | 00:23 |
| jellypony | with lib/environment/compositor/droid-hal-device.conf | 00:24 |
| jellypony | nothing else | 00:24 |
| jellypony | ._. | 00:24 |
| jellypony | mal: What am I missing? | 00:25 |
| mal | jellypony: get the files from my link and add to your sparse to correct place as seen in the link | 00:50 |
| mal | you might also need the ld.config.28.txt modification as mentioned in channel logs, but more tomorrow, it's very late now | 00:51 |
| jellypony | ok | 00:54 |
| jellypony | good night :3 | 00:54 |
| jellypony | mal: actually what is your timezone? :0 | 00:58 |
| r0kk3rz | gmt+3 i think | 02:28 |
| r0kk3rz | i should really be more active and take over the night shift | 02:29 |
| xreactx[m]__ | https://pastebin.com/xBueVXeZ | 03:54 |
| xreactx[m]__ | this seems to be the latest error... when I'm trying to flash it to my device, the SFOS installer fails. | 03:55 |
| T42 | <BusterBg_18> Just flash your boot.img and extract the rootfs as instructed on hadk | 03:59 |
| T42 | <Akatsu %lastname%> @mal https://paste.ubuntu.com/p/YYKs4QtCjr/ seems to be ok | 07:31 |
| *** OhYash1 is now known as ohyash | 07:55 | |
| deathmist | mal: could it be that https://git.io/JeByq doesn't work because /system isn't mounted at this early stage? I'm going to do some more testing because mount binding the ld.config.28.txt is a much cleaner solution imo | 09:02 |
| mal | deathmist: /system is mounted earlier than droid-hal-init service | 11:26 |
| mal | at least it should be | 11:26 |
| T42 | <DylanVanAssche> mal: Installed the V4L fork of Qt Multimedia, still nothing in the Camera app. | 13:01 |
| T42 | <DylanVanAssche> I only have some weird white/blue image in the Camera app. We have /dev/video0 (video render) and /dev/video1 (back camera). I think that the app picks the wrong input? | 13:01 |
| mal | could be | 13:09 |
| mal | @DylanVanAssche it works manually using gst-launch? | 13:11 |
| mal | @DylanVanAssche what do you see when you use GST_DEBUG to get more logs, do those show what it tries to use? | 13:14 |
| T42 | <Akatsu %lastname%> i have question but not regarding sailfish, how can i get device to create bootdevice/by-name/* nodes? now i have no bootdevice under /dev/block | 13:16 |
| mal | those are usually created automatically using udev rules | 13:20 |
| mal | at which state of the boot is your device? | 13:20 |
| mal | which telnet port | 13:20 |
| vknecht | Mal: I hope the new video-snapshot pr is to your liking :-) | 14:24 |
| T42 | <DylanVanAssche> mal: hmmm it worked before, now it doesn't since gst-plugins-good doesn't build on OBS. I did that manually in the past but after reflashing that part is gone :( | 14:53 |
| T42 | <DylanVanAssche> *manually | 14:53 |
| T42 | <DylanVanAssche> mal: Will look at the V4L stuff later. I almost have the proximity sensor working under IIO. Well it works for MCE (display double tap works only when not covered). However, Messwerk doesn't work: 0.000 Lux and always no proximity detected. | 15:04 |
| T42 | <DylanVanAssche> spiiroin: Do you see any issues with this IIO proximity adaptor code? https://github.com/sailfish-on-dontbeevil/sensorfw/commit/94a5ba7fed2d50d3ccd63a5048688aa60051983f | 17:13 |
| T42 | <DylanVanAssche> - The light sensor value reports an invalid value of 4294967295 (after adding this commit). | 17:13 |
| T42 | <DylanVanAssche> - The proximity value is calculated correctly though. However, Messwerk shows -1 for the light sensor (error code I suppose) and proximity doesn't react. | 17:13 |
| T42 | <DylanVanAssche> - journalctl: http://ix.io/1ZjX | 17:13 |
| T42 | <DylanVanAssche> I don't see any difference with the other proximity sensor implementations in sensorfw... | 17:13 |
| mal | I would assume -1 is the same as 4294967295 i.e. unsigned vs signed? | 17:19 |
| mal | the opposite obviously | 17:20 |
| mal | @DylanVanAssche ^ | 17:20 |
| mal | @DylanVanAssche can you also print the values of variables result, iioDevice.offset, iioDevice.scale and *.value_ for both als and prox | 17:25 |
| T42 | <DylanVanAssche> mal: I would assume the same about that number... | 17:27 |
| T42 | <DylanVanAssche> I will rebuild sensorfw to print those values too. | 17:27 |
| *** jellypony1 is now known as jellypony | 17:56 | |
| T42 | <DylanVanAssche> mal: The light sensor is fixed if a manual scale override is applied of 1.0 (the proximity scale override the light scaling -> same sensor? ) | 18:05 |
| T42 | <DylanVanAssche> mal: With scale override fix: http://ix.io/1Zke | 18:15 |
| T42 | <DylanVanAssche> Without scale fix: http://ix.io/1Zkh | 18:15 |
| T42 | <DylanVanAssche> However, the scale fix doesn't fix the proximity detection though | 18:15 |
| mal | @DylanVanAssche look at the offset with scale override | 18:30 |
| mal | the scale looks ok in both cases, 1 | 18:31 |
| T42 | <DylanVanAssche> Yeah that wasn't the case before I tried the scale override. | 18:31 |
| T42 | <adampigg> mal: time to look at camera fixes? | 18:31 |
| mal | @adampigg I'll see if I check those after sauna | 18:32 |
| mal | @DylanVanAssche can you show the iio config file in both cases | 18:33 |
| mal | @DylanVanAssche in the earlier log you had "proximity= true" | 18:34 |
| T42 | <DylanVanAssche> It prints 'true' but if you check messwerk, it's not detected though (the print is coming from assigning true/false to withinProximity) | 18:34 |
| T42 | <DylanVanAssche> mal: config: https://bin.disroot.org/?d41c73acb848f768#uJ5eBN5Vvn7S77MsbRN2ez3/014PFi9oxw140ZOVuNw= | 18:35 |
| mal | @DylanVanAssche we need to first make sure sensorfw can show correct values in log | 18:36 |
| T42 | <DylanVanAssche> mal: true, trying to assign a default value to offset and scale when the sensor has none. Otherwise these values can be uninitialized | 18:37 |
| mal | does als need some scaling? | 18:39 |
| mal | you just need to use 1 by default | 18:39 |
| T42 | <DylanVanAssche> mal: it has a scale property in IIO though | 18:39 |
| mal | well kernel should have initialized that | 18:39 |
| T42 | <DylanVanAssche> `[root@Sailfish ~]# cat /sys/bus/iio/devices/iio\:device1/in_illuminance_scale | 18:40 |
| T42 | <DylanVanAssche> 6.400000` | 18:40 |
| T42 | <DylanVanAssche> proximity has the same scale | 18:40 |
| mal | is illuminance the correct one? | 18:40 |
| T42 | <DylanVanAssche> for the light sensor yes, the the proximity it has the same scale but the raw data path is different (in_proximity_raw) | 18:42 |
| mal | @DylanVanAssche just to understand how things work, are scales wrong or something? is the 6.4 wrong? | 18:46 |
| T42 | <DylanVanAssche> mal: The scales are wrong and the offsets are wrong too. It worked fine if the proximity sensor support is not there though. Anyway, I'm tired, will investigate later further | 18:47 |
| mal | are those scales defined in kernel driver or obtained from firmware? | 18:49 |
| T42 | <DylanVanAssche> They are defined through a sysfs path: /sys/bus/iio/devices/DEVICE/in_illuminance_scale for example | 19:02 |
| T42 | <DylanVanAssche> Sensorfw should read them when creating the sensor | 19:03 |
| mal | @DylanVanAssche it's kernel that creates those sysfs paths so where in kernel is the value set, or is it set using some data from i2c or something | 19:30 |
| T42 | <DylanVanAssche> mal: I'm not so sure how these values are retrieved, but I think from the sensors over I2C or other connections | 19:31 |
| mal | kernel driver source would tell that | 19:34 |
| T42 | <DylanVanAssche> Okay, will take a look soonTM | 19:35 |
| mal | can you give a link to that on github | 19:37 |
| T42 | <DylanVanAssche> To the driver source? | 19:40 |
| T42 | <DylanVanAssche> stk3310 IIO driver: https://gitlab.com/pine64-org/linux/blob/pine64-kernel/drivers%2Fiio%2Flight%2Fstk3310.c | 19:43 |
| T42 | <Umeaboy> Just because Samsung hasn't released full source code to build AOSP for the S10, does that automatically mean that we can't port Sailfish to it? I mean, the HADK tells the porter to build AOSP. | 19:47 |
| T42 | <Umeaboy> I'm considering to purchase it. | 19:47 |
| jellypony | mal: Good evening! I made changes to patterns you suggested yesterday. Now droid hal running but i still cant get into gui. I had a few problem that had been solved by using chapter 13 of hadk. Unfortunately lipstick still fails. journalctl: https://pastebin.com/AhnZk19B | 19:51 |
| jellypony | is it because of jolla-startupwizard-pre-user-session.service failure? | 19:52 |
| mal | @Umeaboy there seems to be unofficial lineage os for that but no sources for the builds, only kernel sources | 19:52 |
| mal | jellypony: you need to show more logs, dmesg and /usr/libexec/droid-hybris/system/bin/logcat | 19:53 |
| jellypony | dmesg no output ._. | 19:57 |
| mal | what? | 19:58 |
| mal | how is that possible | 19:58 |
| jellypony | /usr/libexec/droid-hybris/system/bin/logcat is not readable :0 | 19:59 |
| jellypony | i mean it seems like it contains nontext data | 20:00 |
| mal | that is a command, not a file, same for both | 20:00 |
| jellypony | whoops | 20:01 |
| jellypony | soorry | 20:01 |
| jellypony | a knew about dmesg | 20:01 |
| jellypony | its broken | 20:01 |
| mal | that's one of most basic things, not sure how it can be broken, are you sure you didn't do something strange to kernel configs? | 20:03 |
| mal | like copying whole defconfig from somewhere? | 20:03 |
| jellypony | logcat output: https://pastebin.com/fF7RdKSn | 20:03 |
| jellypony | dmesg doesnt work in all the builds with different kernel configs | 20:05 |
| jellypony | dunno why | 20:05 |
| mal | what different configs? | 20:05 |
| jellypony | manually configured | 20:06 |
| jellypony | i mean | 20:06 |
| jellypony | I messed up few in the beginning | 20:06 |
| mal | you should show all the changes you made | 20:08 |
| mal | @DylanVanAssche have you tried printing the raw value string you read from buffer before you get result using strtol? | 20:09 |
| mal | @DylanVanAssche I mean buf after this https://github.com/sailfish-on-dontbeevil/sensorfw/blob/94a5ba7fed2d50d3ccd63a5048688aa60051983f/adaptors/iioadaptor/iioadaptor.cpp#L435 | 20:10 |
| T42 | <Akatsu %lastname%> @Mister_Magister have you fixed this? I do have same issue with android base | 20:11 |
| T42 | <Akatsu %lastname%> Fwd from mal: Mister_Magister: you have so much failing like "E QMI_FW : QMUXD: WARNING qmi_qmux_if_pwr_up_init failed!" qmi is quite important for many things | 20:11 |
| Mister_Magister | need more context @Akatsu | 20:12 |
| T42 | <Akatsu %lastname%> http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2019-08-15.log.html | 20:14 |
| jellypony | mal: my kernel configs: | 20:16 |
| jellypony | default (from device tree): https://pastebin.com/VLX8Xwmw | 20:16 |
| jellypony | present: https://pastebin.com/Pi555yEh | 20:16 |
| Mister_Magister | @Akatsu ahhh fxtec thingy. Sorry i'm afraid someone else fixed it. piggz fixed it with "Fixed with added firmware symlink /firmware > /vendor/firmware_mnt/" so you can ask him if that suggestion won't help | 20:17 |
| mal | and that is by adding correct things to straggler files probably | 20:20 |
| T42 | <DylanVanAssche> mal: Not yet, will check tomorrow | 20:23 |
| T42 | <adampigg> @DylanVanAssche what do you have in /dev/iio* ? | 20:30 |
| jellypony | mal: sorry, incomplete logcat output . Here is | 20:33 |
| jellypony | correct one | 20:33 |
| jellypony | shi~ | 20:34 |
| jellypony | mal: output of logcat is too big D: | 20:38 |
| mal | jellypony: show the first part of it | 20:47 |
| mal | jellypony: about those kernel configs, seems to are different, one from out and one from kernel repo, very difficult to compare | 20:49 |
| jellypony | mal: got full output (wrote output to file which was transfered to pc via recovery): https://pastebin.com/ZRbNQPG0 | 20:51 |
| jellypony | mal: here is .config if it would be made with no changes at all https://pastebin.com/n14zUZiJ | 21:12 |
| jellypony | now it's easier to compare | 21:12 |
| jellypony | Sorry for my English, I'm not practicing much. | 21:20 |
| mal | jellypony: you seem to have some strange change, you disabled CONFIG_FW_LOADER_USER_HELPER=y | 21:33 |
| mal | and the fallback also | 21:34 |
| mal | jellypony: also it's easier to see the kernel confrig changes if you give the defconfig files (original and modified) | 21:36 |
| mal | not the .config files | 21:36 |
| T42 | <FagotMan> @clee [has anybody started working on getting Sailfis …], I'll "up" that question. Hope some will start working on 3xl 😃 | 21:47 |
| T42 | <FagotMan> I'll keep 200$ for some1 who can make it working if any1 is interested 😉 | 21:47 |
| piggz | mal: added a fix for the resolution icon position also | 21:49 |
| mal | piggz: ok, I didn't look at those PRs today, trying to check tomorrow | 21:52 |
| piggz | np, im away now anyay :) | 21:53 |
| jellypony | mal: mer_kernel_check gives me warnings for these. afair it says these settings needed for lollipop devices. | 21:56 |
| jellypony | so I disabled them | 21:56 |
| jellypony | why not? | 21:56 |
| mal | please show both the original and modified defconfig files (not the .config) | 22:00 |
| mal | jellypony: we use fw loader in sailfish | 22:01 |
| jellypony | oh... | 22:03 |
| mal | let's continue debugging the issues tomorrow | 22:09 |
| jellypony | modified config: https://pastebin.com/VDa3kbfC | 22:12 |
| jellypony | ok :0 | 22:12 |
| jellypony | mal: good night :3 | 22:14 |
| T42 | <Umeaboy> @mal [@Umeaboy there seems to be unofficial lineage …], Okey. What's missing that can't be found on opensource.samsung.com? | 22:14 |
| T42 | <Umeaboy> Can't we use the device tree from omnirom? | 22:19 |
| mal | we can in theory, just might a bit more work, not much but some | 22:22 |
| r0kk3rz | depends on how much retooling they did with the make files | 23:34 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!