tree 0a793639de5fce3a149cbe94c5db754e98c5dc31
parent e043795d3b2fadabb0f20add27c1d1544b1e89fc
author Svet Ganov <svetoslavganov@google.com> 1456517584 -0800
committer Svet Ganov <svetoslavganov@google.com> 1456518214 -0800

Refresh the native app ops manager's token if needed.

The app ops manager serivce keeps track of started app ops
by a process by stashing them in a binder object that is
passed to the remote process to hold on to. Hence, the data
is in the system process and is referenced by the client
process it tracks to prevent garbage collaction and limit
risk of resource leaks. It is possible that the client
process is longer lived than the system seriver, e.g. camera
server starts an app op, the system server dies for some
reason, the camera server's app ops manager ends up with
a stale token. The solution is to check the validity of the
token and refresh it if needed.

bug:27344593

Change-Id: I0abb39e777b7b66b1b5cefede7e7b41c4404c4b1