This got enabled by default on U, and it causes apps like
Chrome and Youtube to set the refresh rate to 30FPS when
playing some videos.
Change-Id: I649bf03d550c2b9726c7957d15ed09e455d874ec
* `libndksensorbridge` was converted to AIDL and is no longer linked to
this static library that contains symbols required by our sensor
blobs. Add a shim linked to `android.hardware.sensors@1.0-convert` to
fix our sensors
Change-Id: I969f97bb15d0abcc71f87352722995db3826e122
Signed-off-by: Woomymy <woomy@woomy.be>
* MediaTek use their own CarrierConfig format, apart from hardcoding
the entire CarrierConfig into the RIL stack (for some weird reason),
they also provide XMLs too, but these seem to specify multiple mncs
per carrier_config entry, which is not supported by AOSP.
* Use a script that allows us to not only merge multiple carrier config
XMLs together, but also create a copy of the carrier config entry
should multiple mncs be specified.
Change-Id: I0987164e083c3983d747b87dccb920892bc63614
Signed-off-by: bengris32 <bengris32@protonmail.ch>
* When the CN RSC configuration is loaded and the device is used on
a non-chinese carrier, RIL crashes are almost guaranteed because
MediaTek engineers are stupid.
* Workaround this by merging the Global RSC configuration into vendor.prop
Change-Id: I930e187d6ed4295a40523a7e8fe932d59ce63478
Signed-off-by: bengris32 <bengris32@protonmail.ch>
* The device's ultrasound proximity sensor is not active
during standby, thus it can't be used as a check before
pulsing. This fixes Ambient Display.
Change-Id: I1fc416247ed13cbfba245f37a4aafeae74ddbff7
Based on observing it's values, xiaomi.sensor.aod reports
the following events:
4.0: Bright environment
5.0: Dark environment
Change-Id: Ie589066bd860a7fed3989092c21aee73686ecea4
Signed-off-by: Arian <arian.kulmer@web.de>
* Use standard sensor type
* Ignore non-wakeup sensor variant
* Ignore events that do not properly match a pickup
[LinkBoi00] Adapt sensor name for our device
Change-Id: I2bab89362aa225344a69c4969096ea9a61ef3033
Signed-off-by: LinkBoi00 <linkdevel@protonmail.com>
* MediaTek ship their own modified task_profiles and
use the V30 cgroups configuration.
Change-Id: I15245ea87b00925597db65f1564e808a094c937a
Signed-off-by: bengris32 <bengris32@protonmail.ch>
This firmware fixes the a2dp crash that was worked around by commit [1]
[1]: e7f12ea3db
Signed-off-by: LinkBoi00 <linkdevel@protonmail.com>
Change-Id: Ibf7816de894e17c59b6b62b9039c74742ccd8b55
* Rearrange power service packages
* Cleanup unneeded power service blobs
Change-Id: I33c6c35164e00f4018d966828fa08dcf6677ca6e
Signed-off-by: bengris32 <bengris32@protonmail.ch>
* Since commit eb57617 [1], the legacy callback interfaces in the Android
AudioTrack system have been deprecated and replaced by a newer callback
interface. Consequently, the user parameter, which was previously part
of the constructor, has been incorporated into this new interface.
* To address the resulting build issues, update the function signatures
to match the new methods. Although AOSP provides a wrapper [2] for this
purpose, it's declared within an anonymous namespace, effectively making
it private to its own translation unit. To work around this limitation,
provide a local copy of the wrapper instead.
* Also format the shim with `clang-format`.
- [1]: eb57617e55
- [2]: https://cs.android.com/android/platform/superproject/main/+/main:frameworks/av/media/libaudioclient/AudioTrack.cpp;l=289;bpv=1
Change-Id: Ieae7df3f5f003538a0319cc77051322a989b93a8
* E init : Control message: Could not find 'android.frameworks.sensorservice@1.0::ISensorManager/default' for ctl.interface_start from pid: 516 (/system/bin/hwservicemanager)
Change-Id: If696de35b0d70e1f67d72be456347c6c7fd691f7
This variable is always false or empty now.
Remove it so we can mark it as deprecated later.
Bug: 241346584
Test: Presubmit
Change-Id: I57cbe875f556bb853d4ea9b1d458c9c554c6bfa5
