Same here!I would buy one also. And if a much improved production model were to be released at a later time, I would probably buy that one also.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.
Same here!I would buy one also. And if a much improved production model were to be released at a later time, I would probably buy that one also.
Tossing my coin in here as well. Would buy immediately as well.Same here!
Definitely interested, but as always, price matters. Any SWAG on that yet?If this were available today as a plug-and-play solution, how many here would realistically be interested in purchasing one? Trying to get a feel for what an initial batch might look like.
Successful command injection with the HVAC command set mapped and confirmed under controlled testing.
Now validating full standalone operation without the OEM NAV/MFD connected, including startup behavior and power-cycle stability.
The goal remains:
OEM-style physical controls
No screen
Plug-and-play
Curious to hear from those following the development:
- If you could completely remove the factory NAV screen, run any head unit you want, and relocate HVAC to OEM-style physical controls in the lower dash - would you choose that over current Teyes/Grom/Android options?
- And honestly, what would make you NOT buy something like this?
Appreciate the feedback. This community has been a big part of shaping the direction.
I just found this thread, and YES, this is exactly what I want to do to my '06 (12/05)! I have a non-nav GX470, and the aftermarket head unit and separate HVAC controls is ideal. The new head unit made an unbelievable difference, and it brought the tech level of that 22 year old truck into semi-modern times....not to mention how much better it sounds, the maps, etc.Successful command injection with the HVAC command set mapped and confirmed under controlled testing.
Now validating full standalone operation without the OEM NAV/MFD connected, including startup behavior and power-cycle stability.
The goal remains:
OEM-style physical controls
No screen
Plug-and-play
Curious to hear from those following the development:
- If you could completely remove the factory NAV screen, run any head unit you want, and relocate HVAC to OEM-style physical controls in the lower dash - would you choose that over current Teyes/Grom/Android options?
- And honestly, what would make you NOT buy something like this?
Appreciate the feedback. This community has been a big part of shaping the direction.
Yes, this.Definitely interested, but as always, price matters. Any SWAG on that yet?
On the "two knob/three knob/screen/no screen*" question, I default to robust and intuitive, no matter the knobs or screens. That said, I do enjoy some digitally small amount of displayed information, just because.
*There has to be a Dr. Seuss poem int here somewhere.

To follow up on my earlier enthusiasm, I'm itching to buy one!First off, thank you to everyone contributing here and through PMs. The level of engagement has been insane with the reddit/facebook traffic.
I am expanding the bench setup into a more complete OEM reference environment, so development can continue off-vehicle while also supporting prototype and product design decisions.
To support that, I’ve been building out a more complete setup:
A big part of this is getting the OEM connectors in hand early, so the prototype interface matches what the final install will look like, whether that ends up being a variant/universal plug-and-play harness or a clean breakout solution.
- LX470 Mark Levinson cassette unit (fitment)
- Dash harness (82136-60B40) for proper prototype breakout and connector strategy
- A/C amplifier (88650-60B60) for full bench testing
- Land Cruiser JBL cassette unit (fitment)
On the fitment side, the goal is to determine whether we can support both LX470 and Land Cruiser with a shared core design and minimal faceplate differences.
Up to this point, I’ve intentionally allowed the community to help shape direction but as we move into product development, decisions have to be driven primarily by engineering and manufacturing reality.
We’ve received a wide range of requests, including:
I’ve evaluated all of these. Some conflict with each other or add complexity without meaningful benefit.
- Screen vs. non-screen
- Two-knob vs. three-knob (including input types: fixed-position rotary, continuous rotary/encoder, push-switch combinations, etc.)
- Audio Knob
- OEM-style vs. more modern UI
- Auto Function
- Smog Function
As the project has progressed, I’ve now brought in additional support where it makes sense (firmware depth, and upcoming PCB + industrial design).
That does increase the burn rate, but it’s intentional, I’d rather move quickly and do this correctly than cut corners and have to redo things later.
Current development burn is roughly the equivalent of a 4 figure monthly car payment but on a weekly basis and will increase further as PCB design and industrial design are added.
I’ve had a few people reach out about buying one as soon as this is ready.
I’m usually not the type to support development-stage products myself. I prefer something that’s tested and ready to ship, and that’s still the standard I’m holding this to. That said, as development progresses (custom PCB, components like the MCU, supporting ICs, power regulation, communication transceivers, input handling, custom harnesses/connectors, enclosure/faceplate, etc.), costs ramp up extremely quickly.
I’m considering whether it makes sense to offer a small early batch / early access units possibly at a discount to help offset development and move faster into production, no decisions made yet just thinking out loud. If this were available today as a plug-and-play solution, how many here would realistically be interested in purchasing one? Trying to get a feel for what an initial batch might look like.
Shout-out @marshcat & @Hautsauce for the support
I've used nothing but auto in my LX for the past few years! Set it at 68 and forget it. It blasts to get to the right temp and then transitions to whisper quiet, all on its own.
Can we discuss briefly what the impact/result of having this installed is? I thought about sending this via DM, but thought perhaps it might help others as well.
I'm guessing, with this, we are then able to source a double din head unit of our choosing for replacement of the existing, yes?
Then, what about the amp and the cd player? Will the amp work? Or just replace it when the head unit is changed? And toss the cd player, yes?
And I guess I better hurry up and get the foam replaced in my door speakers for starters.
If there is a stereo guru out there, help a brotha out with what to do next. I had an Alpine I509 in the Jeep JK I had briefly (huge error buying that rig, but the stereo was killer!) so I'm leaning to another Alpine ILX series unit. Will a double din unit need additional trim bits, or will it fit in the existing spot with minimal effort.
Just trying to wrap my head around to total path here. And I have a birthday coming up and the family is asking for gift ideas...I need to strike while I can!![]()
No impact, separate systemThis might be a dumb question or I may have missed it but is there any impact to the immobilizer or security light on the dash? Can that whole thing just be removed or does it need to be addressed with this? I’m not familiar enough with its function except for when I was programming keys when I first got this car.
I would be interested in one or two depend on price, features and appearance.I’m considering whether it makes sense to offer a small early batch / early access units possibly at a discount to help offset development and move faster into production
First off, thank you to everyone contributing here and through PMs. The level of engagement has been insane with the reddit/facebook traffic.
I am expanding the bench setup into a more complete OEM reference environment, so development can continue off-vehicle while also supporting prototype and product design decisions.
To support that, I’ve been building out a more complete setup:
A big part of this is getting the OEM connectors in hand early, so the prototype interface matches what the final install will look like, whether that ends up being a variant/universal plug-and-play harness or a clean breakout solution.
- LX470 Mark Levinson cassette unit (fitment)
- Dash harness (82136-60B40) for proper prototype breakout and connector strategy
- A/C amplifier (88650-60B60) for full bench testing
- Land Cruiser JBL cassette unit (fitment)
On the fitment side, the goal is to determine whether we can support both LX470 and Land Cruiser with a shared core design and minimal faceplate differences.
Up to this point, I’ve intentionally allowed the community to help shape direction but as we move into product development, decisions have to be driven primarily by engineering and manufacturing reality.
We’ve received a wide range of requests, including:
I’ve evaluated all of these. Some conflict with each other or add complexity without meaningful benefit.
- Screen vs. non-screen
- Two-knob vs. three-knob (including input types: fixed-position rotary, continuous rotary/encoder, push-switch combinations, etc.)
- Audio Knob
- OEM-style vs. more modern UI
- Auto Function
- Smog Function
As the project has progressed, I’ve now brought in additional support where it makes sense (firmware depth, and upcoming PCB + industrial design).
That does increase the burn rate, but it’s intentional, I’d rather move quickly and do this correctly than cut corners and have to redo things later.
Current development burn is roughly the equivalent of a 4 figure monthly car payment but on a weekly basis and will increase further as PCB design and industrial design are added.
I’ve had a few people reach out about buying one as soon as this is ready.
I’m usually not the type to support development-stage products myself. I prefer something that’s tested and ready to ship, and that’s still the standard I’m holding this to. That said, as development progresses (custom PCB, components like the MCU, supporting ICs, power regulation, communication transceivers, input handling, custom harnesses/connectors, enclosure/faceplate, etc.), costs ramp up extremely quickly.
I’m considering whether it makes sense to offer a small early batch / early access units possibly at a discount to help offset development and move faster into production, no decisions made yet just thinking out loud. If this were available today as a plug-and-play solution, how many here would realistically be interested in purchasing one? Trying to get a feel for what an initial batch might look like.
Shout-out @marshcat & @Hautsauce for the support
100% interested.If this were available today as a plug-and-play solution, how many here would realistically be interested in purchasing one?