*** Mister_Magister_ is now known as Mister_Magister | 08:07 | |
T42 | <TheVancedGamer> mal: have you managed to reproduce the WLAN issue on FP5? | 12:58 |
---|---|---|
T42 | <TheVancedGamer> no matter what I try I can't seem to reproduce it | 12:58 |
mal | @TheVancedGamer which one was it again? | 13:04 |
mal | with the updated driver or something else? | 13:04 |
T42 | <TheVancedGamer> with the updated driver, yes - the issue where device would crash upon turning on wifi | 13:08 |
mal | I haven't tried that recently since it was always happening for me if I remember correctly | 13:08 |
T42 | <TheVancedGamer> can you send me a full kernel log from the crash please? | 13:09 |
mal | I'll need to build the kernel first | 13:10 |
T42 | <edp_17> @elros34 , It still doesn't work. I've tried all sort of combination of parameters but nothing helped. What I did was, I symlinked "/system/vendor/firmware" to "etc/firmware" and now the error message saying firmware not found is gone. | 16:19 |
T42 | <edp_17> However, the device still cannot find any other BT devices and it's cannot be found either. | 16:20 |
T42 | <edp_17> In logs I am getting "Bluetooth device /org/bluez/hci0 not enabled" message, so I guess that is the issue. | 16:21 |
T42 | <elros34> but how hciattach output looks like. Does it initialize bt, say something new? | 16:27 |
T42 | <elros34> does kernel prints something when you start hciattach? | 16:28 |
T42 | <edp_17> When I start hciattach, now I see in dmesg "Bluetooth: RFCOMM socket layer initialized" "Bluetooth: RFCOMM ver 1.11" | 16:32 |
T42 | <edp_17> Also, I got an "Incorrect bdaddr" message which is gone now because I hardcoded the BT address | 16:33 |
T42 | <edp_17> I used this command when got the invalid bdaddr: "sudo /usr/sbin/hciattach ttyHS99 bcm43xx 3000000 flow sleep /data/property/persist.service.bdroid.bdaddr" | 16:34 |
T42 | <elros34> thats all? not initialization or something like | 16:34 |
T42 | <edp_17> And now I use this one: sudo /usr/sbin/hciattach ttyHS99 bcm43xx 3000000 flow sleep 50:xx:xx:xx:xx:0A | 16:34 |
T42 | <edp_17> I masked the address | 16:34 |
T42 | <edp_17> Yes, that is also there. Here the full output: https://paste.ubuntu.com/p/SP35X2vbbf/ | 16:35 |
T42 | <edp_17> BT/Scanning/Visibility turns on/off but doesn't find anything. | 16:36 |
T42 | <elros34> what you have in /system/vendor/firmware and how hciconfig looks like when rfkill is unblocked? | 16:37 |
T42 | <edp_17> /system/vendor/firmware: https://paste.ubuntu.com/p/QSdw4P9RKm/ | 16:38 |
T42 | <edp_17> rfkill + hciconfig: https://paste.ubuntu.com/p/xtxhHbsyMn/ | 16:39 |
T42 | <elros34> hciattach really use (strace) bcm4335c0.hcd? | 16:44 |
T42 | <edp_17> Let me check. | 16:44 |
T42 | <elros34> did you try bluetoothctl (and scan on) as root? | 16:46 |
T42 | <edp_17> No, I only tried scan from Settings | 16:47 |
T42 | <edp_17> strace: https://paste.ubuntu.com/p/WG8xVHK4KM/ | 16:49 |
T42 | <edp_17> There is: "read(3, "\1\24\f\0BCM4335C0\0\0\0\0", 17) = 17" | 16:49 |
T42 | <edp_17> bluetoothctl (scan) as user then root: https://paste.ubuntu.com/p/DWP3Kw65M8/ | 16:51 |
T42 | <elros34> you proabably should use -f and -s256 for strace but I don't see this firmware hcd being used | 16:52 |
T42 | <edp_17> Can I kill hciattach without the need of reboot? | 16:53 |
T42 | <edp_17> If I use kill, I cannot start until I reboot it again. | 16:53 |
T42 | <elros34> kill -9 maybe ? | 16:53 |
T42 | <elros34> bleutoothctl is interactive so it even tells you that bt is off, so enable it first | 16:54 |
T42 | <edp_17> Tried that, same result. :( | 16:54 |
T42 | <elros34> result? how you cannot start it? | 16:54 |
T42 | <edp_17> After I killed and tried to start again, I got timeout. | 16:55 |
T42 | <elros34> maybe strace it to see or just reboot | 16:56 |
FireFly | that should be "scan on", not just "scan" | 16:56 |
FireFly | (though it probably doesn't matter at this stage, since it seems there's a problem earlier in the stack) | 16:57 |
T42 | <edp_17> strace -f -s 256 : https://paste.ubuntu.com/p/29k3KwjhJj/ | 16:58 |
T42 | <edp_17> Yeah, I just reboot. Not a big deal, just slow. :) | 16:59 |
T42 | <edp_17> After this strace it stuck on the last line and had to cancel it with ctrl+c | 17:00 |
T42 | <edp_17> Now, hciattach is not even running as I cancelled the strace but I get a "Initialization timed out." when try to start it without strace. Time to reboot. | 17:01 |
T42 | <edp_17> Many thanks for your help again. I need to go now. Will come back to continue later. | 17:02 |
T42 | <elros34> don't forget about what FireFly said | 17:02 |
T42 | <edp_17> Will try that, thanks. | 17:02 |
T42 | <elros34> hmm silly idea change bcm4335c0.hcd to BCM4335C0.hcd | 17:16 |
T42 | <elros34> and for test add "-n" arg for hciattch, maybe you will not have to reboot | 17:23 |
Mister_Magister | mal: had chance to test mce changes? | 17:40 |
T42 | <edp_17> Do you mean, rename the hcd file itself? | 17:44 |
T42 | <elros34> yeah | 18:01 |
T42 | <edp_17> Okay, worth a try. | 18:39 |
rinigus | b100dian and mal : managed to get ims call hangup working - just had to fill full struct by writing it to aidl and not cut the corners. | 18:49 |
T42 | <edp_17> @elros34 : rename didn't make any difference. | 19:10 |
T42 | <elros34> hm maybe do not make symlinks just copy uppercase hcd to /etc/firmware. I think it cannot find right file. | 19:11 |
T42 | <elros34> did you use correct name its zero at the end not O | 19:14 |
T42 | <edp_17> Yes, I kept 0 (zero) at the end. Let me create a /etc/firmware and copy that .hcd file with lower & uppercase. | 21:10 |
T42 | <edp_17> @elros34 : Good news!. I had to create /etc/firmware and copy the uppercase hcd file into it. Then. Bluetooth started working. I paired with my other phone and bt speaker which plays sound from device. A ton of thanks for helping to make it happen! | 21:41 |
T42 | <edp_17> Now, I can build sfos4.6 & 5.0 for this device. | 21:42 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!