home.social

#aaos — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #aaos, aggregated by home.social.

  1. We have the pleasure of continuing a trend that we've followed with previous #Android releases, by making publicly available an Android #Automotive OS emulator for the latest release of Android less than 24 hours after the source code became publicly available.

    There are a few changes to #AAOS 16, and we look forward to hearing folks opinions and experiences.

    Details on how to access the emulator can be found at github.com/snappautomotive/REA

  2. Hello #Android #Automotive OS 16.... Looks like the left panel has changed, and there's now an assistant button where the volume button was before, but, on the whole, #Android16 #AAOS from the #AOSP seems very familiar.

  3. Place your bets please; Will the #AAOS build for Pixel Tablets become a thing in the #AOSP, or will #Google consider the #Automotive #Android variant a proprietary thing, and not make a non-GAS buildable version of it available for the PT?

    Not making an #AOSP buildable #AAOS for the Pixel Tablet would, to me, be a signal of where Google is heading with its new "closed development, then throw it over the wall" AOSP model, and it'd be a sad direction to see them go in.

    android-developers.googleblog.

  4. Great to see the #AOSP get a bunch of externally created merges to the yukawa device tree, which is used for the #VIM3 builds for the @snappautomotive #AAOS dev kit.

    android-review.googlesource.co

  5. Great to see the #AOSP get a bunch of externally created merges to the yukawa device tree, which is used for the #VIM3 builds for the @snappautomotive #AAOS dev kit.

    android-review.googlesource.co

  6. Great to see the #AOSP get a bunch of externally created merges to the yukawa device tree, which is used for the #VIM3 builds for the @snappautomotive #AAOS dev kit.

    android-review.googlesource.co

  7. Great to see the #AOSP get a bunch of externally created merges to the yukawa device tree, which is used for the #VIM3 builds for the @snappautomotive #AAOS dev kit.

    android-review.googlesource.co

  8. Great to see the #AOSP get a bunch of externally created merges to the yukawa device tree, which is used for the #VIM3 builds for the @snappautomotive #AAOS dev kit.

    android-review.googlesource.co

  9. Google posted the hashtag#Android15 source code to the Android Open Source Project last night (for the European timezone), and, as we normally do, we've started to create the hashtag#Android hashtag#Automotive OS emulators for the new release.

    We're currently putting them through our QA tests, but there seems to be no new large user-facing changes, as we expected. We're looking to make these available later today or tomorrow.

    #AAOS #Infotainment

  10. It’s great to see #google have started publicly sharing build instructions for #AAOS for the #PixelTablet.

    At @snappautomotive we’ve been using tablets for AAOS development for multiple years, and have delivered multiple projects that allowed customers to undertake automotive infotainment development on commodity devices, including, most recently, the Pixel Tablet.

    It’s a great to way to cut development time and costs, and now more folk can enjoy the benefits.

    source.android.com/docs/automo

  11. It was great to see #Google announce the early availability programme for #AAOS on the #PixelTablet last week at #io24.

    We've long believed in using Tablets to simplify #automotive development, especially in the area of #ivi and #AAOS, which is why we've been using Android tablets for development since 2021.

    We also have EA #AAOS builds for the #PixelTab up and running, and it's shaping up to be a great platform for #AndroidDev folk interested in automotive development.

  12. It was great to see #Google announce the early availability programme for #AAOS on the #PixelTablet last week at #io24.

    We've long believed in using Tablets to simplify #automotive development, especially in the area of #ivi and #AAOS, which is why we've been using Android tablets for development since 2021.

    We also have EA #AAOS builds for the #PixelTab up and running, and it's shaping up to be a great platform for #AndroidDev folk interested in automotive development.

  13. It was great to see #Google announce the early availability programme for #AAOS on the #PixelTablet last week at #io24.

    We've long believed in using Tablets to simplify #automotive development, especially in the area of #ivi and #AAOS, which is why we've been using Android tablets for development since 2021.

    We also have EA #AAOS builds for the #PixelTab up and running, and it's shaping up to be a great platform for #AndroidDev folk interested in automotive development.

  14. It was great to see #Google announce the early availability programme for #AAOS on the #PixelTablet last week at #io24.

    We've long believed in using Tablets to simplify #automotive development, especially in the area of #ivi and #AAOS, which is why we've been using Android tablets for development since 2021.

    We also have EA #AAOS builds for the #PixelTab up and running, and it's shaping up to be a great platform for #AndroidDev folk interested in automotive development.

  15. It was great to see #Google announce the early availability programme for #AAOS on the #PixelTablet last week at #io24.

    We've long believed in using Tablets to simplify #automotive development, especially in the area of #ivi and #AAOS, which is why we've been using Android tablets for development since 2021.

    We also have EA #AAOS builds for the #PixelTab up and running, and it's shaping up to be a great platform for #AndroidDev folk interested in automotive development.

  16. Come visit us at IAA MOBILITY in Hall A3 - Booth B208 and try SnappOS, our Android Automotive infotainment system!

    #android #androidautomotive #aaos #infotainment #hmi #uxdesign #iaa23 #iaamobility

  17. Explaining #Android12 #AAOS is a mess.

    Android 12 was launched with #Android API Level 31, and QPR1 stayed on API Level 31 (android.googlesource.com/platf). QPR3, however, is API Level 32 (android.googlesource.com/platf), and 32 includes a rewrite of the HVAC system (android.googlesource.com/platf). The recent android-security-12.* tags are also all API Level 31 (android.googlesource.com/platf).

    TLDR; A SoC/SoM vendor saying they ship "Android 12" still leaves a chunk of uncertainty about what folk will actually get :(.

  18. Today, less than 24 hours after Google publicly released #Android14, we're making available an #Android #Automotive OS 14 (#AAOS) emulator build.

    Instructions on how to download the #AOSP based AAOS 14 build can be found in our GitHub repository at github.com/snappautomotive/REA

  19. We're excited to announce that we're partnering with DRIMAES!

    We're combining our strengths to integrate SnappOS, our infotainment system, with DRIMAES' cutting-edge automotive-grade hardware. This partnership marks another significant step forward in our mission to simplify integrating premium automotive user experiences by offering a complete package of both software and hardware!

    We'll be showing a demo together at IAA MOBILITY, see you there!

    snappautomotive.io/news/snapp-

    #aaos #android

  20. One modification we've made to #Android #Automotive OS (#AAOS) is adopting #JetpackCompose for the #UI (including the System UI). This allowed us to follow the current #Google UI/UX best practices, and to create a theming engine that can be easily adopted by system, in-house, and third-party apps to provide a high level of UI customisation.

    If you'd like to know more about this work, and #SnappOS, here's a talk given by two of our team at #Droidcon Berlin last month.

    droidcon.com/2023/08/01/buildi

  21. It looks like Google are planning to update their #AAOS testing devices "in few months with new targets" with some new targets.

    This is great given the most recent supported device for an #AOSP #AAOS build is the Pixel 5.

    groups.google.com/g/android-bu

  22. Nothing to see here... nope... nothing to do with #tangor... nope..... no #PixelTable #AAOS build stuff.

    If you're picky, #tangor was based on the Pixel 6 CPU (gs101 - Whitechapel), whereas the PT folk are getting today is based on the Pixel 7 one (gs201 - Cloudripper) and is #tangorpro.