Allow Custom Default Ringer Vibrations
This change allows devices to define and use custom VibrationEffects as
the default vibration used in Ringer. Before this change, devices were
only able to choose between simple and pulse-based vibration, and their
choice was read in Ringer which creates its own effect. With this
change, devices can have full control of the default vibration via a
config resource overlay.
This will allow different devices/form-factors to specify their own
default Ringer vibrations, without having to modify the Ringer code.
Bug: 282113261
Test: atest RingerTest
Change-Id: I63bfa506b357ee5586ca55d7103bb66b7f57ae87
diff --git a/flags/Android.bp b/flags/Android.bp
new file mode 100644
index 0000000..34bcd81
--- /dev/null
+++ b/flags/Android.bp
@@ -0,0 +1,32 @@
+//
+// Copyright (C) 2023 The Android Open Source Project
+//
+// Licensed under the Apache License, Version 2.0 (the "License");
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+//
+
+package {
+ default_applicable_licenses: ["Android-Apache-2.0"],
+}
+
+aconfig_declarations {
+ name: "telecom_flags",
+ package: "com.android.server.telecom.flags",
+ srcs: [
+ "telecom_ringer_flag_declarations.aconfig",
+ ],
+}
+
+java_aconfig_library {
+ name: "telecom_flags-lib",
+ aconfig_declarations: "telecom_flags"
+}
\ No newline at end of file