* This has been untouched since 2016 and it depends on LockClock
which has been dropped and was also untouched for years.
There is no good weather provider without API restrictions,
so just remove this dead code.
Change-Id: I6540006ce0d7339b7794b6ab207593afb161aa3d
The service will offer updateUserConfig, getUserConfig, and
userConfigContains methods, which will be used from LineageParts and
fwb. The service will also observe Settings.Global.BUGREPORT_IN_POWER_MENU
and Settings.Secure.LOCKDOWN_IN_POWER_MENU to update the GlobalActions
dialog when these are updated.
Signed-off-by: Gegham Zakaryan <zakaryan.2004@outlook.com>
Change-Id: I46663ab1ffe6f8d8b2a3dc7dbe54a65b7a62046a
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 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
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
If the user did not set a custom hostname, the settings service will
set net.hostname to null.
Only set net.hostname if the user actually set a custom hostname.
Change-Id: Ie9cc84e5e8c9468a7e698896e2b21c14a37ebffc
Signed-off-by: Alexander Martinz <amartinz@shiftphones.com>
* When onboarding, the notifications show up properly
* Once you disable any of the notifications, none of them vanishes
due to the logic being inverted:
We want to cancel the notification if the warning is not allowed!
Change-Id: Id3f3b3c9e184cc11d2909dd1e0f7859e32588728
* Fixes the wrong power profile after rebooting the device, if before that low
power mode was turned on.
Change-Id: I6008433b5e304a0f168ba9c7eeb189f4d3e83347
