This will give a better overview of implemented features.
---
android/README | 37 ++++++++++++++++++++++++++++++++-----
1 file changed, 32 insertions(+), 5 deletions(-)
diff --git a/android/README b/android/README
index e3c314f..49536e2 100644
--- a/android/README
+++ b/android/README
@@ -132,15 +132,42 @@ automatically on HAL library initialization. To deinitialize HAL library and
stop daemon type 'bluetooth cleanup'. Type 'help' for more information. Tab
completion is also supported.
+=====================
+Implementation status
+=====================
+
+Summary of HALs implementation status.
+
+complete - implementation is feature complete and Android Framework is able
+ to use it normally
+partial - implementation is in progress and not all required features are
+ present, Android Framework is able to use some of features
+initial - only initial implementations is present, Android Framework is
+ able to initialize but most likely not able to use it
+not started - no implementation, Android Framework is not able to initialize it
+
+profile ID HAL header status
+core bluetooth.h complete
+a2dp bt_av.h complete
+gatt bt_gatt.h not started
+ bt_gatt_client.h not started
+ bt_gatt_server.h not started
+handsfree bt_hf.h initial
+hidhost bt_hh.h complete
+health bt_hl.h not started
+pan bt_pan.h complete
+avrcp bt_rc.h partial
+socket bt_sock.h complete
+
===========================
Implementation shortcomings
===========================
-It is possible that some of HAL functionality is missing implementation due to
-reasons like feature feasibility or necessity for latest Android Framework.
-This sections provides list of such deficiencies. Note that HAL library is
-always expected to fully implement HAL API so missing implementation might
-happen only in daemon.
+It is possible that some of HAL functionality (although being marked as
+complete) is missing implementation due to reasons like feature feasibility or
+necessity for latest Android Framework. This sections provides list of such
+deficiencies. Note that HAL library is always expected to fully implement HAL
+API so missing implementation might happen only in daemon.
HAL Bluetooth
=============
--
1.8.5.3
Hi Szymon,
> This will give a better overview of implemented features.
> ---
> android/README | 37 ++++++++++++++++++++++++++++++++-----
> 1 file changed, 32 insertions(+), 5 deletions(-)
>
> diff --git a/android/README b/android/README
> index e3c314f..49536e2 100644
> --- a/android/README
> +++ b/android/README
> @@ -132,15 +132,42 @@ automatically on HAL library initialization. To deinitialize HAL library and
> stop daemon type 'bluetooth cleanup'. Type 'help' for more information. Tab
> completion is also supported.
>
> +=====================
> +Implementation status
> +=====================
> +
> +Summary of HALs implementation status.
> +
> +complete - implementation is feature complete and Android Framework is able
> + to use it normally
> +partial - implementation is in progress and not all required features are
> + present, Android Framework is able to use some of features
> +initial - only initial implementations is present, Android Framework is
> + able to initialize but most likely not able to use it
> +not started - no implementation, Android Framework is not able to initialize it
> +
> +profile ID HAL header status
use a ------ line here to separate header for content.
> +core bluetooth.h complete
> +a2dp bt_av.h complete
> +gatt bt_gatt.h not started
> + bt_gatt_client.h not started
> + bt_gatt_server.h not started
> +handsfree bt_hf.h initial
> +hidhost bt_hh.h complete
> +health bt_hl.h not started
> +pan bt_pan.h complete
> +avrcp bt_rc.h partial
> +socket bt_sock.h complete
> +
Regards
Marcel
Hi Andrzej,
On Monday 10 of February 2014 15:35:15 Andrzej Kaczmarek wrote:
> Hi Szymon,
>
> On 10 February 2014 12:50, Szymon Janc <[email protected]> wrote:
> > This will give a better overview of implemented features.
> > ---
> >
> > android/README | 37 ++++++++++++++++++++++++++++++++-----
> > 1 file changed, 32 insertions(+), 5 deletions(-)
> >
> > diff --git a/android/README b/android/README
> > index e3c314f..49536e2 100644
> > --- a/android/README
> > +++ b/android/README
> > @@ -132,15 +132,42 @@ automatically on HAL library initialization. To
> > deinitialize HAL library and>
> > stop daemon type 'bluetooth cleanup'. Type 'help' for more information.
> > Tab
> > completion is also supported.
> >
> > +=====================
> > +Implementation status
> > +=====================
> > +
> > +Summary of HALs implementation status.
> > +
> > +complete - implementation is feature complete and Android Framework is
> > able + to use it normally
> > +partial - implementation is in progress and not all required features
> > are + present, Android Framework is able to use some of
> > features +initial - only initial implementations is present, Android
> > Framework is + able to initialize but most likely not able
> > to use it +not started - no implementation, Android Framework is not able
> > to initialize it +
> > +profile ID HAL header status
> > +core bluetooth.h complete
> > +a2dp bt_av.h complete
> > +gatt bt_gatt.h not started
> > + bt_gatt_client.h not started
> > + bt_gatt_server.h not started
> > +handsfree bt_hf.h initial
> > +hidhost bt_hh.h complete
> > +health bt_hl.h not started
> > +pan bt_pan.h complete
> > +avrcp bt_rc.h partial
> > +socket bt_sock.h complete
>
> This should be 'partial' since you application cannot register server
> on custom UUID with channel being assigned dynamically
> (BluetoothAdapter::listenUsingRfcommWithServiceRecord). I have patches
> which add this support but need to fix other code first in order to
> make them work properly.
Right, I'll send V2 later (unless you manage to socket send fixes before me:))
--
BR
Szymon Janc
Hi Szymon,
On 10 February 2014 12:50, Szymon Janc <[email protected]> wrote:
>
> This will give a better overview of implemented features.
> ---
> android/README | 37 ++++++++++++++++++++++++++++++++-----
> 1 file changed, 32 insertions(+), 5 deletions(-)
>
> diff --git a/android/README b/android/README
> index e3c314f..49536e2 100644
> --- a/android/README
> +++ b/android/README
> @@ -132,15 +132,42 @@ automatically on HAL library initialization. To deinitialize HAL library and
> stop daemon type 'bluetooth cleanup'. Type 'help' for more information. Tab
> completion is also supported.
>
> +=====================
> +Implementation status
> +=====================
> +
> +Summary of HALs implementation status.
> +
> +complete - implementation is feature complete and Android Framework is able
> + to use it normally
> +partial - implementation is in progress and not all required features are
> + present, Android Framework is able to use some of features
> +initial - only initial implementations is present, Android Framework is
> + able to initialize but most likely not able to use it
> +not started - no implementation, Android Framework is not able to initialize it
> +
> +profile ID HAL header status
> +core bluetooth.h complete
> +a2dp bt_av.h complete
> +gatt bt_gatt.h not started
> + bt_gatt_client.h not started
> + bt_gatt_server.h not started
> +handsfree bt_hf.h initial
> +hidhost bt_hh.h complete
> +health bt_hl.h not started
> +pan bt_pan.h complete
> +avrcp bt_rc.h partial
> +socket bt_sock.h complete
This should be 'partial' since you application cannot register server
on custom UUID with channel being assigned dynamically
(BluetoothAdapter::listenUsingRfcommWithServiceRecord). I have patches
which add this support but need to fix other code first in order to
make them work properly.
BR,
Andrzej