New Replicant 2.2 preview images (0009) released

New Replicant 2.2 images are now ready and available to download. This new set of images (0009) is available for the following devices:

  • HTC Dream/Magic
  • Nexus One

This new release features the following:

  • Switched to the Android launcher on HTC Dream/Magic (should be faster)
  • We have a newer RIL that should fix some issues on HTC Dream/Magic/Nexus One
  • We added 2 wallpapers that Jan-Christoph Borchardt submitted (thanks a lot!)

Note that Replicant 2.3 images for Nexus One and Nexus S are on their way (you can already build Replicant 2.3 images if you want)!

We are still looking forward Hackers to help us bring some more freedom to the mobile word: there are many ways to contribute to the project!

9 thoughts on “New Replicant 2.2 preview images (0009) released

  1. Honestly, if you want a “stable and fast” ROM for HTC Dream, you should look at CyanogenMod, we just forked it and replaced the non-free components. So if you’re ok with them, CyanogenMod is probably the best choice for you.

  2. Is there a simple way to install the Play Store and Google Syncing? I think that should not be a problem, as that stuff is also just a couple of apks.
    Sure, that is just what this Distribution wants to avoid, but If this is a stable and fast ROM for my HTC Dream, I would use it instead of Ez.

  3. Yes I have an xmpp address. I would be happy to help you this way. Please come on #replicant IRC on irc.freenode.net so I can PM you and give you my XMPP address.

  4. Hi,

    Thanks for the explanations, but in english that’s hard for me. 😀

    Do you got an XMPP login messenger? (or can i give you mine?).

    Or any other way to discuss? (Freenode chat for example http://webchat.freenode.net ) As you want.

  5. In this case, bad hardware design refers to the way hardware is made:
    this occurs for instance on MSM/QSD phones (HTC Dream, Nexus One) where the modem (that runs non-free software that we couldn’t easily replace) has control over hardware components like audio (including microphone), gps, RAM, etc.

    This is bad because it puts the control of these critical-for-privacy hardware pieces under a non-free piece of software we can’t have control over. Considering that the modem also handle the data connection, it’s also easily able to send data/receive orders to mess with this (like sending the GPS location).

    The http://trac.osuosl.org/trac/replicant/wiki/NexusSTechnicalOverview page gives the previous explanations and explains why other devices (like the Nexus S or the Openmoko GTA02) don’t have these problems.

    And yeah, I’m French. If you want more infos in French, please let me know so I can contact you privately (I don’t think non-english talks belong here).

  6. Bad Hardware design?

    What do you mean? Bad ‘architecture’? (Sorry i’m french, mais vous aussi PaulK n’est ce pas? 🙂 ).

    Is there some french tutorials for me to try to install Replicant on my device?

    Thank you.

  7. Galaxy Mini seems more close to the Nexus One than to the Nexus S: it has a Qualcomm MSM7227 SoC. Adding support for it on Replicant might be possible even though it has bad hardware design.

  8. Superb! I’m following this project very closely – unfortunately I haven’t got the time to contribute at the moment. Keep on going guys, your efforts are hugely appreciated! 🙂

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.