In Q, we added a new bugreport API that asks for user consent before
showing the "Share" notification for the bugreport. We will be migrating
all bugreporting clients to use the API in R.
In the new API workflow we are moving away from broadcasts and using
callbacks to communicate with dumpstate. Finished bugreport notification
broadcast used to share the final path of the bugreport but API now uses
file descriptors instead. Hence, moving away from broadcasts.
The full bugreport in this case can be retrieved from dumpstate directory
using 'adb pull' or finding and attaching the file directly to gmail or
betterbug.
Remove outputfile flag since it's unused.
Bug: 135186519
Bug: 137825702
Test: Build and flash to the device. Create a bugreport using combo
keys, share notification does not pop up. Full bugreport created in
bugreports/ dir
Change-Id: I3c15123a6a4ed62ae9cb87f5dd07db60b1416dfc
Using cp instead of mv during the restore step resulted in double the
amount of free space and inodes being used.
For example, a nano arm64 opengapps install uses around 500M. But during
a backup/restore process when the Updater is used, it temporarily uses
1G on the other slot. That causes failed updates on devices that
don't have that much free space on the system partition.
Change-Id: I57ba2e0f52d328d4ff91d47a3db45f47bb8402af
Extracted from sony stock rom firmware 'H8266_Customized DE_1313-6279_52.1.A.3.49_R3C'
E-Plus got merged into O2
Synced the newest O2 changes
Change-Id: I67e6987769d0bcc271e58e7416468faa902a870b
* There is no reference to ANDROID_CACHE now, and
/persist does not exist on most devices, neither
can we write to it.
Change-Id: I91af1e6f571ced317d195e3a7901bf4c269486a1
Backup/restore functionality was broken in the
Ia1f4ae95c9e4dae4df844853e81c264bc838f177 change
because of incorrect check of the function's result.
check_prereq() function refactored to return 0 if
backuping/restoration is possible. Any work should be
performed only if check_prereq() succeeds.
Change-Id: Ic977dba675df58a228ef4b882b25beb66cc9d2c6
For non AB devices system partition should be unmounted
if check_prereq function fails.
This patch also refactors backuptool a bit for AB devices
in order to look same as backuptool for non AB devices.
Change-Id: Ia1f4ae95c9e4dae4df844853e81c264bc838f177
* This check was supposed to check whether the script
addon.d version was lower than backuptool's
* Given that the backuptool addon.d version is 1, this
isn't going to happen ever making this check completely
unuseful
Change-Id: I2464749b52bf4e8825e0b4ef42500ee7d3bbfa61
* For some odd reasons executing `cd /system/addon.d` makes the system
hang and unmount error:
umount: /system_root: Device or resource busy
* Don't change directory to not allow the system partition hang
Change-Id: I3d30bdc59c2f05d16823e99046c1dce2e1e6eb73
* If any of these two function gets run on a recovery mounting system
to /system, /system/addon.d won't exist while /system/system/addon.d will.
* Run the functions with $S as argument to make this work correctly
Change-Id: I02e7b91429a9e74d28bdb77e56955dad97ca75ac
* The path /postinstall exists only for A/B, causing:
grep: /postinstall/tmp/addon.d/*sh: No such file or directory
Change-Id: Ia07b3029e949c3e08302457cd08798a4dde00ef6
* Dynamically mount system to the path chosen by the recovery through backuptool
* This can be helpful because of the fragmentation that will happen with system mount in recovery after Q
Change-Id: I2d1e775efcf87e33319bc7790d1e54bca72116d3
* 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>
