[android-developers] GPU driver issue

hello, i have that problem with the "GPU Driver issues" in past when i open the emulator it work well but after month or two i installed the adnroidStudio again

[android-developers] GPU emulation missing in AVD

In Android emulator documentation under Using Hardware Accelaration it says 1. If you want to have graphics acceleration enabled by default for this AVD, in the *Hardware* section, click *New*, select *GPU emulation* and set the value to *Yes*. *Note:* You can also enable

[android-developers] GPU Acceleration - still not worth using on 4.1.1?

I'm seeing strange issues with GPU acceleration in my app. First, on 4.0.3 / 4.0.4, a WebView with a dark background color flashes white whenever I reload its data. It does this over the whole screen, which looks really nasty in a multi-panel (fragment) UI. This is on an Asus TF101, Sonty Tablet

Re: [android-developers] GPU Acceleration - still not worth using on 4.1.1?

- Am I just so special hitting one bug after another? In a way, yes :) - Is GPU acceleration, by and large, unexpectedly broken and randomly unusable, even in 4.1.1 on the Galaxy Nexus? Considering the fact that every app that ships with 4.1.1 (and now 4.1.2) runs with hardware acceleration

Re: [android-developers] GPU Acceleration - still not worth using on 4.1.1?

2012/10/16 Romain Guy romain...@android.com - Am I just so special hitting one bug after another? In a way, yes :) Thank you :) - Is GPU acceleration, by and large, unexpectedly broken and randomly unusable, even in 4.1.1 on the Galaxy Nexus? Considering the fact that every app

Re: [android-developers] GPU Acceleration - still not worth using on 4.1.1?

Maybe it gets better in 4.2 or 7.1, but with so many new features being added all the time, I'm not getting my hopes up. Canvas is not getting new APIs/features in the foreseeable future. The focus is on fixing bugs and implementing missing features (non rectangular clip for instance.) --

Re: [android-developers] GPU Acceleration - still not worth using on 4.1.1?

Will the correct drawing of line caps (currently missing?) be implemented in the future? There also seems to be bugs with canvas.drawLines() and gaps appearing between lines at the joins (where an individual for loop to canvas.drawLine() works fine), possibly some line join code is not

Re: [android-developers] GPU Acceleration - still not worth using on 4.1.1?

Will the correct drawing of line caps (currently missing?) be implemented in the future? Yes, but no ETA. There also seems to be bugs with canvas.drawLines() and gaps appearing between lines at the joins (where an individual for loop to canvas.drawLine() works fine), possibly some line join

Re: [android-developers] GPU Acceleration - still not worth using on 4.1.1?

Awesome! As I've said before, this hw acceleration of canvas is a huge win and I don't think you guys have gotten enough credit in the world at large for this undertaking. You've mentioned to me that drawing circles and ellipses is still done in software, due to differences in GPUs. The HW

Re: [android-developers] GPU Acceleration - still not worth using on 4.1.1?

You've mentioned to me that drawing circles and ellipses is still done in software, due to differences in GPUs. The HW accelerated workaround, that I know of is obviously drawLines() using approximated geometry - for outlines. This works, but, is there currently a hardware accelerated way to

[android-developers] GPU emulation and hardware acceleration for self-build android + android kernel (goldfish) builds

Hi, I've been trying to get GPU emulation and hardware acceleration working for my self compiled android intel builds on Mac OS X but it just won't work. As soon as I turn GPU emulation on I see graphic artifacts and the visual is completely unusable. For hardware acceleration I don't see HAX

[android-developers] GPU usage

as for Issue 6914, we can see that the UI lag is a very important problem, and as I know most chipsets provide the GPU, such MTK 6573,I wonder whether has a way for us to use the GPU for our UI? especially after ICS. -- You received this message because you are subscribed to the Google Groups

Re: [android-developers] GPU usage

Hardware acceleration for widget-based UIs is on by default with Ice Cream Sandwich. You can opt into it for Honeycomb via the android:hardwareAcceleration attribute in your manifest. On Wed, Nov 16, 2011 at 6:59 AM, Bacon021 wei.pg...@gmail.com wrote: as for Issue 6914, we can see that the UI

Re: [android-developers] GPU

On Sat, Nov 20, 2010 at 1:40 AM, Nathaniel Warner warner.nathan...@gmail.com wrote: How do I force my application to use the current devices GPU if one is available? By using anything visual ... ? Platform will utilise GPU without your interference. Daniel -- You received this message

[android-developers] GPU

How do I force my application to use the current devices GPU if one is available? -- You received this message because you are subscribed to the Google Groups Android Developers group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send