Fourth Alpha for Fennec on Windows Mobile

02.18.10 - 05:54pm

I’m really happy to announce the fourth alpha release of Fennec for Windows Mobile. It has been some time since we released the third alpha and things have come quite far since then. Please have a look at this video walk through to get a sense of how things are shaping up.

We’ve made some pretty big improvements with overall performance since the last release, particularly with panning. Also, the fuzzy zooming that was featured in the 1.0 release for maemo makes an even bigger difference on windows mobile in terms of responsiveness. Finally, we really fixed up our interactions with the soft keyboard.

To install this release, you can grab the cab from here. We’re also experimenting with an alternative exe installer, but only recommend it for users with unlocked devices due to the way Windows Mobile handles signing. It can be found here . For more detailed information on this release, check out the release notes.

Please try this release out and keep the feedback by coming filing bugs, commenting here or dropping in on the #mobile channel on irc.mozilla.org.

Category: mobile, Mozilla |

← →

The Conversation {12 comments}

  1. Omar {Friday February 19, 2010 @ 12:41 am}

    I installed this to my storage card and had horrible freeze ups on my AT&T Tilt 2.

    Now I am trying to uninstall it and it completely freezes my device when attempting to uninstall.

    Any idea what I need to remove in order to manually uninstall?

    Thanks,
    O

  2. Tristan {Friday February 19, 2010 @ 4:46 am}

    The demo is very cool and Fennec is making a lot of progress, including responsiveness. Lovely!

    You may want to update https://wiki.mozilla.org/Mobile/Platforms accordingly (it still mentions Alpha 3 as the latest version).

  3. jack {Friday February 19, 2010 @ 5:37 am}

    good

  4. lockoom {Friday February 19, 2010 @ 5:50 am}

    Doesn’t work on Acer M900 (WM 6.1, 128 MB RAM (51 MB available)). Tried on native 800×480 and 640×480 (via WVGAFix).

  5. ManWM {Friday February 19, 2010 @ 10:46 am}

    Browser is too big & slowly… There are more faster browser that this.
    For example – Ucweb – 2mb

  6. Я {Friday February 19, 2010 @ 10:59 am}

    первый нах

  7. Я {Friday February 19, 2010 @ 3:32 pm}

    Пиздато! =)

  8. Ezh {Friday February 19, 2010 @ 6:29 pm}

    Does not run on HTC Touch Pro with TAEL ROM. XULrunner: not enough memory to run Fennec.

  9. S {Saturday February 20, 2010 @ 4:02 pm}

    Works much better than Fennec alpha 3 on my Xperia X1a (With latest stock winmobile 6.1 ROM). There are still plenty of problems which need to be addressed such as crashing when attempting to install add-ons from the add-ons page, (often) crashing after waking from standby, and other random crashes.

    What happened to the 1.1a1 cab/exe downloads, it seems as though they have now been deleted?

  10. michael {Tuesday February 23, 2010 @ 11:54 am}

    please don’t forget HD2 its the best now , Acer Neo!!!
    also multitouch , it will be available on all WMobile devices coming next year
    also about G-Sensor , when we rotate the phone , browser rotates

    i beg you to dont forget HTC HD2

  11. Flat back {Thursday February 25, 2010 @ 2:52 am}

    Is it possible to un-install if as mentioned a freezing screen occurs as im a bit reluctant to upgrade if there is no recovery option.

  12. blassey {Thursday February 25, 2010 @ 3:06 am}

    @Omar and Flat back – You should be able to uninstall as usual. If that fails for some reason please file a bug. If all else fails you can uninstall by deleting \Windows\FennecFastStart.lnk and rebooting. When the phone comes back up delete \Program Files\Fennec and \Windows\Start Menu\Programs\Fennec.lnk

    @Ezh – we hear of a lot of problems with custom ROMs, if you want you can try with a default ROM

    @S – the links provided are to the 1.1a1 cab and exe. To be clear Fennec version 1.1a1 is the fourth alpha release and the fourth alpha release is version 1.1a1.

    @michael – the HD2 is a high priority. we’re currently working through a bug that seems to be unique how that device loads libraries.

Sorry, comments for this entry are closed at this time.