TODO List

  1. TODO List
    1. Blacklist
    2. New drivers
    3. Service record attribute update methods
    4. L2CAP Authorization
    5. Network service record attribute update
    6. Define a standard for valid services identifier
    7. XML service records
    8. Host Down
    9. Adapter not available(Services)

Blacklist

Implement kernel level devices blacklist 

Date: 2007/03/29
Priority: low
How reproduce: TBD
Assigned to:
Status:
Solved(date):
Modified files/Revision:

New drivers

Implement more kernel level drivers for bluetooth devices 

Date: 2008/03/06
Priority: high
How reproduce: 
Assigned to:
Status:
Solved(date):
Modified files/Revision:

And create a list by maker, make and model.

Collaboration with The Linux Driver Project

Service record attribute update methods

Implement new D-Bus methods to update service attributes.

  • UpdateServiceRecord(uint32 handle, array(byte))
  • UpdateServiceRecordFromXML(uint32 handle, string rec_attributes) 
Date: 2007/03/29
Priority: low
How reproduce:
Assigned to:
Status:
Solved(date):
Modified files/Revision:

L2CAP Authorization

The kernel/userspace doesn't support L2CAP authorization. Currently the L2CAP Connection response signalling packet always contains result 0(connection successful) - without support for pending authorization. 

Date: 2007/04/04
Priority: low
How reproduce:
Assigned to:
Status:
Solved(date):
Modified files/Revision:

Network service record attribute update

It is necessary define requirements to update sdp cache and network files. The network file(for connection objects) can have invalid/old service record attribute data. Maybe store the service handle and update the record for each "Connection.Connect()" call could be a solution. 

Date: 2007-April-13
Priority: low(next release 3.11)
How reproduce:
Assigned to:
Status:
Solved(date):
Modified files/Revision:

Define a standard for valid services identifier

GetRemoteServiceHandles accepts uuid128 string and the friendly name only. By other hand, the network service accepts uuid128 string, the friendly name and the 16bits string(uint16 - service class id). 

Date: 2007-April-25
Priority: low(next release 3.11)
How reproduce:
Assigned to:
Status:
Solved(date):
Modified files/Revision:

XML service records

Investigate if it is feasible create XML file to describe pre-defined service record for network and audio services instead of use c functions to create the SDP record. Define XML files could reduce the code size and improve the maintenance. 

Date: 2007-May-11
Priority: low(next release 3.11)
How reproduce:
Assigned to:
Status: 
Solved(date):
Modified files/Revision:

Host Down

Investigate a possible solution(for the services) to reduce side-effects of the page timeout. Clients should not the wait until the Connection Complete event arrives with Page Timeout error. 

Date: 2007-May-25
Priority:
How reproduce:
Assigned to:
Status: 
Solved(date):
Modified files/Revision:

Adapter not available(Services)

The BlueZ services initialize all objects stored in /var/lib/bluetooth/*/{input, network, nap, gn, audio}. When the adapter is not available, the D-Bus object path is accessible but if someone call Connect a generic error is returned. eg: org.bluez.input.Error.ConnectionAttemptFailed?: No route to host Maybe return a more meaningful error could help. 

Date: 2007-Jun-23
Priority: Low
How reproduce:
Assigned to:
Status:
Solved(date):
Modified files/Revision: