| mal | are those config files etc correct, check also journal log for any errors | 00:00 |
|---|---|---|
| mal | do you have correct conf file defined inside /etc/sysconfig/bluetooth-rfkill-event-hciattach | 00:02 |
| T42 | <edp_17> That file only has 1 line: CONFIGFILE="-c /etc/firmware/bcm4330b1.conf" | 00:03 |
| T42 | <edp_17> However I think the 'patchram=/system/bin/bcm4330B1.hcd' in /etc/firmware/bcm4330b1.conf is wrong. | 00:04 |
| T42 | <edp_17> That should be patchram =1 and the '/system/bin/bcm4330B1.hcd' should be defined somehow else like the '/dev/ttySAC0' which is set as 'uart_dev = /dev/ttySAC0' in the .conf file. | 00:05 |
| mal | you should be able to figure out how to fix that, there aren't that many options in there | 00:05 |
| mal | you can also check the sources https://github.com/mer-hybris/bluetooth-rfkill-event/tree/master/bluetooth-rfkill-event | 00:06 |
| T42 | <edp_17> I have found and tried to find out the parameters in the config from here: https://github.com/fredldotme/brcm-patchram-plus/blob/master/brcm_patchram_plus.c | 00:07 |
| T42 | <edp_17> But your one looks better. 😄 | 00:07 |
| T42 | <edp_17> Yep, as I though the /system/bin/bcm4330B1.hcd' should be defined as fw_patch. | 00:08 |
| mal | hcd should be just a symlink to the correct firmware so the loaded finds it | 00:13 |
| mal | like here https://github.com/r0kk3rz/droid-config-scorpion_windy/blob/master/sparse/etc/firmware/BCM4350C0.hcd | 00:13 |
| mal | which was an example in fq | 00:13 |
| mal | *faq | 00:13 |
| mal | you should really focus and check all that is written in faq | 00:13 |
| T42 | <edp_17> Yes I have that symlink. | 00:13 |
| mal | is the symlink correct? | 00:14 |
| T42 | <edp_17> I have a file bcm43xx.hcd in /etc/firmware that points to /system/bin/bcm4330B1.hcd | 00:15 |
| T42 | <edp_17> The faq is confusing by the way. It is hard to understand when I should use the actual file name (like bcm4330b1) and when the bcm43xx. | 00:18 |
| mal | well if you would have checked the sources like I said you would see that you can tell it the file to use https://github.com/mer-hybris/bluetooth-rfkill-event/blob/master/bluetooth-rfkill-event/bluetooth_rfkill_event.c#L832 using the fw_patch setting in the config file | 00:29 |
| T42 | <edp_17> In the journal there is only 1 line when i turn on the bt in settings: "bluetooth_rfkill_event[2992]: main(bluetooth_rfkill_event.c:1228): Unknown rfkill switch 0" | 00:29 |
| T42 | <edp_17> And the bt is not turning on, only if I run the brcm_patchram_plus command manually. Probably I am doing something wrong. | 00:30 |
| mal | it really shouldn't be that difficult to get working | 00:31 |
| mal | make sure the options for the brcm_patchram_plus are correct when used via that bluetooth-rfkill-event | 00:32 |
| T42 | <edp_17> It seems I have all files, symlinks in place with the correct content. | 00:32 |
| mal | to me the symlink seemed wrong | 00:33 |
| mal | at least compared to the example | 00:33 |
| T42 | <edp_17> I have compared the command and the conf file: https://pastebin.com/mEjZaDjD | 00:34 |
| T42 | <edp_17> Now I have two symlinks in the /etc/firmware. One with name bcm43xx.hcd and another with bcm4330B1.hcd. Both are pointing to the same /system/bib/bcm4330B1.hcd | 00:35 |
| T42 | <edp_17> I have tried to use both in the config file: type_id = bcm43xx and later type_id = bcm4330B1 | 00:36 |
| T42 | <edp_17> bluetooth-rfkill-event.service restarted when I changed these but the same result. | 00:36 |
| mal | what did I tell you about the fw_patch setting | 00:45 |
| mal | you don't even need any symlink if you use that | 00:45 |
| T42 | <edp_17> I tried both. With the symlink and without the fw_patch, and with fw_patch. | 00:47 |
| T42 | <edp_17> If I have fw_patch, do I even need type_id? | 00:48 |
| mal | I also said that you need to make sure the call from bluetooth-rfkill-event is the same, you can add a print to the end of brcm_patchram_plus_cmdline in the source to print it if you can't read the options and set those correctly | 00:48 |
| mal | type_id = bcm43xx like in the example | 00:48 |
| T42 | <edp_17> I think type_id tells to the script the symlink name what it is looking for but if I use fw_patch I don't need type_it and the symlink either. | 00:49 |
| mal | type_id is only for hciattach | 00:49 |
| mal | read the sources | 00:49 |
| T42 | <edp_17> Okay, I remove it then. | 00:50 |
| mal | it's just ignored for brcm_patchram_plus | 00:50 |
| mal | this is going nowhere so I give up for tonight | 00:50 |
| mal | you have all the information you need to solve this | 00:51 |
| T42 | <edp_17> Thanks for your time. | 00:51 |
| T42 | Julie %lastname% was added by: Julie %lastname% | 06:37 |
| T42 | <蔡卡斑 %lastname%> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/VS90SO1bOh.png 更多业务请咨询： @yx9937 | 09:21 |
| T42 | 屠莫雯 %lastname% was added by: 屠莫雯 %lastname% | 11:38 |
| rinigus | hi! is it expected that SD card is mounted automatically on boot (sfos 3.2.1.20). in case of sony tama devices, with /dev/mmcblk0p1 sdcard, it doesn't happen | 19:22 |
| rinigus | ... as far as I was told by one of the users | 19:23 |
| kimmoli | wasn't it issue with sd cards named mmcblk* ? | 19:30 |
| kimmoli | or appearing with such device name? | 19:30 |
| kimmoli | add a udev rule to rename/symlink it to something that the mount thingy recognizes? (disclaimers apply) | 19:31 |
| rinigus | kimmoli: not sure. there was issue with showing it wrong in the settings (all sda/b/c/ assumed to be sdcards), but I don't remember automount issues. I wounder where is the automount script... | 19:32 |
| kimmoli | it was udev rule, but it uses now something more complicated... dont remember its name | 19:34 |
| T42 | <elros34> udisks2 package | 19:35 |
| kimmoli | thats it | 19:35 |
| kimmoli | and yes the issue was way around | 19:36 |
| rinigus | then will have to refresh my memory (grep) | 19:37 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
