| T42 | <Yesfjgs %lastname%> https://t.me/joinchat/Q8EBx9qmr3pM6XeV | 05:16 |
|---|---|---|
| T42 | <ItsMeShouko> how do I run | 10:24 |
| T42 | <ItsMeShouko> rfkill unblock all | 10:24 |
| T42 | <ItsMeShouko> before bluebinder_wait.sh ? | 10:24 |
| T42 | <ItsMeShouko> I added file to /sparse/usr/bin/droid/bluebinder_wait.sh but while building image it conflicts, how do I override it? | 11:22 |
| T42 | <elros34> Why you want to do this? bluebinder_wait.sh is part of bluebinder package. You could probably override bluebinder.service which execute that script in /etc/systemd/system/bluebinder.service instead. | 11:56 |
| T42 | <ItsMeShouko> okay, I'll try that, my device requires rfkill on init while running ubuntu touch to enable bluetooth, I am trying to do the same on sfos so that bt works... | 12:15 |
| T42 | <ItsMeShouko> I tried downgrading sensorfw package to 0.11.9 but I got error while building | 12:48 |
| T42 | <ItsMeShouko> 2 Problems: | 12:48 |
| T42 | <ItsMeShouko> Problem: hybris-libsensorfw-qt5-binder-0.11.9-0.armv7hl conflicts with hybris-libsensorfw-qt5-hal provided by hybris-libsensorfw-qt5-hal-0.11.9-0.armv7hl | 12:48 |
| T42 | <ItsMeShouko> Problem: hybris-libsensorfw-qt5-binder-devel-0.11.9-0.armv7hl requires hybris-libsensorfw-qt5-binder = 0.11.9-0, but this requirement cannot be provided | 12:48 |
| T42 | <ItsMeShouko> Problem: hybris-libsensorfw-qt5-binder-0.11.9-0.armv7hl conflicts with hybris-libsensorfw-qt5-hal provided by hybris-libsensorfw-qt5-hal-0.11.9-0.armv7hl | 12:48 |
| T42 | <ItsMeShouko> Solution 1: Following actions will be done: | 12:48 |
| T42 | <ItsMeShouko> do not install hybris-libsensorfw-qt5-binder-0.11.9-0.armv7hl | 12:48 |
| T42 | <ItsMeShouko> deinstallation of hybris-libsensorfw-qt5-binder-0.12.1+master.20201128125946.492a653-0.armv7hl | 12:48 |
| T42 | <ItsMeShouko> Solution 2: do not install hybris-libsensorfw-qt5-hal-0.11.9-0.armv7hl | 12:48 |
| T42 | <elros34> you need to specify which plugin you want to build. For hybris16 this will be binder: build_packages.sh -oD -b hybris/mw/sensorfw -s rpm/sensorfw-qt5-binder.spec | 12:59 |
| T42 | <simonschmeisser> @elros34 interesting, how do I change that on obs? | 13:58 |
| T42 | <elros34> spec file is selected based on package name, for example: https://build.merproject.org/package/show/nemo:testing:hw:oneplus:dumpling/sensorfw-qt5-binder | 14:09 |
| T42 | <ItsMeShouko> @RealDanct12 how did you fix video recording on lavendar? | 14:26 |
| T42 | <RealDanct12> i didn't | 14:26 |
| T42 | <RealDanct12> video recording only works on front camera | 14:26 |
| T42 | <ItsMeShouko> how did you do it for front cam then? | 14:27 |
| T42 | <RealDanct12> back camera is most likely connected differently, 48mp is impossible on sdm660 by specs | 14:27 |
| T42 | <RealDanct12> @ItsMeShouko [how did you do it for front cam then?], didn't do anything, just worked | 14:27 |
| T42 | <ItsMeShouko> alright | 14:28 |
| mal | @RealDanct12 is there anything in logs when back camera fails? have you tried different resolutions? are you doing 1080p or 4k recording? | 15:27 |
| T42 | <RealDanct12> it happens at doesn't matter which resolution | 15:28 |
| T42 | <RealDanct12> but it's been a while and im busy atm, so no time checking with sfos | 15:29 |
| attah | I thought i should try and hack in some more retries in fastboot, to work around intermittent results on USB3... but seems i can't even do "fastboot devices" - i just get a bunch of question marks, any ideas? | 15:31 |
| mal | did you have some issue during flashing? | 15:38 |
| attah | mal: it's still on stock Android... it's a preemptive Xperia 10 II (: | 15:39 |
| mal | I don't quite understand what you are trying to do | 15:40 |
| attah | At least for me, using the fastboot command, was really intermittent on USB3... like 20% success rate, and you need several of them to go OK for flashing to work | 15:41 |
| attah | so i was thinking if i build in retries under the hood, it could work... but i can't even get it to work once with this particular phone | 15:42 |
| piggz | fastboot doesnt work at all for me on the pro1 with usb 3 ... i have to go via an ancient hub! | 15:42 |
| mal | I have no idea which port I use on my laptop but seems to work fine | 15:42 |
| attah | I tried USB2 on my Pinebook Pro, and i got the same behavior | 15:43 |
| T42 | <simonschmeisser> @elros34 do I need to do anything special after switching from hybris-sensorfw-qt5-hal to -binder? Because well ... it doesn't start the UI any longer | 20:42 |
| T42 | <simonschmeisser> telnet works | 20:42 |
| T42 | <simonschmeisser> just saw that there are quite some updates available, not sure where they come from ... | 20:46 |
| T42 | <elros34> didn't you use hybris-15? I am not aware about anything special needed but for sure you will find in logs why it fails | 20:48 |
| T42 | <simonschmeisser> and hybris 15.1 does not use binder for sensorfw? | 21:03 |
| T42 | <simonschmeisser> mce[707]: mce-sensorfw.c: sfw_plugin_load_cb(): plugin(alssensor): error reply: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. | 21:15 |
| T42 | <elros34> it's recommended and used by default in build_packages.sh on hybris-16 | 21:15 |
| T42 | <elros34> what are even trying to fix? | 21:16 |
| T42 | <simonschmeisser> there's three of these errors (alssensor, orientationsensor and proximity) | 21:17 |
| T42 | <elros34> does sensorfw work? | 21:17 |
| T42 | <simonschmeisser> it did not with the sensorfw-qt5-hal, that's why I tried the binder one (as switching to binder also seemed to fix the modem not being visible) | 21:18 |
| T42 | <simonschmeisser> how do I test from shell if it works now? | 21:19 |
| T42 | <Verevka86> @simonschmeisser [it did not with the sensorfw-qt5-hal, that's w …], Test this- https://github.com/SailfishOS-sagit/droid-config-sagit/commit/c03cb686e16eb2bcc348130fc70e654ba4354667 | 21:20 |
| T42 | <elros34> I will switch back to non binder plugin, then test_sensors to check whether sensors works on android side at all | 21:20 |
| T42 | <elros34> you can use test_sensors even now but my point was that non binder plugin should also works fine | 21:22 |
| T42 | <simonschmeisser> it reports 25 sensors | 21:24 |
| T42 | <elros34> ok so get logs from sensorfw | 21:26 |
| T42 | <simonschmeisser> sensorfwd -l=debug gives lots of Could not find remote object for sensor service. Trying to reconnect. | 21:32 |
| mal | @Verevka86 such pattern change should not be needed to use binder sensors, the binder package provides hybris-libsensorfw-qt5 | 21:40 |
| mal | @simonschmeisser do you have correct version of the sensor plugin built? | 21:40 |
| mal | you should be building version 0.11.9 | 21:41 |
| T42 | <simonschmeisser> it is, I learned that @mal 😃 | 21:42 |
| T42 | <simonschmeisser> accel sensor was working with sensorfw-qt5-hal but no others, so I decided to try out the binder variant but now it doesn't start at all any longer (lipstick times out and get's killed) | 21:44 |
| T42 | <simonschmeisser> with -hal lipstick starts again but sensors like light or proximity do not work in csd (or in general) | 22:06 |
| T42 | <linusdan> @edp_17 Do you remember how to generate the kernel.img for SFOS on the i9100? I went back to the base of hybris-16.0 and I have no idea how to do this | 22:14 |
| mal | @simonschmeisser do you have the csd config on the device? | 22:32 |
| mal | https://github.com/mer-hybris/hadk-faq#sensors | 22:33 |
| T42 | <simonschmeisser> mal: read that many times but I still cannot find what I'm actually supposed to configure there? it seems only yes/no (0/1)? | 22:39 |
| T42 | <simonschmeisser> thanks for your help so far, will go to sleep now | 22:41 |
| T42 | <elros34> at least make sure you have there LightSensor=1 and ProxSensor=1 | 22:42 |
| mal | @simonschmeisser show the whole file /usr/share/csd/settings.d/hw-settings.ini you have on the device | 23:14 |
| T42 | agnesmarain was added by: agnesmarain | 23:22 |
| T42 | <edp_17> @linusdan [@edp_17 Do you remember how to generate the ke …], The same way how you generate the hybris-boot.img: | 23:35 |
| T42 | <edp_17> step into HABUILD (ubu-chroot -r $PLATFORM_SDK_ROOT/sdks/ubuntu) then: | 23:35 |
| T42 | <edp_17> 1. cd $ANDROID_ROOT | 23:35 |
| T42 | <edp_17> 2. source build/envsetup.sh | 23:35 |
| T42 | <edp_17> 3. export USE_CCACHE=1 | 23:36 |
| T42 | <edp_17> 4. breakfast $DEVICE | 23:36 |
| T42 | <edp_17> then finally | 23:36 |
| T42 | <edp_17> 5. make -j$(nproc --all) hybris-hal droidmedia | 23:36 |
| T42 | <edp_17> Then your new kernel will be in $ANDROID_ROOT/out/target/product/$DEVICE/kernel file and this is what you need to flash into KERNEL partition | 23:36 |
| T42 | <linusdan> and how to generate the kernel.img if the file name is only kernel? | 23:40 |
| T42 | <edp_17> That is your kernel image. If you want to flash with TWRP, simply rename it to kernel.img when you copy it to the device. At least this is how I do it. 😁 | 23:45 |
| T42 | <linusdan> OK! I will make :) | 23:46 |
| T42 | <linusdan> Thank you for your help! | 23:46 |
| T42 | <edp_17> No problem. Happy New Year. 😁 | 23:47 |
| T42 | <edp_17> @linusdan : Why are you building for hybris-16.0? Experiment or is there something that specifically you need? | 23:49 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!