It's sometimes useful to know what physical device you're using.
CMHW SerialNumber and an "ro.serialno" property already exists, but
are not guaranteed to be unique. Different OEM may use overlapping
numbering schemes, and sometimes placeholder like "012345ABCDE" are
used.
Attempt to work around these shortcomings by defining a new
UniqueDeviceId class that provides a globally unique device ID that
is both deterministic for a given device and designed not to overlap
with IDs of any other devices.
Change-Id: I3f426972558394ba8e78261273ac8521aa603327
Since the migration is invoked even on a clean flash, with
no means of knowing what scenario we're coming from. Assume
that all null values are to be dropped and default values are
to be given precedence.
Change-Id: I10eb2f4650c379422268423dbc011b49f77ed910
TICKET: CYNGNOS-1721
This fixes the following errors during bootup:
QSTileHost: Error creating tile for spec: visualizer
QSTileHost: java.lang.IllegalArgumentException: Bad tile spec: visualizer
CYNGNOS-1722
Change-Id: Idd45ef73beb004fb4afb310bb335f3cc85b08330
The database is innaccessible during creation through
the android resolver interfaces, thus, no defaults were
loaded even though the code would execute.
So rewrite the DatabaseHelper to create a singular bulk transaction
per table when default settings are to be loaded, and provide
verification tests for the CMSettingsProvider.
TICKET: CYNGNOS-1706
Change-Id: I3d8c5f25704ec9620fe57b82865531fb976a516f
Always add new interfaces to the bottom of the aidl
or you break backwards compatability.
Change-Id: I376fbe6869d3fb0002822112eb05d9acddd51572
TICKET: CYNGNOS-1699
Some of this exists in the PersistentStorage implementation, but it
was never formally documented in the APIs. Inherit the cmhw implementation
error checking & move it into the service.
Add tests to validate the new restrictions & a test that was previously
failing.
Change-Id: I3ecda29fdd28bbc4e6d8ccce7511c4644065ea46
Services that extend KeyguardExternalViewProviderService should also
include this newly defined action in an intent-filter within the
<service> tag in their AndroidManifest.xml. These services can also
include meta-data that defines a configuration xml which will be used
to define a settings activity that can be launched within a yet to
be defined settings/configuration UI.
Change-Id: I0a5ca09cf6f63413d067f89a9757137102dd09f6
TICKET: CYNGNOS-1687
Lower protection level of THIRD_PARTY_KEYGUARD permission from
signature|privileged to normal.
Change-Id: I464daba67a66e88efe6219cec2663a07d15ab3ed
TICKET: CYNGNOS-1689
Setting to keep track of whether a QS tile has disabled the keyguard so
we can display this state elsewhere.
Ref: CYNGNOS-1513
Change-Id: If6ecb78a028d9d74d70bc2f1cd584ac9ac83a2d1
Signed-off-by: Roman Birg <roman@cyngn.com>
Contains contants utilized throughout Settings/Systemui
to log usage of specific fragments, settings, or panels.
An extension of Androids MetricsLogger.
Change-Id: I44eff06f87313fca8c2ecf78b7bdea9055956e3c
Created the AndroidTestCase unit test
Added functional testing for airplane mode, which can be restored
without contaminating other tests.
Also added setZenMode testing, which currently contaminates other
tests. But we will allow for lack of a better way
FOR-156
Change-Id: I2ab5642c60f41266d9de8aab897e4852e872ad38
Since the locksettings database is not backed by a provider, we cannot
use a ContentObserver to know when a change to the third party keyguard
component has occurred. Instead we broadcast that it has changed.
Change-Id: I1384b8ba445dcb8d0c571ded1c68b297182f086a
TICKET: CYNGNOS-1481
Since LOCAL_JACK_ENABLED isn't flexible enough
to have generation of both java archives and jack
binaries, we can work around this by having a
secondary module defined that disables jack compile.
Change-Id: Ied647b659c13b672621d82af536d1ed447d5f7fa
Previously, a new method was added to IPartnerInterface.aidl in the
middle of other methods. This needs to be added only at the end to
ensure backwards compatibility with older versions. Reorder the methods
to place setZenModeWithDuration at the end.
Change-Id: Ib9f9c7acceb928db5acc76e7351147074b230141
See http://review.cyanogenmod.org/#/c/125484 which brings the
changes to allow third party components to set and modify alarms,
and which actually makes use of the ClockContract in the SDK. This
flushes out the fact that the ClockContract in CM13 added a new
state.
Change-Id: If6d57727298c0a749055337809b9a66e91078a01
Matt Wagantall