Not anymore they're not [1][2], permissions now fall into large buckets.
iOS is probably the best as far as privacy sensitive permissions go. You're prompted at request time instead of at install, so you know the context of why it needs a permission (like GPS or contacts). You can also revoke a permission after granting it. You can't do that in Android.
[1] http://www.xda-developers.com/android/play-store-permissions...
[2] https://support.google.com/googleplay/answer/6014972?p=app_p...
I definitely agree that Android's user interface is a problem, and that transparency is hindered because of these changes. Nonetheless, a user can still know what an app can do to a degree of detail far exceeding other systems. Android's technical capability here exceeds other platforms, so let's hope they'll make it usable soon.
[1]: http://www.xda-developers.com/android/exclusive-android-l-lo...
Google are getting worse and worse, becoming more like an Apple or Microsoft. But where else is there to turn?
So you haven't yet taken a look at iOS? iOS is pretty transparent. I would say far more so than the broad, vague permissions model Android is currently using and the even vaguer one they're moving to with their "L" release.
Additionally, with iOS, you can also go back and granularly review app privacy settings and adjust them, if desired. You can't do that on vanilla Android.
2. Some applications want to use too much permissions on your phone. You probably don't want to install them.
And the second is a bigger problem? Really?
Android is the most transparent and detailed about what applications can actually do on your phone from any such system I've ever seen. People make concious (stupid, but concious) decisions to still use apps and ignore the presented information. This exploit removes all control a user may have.
By making this comparison in the first place, you are confusing the discussion already. Yes, Android can and should improve when it comes to user control. But this is a problem that leaves hundreds of millions devices exploitable even without depending on user ignorance. This exploit and the issue you mention are not even related.