frameworks_base.git - frameworks

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add RequiresFeature annotation.	Jeff Sharkey	2018-02-16	1	-0/+3
\| \| \| \| \| \| \| \| \| \|	Certain APIs require that a device have a specific feature to operate correctly, so start annotating them. Test: builds, boots Bug: 72284763 Change-Id: Ie2f30284bdfdb6acc4067f434eba3b5433837606 Exempt-From-Owner-Approval: simple annotations
*	Annotate @SystemApi with required permissions.	Jeff Sharkey	2017-06-05	1	-7/+2
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Most @SystemApi methods should be protected with system (or higher) permissions, so annotate common methods with @RequiresPermission to make automatic verification easier. Verification is really only relevant when calling into system services (where permissions checking can happen on the other side of a Binder call), so annotate managers with the new @SystemService annotation, which is now automatically documented. This is purely a docs change; no logic changes are being made. Test: make -j32 update-api && make -j32 offline-sdk-docs Bug: 62263906 Change-Id: I2554227202d84465676aa4ab0dd336b5c45fc651
*	Avoid caching services with missing binders.	Jeff Sharkey	2016-08-11	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	When fetching system services early during boot, if the underlying binder interface hasn't been published yet, we end up caching a manager class that is broken for the remainder of the process lifetime, and innocent downstream callers end up using the broken cached manager. Fix this by using an explicit exception to quickly abort manager creation when the underlying binder is missing. The exception is only used to skip the remainder of the manager creation, and it doesn't actually crash the process. Bug: 28634953 Change-Id: I0cb62261e6d6833660704b93a11185aa11a2ac97
*	When system server goes down, crash apps more.	Jeff Sharkey	2016-03-01	1	-4/+3
\| \| \| \| \| \| \| \| \| \| \| \| \|	Apps making calls into the system server may end up persisting internal state or making security decisions based on the perceived success or failure of a call, or the default values returned. The reality is that if the system process just died, init will be along shortly to kill all running apps, so we should have no problem rethrowing the RemoteException as a RuntimeException. Bug: 27364859 Change-Id: Ife0bcb079636c88d54c44d17eb580409fd79028b
*	Fix a typo in a javadoc comment	Martin Storsjo	2014-01-24	1	-1/+1
\| \| \| \|	Change-Id: I7f3b5d3bf6ee2f966636a588c14908ee632a531a
*	consumer ir: clarify @link in documentation	Alex Ray	2013-09-11	1	-4/+7
\| \| \| \|	Change-Id: Ifebd0b550f5d9860697539646596a0b1cc782949
*	Add consumer IR framework	Erik Gilling	2013-09-11	1	-0/+153
	Change-Id: I786c00db0cce61ef75e4edc24e90f2cdcba6dbfb