ea331d6bcc
The pin_camera flag being false makes some in-market devices (redfin, bramble, coral, etc.) not pin the camera app by default. Although a Phenotype flag overrides this value, the OTA flag delivery can fail and ends up non-ping state. This change makes sure that the device pins the camera app by default by removing pinner.pin_camera properties modification from this file. The current default is to pin the camera. See PinnerServices.java Note that the camera pinning is still disabled on crosshatch family, sicne it is known to be prone to the memory shortage. See device-crosshatch.mk. Also note that some newer devices already pin by default because they don't refer this file, although the name implies it might. Test: On Redfin: $ vendor/google/tools/flashall -w $ adb root && adb wait-for-device && adb shell am start -a com.android.setupwizard.FOUR_CORNER_EXIT $ adb shell dumpsys pinner Bug: 195035033 Bug: 184897981 Change-Id: I81207d0527f758d4800319a3a3c323919daaf814 |
||
|---|---|---|
| common | ||
| core | ||
| packaging | ||
| target | ||
| tests | ||
| tools | ||
| .gitignore | ||
| Android.bp | ||
| Changes.md | ||
| CleanSpec.mk | ||
| Deprecation.md | ||
| METADATA | ||
| OWNERS | ||
| PREUPLOAD.cfg | ||
| README.md | ||
| Usage.txt | ||
| banchanHelp.sh | ||
| buildspec.mk.default | ||
| envsetup.sh | ||
| help.sh | ||
| navbar.md | ||
| rbesetup.sh | ||
| tapasHelp.sh | ||
README.md
Android Make Build System
This is the Makefile-based portion of the Android Build System.
For documentation on how to run a build, see Usage.txt
For a list of behavioral changes useful for Android.mk writers see Changes.md
For an outdated reference on Android.mk files, see build-system.html. Our Android.mk files look similar, but are entirely different from the Android.mk files used by the NDK build system. When searching for documentation elsewhere, ensure that it is for the platform build system -- most are not.
This Makefile-based system is in the process of being replaced with Soong, a new build system written in Go. During the transition, all of these makefiles are read by Kati, and generate a ninja file instead of being executed directly. That's combined with a ninja file read by Soong so that the build graph of the two systems can be combined and run as one.