Yeah, and Motorola have their own etc.
It really isn't a big deal. Use reflection to find what works at runtime, and live with it. That's the price of the flexibility which makes the whole thing attractive in the first place.
The big problem is trying to cover all bases from the start: you won't. Attack it like an old school PC shareware dev, and respond to customer requests.
There are far larger problems with Android than this kind of thing. That things on external storage basically bypass the security model is a much bigger concern.
Re:Android Fragmentation Visualized
by gravitronic on Tuesday May 15, 2012 @09:23PM
(#3979880)
The brutal part is that generally customer requests are no better than "the bug is shitty app" or just "buggggggg". Thats where a responsive strategy sucks - reliable reports are few and far between.
The function you are talking about only returns a single directory and my users want to use both if available.