Saturday, 2022-05-07

T42<Mister_Magister> @adampigg isn't this what mdm is about?01:10
*** amccarthy_ is now known as amccarthy07:03
T42<elros34> @edp_17 so which bluez do you use on i9100? I can see droid-config-*-bluez5 only in 4.3.0 repo, bluetooth-rfkill-event-hciattach which requires bluez5 instead bluetooth-rfkill-event (bluez4) and droid-config-*-bluez4 and 5 in 4.4.0 repo12:04
T42<edp_17> @elrso22:33
T42<edp_17> @elros34 : The device uses bluez4. On 4.4 it built bluez5 first then I changed the droid-config to build bluez4. I've got too surprised when saw the bluez5 package in there.22:34
T42<edp_17> I think there is a problem with droid config on my local repo but I don't know what. I went back to the version that I used for building 4.3 because that has bluez4 reinstated.22:36
T42<elros34> so have you tried to change bluetooth-rfkill-event-hciattach to bluetooth-rfkill-event?22:41
T42<edp_17> Not yet. Or I don't remember. Give me a second I am checking my notes about the S2.22:43
T42<elros34> just change package on obs22:44
T42<edp_17> Well, in my notes for the S2 is about only bluetooth-rfkill-event. There is no mention of bluetooth-rfkill-event-hciattach. So, I probably mixed up something or used an old repo that wasn't complete on OBS.22:45
T42<edp_17> I've created bluetooth-rfkill-event package. I am removing bluetooth-rfkill-event-hciattach.22:49
T42<edp_17> @elros34 : Thanks!! This was the problem. Now, the mic has started to download packages. 👍22:55
T42<edp_17> I need a little help with fixup-mountpoints. On collabedit, the instruction about how to create correct map for the device is not clear to me.23:00
T42<edp_17> I got this on android:
T42<edp_17> and I defined this in fixup-mountpoints:
T42<edp_17> But this probably is not right as the device stuck on boot logo.23:02
T42<elros34> can't tell you whether this is correct because to create fixup-mountpoints first you need your device's fstab then ls -l *by-name/*23:08
T42<edp_17> Do you mean fstab from android?23:09
T42<elros34> from android or device repo, doesn't matter but that is whole point of fixup-mountpoints23:10
T42<edp_17> Okay, I am in adb shell on device (los17.1 what I'll use for the base) Where I can find fstab? In /etc ?23:12
T42<elros34> probably in / or /system or in $ANDROID_ROOT/device/$VENDOR/*/rootdir/23:14
T42<edp_17> On device I cannot find it either  in / nor /system nor /etc nor /system/etc.23:16
T42<edp_17> In local repo in $ANDROID_ROOT/device/$VENDOR/jf-common/rootdir/ there is an fstab.qcom23:17
T42<edp_17> This its content:
T42<edp_17> *is23:19
T42<elros34> so fixup looks correct23:22
T42<edp_17> Thanks for confirming.23:23
T42<edp_17> Can it be that the device code name is wrong? In fixup-mountpoints I've mentioned "jfltexx" but I might need to use "jflte" | "jfltexx". I am not sure.23:27
T42<edp_17> Is it possible to fix this on device without rebuilding packages?23:27
T42<elros34> sure but why do you think this is the issue? Do your device stuck in telnet 23?23:30
T42<edp_17> In short, yes there is telnet 2323.23:34
T42<edp_17> In a bit longer: this is the device that broke after I built the fisrt image for it. Then, I managed to install the zip on it and yes, I did have telnet. Then, I thought the fixup-mountpoints were wrong, so started experiment. Since, there is no telnet at all. Today, I've installed a new scree, so the device works again. Now I need to flash sfos again to see whether telnet still works.23:35
T42<elros34> 2323 (!=23) or no telnet at all doesn't sound like fixup issue for me23:39
T42<edp_17> So if there is only telnet 2323, that isn't a mountpoint issue.23:41
T42<edp_17> Okay, then I need to dig in logs to see what's crashing.23:42

Generated by 2.17.1 by Marius Gedminas - find it at!