Update instance name of QcRilAudio HAL.
Mutliple (one per SIM) instances of
QcRilAudio HAL is required.
Change-Id: Ied34684509f1db37727880116bab785fddaaded3
This reverts commit c043816b3c.
The reason of the revert is to check for the application start time
regression that may have been caused by the CL
Bug: 38317397
Test: None
Change-Id: I7edaf75eeebcecb848b38a9b7eff2bdb1f233cdb
Signed-off-by: Ahmed ElArabawy <arabawy@google.com>
This change applies uprev of configstore to init.hardware.rc and
manifest.xml
Bug: 37727469
Test: Built and tested on sailfish
Change-Id: I64930ca7dfceb66a1cf7a52b43fd378810ff8dad
Add a full binderized implementation for Power hal
Many subsystems (e.g.wifi) could be living on an
independent power island (sourced from VBatt directly)
and might even have their own dedicated XTAL to source
their clocks. Since these SOCs are capable of
autonomously operating (while the platform is in one
of the sleep states), they are still drawing power
from the VBatt. Hence it is critical to understand
the (SOC) level low power statistics as well when
the battery level changes and be able to find any
correlation in event of unexpected battery drain.
This commit adds the support of the Power Hal 1.1
to wahoo based devices(that includes Muskie/walleye).
This includes the new api for wlan specific power stats
Bug: 29339696
Test: Manual
Change-Id: Iee4e38f2d9ced31f8b6a333b535fa1d9a302ec26
Signed-off-by: Ahmed ElArabawy <arabawy@google.com>
Change the name and interface of UCE HAL to IUceService/uceservice0
Test: Ensure imsrcsd comes up and connects to UceShimService
lshal should show the proper HAL
Change-Id: Ic6c1fdbbd44411519fa3313d5d03075616c8f6ce
Bug: 36097673
Test: mm && tested on Walleye to make sure QCOM driver load.
Test: RS CTS tests pass
Test: Imageprocessing tests pass, and confirming running on GPU.
Change-Id: Iaca74a8e90d9fd10e4327bd55d982e95b700ca0f
UCE is user capability exchange functionality where the device notifies
the network its capabilities and can also find out the capabilities of a
different user from the network. Capabilities such as VoLTE,
Video Telephony, etc.
/external/ims/rcs contains the open source code that needs to interact
with the IMS stack in the modem. The UCE HAL acts as a bridge between
the ims stack in the modem and the open source code that provides
the UCE functionality that is used by Android Apps such as Phone and
Contacts.
Previous architecture was as follows:
UCE client app (aosp, system) <--> AIDL (AOSP) <-->
uce_service (system app) <--> (JNI vendor) <-->
(IMS libs: vendor) <--> modem
With Treble we have formed a clean separation between system and
vendor components: UCE app (aosp, system) <--> AIDL (aosp) <-->
UCEService <--> system/priv-app) <--> (HIDL, vendor) <-->
imrcsd (vendor daemon) <--> modem
Hope is that in future the vendor UCE HIDL is absorbed in AOSP and
we can deprecate the UCE Service system app altogether.
Add policies and permissions for UCE HAL service and UCE HAL client to
run and execute.
Bug: 37262741
Test: Check capability in contacts for VT calling
Change-Id: If426c1c046a2acd16ac30f25e15daf4aa0de1383
"default" implies using "primary" legacy device module.
This doesn't change anything for binderized mode, because
the server was only registering itself as "sound_trigger.primary",
so it was the only possibility anyways.
Usage of "stub" (debugging) module is still possible
if audioflinger and corresponding services are built with
USE_LEGACY_LOCAL_AUDIO_HAL=true (added makefile check to ensure
that).
Change-Id: Idc69c2ae1e0a02a7d2134f469f65d6de72aa5fe9
Test: "Ok Google" from screen off state on sailfish
Bug: 36570720
Add the binderized boot HAL service to the manifest and grant
necessary SELinux permissions to access block devices.
Bug: 35810130
Test: Device boots & passes boot VTS test
Change-Id: I4df5ec0ff2f170da31e0748e376cda309802b554
Signed-off-by: Connor O'Brien <connoro@google.com>
Verified: audio in Hangouts, Play Music + EQ, YouTube,
audio over A2DP and USB.
Soundtrigger seems to be working--the device wakes up to lockscreen,
need to dismiss it manually, and then Assistant prompt appears
immediately by itself. Looks to me more like an issue with Assistant
rather than with s/t.
Bug: 35808308
Bug: 36098105
Test: manual
Change-Id: I03c0e04a8f35b7da0bbef9dd32e606a07067ba36
Bug: 36097960
Bug: 36462741
Test: adb shell lshal on device, successfully ran Daydream Home, though I'm
seeing some crashes in various things.
Change-Id: Id1af18701e2021ab8c3de7889ec71c316fe4420c