| T42 | <nc1x72> Got the droid-system-Spacewar repo up but now running into this error "Could not get version for droid-system-Spacewar: fatal: --unshallow on a complete repository does not make sense" | 02:54 |
|---|---|---|
| T42 | <nc1x72> | 02:54 |
| T42 | <nc1x72> The repo is here https://github.com/SailfishOSSpacewar/droid-system-Spacewar | 02:54 |
| *** xmn_ is now known as xmn | 05:54 | |
| T42 | <elros34> according to channel logs quic search try to tag that repo | 08:38 |
| T42 | <nc1x72> Tagging the repo didn’t work either (unless I did it wrong) | 09:31 |
| T42 | <nc1x72> Nevermind. It got pass this error. Just had to delete local repo first | 09:38 |
| Mister_Magister | mal: I dont' know if you remember but quick reminder, on oneplus 6, on first install, fingerprint works fine, but then it stops working after reboot and i didn't have time to debug your last suggestions. But new fun and interesting piece of information. Apparently if you remove the fingerprint before reboot and then add it after reboot, it works just fine lmao Curious bug isn't it? xd | 09:40 |
| Mister_Magister | i just thought you'd find it fascinating xd | 09:41 |
| T42 | <zhainhart> i also want to install sailfish on my Nothing Phone (1) but do not have enough courage to starting it. i hope the porting process going well and someday can be installed in my phone 👍 (re @nc1x72: Tagging the repo did...) | 13:08 |
| T42 | <Umeaman> Okey, but if you want something you have to do something to. I want to conquer the world, but it's not going to happen if I push my problems onto others. Learn by making mistakes and make a backup of important data before. | 14:49 |
| T42 | <Umeaman> What exactly do you need help with in the porting procedure in the HADK? | 14:50 |
| *** Effilry is now known as FireFly | 15:11 | |
| T42 | <nc1x72> Another error when I run build_packages.sh —version | 17:57 |
| T42 | <nc1x72> | 17:57 |
| T42 | <nc1x72> https://hastebin.ianhon.com/8587 | 17:57 |
| T42 | <nc1x72> | 17:57 |
| T42 | <nc1x72> Anyone knows about this? | 17:57 |
| T42 | <nc1x72> I already run build_packages.sh -c prior to the failing command | 17:58 |
| mal | btw, one thing you'll have issues with, don't use latest master branch of qt5-qpa-hwcomposer-plugin, use last tagged version | 18:09 |
| mal | the issue will be a runtime issue | 18:09 |
| mal | graphics will fail | 18:09 |
| T42 | <nc1x72> I have a question, where are the failed deps supposed to be installed? Under $ANDROID_ROOT/droid-local-repo/$DEVICE or somewhere else? Because the build_packages -c command runs fine but these files are not built. | 18:19 |
| mal | the list of packages is not always accurate | 18:26 |
| mal | all of the other packages have been built? | 18:28 |
| mal | can you see what packages under droid-local-repo/$DEVICE/ | 18:29 |
| mal | have you tried to manually install the missing droid-config packages? | 18:31 |
| T42 | <nc1x72> Here's the packages list : https://hastebin.ianhon.com/7833 | 18:32 |
| T42 | <nc1x72> I haven't tried to manually install the missing packages. What command should I issue? | 18:32 |
| mal | the rpms should be under droid-local-repo/$DEVICE/ so just do something like "sb2 -t $VENDOR-$DEVICE-aarch64 -R rpm -i droid-local-repo/$DEVICE/some_file.rpm" | 18:32 |
| T42 | <elros34> did you finish building middleware build_packages.sh --mw? | 18:35 |
| mal | I still suspect you'll have issues with the device codename, if you don't want to change to lower case then you probably at least need to change the folders and files with codename in here https://github.com/SailfishOSSpacewar/droid-config-Spacewar/tree/master/kickstart to lower case because https://github.com/sailfishos/ssu/blob/master/ssuks/ssukickstarter.cpp does toLower for the codename | 18:39 |
| mal | I mean filenames and folders with codename | 18:40 |
| mal | not sure if other parts could have issues with non-lower-case codename | 18:41 |
| T42 | <nc1x72> @@elros34 it only builds libhybris. Not sure if that's normal | 19:06 |
| T42 | <nc1x72> Regarding the codename, I'll change it and retry everything from scratch | 19:07 |
| mal | you only need to fix those couple of repos | 19:08 |
| T42 | <nc1x72> Correction : build_packages.sh —mw fails to build pulseaudio-modules-droid | 19:09 |
| mal | how does it fail? | 19:09 |
| mal | check that you have latest version of that in sources | 19:12 |
| T42 | <nc1x72> Something about: | 19:12 |
| T42 | <nc1x72> | 19:12 |
| T42 | <nc1x72> -Wimplicit-function-declaration | 19:12 |
| T42 | <nc1x72> ‘dm_config_port’ has no member named ‘type’ | 19:12 |
| T42 | <nc1x72> | 19:12 |
| T42 | <nc1x72> I think my sources might be corrupted because this one seems unusual. I’m deleting everything from hybris and rpm folders to repo sync again. Will let you know | 19:12 |
| mal | I'll do a bit of testing | 19:18 |
| T42 | <nc1x72> With my repos? | 19:19 |
| mal | no fp5 | 19:19 |
| T42 | <nc1x72> Ha | 19:19 |
| T42 | <nc1x72> Okay | 19:19 |
| mal | latest pulseaudio-modules-droid built fine for fp5 | 19:20 |
| T42 | <nc1x72> Yes I just re-run —mw command and it compiled fine. But there are still some dependencies not compiled like the `droid-config-preinit-plugins` | 19:46 |
| T42 | <nc1x72> Could that be due to the S in uppercase in $DEVICE name? | 19:47 |
| T42 | <elros34> for sure this one is built | 20:09 |
| T42 | <elros34> I bet ngfd binder plugin is missing, you are using some other project as a base so you need more packages than default build by --mw | 20:12 |
| mal | yeah, that ngfd binder plugin something I made | 20:18 |
| T42 | <nc1x72> What’s the purpose of the ngfd plugin? | 20:19 |
| T42 | <nc1x72> If it’s not critical, I could just remove it from hal-version requirement | 20:20 |
| T42 | <elros34> its not critical | 20:22 |
| mal | you should instead change this line https://github.com/mlehtima/droid-hal-version-fp5/blob/master/rpm/droid-hal-version-fp5.spec#L9 to this https://github.com/mlehtima/droid-hal-version-fp4/blob/master/rpm/droid-hal-version-fp4.spec#L9 | 20:23 |
| mal | native vibrator is the usual one, fp5 is so far the only device needing binder backend | 20:23 |
| T42 | <b100dian> Was the driver so quirky on fp5 that you had to develop a binder plugin for vibrator service?? | 20:25 |
| T42 | <b100dian> am now curious which is it | 20:26 |
| T42 | <nc1x72> Okay. Here are the remaining missing deps : | 20:29 |
| T42 | <nc1x72> | 20:29 |
| T42 | <nc1x72> - droid-config-preinit-plugins | 20:29 |
| T42 | <nc1x72> - droid-config-pulseaudio-settings | 20:29 |
| T42 | <nc1x72> - droid-config-sailfish | 20:29 |
| T42 | <nc1x72> - ngfd-plugin-binder-vibrator (to be removed) | 20:29 |
| T42 | <nc1x72> - pulseaudio-modules-droid | 20:29 |
| T42 | <nc1x72> - qt5-qpa-hwcomposer-plugin | 20:29 |
| T42 | <nc1x72> | 20:29 |
| T42 | <nc1x72> Which one is not critical and/or is fp5 specific? | 20:29 |
| T42 | <nc1x72> | 20:29 |
| T42 | <nc1x72> I'm still confused about the last 2 dependencies because droid-local-repo/$DEVICE has the rpms | 20:29 |
| T42 | <nc1x72> ``` | 20:32 |
| T42 | <nc1x72> pulseaudio-modules-droid-14.2.106-1.aarch64.rpm | 20:32 |
| T42 | <nc1x72> pulseaudio-modules-droid-common-14.2.106-1.aarch64.rpm | 20:32 |
| T42 | <nc1x72> pulseaudio-modules-droid-devel-14.2.106-1.aarch64.rpm | 20:32 |
| T42 | <nc1x72> pulseaudio-modules-droid-hidl-1.5.1-1.aarch64.rpm | 20:32 |
| T42 | <nc1x72> qt5-qpa-hwcomposer-plugin-5.6.2.26+master.20260109160921.41e7bda-1.aarch64.rpm``` | 20:32 |
| T42 | <nc1x72> | 20:32 |
| T42 | <nc1x72> | 20:32 |
| T42 | <nc1x72> From droid-local-repo/$DEVICE | 20:32 |
| T42 | <elros34> how do you know the are missing? log is not so straightforward about it | 20:34 |
| T42 | <nc1x72> Here's the full log from last trial (after running build_packages.sh —version) : https://hastebin.ianhon.com/9b1d | 20:36 |
| T42 | <elros34> "'ngfd-plugin-binder-vibrator" is still there, do you rebuild droid-config after removing it? | 20:38 |
| T42 | <nc1x72> Not yet. | 20:42 |
| T42 | <nc1x72> Well, it worked after changing the vibrator macro | 20:55 |
| T42 | <nc1x72> It seems like that was the real issue and the script stopped there without checking whether the other dependencies were met or not | 20:55 |
| mal | @b100dian yes, the driver is quite complex on fp5 | 21:03 |
| mal | @nc1x72 remember what I said about qt5-qpa-hwcomposer-plugin | 21:03 |
| T42 | <nc1x72> Also have to remove this line probably https://github.com/SailfishOSSpacewar/droid-config-Spacewar/blob/4c9a63f3abbc46c0c3d71aaecb41a8d29b1dadd8/patterns/patterns-sailfish-device-adaptation-Spacewar.inc#L38 | 21:04 |
| mal | replace it with Requires: ngfd-plugin-native-vibrator | 21:05 |
| T42 | <nc1x72> About qt5-qpa-hwcomposer-plugin, should I clone it and manually compile the rpm? | 21:05 |
| T42 | <b100dian> mal: can you tell me which driver filename is used on fp5 so I can satisfy my curiosity? | 21:06 |
| mal | no, you go to the folder i.e. hybris/mw/qt5-qpa-hwcomposer-plugin and run "git reset --hard 5.6.2.26" and the go back to $ANDROID_ROOT and run "rpm/dhd/helpers/build_packages.sh -o -b hybris/mw/qt5-qpa-hwcomposer-plugin" | 21:07 |
| mal | @b100dian I think this one https://github.com/mlehtima/android_kernel_fairphone_qcm6490/tree/hybris-23.2/drivers/misc/haptic_hv | 21:10 |
| T42 | <b100dian> it's an entire folder :wow: | 21:16 |
| mal | @b100dian you can get some idea by looking at the device attributes https://github.com/mlehtima/android_kernel_fairphone_qcm6490/blob/hybris-23.2/drivers/misc/haptic_hv/haptic_hv.c#L2918 | 21:20 |
| mal | @b100dian the hal module https://github.com/LineageOS/android_device_fairphone_FP5/blob/lineage-23.2/vibrator/Vibrator.cpp#L436 just look at how many things it does to turn vibra on | 21:22 |
| mal | and different things based on duration | 21:22 |
| T42 | <b100dian> mal: yes but haptic_hv.c#input_upload_effect() doesn't look very different than custom waveform for tucana or xperia 5 mark II iirc https://github.com/sailfishos/ngfd/commit/d70238488316756e474c2269acf35021855a63d6 | 21:23 |
| T42 | <b100dian> Anyway, I was just curious, but it's probably better to have a binder vibration anyway | 21:24 |
| mal | yeah, I wasn't interested in debugging how to make it work | 21:27 |
| mal | and that special case for different durations is even worse than just custom waveform | 21:28 |
| mal | it was easy to make the binder plugin | 21:30 |
| T42 | <b100dian> true. /primitive_duration was not in that doc I sent. On those other drivers the duration would be returned from the upload, iirc | 21:32 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!