BlueBus: A fully integrated A2DP Bluetooth solution

[Mattn1192]

Update with the shipment?

[t3ddftw]

No worries, it’s worth just having it on order so I don’t forget to order when it’s back in stock!

My other question is, will this work on non-OE headunits? My OE is starting to screen burn and I haven’t had luck tracking down a food replacement LED screen

It won't work with non-OE radios. Is it the Nav screen? If you contact me via email, I can probably find time to replace it for you. There are other shops out there that replace the TFT screen in the Navi too.

Thanks!
-Ted

[Chas3n]

You only need the BlueBus unless you want to take calls, in which case you'd also want the TCU adapter (54-pin for most M3s, especially post-LCI).

Unfortunately, anyone ordering today is not likely to get one from this batch, which means you're not getting one at all until sometime next year. The state of the supply chain has halted the project.

-Ted

No worries, it’s worth just having it on order so I don’t forget to order when it’s back in stock!

My other question is, will this work on non-OE headunits? My OE is starting to screen burn and I haven’t had luck tracking down a food replacement LED screen

[simonnim]

Wow... Wish I jumped on the previous run..

[t3ddftw]

Ted,

Question about operation of the Bluebus. I'm sure this is an Android configuration thing, but when using Google Maps and listening to audio directions through BlueBus and a CD53, I miss the first fraction of a second of audio. With no other audio playing, it appears that the Maps audio is "paused" while nothing is being said, then it takes a fraction of a second to un-pause it before the audio comes through. Once the directions audio is done, it goes back to paused. The result is always that you don't hear the first word or two. Is there a reason why it would enter a "paused" state when there is no audio being played? Is there a way to change that behavior? Or is this purely a per-phone implementation thing?

Thanks!
Jason

So, this is caused by the Bluetooth module entering an audio "stream sleep" state. About ten seconds after the last bit of audio is played, the audio path enters this sleep state and it takes it about a second to spool back up when data is seen again. Unfortunately, I can't really stop it from entering this state via configuration, but I have found some possible work-arounds, though they're both pretty ghetto:

1. Issue a volume down and then volume up command. This wakes the stream back up.

2. Play some built in tones through the BC127, but this results in random pops and only keeps the stream alive for the length of the tone.


An update on the October branch:

The factory said there were some issues with FedEx getting parts to them (!?), but the batch is scheduled for assembly on the 14th and shipping on the 19th, so it's yet another week delayed 😑

Thanks!
-Ted

[krambjas]

Ted,

Question about operation of the Bluebus. I'm sure this is an Android configuration thing, but when using Google Maps and listening to audio directions through BlueBus and a CD53, I miss the first fraction of a second of audio. With no other audio playing, it appears that the Maps audio is "paused" while nothing is being said, then it takes a fraction of a second to un-pause it before the audio comes through. Once the directions audio is done, it goes back to paused. The result is always that you don't hear the first word or two. Is there a reason why it would enter a "paused" state when there is no audio being played? Is there a way to change that behavior? Or is this purely a per-phone implementation thing?

Thanks!
Jason

[jet_dogg]

That date is +/- some days. The units being produced now are scheduled to ship to me on the 11th of October, then it usually takes 2 - 3 weeks for me to unpackage, program, test and encase each unit.

Thanks!
-Ted

Thanks for the update Ted, these things happen and are beyond anyone's control.

[Mattn1192]

Did you order from ECS?

Yes

[t3ddftw]

Is there anything else needed to order? Or just the link to ECS with the box?


Sent from my iPhone using Tapatalk Pro

You only need the BlueBus unless you want to take calls, in which case you'd also want the TCU adapter (54-pin for most M3s, especially post-LCI).

Unfortunately, anyone ordering today is not likely to get one from this batch, which means you're not getting one at all until sometime next year. The state of the supply chain has halted the project.

-Ted

[Chas3n]

Is there anything else needed to order? Or just the link to ECS with the box?


Sent from my iPhone using Tapatalk Pro

[VisorM3]

That date is +/- some days. The units being produced now are scheduled to ship to me on the 11th of October, then it usually takes 2 - 3 weeks for me to unpackage, program, test and encase each unit.

Thanks!
-Ted

Awesome, looking forward to it, thanks for the update Ted!
I'll go make calls in my car for fun since it's pretty much stored for winter at that point but all good haha

[t3ddftw]

Mine is from ECS and just got an update this morning that it should be October 28th instead of 29th initially that I received 2-3 days ago lol
I was also pretty bummed after waiting all these months

That date is +/- some days. The units being produced now are scheduled to ship to me on the 11th of October, then it usually takes 2 - 3 weeks for me to unpackage, program, test and encase each unit.

Thanks!
-Ted

[VisorM3]

Did you order from ECS?

Mine is from ECS and just got an update this morning that it should be October 28th instead of 29th initially that I received 2-3 days ago lol
I was also pretty bummed after waiting all these months

[simonnim]

I was looking forward to receiving them this week 😩😩😩 damn it… mine says October 29th now. A giant kick in the chi-chi’s

Did you order from ECS?

[Mattn1192]

I was looking forward to receiving them this week 😩😩😩 damn it… mine says October 29th now. A giant kick in the chi-chi’s