Adapter makes Google’s wireless Android Auto a reality

Bluetooth and Wi-Fi combine to untether smartphone-to-car connections…this time with a Google, versus Apple, angle.

Last month, I took apart a third-party adapter that aspires to augment Apple’s CarPlay interface with wireless connectivity between iPhone and vehicle.

This time, I’ll be disassembling the other adapter I’d mentioned at the end of late January’s initial conceptual coverage, in this case intended to wirelessly bridge between a car and an Android-based handset using Google’s Android Auto protocol.

But once again, the originally planned hardware target of my dissection attention isn’t what you’ll actually be seeing today. Initially, I’d planned on taking apart the v1 AAWireless unit, which I’d bought several years back in its original Indiegogo crowdfunding form.

But then I remembered that AAWireless had notably iterated the hardware (and associated software) design in-between that initial version and what ended up going into full production where it was sold and stocked not only by the manufacturer but also retailers like Amazon. AAWireless has already moved on to its second-generation product, in fact.

Supplier switcheroo, part 2

I didn’t want to further limit the project’s relevance by focusing on the rarer premier version of the first-generation offering (which put the company on the map, mind you, but still…). Instead, today you’ll be seeing the insides of this adapter (model BY969C).

It came from a company named “Vnilrgle” (believe it or not, and despite the user manual variously alternatively mentioning “TERUNSOIU”, or maybe that’s “TERUNSOIL”, as the supplier) and cost me a whopping $9.99 plus tax (with free shipping) from Woot in late February (versus listing for $48.87 on Amazon as I write this). Here are more stock shots to whet your appetite.

As you may have already noticed from one of them, this adapter model was of particular interest to me because of its low price, its quality construction (belying the $10 I paid for it), and its integration of NFC functionality, which aspires to simplify the initial setup process.

I’ll start out with shrinkwrap-inclusive front and back shots, as-usual accompanied by a 0.75′′ (19.1 mm) diameter U.S. penny for size comparison purposes, and revealing additional labeling.

The shrinkwrap-clinging stickers are absent from the now-clear-plastic-less backside photo that follows.

Time to open ‘er up.

Some literature bits (here’s an online version of the user manual).

And an optional-use double-sided sticker for, as I also said last month, adhering the wireless adapter to the vehicle interior.

As with its Apple CarPlay-supportive predecessor, this one includes a USB-A-to-USB-C adapter.

And here is today’s patient standalone, viewed from top.

Bottom.

Cable-entry point.

And cable connector-end perspectives.

Sh-sh-sh-shattered

(Obligatory admittedly-obscure-to-at-least-some section header reference)

Now to get inside. You’ve likely already noticed the gap between the silver-color circumference of the device body and the clear flat regions, both of which I’d assumed were made of plastic (for NFC reception reasons). My attempts to insert a spudger were unsuccessful, however.

So, I stuck the device in my vise (see what I did there?) in preparation for an attempted hacksaw-cut of one side. Oops.

I guess that’s glass, not plastic. And I won’t be using this device post-teardown. Onward.

Now for the other side, with tap-assistance from a ball peen hammer.

See those four screws? Not anymore, you don’t.

And with them removed, we have achieved liftoff.

An “Ultra” foundation for the fortunate

Let’s look first at the PCB underside (based on a device orientation assumption that places the product logo on the NFC antenna “top” side, with the marking minutia on the “bottom” side).

At left in the three-area-dominant IC row is the system processor. I mentioned last month, generally speaking about the wireless Android Auto and/or CarPlay product category, that “these are commonly Arm-based”. Judging from the markings on top of this one, there’s no doubt as to whose CPU core(s) is/are inside.

I’d even go so far to guess Cortex-A7 in generation. But who makes it? A search on “BU2025021” brought up bupkis. And the only reference I found to an “A7 Ultra” was associated with this Vanzen dual Android Auto-plus-CarPlay wireless adapter.

Although…”Cotex”?

Anyhow, to its right is the presumed serial-interface (therefore eight-lead package) firmware storage NOR flash memory, from GigaDevice and marked as follows.

AP2133
5F1GQ5UEY1H
UG5131

“1G” is suggestive of a 1 Gbit capacity, but I can’t find a direct reference to the IC anywhere online; reader assistance is welcomed! GigaDevice also makes Arm-based SoCs, by the way, so the company also acting as the source for the “A7 Ultra” wouldn’t be a complete surprise to me.

If you’re wondering (assuming my guess is correct) why 128 Mbytes of storage is necessary to implement a seemingly elementary device like this, my answer is two-fold albeit related.

It doesn’t just handle Android Audio protocol and USB-to-wireless bridge functions
And that capacity isn’t solely devoted to code

Turns out there’s also a web server (and pages) running inside the device, used for firmware-update and broader technical support-outreach functions, as this user manual page documents.

In fairness, circling back for a moment, the CarPlay adapter I took apart last month offers similar capabilities. I finally dug up an online version of the user manual for it; here’s the relevant page.

What’s the frequency, Kenneth?

(Another obligatory admittedly-obscure-to-at-least-some section header reference)

Finally, at far right is the wireless communications subsystem, based on the AIC8800DC40 controller from AICSemi, a company previously unknown to me, and surrounded by embedded Wi-Fi and Bluetooth antennae. Once again referencing last month’s writeup, I’d written the following.

Two wireless broadcast links are necessary: 2.4 GHz Bluetooth for initial setup, and Wi-Fi for ongoing streaming. The latter is usually based on the 5 GHz band for higher transfer bandwidth, since range isn’t a concern in a diminutive vehicle interior.

But in that teardown, I’d only found one antenna, suggestive of Bluetooth-plus-Wi-Fi shared usage, therefore 2.4 GHz-only system functionality. And this time, a datasheet I found online for the AIC8800DC40 suggests that it has 2.4 GHz-only Wi-Fi capabilities, even though the device documentation makes the following claims.

Wi-Fi Bluetooth module frequency:
Bluetooth 2.4 GHz, Wi-Fi 2.4-5.8 GHz

So… In search of clarity, I went looking for an FCC ID, which I hoped would lead me to definitive certification documentation. Believe it or not, nowhere related to last month’s patient—packaging, literature, or device itself—had I been able to find an FCC ID reference, or even a product name that might indirectly point me to my desired certification-data prize. Here’s what Google AI Assistant rightly said in response to my search query on “WOLIOS carplay adapter FCC ID”.

The WOLIOS wireless CarPlay adapter does not have an official, dedicated FCC ID registration tied directly to the “WOLIOS” brand name. Budget-friendly online resellers like WOLIOS often rebrand generic white-label factory units (such as common smart dongles) that may display general CE/FCC compliance claims or use an unverified label rather than maintaining an authentic, searchable filing in the FCC ID Database.

Alrighty, then. This time I at last had a valid model code, BY969C. With it, I tracked down the FCC ID (2A5XO-BY969D), which as it turned out covered a variety of products with different model numbers, physical appearances and both Android Auto and CarPlay support, suggestive of common hardware differentiated via firmware. And yes, both 2.4 and 5.8 GHz beacon support.

Speaking of antennae, and in closing, let’s now flip the PCB over to its topside and more closely check out that NFC subsystem.

Sequentially detaching the antenna from the PCB, both from connector and adhesive perspectives, and then peeling off its accoutrements, results in the following image sequence.

Note the LED that shines through the NFC antenna center “hole” and out the top of the device.

And now to dispense with the foam (at least most of it) between the double-sided sticker and antenna itself.

A Google search on the “BY969-LS-V01-NFC-HXW” product code stamped on top of the NFC antenna was of no help whatsoever. Alas. Unless, that is, I’m mistaken and it’s actually a Textured Johnny Collar Sweater Polo from Original Penguin by Munsingwear, sold by (but sold out at, as I type this) J. Crew Factory stores.

With that final bit of silliness out of the way, I’ll wrap up for today. Sound off in the comments with your thoughts on Rolling Stones or R.E.M. songs, men’s sweaters or anything else discussed in this piece!

—Brian Dipert is the associate editor, as well as a contributing editor, at EDN.

Related Content

The post Adapter makes Google’s wireless Android Auto a reality appeared first on EDN.

Source link