Hi again, mtnMan and Alexander,
et.al. (if anyone else is reading) —
mtnMan, in response to our latest query, I don't have an answer. I was simply trying to "head you off at the pass" from trying out the K/M firmware updater unawares. (Months ago, I forced this updater to run as a test to help an Apple Discussions participant, and
crashed my eMac. No big deal, but a bit startling if you're not expecting it...)
Now here are some further thoughts I'd begun drafting before seeing your follow-up...
(1) I agree — these developer tools are really aimed in a different direction, AFAIK. However, I'm still developing an understanding of the specifications and their implementation... I just thought you'd be interested in flexing what "hidden" tools there are, particularly since you'd expressed acumen with 802.11.
Btw, segueing to a slightly different topic: note that there are
a few Bluetooth-related logged messages in, e.g., your
system.log once in a while. As an example, you can view entries during every boot process about CSRHIDTransitionDriver (checking for a startup keyboard shortcut) while a startup volume is being sought; then IOBluetoothHIDDriver starting and seeking a handshake from your keyboard. Beyond that, I can't promise they're necessarily much help — although Bluetooth Error Codes are well defined. (See Volume 3, pp. 324-325 of the Core Specification v2.0 + EDR, if you dare dip into the 1230-pp. pdf!)
(2) My pleasure; just wish I could help more with what you seek. I recognize your objectives in this regard, and I'll keep 'em in mind — just in case I encounter an "
Aha!" somewhere down the line.
(3) Perhaps I dashed off that section of my post a bit too hastily. I don't intend in any way to deny a reality that many are experiencing. (Although I hope you'll note — say, by scanning through some Bluetooth Keyboard/Mouse forum threads — that following some ~straightforward strategies to the letter are often necessary for most trouble-free Bluetooth performance. (As Alexander is fond of saying in a similar context, "Don't ask me why.") In this same vein, I've been sharing off-and-on lately this quote from a recent article by Glen Fleishman about UWB (TidBITS #819, 06-Mar-06): "Just when... you've figured out that Bluetooth can work if you perform the steps just right..."
That said — back to brass tacks. Although I'm ~an "Intel-based Mac wannabe" (jealous, but too poor), I am trying to follow the trials and tribulations as closely as I can. And to participate in exploring for solutions — though this is a lot more difficult when I can't directly test a purported "fix." By all means, the objectives of the Bluetooth SIG — and of Apple — include a relatively "transparent" interface that doesn't require a lot of ongoing tinkering by users. And, since y'all are experiencing such troubles, obviously things aren't working as they should in that regard.
Imo, you are mostly correct in re: the module firmware: no "stand-alone" updater is presently available (nor required?) for those of y'all with 2.0+EDR chips in a Mac. But — just fyi — release date isn't always as meaningful as it may intuitively seem. I bought my eMac 1.42 GHz in mid-May 2005, with CTO Bluetooth, K&M. The eMac's manufacturing date (see S/N) wasn't too far previous. Yet the Bluetooth Firmware Updater 1.2 [11/23/04] demonstrably upgraded Firmware from version 2.1241 to 2.1586. For clarity of others who may be reading, "firmware" in this case refers to software instructions residing on the Bluetooth chip, not on the Mac's ROM, etc. [Btw, I appreciate your sharing that your Bluetooth Firmware Version has changed from (?) to 0.1.17 in Software Profiler. I've been trying to keep track of these versions and changes; they're model-specific. Do you perchance recall the original version reported upon purchase?]
As I think you've guessed, my statement about "platform-independence" was meant in the context that its Bluetooth specification, chip, card, software, etc. are not a dependent variable of the Intel processor. Am I reasonably sure about this? Yes. Keep in mind that Apple began implementing Bluetooth c. 10.2.x Jaguar; adding Bluetooth v.1.2 features in 2004 and 2.0+EDR beginning January 2005. They're still "tinkering" with things — and will, I'm sure, continue to do so. If Apple's track record holds true, you can expect that they'll remain on the forefront of implementing new technologies; and they'll continue to issue OS X 10.x.x updates/improvements on a regular basis — particularly wrt Intel-based Macs' issues.
Am I absolutely sure? Nah — that'd take digging into the code — beyond my available time (and, largely, my ken). I presume that the Bluetooth software has been reworked into "Universal Binary" — but, beyond that, I've seen no mention anywhere about Apple's Bluetooth implementation being modified for Intel-based Macs. Someone in bluetooth-dev asserted that Bluetooth doesn't support Rosetta, but that was promptly refuted, and is beside the point anyway. I have used Pacifist to scan through the "MacOSXUpdateCombo 10.4.6PPC.pkg" contents; perhaps I'll try to do the same for the Mac OS X 10.4.6 Combo for Intel download one of these days... I can say that the statement about "specific fixes for the following applications and technologies [including]... using Bluetooth wireless devices" is definitely true — and I'm sorry to note that these haven't addressed your issues..
(4) Sorry to hear that your experiences with AppleCare haven't been satisfactory. When I've reached higher-level support, folks have always been great — spending their time, and pulling up schematics, etc. to ensure we were arriving at correct answers.
Perhaps you've reached a point where using BugReporter would be beneficial. (Requires free ADC membership.) If you decide to go this route, Apple provides FAQs and a "Bug-Reporting Guide" for using BugReporter. Simon Tatham's How to Report Bugs Effectively is an excellent resource. I'm reticent to "get your hopes up," but investing the necessary effort into this approach does assure that a "bug" is tracked and taken seriously. While not promised, follow-up accountability may also occur.
(5) Cool.
(6) I'm always interested in noting and following the results of direct experimentation. Unfortunately, it can sometimes be difficult to control all the variables. One example is that Bluetooth protocols within the HID profile specification differ quite a bit for keyboard vs. mouse. Btw, please understand that all of my comments have focused on Bluetooth — not AirPort. (What I said about AFH being more informational than anything else. It was intended, at least in part, to support my argument that Bluetooth was not the likeliest candidate as the source of folks' AirPort issues in some of the other threads. Sounds like you agree.)
(7) MIscellaneous stuff. We haven't really talked about what I consider "standard Bluetooth troubleshooting" — beyond the discussion about firmware. Again — Bluetooth, not (necessarily) AirPort. A few items for the moment:
(a) Have you done an evaluation of other potential sources of ~2.4 GHz RF and other interference in the environment? If not — this can become a semi-complex subject in its own right, but this KnowledgeBase article provides a starting point...
(b) In re: "sluggishness," my experience points to three factors that may be involved: "in-place" voltage, interference, &/or the driver itself. For example, I've started using SteerMouse — in part because it provides excellent tracking speed /acceleration control for my Bluetooth mouse. (Plus programmability, etc. for when I'm using my old optical mouse.)
(c) When you get a chance, take a look at the Bluetooth Troubleshooting Checklist I posted a few weeks ago. Perhaps something there will be helpful with your Bluetooth performance.
(d) In case you haven't realized, Alexander is a Bluetooth shareware developer — and all-around savvy resource...
HTH!
Regards,
Dean
[2,111 ⊥ 3,525]
