summaryrefslogtreecommitdiffstats
path: root/jni
diff options
context:
space:
mode:
authorPavlin Radoslavov <pavlin@google.com>2015-06-12 17:49:02 -0700
committerPavlin Radoslavov <pavlin@google.com>2015-06-12 17:49:02 -0700
commit18239ca2a5880af0510b762201f02b169445c44f (patch)
tree965729e208d5267abcd8825450e1ab65940217fd /jni
parent8f3a54a0ed8591f4844ee7b47e37bd6451650783 (diff)
downloadandroid_packages_apps_Bluetooth-18239ca2a5880af0510b762201f02b169445c44f.tar.gz
android_packages_apps_Bluetooth-18239ca2a5880af0510b762201f02b169445c44f.tar.bz2
android_packages_apps_Bluetooth-18239ca2a5880af0510b762201f02b169445c44f.zip
Removed AVRCP-related log messages that could fill-up the log.
For some Bluetooth devices, the AVRCP interaction could trigger periodic log messages at INFO level, and those messages can fill-up the log file. Bug: 21818725 Change-Id: I87aca499138b46a79f4251d8a5fe8552ae171205
Diffstat (limited to 'jni')
-rw-r--r--jni/com_android_bluetooth_avrcp.cpp3
1 files changed, 0 insertions, 3 deletions
diff --git a/jni/com_android_bluetooth_avrcp.cpp b/jni/com_android_bluetooth_avrcp.cpp
index b28a43e30..5207f4d99 100644
--- a/jni/com_android_bluetooth_avrcp.cpp
+++ b/jni/com_android_bluetooth_avrcp.cpp
@@ -118,8 +118,6 @@ static void btavrcp_get_element_attr_callback(uint8_t num_attr, btrc_media_attr_
}
static void btavrcp_register_notification_callback(btrc_event_id_t event_id, uint32_t param) {
- ALOGI("%s", __FUNCTION__);
-
if (!checkCallbackThread()) {
ALOGE("Callback: '%s' is not called on the correct thread", __FUNCTION__);
return;
@@ -391,7 +389,6 @@ static jboolean registerNotificationRspPlayPosNative(JNIEnv *env, jobject object
bt_status_t status;
btrc_register_notification_t param;
- ALOGI("%s: sBluetoothAvrcpInterface: %p", __FUNCTION__, sBluetoothAvrcpInterface);
if (!sBluetoothAvrcpInterface) return JNI_FALSE;
param.song_pos = (uint32_t)playPos;