Required because the lights need to be turned off late in boot
(e.x. during fsck for disk health), and before, blank_screen
accessing light encountered a race condition where if it didn't
get scheduled before all of the processes which were getting
shutdown were getting killed, the screen wouldn't blank.
Bug: 74976325
Test: adjusting brightness continues to work
Test: screen blanks during shutdown at the correct time
including when an artificial 5s delay is inserted when
the phone normally fscks (which can also be quick)
Change-Id: I57ebc11d7ecf57ee327c681455712f4b53de6fd3
Convert clearkey plugin to HIDL to support drm HAL v1.1.
Add SELinux policy for android.hardware.drm@1.1-service.clearkey.
Test: CTS test
ANDROID_BUILD_TOP= ./android-ccts-tradefed run cts-dev
--module CtsMediaTestCases
-t android.media.cts.ClearKeySystemTest#testClearKeyPlaybackCenc
bug: 69635855
Change-Id: I61e9c272c2a2788fd07d5c12921d28c785661b77
Leaving 1.0 in the old format and 1.1 in the new format
since this is agaisnt FCM 2 which requires 1.0 (this makes
sure that OTAs work).
Bug: 73556059
Test: vts_treble_vintf_test (DRM served in 'HalsAreServed')
Test: ota 3/15/2018 build -> ToT + this
Change-Id: I82e6f9fe0b29b15c2e79e92eb9b2abdbab615a71
Test: regression test on the board
Bug: 38184704
Change-Id: Ife559125850277865451f92ea862e7ec47fc9da7
Merged-In: Ife559125850277865451f92ea862e7ec47fc9da7
Cherry-picked from master
Signed-off-by: Kevin Rocard <krocard@google.com>
To abort inet receiver thread, an abort
message must be sent explictly to loopback address.
For reciever to receive abort message it must be
open to receive messages on INADDR_ANY and not
just specific IP address.
CRs-Fixed: 2462833
Change-Id: I9ab3266d582bc774655fcabfc086dab33010f7d8
When qrtr socket receiver has restarted, need a way to inform
sender so sender can restart the service discovery process
Change-Id: Id665da649e0962691277124b42f1ee9cc6160fa8
CRs-fixed: 2445555
(1) Add support to report out calibration confidence in position
report
(2) Update gps quality of GGA, mode indicator for GMC and VTG
NMEA sentences
Change-Id: Ia1aa5283deffed6638172b90a41b481c2d199229
CRs-fixed: 2438838
This allows HAL to request locations into AFW
even when Location is disabled in Settings.
Change-Id: I0c1d4fef55937f3094980dad29ff09d212f541fe
CRs-fixed: 2475037
Fix the issue that SV in use mask isn't set correct
in reportSv function in GnssAdapter.cpp.
Change-Id: Ie90fc4b938875817b105745cf531ee8dc31e74bc
CRs-Fixed: 2473868
loc_service_mask should not be populated with any
SAP(Basic or Premium) value if the SAP value is
MODEM_DEFAULT.
Change-Id: I665bb90e4a814dc31bed566cc0b2ecffcfae52ac
CRs-Fixed: 2457874
Redesign the inet sender and receiver to
be able to accomodate udp and tcp types into
one base class.
CRs-Fixed: 2429102
Change-Id: Ie138839a5c8842813c99053816e06e4ed7f6b314
Move basic location info to top so if a new field is added to
GnssLocationInfoNotification, it will not impact the basic
location info.
Change-Id: I362ee0f6f09c10e3df64ed6993b73a256690c38d
CRs-fixed: 2468348
Qrtr and Qsock bot have createLocIpc*Sender and Recver
APIs in LocIpc. But Qrtr is really next gen of Qsock.
The two will not co-exist. Their existence depends on
kernel versions, i.e. 4.9 and earlier is Qsock; while
4.14 and later is Qrtr. Having 2 sets of APIs doesn't
make sense, as client would have to know what are the
right ones to use, which there is really only one set
of backing implementations.
Change-Id: Ia473f282bb271ae213d7dc5020b0b8c7b0a8cb8f
CRs-Fixed: 2466857
Cross processor communication needs explicit sized structures.
Avoid using platform defined values like size_t which may
vary from 32-bit to 64-bit.
Also use explicitly defined timespec32_t structure that will
only use uint32_t fields.
CRs-Fixed: 2428163
Change-Id: Ida72f53ac672d9c9b86879bb9861cecefe6f8c6d
We want to avoid reporting locations to AFW while
measurements is active but tracking is not active.
Change-Id: Icbb581199e6f5eba3cfe81cb6ab39337bb7ea51a
CRs-fixed: 2441384
On cleanup, the locApiStopTracking is called regardless
if a session is active or not, where this error would
be printed. This is an expected case, so it should not
be an error print.
Change-Id: Ieb10d159ad61a212821ef897d50d635354557cca
CRs-fixed: 2461760