On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo <kvalo@xxxxxxxxxxxxxxxx> wrote: >> Can't be fixed in firmware, but it would be good to have confirmation >> of the hardware behavivour, and maybe some other solution is possible? >> Are you following this up within Qualcomm? > > No time to do that right now, sorry. I got several autoresponders from people on this thread from Qualcomm Taiwan. Would it be useful for us to drop off a sample of the affected product at your Taipei or Hsinchu office so that you can investigate further? Thanks Daniel