aboutsummaryrefslogtreecommitdiff
path: root/en/devices/graphics/arch-sh.html
diff options
context:
space:
mode:
Diffstat (limited to 'en/devices/graphics/arch-sh.html')
-rw-r--r--en/devices/graphics/arch-sh.html4
1 files changed, 1 insertions, 3 deletions
diff --git a/en/devices/graphics/arch-sh.html b/en/devices/graphics/arch-sh.html
index c3c74dfe..3b597abb 100644
--- a/en/devices/graphics/arch-sh.html
+++ b/en/devices/graphics/arch-sh.html
@@ -60,9 +60,7 @@ hardware-accelerate the Canvas API. As you can see from the charts on the
Acceleration</a>
page, this was a bit of a bumpy ride. Note in particular that while the Canvas
provided to a View's <code>onDraw()</code> method may be hardware-accelerated, the Canvas
-obtained when an app locks a Surface directly with <code>lockCanvas()</code> never is.
-As of API 23, a hardware-accelerated Canvas can be obtained from a Surface using
-<code>lockHardwareCanvas()</code> instead.</p>
+obtained when an app locks a Surface directly with <code>lockCanvas()</code> never is.</p>
<p>When you lock a Surface for Canvas access, the "CPU renderer" connects to the
producer side of the BufferQueue and does not disconnect until the Surface is