| T42 | <edp_17> Hi all! Can I get some help with BT please? | 13:26 |
|---|---|---|
| T42 | <TheVancedGamer> We could help the most we can, sure :) | 13:26 |
| T42 | <edp_17> The device uses bluez5 and BT doesn't turn on when I try. Some logs: https://paste.ubuntu.com/p/gsdJBc9CVD/ | 13:26 |
| T42 | <edp_17> Thanks @TheVancedGamer ! :) | 13:27 |
| T42 | <MaxRegnerasif> Is there a fix for kugo (Xperia x compact) sailfish x patcher? | 13:27 |
| T42 | <edp_17> I guess the parameters of brcm_patchram_plus are wrong but I have no idea what and how to fix. | 13:28 |
| T42 | <TheVancedGamer> you have CONFIG_BT enabled, right? | 13:28 |
| T42 | <MaxRegnerasif> I have used sailfish x patcher but root.img.tar | 13:29 |
| T42 | <edp_17> @TheVancedGamer : Yep, CONFIG_BT is on. | 13:29 |
| T42 | <MaxRegnerasif> And home.img.tar not found | 13:29 |
| T42 | <edp_17> @TheVancedGamer : https://paste.ubuntu.com/p/qyHQnRJ45R/ | 13:30 |
| T42 | <TheVancedGamer> and here's where my knowledge ends. :( | 13:30 |
| T42 | <TheVancedGamer> hope somebody else can help you | 13:30 |
| T42 | <MaxRegnerasif> make -i | 13:31 |
| mal | just to be sure are those paths in brcm_patchram_plus command correct? also maybe show dmesg | 13:32 |
| T42 | <MaxRegnerasif> When building using make, just use -i flag | 13:32 |
| T42 | <MaxRegnerasif> Is anyone here able to fix sailfish x patcher? | 13:33 |
| T42 | <edp_17> mal , @TheVancedGamer : The bluetooth service is failed, here is log when I try to restart : https://paste.ubuntu.com/p/6PjpMXtKyv/ | 13:34 |
| T42 | <MaxRegnerasif> Can u restart it? | 13:35 |
| mal | @edp_17 which kernel version does that device have? | 13:35 |
| T42 | <edp_17> 3.4.112 | 13:35 |
| T42 | <edp_17> dmesg : https://paste.ubuntu.com/p/dbJyvcf4Pk/ | 13:35 |
| mal | did you backport bt driver needed for bluez5? or why are you using bluez5? | 13:36 |
| T42 | <edp_17> I don't remember why I started to use bluez5. I haven't backported nothing. | 13:37 |
| mal | bluez5 needs 3.10 kernel (if I remember correctly) or backported bluetooth drivers | 13:37 |
| T42 | <MaxRegnerasif> Can anyone help me? | 13:37 |
| T42 | <edp_17> mal : Oh, okay. I'll try with bluez4 then. Thanks! | 13:37 |
| mal | @edp_17 which bluetooth chip does that device have? | 13:38 |
| T42 | <MaxRegnerasif> Thanks | 13:39 |
| T42 | <edp_17> mal : How can I check? (It's Galaxy S4 i9505) | 13:39 |
| T42 | <elros34> @MaxRegnerasif never used it but if it can't find some file then run script with bash -x command to figure out what is wrong | 13:39 |
| T42 | <edp_17> mal : Qualcomm APQ8064T Snapdragon 600 | 13:39 |
| mal | kernel defconfig probably tells which driver it uses | 13:39 |
| T42 | <MaxRegnerasif> There is sailfish x patcher | 13:39 |
| T42 | <edp_17> mal : is it? bcm4335 | 13:40 |
| T42 | <MaxRegnerasif> And I own x compact | 13:40 |
| mal | @edp_17 probably | 13:40 |
| T42 | <edp_17> I'll try to switch to bluez4 and will report. Thanks again. | 13:41 |
| mal | @edp_17 probably easiest to test woth bluez4 first, I have only seem qcom bt chips being used with backported drivers (as mentioned in faq) | 13:41 |
| T42 | <edp_17> Thanks mal! | 13:41 |
| T42 | <edp_17> Help! On OBS, I want to build droid-config-$DEVICE-bluez4 package. I've changed Project Config to : Prefer: droid-config-$DEVICE-bluez4 and changed droid-config to use bluez4. However, OBS still builds droid-config-$DEVICE-bluez5 package. What am I doing wrong? | 23:22 |
| T42 | <Mister_Magister> why do you want to build bluez4 | 23:22 |
| T42 | <Mister_Magister> it's not even supported anymore | 23:22 |
| T42 | <edp_17> Because my device uses that (kernel 3.4.0) | 23:22 |
| T42 | <edp_17> I know it is not supported but already added back to my other two devices. | 23:23 |
| T42 | <Mister_Magister> i have 3.4 and i'm using bluez5 like there's no tomorrow | 23:27 |
| T42 | <edp_17> Lucky you. | 23:27 |
| mal | @Mister_Magister you are probably using backported bt drivers | 23:28 |
| T42 | <Mister_Magister> yes i am | 23:28 |
| mal | @edp_17 do you have different submodule revision in those devices? the one in that jfltexx uses so new submodule that it has removed bluez4 support | 23:29 |
| T42 | <edp_17> Let me check | 23:30 |
| mal | 1d38d62d0223477a9fb630795a6a029eaffa6298 is the last revision of droid-hal-configs which has bluez4 stuff | 23:30 |
| T42 | <elros34> bluez5 package will be build anyway, thepoint is what do you use | 23:30 |
| T42 | <Mister_Magister> why can't he baackport bt drivers? | 23:31 |
| mal | @edp_17 ah, since you have everything from submodule in sparse it doesn't matter that bluez5 is being built as long as it is not installed | 23:32 |
| T42 | <edp_17> @elros34 : When trying to install new patterns on device, it is complaining about : "Problem: the to be installed patterns-sailfish-device-adaptation-jfltexx-1+master.20221217223848.ac1f180-1.4.1.jolla.armv7hl requires 'droid-config-jfltexx-bluez4', but this requirement cannot be provided" | 23:32 |
| mal | @Mister_Magister not sure if anyone has tried backported drivers with broadcom bt | 23:32 |
| T42 | <edp_17> mal : Oh, so I have to remove bluez5 from device first, then upgrade patterns? | 23:33 |
| T42 | <elros34> why do you want to even build droid-config-*-bluez4 instead do it excatly like for previous device you did no so long time ago: so put all to sparse and make adjustemnts in droid-config*.inc | 23:33 |
| T42 | <Mister_Magister> ah braodcom | 23:33 |
| T42 | <Mister_Magister> that explains things | 23:33 |
| mal | @edp_17 what do you mean? | 23:33 |
| T42 | <edp_17> @elros34 : I did exactly what I did for the other two devices. | 23:33 |
| T42 | <elros34> show the changes then and it will be clear | 23:34 |
| mal | https://github.com/edp17/droid-config-jfltexx | 23:34 |
| T42 | <edp_17> However on the i9100 repo, there is a droid-config-i9100-bluez4 package | 23:34 |
| T42 | <elros34> first make sure you really pushed changes and built correct branches | 23:34 |
| T42 | <elros34> it shouldn't be there | 23:34 |
| T42 | <edp_17> It is there: https://repo.sailfishos.org/obs/nemo:/testing:/hw:/samsung:/i9100/sailfishos_4.4.0.72/armv7hl/ | 23:35 |
| T42 | <edp_17> However, I might built with something else and it is only a residue. | 23:35 |
| mal | probably older submodule? | 23:35 |
| T42 | <edp_17> So, the question is : On device, should I remove bluez5 first, then upgrade patterns packages? | 23:36 |
| mal | if obsoletes are correct it should do it automatically | 23:37 |
| T42 | <elros34> this rpm is few days old | 23:38 |
| T42 | <edp_17> This is the error I am getting : https://paste.ubuntu.com/p/kyWXnVVF68/ | 23:38 |
| T42 | <edp_17> @elros34 : Yes, on that day I fixed bt on device as you recomended with that bluez4 change. | 23:39 |
| T42 | <elros34> but your commit is 1h old? | 23:40 |
| mal | @elros34 are you mixing two devices? | 23:40 |
| T42 | <elros34> or maybe I am mixing 3x devices... | 23:41 |
| T42 | <elros34> and urls | 23:41 |
| mal | @edp_17 why do you have Requires: pulseaudio-modules-bluez4 in two places | 23:42 |
| T42 | <edp_17> Could be. :D | 23:42 |
| T42 | <edp_17> mal : Hm. Typo, probably. | 23:43 |
| mal | but it seems i9100 has the same so should not be a problem | 23:44 |
| T42 | <edp_17> Yeah, I just checked and wanted to say. | 23:44 |
| mal | @edp_17 do you have too new bluetooth-rfkill-event-hciattach ? that is the bluez5 version | 23:51 |
| T42 | <edp_17> I though, okay, I build an image to see what packages will be in there, but running the mic gave me this : https://paste.ubuntu.com/p/ZCKdXZnsHr/ | 23:51 |
| T42 | <edp_17> mal : I use this bluetooth-rfkill-event-hciattach : https://github.com/edp17/bluetooth-rfkill-event/tree/jfltexx4.4 | 23:52 |
| T42 | <edp_17> Yep, it is a bluez 5 version. | 23:52 |
| mal | probably make it similar to that i9100 branch but with correct rfkill name | 23:54 |
| T42 | <edp_17> I'll try that. | 23:54 |
| T42 | <edp_17> Thanks. | 23:54 |
| mal | don't you need that broadcom-bluetooth package on that device? | 23:56 |
| T42 | <edp_17> I don't know. | 23:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!