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
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
* Don't call ConnectionManager.get* methods from within the callback,
docs say it's racy.
* Remove the NetworkState struct whilst we're here. It was
useful for debug during development but is no longer needed.
Change-Id: Ia1abbdfa31b258c38ba809844340d0dc06e5bd07
Audio files were moved to /product on Android 10.
Moreover, align with AOSP and use the wireless sound
for wired usecase too.
In order to perform upgrade properly, handle the migration
for custom charging sound setting.
Change-Id: Ifb2085e3f56d777091d66544a72cdd75c843fb56
*) Regular interface stats don't include hw offload tethering
statistics so collect and include them in our traffic
calculations.
Change-Id: Id72577429840f65ae20d7b80e7490ec41d826579
* This conflicts with AOSP gestures implemention now, and
the framework part is hard to port.
* Furthermore the original implementation has the following
bugs/issues:
1. Pressing power button or double tap does not wake up the device
2. No soft-key buttons when opening the keyboard
3. Probably more
Change-Id: Ia233c3b9d0aa7426f0fd15dffe4da203b4e09b1d
* Fixes the wrong power profile after rebooting the device, if before that low
power mode was turned on.
Change-Id: I6008433b5e304a0f168ba9c7eeb189f4d3e83347
