1. Accueil
  2. Question et réponse
  3. Pourquoi HTC Droid exécutant OTA 2.1 ne peut-il pas communiquer avec RFCOMM?

Pourquoi HTC Droid exécutant OTA 2.1 ne peut-il pas communiquer avec RFCOMM?

2010-05-17 22 views
0

Hier nous avons reçu OTA Android 2.1 sur le HTC Droid de ma femme - HOORAY !!! Je suis enfin en mesure de charger mon application de carpette sur son téléphone.Pourquoi HTC Droid exécutant OTA 2.1 ne peut-il pas communiquer avec RFCOMM?

Eh bien, nous l'avons chargé, mais cela ne fonctionne pas. Plus précisément, il se connecte mais ne voit pas d'E/S !!!

J'ai apparié, réapparié et réapparié, chaque fois que c'est le même problème: connect() dit que nous nous sommes connectés avec succès, mais toute tentative d'envoyer ou de recevoir des données semble fonctionner, mais aucune donnée n'arrive dans le tampon d'entrée.

Le périphérique auquel je me connecte utilise des commandes AT. ATI doit répondre avec un ID de périphérique. Cela fonctionne bien quand je lance l'application sur mon Moto Droid, mais sur le droïde HTC, aucune donnée n'est jamais présente dans le flux d'entrée/tampon.

Personnellement, je suis sûr que c'est un bug ou une limitation dans cette version pour le HTC (parce que l'application fonctionne très bien sur mon Moto A855 Droid).

Quelqu'un peut-il commenter le problème?

extraits de code obligatoires:

variables membres qui définit mon RFCOMM UUID

static final UUID UUID_RFCOMM_GENERIC = UUID.fromString("00001101-0000-1000-8000-00805F9B34FB");

parties de ma connexion()

// make sure peer is defined as a valid device based on their MAC. If not then do it. 
    if (mBTDevice == null) 
     mBTDevice = mBTAdapter.getRemoteDevice(mPeerMAC); 

    // Make an RFCOMM binding. 
    try {mBTSocket = mBTDevice.createRfcommSocketToServiceRecord(UUID_RFCOMM_GENERIC); 
    } catch (Exception e1) { 
     msg ("connect(): Failed to bind to RFCOMM by UUID. msg=" + e1.getMessage()); 
     return false; 
    } 

    msg ("connect(): Try to connect."); 

    try { 
     mBTSocket.connect(); 
    } catch (Exception e) { 
     msg ("connect(): Exception thrown during connect: " + e.getMessage()); 
     return false; 
     // there was a problem connecting... make a note of the particulars and move on. 
    } 

    msg ("connect(): CONNECTED!"); 

    try { 
     mBTOutputStream = mBTSocket.getOutputStream(); 
     mBTInputStream = new BufferedInputStream (mBTSocket.getInputStream(),INPUT_BUFFER_SIZE); 
     //msg ("Connecting non-buffered input stream..."); 
     //mBTInputStream = mBTSocket.getInputStream(); 
    } catch (Exception e) { 
     msg ("connect(): Error attaching i/o streams to socket. msg=" + e.getMessage()); 
     return false; 
    } 

    resetErrorCounters(); 
    setConnected(true); 
    return true; 
}

J'envoyer "ATI\r"

et attendre quelque chose comme "CAN OBD II" mais je n'ai rien.

mBTInputStream.available(), semble-t-il, est TOUJOURS nul, même lorsque les données doivent être dans le tampon d'entrée.

Il y a GOBS de messages de trace générés par le système d'exploitation tel que vu avec adb logcat -v time

Certains des plus intéressants:

05-17 19:44:21.447 D/BluetoothSppPort(5809): connected to device service! 
05-17 19:44:21.447 D/BluetoothSppPort(5809): Creating a BluetoothSpp proxy object 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort called! 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort checking uuid 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort UUID=00001101-0000-1000-8000-00805f9b34fb auth=true encrypt=true 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort enforcing bluetooth perm 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort creating a jbtlspp object 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort checking if the btl spp object is valid 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort try to create an spp container 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort try to create security params 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort Set Security L2 
05-17 19:44:21.467 D/BluetoothSppService( 74): createPort spp port create 
05-17 19:44:21.467 D/JBtlSpp ( 74): create: Entered 
05-17 19:44:21.467 D/JBtlSpp ( 74): Calling NativeJBtlSpp_Create 
05-17 19:44:21.467 D/JBtlSppNative( 74): NativeJBtlSpp_Create: Entered 
05-17 19:44:21.467 D/JBtlSppNative( 74): NativeJBtlSpp_Create: Calling BTL_SPP_Remote_Create 
05-17 19:44:21.477 D/JBtlSppNative( 74): NativeJBtlSpp_Create: BTL_SPP_Remote_Create returned 0, context:18 
05-17 19:44:21.477 D/JBtlSppNative( 74): NativeJBtlSpp_Create: Setting context value in jContext out parm 
05-17 19:44:21.477 D/JBtlSppNative( 74): NativeJBtlSpp_Create: Calling Java setValue(0x18) in context's class 
05-17 19:44:21.477 D/JBtlProfileContext( 74): setValue: setValue called, value:24 
05-17 19:44:21.477 D/JBtlSppNative( 74): create_spp_port_data: will use context struct 0 for the port 24 
05-17 19:44:21.477 D/JBtlSppNative( 74): create_spp_port_data: spp port context 0 added 
05-17 19:44:21.477 D/JBtlSppNative( 74): NativeJBtlSpp_Create:Exiting Successfully 
05-17 19:44:21.477 D/JBtlSpp ( 74): After NativeJBtlSpp_Create, status=SUCCESS, Context = 24 
05-17 19:44:21.477 D/JBtlRbtlServices( 74): addUser: Entered, userRefCount = 1 
05-17 19:44:21.477 D/BluetoothSppService( 74): port create returned status SUCCESS 
05-17 19:44:21.477 D/JBtlSpp ( 74): enable: Entered 
05-17 19:44:21.477 D/JBtlSpp ( 74): enable: UUID=00001101-0000-1000-8000-00805f9b34fb 
05-17 19:44:21.477 D/JBtlSppNative( 74): NativeJBtlSpp_Enable: Entered 
05-17 19:44:21.487 D/JBtlSppNative( 74): NativeJBtlSpp_Enable: BTL_SPP_Enable returned 0 
05-17 19:44:21.487 D/JBtlSppNative( 74): NativeJBtlSpp_Enable:Exiting 
05-17 19:44:21.487 D/JBtlSpp ( 74): After NativeJBtlSpp_Enable, status=SUCCESS 
05-17 19:44:21.487 D/JBtlSpp ( 74): enable: Exiting 
05-17 19:44:21.487 D/BluetoothSppService( 74): port enable returned status SUCCESS 
05-17 19:44:21.487 D/BluetoothSppService( 74): connectPort called! 
05-17 19:44:21.497 D/BluetoothSppService( 74): connectPort received bdaddress:00:18:E4:1D:23:9B 
05-17 19:44:21.527 D/BluetoothSppService( 74): Trying to connect to 00:18:E4:1D:23:9B 
05-17 19:44:21.527 D/JBtlSpp ( 74): setServiceName: Entered 
05-17 19:44:21.527 D/JBtlSppNative( 74): NativeJBtlSpp_SetServiceName: Entered 
05-17 19:44:21.547 D/JBtlSppNative( 74): NativeJBtlSpp_SetServiceName: native func returned 0 
05-17 19:44:21.547 D/JBtlSppNative( 74): NativeJBtlSpp_SetServiceName:Exiting 
05-17 19:44:21.547 D/JBtlSpp ( 74): After setServiceName, status=SUCCESS 
05-17 19:44:21.547 D/JBtlSpp ( 74): setServiceName: Exiting 
05-17 19:44:21.557 D/BluetoothSppService( 74): port setServiceName returned status SUCCESS 
05-17 19:44:21.587 D/JBtlSpp ( 74): connect: Entered connecting to 00:18:E4:1D:23:9B 
05-17 19:44:21.587 D/JBtlSppNative( 74): NativeJBtlSpp_Connect: Entered 
05-17 19:44:21.597 D/JBtlSppNative( 74): NativeJBtlSpp_Connect: BTL_SPP_Connect returned 2 
05-17 19:44:21.597 D/JBtlSppNative( 74): NativeJBtlSpp_Connect:Exiting 
05-17 19:44:21.597 D/JBtlSpp ( 74): After NativeJBtlSpp_Connect, status=PENDING 
05-17 19:44:21.747 D/AK8973 ( 61): Compass CLOSE 
05-17 19:44:21.887 W/Process ( 74): Unable to open /proc/5749/status 
05-17 19:44:21.917 I/ActivityManager( 74): Displayed activity com.gtosoft.dash/.Dash: 1279 ms (total 1279 ms) 
05-17 19:44:24.047 D/  ( 74): signal_BTEVENT_ACCESSIBLE_CHANGE: Entered 
05-17 19:44:24.047 D/  ( 74): signal_BTEVENT_ACCESSIBLE_CHANGE: Calling Java Accessible Change callback 
05-17 19:44:24.047 D/JBtlBmg ( 74): nativeAccessibleChange 
05-17 19:44:24.087 D/BluetoothService( 74): Callback - accessbileChange, btErrCode = NO_ERROR, mode = CONNECTABLE_ONLY 
05-17 19:44:24.087 D/BluetoothService( 74): Sending ACTION_SCAN_MODE_CHANGED intent, mode = 21 
05-17 19:44:24.087 D/  ( 74): signal_BTEVENT_ACCESSIBLE_CHANGE: Exiting 
05-17 19:44:24.097 D/  ( 74): signal_BTEVENT_LINK_CONNECT_CNF: Entered 
05-17 19:44:24.097 D/  ( 74): signal_BTEVENT_LINK_CONNECT_CNF: context: 1, errCode: 0 
05-17 19:44:24.097 D/  ( 74): signal_BTEVENT_LINK_CONNECT_CNF: Calling Java Link Connect Confirmation callback 
05-17 19:44:24.097 D/JBtlBmg ( 74): nativeLinkConnectCnf 
05-17 19:44:24.107 D/BluetoothService( 74): Callback - linkConnectCnf, btErrCode = NO_ERROR, bdAddr = 00:18:E4:1D:23:9B 
05-17 19:44:24.117 D/JBtlBmg ( 74): getKnownDeviceInfo: Entered 
05-17 19:44:24.117 D/JBtlBmg ( 74): getKnownDeviceInfo: Calling NativeJBtlBmg_GetKnownDeviceInfo 
05-17 19:44:24.137 D/  ( 74): NativeJBtlBmg_GetKnownDeviceInfo: Entered 
05-17 19:44:24.137 D/  ( 74): NativeJBtlBmg_GetKnownDeviceInfo: Calling BTL_BMG_GetKnownDeviceInfo 
05-17 19:44:24.227 D/JBtlBmgJniKnownDeviceInfo( 74): setValues: Entered 
05-17 19:44:24.227 D/  ( 74): NativeJBtlBmg_GetKnownDeviceInfo:Exiting 
05-17 19:44:24.227 D/JBtlBmg ( 74): getKnownDeviceInfo: After NativeJBtlBmg_GetKnownDeviceInfo, status=SUCCESS 
05-17 19:44:24.227 D/JBtlBmg ( 74): getKnownDeviceInfo: Exiting 
05-17 19:44:24.227 D/BluetoothService( 74): onRemoteDeviceConnected, device 00:18:E4:1D:23:9B is Paired 
05-17 19:44:24.227 D/BluetoothService( 74): Sending ACTION_ACL_CONNECTED intent, address = 00:18:E4:1D:23:9B 
05-17 19:44:24.227 D/BluetoothA2dpService( 74): Received intent with action: android.bluetooth.device.action.ACL_CONNECTED 
05-17 19:44:24.227 D/  ( 74): signal_BTEVENT_LINK_CONNECT_CNF: Exiting 
05-17 19:44:24.757 D/JBtlAg ( 163): setIndicatorValue: entered 
05-17 19:44:24.767 I/JBtlAg ( 163): After NativeJBtlAg_SetIndicatorValue, status = SUCCESS 
05-17 19:44:24.767 D/JBtlAg ( 163): setIndicatorValue: exiting 
05-17 19:44:24.807 D/JBtlSppNative( 74): signal_SPP_EVENT_OPEN: Entered 
05-17 19:44:24.807 D/JBtlSppNative( 74): signal_SPP_EVENT_OPEN: status: 0 context:24 
05-17 19:44:24.827 D/JBtlSpp ( 74): nativeCb_open: Entered from 00:18:E4:1D:23:9B 
05-17 19:44:24.827 D/JBtlSpp ( 74): nativeCb_open: Calling callback 
05-17 19:44:24.827 D/BluetoothSppService( 74): connected called! 
05-17 19:44:24.847 D/JBtlSpp ( 74): connect: Exiting 
05-17 19:44:24.847 D/BluetoothSppService( 74): port connect returned status SUCCESS 
05-17 19:44:24.847 D/JBtlSppNative( 74): signal_SPP_EVENT_OPEN: Exiting 
05-17 19:44:24.847 D/JBtlSppNative( 74): signal_SPP_EVENT_MODEM_STATUS_IND: Entered 
05-17 19:44:24.847 D/JBtlSppNative( 74): signal_SPP_EVENT_MODEM_STATUS_IND: Exiting 
05-17 19:44:25.424 D/BluetoothSppService( 74): writeSync called! 
05-17 19:44:25.424 D/JBtlSpp ( 74): write: Entered 
05-17 19:44:25.427 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: Entered 
05-17 19:44:25.427 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: BTL_SPP_WriteSync returned 0 written: 6 total: 0/6 
05-17 19:44:25.437 D/JBtlSppNative( 74): signal_SPP_EVENT_TX_DATA_COMPLETE: Entered 
05-17 19:44:25.437 D/JBtlSppNative( 74): signal_SPP_EVENT_TX_DATA_COMPLETE: status: 0 context:24 txDataLen:6 
05-17 19:44:25.437 D/JBtlSppNative( 74): signal_SPP_EVENT_TX_DATA_COMPLETE: Exiting ok 
05-17 19:44:25.437 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: written 6 
05-17 19:44:25.437 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative:Exiting with 0 
05-17 19:44:25.437 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: returning 6 bytes 
05-17 19:44:25.437 D/JBtlSpp ( 74): After write, status=SUCCESS 
05-17 19:44:25.437 D/JBtlSpp ( 74): write: Exiting 
05-17 19:44:25.437 D/BluetoothSppPort(5809): written 6 bytes 
05-17 19:44:25.467 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Entered 
05-17 19:44:25.467 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: status: 0 context: 24 rxDataLen: 1 
05-17 19:44:25.467 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Exiting 
05-17 19:44:25.477 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Entered 
05-17 19:44:25.477 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: status: 0 context: 24 rxDataLen: 5 
05-17 19:44:25.477 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Exiting 
05-17 19:44:25.487 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Entered 
05-17 19:44:25.487 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: status: 0 context: 24 rxDataLen: 10 
05-17 19:44:25.487 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Exiting 
05-17 19:44:25.497 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Entered 
05-17 19:44:25.497 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: status: 0 context: 24 rxDataLen: 7 
05-17 19:44:25.497 D/JBtlSppNative( 74): signal_SPP_EVENT_RX_DATA_IND: Exiting 
05-17 19:44:27.930 W/ActivityManager( 74): Activity destroy timeout for HistoryRecord{447e0d48 com.gtosoft.dash/.Dash} 
05-17 19:44:29.907 D/dalvikvm( 448): GC freed 78 objects/3664 bytes in 153ms 
05-17 19:44:29.917 D/BluetoothSppService( 74): writeSync called! 
05-17 19:44:29.917 D/JBtlSpp ( 74): write: Entered 
05-17 19:44:29.917 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: Entered 
05-17 19:44:29.927 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: BTL_SPP_WriteSync returned 0 written: 6 total: 0/6 
05-17 19:44:29.937 D/JBtlSppNative( 74): signal_SPP_EVENT_TX_DATA_COMPLETE: Entered 
05-17 19:44:29.937 D/JBtlSppNative( 74): signal_SPP_EVENT_TX_DATA_COMPLETE: status: 0 context:24 txDataLen:6 
05-17 19:44:29.937 D/JBtlSppNative( 74): signal_SPP_EVENT_TX_DATA_COMPLETE: Exiting ok 
05-17 19:44:29.937 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: written 6 
05-17 19:44:29.937 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative:Exiting with 0 
05-17 19:44:29.937 D/JBtlSppNative( 74): NativeJBtlSpp_WriteNative: returning 6 bytes 
05-17 19:44:29.937 D/JBtlSpp ( 74): After write, status=SUCCESS 
05-17 19:44:29.937 D/JBtlSpp ( 74): write: Exiting

Source

2010-05-17 Brad Hein

Répondre

1

Il est un jeu d'attente. Jusqu'à ce que HTC finisse d'écrire des pilotes pour prendre en charge RFCOMM sur cet appareil, RFComm ne fonctionnera pas.

Source

2010-06-29 18:52:15

+0

rupture possible dans le cas - disponible() pourrait bien être cassé, donc je vais écrire un code de test sortir et obtenir des données même si disponible() renvoie 0. Merci à @Femi pour les indices. –

1

J'ai un HTC incroyable Android 2.3.4. J'ai eu des problèmes similaires que j'ai pu travailler en utilisant la réflexion.

Ainsi, au lieu d'utiliser:

mBTSocket = mBTDevice.createRfcommSocketToServiceRecord(UUID_RFCOMM_GENERIC);

Essayez d'utiliser:

Method m = device.getClass().getMethod("createRfcommSocket", new Class[] {int.class}); 
mBTSocket = (BluetoothSocket) m.invoke(device, 1);

Source

2012-02-07 19:30:47 Damon

 Questions connexes

  • Aucun problème connexe^_^