Marcel Holtmann <marcel-kz+m5ild9QBg9hUCZPvPmw@xxxxxxxxxxxxxxxx> writes: > it does not make any sense. I see. And my testing todays confirms that. Sorry for the first misplaced shot, and thanks for reviewing. > Can you just try to run the latest > bluetooth-testing.git tree kernel and see if that might have fixed this > issue. I tried it, and the problem was gone. Only thing is: I cannot reproduce the problem at all anymore. Weird. Yesterday it was easily reproducible using the procedure mentioned. Which means that there must be a mitigating factor I haven't found. Could the presence of other BT devices make a difference? The initial testing was done at work where there are a large number of active BT devices nearby, while today's testing has been done at home where there aren't so many. That's the only difference I can come up with. Well, I'm satisfied as long as the problem is gone. Will do more proper testing and report back if it reappears. Thanks Bjørn -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
