* With the techpack integration implementation of Google's msm-4.14
kernel https://bit.ly/2WqiMFx (CAF didn't port this to their kernel
thus suppose Google's port is the standard one), these headers are
installed to include/audio/include/uapi.
* This fixes building audio HAL with 4.14 kernel
Change-Id: I8283699470a7bcb31c771c9aa770a825b4e82519
[installrecovery]
* Don't try to mount system
[installboot]
* Kill kernel module pushing
* Now we don't need to mount system anymore ^.^
[eat]
* No need to use /cache/recovery/command when we have
adb reboot sideload-auto-reboot
* Make use of our custom adb wait-for-online
[_adb_connected]
* Could be removed entirely, but for now make it use
adb wait-for-online
Change-Id: Ife25e63c63c784670c7d330f8a69de01326de1a0
* APEX is useless to average Lineage user, as we aren't
licensed to ship the GMS APEX's, nor would we want to,
as we want to keep compatibility with non-GMS use-cases.
* Additionally, APEX's should each be signed with their
own unique key, and number of them can vary per-device,
which makes signing them in a standard way on infrastructure
quite complex.
* Though this flag is default, we need to disable it
explicitly to make sure any maintainers who set up the
configurations for APEX images won't change needs of
infrastructure. This will allow people who want to build
locally to use full APEX(s).
Change-Id: I7f2eb52593eeca1b3761a7a163ce9079995870c6
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
.repo/manifest.xml is no longer a symlink becuase apparently windows
developers need to use repo and windows needs admin for symlinks.
https: //gerrit.googlesource.com/git-repo/+/a269b1cb9dc21dfd598bfea3766206b606ad4589
Change-Id: I88ea0295133959136d7214f13a76b66d89dc88d4
* 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
* We can survive without granting this permission
out of box, also fixes Exchange-less boot up
exception.
D AndroidRuntime: Shutting down VM
E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
E AndroidRuntime: java.lang.IllegalArgumentException: Unknown permission: com.android.email.permission.READ_ATTACHMENT
E AndroidRuntime: at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:2103)
E AndroidRuntime: at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:121)
E AndroidRuntime: at com.android.server.pm.permission.PermissionManagerService$PermissionManagerServiceInternalImpl.grantRuntimePermission(PermissionManagerService.java:3032)
E AndroidRuntime: at com.android.server.pm.PackageManagerService.grantRuntimePermission(PackageManagerService.java:5800)
E AndroidRuntime: at android.app.ApplicationPackageManager.grantRuntimePermission(ApplicationPackageManager.java:684)
E AndroidRuntime: at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1217)
E AndroidRuntime: at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissionExceptions(DefaultPermissionGrantPolicy.java:1381)
E AndroidRuntime: at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissions(DefaultPermissionGrantPolicy.java:297)
E AndroidRuntime: at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21731)
E AndroidRuntime: at com.android.server.SystemServer.startOtherServices(SystemServer.java:2037)
E AndroidRuntime: at com.android.server.SystemServer.run(SystemServer.java:529)
E AndroidRuntime: at com.android.server.SystemServer.main(SystemServer.java:356)
E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:908)
Change-Id: If2caad2b004820b10b7095a4bb4307d0f065c723
* 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
This fixes parsing when arguments contain colons, a typical usecase
would be:
-vendor/app/TimeService/TimeService.apk;:timeservice_app_cert
Change-Id: I7500ae09632632ddc10734d9b1df267e28286b67
* We are no longer providing our own root access solution
as of 17.0, as PermissionHub has largely replaced the
functionallity of Privacy Guard, which this feature
was housed in.
* We do still have a baked in ADB root solution that can
be enabled in developer settings (see topic:ten-adbroot
on Gerrit).
* This DOES NOT mean we will be providing support for other
root solutions.
Change-Id: Iecf92e3c8f91304ed998e0260d09a8048dc44d82
* there's no per device way to add props to /system/build.prop
* adding it here is the only way so far
Change-Id: Iafc286d9e479677540a4ec617db76715c018ae8e
This can be imported into Android Studio more easily, eventually even
as a repository of LineageOS emulator images.
(Build with `m sdk_addon`, it will end up in out/host/linux-x86/sdk_addon)
Change-Id: Ia78524dd729b0f2ccc96f5a6eb2503cdc8b4d253
Starting with Q, Chrome is no longer a webview provider.
The role was switched over to google's webview app.
Change-Id: I59251578820a9af0b8ad8e51eb429156e7b7a3eb
AOSP pushes RROs to system by default now,
therefore our custom target is not needed anymore.
This reverts commit 546c9a1ec5.
Change-Id: I46753a3b60a89f0198058fbc6d07d3db8a6699b5
Permission no longer required because Styles handling was
removed from LineageParts. ThemePicker is our best friend now.
This reverts commit a7b0cf7ec3.
Change-Id: I003cd2281de9f7edbd81a15e0c1b1258e537ccb3
dianlujitao
Han Wang
Luca Stefani
shagbag913
XiNGRZ
Arne Coucheron
Alessandro Astone
Nolen Johnson
z3DD3r
Andreas Schneider
Tom Powell
Kshitij Gupta
Marc Bourgoin
Bruno Martins
razorloves
Wei Wang
Davide Garberi
LuK1337
Anirudh Gupta
Michael Bestas
Roman Birg
Sam Mortimer
Volodymyr Zhdanov
Tim Schumacher
Martincz Gao
Jan Altensen
Danny Baumann
Demon000