You can use a settings.ini configuration file to configure the execution speed and system debugging logs for the Generic Graphics Accelerator.
The settings.ini configuration file is
in the directory
However, the settings.ini file in the current
directory is used to configure the Generic Graphics
NoteYou must copy settings.ini to your current directory in which you run the command to start the Generic Graphics Accelerator.
Execution speed settings
The settings.ini file provides the following parameters to control the execution speed of the Generic Graphics Accelerator.
- Instructs the Generic Graphics Accelerator to execute all calls on both the host and target.
- When you specify conformant, the execution speed of the Generic Graphics Accelerator is slow because command batching is not allowed.
- Instructs the Generic Graphics
Accelerator to batch commands, skip certain calls from the
target, and render directly to the frame buffer.
When you specify fast, the execution speed of the Generic Graphics Accelerator is faster. However, OpenGL ES APIs might be issued to the OpenGL ES Emulator in an order different than the order the OpenGL ES APIs are issued by the application on the Android target. As a result, the OpenGL ES API mapping between the host and the target is vague.
Do not specify fast if you want to check the relationship between the following OpenGL ES APIs:
- The OpenGL ES APIs called on the host graphic driver.
- The OpenGL ES APIs called by the application on the Android target.
By default, conformant is set.
The settings.ini file provides the LogLevel parameter to specify the verbosity level of logs. You can use the logs to trace the OpenGL ES API invocation sequence and debug the Generic Graphics Accelerator.
The logs can be found in the following locations:
- The logs about the interaction between the Reconciler and the OpenGL ES Emulator are printed in the current console.
- The following logs can be viewed by the
logcatcommand in Android:
- Logs about the interaction between the Shim Layer and applications.
- Logs about the interaction between the Shim Layer and the Reconciler.
For the LogLevel parameter, you can specify one of the following verbosity levels, by using macros. The verbosity order goes from the least verbose level, 0 to the most verbose level, 6567.
# LOG_LEVEL_OFF 0
- The Generic Graphics Accelerator issues no messages.
# LOG_LEVEL_FATAL 1
- The Generic Graphics Accelerator issues fatal messages.
# LOG_LEVEL_ERROR 2
- The Generic Graphics Accelerator issues error messages.
# LOG_LEVEL_WARN 3
- The Generic Graphics Accelerator issues warning messages.
# LOG_LEVEL_INFO 6565
- The Generic Graphics Accelerator issues information about important stages of executing APIs.
# LOG_LEVEL_DEBUG 6566
- The Generic Graphics Accelerator issues the names and parameters of each API that is called.
# LOG_LEVEL_TRACE 6567
- The Generic Graphics Accelerator issues detailed information for checking bugs in the Generic Graphics Accelerator.
- Do not specify this value unless ARM requests you to provide more detailed information for debugging purpose.
The verbosity level that you choose affects the system performance. The higher the verbosity level, the slower the system runs.
The default setting is LogLevel 2.
If you find any abnormal situation with the Generic Graphics Accelerator, send these logs to email@example.com for diagnostic purposes.