For in‑vehicle exporters, it's been felt – in 2026, Google is making frequent changes to the Android Auto certification landscape. From the complete termination of Certification 1.0 and mandatory switch to the 2.0 process at the start of the year, to now the tightening PDK version window and video‑codec licensing rule changes – these cumulative changes have significant impact on ongoing or planned AA projects.
Currently, the vast majority of in‑vehicle projects still use PDK 4.5. Google's official timeline is clear: the end‑of‑use date for PDK 4.5 is 17 January 2027. After this date, all new AA applications must use PDK 5.0 or later.
What does this mean? If you still have projects stuck in the planning phase without starting certification – the window for PDK 4.5 is actually quite limited. Entering 2027 and trying to use 4.5 – the system will simply not accept it.
2. H.264 to H.265 – The Cost Chasm Behind Protocol Change
More challenging than version iteration is the codec change. PDK 4.5 can still use H.264 – but upgrading to PDK 5.0 requires H.265.
The cost impact of this change is far beyond what many manufacturers expect. H.265 involves patent licensing fees – one client found that obtaining full H.265 authorisation from scratch approached 10 million RMB.
That is not a small figure. For in‑vehicle equipment manufacturers with modest annual volumes, this licensing fee alone could wipe out the project's entire profit margin. Moreover, H.265's licensing model differs from H.264 – it is not a one‑time buyout – it involves per‑unit fees and annual reporting – ongoing compliance costs.
3. 3PL Certification System Tightens Simultaneously
Beyond PDK version and codec changes, the certification execution side is also tightening. From January 2026, Google requires all new vehicle projects to complete Android Auto certification through third‑party authorised labs (3PL). The old Certification 1.0 system is officially retired.
The old route where manufacturers ran internal self‑tests and submitted reports – that is no longer possible. Now you must follow the complete 2.0 certification process – from test execution to report issuance, all controlled by 3PL labs – with Google final verification. Both certification timelines and costs are increasing.
4. Recommendations for Manufacturers Currently Pursuing AA Projects
First, confirm the PDK version used by your current project now. If you are still on 4.5, assess whether the project can complete certification and obtain the certificate before 17 January 2027. If timeline is tight, you may need to reprioritise scheduling.
Second, evaluate H.265 licensing costs early. If your project will inevitably move to PDK 5.0, H.265 licensing fees must be built into the project budget. We recommend contacting the patent pool administrators directly for formal quotes – do not rely on second‑hand information.
Third, if you can stay on 4.5, do not drag it into 5.0. For most in‑vehicle infotainment manufacturers, PDK 4.5 functionality is sufficient. If H.265 licensing costs are truly unsustainable, we suggest completing AA certification under PDK 4.5 as soon as possible – avoiding forced upgrades.
Fourth, choose an experienced 3PL lab for pre‑testing. With the certification system now tightened, labs have significantly higher sample quality requirements. Before formal submission, run a full pre‑test with an authorised 3PL – identify obvious issues and filter them out – saving significant retesting time and costs.
Overall: 2026 is a year of comprehensive restructuring for the Android Auto certification system. PDK version iteration, codec changes, and mandatory 3PL certification – these three overlapping changes demand higher compliance capability and cost control from in‑vehicle manufacturers. Early planning and early assessment are far more proactive than reactive responses.
For Android Auto certification enquiries, contact BlueAsia at 13534225140 (King) or king.guo@cblueasia.com.
Related News
