3 ms·
What was the bug you submitted? The thing about AOSP is exactly what JBQ said: It's meant for reports about open source parts of Android, not reports about Sam
by DannyBee 13y ago
What was the bug you submitted?
The thing about AOSP is exactly what JBQ said: It's meant for reports about open source parts of Android, not reports about Samsung's skin on top of it, etc.
Most of the bugs submitted are not AOSP bugs (I know it's hard to believe, but i've done triage on it). They are bugs in some vendor's patches or changes to AOSP, which, for the most part, Google can do nothing about.
It would be worse if these bugs were left open, giving people the false hope that Google can solve their problem, or that the bug got to the right place.
If this bug/feature is somewhere in the AOSP code, great, reopen the bug and point it out.
- jmngomes 13y agoI submitted a bug stating that the OS' facilities for managing audio (i.e. AudioManager et al) weren't working according to the spec/docs, some classes would report an incorrect volume during a call. I only tested it on a Samsung phone, I didn't bother testing with other brands because breaking on Samsung would be bad enough for my/any Android app. I understand what you say, but if it was the other way around my reply would have been something in the lines of "1) please confirm it by testing on another phone brand; 2) if it's specific to Samsung, here's the link to file the bug"
- DannyBee 13y ago1. Sure, but it's entirely that brand's drivers would also not have been in AOSP. 2. You must realize there are hundreds of devices, and manufacturers change their support links all the time :(