Capability-based security is ultimately just another buzzword, no more of a perfect solution than any of the others. I don't think you can call any type of security problem solved by your pet technology until it is deployed at scale in the real world and proven to work. Until you have had tens of millions of users and hundreds of thousands of developers bashing away at it for years, you just don't know if you've really solved the problem.
Android's capability-based security is good, but IMHO the more important security innovation is secure app-specific data stores. You might request more permissions than you should, and some clueless users might install it anyways, but you still can't ever get access to the data or credentials stored by the banking app, the social media app, etc.
I don't have much experience with iOS, but I expect it does something similar.
The challenge is more widely used apps that ask for permissions that make no sense to me as a developer. App developers should be able to provide a justification for each permission.
Ideally I'd like to be able to reject specific permissions, and the app should just tell me what functions are disabled... or I'll take my own risks.
Basically, IMHO, Android permissions is almost as broken as UAC in Windows, with all but a very small % of people actually reading and bothering to understand application permission requests.
What is needed, is for trusted third parties to verify if a given list of permissions is needed, and give (via a security software add-on) a popup with an assessment of how safe it is to install that app -- green, yellow, or red, for example. That is about the only thing that most end users (and even busy geeks) can really comprehend.