Fisker is using Android Automotive OS but NOT using Google Automotive Services. (In this, they are following in the footsteps of RIvian, BMW, and Lucid and breaking ranks with Geely, Ford, GM, Honda. There is a good article here that explains this. Sharing insights elevates their impact
TomTom is essentially providing the services that GAS is providing to GM, Ford, et. al. as outlined in these papers.
The TomTom approach outlined here looks solid to me, but I am very much a software non-expert. (I am anxious about Android Automotive, but hey what can you do, auto companies cannot write software. They suck at it.). I like the Cameras+ Maps approach to ADAS and think it is the best way to get the best ADAS for qualified roads. Most important from my perspective is that TomTom seems to have a very clear strategy for charger routing. The key question is: where does it get the data. If it have a very comprehensive real-time data suite about available chargers and speed, the software can do its job. If it is stuck with the half-a$$ed chargepoint data set it will be poj.
The key to the entire suite will be seeing how frequently these are updated and features are modified and added based on customer learning. I suspect that will be significantly in the hands of Fisker, but the ability to swiftly add and adapt features while maintaining the latest version of AAOS will tell whether this is going to be a viable solution or typical auto oem garbage. Rivian seems to be doing pretty well with rapid improvement on its AAOS system so I am hopeful. As usual, GM totally sucks and is introducing new vehicles with three-generation old AAOS out of the gate. We will all see soon if Ocean is running on AAOS 13 (latest) or some half abandoned v 10 like the new Tahoe.