Tag Archives: macos

Bluetooth signal quality on MacBook Pro

Posted on by
Reply

If you press the Option key then click the Bluetooth icon on your MacBook Pro then MacOS will show you the signal strength (RSSI) and other info about your Bluetooth devices. RSSI is the “Received Signal Strength Indicator” as explained by ChatGPT. The current RSSI for my bluetooth speakers is -67dBm, which ChatGPT explains:

An RSSI value of -67 dBm is generally considered a good signal strength when it comes to WiFi, and the same could be roughly said for Bluetooth and other wireless communication technologies. In terms of qualitative interpretation:

  • -30 to -50 dBm: Excellent signal strength. This is about as good as it gets. Usually, this is only seen when you’re very close to the access point or device.
  • -50 to -70 dBm: Good signal strength. For most general applications, this range provides a reliable, strong connection. Voice, streaming, and even video applications usually work well in this range.
  • -67 dBm: This specific value is often cited in WiFi scenarios as the minimum strength for reliable voice applications.
  • -70 to -90 dBm: Fair signal strength. The connection is more susceptible to interference and might not be reliable for all applications. Data rates will be lower, and minor obstructions can cause the signal to drop.
  • Below -90 dBm: Poor signal strength. The connection is unreliable and might drop frequently. It’s challenging to maintain a stable connection in this range.

So, an RSSI of -67 dBm is generally good for most applications, including voice and streaming. However, the actual performance can vary based on the specific wireless technology in use, the environment (presence of physical obstructions, other interfering signals), and the application’s specific requirements.

The End of OS X

Posted on by

Today I read The End of OS X. I particularly liked the bit about the Unix philosophy:

  1. Make each program do one thing well. To do a new job, build afresh rather than complicate old programs by adding new “features”.
  2. Expect the output of every program to become the input to another, as yet unknown, program. Don’t clutter output with extraneous information. Avoid stringently columnar or binary input formats. Don’t insist on interactive input.
  3. Design and build software, even operating systems, to be tried early, ideally within weeks. Don’t hesitate to throw away the clumsy parts and rebuild them.
  4. Use tools in preference to unskilled help to lighten a programming task, even if you have to detour to build the tools and expect to throw some of them out after you’ve finished using them.