Once again, Google has chimed in on the issue (60058), officially marking the issue as fixed (internally anyway). They’re promising all will be made well in the next major Android release for the Nexus 5 (Android L), but only as it relates to the Nexus 5. Devices like the Moto G or Samsung Galaxy S5 will still require an update from their respective OEMs to fix the problem, wherever it may arise.
The good news is we’re expecting Android L to officially roll out later this month, so it shouldn’t be much longer. Special shout out to the guy on Google Issue Tracker who tried to get pry a solid release date “for the next major Android release” from Google. Can’t blame you for trying.