I'm lost for words really - how can this basic a flaw in the way Windows 10 Mobile works have been broken for OVER A YEAR, ACROSS THREE DIFFERENT BRANCHES of the OS? Surely this would have been picked up by anyone at Microsoft actually using their OS day to day? Is it possible that so many of them are using iPhone and Android now for phone use that the basics are being overlooked, with 'mobile' as the unloved step-child in the whole Windows 10 ecosystem?
Anyway, watch the video now:
Surely this is not just me? This has been happening across ALL branches of W10M, across ALL devices, across ALL Insiders rings and for many audio-centric applications. It's broken, pure and simple, and I just cannot understand why Microsoft doesn't assign a programmer to fix this up.... Gah!
Update: apparently this video was helpful to the 'media team' inside the Windows 10 unit. Will this mean that they'll fix the issue? I live in hope....
Update 2: it seems that a few select applications do work better, those that use the old, pre-Anniversary Update multi-process background audio - not perfectly, but better than BringCast demonstrated above. The latter is using the official, new AU single process background audio though - this should be the system that works perfectly. And it's worse. Anyway, as I say, Microsoft is 'on it'.