PLEASE NOTE THE FOLLOWING: This is the BETA Series of releases. Some things do not work and you should assume BUGS will be present. I am not responsible if you brick your phone with this or any other firmware. You are your own warranty once you start loading firmware. Please do NOT post about anything that's in the "broken" or "bugs" list; I will ignore you if you do. The status of things that are "working" and not will be updated as changes are made. See the second post for a reverse-chronological set of builds. While I am using this as my "daily" as most elements are currently functional, not everything is working - or working properly. Note that this build uses the ext4 filesystem. Not all Clockwork versions can load this. The one in this thread can as can those of recent build by Isaac (yes, you should read the top posts by myself on every update, top to bottom.) If it's not listed as working or broken below then that particular feature has likely not been tested at all. This code has very little runtime on it at present and is under constant revision and development. You're getting a peek at the code in a state where I would normally never let anyone see it simply due to lack of testing and documentation - please keep that in mind. Kernel: Mine, built from Motorola's released source. The kernel has ext2, ext3 and ext4 support, and in addition to the standard governors also supports "SmartassV2". Default governor is "ondemand". Note that Smartass currently logs a bunch of complaints in the kernel log when ramping down the CPU speed; I'm looking into this but it does not appear to affect the performance or usability of the governor. I really like SmartassV2 but will not set it as a default; use CM7's or SetCPU's profiles to do so if you wish. Tunneling is built in and the CIFS loadable is present. Performance: Quadrant scores around 2400 on my unit with gobs of applications loaded. Codebase and credits: Originally sync'd from Isaac's work in the other thread, heavily modified at this point. Isaac deserves the credit for getting the base code to boot and getting me interested in hacking on it. We continue to work together. Please note that I have moved from Virgin Mobile and expect to sell my Triumph, so I will not be able to test anything else soon. The 0.8 build should thus be seen as a "final", although I will monitor the reports on Github for bugs and can build if necessary. What's remaining as non-functional, other than the wifi/bluetooth interrupt storm, is relatively minor or has no reasonable hope of being fixable. What's working (Bold = changed since last version): If it's not listed below, you can reasonably assume it works. In other words, pretty-much everything is working. Wifi tethering is supported in 0.8 but is untested What's known BROKEN (Bold: Added since last version): HDMI is inoperative. Front camera does not mirror snapshots or videos taken. Preview, however, is mirrored. Occasional force-closes if you switch cameras from front to back; the switch works but there is a buffering problem in the camera code that causes a fault during the switch process. CPU pegs if both Wifi and Bluetooth are on at the same time. This appears to be an interrupt storm and is a nasty problem as we do not have driver source for the libra.ko driver (Wifi); it appears to be coming from that device. For now the only answer is "don't do that." Included Apps: Essentially nothing. See below for GAPPS if you want Google applications (you almost-certainly do.) Note that you cannot provision on the CM7 ROM (the "Activate" apk, if you grab it from the Triumph, will not work - it appears to run, but does not function.) You must be provisioned using the stock ROM before you load this code. To install or update: 1. MAKE A NANDROID BACKUP! I cannot emphasize this enough - and make sure you keep that backup somewhere SAFE. Most notably there is no way to activate the phone on CM7 at this time, and there may never be. If you need to change your phone number or similar you need to swap back to stock firmware. If you lose the ability to do that you will be pissed. Consider yourself warned. 2. Place the file in the below post on your SD card in the root. 3. Boot to clockwork by turning your phone off and then hold BOTH volume buttons while pressing POWER. Release power when the phone vibrates and continue to hold both volume rockers until Clockwork comes up. 4. Important: Clear the cache and data ("factory reset") unless you are coming from a previous build of my CM7 code. If you fail to do this CM7 will almost-assuredly blow up on boot. If you have odd problems and didn't do a factory reset from Clockwork, try that before reporting bugs. You'd be surprised at how often ill-behaved applications have a kitten when versions of the operating system are changed out from under them. 5. If you are coming from a previous CM7 build I strongly suggest formatting /system (from the Clockwork menus) before loading. You don't technically need to, but not doing so could leave pieces of the old load laying around. Doing this will not bork your data and apps. 6. Select the ZIP file from the SD card (about halfway down on the top screen of Clockwork to get to that menu, then the first entry and point at it.) 7. Commit the update. On first boot it will take about 2 minutes before the system comes up. Provided you see the little CM7 guy with the rotating arrow, it has booted. If you are not clearing data and have a lot of apps loaded it may take materially longer - as much as five minutes - as the davik cache has to be rebuilt and the screen may time out before the boot is complete. If it's been more than 5 minutes hit the power button twice and see if that turns on the screen. It should. NOTE: On this release and forward the "Gapps" (Google Apps) must be separately downloaded and flashed after you load the ROM (before booting the first time is recommended): http://goo-inside.me/gapps/gapps-gb-20110828-signed.zip - Base Google Apps http://goo-inside.me/gapps/gapps-gb-20110828-newtalk-signed.zip - Google Talk (if you want it) The base "Goo-Inside.me" page is found here: goo-inside.me - gapps downloads. IF YOU FORMAT /SYSTEM AND DO NOT REFLASH BASE GAPPS AFTERWARD MANY THINGS WILL BREAK. That package contains all of the Google connections to Android - the authentication for your contact list, email, sync settings and more. It is generally safe to not format /system if and only if you are coming from one of my previous ROMs in the same series (e.g. Beta, etc) and you have not manually tampered with any files in the /system area or the kernel. If that does not apply then you should format /system and reflash GAPPS or I can virtually guarantee that you will not like the results. If you have changed files under /system, especially if you have replaced any of the stock applications (e.g. the dialer, etc) or the kernel there is a very high probability that the remainder of the load will be out-of-sync with what you did and that can cause serious stability problems. There is no way for me to know what you did in this instance and I cannot realistically provide individual assistance if you have modified system files in the load or on your phone. Please be aware that the framework, kernel and loadable modules are different than stock and in many cases from one version to another as this is a work in progress. If you want to make a donation to me for my work, please use the "Market Ticker" link below and hit the "Tip Jar." Any amount can be donated through PayPal using this method. If you sign up for my forum there you'll get credit for it too. Note: It's a tip; you're not buying continued work on my part by doing so. My Github repository is under the user ID "Tickerguy"; I have verified that the code I am running will build off the manifest and repos there from scratch, so if you wish to pick up the development the ability do so is there. Due to time constraints I cannot provide hand-holding on getting set up to build or develop on this or any other device; PMs requesting same will be ignored. If you know enough to be a developer and be productive for this or any other Android device then you know what you're doing already or where you can find the information on the Internet (yes, it is easily found!) on setting up the cross-compile environment necessary to do so.