One of the well received features was application's permission manager which was exposed indirectly and was later removed in a future update. I guess, this must have been done to ensure graceful handling of permission failures when used by applications. Few requests to vibrate etc could be ignored silently but requests like connecting to camera probably needs to be handled with a kind of notification to the user. And in the worst case, permission denial of this kind shouldn't trigger a framework failure. One such failure is when a pattern vibration request by an application is to be ignored (https://android-review.googlesource.com/#/c/70914/), which ends up overloading the main thread of the framework process (system_server) and performance is noticeably impacted.
No comments:
Post a Comment