Everyone who complained on this bug paid for Android as a commercial product.
I may be a master Linux debugger, but I'm not about to debug every little appliance/automobile issue I have because there's a bug in it's embedded Linux subsystem.
I never thought I'd see the day when people would use OSS as a defense for a commercial product not getting fixed. Especially when I suspect that the component involved isn't actually open source.
You most definitely didn't buy Android from Google. The OEM bought Android from Google. Then your carrier bought the phone with Android from that OEM. Then you bought the phone from the carrier.
By the time it gets to this point; what's in AOSP and what's on your handset are only very distantly related.
On the other hand, if you are running AOSP on your phone, then you did that all by yourself after cloning it from their public git repository.
Remember, Google is not to blame for bugs in Android. Your carrier is. (And most of the time, they're the ones who break it. This case is probably something that can be solved by Google, but apparently the OEMs and carriers are not prioritizing it above adding NASCAR apps and changing all the colors. And that is who is getting your money.)
Everyone who complained on this bug paid for Android as a commercial product.
I may be a master Linux debugger, but I'm not about to debug every little appliance/automobile issue I have because there's a bug in it's embedded Linux subsystem.
I never thought I'd see the day when people would use OSS as a defense for a commercial product not getting fixed. Especially when I suspect that the component involved isn't actually open source.