Wednesday, 2019-09-04

Qiangong2[m]If the recovery fstab for a new device already uses mmcblk0pX, what do I set up for the fixup-mountpoints?02:02
Qiangong2[m]Do I even need to edit it?02:03
Qiangong2[m]Or is it fine?02:05
malQiangong2[m]: usually it doesn't find the recovery fstab during build so you just need to check which one it finds04:50
Qiangong2[m]mal: So how would I configure fixup-mountpoints? Would I need to change block/bootdevice to block/mmcblk0pX05:13
malthat is what it's supposed to do, you need to check which paths it uses in fstab and then find the real device nodes from device05:23
Qiangong2[m]The fstab uses /dev/block/mmcblk0pX already05:27
Qiangong2[m]My device doesn't have by-name linking05:28
T42<elros34> then just add your device here
T42<adampigg> does pulseaudio-modules-droid-hidl replace audioflingerglue -and- pulseaudio-modules-droid-glue?06:13
T42<adampigg> jusa ^^06:13
jusa@adampigg: For Android >= 806:27
T42<adampigg> jusa, yes, but does it replace both parts?06:27
jusa@adampigg: and yes, for ril only pulseaudio-modules-droid-hidl is needed, if other components require access to audioflinger service then you'll need to run audioflingerglue in addition, but no need for pulseaudio-modules-droid-glue06:28
T42<adampigg> thx, what other components typically require access to audioflinger?06:29
jusa@adampigg: but I already have pending PR for pulseaudio-modules-droid-hidl where I separate the helper (connecting to hwbinder or binder) and pulseaudio module, so then you could use only the helper where audioflinger is needed (much simpler build than audioflingerglue)06:29
jusa@adampigg: I think only camera on some devices has needed access to audioflinger06:30
T42<adampigg> ok,good info06:30
T42Maria %lastname% was added by: Maria %lastname%07:06
ghosalmartinr0kk3rz, morning, do you remember the config_vt fix in the kernel? it was reverting some thread work google did09:44
r0kk3rzthat was the gist yeah10:21
r0kk3rzin the logs somewhere10:21
ghosalmartinr0kk3rz, am digging :P10:25
r0kk3rzthere should be a fixed kernel on github somewhere10:28
r0kk3rzi think10:28
ghosalmartinr0kk3rz, it was this thanks :D10:43
ghosalmartinam having anotehr go ar marlin port10:43
ghosalmartinbullhead has just annoyed me far too much10:43
ghosalmartin!seen osum4est10:45
merbotghosalmartin: osum4est was last seen in #sailfishos-porters 17 weeks, 4 days, 12 hours, 28 minutes, and 59 seconds ago: <osum4est> mal, tried setting that as well, didn't seem to help10:45
riniguskimmoli: any progress with testing?10:52
riniguskimmoli: for me, it seems to work now without any extra difficulties.10:52
r0kk3rzghosalmartin: yeah that looks like it11:55
r0kk3rzi wonder what they were trying to fix with that patch11:56
electro575Just for information, who have a device who works properly for SIM detection and all service around with sailfishos ? Without sony taking into account12:11
r0kk3rzwe have many12:11
r0kk3rzthey probably wont help you though12:12
electro575okey, so what can be added to my defconfig about htc one m8 devices ? i don't have my file here but just for as example12:13
r0kk3rzwhat do you mean?12:14
r0kk3rzits the kernel config, theres a zillion options...12:14
electro575zillion ?12:14
r0kk3rzyou need to figure out what changes you need in there12:15
electro575yes i know, just one second, i find the last project12:15
r0kk3rzif any12:15
electro575okey, but sometimes it's an hardware problem12:15
electro575because we don't have the good firmware to talk with hardware12:15
r0kk3rzindeed, it can be complicated, this is what device porting is about12:16
r0kk3rzwhat are you trying to get at?12:16
electro575this repo -> msm897412:17
electro575i have lineageOS12:17
electro575i'm looking for the ofono : RIL problem : no such file12:20
electro575for SIM detection12:20
electro575but if you add configuration and remove configuration of the kernel, the files whose added are removed or not ?12:21
r0kk3rzwhich files?12:21
electro575kernel file12:22
electro575.o , ...12:22
r0kk3rzyou need to figure out which file it needs, and where it comes from12:22
r0kk3rzmaybe it comes from kernel, maybe it comes from somewhere else12:22
electro575yes, but why the RIL problem is alaways this ? i'm on lineageOS 15.1 with libhybris 15.112:23
electro575and ofono-blinder12:23
r0kk3rzbecause you havent fixed it12:24
electro575my smartphone is 32 bit12:24
electro575i have reset repo for ofono-blinder12:24
electro575fix it ? in my kernelconfig ?12:25
Mister_Magisterr0kk3rz: seeā€¦12:25
electro575i will see with dbus the problem12:25
r0kk3rzi have no idea what you're talking about12:25
electro575but the link FAQ not work for this problem12:26
electro575i will more search but i just want similar project for a defconfig if it exist12:26
electro575i will more search, i have no many time ^^12:27
electro575sorry for my flood12:28
electro575but i have port my galaxy note II t0lte, and i have sometimes problem with SIM detection12:28
electro575and the phone is low speed to load the OS12:28
r0kk3rzrandomly changing the kernel config is not advised12:29
electro575the battery drain is more than other OS, but it's samsung12:29
electro575can i reset the output of my kenel compilation ?12:29
r0kk3rzits a git repo, it keeps track of changes12:30
electro575i will test, okey12:31
s31mhi there, I am looking for Sailfish on Shiftphones13:26
T42PacoLanciano was added by: PacoLanciano14:07
Qiangong2[m]For my spreadtrum device, it has a bunch of patches required to build cm-13 successfully. Is it safe to apply them? Or is there a reason I shouldn't?17:39
r0kk3rzQiangong2[m]: you might need to apply them to the hybris tree too18:06
Qiangong2[m]Okay, so they won't interfere with the final build?18:06
TheKitdepends on what is patched exactly, but hybris changes to most components are not that large, so they shouldn't18:07
Qiangong2[m]Okay, thanks18:07
s31mis there a list of devices that are compatible with Sailfish ?18:13
Mister_Magisters31m: not all but most
Qiangong2[m]My device tree is here: However, I am stuck at breakfast. It is saying it can't find the config makefile18:40
Qiangong2[m]It shows up in the lunch menu, but same issue18:40
Qiangong2[m]build/core/ *** Can not locate config makefile for product "lineage_logan2g".  Stop.18:41
Qiangong2[m]Device logan2g not found.18:41
piggzmal: sledges: is this a viable patch to dhd?
ghosalmartinhas anyone managed to roll a boot and recovery image together yet?19:54
ghosalmartinturns out marlin needs twrp-3.2.2-0-marlin.img20:22
ghosalmartinthe newest version fails to mount vendor and system for some strange reason20:22
malpiggz: hmm, so that device doesn't have a real /vendor partition or what?20:34
piggzmal: it does, but as part of the hal buiild, i want to modify some stuff from the cendor partition20:35
malhmm, ok20:36
maljust hoping that won't cause issues on any devices, is that libexec vendor in search path?20:36
piggzmal: well, actually, its broke DHI for me so far20:37
malpiggz: search path would need modifying anyway if you want to add such a thing20:38
malpiggz: is /vendor priority over libexec system?20:38
piggzmal: in what context?20:39
malpiggz: I mean just if there is alternative ways to achieve the same outcome20:39
piggzmal: well, i was wondering if i can just add the 2 libs i want to install to detrious package?20:40
malhmm, that probably won't work easily, maybe we could think of that libexec vendor tomorrow, it's a bit late20:42
piggz_mal: what have i broken here :/
piggz_dhi failing21:13
piggz_problems start around line 21321:17
piggz_2183 even21:18
malpiggz_: which libs did you add to the device?21:38
malpiggz_: line 2175 is the first error, no idea why servicemanager fails21:46

Generated by 2.17.1 by Marius Gedminas - find it at!