| T42 | <Mister_Magister> @b100dian insteado of porting sake, have you tried using it daily? how does it perform? how's camera quality | 07:08 |
|---|---|---|
| T42 | <Mister_Magister> | 07:08 |
| T42 | <Mister_Magister> my 5z gets just worse and worse and i think i will soon have to switch to sake | 07:08 |
| Mister_Magister | awshit i didn't know multiline is split into many messages, my bad | 07:08 |
| T42 | <b100dian> A little bit yes. This is how I discovered wifi power drain, video decoding actually stops after a very short time and I think some keyboard vibrations are missed when typing | 07:25 |
| T42 | <b100dian> Re: camera. Seems alright but the Camera1 API hinders its rendition as defaults are highly oversharped. Using it from waydroid OpenCamera you can turn off sharpening and is pribably as good as stock, but I have a hunch that OIS might be missing | 07:27 |
| T42 | <b100dian> This is why after I release a new image I plan to join the Camera2 API effort when mal has something to share too:) | 07:28 |
| T42 | <Usman> SAILFISH OS FOR XIAOMI A3 ....? | 15:40 |
| T42 | <Mister_Magister> don't spam caps | 15:50 |
| T42 | <Mister_Magister> hmm thank (re @b100dian: A little bit yes. Th...) | 15:51 |
| T42 | <Mister_Magister> my 5z gets worse and worse and i'm afraid i will have to switch soon | 15:51 |
| T42 | <Papoucifle> Hello ! I couldn't flash my image on Moto Z Play (addison) because I had an error "signal 7" on my recovery. It seemed to be caused by the lack of tar.bz2 support on the recovery. So I tried this solution to flash "manually" : | 16:47 |
| T42 | <Papoucifle> adb shell; su; mkdir -p /data/.stowaways/sailfishos; tar --numeric-owner -xvf /sdcard/sailfish*bz2 -C /data/.stowaways/sailfishos; exit; exit; adb reboot bootloader; fastboot flash boot hybris-boot.img; "Start" <power button> | 16:47 |
| T42 | <Papoucifle> | 16:47 |
| T42 | <Papoucifle> (found on this chat) | 16:47 |
| T42 | <Papoucifle> | 16:47 |
| T42 | <Papoucifle> But now my phone is stuck on the "your device has been unlocked" screen. Does anyone has an idea of what could cause that ? | 16:47 |
| T42 | <elros34> you must check whether you see any sign of sailfish in your host dmesg. See hadk pdf telnet and hadk-hot | 17:27 |
| T42 | <Papoucifle> Unfortunately I don't have any sign of sailfish or telnet on my host. Dmesg only tells me that my device disconnected, and lsusb tells me the same | 17:33 |
| T42 | <elros34> fastboot flash hybris-boot.img, run dmesg -w and connect device. The watch carefully how long it takes to poweroff /reboot and show that dmesg. Did you compare kernel changes from old port? Did you upload your kernel changes already? | 17:37 |
| T42 | <Papoucifle> After flashing, it almost instantaneously shows "USB disconnect" on dmesg, and then it never comes back. I tried to compare my kernel changes with the old port, but I don't know what to look for. I actually only modified the "addison_defconfig" file, and all other differences are the ones made by the Lineage OS team throughout the years. I uploaded the kernel here : https://tinyurl.com/56wzsz2v | 17:59 |
| T42 | <elros34> I am not sure if this is still issue but do you have cpio installed in HABUILD? | 18:31 |
| T42 | <elros34> so there is not any connect info in host dmesg with first boot after flashing kernel? | 18:33 |
| T42 | <elros34> ah ofcourse your device have commit which you must revert: "tty: move tty_port workqueue to be a kthread": https://github.com/theorime/android_kernel_motorola_addison/commits/hybris-18.1/drivers/tty | 18:39 |
| T42 | <Fingus> Hello dear Sailfish OS Porters. | 19:30 |
| T42 | <Fingus> | 19:30 |
| T42 | <Fingus> I want to port SailfishOS for Sony XZ1 Compact. There is already Lineage 20 (Android 13 - 20-20230506-UNOFFICIAL-lilac) installed on my Test-Device and all Hardware is working. | 19:30 |
| T42 | <Fingus> | 19:30 |
| T42 | <Fingus> So i'm unsure what Android Base to choose for the Port. The "official" Path seems to be Android 11 from Sonys AOSP: https://developer.sony.com/develop/open-devices/get-started/supported-devices-and-functionality/ | 19:30 |
| T42 | <elros34> I think lineage->hybris-20 might be still experimental. Latest known working is hybris-18. Not idea about aosp base but it will be probably same as the latest sony supported device by jolla | 19:38 |
| T42 | <Papoucifle> @elros34 ok thank you ! I reverted the the commit, but now I cannot build anymore because some variables created in this commit were used in the next commits. So I reseted my git to this commit, but now when I make hybris-boot, I have "/home/user/hadk/kernel/motorola/msm8953/scripts/mod/devicetable-offsets.c:10:2: error: unexpected token at start of statement | 20:15 |
| T42 | <Papoucifle> DEVID(usb_device_id);", event though this file did not change between both commits. | 20:15 |
| T42 | <Papoucifle> | 20:15 |
| T42 | <Papoucifle> Also, I can confirm that I have absolutely nothing in dmesg after the first boot (and the next ones). | 20:15 |
| T42 | <Papoucifle> | 20:15 |
| T42 | <Papoucifle> I did not have cpio installed on habuild, so I installed it via apt-get | 20:16 |
| T42 | <elros34> no, revert all related commits too so: https://github.com/LineageOS/android_kernel_motorola_msm8953/commits/lineage-18.1/drivers/tty from 'msm_serial_hs: make the Bluetooth tty thread RT ' to 'tty: move tty_port workqueue to be a kthread '. BTW you should fork kernel instead uploading whole with different name to make it even more misleading | 20:21 |
| T42 | <elros34> maybe without: "Make msm_serial_hs RT to improve bluetooth performance " but you will see | 20:24 |
| T42 | <Papoucifle> Ok thank you ! I'm going to try that today or tomorrow. Sorry for the name, I realized just today that I misnamed it. I'm changing it right now from a fork to clean things up. | 21:04 |
| T42 | <elros34> not a big deal | 21:06 |
| T42 | <elros34> you can flash only kernel to test whether it works instead whole image | 21:07 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!