Panda: Bluetooth file transfer fails (Rfcomm socket connect exception)

Bug #987765 reported by Abhishek Paliwal
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Linaro Android
Won't Fix
Medium
vishal
linaro-landing-team-ti
Fix Released
Undecided
Unassigned

Bug Description

Description:
==========
Bluetooth file transfer fails on build:
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob-12.04-release/#build=4

Initiated a file transfer from panda board to another commercial phone - file is not sent even after multiple attempts.
Serial logs(logcat) shows message:
E/BtOppTransfer( 1962): Rfcomm socket connect exception

Reproducible:
===========
Yes, 5/5 time

IMPACT:
========
Bluetooth functionality (file transfer )broken.

Steps:
==========
1. Pair Panda board witha another device which has Bluetooth support.
2. Make sure you have a image file present in sd card
3. Open gallery app and select the image >options->select sharing icon -> bluettoth->seelct paired device.
Issue: File transfer always fails, notification area shows , number of file transfer failed.

Hardware:
==========
Panda 4460
USB Camera connected - Logitech HD Webcam C310
HDMI out to TV
4GB SD card

Software:
==========
https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob-12.04-release/#build=4

Logs:
======
root@android:/ #
root@android:/ # logcat -c
root@android:/ # logcat &
[1] 1957
root@android:/ # --------- beginning of /dev/log/main
E/AudioFlinger( 1347): createTrack_l() Bad parameter: sampleRate 44100 format 1, channelMask 0x00000001 "for output 0x1f4a440 with format 1
E/AudioTrack( 1461): AudioFlinger could not create track, status: -22
E/SoundPool( 1461): Error creating AudioTrack
--------- beginning of /dev/log/system
I/ActivityManager( 1461): START {act=android.intent.action.SEND typ=image/* cmp=com.android.bluetooth/.opp.BluetoothOppLauncherActivity (has extras)} from pid 1929
D/dalvikvm( 1461): GC_FOR_ALLOC freed 313K, 8% free 8854K/9607K, paused 51ms
I/dalvikvm-heap( 1461): Grow heap (frag case) to 8.844MB for 124216-byte allocation
D/dalvikvm( 1461): GC_FOR_ALLOC freed 4K, 8% free 8970K/9735K, paused 50ms
I/ActivityManager( 1461): Start proc com.android.bluetooth for activity com.android.bluetooth/.opp.BluetoothOppLauncherActivity: pid=1962 uid=10008 gids={3003, 3002, 3001, 1015}
W/NetworkManagementSocketTagger( 1461): setKernelCountSet(10008, 1) failed with errno -2
I/ActivityThread( 1962): Pub com.android.bluetooth.opp: com.android.bluetooth.opp.BluetoothOppProvider
I/ActivityManager( 1461): START {act=android.bluetooth.devicepicker.action.LAUNCH flg=0x800000 cmp=com.android.settings/.bluetooth.DevicePickerActivity (has extras)} from pid 1962
W/NetworkManagementSocketTagger( 1461): setKernelCountSet(1000, 1) failed with errno -2
D/LocalBluetoothManager( 1862): setting foreground activity to non-null context
D/BluetoothEventLoop( 1461): Property Changed: Discovering : true
V/BluetoothEventManager( 1862): Received android.bluetooth.adapter.action.DISCOVERY_STARTED
V/BluetoothDiscoveryReceiver( 1862): Received: android.bluetooth.adapter.action.DISCOVERY_STARTED
I/Process ( 1461): Sending signal. PID: 1862 SIG: 3
I/dalvikvm( 1862): threadid=3: reacting to signal 3
D/dalvikvm( 1862): GC_FOR_ALLOC freed 271K, 8% free 7435K/8007K, paused 33ms
I/dalvikvm( 1862): Wrote stack traces to '/data/anr/traces.txt'
I/ActivityManager( 1461): Displayed com.android.settings/.bluetooth.DevicePickerActivity: +1s175ms (total +1s388ms)
W/NetworkManagementSocketTagger( 1461): setKernelCountSet(10008, 0) failed with errno -2
V/StateManager( 1929): saveState
D/BluetoothService( 1461): updateDeviceServiceChannelCache(00:0F:3D:5F:13:0B)
V/StateManager( 1929): saveState class com.android.gallery3d.app.AlbumSetPage
V/StateManager( 1929): saveState class com.android.gallery3d.app.AlbumPage
V/BluetoothEventManager( 1862): Received android.bluetooth.device.action.FOUND
D/BluetoothEventManager( 1862): DeviceFoundHandler created new CachedBluetoothDevice: 00:0F:3D:5F:13:0B
D/BluetoothService( 1461): updateDeviceServiceChannelCache(00:24:7E:ED:88:50)
V/BluetoothEventManager( 1862): Received android.bluetooth.device.action.FOUND
D/BluetoothEventManager( 1862): DeviceFoundHandler created new CachedBluetoothDevice: 00:24:7E:ED:88:50
E/AudioFlinger( 1347): createTrack_l() Bad parameter: sampleRate 44100 format 1, channelMask 0x00000001 "for output 0x1f4a440 with format 1
E/AudioTrack( 1461): AudioFlinger could not create track, status: -22
E/SoundPool( 1461): Error creating AudioTrack
D/BluetoothEventLoop( 1461): Property Changed: Discovering : false
E/BluetoothService.cpp( 1461): stopDiscoveryNative: D-Bus error in StopDiscovery: org.bluez.Error.Failed (Invalid discovery session)
D/dalvikvm( 1461): GC_FOR_ALLOC freed 218K, 10% free 8859K/9735K, paused 50ms
V/BluetoothEventManager( 1862): Received android.bluetooth.adapter.action.DISCOVERY_FINISHED
V/BluetoothDiscoveryReceiver( 1862): Received: android.bluetooth.adapter.action.DISCOVERY_FINISHED
D/LocalBluetoothManager( 1862): setting foreground activity to null
I/GalleryEGLConfigChooser( 1929): Config chosen: R5 G6 B5 A0 D24 S8 ID9 CAVEAT12344
D/dalvikvm( 1929): GC_CONCURRENT freed 163K, 7% free 7406K/7879K, paused 3ms+6ms
I/GLRootView( 1929): GLObject has changed from com.google.android.gles_jni.GLImpl@41252b70 to com.google.android.gles_jni.GLImpl@4123ecc8
I/GLRootView( 1929): onSurfaceChanged: 1920x1032, gl10: com.google.android.gles_jni.GLImpl@4123ecc8
W/NetworkManagementSocketTagger( 1461): setKernelCountSet(1000, 0) failed with errno -2
D/dalvikvm( 1862): GC_CONCURRENT freed 290K, 6% free 7595K/8007K, paused 8ms+12ms
W/InputManagerService( 1461): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@4131e5e0 (uid=1000 pid=1862)
D/OpenGLRenderer( 1862): Flushing caches (mode 1)
I/BtOppRfcommListener( 1962): Accept thread started on channel 12
E/BtOppTransfer( 1962): Rfcomm socket connect exception
D/dalvikvm( 1962): GC_CONCURRENT freed 320K, 7% free 6592K/7047K, paused 1ms+3ms
D/dalvikvm( 1540): GC_CONCURRENT freed 305K, 5% free 7732K/8135K, paused 6ms+9ms
D/libEGL ( 1540): loaded /system/lib/egl/libGLES_android.so
D/libEGL ( 1540): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 1540): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 1540): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 1540): Enabling debug mode 0
D/OpenGLRenderer( 1540): Flushing caches (mode 0)
W/InputManagerService( 1461): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@4126f688

Revision history for this message
warmcat (andy-warmcat) wrote :

See if this problem is the same on later kernels when you're able to test them.

Revision history for this message
Botao (botao-sun) wrote :

Observed on tracking panda Android 12.06 RC2 image, pair can be done successfully but file transfer failed:

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob/#build=87

Revision history for this message
Abhishek Paliwal (abhishek-paliwal) wrote :
Revision history for this message
Botao (botao-sun) wrote :

On Panda 4430 board with Linaro Android build:

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob/#build=105

Bluetooth can't be enabled, the whole feature is unavailable.

Revision history for this message
warmcat (andy-warmcat) wrote :

tilt-3.4 >= 448be0e3981852c8b7032c5d7d51747a1187b774 fixes it.

Notice though:

 - bt firmware now lives down <base firmware path on Android>/ti-connectivity

 - on my PandaBoard ES, it needed TIInit_7.6.15.bts rather than the TIInit_7.2.31.bts on 4430 PandaBoard

Fathi Boudra (fboudra)
Changed in linaro-android:
assignee: Zach Pfeffer (pfefferz) → vishal (vishalbhoj)
Revision history for this message
Botao (botao-sun) wrote :
Revision history for this message
warmcat (andy-warmcat) wrote :

From kernel side it's workable as told on 2012-06-27.

Changed in linaro-landing-team-ti:
status: New → Fix Released
Revision history for this message
Botao (botao-sun) wrote :

Bluetooth is unavailable for Panda 4430 board with Linaro Android image, enabling failed.

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob-12.06-release/#build=4

Revision history for this message
Michael Marley (mamarley) wrote :

I am trying to build a Linaro-optimized ICS ROM for a phone, and I am running into this same issue. I tried to find the commit (448be0e3981852c8b7032c5d7d51747a1187b774) you referenced in the tilt kernel tree (http://git.linaro.org/gitweb?p=people/andygreen/kernel-tilt.git;a=summary), but I could not find it. Am I looking in the wrong tree? What change exactly fixed this?

Revision history for this message
Botao (botao-sun) wrote :

Bluetooth is unavailable for Panda 4430 board with Linaro Android image, enabling failed. Observed on:

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob/#build=116

Revision history for this message
Amit Khare (amit-khare) wrote :

observed on panda 4460, bluetooth enabling failed

While turning on bluetooth from settings menu the settings app closes.

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob/#build=123

log from mincom:

[ 4039.411804] Bluetooth: st_register failed -22

Revision history for this message
Amit Khare (amit-khare) wrote :
Revision history for this message
Amit Khare (amit-khare) wrote :

observed on panda 4430

https://android-build.linaro.org/builds/~linaro-android/panda-ics-gcc47-tilt-tracking-blob/#build=142

enabling fails

[ 302.523956] Bluetooth: st_register failed -22

Revision history for this message
Amit Khare (amit-khare) wrote :
Revision history for this message
Milosz Wasilewski (mwasilew) wrote :

Ubuntu is not mentioned anywhere in the description - removing.
ICS is not supported - closing.

no longer affects: linaro-ubuntu
Changed in linaro-android:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.