Ohai! Here's the deal. I pulled the plug on the Eos project for a few reasons. First, I became unable to maintain the quality of the project while having to deal with countless internal systems issues and doing branch and build maintenance. Second, I didn't have control of the servers and other various resources, like the Goo account. That's why I couldn't get rid of the last two derped builds. Third, I'd rather focus on innovation than dealing with all the internal AOSP build system stuff. As of now, it appears the Eos servers are offline. Which is fine because i have the repository on numerous boxes and right here on my laptop. Finally, I was no longer enjoying Androiding. I NEEDED SOME FRESH ENERGY! Virtually the entire Eos team has already migrated to the new project and got their respective devices up and running! I put about 40 hours a week into Android and I needed to find some guys who have similar time to dedicate to a project. And that team is CodeFireX, lead by Synergy.
A little about Synergy, founder and new combined project team leader. Synergy is a linux guru. He is a master of the aosp build system and talented C programmer. Synergy leads the AOSP scene in innovative new optimization techniques and build solutions. TeamEos has worked closely with Synergy and CodeFireX for a while now. So the decision for us to migrate over to CFX made perfect sense.
When I drop some test builds, you will notice that, indeed, it is a new project, with some new philosophy. There is more CyanogenMod resources in this project. Particularly, some of the CyanogenMod apps including the CMFileManager and Apollo, the CM music player. We are also using the open source Superuser solution from Koush. "Why is this?" "Won't it look like a kang build?" Well, yes. But this project will be the one getting kanged. Like Eos, this project started with a pure AOSP base. I have been surgical in bringing in select desired resources from other teams. Synergy embraces the philosophy of having a solid build without a gapps package installed. In light of recent revelations regarding government surveillance, many people are enjoying Android without the Google Services. We want to provide a build that caters to these wise individuals. And, we feel that the open source CyanogenMod resources are the best. You will "feel" Eos in this build. The Eos spirit lives on in CFX. Always remember, it's not about team names, it's about people.
We now have a wealth of new resources to provide to our users. We have dedicated hosting in which downloading builds will be smoking fast. We have SERIOUS bandwidth. We also have a new forum in which we can provide users with tools that go beyond XDA support. However, I will continue to maintain XDA threads, of course. We have a sophisticated new ChangeLog scheme. And we now use Phabricator instead of Gerrit for project review.
Xoom users face a challenge now. Because of optimization, the build is rather large. Optimization increases the size of libraries and binaries. So, in order to get a successful Xoom build, I have to really "unbloat" the build. This is due to the Xoom having such a small system partition. And that brings us to gapps. Many of you know, CyanogenMod has made the decision to discontinue support on "non-neon" devices. The Xoom is one such device. The reason for this is mostly because Google is discontinuing support of non-neon devices as well. So, for now, I don't have a solid gapps solution. But i'll come up with something, I always do ;D
Test Builds: I should have round 1 up soon. First rounds will be no gapps and meant to simply test core functionality and hardware.
I truly hope you guys enjoy the new project. Besides, it's time to get some fresh ENERGY back in the Xoom scene anyway!
Stay tuned
A little about Synergy, founder and new combined project team leader. Synergy is a linux guru. He is a master of the aosp build system and talented C programmer. Synergy leads the AOSP scene in innovative new optimization techniques and build solutions. TeamEos has worked closely with Synergy and CodeFireX for a while now. So the decision for us to migrate over to CFX made perfect sense.
When I drop some test builds, you will notice that, indeed, it is a new project, with some new philosophy. There is more CyanogenMod resources in this project. Particularly, some of the CyanogenMod apps including the CMFileManager and Apollo, the CM music player. We are also using the open source Superuser solution from Koush. "Why is this?" "Won't it look like a kang build?" Well, yes. But this project will be the one getting kanged. Like Eos, this project started with a pure AOSP base. I have been surgical in bringing in select desired resources from other teams. Synergy embraces the philosophy of having a solid build without a gapps package installed. In light of recent revelations regarding government surveillance, many people are enjoying Android without the Google Services. We want to provide a build that caters to these wise individuals. And, we feel that the open source CyanogenMod resources are the best. You will "feel" Eos in this build. The Eos spirit lives on in CFX. Always remember, it's not about team names, it's about people.
We now have a wealth of new resources to provide to our users. We have dedicated hosting in which downloading builds will be smoking fast. We have SERIOUS bandwidth. We also have a new forum in which we can provide users with tools that go beyond XDA support. However, I will continue to maintain XDA threads, of course. We have a sophisticated new ChangeLog scheme. And we now use Phabricator instead of Gerrit for project review.
Xoom users face a challenge now. Because of optimization, the build is rather large. Optimization increases the size of libraries and binaries. So, in order to get a successful Xoom build, I have to really "unbloat" the build. This is due to the Xoom having such a small system partition. And that brings us to gapps. Many of you know, CyanogenMod has made the decision to discontinue support on "non-neon" devices. The Xoom is one such device. The reason for this is mostly because Google is discontinuing support of non-neon devices as well. So, for now, I don't have a solid gapps solution. But i'll come up with something, I always do ;D
Test Builds: I should have round 1 up soon. First rounds will be no gapps and meant to simply test core functionality and hardware.
I truly hope you guys enjoy the new project. Besides, it's time to get some fresh ENERGY back in the Xoom scene anyway!
Stay tuned
Last edited:
