rinigus | r0kk3rz : manual copy of pro1 meta package and manual check that all patterns were covered + corrections/additions. Didn't know about the script... Fortunately, it's a single time investment | 06:05 |
---|---|---|
Mister_Magister | mal: @NotKit i added/subtracted values from https://github.com/mer-hybris/qt5-qpa-hwcomposer-plugin/blob/master/hwcomposer/hwcomposer_backend_v20.cpp#L281-L282 these 2 lines but that didn't do any change. I tried reporting less height in get screen size but that caused it to fail validation | 07:15 |
r0kk3rz | rinigus: yeah its not bad, but would have been nice to test the script a little nvm | 07:39 |
vknecht | rinigus, good idea about using official recovery, thanks ! now I see /vendor symlink and /fstab.loire are missing... | 08:52 |
vknecht | (despite taking measures so they're in out/ before packaging droid-hal) | 08:53 |
T42 | <adampigg> R0kk3rz, hand crafted | 09:10 |
rinigus | vknecht: hopefully it help to add those | 10:23 |
rinigus | looking into logs, seems like my message was skipped. so, let me ask again | 10:49 |
rinigus | for those blessed with lvm/ext4: how do you backup and restore partitions? as when I want to flash new sfos or aosp image, test something and then restore old install. | 10:49 |
rinigus | I presume that combination of flashing old image and ext4 dump/restore should work. | 10:49 |
vknecht | rinigus, guess good old 'dd' should do the job | 11:36 |
rinigus | vknecht: you mean with full lvm pe data? | 11:37 |
rinigus | but I do wonder if something like it has been thought about. as we cannot rely on twrp | 11:37 |
vknecht | afaik dd doesn't care about what it reads/write | 11:38 |
vknecht | other option could be EDL mode with emmcdl utility ; requires having programmer file for the device tho, don't know it's that's available on sonys | 11:40 |
rinigus | vknecht: it should be something simple and available through hybris-recovery, I think. then it would be useful for such tests | 11:42 |
rinigus | another issue that was raised last night: looks like on couple of devices, NFC gets re-enabled after reboot (if user disabled it in settings). is this SFOS bug or issue with the ports? | 11:56 |
vknecht | just an idea, maybe a permission problem like for manual access point config some years ago ? https://github.com/mer-hybris/hadk-faq#rild-is-running-but-ofono-does-not-work ? | 12:04 |
rinigus | vknecht: maybe. note that nfc does get disabled when you toggle it in the settings. | 12:06 |
rinigus | so, its at least not permissions for nfc switch | 12:06 |
vknecht | yes, but maybe just for the state-remembering file or whatever | 12:08 |
rinigus | vknecht: yes, but then its a general SFOS issue | 12:12 |
vknecht | rinigus, didn't you get that sort of build dependencies errors for droid-hal-img-boot, where it requires cryptsetup, initrd-logos, openssh-{clients,server} and droid-hal-$HABUILD_DEVICE-{kernel,tools} ? https://pastebin.com/Ankr0ida | 16:46 |
vknecht | previously I installed them with sb2, but now I've reset the target and wonder if I really should have done it | 16:47 |
rinigus | vknecht: probably I did. did you run sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in --force-resolution droid-hal-$HABUILD_DEVICE-kernel-modules ? | 17:15 |
rinigus | vknecht: as I am building boot image at OBS, check the dependencies there. had to add few packages to my obs for it, if I remember correctly | 17:16 |
vknecht | yes, I ran it for droid-hal-suzu-kernel-modules, but it looks as if installing droid-hal-suzu-kernel and droid-hal-suzu-tools is required too | 17:21 |
vknecht | just build the others with build_packages like that: | 17:22 |
vknecht | rpm/dhd/helpers/build_packages.sh --mw=https://git.sailfishos.org/mer-core/cryptsetup | 17:22 |
vknecht | rpm/dhd/helpers/build_packages.sh --mw=https://github.com/mer-hybris/initrd-logos-sailfish | 17:22 |
vknecht | rpm/dhd/helpers/build_packages.sh --mw=https://git.sailfishos.org/mer-core/openssh | 17:22 |
vknecht | the ones you had to add were probably yamui/initrd-helper/hw-ramdisk (the ones built locally by build_bootimg_packages.sh) | 17:27 |
mautzone | Hi! I'm trying to make a new cm14.1 based port for the Nexus5. I'm stuck at hybris-hal: external/bouncycastle: Invalid LOCAL_SDK_VERSION '9' | 17:27 |
mautzone | Can anyone point me in the right direction? | 17:27 |
vknecht | mautzone, https://ekasiswanto.wordpress.com/2017/06/21/how-to-compile-android-lollipop-5-1-1-contacts-onwindows-os/ mentions the problem, apparently solved by downloading/updating a prebuilt | 17:38 |
mautzone | vknecht: Thanks, was reading it at the moment :) | 17:40 |
rinigus | vknecht: don't you run it after `rpm/dhd/helpers/build_packages.sh --droid-hal` | 17:41 |
rinigus | ? | 17:41 |
vknecht | run what ? sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -m sdk-install -R zypper in --force-resolution droid-hal-$HABUILD_DEVICE-kernel ? | 17:43 |
vknecht | or you mean that build_packages.sh --droid-hal should do it already ? | 17:44 |
rinigus | vknech: I mean whether droid-hal-suzu-kernel and droid-hal-suzu-tools are installed already during --droid-hal stage? | 17:45 |
rinigus | (not sure about it though) | 17:45 |
vknecht | doesn't look like it installs them, just have the -devel and -kernel-modules: https://pastebin.com/buQTd5f7 | 17:49 |
vknecht | from rpm/dhd/helpers/util.sh, building dhd has a do_not_install flag (like configs and version) | 17:56 |
rinigus | vknecht: but I wonder why doesn't it pull the required dependencies? as they should be defined in img spec? | 17:57 |
rinigus | openssh ones, for example. I may have installed them manually, though. with sb2 for local build | 17:57 |
rinigus | at obs it looks to be pulled | 17:58 |
vknecht | maybe a shortcoming of local builds | 17:58 |
vknecht | for openssh, only had to build it like other mw | 17:58 |
vknecht | maybe I should switch to obs already | 17:59 |
*** OhYash1 is now known as ohyash | 18:12 | |
vknecht | ain't it ? | 23:26 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!