* Needs to be an env-var, or when Android.mk is read in partner_gms
we runinto issues with the var not being set yet.
Change-Id: Ia90f9a6c97ebf406a0f3c1848286300cace2c2c9
The check for official builds now only affects the case where a prebuilt
kernel was actually used, not the case where a device builds a kernel
from source as normal.
The check has also been turned around so that it only fails the build if
it's actually an official build, not an unofficial one.
Change-Id: I1280b16b90589742c2abe7f3f6f5975a3aaeea03
* TARGET_FORCE_PREBUILT_KERNEL should be useful when you don't have ready kernel sources (OEM releasing broken sources or releasing them lately)
* It lets you use kernel sources for userspace generated headers (generated_kernel_headers) while keeping using prebuilt kernel
* Keep in mind that generated kernel headers may not align with the ABI of kernel you're including
* This commit also partially revert commit a836d79, where TARGET_KERNEL_SOURCE would have been unset if TARGET_PREBUILT_KERNEL was defined (we already check in kernel.mk if kernel sources are present anyway)
Change-Id: I84acae890dabb5b9dbd48143ad58f6420c0cef75
* This fixes the case of have having APNs with same the name,
such as:
“Sprint EHRPD”
"Sprint EHRPD ota"
“Sprint EHRPD internet”
* But we want to replace only “Sprint EHRPD”, not all matches.
Change-Id: Ic3139c5d73a8c3c8667ac2bc527abc1a85541361
* It's EE now
* Should not be required since 2015:
"In 2010, it merged with Orange UK to form a joint venture,
Everything Everywhere, in 2010, which continued to operate the
T-Mobile and Orange brands until March 2015 and allowed T-Mobile
customers to utilise Orange's 2G signal and vice versa.
In 2012, Everything Everywhere launched a new network, branded EE."
-- https://en.wikipedia.org/wiki/T-Mobile_UK
Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/3069
Change-Id: Id94a6e156f20b484ea3d23cd3a30f5f9e796b117
* PosteMobile is now a full MVNO and it has its own mnc
* Entries extracted from platina-user 10 QKQ1.190910.002 V12.0.3.0.QDTMIXM release-keys
Change-Id: I70d314c558074f2564e88c761c22bc842b973d99
* CoopVoce is now a full MVNO, thus deprecating older ESP entries (still kept here because not all users changed SIM card yet)
* Entries extracted from platina-user 10 QKQ1.190910.002 V12.0.3.0.QDTMIXM release-keys
Change-Id: I9a59ba54926e27ce64d5adbca42fb7b058436e6f
As described in 204837/2#message-9ecc61fe611f195b13f5770e33904afccb01c2fa :
The "network location provider" which is finally used is selected in three steps:
- first the signatures of all packages, which are in this list AND which are installed in system, are collected (services/core/java/com/android/server/ServiceWatcher.java#L96)
- secondly the packages which implement the "network location provider service" are selected and their signatures are compared against the previous collected signatures (#L225)
- thirdly these packages are requested for their "serviceVersion" in metadate. The package which provides the highest version is used. If there are two packages with the same serviceVersion the first selected wins. (#L243)
There are no security implications because there has to be a proper signed package of "org.microg.nlp" in sytem first. (The check against the signature of this package allows for later updates of the package outside of system)
To quote Andreas Schneider from 204837:
"This doesn't have security implications as in order to use the location provider in needs to be installed as a system app. However this would allow it to be flashed to system like gapps."
On my opinion it's up to the user to decide if he want to use Gapps and Unified / MicroG. But in the first place this patch is needed to make it possible.
Change-Id: I4a046ead2cc46929d2c18cfe1561becb10a75bcd
* Ignore the block devices in case their mount points are symlinks.
This is common on devices where maintainers have chosen not to use
real partitions because of their size being too small to be useful
Also `continue` instead of `break`. Oops.
Change-Id: I3e27abe510219066ecacd81d099220ac8e119f9f
There are addon.d scripts that rely on the value of ADDOND_VERSION
to determine if they're being called from a-only vs a/b backuptool.
If they declare ADDOND_VERSION=3, they shall stop doing that;
otherwise offer them the same environment, that is unset ADDOND_VERSION
for a-only backuptool.
Change-Id: I1be21eda2e6ec9837b3080bb5e7fbe5241318eaa
* Also: add a lot of additional info for many of the numbers based on
the comments from the commit prior to this
Change-Id: I937637c8f002d193ed6b23ac60c1f350d7d2eec7