Status, something sleeping in HD

I remember when I was coding the Relauncher_deamon I isolated the component showing the feedback, and placed it in separated application, that must have happened around 2003!
The intention to isolate it, was to show information about the startup process, I placed it in an own LiveCD based on R5. I think it can be useful for scripts.

So after some talks in the Spanish mail-list, I have got the motivation to get that harddisk and recompile the application:

Can be downloaded here or in its bebits page

Important change

In the last week, due a more advanced implementation on how HCI commands are created, I checked the possibility to start using the size value given by the ioctl's(control hook on drivers). On R5 the value was always 0, therefore I was forced to pass in the first 4 bytes of the buffer, its size.

This ioctl's feature works as expected in Haiku, therefore as this new mechanism for bluetooth commands assumes this fact, the R5 behavior, although present in code has been dropped in r29639. Check inclusion for define BT_IOCTLS_PASS_SIZE.

With the new mechanism memory leaks allocating commands are solved, as they are meant to be allocated in stack, and dropping this R5 legacy, we are using 4 less bytes of memory per command (considerable as many bluetooth commands are just 3 bytes).

Bla bla bla, sumarizing the important part:

*** After this revision, be sure you recompiled and are using an updated version of at least: h2generic, bluetooth kit and bluetooth_server. As this change solved many issues but broke many compatibilities ***

For the ones who test often, there are some strings more on the LocalDevice panel information (preferences), there you will be able to check your dongle's bluetooth version, and the company who maufactured.

I use this update to thank Edwin Erik Amsler, who has shipped me some bluetooth devices to test, and a bluetooth 1.2 dongle which was recognized by the stack:



the phone discovered:

The Inquiry Panel

Maybe this is the most visual thing the bluetooth stack can show.

I have 2 bluetooth dongles connected: "CSR - bc4" and "Broadcom BCM2035". The further tests are gonna be pair the one with the other despite they are plugged in the same host. But by this way the input and the output are tested at the same time, as they don't know about each other and there is no such thing as loopback device in bluetooth context.

In the video can be seen how i set to discoverable the CSR one, and leave selected the Broadcom one. This will be used for the inquiry process. After the scanning and the retrieval of names, a phone and the CSR device are listed, and can be added to the Remote Device list.



Again UI suggestions/mockups are Welcome

Whisper BeNet running in Haiku

I have taken some time to comment about this parallel subject. Actually, I needed to check the commit date to know when that happened.

At the end I committed the initial sources of Whisper BeNet. Used Niue as build system for ZETA, and Paladin, for build system for Haiku.

Later on at the end of last December as per revision 13 the code is now running in Haiku. What I can see is that the network part might be working quite well, as it was possible to set a silence conference as can be seen in the screenshot. But the sound recording will be pending...

Some other evolution

This is the current state after some feedback. The information about the Local Device is not taking so much protagonism now, and the first tab the user can see is the list of the current remote devices(not implemented).

The intention is that the settings tab should not be needed for an average user, and the identified needed functions of this tab would be accessible also through a Deskbar applet...

Preference & next steps

In the next months all work is being focused in the codebase of the Phase1(ARCE) of the project. Three main things, fix bugs, clean, and implement features and tools which will make starting the Phase2 with a more comfortable Bluetooth base.

One of the most annoying things is that the bluetooth_server is not recognizing the hotplugged dongles on the system, they must be plugged before starting the server. So basically the management of the device(s) plugged in the Haiku system must be improved.

The second big one is the lack of tools, there are 2,  one informational, and another for discovering, but we cannot yet(in svn) take any action. The actions needed by the tests were taken by the remote device(phone).

In a document I was dropping during these months my UI Wishlist

There is a mockup of the future InquiryPanel which I would like to receive some feedback too, but the intention of the post is to show the current Preference application:

3 tabs, rightmost is pretended for global settings. The middle one, pretends to be a list of all known remote device: reacheable, paired, blocked, connected. And a description of what we know about it or services offered if available.

And the target of the post would be the tab which can be seen in the screenshot. Is the description of the LocalDevice, and the most basic action make it enter the game(discoverable). The good thing of those 2 checkboxes is that they are actually working. The black box is intended to show a laptop or Desktop machine(who know.. a smartphone?) icon depending how are you willing to identify yourself.

The panel is very basic so I thought there are many artists around that might want to give me some ideas with mockups or comments. I would be glad reading them before going on with the code.

BTW: The dongle identified in the screenshot is one donated by Pieter Panman one finally containing a valid bdaddr, thanks!

5th/6th Milestone, Phase 1 reached.

It has been since our first Google Summer of Code, back in spring 2007, that I wanted to write this post.

After achieving l2cap signalling communication in both ways, the test was to force the mobile phone to initiate any kind of communication with Haiku. Concretelly it was a SDP(service discovery protocol) session, in which the mobile asks Haiku, about which bluetooth services is Haiku providing.

There are some signals that needed to be replied and some issued by our side, after getting the first portion of data that actually belongs to the next upper protocol(SDP in this case).

Here in the kernel syslog we can see some traces:

Basically these 2 lines with HEX data, is the SDP packet traced at l2cap Layer. The packet is fragmented in 2 ACL frames so somehow the ACL segmentation could be tested here.  Eventually the target was to drop this packet, to an application that was creating a L2cap socket with the SDP psm(protocol service multiplexer).

So a small application was created faking a SDP server(mobile was acting as a SDP client) creating a l2cap socket listening in the SDP psm(similar to tcp/ip ports) and here we could see the first read of that app:

My mobile was actually freaking out not receiving any SDP response after all the successful pairing and the l2cap signalling configuration. Having many times to remove the Battery, or wait around 10 minutes to expire all connections.

So thats all for the moment. The  proposal document  is updated. In another post I will comment about what is my plan post-Phase1/Arce.

Thanks to all for support, but... there is still more to come:)