* In O, the default setting for mobile data always active was
changed from off to on, meaning that when non-WiFi tethering
is being attempted, more than one connection can be active
* Since the first active connection type in this overlay is used,
reorder the values to get WiFi connections first, and then
any type of mobile data connection, instead of vice versa
Change-Id: I41f31ba1a2793e209ff439c9ba28a390fecdeecb
* send_mic_mute_to_AudioManager hasn't been doing anything
since Android 4.4, therefore there's no reason to keep it.
Change-Id: I74ed33265fccd59def5c2f9e67a9e8a28ce4dbc9
The .rc file should be on the vendor image, or can not boot
with generic system image.
Bug: 63051055
Test: Boot with GSI to home screen
Change-Id: I1e2ebe5d23a6cf5a4176ee33613ef621b4b558cf
* camera.device impl is a dependency of camera provider
therefore there's no need to add it to PRODUCT_PACKAGES.
Change-Id: I3ae211965a31b5f85af3dd0fa1c7811b802586c3
* Mounting /system and /vendor partitions is handled in kernel now,
however removing the entries from fstab caused issues building
the OTA. The workaround was to have a separate fstab, but turns out
that simply setting the recoveryonly flag does the trick because
those are then ignored during a normal Android boot.
Change-Id: I2944384d0a1c41bc9f9f51e2e29daff2bed0a0f4
* Led capability LIGHTS_ADJUSTABLE_BATTERY_LED_BRIGHTNESS was recently
added to the Lineage SDK. Declare such capability, since our targets
don't have RGB battery leds, but the lights HAL supports brightness
control via the alpha channel for battery and notification lights.
Change-Id: Ifcdc4816d27f7b781712dde6eb9b2e4f73449c6c
This change is to add some more libraries needed to
be present in the vndk-sp library set. Also, move towards
a better the mechanism to build vndk-sp.
Signed-off-by: Isaac Chen <isaacchen@isaacchen.cn>
hal daemon
Move hal daemon socket creation to loc_client directory
Define uid/gid for locclient
CRs-Fixed: 2260194
Change-Id: Icaac885c19cd65b11254bb93b6a938b2d4595761
The event mask can be retrieved in the context of
client thread as zero and then queued up to go to
msg task thread. By the time the msg is actually
handled in msg task thread, the actual event
mask at LOC API layer may have already changed, but
this mask would then be overridden by zero. This
can cause no modem events to ever come, including
position reports.
The fix is to not retrieve the event mask in the
client thread, but instead wait for msg to be
handled in msg task thread before retrieving it.
Change-Id: I48562d028bbfa187732686c060b5cdd62c6d5a89
CRs-fixed: 2219519
GNSS adapter to block CPI injection for CPI originates from modem.
One source of the fix is QNP fix from modem. Only fixes that
comes within time threshold and with latitude and longitude
falls within the same proximity will be blocked.
Change-Id: If67a164d1e1c75735979f048a9f8dc93f0b0a41f
CRs-fixed: 2260721
