Thursday, 2024-12-26

T42<A_T_R> how to solve this (building droid-config)01:19
T42<A_T_R> error https://pastebin.ubuntu.com/p/GbVhQ8zPx5/01:19
T42<A_T_R> log https://pastebin.ubuntu.com/p/VZjMSjhj3t/01:19
T42<Umeaman> That's an error in the spec file.01:23
T42<Umeaman> I've seen this to many time in several projects.01:23
T42<Umeaman> You can patch the spec file and try to rebuild to see if it fixes it.04:27
T42<A_T_R> which patch04:28
T42<A_T_R> where is the patch or droid-config-$device that fixed that error04:29
T42<Umeaman> You can make the patch. Use the diff command to solve the warnings and the errors.04:34
T42<A_T_R> Solve the warning means ,remove those warning lines from *.spe04:36
T42<A_T_R> Solve the warning means ,remove those warning lines from *.spec (edited)04:37
T42<Umeaman> To correct those lines YES.04:38
T42<AnotherZain> mtp & rndis seems working now, but ssh connection got stuck after accept cert/key prompt. (re @AnotherZain: Rebuild sailfish now)05:35
T42<AnotherZain> ```05:36
T42<AnotherZain> srv:~/Desktop$ nc 192.168.2.13 2205:36
T42<AnotherZain> SSH-2.0-OpenSSH_9.605:36
T42<AnotherZain> zainarbani@linuxsrv:~/Desktop$ ssh defaultuser@192.168.2.13```05:36
T42<AnotherZain> ```05:37
T42<AnotherZain> srv:~/Desktop$ nc 192.168.2.13 22```05:37
T42<AnotherZain> 05:37
T42<AnotherZain> ```05:37
T42<AnotherZain> SSH-2.0-OpenSSH_9.6```05:37
T42<AnotherZain> 05:37
T42<AnotherZain> ```05:37
T42<AnotherZain> srv:~/Desktop$ ssh defaultuser@192.168.2.13```05:37
T42<AnotherZain>  (edited)05:37
ecrn@AnotherZain: what helped with the usb-moded? the CONFIGFS_F_FS?06:37
T42<David_Telegra> Hi !09:57
T42<David_Telegra> Do you have page by device with working elements (NFC, sound ...) ?09:57
T42<David_Telegra> The NFC work on poco X3 Pro ? In Sailfish and Waydroid ?09:57
T42<David_Telegra> 09:57
T42<David_Telegra> Thanks in advance09:57
T42<A_T_R> community-adaptation is needed by droid-config-x00td-1-202412261037.aarch6410:38
T42<A_T_R>         pkgconfig(android-headers) is needed by droid-config-x00td-1-202412261037.aarch6410:38
T42<A_T_R>         ssu-kickstart-configuration is needed by droid-config-x00td-1-202412261037.aarch6410:38
T42<A_T_R> 10:38
T42<A_T_R> how to solve10:38
ecrnhalium?10:44
ecrnI am trying to build as well10:45
ecrnthis one I solved adding the halium repo to the target10:45
T42<A_T_R> hybris-17.110:45
ecrnok10:45
ecrnno idea then10:45
ecrnbut probably also misses the package providing the android-headers10:46
T42<A_T_R> ok10:47
T42<A_T_R> let me check , i might missed some things10:47
T42<elros34> did you build droid-hal?11:33
T42<A_T_R> droid-hal  failed11:35
T42<A_T_R> `./out/soong/.intermediates/art/build/apex/com.android.runtime.release/android_common_com.android.runtime.release/image.apex/lib/bionic/libdl_android.so`11:35
T42<A_T_R> in the above directory only 3 libs present (libc,libdl,libm)11:36
T42<elros34> did you finish hybris-hal without error?11:36
T42<A_T_R> yes11:36
T42<elros34> find where is libdl_nadroid.so in  out/ directory11:37
T42<elros34> it's common issue but usually porters fix it for themself and do not propose any  PR to improve code11:38
T42<A_T_R> https://pastebin.ubuntu.com/p/VQZHNpkG6F/11:40
T42<elros34> maybe use this one from obj/ dir. Check whether is striped. Is it different then the one from system/11:46
T42<A_T_R> there is no common folder present that 4 libs11:49
T42<elros34> ok but check from where you can take libdl_android.so. Honestly I do not remember what porters usually choose11:51
T42<A_T_R> ok11:53
T42<elros34> then you can either modify droid-hal-device.inc or copy libdl_android.so to common folder with libc,dl,m11:53
ecrnI also have an issue, droid-config-halium provides /system, /persist etc as symlinks11:59
ecrnand rpm installation fails because these file exists11:59
ecrnas directories, already in the filesystem11:59
ecrnbut there is no package that provides them, so it neither detects collision prior to unpacking12:00
ecrnnor it is possible to replace the package with the droid-config12:00
T42<A_T_R> manually copied libdl_android.so compiled droid--hal and droid-config ,mw,droidmedia without error12:41
T42<A_T_R> dhvd failed https://pastebin.ubuntu.com/p/JCJqR68wZ9/12:41
T42<A_T_R> `sb2 -t $VENDOR-$DEVICE-$PORT_ARCH -R -m sdk-install zypper in droid-config-$DEVICE -ofono-configs-binder` THIS solved dhvd12:43
ecrnah, ok, the /system exists only because of /system/build.prop13:24
*** Mister_Magister_ is now known as Mister_Magister14:21
*** Mister_Magister_ is now known as Mister_Magister15:09
T42<maliklbn> /system@SailfishFreenodeIRCBridgeBot16:20
T42<A_T_R> /system@SailfishFreenodeIRCBridgeBot17:12
ecrndid the bridge bot broke?17:26
deathmistno, it's the telegram people stop trying to tap on things starting with forward slash challange17:26
deathmisttelegram makes them links17:27
ecrnok17:27
rinigus@b100dian: small update on my side. working on getting lineage based on stock for nagara booting. currently can build a kernel that is not gki and boot into recovery, los or stock. los recovery is more interesting as it allows to have adb root access19:08
riniguson trying to boot los I get stuck on sony logo and can't get meaningful fail logs (once in a very while get ramoops, but not much use so far as they tend to be very small.19:10
rinigusalso, have to use dtb/dtbo directly from stock as the ones provided as copyleft don't lead to boot into recovery even19:11
rinigusso, some work still to do before we can use it as a base19:11
rinigussame issue with boot into stock if I replace with my own boot, vendor_boot, and vendor_dlkm.19:13
rinigusvbmeta is obviously disabled19:13
T42<b100dian> rinigus: that is actually great progress, if you have lineage recovery, indeed that is better than the stock one too. Too bad you don't get good logs while booting. Is it a lack of access to logcat? ramoops means reboot, but you don't have logs, is that so?19:28
rinigus@b100dian: pretty much no logs. but right now looking into kernelsu + stock and will try to see if there are some minidump data there. need just to figure out how to make adb shell a root shell with kernelsu help19:30
rinigusso, current workflow is as follows: flash boot, vendor_boot, vendor_dlkm and try to boot stock. gets stuck on sony logo for a while and then reboots. I get into bootloader as I keep pressing volUp and have cable in. from there reboot to recovery and ... not much in /sys/fs/pstore. occasional ramoops19:32
T42<b100dian> so sometimes you do have something in pstore? Interesting, maybe it is only in debug kernels?19:32
ecrnhttps://ibb.co/n6RMwyq also an option19:53
rinigusecrn: thanks, I hope that I don't need to mess with that20:13
rinigus@b100dian: can't really make any meaningful stats or conclusions so far based on pstore20:18
T42<b100dian> That is actually from https://developer.sony.com/open-source/aosp-on-xperia-open-devices/guides/access-uart-ports so.. :)20:33
ecrnyes20:37
ecrnsurprisingly microsd extenders are readily available20:38
ecrnsamsung used to do uart on usb when microusb was used20:39
ecrnsome people say now it is still available in samsungs on usb port, but in debug accessory mode20:40
T42<b100dian> so something like this https://shop-nl.blinkinlabs.com/products/microsd-to-jtag-adapter-for-esp32?variant=39859499729090 :D20:43
ecrnwould fit?20:45
T42<b100dian> well of course it sticks out, but one won't be using their phone with that attached  ;)20:46
ecrnhttps://ae01.alicdn.com/kf/HLB1hVVdOSzqK1RjSZFLq6An2XXay/Cablecc-TF-Micro-SD-TO-Micro-SD-Card-Extension-Cable-Adapter-Flexible-Extender-MicroSD-To-SDHC.jpg but soldering required20:47
xmn_ecrn: I have one of those of very similar. I ended up recreating the pine one by bending the cable and taping it at a 90° angle. I think its a must if you do lot of card swapping or testing22:21

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