There is in my mind until I understand a good reason why the following scenario exists.
To be complete, but probably irrelevant, immediately after both of my gos installations, I found BT to be on. So I turn it off.
Seems like I'm done, no? I'll get into why I'm so fanatical about chucking BT below. But...since I am, o go through all the settings I know to reach, looking for my arch enemy, Bluetooth. Among the few is found in settings>apps>see all x apps> (with show system apps selected) Bluetooth.
There I find that this app has permissions to access a lot of things, like files, sensors, network, to name a few. Viewing the permissions reveals that they are all enabled and grayed out. Can't be disabled.
This begs the question: whats the point of disabling my ability to control access of a thing (that happens to be used to radio stuff in and out of what it can access) if I can actually turn it off? Without a sensible explanation, the situation is disturbing.
Now to why I'm overboard about this and use"disturbing".
My surface running updated win10 has, of course, BT capability. Left to its own devices, it will install some 15 drivers that allow BT to poke its nose into my system using various protocols. The drivers seem somewhat persistent. I found only one way to convince win10 that I goddamn fucking do not want Bluetooth in my surface: cut it off in uefi. This does the trick. No traffic per wireshark, no ability in any settings to enable BT.
If this same ability to kill BT in windows exists in gos/android, its not obvious to me that its effectively working.
Why do I want to control BT so badly?
Bluetooth was introduced before 9/11. Before McVeigh. Before Lockerbie. Before, I think, you could still install win95 on all your machines that would run it from the same CD.
Security then was such a joke that broward county required more care to keep someone from logging in to pay my water bill for me than boa required to keep others out of my business.
You couldn't joke about a bomb at the airport in 1979 but getting one on board and detonated seemed pretty trivial given the continuing incidents. We due don't have things like kiddie scripters. Hacking wasn't seen as a legit Method for your own little group of creeps to influence society.
Bluetooth was how you avoided wires in transport of mostly digital audio. I had some modules that did that. My bet is that I could have hacked into them to repurpose them, but I had two Harris prism radios leftover from a project, which did raw dsss with a mere setting of parameters. Cypress semiconductor started selling a 7 chip that did short range dsss soon after that and they still do.
None of these things had security in mind then. And I'm sure that workable drivers can be found.
In 1987, I was designing the camera head for a face recognition system. The hardware and firmware, including 16-bit is a card, were done but needed testing. The two guys doing the analysis software in I think winnt, were slow to get me something. A high school buddy happened to work there. What I needed was the old outp and inp (I think those are the names) that were no longer available in Borland c. Two days after I asked, this guy delivered to me a file that he wrote in Microsoft assembler. I had what I needed. It was that easy for him to poke through the security layers that nt had put in my way.
Security was just then starting to be taken seriously, long after Bluetooth should have been buried.
This mess gives me the concern that bluetooth, perhaps not by intent, offers more hacking possibilities than I care for. Having it remain in any of my systems whether I like it or not only sharpens that concern.