Sunday, 2021-05-16

T42<Balraj %lastname%> did anyone patch this into kernel https://github.com/ubports/android_kernel_google_msm/pull/5/files as explained in the documentation https://docs.halium.org/en/latest/porting/build-sources.html03:34
T42<Balraj %lastname%> I got this error while executing mka systemimage05:29
T42<A_T_R> Balraj ask here @halium05:36
T42<A_T_R> dcd - commits https://github.com/SailfishOS-sdm660/droid-config-X00TD/commits/hybris-17.106:02
T42<A_T_R> BC mk -  BOARD_KERNEL_CMDLINE += androidboot.selinux=permissive audit=006:02
T42<A_T_R> kernel/asus/sdm660/arch/arm64/configs/X00TD_defconfig - https://pastebin.ubuntu.com/p/GmZzTq88TW/06:02
T42<A_T_R> after added commits to dcd it is still stuck at bootlogo and no telnet connection06:02
rinigusjust stumbled on https://github.com/sailfishos-sony-tama/main/issues/145 . in short, SFOS 4.1.0.23 requests in almost endless loop fingerprint identification. which prevents CPU sleep as well as leads to identification failure when it is actually needed06:59
rinigusmal or someone else knowing the subject - any earlier reports on it? ^07:00
T42<elros34> Balraj edp17 had issue with vfs_fstat on one or more old samsung devices: https://github.com/edp1707:00
spiiroinrinigus: personally I've never seen behavior like that... but it looks like it could be fpwakeup related -> something along the line: mce - fpd (in general/community version?) - android fp service. commented at issue09:20
T42<ruspartisan> I want to use pinephone image as a base for my port for qemu-arm, there are several version:09:24
T42<ruspartisan> "Which image do you want to flash?09:24
T42<ruspartisan> 1) PinePhone 1.0 (Development) device09:24
T42<ruspartisan> 2) PinePhone 1.1 (Brave Heart) or 1.2 (Community Editions) device09:24
T42<ruspartisan> 3) PineTab device09:24
T42<ruspartisan> 4) PineTab Dev device09:24
T42<ruspartisan> 5) Dont Be Evil devkit"09:24
T42<ruspartisan> which one should I use? devkit?09:24
rinigusspiiroin: thank you very much! let's continue discussion under the issue, I am trying to process it...09:25
T42<elros34> @ruspartisan If you are not aware there is application sdk with i486 emulator. What is the point  for qemu arm image?11:34
T42<ruspartisan> @elros34 [@ruspartisan If you are not aware there is app …], I know there's a x86 emulator for virtualbox, I even ported it to QEMU by hacking in another kernel. I want to use raspberrypi with kvm to run sailfishos in qemu (don't ask me why, I can't really answer)11:36
T42<b100dian> Some of the best results are for this exact reason:)12:27
T42<A_T_R> host-dmesg13:51
T42<A_T_R> [  206.233907] usb 1-4: SerialNumber: Mer Debug telnet on port 2323 on rndis0 192.168.2.15 - also running udhcpd13:51
T42<A_T_R> ```telnet 192.168.2.15 2323``` is not connectin13:51
T42<A_T_R> cconnecting*13:52
T42<A_T_R> how to flash sfos (hybris-17.1 )14:35
T42<A_T_R> flash lineae-17.1 vendor to vendor partition14:35
T42<A_T_R> flash sailfishos_image zip ?14:35
T42<A_T_R> right ?14:35
malyou install the sailfish zip from recovery14:43
malyou need to install whole lineage first before sailfish14:43
T42<A_T_R> actually i couldn't install sailfish from recovery ...i am extracting *.tar.bz2 and flashing hybris-boot.img14:45
malok14:45
malsometimes twrp has issues because tar uses so much memory14:45
T42<A_T_R> ```cp /sdcard/Download/busybox /tmp/ && chmod 0777 /tmp/busybox && mkdir -p /data/.stowaways/sailfishos/ && /tmp/busybox tar --numeric-owner -xvjf /sdcard/*.tar.bz2 -C /data/.stowaways/sailfishos/```14:46
T42<A_T_R> this how i am flashing now14:46
T42<A_T_R> https://github.com/SailfishOS-sdm660/droid-config-X00TD/commits/hybris-17.114:46
T42<A_T_R> can you took at from commits from "add ld.config.29.txt"14:47
T42<A_T_R> after adding those commits ,it still stuck at logo and no telnet connection14:47
malI don't see the selinux configuration files in that repo15:03
malah, wrong branch15:03
T42<A_T_R> Ah ok15:03
maldid you try manually setting ip for the usb interface?15:04
T42<A_T_R> yeah but no use15:05
T42<A_T_R> sudo ifconfig enp2s0 192.168.2.1315:05
T42<A_T_R> then telnet 192.168.2.13 232315:05
T42<A_T_R> But in my case usb0 doesn't show the IP address15:06
malthat's not how you use it15:07
malthe device is still 192.168.2.15, that .13 is the ip you set to your computer15:07
malwhich means you use ifconfig to set the ip to for example that 192.168.2.13 but and then use telnet 192.168.2.15 232315:12
T42<A_T_R> No15:45
T42<A_T_R> Set IP 192.168.2.13 and telnet 192.168.2.1315:45
T42<A_T_R> 2323 port15:46
maldid you read what I wrote, you are setting the ip address of the host interface not the device, the phone ip is still 192.168.2.1516:14
T42<A_T_R> Then how to  it correctly ?16:21
mal@A_T_R you need to understand the difference, .15 is the ip of the phone, .13 is the ip of your computer usb interface16:57
maljust do what I say16:57
T42<A_T_R> Okk17:08

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!