hardware-acceleration

Which APIs are supported when hardware acceleration is enabled on Honeycomb?

爷,独闯天下 提交于 2019-12-04 15:48:23
问题 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

CSS hardware accelerated width?

我是研究僧i 提交于 2019-12-04 11:35:09
问题 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")

Why does calling setScaleX during pinch zoom gesture cause flicker?

烈酒焚心 提交于 2019-12-04 11:32:53
问题 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

Is there a way to detect if Java FX is using hardware acceleration?

前提是你 提交于 2019-12-04 11:17:38
And related to that, is there a way to force Java FX to use hardware acceleration and bomb if it is unable to? Just found out: You can run with -Dprism.verbose=true which will print what graphics pipeline it uses. "sw" or "j2d" for software and "d3d" or "es2" for hardware accelerated. You can also try this hack @SuppressWarnings("restriction") static String getCurrentGraphicsPipeline() { return com.sun.prism.GraphicsPipeline.getPipeline().getClass().getName(); } If you get back "com.sun.prism.sw.SWPipeline" then you're using software acceleration. All other values will mean that probably some

Are CSS3 properties like animate too CPU intensive?

爱⌒轻易说出口 提交于 2019-12-04 05:27:40
will this repetitive animation code slow down my system?: @-webkit-keyframes animate {-webkit-animation-iteration-count:infinite;...} Are all CSS3 properties CPU intensive ? Thanks. Avoid using box-shadow & text-shadow. Don't try and animate the whole page, or the body element and use translate3d, scale3d, rotate3d as they are hardware accelerated on computers and mobile devices. As stated above, avoid the OVERUSE of animating properties. I however doubt that one or even four infinitely animated elements will slow down your page. Improving the Performance of your HTML5 App UPDATE Beware!

How to verify that Android SDK emulator is running in Hyper-V

我怕爱的太早我们不能终老 提交于 2019-12-04 04:24:35
问题 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

How to properly use a hardware accelerated Media Foundation Source Reader to decode a video?

萝らか妹 提交于 2019-12-03 15:17:31
I'm in the process of writing a hardware accelerated h264 decoder using Media Foundation's Source Reader, but have encountered a problem. I followed this tutorial and supported myself with Windows SDK Media Foundation samples. My app seems to work fine when hardware acceleration is turned off, but it doesn't provide the performance I need. When I turn the acceleration on by passing a IMFDXGIDeviceManager to IMFAttributes used to create the reader, things get complicated. If I create the ID3D11Device using a D3D_DRIVER_TYPE_NULL driver, the app works fine and the frames are processed faster

Blurry offset paths when canvas is scaled under hardware acceleration

拜拜、爱过 提交于 2019-12-03 15:04:31
问题 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

What graphic cards do Android emulator GPU emulation support?

安稳与你 提交于 2019-12-03 14:27:25
I have HD7690M XT (an overclocked version of 6770M) and Android emulator (sdk tool rev.20) for ICS failed to start hardware OpenGL ES emulation with the following error message: emulator: ERROR: Could not load OpenGLES emulation library: Could not load DLL! emulator: WARNING: Could not initialize OpenglES emulation, using software renderer. and with software renderer I got really bad color resolution (please see the attached screenshots). I suspect that this is due to the software renderer (no such problem in emulating earlier versions of Android). Have someone who can run hardware emulation

WebView inside ViewPager or ScrollView - weird rendering bug on Android 3.0+

早过忘川 提交于 2019-12-03 13:02:42
I have a ViewPager. Every page of the ViewPager is a ScrollView. The ScrollView contains a WebView and several other Views. On Android 2.3 and older everything works fine but on 3.0+ there's a weird rendering issue: When scrolling left / right in the ViewPager, there is also a very subtle rendering issue (which is present in Android 4.0 Gmail app too). This might be related to hardwareAcceleration. Try specifically turning it off. You can do this 1) in the application tag inside your manifest (which will disable hardware acceleration throughout the app) android:hardwareAccelerated="false" OR 2