* No longer used by any device and fw/base part is missing
Revert "Update boosted audio files 2/2"
This reverts commit 103c64a964.
Revert "Add volume boosted ringtones (1/2)"
This reverts commit a1c783fb28.
Change-Id: I384f44d515e2bcc237662184de0830836ba95b09
Add dun apn type to fix hotspot/tethering.
Also update according to https://www.ultramobile.com/data-settings/
BUGBASH-2371
Change-Id: I202cc7be26403d774e8694dd4386391d3576ea66
(cherry picked from commit 367ca28f8206a1e5be8655fb2f1c2e4972d7e8e3
For Example new devices need the new Sprint APNs, so add a new board flag for
them to set that will make the build system add the new APNs to
the APN config XML. If the flag is not set, continue to use the
old APNs.
To add or replace APNs, the custom_apns.py script has been
added. If CUSTOM_APNS_FILE is defined, custom_apns.py
is run and generates a new version of apns-conf.xml.
Change-Id: I7ff12a4342de2a7663b2b66fd627244214a8dc71
* LineageOS/android_system_sepolicy@0e3235f45d removed open, read,
and write for init to general sysfs types. As schedulers are
changed, the related directories gets dynamically torn-down and
rebuilt, but they lacks proper contexts. We need to make sure the
context is correct before init can write to these nodes.
Change-Id: Ic6f4567c173799bc56ecccc217040392f73aeaba
Bulgarian numbers: Most of these were directly sourced from Crisis or
Emergency centers' websites. At least half are from one of the leading
NGOs' detailed map that includes contact details for numerous hotlines,
centers, etc.
The non-Bulgarian numbers were sourced from https://116111.eu and
from the CM 14.1 sensitive_pn file.
Change-Id: I925b36ad7f616acf24c4c1e2109ea817a6de9338
(cherry picked from commit c88df996bea6f45093a6493d85c84b2df8a204d8)
Changes:
1. Rename "Internet" to "JIO 4G" per carrier request
2. Make IMS APN invisible per carrier request
3. Remove "carrier_enabled=true" to reduce
redundency as that's default value
Bug: 32935086
Change-Id: Ic7ce9978ed03aa24f116cad3b4fb049277864b89
This fixes BUGBASH-2328 for Portuguese carrier NOS (mcc="268"
mnc="03").
This is an ugly workaround since you can't edit the APN definition
anymore: if you try to save an APN with type dun, you get the error
message: "Carrier does not allow adding APNs of type dun." But it's
working.
Since the preinstalled APNs does not need to be edited and this
doesn't break anything else for this carrier, this is acceptable.
Thanx to tfae@xda.
Change-Id: Ic81a9549bf9610805e68b9be56c811b008cbdacb
* T-Mobile's domestic network is IPv6 only, and T-Mobile
support recommends setting IPv6 only for max compat
* T-Mobile support also recommends IPv4 only for roaming,
however compat issues have been discovered in the past
* Switching to IPv6 only domestically fixes an issue with
literal IPv4 addresses failing to resolve properly on ether
Change-Id: I7e394c6b7eebf9c106eaea5e000fe021adf421e6
* The LineageOS versions properties were removed from the build.prop,
which is resolved properly in commit:
"lineage: Keep LineageOS versions properties in build.prop"
Change-Id: I0060141c097b3d14c3710eee1e0caf7110634967
Change-Id: Ib11670474641d6fd14a00f8421e9fe8d1879bbc2
* The grep errorlevel output was not properly used by the if,
therefore allowing a device to upgrade with old addons
instead of aborting the backuptool steps
* The LineageOS versions properties were removed from the build.prop,
which is resolved properly in commit:
"lineage: Keep LineageOS versions properties in build.prop"
Change-Id: I0060141c097b3d14c3710eee1e0caf7110634967
* Introduced in the following commit:
"backuptool: Take into account new location for system default props"
Change-Id: I62046447876c2198a0c4f88a4f36f4723d417617
This reverts commit 1022cc7c50.
Change-Id: I7f5a3510f64f0ecabfe9d15b5dbc1a667b210eb8
Signed-off-by: Adrian DC <radian.dc@gmail.com>
* otasigcheck doesn't work on encrypted devices and makes
the zip installation fail since oreo.
* The build part of this was never ported to oreo.
This reverts commit aff5e54c4e.
Change-Id: I411f33c1db64844091c1692ef4706ae541925d4f
* Newer Sprint devices will only get LTE on the x.* variant of
the APN. Though, using this breaks all legacy Sprint devices
LTE connection. until we have a majority of post 8996 era
devices, default to the n.* variant of the APN.
Change-Id: I95a26a5d3175dbf6ebd4eb78e9f2720017c8c7e2
* Since A/B addon.d scripts are going to need to do things in a
specific way or things could go horribly wrong for a user, let's
introduce versioning so that scripts can claim to be compatible.
* A script can denote it is compatible with addon.d version 2 by
adding: "# ADDOND_VERSION=2" somewhere in its script.
* Only A/B will require version 2 scripts for now, and version 2
scripts will still run on non-A/B. Additionally if a script does
not explicitly denote its version, assume its version 1.
* Version 1: The same old scripts we've always used. We cannot assume
these will all work with A/B backuptools.
* Version 2: Scripts that denote they are compatible with version 2
must be aware of the fact that A/B devices will run this
script for a rom, during a seamless update, mounted at
/postinstall. The best way to ensure compatibility would
be to use the pre-designated functions found in the
backuptool[,_ab].functions scripts.
Change-Id: I5573018dabd21bb64c7c964e2081806072a75243
* A/B OTA devices wont run backuptools in recovery (because they don't
go in to recovery to do an OTA). In these cases let's use a modified
version to backup/restore from within android upon postinstall.
* Add backuptool_postinstall.sh which will be run prior to the normal
postinstall script in order to backup/restore via addon.d scripts.
* This needs to be done in such a manner because we need /postinstall
mounted rw instead of the ro with context= options which are used for
the normal postinstall (dexopt) script.
Change-Id: I51511870634dd1ec5388adafddb446f95cc5a950
* Due to both following commits, backuptool went permissive
and lineage properties got lost from the system on devices
that do not have BOARD_PROPERTY_OVERRIDES_SPLIT_ENABLED
"backuptool: Take into account new location for system default props"
Change-Id: I62046447876c2198a0c4f88a4f36f4723d417617
"lineage: Move to Google's method of defining system default props"
Change-Id: I6cb0e28a7599b010b389cc541015a37010a00f4b
* Once the properties issue is properly resolved in the sources,
a period of time is required for "most" of the users to upgrade
their system with fixed lineage properties before we break addons
by repairing the backuptool script globally
Change-Id: Iea8865ea9bb05eed56a8a0a7b95e3f04b01c4bae
- Add missing ims apn. Without this, pixel and nexus users were not
able to use ims features.
- Set the mtu value. This improves data connection reliability.
- These changes match with pixel's aosp apn.
Change-Id: I170de2c92cc916424c266dc972a6538599640b7c
Pixels will only establish a data connection to these carriers using
IPv6, so this fixes the reports of no cellular data and no mms.
Also, this matches with what aosp has.
Change-Id: I07768f817cf6bb4997dd737cc467fb146c959434
* System default props defined using PRODUCT_SYSTEM_DEFAULT_PROPERTIES
are stored into /system/etc/prop.default, so that's the location where
ro.lineage.version prop needs to be checked now. Although, fallback
to the old location to allow sucessful upgrades.
Change-Id: I62046447876c2198a0c4f88a4f36f4723d417617
Michael Bestas
Rashed Abdel-Tawab
Bruno Martins
Luca Stefani
Marc Bourgoin
Nicholas Lim
Reza Feizi
aleksei74
jperal
Arekusu Rin
Jacob Willoughby
Michael W
razorloves
LuK1337
Kevin F. Haggerty
Youhan Wang
Meng Wang
Nvertigo
Paul Keith
Adrian DC
Nolen Johnson
Dan Pasanen
James Hilliard
Eric Meddaugh
Olivier Karasangabo
Louis Rousseau
Alexander Kaindl