Sunday, 2022-06-05

T42<elros34> because it's broken: mount sdcard  by cryptic UUID instead label00:03
Mister_Magisterwho's mounting by label00:04
T42<elros34> udisks, this was answer to Thaodan question00:06
Mister_Magisterlol udisks is/are retarded then00:07
ThaodanHow is using the uuid broken?00:37
ThaodanLabel isn't unique it can break if you have two devices with the same label00:38
Mister_Magisterhence i mentioned its retarded xd00:42
Mister_Magisteront only that but label could have characters that are not fit for directory00:43
T42<elros34> two devices with same label? You meant 2 sdcar00:55
T42<elros34> ds? It was fine for few release to mount using label00:55
Mister_Magister@elros34 it's okay to correct ones mistakes, so it doesn't matter that it was using label01:12
T42<Verevka86> Hi @adampigg07:14
T42<Verevka86> why are you using this?07:14
T42<Verevka86> Android11 base?07:14
T42<adampigg> Because it works, and the other doesnt, dunno why! (re @Verevka86: Android11 base?)07:40
Mister_Magister@adampigg @Verevka86 "For android 4-10 use pulseaudio-modules-droid-jb2q instead pulseaudio-modules-droid"09:46
T42<Verevka86> yes i know, just wondering09:52
T42<adampigg> Yes, but it seems not always 😂 (re @SailfishFreenodeIRCBridgeBot: <Mister_Magister>@ad...)10:16
T42<adampigg> Had erro10:16
T42<adampigg> Had error about internal data structures messed up, UT uses the jb2q version on this device10:17
Mister_Magisteri still don't know how to fix seccomp on the 3.4 kernel xd10:18
Mister_Magisteri'm not giving up on 3.4 kernel xd10:18
Mister_Magisternatural course of action will be to upgrade to mainline but mainline for snap400 is not ready yet10:20
T42<edp_17> @Mister_Magister : What device/android base?10:23
Mister_Magistermotorola moto g 2014 2nd gen titan/thea10:24
malhmm, seccomp, that sounds familiar10:33
Mister_Magisterdoesnt it xd10:49
Mister_Magisterall i've found was from @elros34 saying "for the record: I anyone with old kernel have failing tracker-extract-3 with: "Failed to load seccomp rules", extend following patch with ECANCELED check:"10:50
Mister_Magisterprobably there's some backport10:52
stoefelzThaodan: thanks for clarification10:54
T42<edp_17> @Mister_Magister : Is there a particular reason why you use 12.1? Why not a newer base like los17 ? (In there you probably won't get this problem and wouldn't need backporting stuff (or not as much as for an older base). )12:22
Mister_Magister@edp_17 i would get in 17 same problem? newer androids don't update kernel, blobs are the same13:58
T42<edp_17> Yes, true, but newer android needs some stuff from newer kernels. Therefore, if a device has a newer android custom rom, it's kernel has lots of stuff backported already. Example: the galaxy s4 has 3.4 kernel that originally  has lots of missing stuff that requires for lxc. As I've chosen los17.1 base, all necessary stuff was already in its kernel. (Had similar experience with my other port galaxy note4. )14:43
ThaodanThere's a limit to that16:38
ThaodanAny device that is using miniaudiopolicy that is not A10 or greater?16:39
T42<Gwise> Forwarded from VE: Wow this is really unbelievable I just got paid again by this platform I ignored at first .The company has really proved me wrong with my account manager I could have been a millionaire if I had trusted this company earlier It's never too late though.This is no joke. I have Tested them and I trust them ! so i actually recommend them to my friends out there , you can reached them through this link below 👇23:11
T42<Gwise> 👉👉👉👉✍✍✍✍23:11
T42<cryptodas> Ah, here I go again. Trying hybris-boot on HTC One M8 I don't have telnet. Here is my init.log:23:58
T42<cryptodas> I understand that I don't have usb0 interface, only rmnet_usb0, but got no idea what to do. It's likely that something is missing in kernel config (or something is odd). The kernel is old enough that there are no CONFIG_USB_CONFIGFS_F_GSI or CONFIG_USB_CONFIGFS_RNDIS options.23:58
T42<cryptodas> Here is my kernel config:

Generated by 2.17.1 by Marius Gedminas - find it at!