* 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
This is to allow repopick to determine a branch even on a
revision locked manifest. If upstream is not set, it falls
back to revision.
Per the repo manifest documentation:
Attribute upstream: Name of the Git ref in which a sha1 can be
found. Used when syncing a revision locked manifest in -c mode to
avoid having to sync the entire ref space. Project elements not
setting their own upstream will inherit this value.
Change-Id: I12876f7e3b440f9eab6d1b96eba9b18a13cff2e0
When a manifest project path and project name is identical, the
repo manifest parser returns None for the project path. Since
both name and path are required, fall back to using name for path
when path is None.
Change-Id: I2fb3cc0cc643808a3049171804742f249d737679
Sourced from: https://github.com/dslul/openboard/pull/108
A total of approximately 750 words and their forms were added. The first line was amended with the new version and a correction for the name of the dictionary, which did not list the language name with a capitalized first letter as it should have.
The newly added words are mostly names of local dishes (cuisine), old or dialect words, Turkish loanwords that are commonplace, curses and offensive words and words pertaining to gender studies.
As is noted in the original source (https://github.com/dslul/openboard/issues/105), the new lines received the addition of ',flags=originalFreq=' for future proofing, but the old lines did not.
Other things to note if somebody wishes to improve this in the future:
1. The general frequency is skewed and needs to be heavily improved.
2. Offensive and possibly offensive flags are missing, as are any other flags that may exist.
3. Common personal and family names, famous historical figures' names, as well as monikers and/or celebrities' pseudonyms could be added to further enrich the dictionary.
4. The prefixes 'по' and 'най' (hyphenated in front of certain words) can't be handled by the dictionary as is.
Change-Id: Iee6d2e43166b324ec16f5bbe00dceac8b9289b67
By setting QCOM_SOONG_NAMESPACE in device.mk
This will allow a device to specify a device specific branch within
hardware/qcom-caf/ or the device tree.
Signed-off-by: Andrew Hexen <SyberHexen@gmail.com>
Change-Id: I39693a0fb9665129f0810590d389c4cb06cdf8d7
Move required permissions to the respective apps.
This allows people to use a lot of our apps outside lineage
without extra changes.
Change-Id: I840a9edeae38e94ff6592c4817fcea6f5e4a7e8f
There are a lot of apps installed by default that are unusable with
a controller. This splits the mobile related settings out of common
into a common_mobile config and adds common_tv.
Note: The EXCLUDE_AUDIOFX flag was removed from the tv configs
because the new config path no longer builds it.
Change-Id: I67db32750fca91725d703243f2bcee8bcd9b82cd
* zip stores timestamp for all included files. The timestamps of dex
files are different across different runs, result in inconsistent
checksum of output apk/jar.
* Workaround the issue by using fixed timestamp for dex files.
Change-Id: I21f3a7e32cdfdb07c5f5c140df2e797efd4a8005
* 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
