Other than using Shazam, when is this an issue for people? On Zoom or Facetime, the audio connection is almost certainly using an HFP/SCO connection, which is going to downgrade to an 8K or 16KHz sample rate regardless of where the mic is coming from.
I don't use Shazam, but it doesn't actually make sense to me that you would even use Shazam while listening to audio in your Airpods. I thought that was for music you heard from something other than your own device. You are listening to music in your Airpods and trying to identify a song from another source at the same time?
I genuinely don't understand why anyone would be interested in using frameworks on top of JS. None of them can do anything that pure JS can't do (+libraries), they just make it less readable and less intuitive compared to the original C-like syntax of JS. JS libraries make sense, of course, but why keep messing with the syntax?
Bluetooth/BLE has the unique problem that you don't own the code on both sides of the wireless tx/rx. In webdev, you have control over client side and server side code and can make them work together in some unique way, without worrying about interoperability. But with Bluetooth/BLE devices, not only do you need to be able to communicate with random peers you've never seen before, those peers also need to be able to connect to countless other BT/BLE devices and read information about the services available on those devices. In order to enable this interoperability between BLE devices, a standardized format needed to be developed: GATT. GATT is the very highest layer of this interoperability and is considered "user-level" from the perspective of a BT firmware dev. In BT classic, the SDP table provides nearly the same service as GATT, except that data isn't carried over it, just service discovery.
> Never thought about how confusing it would be when banks start playing musical chairs with your mortgage.
I think Dodd-Frank addressed this, but maybe it was some legislation after. I think they made ACH details transferrable and padded payment windows iirc.
> But the more people that realize that, the less soft the landing might be.
Yeah, definitely, but that's why they crank the interest rate through the ceiling. People that are cash heavy could come up quite a bit if left uninhibited. Of course, they can still do that, but not in a property acquisition kind of way.
This is a very layman's understanding, so take it with a grain of salt.
If you have a ton of cash on hand when markets go to shit and interest rates go through the roof you suddenly have something no one else does: cash on hand that was traded when that dollar was worth less. When you buy property or stock with that money, you've effectively bought it at a hefty discount. When the markets and interest rates normalize again you stand to make huge gains.
They lock up financing to put a cap on growing inflation, but that same cap stops people from taking advantage of the market and thereby continuing inflation through a new avenue.
Interesting. What you say is true, but there is an opposing force. If someone has cash on hand when interest rates spike, they can buy when everyone else has a much harder time getting loans. So this makes things appear cheaper because there are less buyers on the market.
BUT the opposing force is the inflation that originally justified the spike in interest rates. That cash they are holding is simultaneously worth less due to the devaluing of the dollar, but also enables you to operate when others have run dry.
EDIT: so I guess there is a distinction in the value of the dollar when you are using it to buy large things that require debt vs the day to day little items. Because the little items will get inflated easily as everyone allocates their limited capital to food and fuel. But the real estate market will stagnate as no one can trade houses around in this environment.
I agree with what you put here; I think there's also a "threshold" of cash on hand you have to have in order for it to be useful in the ways we're describing. It's likely a rather large sum.
Well that's doable with enough embedded memory, but it will become an issue when you want to sync audio and video. So it really is less of a protocol thing and more of something that an individual product could design in, allowing a user to toggle the feature via an app.
This article is not about Bluetooth in general, it is a deep dive into the bugs buried within the Android Bluetooth stack.
And what the writer is not acknowledging at all is that the underlying hardware being used is highly variable. Android runs on top of numerous Bluetooth chipsets. So when he gets a patch to seem to work on his hardware, there is no saying that it will work for a different Android phone.
Furthermore, this all depends on what else the device is up to at the current moment. If you have shared BT+Wifi chipset and you are streaming a video over wifi, then streaming the audio to your headphones, the device is having to allocate resources based on wifi usage and BT. So playing audio stored locally and audio via a stream is not necessarily going to get the same CODEC parameters.
There is so much nuance to this subject that the author just hasn't considered. Please be careful what you read.
Former custom ROM developer here who has reviewed and integrated valdikSS modification.
It’s not a bug that the patchset is doing, but enables dual-channel SBC to be negotiated in the source and sink connection. This enables the higher bit-rate without exceeding the maximum bitpool both Android and BT receiver impose.
There’s still negotiation occurs between the source and sink and if either one of them doesn’t support dual-channel SBc, it’ll fallback to whatever its supported. All the device that i had maintained supports it, while some cheap speaker that i test at that time doesn’t and able to negotiate joint stereo session.
Right, it’s more of a configuration that is being changed. But my point was that this is all above the HCI layer, so at the end of the day it’s related to the specific host-stack implementation and not to do with Bluetooth in general.
I guess I’m basically saying the title should be changed
Unrelated: Every once in a while you'd see a familiar name on this website. Thank you for goodbyedpi, it saved me when all isps in my country started blocking raw.githubusercontent.com among others ofc :)
