View Single Post
Posts: 16 | Thanked: 6 times | Joined on Oct 2007 @ Helsinki, Finland
#12
Sorry for offtopic.

Originally Posted by sparkling View Post
I have reported the problem, but I do not know anything about "hcidump", and frankly it's not my job to do Nokia's quality assurance legwork. Nokia is in the mobile phone business and they certainly should have a Treo available for testing.
There is quite a lot of bluetooth IOP testing being done (in context of single companies and also as demanded by the Bluetooth Special Interest Group), some exotic devices (in Nokia's opinion) might slip through the 'net'. Maybe Palm will have a presence in the next bluetooth unplugfest..

The problem is that the BT profile implementations in some phones are lackluster and contain bugs that cannot be remedied on remote end. Then theres the "slight" issue that especially in the US the operators have much power over the hardware vendors and retail market - end result is crippled operator-specific devices (sad, sad).

The bluetooth (user space) functionality in the tablets, bluez-utils, is developed completely in open source and free software (google for BlueZ). Bugs can be also reported in that context, and fixes eventually end up to tablets, too. Kernel space part is synced for the most into linux mainline. The developers are usually not very willing to implement device specific hacks, they rather stick to the standards. If helpful users can provide logs, they still might.

Anyway, I don't try to justify anything, just hopefully providing some insight. I found one bug having word "treo" in summary (here), made a few days ago. If this is your bug, thanks for that.