Thursday, 2022-07-07

T42<Umeaman> mal: Do I still need to do the patches or do I continue to building hybris-hal droid-media?01:34
T42<Umeaman> For the hybris-18.1-update branch.01:34
T42<elros34> you need too apply hybris patches before first 'make' for >= hybris-1608:35
T42<edp_17> @elros34 : It seems the active profile is default when the headphones connected or not.10:40
T42<edp_17> pactl list - no headphones connected:
T42<edp_17> pactl list - headphones connected:
T42<edp_17> I have no idea what and how to fix this.10:40
T42<elros34> hmm 'Active Port: output-wired_headphone looks correct'10:41
T42<edp_17> Yes.10:42
T42<edp_17> Is the 'State: SUSPENDED' correct?10:44
T42<edp_17> This also looks correct "x-maemo.mode = "lineout""10:45
T42<elros34> you do not have sound at all with connected headphones? Did you tested them on same device with android? You know some devices have different physical connections than others10:46
T42<edp_17> The sound is only coming from the phone's loudspeaker not from the headphone.10:46
T42<edp_17> Weird. Now it works. 😳10:48
T42<elros34> I think 'State' depends on whether you are currently playing something. DO you have some errors in pulseuadio logs? What pulse module version do you use?10:48
T42<edp_17> No, there is no error. I have these pulse modules installed :
T42<edp_17> Can you please help with bluetooth? Based on what's in hadk-faq I don't know which section I should follow (10.2 or 10.3 or 10.4 or 10.5).11:19
T42<elros34> so now audio works correctly or randomly? I do not know what you should use for bluetooth, it's device specific. Try to figure out whether you have binder based bluetooth, maybe in device repo or lshal, not sure. 10.4 is about patches for old kernel needed for 10.3 (beware scripts are outdated). 10.5 is a about broadcom based bluetooth yo should know already quite well11:25
T42<elros34> there is a tool binder-list from libgbinder which I think should be way to go11:27
T42<edp_17> My confusion about those section is the following. This device is a qualcomm (snapdragon 600) one. It has kernel version 3.4. Originally it had android 5 (lollipop) but I am using an android 10 (los 17.1) base. This base has bluez 5 backported.11:34
T42<edp_17> So far I've tried broadcom with patchram but doesn't work at all. Even when I start patchram manually. Therefore, I think should use something else.11:35
T42<elros34> yeah why don't you check device repo, if it use broadcom chip then you will see it11:35
T42<elros34> or kernel defconfig11:35
T42<edp_17> Regarding audio. I'll play with it today, but it seems works fine now. Odd, because I already tried with this setup and didn't work. Anyway, it's fine now. :)11:36
T42<elros34> check" Active port" next time it will now work11:36
T42<edp_17> What should I see in device repo to check whether this uses a broadcom chip?11:36
T42<edp_17> I will, thanks!11:37
T42<elros34> it should be obvious when you will see it:) like config files you used to create correct settings for bluetooth-rfkill-event: or
T42<edp_17> In device tree I couldn't find anything that broadcom related. I did : grep -rnw device/ -e ".*BROAD.*"11:41
T42<elros34> better grep -i bcm or brcm11:41
T42<edp_17> Yeah, I have similar in there for this device too.11:41
T42<edp_17> Have this :
T42<elros34> so check whether you have /dev/ttyHS0, search bcm4335 <device codename> in net, it should be pretty straightforward to figure out used chip, maybe you will even find boardview or schematics:)11:44
T42<edp_17> I have /dev/ttyHS0 on device.11:45
T42<edp_17> In kernel/net I didn't find anything for bcm4335.11:47
T42<elros34> what about just bcm11:49
T42<elros34> second link in net shows my what kind of chip it use:
T42<edp_17> For bcm, I got loads of lines.11:51
T42<edp_17> e.g.: bcm.c - Broadcast Manager to filter/send (cyclic) CAN content11:52
T42<elros34> you have all kind of evidence what kind of bluetooth chip device use no need to dig in sources (defconfig is enough)11:53
T42<edp_17> Thanks for helping with this. :)11:54
T42<edp_17> So bcm* in defconfig means broadcom ?11:55
T42<elros34> most likely, didn't you have this in other samsung devices?
T42<edp_17> I have similar in the S2's Although, there is no if around that.12:01
T42<edp_17> So, as this is broadcom, then the path I started was correct. Then I don't see why this doesn't work.12:05
T42<edp_17> I am sure it will magically starts working soon after you help me. :) Just like audio routing. :D12:06
T42<elros34> so have you try binder-list/lshal already?12:11
T42<edp_17> I've tried /system/bin/lshal | grep radio Which gives me:
T42<edp_17> And here is without the grep :
T42<elros34> there is 'android.hardware.bluetooth@1.0::I*/*" but I am not sure how to interpret it. What about binder-list -d /dev/hwbinder?12:23
T42<edp_17> I don't have binder-list. I've installed binder-utils because though this was part of that but it wasn't.12:24
T42<edp_17> *thought12:25
T42<elros34> most likely libgbinder-tools12:28
T42<edp_17> binder-list -d /dev/hwbinder :
T42<edp_17> There is no bluetooth. :(13:18
T42<Umeaman> I did the patch procedure, but still ended up with this:
T42<Umeaman> What's the solution?13:21
T42<Verevka86> (re @Umeaman: What's the solution?)13:27
T42<edp_17> @Umeaman : Is this export not required for A11 (before running breakfast)? export TEMPORARY_DISABLE_PATH_RESTRICTIONS=true13:29
ThaodanFor builds using hybris-boot it is required13:33
Thaodanif you use droid-hal-img-boot based boot.img packaging it is not.13:34
T42<elros34> @edp_17 so you have all needed info, no binder based bluetooth, and broadcom driver13:34
Thaodankernel based firmware loading or userspace?13:35
T42<Umeaman> What's next?13:37
T42<elros34> @Umeaman 8GB ram? This may not finish. Did you remove out/ before start building?13:39
T42<edp_17> Thanks Thaodan.13:39
T42<edp_17> @elros34 : Thanks, I will retry the bluetooth again.13:40
ThaodanOh 8GB of RAM is to low, that sounds like pain.13:40
T42<Umeaman> Thaodan: I have built Lineage before with the same amount of memory. It takes time, yes, but it does finish.13:41
T42<Umeaman> I did that now and I still get the same result. (re @elros34: @Umeaman 8GB ram? Th...)13:46
T42<Umeaman> It's building......13:47
T42<Umeaman> So, I'm still stuck.13:50
Thaodan Umeaman13:58
Thaodan Umeaman: Does that happen on just lineage too?  (building without hybris-patches)13:58
ThaodanIf not it could be that the module is just missing because of hybris-patches.13:59
T42<edp_17> @elros34 : Based on logs, it looks like BT is turning on / off but in real only the white spot is blinking next to Bluetooth in Settings. Logs:
T42<edp_17> Interestingly, the bluetooth.service crashes14:09
T42<edp_17> Log when trying to start bluetooth.service :
T42<edp_17> Is this the problem? "bluetoothd[29988]: src/adapter.c:adapter_init() Failed to access management interface"14:13
T42<elros34> @Umeaman go to advanceddisplay directory > realize it's java android app > try to get rid if it (check what imports it: maybesomething in device repo)14:27
T42<Umeaman> I haven't built 18.1 for this phone. Only 17.1 (re @SailfishFreenodeIRCBridgeBot: <Thaodan> Umeaman: D...)15:38

Generated by 2.17.1 by Marius Gedminas - find it at!