The priority order for overlays is PRODUCT > DEVICE > LOCAL
Having PRODUCT here was overriding all of the DEVICE_ specifics
mentioned in device repositories, which was not the intent.
vendor/cm is present as a set of sane defaults, but for the most
part these overlays are intended to be overridable by the device
if needed.
The logic is that PRODUCT_PACKAGE_OVERLAYS should be used by a
particular product while DEVICE_PACKAGE_OVERLAYS is used by
several products that share common device configs. Yeah, the naming
is counterintiuitive, but that's the implementation in
build/core/package_internal.mk
Partially addresses CYNGNOS-2229
Change-Id: Icfbc92593e37f3c00c3d26dd09e08d09267621ed
Since cmsdk prebuilts lives in a single master branch,
previous branches that apicheck will fail since they'll
verify against an api that exists in future releases.
Change-Id: I56594d075b89cb1a3d7a606cc9c1699dfffd94cb
TICKET: CYNGNOS-2220
This module will be required by a number of packages across the
build tree.
The artifact is currently hosted on Maven Central and the version
defined in the mk file is the latest version of the artifact
available in the repository.
**Note: this change will require Maven to build (v3 is recommended).
Change-Id: I9459ae21b0f4c8f88d2b3a2b5014a36b17b9651b
Add ability to `make cmsdk-test-coverage`
to generate an html page which denotes how
much the testing package from vendor/cmsdk
covers public interfaces.
Change-Id: I76556df1822934a6b7e86ebf2ff42e302acff46d
TICKET: CYNGNOS-2189
This fixes issues where the kernel would need to read and write
files from internal or external storage. More specifically, the
kernel needs these rules for USB mass storage to work correctly.
Change-Id: I8cb0307727bc0c464d5470e55275ad808e748ee0
The default behavior is as if this setting is off. There's no need
to set it. Settings will now set it at boot if not configured.
This reverts commit e0e8c2772e.
OPO-490
Change-Id: I77963dfc9eea8ece25ed1b6b17bd2c6936ae69ee
* wap? WAP? What?!? Are we living in the dark ages with our dumbphones? :)
* Remove redundant Telenor entries
* Tele2 are part of NetCom now, and all users have been transferred there
* Talkmore and djuice can use the Telenor APN
* Remove providers that doesn't exist anymore
* Update some APNs according to info on providers webpage
* Consolidate some APNs
Change-Id: I2bd6441e476aebf1c0c63b34d659efce40e42847
For the record, I do not like my name being first here. When all is
said and done, u-ra chose his handle unwisely and is relegated to the
end of the alphabet -- a doltish move.
Change-Id: Ib1f15af12c1118e6fda5673b08e870dfdb941e15
System server needs to be able to create a pipe in the cache partition
for uncrypting OTAs. Uncrypt needs to be able to read and write the
pipe.
Change-Id: Ie03ee7d637eaecff8fe38bf03dc733b3915cd336
* Allow both IPv4 and IPv6 protocols for data and mms
* Provide an apn name for the initial attach profile
With respect to initial attach, it seems at least the qcom ril blobs
on my device require the apn field to be set. The following error is
produced and data will not connect on boot unless radio resets (e.g.
airplane mode toggle) so that the default APN is used.
E RILQ : (0/231): RIL[0][cmd-111(680)] qcril_data_request_set_lte_attach_profile: ril_apn (provided NULL) is mandatory param for looking up profile.
E RILQ : (0/231): RIL[0][cmd-111(680)] qcril_data_request_set_lte_attach_profile: EXIT with FAILURE
E RILQ : (0/231): RIL[0][cmd-111(680)] qcril_qmi_nas_set_initial_attach_apn: Data RIL call for Attach APN failed with Error code 2
Change-Id: Ie983474780a7443c870911994234ea2f2025de12
We now use a temporary context when mounting /data, so add permissions
to do that, and add permissions necessary to do the recursive wipe.
Change-Id: Ic925c70f1cf01c8b19a6ac48a9468d6eb9205321
AdrianDC also in the crew now while Marcelo doesn't have the device anymore.
This patch was requested by AdrianDC.
Change-Id: I57a27655537d96c7f5dc33f33d8e7d7e3982d6db
Also allow apps to read the contents of mounted OBBs.
See AOSP Change-Id: I66df236eade3ca25a10749dd43d173ff4628cfad
and Change-Id: I49b722b24c1c7d9ab084ebee7c1e349d8d660ffa
Change-Id: I757a2a8831c69d41c0496025a39eaf79ceb0e65f
Maven APK (Why are these in maven anyways?) will crash due to it not
needing to generate a jack file. This wasn't noticed before as brunch
succeeded, however, doing an mmm on one will cause this to fail. This
adds in logic to not generate a jack file for an apk in maven.
Change-Id: I44036bfd51ae3edd9437b153898b419ffc6ba2d6
