T42 | <Verevka86> Hello, does anyone have a working hybris18.1 port (not sony), are you interested in whether your microphone works when you make a phone call? | 13:31 |
---|---|---|
T42 | <adampigg> Mine works (re @Verevka86: Hello, does anyone h...) | 13:59 |
T42 | <edp_17> @adampigg : Hi, I've tried those in my ril_subscription.conf but still no telephony on the device. Do you have any more ideas? | 14:08 |
T42 | <Deepoff> /names@M1kaela_freenode_relaybot | 14:10 |
T42 | <edp_17> Another question. I cannot ssh into the device (telnet works but need to manually bring up the usb network). In Settings/Developer tools I've set password, ticked Developer mode and Remote connection. | 14:24 |
T42 | <edp_17> I even tried to start sshd service but didn't help. | 14:24 |
T42 | <edp_17> Hmm, ssh with wifi do work now. (it didn't before) | 14:26 |
mal | @edp_17 which binder plugin are you using? if you are using the newer one then that doesn't use ril_subscription.conf but uses binder.conf | 18:26 |
piggz | mal: oh, thats news to me :D | 18:28 |
Thaodan | mal: Doesn't seine still include ril_subscription.conf? | 18:56 |
mal | hmm, or will it use both, not sure | 19:25 |
mal | piggz: Thaodan: https://github.com/mer-hybris/ofono-binder-plugin/blob/master/src/binder_plugin.c#L1824 https://github.com/mer-hybris/ofono-binder-plugin/blob/master/src/binder_plugin.c#L84 | 19:27 |
mal | Thaodan: there is default binder.conf in submodule sparse but indeed there is ril config also on seine because submodule brings in those | 19:35 |
T42 | <edp_17> mal : I have binder.conf. As anything I changed in ril_subscription.conf didn't make any difference, I think it proves that it's not used. | 19:54 |
Thaodan | I noticed that including ril_subscription.conf for dual sim also bugs the binder adaptation. | 21:10 |
Thaodan | So it at least makes the plugin unhappy | 21:10 |
mal | oh | 21:13 |
T42 | <slavamon> `ril_subscription.conf` is for `ofono-ril-plugin` | 21:34 |
T42 | <slavamon> `binder.conf` is for `ofono-binder-plugin` | 21:34 |
Thaodan | ok | 21:36 |
T42 | <cryptodas> Hi everyone! | 22:42 |
T42 | <cryptodas> I'm trying to port SailfishOS (4.4.0.58) to HTC U11 (codenamed ocn). I took unofficial LineageOS 17.1 as base and finally got rootfs built without errors. I flashed hybris-boot.img and rootfs but the device reboots immediately after showing boot logo. selinux is already set to be permissive. | 22:42 |
T42 | <cryptodas> I searched the chat history for similar issues and did the following: | 22:42 |
T42 | <cryptodas> 1) checked kernel cmdline (via `/proc/cmdline`) when booted to Android — it doesn't contain skip_initramfs; | 22:42 |
T42 | <cryptodas> 2) looked at resulting cmdline in boot.img from lineage build: it differs from mine in `buildvariant=eng`, so I tried adding this param to avoid dm-verity checks — still no success; | 22:42 |
T42 | <cryptodas> 3) combined lineage kernel with sailfish ramdisk and flashed resulting image — the device is stuck on boot logo (sometimes with visual artifacts) for 90 seconds, than on black screen for 30 seconds and finally reboots; | 22:42 |
T42 | <cryptodas> 4) combined sailfish kernel with lineage ramdisk — in this case the device reboots immediately just as with normal hybris-boot.img. | 22:42 |
T42 | <cryptodas> Any help would be highly appreciated | 22:42 |
T42 | <cryptodas> /dev | 22:44 |
T42 | <cryptodas> Hi everyone! | 22:46 |
T42 | <cryptodas> I'm trying to port SailfishOS (4.4.0.58) to HTC U11 (codenamed ocn). I took unofficial LineageOS 17.1 as base and finally got rootfs built without errors. I flashed hybris-boot.img and rootfs but the device reboots immediately after showing boot logo. selinux is already set to be permissive. | 22:46 |
T42 | <cryptodas> I searched the chat history for similar issues and did the following: | 22:46 |
T42 | <cryptodas> 1) checked kernel cmdline (via proc/cmdline) when booted to Android — it doesn't contain skip_initramfs; | 22:46 |
T42 | <cryptodas> 2) looked at resulting cmdline in boot.img from lineage build: it differs from mine in `buildvariant=eng`, so I tried adding this param to avoid dm-verity checks — still no success; | 22:46 |
T42 | <cryptodas> 3) combined lineage kernel with sailfish ramdisk and flashed resulting image — the device is stuck on boot logo (sometimes with visual artifacts) for 90 seconds, than on black screen for 30 seconds and finally reboots; | 22:46 |
T42 | <cryptodas> 4) combined sailfish kernel with lineage ramdisk — in this case the device reboots immediately just as with normal hybris-boot.img. | 22:46 |
T42 | <cryptodas> Any help would be highly appreciated! | 22:46 |
Thaodan | I'd try to get telnet working and then get logs. | 22:47 |
Thaodan | Enabling persistant logging also helps | 22:47 |
T42 | <cryptodas> Hi everyone! | 22:47 |
T42 | <cryptodas> I'm trying to port SailfishOS (`4.4.0.58`) to HTC U11 (codenamed ocn). I took unofficial LineageOS 17.1 as base and finally got rootfs built without errors. I flashed hybris-boot.img and rootfs but the device reboots immediately after showing boot logo. selinux is already set to be permissive. | 22:47 |
T42 | <cryptodas> I searched the chat history for similar issues and did the following: | 22:47 |
T42 | <cryptodas> 1) checked kernel cmdline (via `/proc/cmdline`) when booted to Android — it doesn't contain skip_initramfs; | 22:47 |
T42 | <cryptodas> 2) looked at resulting cmdline in boot.img from lineage build: it differs from mine in `buildvariant=eng`, so I tried adding this param to avoid dm-verity checks — still no success; | 22:47 |
T42 | <cryptodas> 3) combined lineage kernel with sailfish ramdisk and flashed resulting image — the device is stuck on boot logo (sometimes with visual artifacts) for 90 seconds, than on black screen for 30 seconds and finally reboots; | 22:47 |
T42 | <cryptodas> 4) combined sailfish kernel with lineage ramdisk — in this case the device reboots immediately just as with normal hybris-boot.img. | 22:47 |
T42 | <cryptodas> Any help would be highly appreciated! | 22:47 |
T42 | <elros34> First thing to check is host dmesg | 22:52 |
T42 | <elros34> " the device is stuck on boot logo (sometimes with visual artifacts) for 90 seconds" doesn't tell much without host dmesg. It should tell you whether it tires to boot android/sfos/or some other mode | 22:58 |
T42 | <cryptodas> Oh, forgot to mention: when trying to boot the device is not visible in running `dmesg -w` (also tried `while : ; do lsusb -v 2>/dev/null | grep -Ee 'iSerial +[0-9]+ +[^ ]' ; done | uniq` from halium docs). And I have empty `/sys/fs/pstore/` in recovery (I guess because it's not possible to reboot straight to recovery). | 23:00 |
T42 | <cryptodas> | 23:00 |
T42 | <cryptodas> Gonna check dmesg when booting with lineage kernel | 23:00 |
T42 | <cryptodas> The last thing I see is "USB disconnect" message when on `fastboot reboot` | 23:04 |
T42 | <cryptodas> The last thing I see is "USB disconnect" message on `fastboot reboot` (edited) | 23:04 |
T42 | <elros34> is that with lineage kernel image? | 23:06 |
T42 | <cryptodas> Yes, with lineage kernel and hybris ramdisk | 23:07 |
T42 | <elros34> strange that it change something on screen but doesn't show any connection on usb | 23:08 |
T42 | <cryptodas> When booting with normal lineage image I see something like this: | 23:11 |
T42 | <cryptodas> ``` | 23:11 |
T42 | <cryptodas> [15233.944877] usb 1-9: new high-speed USB device number 41 using xhci_hcd | 23:11 |
T42 | <cryptodas> [15234.094471] usb 1-9: New USB device found, idVendor=0bb4, idProduct=0c81, bcdDevice= 4.04 | 23:11 |
T42 | <cryptodas> [15234.094486] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3 | 23:11 |
T42 | <cryptodas> [15234.094491] usb 1-9: Product: HTC U11 | 23:11 |
T42 | <cryptodas> [15234.094495] usb 1-9: Manufacturer: HTC | 23:11 |
T42 | <cryptodas> [15234.094499] usb 1-9: SerialNumber: FA79B1800083``` | 23:11 |
T42 | <cryptodas> | 23:11 |
T42 | <cryptodas> | 23:11 |
T42 | <cryptodas> With hybris ramdisk it doesn't change much on screen, just HTC logo gets sort of smashed | 23:11 |
T42 | <elros34> are you sure that you recreate abootimg correctly? | 23:12 |
T42 | <cryptodas> I tried the same pack steps and params with lineage image (so I unpacked and packed it without changing file) and it booted to android | 23:14 |
T42 | <elros34> u add some sleep here: https://github.com/mer-hybris/hybris-boot/blob/master/init-script#L343 then make hybris-hal. This may give idea whether hybris scripts is started | 23:16 |
T42 | <cryptodas> I added 13 seconds and the device has been showing boot logo for exactly 103 s | 23:31 |
T42 | <elros34> with sailfish or android kernel? | 23:32 |
T42 | <cryptodas> Andoid. With sailfish kernel it reboots immediately | 23:33 |
T42 | <elros34> ok so looks like android kernel start iniramfs but your defconfig changes makes it unbootable | 23:34 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!