| masha11 | Hello. Help me, please. How do I do this step? HADK 5.3: In initrd we then have to specify hardcoded /dev/mmcblkXpY nodes for /boot and /data partitions. My device: Motorola Moto Z (griffin). My fstab: https://pastebin.com/zSjAWqUm. My fixup-mountpoints: https://pastebin.com/VX9PpPgL. | 08:15 |
|---|---|---|
| T4 | <elros34> @masha11: your fixup-mountpoints looks ok. make hybris-hal or hybris-boot and changes should be included in initramfs | 08:49 |
| piggz | mal: dhv changes made ... now, if you change your mind again...... !!"$$£%£"" | 10:20 |
| masha11 | T4: After I make hybris-boot, should I rebuild build_packages.sh? | 11:50 |
| mal | you need to run at least build_packages.sh -d | 11:52 |
| mal | unless you manually flash the kernel for testing, meaning flashing hybris-boot.img from out/ using fastboot | 11:53 |
| mal | but to include new kernel to your next build build_packages.sh -d is needed | 11:54 |
| masha11 | mal: ok | 11:54 |
| masha11 | mal: According HADK 5.3: In initrd we then have to specify hardcoded /dev/mmcblkXpY nodes for /boot and /data partitions. Does this mean checking a file fixup-mountpoint or something else? | 12:00 |
| mal | masha11: those are hardcoded automatically by build scripts | 12:08 |
| mal | using fixup | 12:08 |
| masha11 | mal: ok | 12:09 |
| masha11 | mal: Further: "After initrd, systemd needs to mount all other required partitions (such as /system, /firmware, / persist, /config, . . . ) for the HAL layer to work." Should I mount partitions or does systemd do it automatically? | 12:13 |
| mal | masha11: again those are created automatically from fstab using fixup | 12:15 |
| masha11 | mal: ok | 12:15 |
| mal | what are you trying to fix? | 12:17 |
| masha11 | mal: I checked the mount points, they look fine. I'm trying to get an initrd download. I do not have a message "Running Mer Boat Loader" in dmesg. Maybe you need to add any of configuration to defconfig? | 12:36 |
| mal | masha11: which android base? | 12:45 |
| masha11 | mal: android base 8, lineageos 15.1 | 12:47 |
| mal | show your defconfig | 12:48 |
| masha11 | mal: https://pastebin.com/Fc0DAF77 | 12:49 |
| T4 | <elros34> masha11: try to enable CONFIG_USB_CONFIGFS_RNDIS and disable CONFIG_RNDIS_IPA also change these NETFILTER*=m to =y | 13:21 |
| masha11 | T4: ok | 13:22 |
| masha11 | When I install SailfishOS.zip in TWRP, then I have the following output: https://pastebin.com/2xzzJqiy, is this normal? | 13:23 |
| T4 | <elros34> not sure, I never looked at zip installation log. For now flashing hybris-boot is enough. Latest release is 3.0.1.11 | 13:28 |
| T4 | <elros34> you can chek in twrp, sailfish is installed in /data/.stowaways/sailfishos/ | 13:29 |
| vknecht | funny... in h-a-c, ratio is strange for some resolutions eg. 4096x2160 is 256:135 instead of 9:5 like in camera-resolutions.json generated from droid-camres | 16:00 |
| mal | vknecht: I noticed that also, needs some code the make those aspect ratios better, ping piggz | 16:01 |
| vknecht | nah, it's his day off :-) | 16:10 |
| vknecht | might have a look some day, or file an issue to keep it in mind | 16:11 |
| piggz | mal: vknecht: because 256:135 is technically more correct than 9:5 ;) | 17:02 |
| piggz | i got the code of stackexchange for calculating the nearest ratio | 17:03 |
| vknecht | ah ! all is well then :-) | 17:03 |
| kimmoli | isnt there a 'fuzzycompare' in camres? | 17:04 |
| *** OhYash1 is now known as ohyash | 20:01 | |
| vknecht | any tip/example about passing all of a ListView model content as an array ? line 34 was a naive try I guess... https://pastebin.com/YKmsU3gj | 20:06 |
| heroic_1 | piggz: where do you get droid-hal-mido-img-boot from? https://github.com/piggz/droid-config-mido/blob/master/patterns/jolla-hw-adaptation-mido.yaml#L8 | 20:11 |
| piggz | heroic_1: ist built by d-h-d | 20:12 |
| heroic_1 | as far as I can see it only builds droid-hal-img-boot, not the device-specific one | 20:12 |
| heroic_1 | https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L224 | 20:13 |
| piggz | heroic_1: no, the device specific one 'Provides' the generic pacakge | 20:14 |
| heroic_1 | ok nevertheless, where is the device-specifc one built? I only see "%package img-boot" | 20:15 |
| mal | heroic_1: what is the problem you are trying to solve? | 20:20 |
| heroic_1 | I have switched all of my spec files over to use the "community-adaptation"-way you recommended, including getting rid of the "official" kickstart files | 20:21 |
| heroic_1 | Now I am wondering where you get "droid-hal-kagura-img-boot" from | 20:22 |
| mal | heroic_1: was there some reason for that? didn't the old way work? | 20:22 |
| heroic_1 | mal: the "offical" way is a bit cumbersome as it requires users to wipe userdata entirely | 20:22 |
| heroic_1 | I have this package which provides droid-hal-kagura-img-boot https://github.com/marina-bay/droid-hal-img-boot-sony-tone | 20:22 |
| heroic_1 | But that one uses jolla-recovery from hybris-initrd, which expects an lvm setup | 20:23 |
| heroic_1 | jolla-init from https://github.com/mer-hybris/hybris-initrd/blob/master/jolla-init pulls in https://github.com/mer-hybris/hybris-initrd/blob/master/sbin/root-mount | 20:23 |
| mal | heroic_1: if you remove the have_custom_img_boot from spec then img-boot is automatically created from hybris-boot.img built in hybris-hal build | 20:23 |
| mal | https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L649 | 20:24 |
| mal | https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L800 | 20:24 |
| heroic_1 | ok and I should remove the requirement on the device-specific droid-hal-$DEVICE-img-boot then in patterns? | 20:24 |
| mal | https://github.com/mlehtima/droid-config-fp2-sibon/blob/master/patterns/jolla-hw-adaptation-fp2-sibon.yaml#L6 | 20:25 |
| heroic_1 | piggz: but I'm still wondering where you build droid-hal-mido-img-boot, I can't see any repo like "droid-hal-img-boot-mido" under your github account | 20:25 |
| mal | heroic_1: read what I just said | 20:25 |
| heroic_1 | mal: now I'm confused, you now showed me another device which seems to use a device-specific img-boot | 20:26 |
| heroic_1 | is there some rpm magic going on that created "droid-hal-kagura-img-boot" from "%package img-boot" ? | 20:26 |
| mal | heroic_1: I SAID IT IS AUTOMATICALLY GENERATED | 20:27 |
| mal | heroic_1: base name of droid-hal packages is droid-hal-$DEVICE and when you add img-boot to it you get the device specific package | 20:28 |
| mal | it shouldn't be that difficult to understand | 20:29 |
| _sven | heroic_1: what device are you working on? | 20:29 |
| heroic_1 | mal: thank you. it is not particularly difficult to understand, just not documented clearly that the basename is automatically prepended. a section in the wiki about how patterns/spec/inc files work would go a long way | 20:31 |
| heroic_1 | _sven: sony xperia xz, codename kagura | 20:31 |
| mal | once again you are overthinking | 20:31 |
| piggz | heroic_1: i would guess that the %package macro expands to droid-hal-$device + img-boot | 20:32 |
| piggz | but, as mal says, you're over thinking .... i just happens as part of d-h-d, i didnt do anything else | 20:33 |
| heroic_1 | piggz: yes, I understand it now, thank you | 20:33 |
| heroic_1 | there's just a lot of magic going on, and it's not good for grep-a-bility | 20:33 |
| _sven | heroic_1 i tried that one 1,5 years ago, | 20:34 |
| heroic_1 | _sven: I have it working, ril, audio, camera, bt, pretty much everything except usb | 20:34 |
| piggz | mal: https://twitter.com/Nokius/status/1100802937771704321 | 20:34 |
| heroic_1 | _sven: but the port is ugly, it uses the "sailfish x" way of packaging which makes little sense for community adaptations | 20:35 |
| heroic_1 | (pretty much because I kanged nearly everything from the jolla nile port) | 20:35 |
| mal | piggz: https://github.com/piggz/harbour-advanced-camera/pull/9 | 20:35 |
| _sven | i still got the phone, lended it out to someone, maybe its time to get it back | 20:36 |
| mal | vknecht: ^ check the PR above | 20:38 |
| mal | that PR became a bit large again | 20:39 |
| mal | heroic_1: it's basic spec feature that main package name is prepended to subpackage names, main package name is defined here https://github.com/mer-hybris/droid-hal-device/blob/master/droid-hal-device.inc#L128 | 20:43 |
| heroic_1 | ye Imma go write up some docs on that, if only for myself | 20:44 |
| heroic_1 | again mal, for someone not immersed in this it's completely alien | 20:45 |
| heroic_1 | and I don't think it's useful to expect people to know all about rpm packaging when they only need a specific subsection | 20:46 |
| vknecht | mal, now with selfies ? :-) | 20:49 |
| mal | vknecht: yes, although I need to figure out how to mirror the viewfinder | 20:55 |
| mal | heroic_1: you really shouldn't have to think about packaging much when porting | 20:56 |
| mal | vknecht: I also have preliminary code for dynamic orientation handling but it has some viewfinder orientation issues | 20:57 |
| vknecht | that's cool, I'll try tomorrow ; for gallery, I guess dbus jollaGallery.call('showPhotos', undefined) would do for now, unless we really want to keep the slideshow ? | 20:59 |
| vknecht | the 'showImages' call sounds like it could open only a limited list of files, but not able to use it atm | 21:01 |
| heroic_1 | mal: took me 3 minutes https://sx.ix5.org/info/post/sailfish-packaging/ | 21:12 |
| heroic_1 | any way to get that info added to the wiki? | 21:12 |
| heroic_1 | mal: remember the slowness to refresh repos I told you about? turns out the sailfish chroot does not like systemd-resolved | 21:43 |
| heroic_1 | switched NetworkManager's dns resolver on the host to dnsmasq and inexplicably it is way faster now | 21:44 |
| heroic_1 | the chroot is somehow misconfigured, because ALL network calls are extremely slow when using systemd-resolved | 21:44 |
| heroic_1 | even pinging google.com takes ~10 seconds and more | 21:45 |
| mal | ok | 21:46 |
| heroic_1 | this is going to be a problem soon-ish because of systemd's relentless creeping prevalence in distros | 21:47 |
| heroic_1 | because arch is so bleeding edge it's kind of a harbinger for what's to come on ubuntu etc :( | 21:47 |
| piggz | mal: https://github.com/piggz/harbour-advanced-camera/pull/10 | 21:59 |
| mal | piggz: heh, I forgot we have grid layout, I was wondering how to do that | 22:03 |
| piggz | mal: ha, it was pretty simple ;) | 22:03 |
| mal | piggz: so it seems :) | 22:04 |
| mal | piggz: will also help with my dynamic orientation code | 22:04 |
| piggz | mal: i put a comment on the one lime i expect to get commented on ;) | 22:04 |
| mal | piggz: maybe do anchors like this for readability https://github.com/piggz/harbour-advanced-camera/blob/master/qml/pages/CameraUI.qml#L242 at least when there are more than 3 of those | 22:07 |
| piggz | mal: ok | 22:07 |
| mal | piggz: qt qml guide suggests that way | 22:07 |
| mal | https://doc.qt.io/qt-5/qml-codingconventions.html | 22:08 |
| mal | grouped properties in there | 22:09 |
| piggz | mal: updated | 22:11 |
| mal | piggz: I looked at anchors and wonder do we need that one with different value, anchors.margins would set all at the same time | 22:13 |
| piggz | mal: oh yes, forgot that... | 22:13 |
| piggz | done | 22:14 |
| mal | piggz: approved | 22:15 |
| mal | piggz: good fix | 22:16 |
| piggz | mal: coolio ... thats me for the evening, gnight.. | 22:16 |
| mal | piggz: I'll try to get the dynamic orientation finished tomorrow | 22:17 |
| piggz | and i'll do the scene icons | 22:18 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!