framework/connectivity/bluez.git
11 years agoModified supported feature for Target role in AVRCP profile
sangki79.park [Fri, 15 Mar 2013 04:44:50 +0000 (13:44 +0900)]
Modified supported feature for Target role in AVRCP profile

* Previous feature : Category 1/2/3/4, Player Application settings.
* Modified feature : Category 1, Player Application settings.

* AVRCP profile ensures the interoperability by classifying the A/V functions
  into four categories.
  - Category 1 : Player / Recorder
                 (mandatory function : play & stop)
  - Category 2 : Monitor / Amplifier
                 (mandatory function : volume up & down)
  - Category 3 : Tuner
                 (mandatory function : channel up & down)
  - Category 4 : Menu
                 (mandatory : root menu, up, down, left, right and select)

Change-Id: I9ea7fdca57fca26db9f8b88c621175ad0eab72c3

11 years agoMerge branch 'master' into tizen_2.1
DoHyun Pyun [Fri, 22 Mar 2013 00:25:49 +0000 (09:25 +0900)]
Merge branch 'master' into tizen_2.1

Change-Id: If4a0387d4729027095b8bcbeda4c2c4ef02d6c35

11 years agoIncrease the version to release
DoHyun Pyun [Thu, 21 Mar 2013 10:21:50 +0000 (19:21 +0900)]
Increase the version to release

Change-Id: Ia1123f4e82bed337183e103063a971264c23c4b4

11 years agoRemove '-d' option such like upstream bluez
DoHyun Pyun [Thu, 21 Mar 2013 10:21:09 +0000 (19:21 +0900)]
Remove '-d' option such like upstream bluez

Change-Id: I934d6e51bf909450a415b4f5f70d76c4e1eebe60

11 years agoFix the issue that we can't start discovery
DoHyun Pyun [Thu, 21 Mar 2013 10:04:46 +0000 (19:04 +0900)]
Fix the issue that we can't start discovery

[Issue] Reported bug from Web API part

[Problem] We can't start discovery without -d option

[Cause] This problem is caused by various issues such as timing,
        bluez logic, and kernel bug.

1. Timing issue
 - After activating BT we get many mgmt events.
   (MGMT_OP_READ_INFO / MGMT_OP_SET_POWERED / MGMT_OP_SET_SSP / ETC)
   We call 'mgmt_new_settings' function in all cases.
   If the kernel send the event before finishing previous settings,
   the previous setting values will be overwrited.

2. bluez logic
 - When the 'mgmt_new_settings' function was called by mgmt events,
   there is no rutine to check if we already call to set LE or not.
   So we run 'Set LE' command over two times.

3. kernel bug
 - If the kernel recieve 'Set LE' command, it seems that the function
   don't check if the input value is same with previous value.
   The function just toggle the LE value.

[Solution] If we activate BT, LE flag already set in kernel.
           So we don't need to set LE flag again in bluez.

Change-Id: I4458797cd01d3fac92d0c457cf9cfdf1d2f35122

11 years agoIncrease the version number to release
DoHyun Pyun [Tue, 19 Mar 2013 08:05:30 +0000 (17:05 +0900)]
Increase the version number to release

Change-Id: If61928f009e4f5dfac1caa54f421c635ad961488

11 years agoFix the issue that we can't start discovery
DoHyun Pyun [Tue, 19 Mar 2013 07:59:33 +0000 (16:59 +0900)]
Fix the issue that we can't start discovery

[Issue] Reporting bug from web API team

[Problem] We can't start discovery

[Cause] It seems the timing issue, we will discuss with
        systemd part about this bug in later.

[Solution] Add '-d' option such like private codes

Change-Id: I0c694dc8f72ebb64be5c21005be39a1494365a29

11 years agomerge with master
Jinkun Jang [Fri, 15 Mar 2013 16:13:11 +0000 (01:13 +0900)]
merge with master

11 years agoTizen 2.1 base
Jinkun Jang [Tue, 12 Mar 2013 16:47:11 +0000 (01:47 +0900)]
Tizen 2.1 base

12 years agoInitial empty repository
Eunkyoung Kim [Fri, 6 Jan 2012 12:59:37 +0000 (21:59 +0900)]
Initial empty repository