From 45ff87c8c763205ca66cfd96b25a5ff98549ac1a Mon Sep 17 00:00:00 2001
From: Sal Savage <salsavage@google.com>
Date: Thu, 23 Mar 2023 12:52:17 -0700
Subject: [PATCH 1/2] Use the ?= operator for assignment to avoid downstream
 assignment errors

Using the = operator makes it so no one else can assign the system
property anymore. Other build targets downstream do try to set these
properties explicitly to false. Since no one sets the property before,
we can use the ?= operator to apply the values, which still allows other
makefiles downstream the chance to the change the value.

Bug: 274950131
Test: m
Change-Id: I113da6efefccef562bb13cb73087e4b5c7eca453
---
 bluetooth/syna_default.mk | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/bluetooth/syna_default.mk b/bluetooth/syna_default.mk
index 71ad5ab..43d9198 100644
--- a/bluetooth/syna_default.mk
+++ b/bluetooth/syna_default.mk
@@ -18,12 +18,12 @@
 # Bluetooth LE Audio
 PRODUCT_PRODUCT_PROPERTIES += \
     ro.bluetooth.leaudio_switcher.supported=true \
-    bluetooth.profile.bap.unicast.client.enabled=true \
-    bluetooth.profile.csip.set_coordinator.enabled=true \
-    bluetooth.profile.hap.client.enabled=true \
-    bluetooth.profile.mcp.server.enabled=true \
-    bluetooth.profile.ccp.server.enabled=true \
-    bluetooth.profile.vcp.controller.enabled=true \
+    bluetooth.profile.bap.unicast.client.enabled?=true \
+    bluetooth.profile.csip.set_coordinator.enabled?=true \
+    bluetooth.profile.hap.client.enabled?=true \
+    bluetooth.profile.mcp.server.enabled?=true \
+    bluetooth.profile.ccp.server.enabled?=true \
+    bluetooth.profile.vcp.controller.enabled?=true \
 
 # Bluetooth HAL and Pixel extension
 DEVICE_MANIFEST_FILE += \

From 88163f2a2085ae859fcfbef78c7ea45e25ff96ae Mon Sep 17 00:00:00 2001
From: Siarhei Vishniakou <svv@google.com>
Date: Tue, 21 Mar 2023 01:38:48 +0000
Subject: [PATCH 2/2] Decrease the touch slop to prevent unintentional long
 presses

On this device, the default touch slop value of 8dp is too large. It corresponds to a physical distance of ~ 1.5mm.
This results in long presses getting triggered too easily.

Reduce the touch slop to 5 dp, which is about ~ 1mm, and closer to a reference device that doesn't exhibit the long-press issue.

Bug: 270835406
Change-Id: I1973e7831f527f2f654661bd4917f48992c74b61
Test: use a test app for long presses
---
 .../frameworks/base/core/res/res/values/config.xml        | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/tangorpro/overlay/frameworks/base/core/res/res/values/config.xml b/tangorpro/overlay/frameworks/base/core/res/res/values/config.xml
index 572d514..0bdc02d 100644
--- a/tangorpro/overlay/frameworks/base/core/res/res/values/config.xml
+++ b/tangorpro/overlay/frameworks/base/core/res/res/values/config.xml
@@ -569,6 +569,14 @@
         <item>3</item> <!-- COLOR_MODE_AUTOMATIC -->
     </integer-array>
 
+    <!-- Override the "touch slop" value used by ViewConfiguration.
+        This prevents misclassification of gestures as long presses, by reducing the
+        distance that the pointer can travel while still being treated as "stationary".
+        The default value is 8dp, which is roughly 1.5mm on this device. On another
+        reference device, the touch slop was estimated at ~ 1 mm. Therefore, set the
+        touch slop to 8/1.5 =~ 5 dp to make it closer to the reference device. -->
+   <dimen name="config_viewConfigurationTouchSlop">5dp</dimen>
+
     <!-- The default volume for the notification stream -->
     <integer name="config_audio_notif_vol_default">0</integer>