Geek Answers Handbook

What APIs are supported when hardware acceleration is enabled in Honeycomb?

Honeycomb docs are vague:

When a hardware accelerator, most of the operations in Canvas, Paint, Xfermode, ColorFilter, Shader, and the camera are accelerated.

Is there a final list of exact APIs that (and are not supported) are supported when enabling hardware acceleration? Some methods are quickly executed with exceptions, while other functions are simply rendered differently when acceleration is turned on.

For example, Canvas.clipPath (...) completes quickly with an exception. Although the clipPath API does not mention this, it is fairly easy to determine when testing on real hardware.

Other functions are displayed improperly with no exceptions, which leads to complex and time-consuming porting efforts. For example, I have a screen that uses ComposeShader, consisting of RadialGradient and LinearGradient, using PorterDuff.Mode.SRC_IN. It looks beautiful without acceleration, but completely wrong when acceleration is turned on.

+2
source share
1 answer

I am working to publish a complete list. Unsupported Features:

  • clipPath
  • clipRegion
  • clipRect with XOR or Difference op
  • drawPicture
  • drawPoints
  • drawPosText
  • drawTextOnPath
  • drawTextPos
  • drawVertices
  • setMaskFilter
  • setRasterizer

: , , Android 3.0.

, , . , . , , , .

+4

More articles:


All Articles