OpenEclair is a community ROM based on the AOSP 2.1 source code (with lots of Cyanogen mixed in).
The goal of OpenEclair is to bring to the community a fast and stable Eclair 2.1 ROM, with contributions from numerous ROM developers.
Follow @OpenAndroidTeam on Twitter.
Developer - ctso - Twitter
Developer - wesgarner - Twitter
Developer - benbuchacher - Twitter
Forum Support - zeppelin481 - Twitter
Forum Support - zimphishmonger - Twitter
Forum Support - JAguirre1231 - Twitter
Bandwidth - A HUGE thanks to AndroidSPIN for hosting the ROMs!
Want to get involved? Simply ping one of the developers on Twitter!Features
- G1 - Requires DangerSPL
- AOSP 2.1 Eclair
- 10MB RAM Hack
- Nexus One Voice Input
- Live Wallpapers
- Compcache via SpareParts (including size!)
- CM Updater - Updates right from your phone.
- Supports G1/MT3G
- 5 Screen LauncherDownloads
OpenEclair - v1.0.1 STABLE
For the latest BETA version, go here:
OpenEclair - v1.1.1 BETA - 02/02/2010
- Reverted JIT (No longer using JIT - causes too much instability)
- Added EXT tools.
- Readded DangerSPL Requirement
OpenEclair - v1.1 BETA - 02/01/2010
- New Apps2SD (disables Apps2SD on MT3G)
- Added Passion Google Apps
- Fixed "insufficient storage" issue.
- Switched to WG-Kernel
- Optimized Launcher (thanks dumbbestcrayon)
- Fixed Music button on Desk Clock
- Removed DangerSPL requirement
- Added Swap settings to SpareParts
- Default compcache size set to 32MB
- Fixed keystore errors.
- Added rwsystem/rosystem
- Fixed "pm: not found" errors.
- Complete recompile from AOSP/Cyanogen
- Removed CM Updater (will be added again in a future release)
OpenEclair - v1.0.1 - 02/02/2010
- Fixed "insufficient storage" problem when installing apps.
OpenEclair - v1.0 - 01/28/2010
- Initial release based on Intension v1.4.0.Issue Tracker
Before posting an issue please do your best to make sure it has not already been reported. A good idea is to check the "Known Issues" section below.
Issue Tracker on Google Code
Please post all issues in the Google Code Issue Tracker. This thread can be a great area for support, but any bugs should be reported at Google Code so they do not get lost.
We are not responsible for bricking your phone!