Fixed
Status Update
Comments
sa...@google.com <sa...@google.com>
rk...@google.com <rk...@google.com>
si...@google.com <si...@google.com> #2
These changes would be really nice! Being able to change the text colour is really important as it now doesn't match the rest of our app either.
Stack overflow posting -http://stackoverflow.com/questions/32533069/how-to-change-a-title-color-in-chrome-custom-tabs
Stack overflow posting -
si...@google.com <si...@google.com> #3
Changing text color and the overflow icon color is important to us too! Awesome work on the feature though.
si...@google.com <si...@google.com> #4
The ability of customize the status bar color is very important!
co...@accenture.com <co...@accenture.com> #5
It is in the essence of a "custom" UI component to have a custom color. Please add this feature!
si...@google.com <si...@google.com> #6
I have noted that the status bar automatically generated from the toolbar color is a bit darker than needed. The status bar color of the chrome activity is different to the one of the rest of my app. It doesn't strictly follow Material guidelines.
si...@google.com <si...@google.com> #7
The same issue I met. And is there a way to customize the title? using my own title rather than the url's. Thanks
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)