Flash in Android2.2 Froyo

Google has started updating Nexus One phones to Android Froyo and the update file is already public. I updated my phone using a pre-rooted version from Modaco which doesn’t require the stock recovery image.

Even if it’s not included in Android, the Flash runtime is one of the few applications that require Android 2.2. Right now, you can install from the Android Market the first beta release for Flash 10.1.

Whether you love it or hate it, installing Flash changes the way you look at a mobile phone. HTML5 may be the future, but a lot of websites use Flash for playing video, music, games and interactive content. Instead of getting messages that recommend you to install the Flash plug-in, you’ll see the actual content.

The trouble with Flash on a mobile phone is that most Flash content is designed for a computer and it’s difficult to use on a device with a small screen. Video players have small buttons and it’s challenging to click on one of them, some websites serve high-quality videos that aren’t appropriate for a slow Internet connection, clicking on a Flash object is a disrupting experience because you might open a new page, pause a video or display the Flash content in full-screen.

I’ve tried to open many sites that use Flash and the experience isn’t smooth. Animations are sometimes choppy, web pages load much slower, scrolling web pages that use Flash is slow and there’s a lot of lag when zooming a page with Flash content. In some cases, the browser is no longer responsive for a few seconds and you need to wait until you can switch to another page. Fortunately, Adobe managed to optimize the code and using Flash doesn’t drain your phone’s battery much faster.

The version you can install from the Android Market is not the final release, but don’t expect too many changes until next month. It’s nice to have options, so I recommend to install the Flash runtime and to change the browser settings so that plug-ins are loaded “on-demand”. This way, web pages will continue to load fast and you’ll only display Flash content when necessary.

Fix for Karmic Koala 64 bit Flash Plugin – patshead.com Blog

upgraded my laptop to the 64 bit Ubuntu Karmic Koala beta yesterday. For me, Flash was very broken…

The 32 bit Plugin

Ubuntu defaults to installing the 32 bit Adobe Flash plugin and runs it under nspluginwrapper. When I run the plugin this way it will not accept mouse clicks properly. This seems to be a known issue. The bug reports make it sound like disabling compiz fixes this… I don’t run compiz, I run the Sawfish window manager. I tested Metacity and it works just fine.

The 64 bit Plugin

Next I tried disabling the 32 bit plugin so that it would use the 64 bit plugin that I already had installed in my .mozilla directory. Mouse clicks worked… Unfortunately it was crashing constantly. I couldn’t even load gmail without crashing Firefox.

Is it Firefox’s Fault?

I have both Firefox 3.0 and 3.5 installed. Both were just as crash happy. I was hoping it would be as simple as blaming Firefox 3.5…

Firefox in a Jaunty chroot

I had a 64 bit jaunty chroot environment already sitting on my hard drive. It only took a few commands and a little waiting before I had Firefox and the 64 bit Flash plugin from Adobe installed in the chroot. It ran perfectly.

I compared the output of ldd libflashplayer.so from inside and outside the chroot. One extra library was showing up in the chroot, libresolv.so.2.

How to Fix It

Just install the libadns1 package:

sudo apt-get install libadns1

That fixed it for me. As always, your mileage may vary!