IssueTracker

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

Changing text color and the overflow icon color is important to us too! Awesome work on the feature though.

The ability of customize the status bar color is very important!

It is in the essence of a "custom" UI component to have a custom color. Please add this feature!

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.

The same issue I met. And is there a way to customize the title? using my own title rather than the url's. Thanks

Would very appreciate this enhancement!

I'd love to have the possibility to change title text color, I'll be a very important graphic consistency inside my app

Voting +1 for this feature.

It has been more than a year. Please add this!

[Comment deleted]

It will certainly be a nice feature and have a nice title for the chrome tab. Please fix this.

Customize the status bar color is a real need. Voting +1

Yes, it's needed definitely. Please!! Voting+1.

Any date to the release of this feature? Working with VectorDrawables is awesome and let us have an IconKit but this little impediment make it not perfect

Voting +1 for this feature.

Voting +1 for this feature.

voting +1 for this feature

Voting +1 for this feature.

Voting +1 for this feature.

+1 from me. I really need this feature.

+1 from me. I've to fallback my implementation to webview because of this graphic inconsistency.

Voting +1 for this feature.

Voting +1 for this feature.

Voting +1 for this feature.

Not being able to set a proper dark or light statusbar/toolbar icon color is breaking our app color design very bad.

+1 for this feature.

Voting +1 for this feature.

Estoy de acuerdo con este comentario, es molesto cuando el diseñador te levanta la mano porque no le convence el contraste de los colores y te es imposible responder con fundamento y suplir los criterios. Sería genial poder personalizar más esta sección.

This has been an issue for 6 years now. Why isn't Google dealing with it? If I'm to use  Custom Tabs, I need to be able to change the toolbar text and color at will.

Hello are,

I am getting the following issue when try to execute the android app for the first time after setting up in my system

[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - Emulator] Failed to create Context 0x3005
[2013-03-03 00:43:18 - Emulator] emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - Emulator] could not get wglGetExtensionsStringARB
[2013-03-03 00:43:18 - HelloAndroid] New emulator found: emulator-5554
[2013-03-03 00:43:18 - HelloAndroid] Waiting for HOME ('android.process.acore') to be launched...

Please help me

[Comment deleted]

similar problem, just resolved ,grahics driver works for me! thanks edobar

I got the same problem, but Zachary's solution of copying the dlls to the tools directory didn't work for me. Maybe there are other errors.

I updated my graphics driver to the latest one and that fixed the problem.

Experienced issue on latest SDK (22.0.1) on Windows 8 64-bit. Fixed it by adding ...\sdk\tools\lib to the SYSTEM (!) path. It does not work if you add the lib folder to the user path.

Working on a fresh Debian Wheezy, this solved the problem for me:

$ export LD_LIBRARY_PATH="/home/user/adt/sdk/tools/lib"

and then run the emulator in the same shell.

For this to work you also need to have the package "libgl1-mesa-dev" installed. If you don't have it, it will fail to find "libGL.so".

[Comment deleted]

This is still an issue, a year later I guess, I ran into the same problem. I had downloaded the latest Android bundle w/ Eclipse etc, installed the SDKs, launched Eclipse, from within Eclipse launched the AVD Manager, created a "Galaxy Nexus" image, and I got the errors in the little log window. This DID NOT happen when launching AVD Manager from the Start menu, only when launching from Eclipse. Per Zachary's solution, copying those four DLLs from android/sdk/tools/lib to android/sdk/tools caused the error to disappear.
Using Windows 7 x64. Java 6 and 7 are both installed; JAVA_HOME var points to 6. Android Studio was also installed. Xamarin had also been installed; it clobbered some of the AVD/SDK bits but I had reinstalled them from the SDK manager.

I see the problem with why the DLL is not found on Windows, and why using the SYSTEM path can work.

In Process Monitor, I noticed that the PATH environment variable was correct when emulator.exe was launched, but when it launched emulator-x86.exe, the PATH was truncated at 2042 bytes.  2042 for the path + 5 for "PATH=" + 1 null terminator = a 2048 byte buffer.

In qemu\android\main-emulator.c, prependSharedLibraryPath, the PATH environment is being set into a fixed 2K buffer.  If your tools/lib is towards the end of the path it will be lost when it's truncated.   The logic is also backwards for _WIN32 - it's appending instead of prepending.  It also looks like there's an unnecessary strdup() that will leak.

The SYSTEM path is probably working for some folks because it's shorter than the user/process path, and the tools directory falls within the first 2K.

Until this gets fixed, a workaround is to put the tools\lib folder first (or early) in your path, or shorten the path to ensure it doesn't become longer than 2K.   I do this in a command file that launches Eclipse, and the DLLS are found correctly.

After copying files to /tool dir, i am not getting error but when i create new android project in visual studio its shown Failed

? visual studio?

Thank you frank for your insight. That was indeed the problem.

Well, I found the issue that made the command line workaround to stop working. After executing any command I always receive:

ERROR: Could not load OpenGLES emulation library: Could not load DLL!
WARNING: Could not initialize OpenglES emulation, using software render.


I tried to fix this by copying all the lib*.* files from <sdk-installation-folder>/tools/lib/ to one folder up <sdk-installation-folder>/tools/ or adding the <sdk-installation-folder>/tools/lib/ path to my "Path" System Variable, as many website suggested, resulting in the emulator crashing every time.

Reversing those changes made the command line workaround to work again. Now I guess this is where all my issue comes from, because I have never received that error or warning when using the normal ADT emulator launcher like this: http://delphi.org/wp-content/uploads/2013/11/OpenGLES-error.png

As I said here: http://stackoverflow.com/questions/13997771/android-emulator-segmentation-fault

Renaming all the lib*.* files from <sdk-installation-folder>/tools/lib/ to lib*.*.xxx made the emulator to start. So the crashing it's OpenGLES fault.

1.Copy  the following file to the tools dir:

libEGL_translator.dll
libGLES_CM_translator.dll
libGLES_V2_translator.dll
libOpenglRender.dll

2.Update graphics driver
This is how to Update your graphics drive :) :) :)
https://www.youtube.com/watch?v=7i8fS3Owu4E

It work for me

Cheers from  
Tin Tin :P :P :P

I had the same problem on my Windows 7 (64-bit) machine running Android Studio and the final version of AVD. The reason: I found that the libOpenglRender.dll and other related Dlls could not be located. I added <android-sdk>\tools\lib to the PATH variable and could run the emulator without error messages.

Back on!!!