Clearing and rebuilding modem cache (e.g. mdmddr, mdm1m9kefs1,
mdm1m9kefs2, carrier, and ddr partitions for MDM devices) is typically
necessary after modem firmware upgrade. However, NR is disabled in
Moto's modem firmware by default, so choosing NR results in "No signal"
after rebuilding modem cache with custom ROMs installed. Users have to
go back to stock once to make it work again, which is a huge pain.
It's observed that stock ROMs control NR via a custom RIL request, and
choose it based on carrier config and user preference (yes they have a
toggle in system settings) after SIM provisioning. Here, we implement a
service to automatically enable NR and DSS in the same approach, so
that users no longer need to go back to stock after upgrading modem
firmware. The implementation is based on telephony-common.jar,
qti-telephony-common.jar and qcom-moto-telephony-ext.jar from nio.
You're suggested to check if the magic numbers and payload formats
match your device's stock ROM before using this service.
Change-Id: I5ecfae93717fe87e6b1c1a75caa674b466403391
* White stroke color makes it very hard to interpret icons in dark mode
Before/After: https://imgur.com/a/1vz6SON
Change-Id: Idaedaa4bb62a42253c1000001476ccfedd01b790
* Android.mk because we link libqsap_sdk which is Android.mk.
Co-authored-by: Dan Pasanen <dan.pasanen@gmail.com>
Co-authored-by: Erfan Abdi <erfangplus@gmail.com>
Co-authored-by: Prema Chand Alugu <premaca@gmail.com>
Co-authored-by: Jeferson <jroliveira.oliveira301@gmail.com>
Co-authored-by: Nolen Johnson <johnsonnolen@gmail.com>
Change-Id: I97b856d1bf6d390c65cb0043e8ffe4d3d0d55d75
* Use Theme.SubSettingsBase for theme
* Replace PreferenceActivity with CollapsingToolbarBaseActivity
* Add Titles to preference screen
* Remove onOptionsItemSelected and where necessary move to activity
Co-authored-by: Erfan Abdi <erfangplus@gmail.com>
Change-Id: I87af15f5e165aa7bcd556eb2b716c0ce624ca4e7
* Remove unused classes, methods, interfaces, imports
* Reorder imports
* Add final where applicable
* Fix line lengths
* Use local variables where possible
* Replace deprecated Vibrator.vibrate(long) with the successor
* Simplify conditions where they are always met
* Rearrange tags and remove unused schemas in resources
* Merge ScreenReceiver into the service
-> a separate, instantiated but never called-into class makes
one think it's unused
Change-Id: I05cff7ecaf424c166fedceb1f4f8963164c6085a
* The behaviors of stow and proximity sensors are pretty similar, so
there's no need to use both at the same time. Simply use the stow
sensor to handle both hand wave and pick up gestures.
* Switch to timestamp associated with the sensor event to determine the
operation while at it.
Change-Id: I39767cf7b2e48bc2b0baabfac1e47240012f71d6
* This sensor gets triggered by any physical movements of the device.
Slight shakes of your table could even wake up the device, which is
clearly undesired.
* The ordinary pick up gesture is detected by the flat up sensor.
Change-Id: I1fe492e8e23f09adebab38f123f6bb497cc7a0f4
Targeting S+ (version 31 and above) requires that an explicit value
for android:exported be defined when intent filters are present
Change-Id: I2ce2b2cd1dcd69e343ae8577587483b19d825fdc
* Actually callback is not registered and never triggered. When user enabled torch with power long press or with qs tile and then do the gesture to disable it (or the other way around), he will have to do the gesture twice since boolean has not been updated.
Change-Id: I03e88b6975300943fbeaf536fdf8552b9e3b3396
* While c9999dacb17 introduced options to false, whole code sets to true as default.
Bring it back to default code behavior
Change-Id: I32cb9851c81282e0440f5a0d1654f31b37e35c91
* Make follow system accents as well
Change-Id: I8ea63f82e079ba7868313c14e4973f9c1dd9789d
(cherry picked from commit c9999dacb17c2372be960a05789b603f827dad2b)
* Looks like some variants don't have a CameraActivationSensor, so let's
remove the preference as the user's choice won't have an effect anyway
Change-Id: I7d157a992a6cb9ee333752772bc5e3b647b614f2
* Registering a non-existing sensor causes a RuntimeException which crashes
the Settings app which in turn takes down the whole system
* Change the RuntimeExceptions to normal error loggings
Change-Id: I18a73adc311bec6b70440a3266c7e2af74baa55a
