hardware-acceleration

So there's a known bug with WebView hardware acceleration in Android, see here for example: https://code.google.com/p/android/issues/detail?id=17352 Disabling hardware acceleration is not an option for me. I've read these great references: Android webview slow https://plus.google.com/+PaulIrish/posts/ccP98BTMd5Z http://riamobilesolutions.com/android-webview-scrolling-performance/ My question is, given HWA is turned on, does anyone know any CSS/HTML workarounds to prevent the rendering artefacts that can occur? I'm only seeing them when I give focus to a form field, it seems to cause vsync

The Honeycomb docs are vague: When the hardware-accelerated renderer is enabled, most operations in Canvas, Paint, Xfermode, ColorFilter, Shader, and Camera are accelerated. Is there a definitive list of the exact APIs that are (and are not) supported when hardware acceleration is enabled? Some methods fail fast with exceptions, while other features simply render differently when acceleration is enabled. For example, Canvas.clipPath(...) fails fast with an exception. Though the clipPath API makes no mention of this, it is easy enough to determine when testing on real hardware. Other features

I am trying to create a zoomable container and I am targeting API 14+ In my onScale (i am using the ScaleGestureDetector to detect pinch-zoom) I am doing something like this: public boolean onScale (ScaleGestureDetector detector) { float scaleFactor = detector.getScaleFactor(); setScaleX(getScaleX() * scaleFactor); setScaleY(getScaleY() * scaleFactor); return true; }; It works but the zoom is not smooth. In fact it noticeably flickers. I also tried it with hardware layer thinking that the scaling would happen on the GPU once the texture was uploaded and thus would be super fast. But it made no

I am attempting to build a Phonegap app that will allow the user to change the size of a two column layout by moving the middle divider. I was able to get this working, but there is a huge UX problem: it's laggy. It's not terrible, but on the latest iPad it's even noticeable, which has me worrying. Here's my JS that does the resizing: $("div").on("touchmove", "#columnResizeIcon", function(e) { e.preventDefault(); var left = e.originalEvent.touches[0].pageX; var right = $("#columnContainer").width() - left; $("#leftColumn").css({ "width":left - 1 + "px", "right":"auto", }); $("#rightColumn")

My application uses a canvas that I scale so that I can specify path points in meters instead of pixels. When I scale the canvas, then draw a line using path.lineTo() , with hardware acceleration on, the line is blurry and offset. This does not happen with hardware acceleration off or with canvas.drawLine() . Here is the code to reproduce the problem: package com.example.canvasproblem; import android.app.Activity; import android.content.Context; import android.graphics.Canvas; import android.graphics.Paint; import android.graphics.Path; import android.os.Bundle; import android.view.View;

I have the next issue. After updated HAXM up to 7.2.0 android emulator in android studio with version API 28 dont start up. I cant run the emulator. I am using laptop on Intel processor, i7. Virtualization is on. Before updating it worked. After updating, I can run emulator just if Turned On Software acceleration. If Hardware - impossible to run. If use x86_64 instead x86 I get black screen on emulator and errors in logcat: 06-18 08:13:42.256 1632-1632/? E/SurfaceFlinger: Error while linking shaders: 06-18 08:13:42.529 1632-1632/? E/SurfaceFlinger: Error while compiling shader: attribute vec4

I am developing an app for android using Xamarin. I am using Visual Studio 2017 and the Android SDK emulator that came with the Xamarin package from the visual studio installer. The emulator is very slow. I followed the instructions in this article to enable acceleration with Hyper-V: https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration The article does not say anything about having to set up a VM or configure the emulator itself to use Hyper-V, only how to enable Hyper-V... The emulator is still slow. How can I verify that the

Is there a way to find out if the decoder that received using MediaCodec.createDecoderByType(type) is a hardware decoder or a software decoder? There is no real formal flag for indicating whether a codec is a hardware or software codec. In practice, you can do this, though: MediaCodec codec = MediaCodec.createDecoderByType(type); if (codec.getName().startsWith("OMX.google.")) { // Is a software codec } (The MediaCodec.getName() method is available since API level 18. For lower API levels, you instead need to iterate over the entries in MediaCodecList and manually pick the right codec that fits

I've written CSS that uses -webkit-transform, -webkit-perspective and several similar. My design looks the bees knees on machines where hardware acceleration is available but is practically unusable when not. How can I check hardware acceleration availability and provide fallback CSS? Side note: Run chrome://gpu-internals/ to manually check for availability. Sadly, the answer seems to be 'you can't (yet)'. The Modernizr project lists HW acceleration amongst its 'undetectables': https://github.com/Modernizr/Modernizr/wiki/Undetectables . Part of the problem seems to be that HW acceleration is