This reverts commit caa3bddf00.
Reason for revert: Breaks pixel dtbo.img build, since kernel depends on
mkdtimg. Add it back so it gets compiled and kernel can pick it up.
Change-Id: I2b9fd0b2b35e0cf2f908516b10f65399780d5c30
This also removes user_visible="false" for some AT&T WAP APNs as
the rest of the AT&T MVNOs APNs had it visible but these ones
weren't.
The reasoning for this is that we can't (and no one can ever)
guarantee a single static APN list is correct for all devices
all the time. Let's not leave users in a situation where they
can't attempt to recover themselves by fixing their APN without
jumping through hoops to copy the APN fields into a new APN.
TODO: Evaluate how user_visible should be used.
Change-Id: I2b4975db9d52943390b61b50b9258746eab447c9
* This also adds proper Carrier ID and MVNO ID to
the APN, so it's not shown on incompatible carriers.
Change-Id: Id682adfacc76e95ba53c83e47d842b5868424db1
* AOSP build system is not aware of dtb(o) source update, and thus
won't rebuild the images, results in outdated artifact.
* Convert DTB(O)_OUT to make targets and make the images depend on them
to address the issue. This makes AOSP build system be aware of
their timestamp changes and re-execute recipes depending on them.
Finally, it's up to kernel's build system to decide actions to take.
Test: m dtb(o)image and observe dtb(o).img get rebuilt
Change-Id: I197e7d2d3e013ded0e555fc22bb6a1200d40df9c
This soong variable is used to conditionally revert a commit [1]
which causes random camera crashes on tama devices
[1] a9550f3fe9
Change-Id: I749c7029f8f2b6d6d95b066aed4929c33e3c75e7
* For every commit, repopick checks the last commits for the presence of
the commits to be picked
* In every project a change should go in, it calls "git rev-list --count"
to find the maximum amount of commits to be searched, but it only cares
if there are less (or equal) commits at all than to be checked
* Therefore, we can limit the counting to one more than we want to check
* This is relevant for example for fw/b, where there is a huge amount of
changes and therefore a lot of time used to count
* Example: fw/b
git rev-list --count HEAD: 46.693s
git rev-list --count --max-count=1000 : 0.019s
* Real-life example:
repopick -t qs-lightmode
Old: 2m33.375s
New: 0m6.657s
Change-Id: If0500574fb282e332996b606dd9926841f8e0e88
Flag PRODUCT_IS_ATV must be set for all ATV targets,
so Automotive targets can follow and adopt PRODUCT_IS_AUTO as well.
No need to export WITH_GMS_TV or WITH_GMS_CAR anymore.
Change-Id: I7f35e7fa731f7cee239aff03c99b83975abbb56e
Similarly to change I6a55dd25f8435523f98970bfd24c3f86657ba6f7 the CNE
app also receives the phone state broadcast including location data,
which constantly triggers the location indicator.
Change-Id: Ic11674b7f3cccb6b5b7de1e5f8a99a01fd32c589
msm8953 has updated HAL projects. Make use of them.
This can be made use of by setting `TARGET_ENFORCES_QSSI`
to true.
Change-Id: Ib7ababd52470913c915f1da3d6b726eff2f38410
Android 12's privacy dashboard shows permission usage timelines for
location, camera, and microphone. However, there's no reason to limit it
to those specific permissions; all the infrastructure is in place for
other permissions.
To enable the usage timeline for more permissions, keep discrete app op
history for all permission groups shown in the privacy dashboard. The
list of permission group -> app op mappings was obtained from
AppOpsManager.RUNTIME_AND_APPOP_PERMISSION_OPS with a few additional ops
from PrivacyItemController, and each op was resolved to its respective
enum ordinal from frameworks/proto_logging/stats/enums/app/enums.proto.
Change-Id: Icbde7fb59ae16fa7b15160d78d9dce7125a82ba6
* BFQ is not enabled in kernels for recent devices. Considering
that pre-MSM8998 devices are likely to be dropped, it is time
for this ricing to die.
Change-Id: I7fcf7afa7aa7c7aaab2e7ee917b1e2e8203d0abb
- This looks more modern and matches the stock Pixel style.
- This matches the stock Pixel rounded corner styles as of Beta 5.
Change-Id: I94d6e782a24873ae0c59b6613e998f4a80842712
Commit 8ac7d31 introduced this issue.
Test: run `m recoveryimage` and verify that recovery
image is now built.
Change-Id: Iffdd8112db2ba1baff28db7ee4c340dbb5ebd917
Commit 8ac7d31 introduced this issue.
Test: run `m installclean && m bootimage` and observe that
kernel image is built.
Change-Id: I41eb7cd2e5108bae8f4c40c0f9a300a8a3cc95a7
