This reverts commit 4c6e1b62e0, since sr-Latn is no longer planned for MR1.
Bug: 29455508
Bug: 29601930
Change-Id: I47c240fa7456940ecb272f05e94f563b221c92c3
The Dev Settings app currently just launches an intent that is received
by the regular Settings app. However, since N the Settings app only
receives the intent when developer mode is enabled. If it is not enabled
the Dev Settings app will crash. Since the Dev Settings app doesn't
really add much benefit this change removes it from the emulator system
images to prevent this issue. The user will have to access the developer
settings from the regular Settings app just like on a physical device.
BUG: 27549126
Change-Id: I8191f9003bb452ef76c4b236b965368b48be3d25
Use default phone compiled-classes list to cut down boot image
size on most devices.
Bug: 28026683
Change-Id: I73bb59b792923ebc7549f775085b1c9aed88cc1a
The inclusion of Romansh (rm_CH), while it did not have localized
strings, was causing the incorrect assumption that the system
supports Romansh, causing the language fallback to work incorrectly
when Romansh was in the list of user's locales.
Hindi (hi_IN) was also included twice, and this removes the duplicate
too.
Bug: 27325465
Change-Id: I87ec06dc459137f71bb8e5e2f431f629bd51928e
The Android framework assumes that if an app uses UsbManager then there
must be USB support on the device. In order to deal with this the
emulator has to indicate USB support. Previously this was true for
Google SDK phone images because USB support is part of the common API
packages that gets installed. For AOSP and some other build targets USB
support was not included. This change indicates support for USB for all
emulator system images.
BUG: 28088069
Change-Id: I880210e89e6ad3412bdc069d6c20ed54a52cff83
Build errors when trying to dex2oat the CtsShim prebuilt even though it's marked with "hasCode=false".
This reverts commit d987a11126.
Change-Id: If47b3bcd4c727da7acd9068c02f8fb671ed0ae84
We need a shim application on the system partition that we can upgrade
during CTS tests.
Bug: 27450489
Change-Id: I32a72dc5110cedd466cdee2607965c705f7aa6d3
Recent changes have brought the log volumes for
the QCA WifiHAL down to reasonable levels. As
such, we no longer need to use a custom default
log level for WifiHAL.
This reverts commit f83213a5b5.
BUG=28178513
TEST=build, check log volume after >12 hours
This is not the proper way to really fix this, but it is the best thing to
do in the time period we have for N. In the future they will be moving
more to a dumpsys style approach.
Change-Id: I98ec7928cd93a3edfb93cdbf3703132ac6658699
This file contains list of libraries that should be directly or
indirectly accessible to apps for the platform. Note that this
file is not device specific but rather device class specific.
Bug: http://b/27546414
Change-Id: Ica2e6c5cedac6e4af9bd78addaa512b2fa272d64
Emulator is a product, so add an overlay that allows us to override some
stock android resources.
BUG: 27484734
Change-Id: I1b651316a14f6d5c79651813ad13302b67507cae
We've gone back and forth on this a few times.
Just state clearly why we're including the AOSP messaging APP here.
BUG:22097835
Change-Id: I26864ba033f0a211d038fa3526241c869d677217
If we are using an old API for the emulator
(API 19 for example) and then upgrade the AVD
to API 23 through the AVD settings, we get a bunch
of crashes in the TelephonyProvider,
as it is looking for a file that does not exist
that concerns upgrading from old "apn"'s.
This CL adds this file to the files to be copied
to /etc in the system image.
BUG: b.android.com/200390
BUG=27273457
RELEASE NOTE: Fixed telephony service crashes on startup when upgrading from an old API.
Change-Id: I227713880bf20541c759aab588c00197ac7aebfd
(cherry picked from commit e5083159401edf1df5109b56d1aedbbb739584e6)
This change explicitly includes only the messaging app instead of all of
aosp_base_telephony. This fixes the issue where on initial boot the user
was prompted to select a Home app. This happened because the
aosp_base_telephony makefile includes other makefiles that in turn add
the package Provision which has an activity with an intent filter for
handling HOME. SdkSetup already had such an activity so with two choices
it was left to the user to decide which one to use.
BUG=27273457
Change-Id: I42e77b892ce235a5fa858561325ae37973cfb0cd
(cherry picked from commit 12de252f451b34cfa67f7256027dad84dcfd984d)
