Make sure that the option has effect ONLY when battery is uh...
fully charged.
Additionally add previously missing logging.
Change-Id: Ib232d0ea6652230a2435be6931f964dc04a30f71
* In order to be able to reference this package
in non-platform packages, we need to compile
this against the current sdk
Change-Id: Id87059d876854907d947e5802a04db634435c6ed
* Allow each item to carry additional infos:
<item>
<name>SomeNameHere</name>
<number>1234</number>
<someTag>someValue</someTag>
</item>
* We treat all but <number> as optional
* This way we can show info we have and skip what
we don't know
Change-Id: I724d9ac25ce8a0ae7f69ec513ba9796b06c9e7f2
* In order to also mark numbers as sensitive when calling to your home
country, check the sim's operator as well
* Also move the fallback mechanism out of the "else" in order to perform
as many checks as possible to not miss any case of hiding
Change-Id: I23b67145406793506be657df8b62f5d09b5a2a18
* In certain network situations (e.g. while changing from wifi to
cellular) it can happen, that the HashMap is modified while the stats
are currently being recalculated
* We can prevent this by moving adding and removing of any network
to the same handler so the callbacks can happen without breaking the
flow
* Move the existing code in handleMessage into some little helper
methods so it stays simple and readable
Fixes: https://gitlab.com/LineageOS/issues/android/-/issues/2870
Change-Id: I38c0c27a4f76fab5aeee013beab346c088bbbd59
On FDE we check wether keyguard is enabled before starting non-core
services like ProfileManager.
All method calls are already guarding RemoteException for a binder
fail, so just throw one if getService() fails.
Change-Id: I44a3a5ea56a5277d84d96a0bc2c7135433811e20
The default is no action. Furthermore, split screen is not supported
on Android Go devices and being that one the default action makes it
inconsistent with Go-aware ButtonSettings code in LineageParts.
Change-Id: I21e834f8557d0d0dc81af8443bcb8db30300ded0
For Spotify and other players that allow music controls for
remote devices (PC, PS4) through the media notification
Change-Id: I38887f8b1cff1a0c1e3adadbfe37d5af59b5cdcc
For as strange as it may be, so far the visibility of the features depended
on the default value of config_{button,keyboard}BrightnessSettingDefaultFloat.
This was nonsense, because it would force everyone to overlay that default
with a value of 0.0, just to make the unsupported feature go away.
Change-Id: If605238bf30642db057b06b03224d9a8b4451f12
Since Android 10 arrived, the support for manual SIM provisioning
was never ported. In fact, there seems to be a way to do that
using some bits of AOSP code.
This way we get rid of the telephony-ext dependency for good.
Change-Id: Ibe4e430d696782032b7d9840ab36db040c3a4df9
According to the lifecycle of a SystemService, onStart() is called to get
the service running and the service should publish its binder interface
at that point. First of all, ensure to do that and then do the real work
once boot is completed.
This was actually the root cause of the issue that commit c06e32d
addressed (not entirely correctly). Although the crash was no longer
observed after that commit, the proper fix is actually this one.
Change-Id: I42dc7182ba3d0db5413709de229ab9c0c4926df6
According to the lifecycle of a SystemService, onStart() is called to get
the service running and the service should publish its binder interface
at that point.
Change-Id: I99031807f45d8d7e048582749b1ba6885aa12af4
According to the lifecycle of a SystemService, onStart() is called to get
the service running and the service should publish its binder interface
at that point. First of all, ensure to do that and then initialize the
rest of the stuff only during PHASE_ACTIVITY_MANAGER_READY boot phase,
because services can only broadcast intents after that phase.
This fixes a particular issue, that was causing LineageParts to crash
while starting System Profiles activity.
Change-Id: I8a397523aec8b5008da3e596eee23463618c8489
Ensure that the variable is not null when removeNotificationForFeatureInternal(int)
is called so to avoid the NPE:
E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.app.NotificationManager.cancel(int)' on a null object reference
This fixes LineageParts crashing when disabling Trust notifications.
Change-Id: Ia0fa793378116101821a7bd424e0859869db48f5
* Fixes really strange looking errors while building rild:
FAILED: ninja: 'out/target/product/generic_arm64/vendor/bin/hw/org.lineageos.platform-res.apk', needed by 'out/target/product/generic_arm64/vendor/bin/hw/rild', missing and no known rule to make it
Change-Id: I0fb91383829b9b478b3dee9686e9e719ea3ed695
* Fixes compile error:
lineage-sdk/packages/LineageSettingsProvider/Android.bp:17:1: module "LineageSettingsProvider" variant "android_common": platform_apis: platform_apis must be true when sdk_version is empty.
Change-Id: I3024ef46e729fea6f85ed9e84acf8ab5a9f05cb1
(cherry picked from commit 7954524e3cc618830f0bf7b23687bf222ecd285b)
Bug: 134566750
Test: m
Change-Id: I0260942108a13cc5e9bed1d6005abfb8daffe0ac
Exempt-From-Owner-Approval: minor build change
