* Constructor is called during boot, adding boot time where
it's not necessary
* Use the first actual call to a function to parse the list
Change-Id: I02548d004c5d78db65c872247cd36a0405d826ea
* Now that there are more users than just call log, it is better to parse
the XML-file just once
* Keep an instance around for the various users of this class
Change-Id: Iff1510dc40d68a211a6a1c5f19e4ca9ac64c3fcd
* When calling the number with intl. prefix it is currently not hidden
* Remove the international prefix before checking th number
Test:
Before:
116006 - hidden
+49116006 - not hidden
004911606 - not hidden
After:
116006 - hidden
+49116006 - hidden
0049116006 - hidden
Change-Id: I72ec2c9a4da87ef243c59c8c4bab33585fdbd854
* Instead of only checking the current or default MCC to hide a number,
see if any of the connected networks would hide a number
* This makes sure that e.g. for multiple sims (e.g. living next to the
country border, having one sim for each country) and accidentially using
the wrong sim for a call, the number would still get hidden
Change-Id: I2692d00217d3143fd55122cee9064528bb09352d
* In order to access the classes in Dialer, we need to expose them
This was extracted from the original implementation in Telecom
Author: Olaia Segovia <olaia.segovia@bq.com>
Date: Thu Mar 16 08:40:30 2017 +0100
(1/2) Make sensitive phone numbers not to be shown in call log history.
Considering sensitive phone numbers to be, hotlines dealing with
violence against women.
In the EU, these numbers do not show up in the phone bill.
In order to avoid these phone numbers to be listed in the Call Log, we
have implemented a new XML file which is parsed with phone numbers
from different countries to be filtered. This file needs to be copied to
device via desired Android.mk file in order to be able to process it.
The comparison is made checking the network MCC the SIM is connected to
in order to consider roaming and multisim scenarios.
Test: CallLogManagerTest.testDontLogCallsToSensitivePhoneNumber PASS
Change-Id: I4a59ff0577942ce56924f1a434ae0a3a38eacc62
Signed-off-by: Olaia Segovia <olaia.segovia@bq.com>
Author: Paul Keith <javelinanddart@gmail.com>
Date: Thu Jun 22 19:40:56 2017 +0200
SensitivePhoneNumbers: Handle lists of MCC codes
* Some countries have multiple MCC codes, so handle it
* In the sensitivePN network field, enter the list of
MCCs like so: https://review.lineageos.org/178233
Change-Id: I34225473404b2be2640ea9ab05691dc985c49fa0
Author: Paul Keith <javelinanddart@gmail.com>
Date: Thu Jul 6 16:12:12 2017 -0500
SensitivePhoneNumbers: Fix number comparison
* Currently, we just compare the strings for equality,
which results in incorrect detection of sensitive nums
a lot of the time, because adding (or removing) the
country code is enough to make the detection fail,
meaning the call to that phone number is logged
* Use Android's PhoneNumberUtils comparison method to
fix this, since it takes these factors into account
Change-Id: I26ac180f8a6552cf87a4bada1d370f0ebb884ee1
Author: Michael W <baddaemon87@gmail.com>
AuthorDate: 2019-09-07 18:34:57 +0200
CallLog: Fix improper call to SensitivePhoneNumbers
* isSensitiveNumber expects a subId to be passed, but with the current
implementation gets a PhoneAccountHandle
* Actually pass the subId and make the call use an int, while on it
* Fall back to the default subId only when we get an
INVALID_SUBSCRIPTION_ID
Change-Id: Id6d64f2c9f76d94d1b4d9851317ea2cc7e07323b
Change-Id: I241c1652105b82d1d15549332cb6e274d7c726ce
* Fix bp and manifest to work with AndroidJUnitRunner.
* Remove broken tests (we no longer intercept in fw/b
settings provider and QS_USE_MAIN_TILES was removed).
* Tests pass when executed using:
adb shell am instrument org.lineageos.lineagesettings.tests/androidx.test.runner.AndroidJUnitRunner
(see README.md for more info)
Change-Id: I3fcf4885c61106f43e99847293220afee78e2f6a
* Works around:
lineage-sdk/Android.mk:116: error: BUILD_DROIDDOC is obsolete. Droiddoc is only supported
in Soong. See details on build/soong/java/droiddoc.go.
* Need to reimplement in soong later.
Change-Id: I1a3756b4e4779dc27fe52ed31d767ca660756298
API changed here:
633a13e2fa (diff-944e798f679ef205433bd711345d06dcR75)
Fixes:
AndroidRuntime: Caused by: java.lang.SecurityException: The authority
unknown does not match the one of the contentProvider: lineagesettings
Change-Id: I5fe85fee777f919824e6a2ff78986e2d736e0267
* moveTaskToFront() now has 2 nullable parameters at
the beginning:
- IApplicationThread appThread
- String callingPackage
Change-Id: I761784bdb3918021a0848e8ee31baa0818540bb1
In particular, fixes packages/LineageSettingsProvider/tests/Android.bp
which otherwise results in errors about unknown properties tags
and instrumentation_for.
Change-Id: I1d44fce77765a77ed6f3c23763f439a216eaefda
* Use getFocusedStackInfo() to check active task, also do general
cleanups for this class. Hopefully this will get rid of the
strange issues of "kill foreground app" feature.
Change-Id: Ice1ca8e088ea4fec050fa171d990cb938dd3272c
Problems with current TrafficStats.getTotal[RT]XBytes()
implementation:
* Tethering related traffic is not counted at all.
* If you have a VPN active, stats are double counted.
So change the approach and track traffic on all non-VPN Internet
capable networks since:
* Tethering traffic is included in interface specific stats
(unlike getTotal*).
* VPN networks are excluded so no longer double counted.
* Works correctly regardless of hotspot "Allow clients to use
VPNs" hotspot setting.
* Works with simultaneous wifi ap and wifi upstream.
(WIFI_HIDL_FEATURE_DUAL_INTERFACE = true)
Change-Id: Ic1135f10388b5be427202b092acd1444f94bd2b6
* LiveDisplayConfig isn't instanced until boot completed, thus if
LiveDisplayManager is instanced earlier, null is always returned.
Change-Id: I003886ffced86a5a82dec25a4cc7b542da0f2331
* On HWC2, setting "Display mode" to "Automatic" and disabling
"Automatic outdoor mode" at the same time makes no difference with
setting "Display mode" to "Off" alone. Obviously this is redundant
and could confuse the user, so simply ignore the "Automatic outdoor
mode" setting on HWC2 to reduce redundancy.
Change-Id: I6858571a6b9ded3540fd3d936499878f57a7b3d4
* This capability is set by ColorTemperatureController on HWC1 which is
not used on HWC2, but it controls whether to enable automatic outdoor
mode, thus advertise it here.
* Set the default mode back to MODE_AUTO.
Change-Id: I2061cdb9ca5991e60dc9c4b3d566dd811c3c8936
This reverts commit f781a9399a.
* Twilight tracker and display mode are still used by
ColorTemperatureController
Change-Id: Icaf2a93befd56478eb2307d6f25da49c7c3fd73f
* When SuW is not yet done, the notification is already posted
* This results in an english notification text when the SuW is finished
because the notification doesn't update when the locale changes
-> Listen for locale changes and post the notification again (= update)
Change-Id: I920a52c5c85c91adb7333a20d410a5464e80a812
* Having decided to use AOSP's night display feature in favor
of our equivalent implementation, then we should take care of getting
the latter completely disabled. Not only it can happen that a user was
likely using it and enabling night display will now cause color
transformation matrices to be applied twice, but also because there
are resources being used for nothing.
Change-Id: I4ba7f643bf9e3d3b9bda17102b41668644e22ba1
* Handle the migration for old settings and default
to Android's stock battery style.
* Hiding battery icon is now achieved using icon blacklist
via system tuner settings.
Change-Id: Ie41d71c774a34abe225e2c0a6a0a9fd4316189cd
* Update 2x a minute rather than 1x a minute as a result of dropping
TWILIGHT_ADJUSTMENT_TIME from 1hr to 30min in an earlier change
* Use an AccelerateDecelerateInterpolator for transitioning from day
to night mode and back to make the transition smoother for the user
* Update copyright while we're at it
Change-Id: I438f265c6cd9a2487b75744beccaf2bbac21b36e
Parts uses notifications to preview custom notification lights.
Since Android O we got NotificationChannels and the internal API uses
the color values of the channel instead of the color set at the notification.
To prevent unexpected breakage in future, introduce a flag to be used for
providing preview colors in a bundle to force said color.
Also introduce flags to control the ON and OFF duration.
Change-Id: Ifbb7995a19d95b6ddb2627c1b14dd201f9dc5430
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
