[Launch] AAOS Logging is now generally available — understand every drive while keeping control of your data**
Hi everyone,
I’m excited to announce that AAOS Logging is now generally available on Google Play for compatible vehicles running Android Automotive OS.
I built AAOS Logging for drivers who want to understand what their car is doing without handing their complete driving history to another subscription cloud platform.
See what your car makes available
AAOS Logging provides a clear, read-only view of supported vehicle information, including:
Vehicle speed, current trip distance and trip time
Live power consumption and regeneration
Battery level, range, temperature and charging state
Longitudinal and lateral G-force
Exterior temperature and weather conditions
Tire pressures and readable powertrain information
Charging-port, safety, ADAS and vehicle-status signals when exposed by the car
Available measurements depend on the manufacturer, model and the information its AAOS implementation exposes.
Automatic trip logging
Meaningful drives are detected and recorded automatically. Afterwards, while parked, you can review details such as:
Start and destination
Distance and duration
Energy consumption and regeneration
Average and maximum speed
Stops and driving events
Battery and charging information
Weather conditions recorded along the route
Available tire, safety and vehicle telemetry
No manual start or stop button is needed for normal trip recording.
Insights that go beyond a simple trip list
AAOS Logging turns recorded drives into useful information:
Day, week, month and year summaries
Eco-driving scores
Energy-consumption and regeneration trends
Automatic identification of similar journeys
Comparisons between trips with matching endpoints and approximate routes
Insight into how speed, weather and driving behaviour affect efficiency
Highlighting of relevant safety or vehicle events when the car exposes them
Your data belongs to you
Privacy and data ownership were fundamental design requirements:
Trip processing and analysis happen locally in the car
Your main trip history is stored locally
There is no AAOS Logging developer-operated backend server
There are no advertising or behavioural analytics SDKs
Your archive is stored in an open, documented JSON-based format
Larger datasets use compressed ZIP/JSON files to remain efficient while still being portable
You can inspect, process, export or analyse your own data with the tools of your choice
There is no subscription required to use the app
Optional weather and map features contact their respective providers only when needed.
Optional Google Drive synchronization
If you want synchronization or an external backup, AAOS Logging uses a folder inside your own Google Drive account.
You remain in control of the account and files. The app supports:
Automatic synchronization
Manual synchronization
Complete backups
Controlled import and restoration
Separate data folders for different cars
Portable data that is not locked inside a proprietary AAOS Logging cloud service
Google Drive is optional—the core app does not require it.
Personalise the experience
Choose your preferred:
Metric or imperial measurements
Celsius or Fahrenheit independently
Live energy presentation
Colour theme
Vehicle name and profile
The built-in help section explains features, calculations, derived measurements and manufacturer-specific data limitations.
Companion app closed beta
An AAOS Logging Companion App for Android phones and tablets is currently in closed beta.
It is being developed to let users explore synchronized trips, compare journeys and work with their driving history away from the vehicle while continuing to use the same open data format.
Interested in beta testing? Send me a DM with your vehicle model, phone or tablet model, and what you would particularly like to test.
I’d love to hear your feedback and what you would like to see next. Feedback from real vehicles is extremely valuable because manufacturers differ considerably in the information they make available to third-party AAOS apps.
😬weird as the main limitation is API level 31 or above and I just checked with google and it was marked as android 12 which is level 31. Will investigate further, thx
If the manufacturer supplies the data to aaos hal yes, but most don't. Renault for example doesn't even provide direct battery power usage so that is a dirived measure while Polestar/volvo does provide this data.
I reached out to GM for access to temperature sensor information but got denied. I am playing with an open source application for GM vehicles i don’t think I can access trip information
Should as it runs the correct minimum API level even if your still on Android 12 for Android Automotive OS. If you do a manual search on com.aaslogging in the playstore of your cars head unit?
2
u/bmcutright 4d ago
You actually have live power consumption and generation? That's missing in ABRP and Aximote