Fixed
Status Update
Comments
sa...@google.com <sa...@google.com>
rk...@google.com <rk...@google.com>
si...@google.com <si...@google.com> #2
Information redacted by Android Beta Feedback.
si...@google.com <si...@google.com> #3
Thank you for reporting this issue. We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
si...@google.com <si...@google.com> #4
Workaround/fix for me is to reinstall the Home app from the Play Store.
Pixel 6 Pro (raven), Baklava (BP22.250103.008)
Home Version 3.28.1.7
com.google.android.apps.chromecast.app
Hope this helps some users get control back over their smart home tech while a fix is prepared.
Pixel 6 Pro (raven), Baklava (BP22.250103.008)
Home Version 3.28.1.7
Hope this helps some users get control back over their smart home tech while a fix is prepared.
co...@accenture.com <co...@accenture.com> #5
Workaround for me is to ask Gemini "List my devices"
Description
The Car Service API allows programmatic access to the AAOS VHAL. The problem is that thehttps://android.googlesource.com/platform/external/qemu/+/emu-master-dev/android/android-grpc/services/incubating/car/proto/car_service.proto has the type for CarEvent as string whereas its expected as a byte string by AAOS.
The fix is to change the type from string to bytes. I've rebuilt the emulator on Linux and the fix is working fine with both python and node.js gRPC clients.
The following example python script can be used for reproducing the problem using a Linux emulator running an AAOS image (for example system-images;android-32;android-automotive-playstore;x86_64)