As of fw/b change I14365389990eb06daaa127f5db66df45abf6c064,
we now have an option to long-press on power to enable torch.
To support this feature, we need to enable long-press on power
while the device is still non-interactive.
Change-Id: I4e2b4af86d397f68e119963054c33fd890c77cc5
Chrome Stable and Google Webview had incorrect
signatures. That was due to an incorrect method
of determining the right signature.
That mistake wasn't noticed because Android
disables the signature check on "userdebug" and
"eng" builds. It is only enabled on "user" builds.
So this commit replaces the wrong signatures
of Chrome Stable and Google Webview by the
correct ones and thus makes them avaliable
webview providers on "user" builds.
Main credits go to @KreAch3R for his
extensive research on the issue.
Change-Id: I081783b59254bfed0b2e3568ba8ae2801d86efea
Signed-off-by: Alex Naidis <alex.naidis@linux.com>
The framework disables aggressive power-save modes when appropriate,
such as when the device lacks a significant motion detector.
Thus, instead of enabling it in each device tree,
enable it by default for all devices.
Change-Id: I1999b04876f1ddce1574c050b6bc582e9a9a96da
If Gapps are installed, better webview providers
become avaliable.
This commit adds support for those and makes the system
choose the best provider: Chrome Stable>Google Webview>AOSP Webview
It also allows the user to choose between additional
providers from Play Store: Chrome Beta, Chrome Dev and Chrome Canary.
This patch is a collobarative work of:
mfonville <maarten.fonville@gmail.com> @mfonville
rapperskull <rapper.skull@hotmail.it> @rapperskull
Arne-Christian Blystad <arne.christian.blystad@bartec-pixavi.com> @Blystad
Alex Naidis <alex.naidis@linux.com> @TheCrazyLex
Bugfixes and move to an overlay by blunden <blunden2@gmail.com>
You can find more information on this topic here: opengapps/aosp_build#76
Change-Id: I006d814b7c12ffe4f29cd865c9d4cc6a60bc7783
Make sure that the example overlay for configuring a product's
default-active backup transport names the latest incarnation.
Change-Id: I867062f703d3b5f39d40736805ba15f0d21b1afd
Rebuild those for which source wordlists are available.
Also, remove a couple of redundant ones provided by LatinIME
Change-Id: Ida10e7523f1af760a8fa7866dcea2caf16903d90
This removes the empty string here since it was overwriting anything
declared in our usual places for.
Change-Id: Ia46cc45938dfaa9a66014bfdbe8c3fd097298742
This will allow us to remove the overlay in vendor/cm so devices
with no battery, aka fugu, can override this to none.
Change-Id: I80c0cc06d3aed344c7c705d420af297c96baf706
Added SecretCodeReceiver to locked components
Added list of components that need to be forced enabled
(because they've been previously disabled)
Change-Id: I7cc0efc1830b45bc5384ff421b829e0be0d955d8
Settings resources states that this should be overlayed in product config.
Due to lack of another central source for info (note: need wiki page), point
to Google Support page.
Change-Id: Ic472951b98a409583571442909a638991396d538
This forces set UA string to Nexus5 for SoftBank MCC:440 MCN:20.
Tested send/receive & confirmed working by yours truly.
Change-Id: I1831c329eb38507a957111052bb5f56350c49361
In theory, could have been a good idea, but ultimately just leads to
headaches for device maintainers that need to overlay any of these.
Revert "overlay: remove Verizon specific eri.xml"
This reverts commit 5f92da62c6.
Revert "Add Japanese APNs/eri for au, docomo MVNO, EMOBILE and SoftBank"
This reverts commit eeeb0888d4.
Revert "Add apns/eri for Boost Mobile"
This reverts commit b207e2eda3.
Revert "add more vzw eri's"
This reverts commit 82e10af192.
Revert "multi-carrier overlays: Add eri and config for US Cellular"
This reverts commit 1af75f1ba7.
Revert "Multi-carrier overlays: Fix Mms"
This reverts commit f8b0737a43.
Revert "Generic multi-carrier overlays based on hammerhead"
This reverts commit 6f5758c9c3.
Change-Id: I3495a89ce405362dc558f7ec7f0e61adea9fa507
Restore order to the universe by removing that which is evil.
For some strange reason, Verizon devices do not agree on the eri.xml to
use, even on the same spn. Since it is not universal, it does not belong
in vendor/cm (at least while there is no automatic method to check which
eri.xml should be used). Remove these so that we don't end up with
strange double-overlay issues for devices.
Change-Id: If5a28ed03c8cc6b145c151c7ebf95fabdf81f434
Companion change to I8a648014873319ea0d0f1089495d6777b8a1b8bf,
config_mms_user_agent_profile_url can't be empty either
Change-Id: Ib6b34972439818da47c389377664e75263dfd21b
The default user-agent isn't set, which makes
TelephonyManager.getMmsUserAgent() return an empty string when a
device doesn't have one in its own overlays. Every hardware should
set its own unique name for this, but add a default value for cases
in which is is forgotten.
Fixes android.telephony.cts.TelephonyManagerTest#testTelephonyManager
Change-Id: I8a648014873319ea0d0f1089495d6777b8a1b8bf
Add a separate list of default lockscreen unlock targets for devices
without voice capability.
http://review.cyanogenmod.org/#/c/52966/1
Change-Id: Ifbb066faade39b1cd98a6d1bfb7b5021eb51ab95
Zhao Wei Liew
David Hays
Dan Pasanen
Alex Naidis
Joey Rizzoli
Ethan Chen
mfonville
Chippa-a
Brandon McAnsh
Steve Kondik
Luca Stefani
Abhisek Devkota
Dan Pasanen
Luis Vidal
Richard MacGregor
Michael Bestas
Adnan Begovic
d34d
Dave Kover
Marcos Marado
Christopher Tate
Ricardo Cerqueira
Danesh M
Yvonne Wong
herriojr
Raj Yengisetty
Joao Figueiredo
Matt Garnes
Roman Birg
dhacker29
Gianmarco Reverberi
Michael Bestas
Arne Coucheron
Michel Weimerskirch
Brinly Taylor
Dave Daynard
Chirayu Desai
neatchee
Lorenzo M
Ricardo Cerqueira
Steve Kondik
Les Prock
Samir Ibradžić
Matt Mower
black
fuzz
Veeti Paananen