While I understand what you're trying to say, I argue that there's a fundamental flaw in your analogy.
The difference between windows and android is that windows is a) (More or less) stable, b) You have options to fix problems, and c) people are *used* to having to deal with problems, so when a problem happens people arn't surprised. They just roll their eyes and grunt "Great, not again..."
With android, as an end user you are stuck with what you got. There's (generally) no such thing as modding your android device. Hell, there's an excellent chance that you won't even get point releases for your OS, *even when* you bought your device from one of the major manufacturers, so you can forget about OS fixes, driver updates, etc.
Additionally, you say that people don't complain when their desktop games have issues. That's incorrect. I was having trouble getting Fallout 3 to run stable in a Windows VM, and while researching the causes I found a shockingly number of issues, many of which required going into the games config files to change the number of simultaneous threads, changing the amount of physical memory in the machine, etc. The difference here is that if you have problems on your desktop, there is a good chance that it's *fixable*. You may need to take extreme steps, but there is usually a way to work around whatever problem you're having.
For Android? If it doesn't work, it doesn't work. End of story. All you can do is complain to the dev and hope they can fix the problem, and won't just update the app description with "This game/app won't work on device X".
As a developer, in the desktop world, if your game is having a strange graphics issue, you don't go to Microsoft. You go to the graphics chip manufacturer because of possible bugs in the driver.
If your game doesn't work on the EU version of Samsung Galaxy S4, what do you do? Complain to samsung? Dig through spec sheets to find out what graphics chip samsung happened to use for that particular SKU, and then hope beyond hope you can even talk to chip manufacturer for help, assuming that Samsung didn't make proprietary tweaks to the base driver code, or possible something even more esoteric?
As long as you stick with major manufacturers, and use a toolkit like Unity, then the likelyhood of this happening is pretty remote. But I've already learned the hard way that using a generic android device from a non-major manufacturer just takes you into a world of pain.