hardware_samsung, branch replicant-10

samsung: hidl: light: Use mainline kernel path for brigthness

2020-06-25T11:35:51+00:00

Signed-off-by: Joonas Kylmälä 
Change-Id: I3d954bd44b0ae638bafe419f79a1dd2c18f19563

hidl: Add standard timed_out vibrator service

2020-06-09T08:21:40+00:00

Change-Id: I48164e9adfa52cd223c5a2925fa3b48417a6e50c

hidl: powershare: add vintf manifest fragment

2020-06-09T08:21:05+00:00

Change-Id: I7fddba246ce58127192b7cebcaa09da667e33c91

fingerprint: inscreen: add vintf manifest fragment

2020-06-09T08:20:58+00:00

Change-Id: Ie9579e4dea63fd8210f0d3a0a0fa41bd3202d352

Automatic translation import

2020-05-23T15:20:03+00:00

Change-Id: I7f11df70b63f3b068d9aac0d1e9ef1476f79c029

sensors: set max range of proximity sensor to 1

2020-05-19T09:27:32+00:00

Samsung's proximity sensor type is binary in nature.
There are only two state: FAR and NEAR.

However, Samsung uses values between min and max for
other purposes like proximity detection during Always-On
Display.

This breaks proximity detection during Doze for AOSP as
AOSP only considers the proximity sensor in FAR state
when the value equals or larger than max.

Thus, this change sets the max to 1 so any > 1 value
would be considered as FAR and the behavior of this vendor
proximity sensor type matches the behavior expected by AOSP.

Change-Id: I56af8e2ae743b47e3c4894e5ef68ce0b54e5cfdb

fingerprint: inscreen: allow to set_fod_rect at boot

2020-05-16T15:41:10+00:00

We found that stock firmware calculates the fod rect
from resolution and a set of inscreen fingerprint
sensor position data at boot and then use set_fod_rect
command to tell the Kernel TSP driver.

Then the Kernel TSP driver wrote it to "sponge"
(presumably firmware of touchscreen panel).

It is not yet known what exactly was done with this
data but it is good to keep in line with stock
firmware when we can.

Change-Id: Id44d399a8dc482c7d6f320a3bbfea1282ac4f83a
Signed-off-by: Jesse Chan

fingerprint: inscreen: enable sensor on ShowFODView

2020-05-16T15:41:10+00:00

Enabling sensor on Press is slow and frequent on/off
switching on Press/Release leads to unexpected results.

Looking into Kernel, the purpose of FOD_ENABLE/FOD_DISABLE
commands are to save battery. (ts->lowpower_mode) It is not
meant to handle fingerprint authentication on Press/Release.

It is expected that FOD is in ENABLED state whenever the user
is EXPECTED to use fingerprint authentication soon.

Thus, this patch moved FOD_ENABLE/FOD_DISABLE from
OnPress/onRelease to onShowFODView/onHideFODView so the
fingerprint authentication can be faster and the logic makes
more sense.

Change-Id: Id94b71acd55038d6eda7a1a89dde5fdf5a1e298f
Signed-off-by: Jesse Chan

sensors: get the full list of sensors

2020-05-16T02:30:26+00:00

Samsung uses a special OperationMode (5555).

Thanks to Pierre-Hugues HUSSON for the hint.

Change-Id: I037ff5bf5a1edd65b616480d1c43cef8e61ba999
Signed-off-by: Jesse Chan

sensors: map Samsung proximity sensor type to generic

2020-05-15T14:15:57+00:00

Samsung uses their own com.samsung.sensor.physical_proximity
type instead of SENSOR_TYPE_PROXIMITY of Android.

This makes proximity sensor unavailable for us as we only
look for SENSOR_TYPE_PROXIMITY.

Thus, this change maps Samsung's vendor-specific proximity
sensor type to generic one.

Change-Id: I64f6558876e1398dfbea0e5c0eb76aa1aafd2dfd
Signed-off-by: Jesse Chan