Skyfire 2 for Android, a great browser with support for Flash video players released


Native Flash support for Android phones may be only a month away, but in the meantime, mobile browser-maker Skyfire presents a workaround in its brand-new beta app for Android phones.
Skyfire 2.0 beta for Android looks and acts like your typical souped-up WebKit browser for Android phones, with the exception of a tool that lets you stream Flash video--and soon Silverlight. WebKit doesn't currently support either technology.
When Skyfire detects a broken embedded video on a Web page, it signals Skyfire's servers to fetch the video and transcode it from its original format to HTML 5 video. 
What's more, Skyfire's servers will adjust the video resolution to performance factors like your phone's screen size and your network speed in order to provide smoother streaming. Videos certainly played without lagging or buffering interruptions in our demo with Skyfire on the Motorola Droid, and in our own tests on the Nexus One.
Skyfire's Flash-support-by-proxy isn't an all-in-one solution by any means. It doesn't detect every video in a playlist. Occasionally, it crashed a browser tab. And it doesn't address Flash games or other interactive sites; we're still waiting for a seamless way to read Flash-based menus online.
In addition to video streaming, Skyfire also adds its twist to the Android's WebKit browser with a button for viewing more relevant content, like headlines, images, and Twitter updates, and a link-sharing module. There's a browser tab-switcher, a shortcut to easily switch between desktop, Android, and iPhone mode (known as user agents,) and a drop-down menu with access to the settings, download list, text selection, and other tools. The quintessential "back" arrow and bookmarking are also present. On Android phones running OS 2.0 or higher, Skyfire also supports multitouch pinch-zooming.
Skyfire's brand-new Android browser
Skyfire's brand-new browser gives WebKit an Android twist.
(Credit: Skyfire)
There are some known issues and limitations with the Skyfire beta's video support and browser in general. It won't currently stream back Windows Media, Silverlight (that's next), or Quicktime video, and it intentionally won't provide video or additional content for secure sites. On some sites, swapping browser modes (the user agent) will force-close the app. The Help function was turned off when we tested the app before its official launch, and there are some interface issues with the Explore window on the Motorola Backflip while in "backflip" mode.
Although Skyfire's browser for Android is officially labeled 2.0 (beta), it is, in fact, the company's first offering for Google's mobile platform. The browser's front and backend designs are what diverge it from earlier 1.0 and 1.5 models for Windows Mobile and Symbian phones, which were coded entirely by Skyfire and built to look like a traditional desktop browser. With Android, the company layered additional features onto WebKit, much likeDolphin BrowserxScope, and others.
Skyfire CEO Jeff Glueck confirmed in an interview with CNET that we should expect to see a version of Skyfire for BlackBerry soon after OS 6.0 emerges with a new WebKit-based BlackBerry browser. We're also keeping our eyes trained on the iPhone--after Opera's success getting its proxy browser into the App Store, Skyfire made it no secret that it intends to follow suit, this time bringing unprecedented Flash video transcoding and streaming to an OS the CEO of which has emphatically declared will never carry Flash.
You can try Skyfire 2.0 beta for Android free from the Android Market on your phone and at get.skyfire.com.
Thanks to Cnet News

Ubuntu 10.04 hit by major bug on release day



It's the end of April. Spring is here, and so is Ubuntu 10.04. Or at least, that's the plan. Canonical's rigid release schedule is awesome for many reasons -- one of which is the amount of excitement it generates around each new Ubuntu release. However, I don't think this is the kind of excitement Mr. Shuttleworth had in mind when the "fixed schedule" policy was set. 

As it turns out, after the final release ISOs were already created (or "spun" in Ubuntu geek-speak), a critical bug came up; and no, I don't mean something like "OMG, we put the window buttons on the wrong side!". I mean something like "once you install Ubuntu, you will not be able to boot your other operating system." Oops. It doesn't kill the other OS, and it's fixable when it happens (it's a problem with the GRUB2 bootloader configuration), but it's certainly not something you want to have happen to people just trying out your OS (or even upgrading from previous versions).

Granted -- it doesn't happen with each and every installation, but it can happen. The Ubuntu team considered a quick-fix, but eventually went for the more responsible (and safer, in terms of PR) option of re-spinning the ISOs. However, re-spinning all ISOs would push the release into May, which would be a PR flop in itself. So they're just re-spinning some of the most popular ones, like the x86 and x64 desktop releases, as well as the Netbook remix. Exciting stuff!



Incident Description given by Ubuntu Release Team


We had a late discovery of GRUB bootloader bug affecting dual-boot users of Ubuntu. When installing in a dual-boot environment, the other operating system will not appear at first in the GRUB menu. Installing the available updates and rebooting will fix this issue. However, it was determined the day of the release that this is not an optimal solution for new users or those not connected to the Internet.

Chk it out here : https://wiki.ubuntu.com/IncidentReports/2010-04-29-Late-respin-for-bug-570765