API review : use a range of numbers for OEM errors
By API review feedback, it would be better to use a range of numbers for OEM errors instead of just defining CUSTOM_ERROR_1 / CUSTOM_ERROR_2 in HotwordDetectionService. Bug: 184962614 Test: atest CtsVoiceInteractionTestCases Test: atest CtsVoiceInteractionTestCases --instant Change-Id: Id1e3a29e37ef566a1d8e30c703b7f2c4ae138f82
Loading
Please register or sign in to comment