* Buffer got corrupt because of the mNumFlexPlanes member.
Use fixed value of 4 instead and exclude the member.
* Usage bits were not filtered properly
Change-Id: I7ee9fa73f896c505403447ae118a76d9f53e00a8
New herolte OUI observed: 1c:70:22
Checked on hwaddress.com
Change-Id: I4a2c15e315b46af81f815114cf85f0d1cced87f3
(cherry picked from commit ba6c738c2f39fc1011ae5f61067f84b1bf430111)
* Sometimes, the modem is sending 1-2 extra fields with
the country mcc, which confuses ServiceStateTracker
* Drop the extra data here, instead of in our RIL class
[haggertk]: Forward port to ril-caf on lineage-15.
Change-Id: Ifbec67bb0dac271226bd8b5471deaf6a2ef33f2b
Current get_pcm_device return always first finded pcm_profile.
And out->pcm_dev_list always have only pcm_device_playback pcm_profiles.
But if we need use deep_buffer pcm device
we need use deep_bufer pcm_config - current hal
don't did this...
And we configure out->config in adev_open_output_stream
function with proper pcm_config (deep or no).
Change-Id: I86fdb18202afb0e83393f32830d57c929f174ae6
(cherry picked from commit 39d1d019965d04ddfad2c643de53cd5501803aa4)
Android expects a FINGERPRINT_ERROR_CANCELED error-message if a
fingerprint authentication-requested was cancelled.
As bauth doesn't deliver such a message on its own, we use the
already notify-wrapper to send a message to Android if the
authentication was cancelled by bauth to allow a proper operation
of the fingerprint-service.
Some devices (hero, hero2) with the fingerprint scanner embedded in
the home button need this for the "config_fingerprintWakeAndUnlock"
option to work reliably.
Change-Id: Id5ec866a7608885925687a1927e0e6085e9b6cff
Ref: BUGBASH-1422
* Checking numInts and numStrings for strict equality when
we're not looping is dumb, because Samsung is notorious
for sending extra information in their RIL
* Check if there's *enough* data rather than the *exact amount*
to fix a bunch of invalid response errors
Change-Id: I14bc37240e5760b4629fcb74b64f25ad95d4fdfc
Before:
if (response == NULL || numStrings != 3) {
After:
if (response == NULL || numStrings != mqanelements - 2) {
This patch fixes the logic so we don't change the value check.
"mqanelements" is not related to getOperatorResponse, so get get rid of
the affected code.
Change-Id: I86c6ae7b7492a5d04fbc8dc415c4f615e7d05bab
* Samsung now supports many more modes than just inverted colors
* Add strings for these extra modes while we're at it
Change-Id: If2a469c994658d521d98b91adec1a19badb8092f
* It just so happens that not all devices will have the
same options available, so allow them to specify what
they have without breaking tranlations by moving the
scenario names into individual strings from the arrays
* Update a few strings to be actually translatable
* Fix an off-by-one error for every display mode after
"LineageOS (default)": UI is the same thing as the
default mode, so remove it to make the mode selection
actually choose the user-selected mode
Change-Id: Id5d659d79c10ea097c35b7416ef7c1cc93937756
On some devices, certain input and output mixer controls share the same
endpoint, which means that if an input stream is disabled (and the mixer
is updated), that shared endpoint may be disabled as well.
This would result in no audio, because no one is aware that the output
stream in fact does still need the shared endpoint to be enabled.
We prevent this by enabling the output mixers after disabling input mixers,
if any.
Change-Id: I4d80fcd0648a11099f27177da3cd29095b6a8c34
(cherry picked from commit 507e8ce5bffb36fae8b1cd4e5498fa19a6273ee6)
