07-21-2018, 09:40 PM
(07-21-2018, 06:31 PM)badbat75 Wrote:(07-19-2018, 01:52 PM)TheOldPresbyope Wrote: As an expedient, I copied over /usr/bin/hciattach and /usr/bin/hcidump from a moode-r42 I built with mosbuild.sh.
Now the moode-r42 I built with @badbat75's tool is working, including Bluetooth configuration.
Emboldened, I tried using a pair of Sennheiser HD-450BTNC headphones I just picked up in the Amazon Prime Day sale. The aptX codec is baked into their firmware.
Hcidump shows that the moOde Bluetooth stack negotiated the use of the aptX codec instead of the default SBC (subband codec) during the connection phase, so the stack knows it has the openaptx codec available. Once connected though, I'm getting a rhythmic pulsing noise with a roughly one-second interval instead of music when I hit play.
Time to create a new thread devoted to the codecs, as Tim suggested.
Regards,
Kent
Many thanks Kent for your feedbacks. I'm trying to sort-out the problems you described.
Anyway, thank you again for testing the APTx codec. Unfortunately I don't have any aptX reproduction devices so I couldn't test it, but I'd like someone will test aptx codec as sink device to see if it works: if not, it means this codec can't be used at the moment.
I think my inability to stream music to my headphones is just a confirmation of the Warning message about openaptx which I posted about earlier. As you can see in my post today about the Creative BT-W2 adapter, I have found a hardware/firmware solution which bypasses the Bluez stack.
Then there's the AAC codec. I don't have any devices which use AAC over Bluetooth (do Apple products?) so I can't test it.
Regards,
Kent
