AARE: A proof-of-concept open-source implementation of Android Auto
Comments on “AARE: A proof-of-concept open-source implementation of Android Auto”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
AARE is an open-source proof of concept that reimplements the phone side of Android Auto without Google Play Services, letting apps such as CoMaps, Organic Maps, Tempus and WhatsApp run on a car screen. The project reports two real cars working, but units that check for Google-issued certificates reject its self-signed one, so users must extract Google's key. Google Maps and Waze can't be hosted. A desktop head unit allows testing without a car. The compatibility reports couldn't be independently verified.
Why it ranked
No. 13 of 51 with a score of 0.61. The panel rated it highest on new information (0.95) and technical depth (0.90), lowest on audience breadth (0.44). Placed No. 13, No. 20 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Open-source Android Auto reimplementation with detailed protocol and integration content; early-stage and only tested on few head units, so moderate significance and substantiation, with clear new information and a new-project release.}
- AI judgeJudge 3gpt-5.6-luna
- A detailed, reproducible early open-source implementation with extensive protocol, compatibility, security, build, and testing documentation. It is highly relevant to Android, automotive, and open-source builders, though its audience is narrower than general software engineering.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.61total under rubric v2.3
- Significance0.51
- Reader interest0.73
- Audience breadth0.44
- Practical relevance0.64
- Substantiated0.79
- Technical depth0.90
- New information0.95
- Counts against: Promotional0.06
- Counts against: Overclaim0.15
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.50 | 0.45 | 0.58 | 0.51 | 0.13 | +0.24 | +0.122 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.64 | 0.72 | 0.82 | 0.73 | 0.18 | +0.26 | +0.189 |
| Audience breadthHow many people who build technology does it concern? | 0.40 | 0.55 | 0.38 | 0.44 | 0.17 | +0.13 | +0.058 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.66 | 0.60 | 0.65 | 0.64 | 0.06 | +0.22 | +0.140 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.93 | 0.55 | 0.90 | 0.79 | 0.38 | +0.05 | +0.040 |
| Technical depthHow technically substantive is it? | 0.99 | 0.80 | 0.90 | 0.90 | 0.19 | +0.05 | +0.045 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.93 | 0.95 | 0.98 | 0.95 | 0.05 | +0.05 | +0.048 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.12 | 0.03 | 0.06 | 0.09 | −0.19 | −0.012 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.15 | 0.25 | 0.04 | 0.15 | 0.21 | −0.11 | −0.016 |
| Sum of contributions | +0.613 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.613 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-08/13/"><img src="https://rubric.hrih.si/badge/2026-11-08/13.svg" alt="Ranked #13 on Rubric, 8 Nov 2026" width="238" height="28"></a>Claim check
Claim check: 1 no source given · 7 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkNumber
AARE works with the factory Denso Ten E-DA2 unit of a 2026 Toyota Land Cruiser 79 series over USB with a Samsung Galaxy S23, with all features tried, using AARE's own self-signed certificate.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Works, all features tried (#37), with AARE's own self-signed certificate”
The source says No passage could be compared.
Source cited by the article: github.com/prototux/AARE/issues/37
Couldn’t checkNumber
The Skoda Octavia V MIB3 unit rejected AARE's own self-signed certificate with AUTH_COMPLETE status -3, but connects with the extracted certificate.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “with AARE's own self-signed certificate the unit rejected the connection (AUTH_COMPLETE status -3, #48); with the extracted certificate it connects”
The source says No passage could be compared.
Source cited by the article: github.com/prototux/AARE/issues/48
Couldn’t checkNumber
The factory Denso unit of a 2024 Toyota RAV4 rejected AARE's self-signed certificate.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Rejected: the self-signed certificate (#46”
The source says No passage could be compared.
Source cited by the article: github.com/prototux/AARE/issues/46
Couldn’t checkNumber
The factory unit of a 2024 Ford Transit rejected AARE with status -3.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Rejected: status -3 (#44”
The source says No passage could be compared.
Source cited by the article: github.com/prototux/AARE/issues/44
Couldn’t checkCausal conclusion
On Android 17, the ZLink 3 aftermarket unit needs the local network permission for AARE to work.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “On Android 17 it needs the local network permission (#22”
The source says No passage could be compared.
Source cited by the article: github.com/prototux/AARE/pull/22
Couldn’t checkCausal conclusion
Google's Desktop Head Unit and head units built on Google's receiver library accept only phone certificates issued by Google's "Google Automotive Link" CA; against Google's DHU, AARE's TLS handshake completes and then authentication is refused with status -3.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “AARE was tested against Google's DHU: the TLS handshake completes, then the head unit refuses authentication (status -3”
The source says No passage could be compared.
Source cited by the article: github.com/prototux/AARE/blob/main/docs/certificates.md
No source givenVersion
Apps built with car-app library 1.8.0-beta01 or older accept a host holding android.car.permission.TEMPLATE_RENDERER, so CoMaps (1.7.0), Organic Maps (1.8.0-alpha02) and Lapin (1.7.0) work with AARE.
The article gives no link or citation for it.
The article says “apps built with car-app library 1.8.0-beta01 or older also accept a host holding android.car.permission.TEMPLATE_RENDERER”
The source says No source to compare with.
Couldn’t checkVersion
AARE's protobuf definitions come from aasdk.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “AAP protobuf definitions, from aasdk”
The source says No passage could be compared.
Source cited by the article: github.com/opencardev/aasdk
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 5 pts, not on front page
Recorded for context only, checked 8 Nov 2026, 05:46 UTC. It played no part in the ranking.