On Mon, Jan 16, 2012 at 07:45:52AM -0800, sblantipodi wrote: > No code is needed, every code that draw something on a canvas is > slowed down.
Repeating my previous post...it does NOT do this on my Acer Iconia A500 tablet. This makes your claim that it's a bug in Android overall a bit dubious, to say the least. Have you considered that it may be (and from everything I've read and seen, most likely IS) a device issue, not the OS itself? My A500, running 3.2.1, is extremely fast with all graphics. Much, MUCH faster than either of my Froyo devices. Get over it. This almost certainly is NOT a Google issue. This IS very likely a DEVICE issue (or maybe a code issue). > Wallpaper that runs fine on Galaxy S with gingerbread runs choppy on > Galaxy Nexus (double the horse power). Invalid test. You didn't use the same device type. To be a valid test, you need to run the test using two of the same device, side by side, one running Gingerbread and one running Honeycomb. But even that won't prove anything by itself, until repeat this with a good number of other devices, and get consistent results across ALL of them for the exact same controlled test. In other words, you need to eliminate all of the variables except for one: the OS. NOT the vendor's implementation of the OS in firmware, but the OS itself. That's why you MUST test over multiple devices. How do you know that the firmware for the Galaxy S isn't a better overall design than that of the Galaxy Nexus? Could it be that Galaxy rushed out the Nexus, just like they (and many other vendors did) did with their tablet? Did you know that Motorola rushed out the Xoom with USB ports that didn't work, promising that a later firmware release would fix that? Did you knwo that Galaxy rushed the Galaxy Tab 10.1 out without ANY USB ports? I don't know HOW they plan to fix that...firmware obviously won't do it. Yes, there was a massive rush by the hardware vendors to get the latest/greatest tablets out. What makes you think that there wasn't just such a rush by those same vendors to get Honeycomb and now ICS out? If the firmware's implementation of the graphics functions sucks, so will the graphics. Even without a degree in the electronics side of it (and experience with it overall since about 6th grade), I STILL could have told you that much.... I'm not trying to be a big google supporter. Sorry, but I'm just not that. But in this case, you are pointing the finger in a direction for which you have exactly ZERO conclusive test results. And with that, the mash is almost done, and it's time for me to get back outside, crank up the brew kettle, and make hot liquor (water) for sparging/lautering. (Brewing my Black Cat ESB, Mk II today). Later, --jim -- THE SCORE: ME: 2 CANCER: 0 73 DE N5IAL (/4) MiSTie #49997 < Running FreeBSD 7.0 > [email protected] ICBM/Hurricane: 30.44406N 86.59909W Do not look into waveguide with remaining eye. Android Apps Listing at http://www.jstrack.org/barcodes.html -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
