TeamEos joins CodeFireX discussion and testing

SamuriHL

Senior Member
Aug 5, 2010
3,418
2,200
0
When 4.3 drops, we'll be working overtime merging. Synergy loves all that crap! I hate all that crap! See, this project works! But I'll help merge and make sure things are smooth and proper. This is a convo thread dude. Ask away!
Ohhhh, I see wonderful things coming out of this project with that kind of.......synergy? /Dr Evil :D
 

NoMercyWWE

Senior Member
May 29, 2009
648
60
0
34
Wingray seems good so far i will restore and test Everest

unable to test Everest, seems i have destroyed my sim Card Slot and have to replace it, will test the Everest build though but will not be able to test 3g
 
Last edited:

armido

Senior Member
Jun 4, 2012
101
8
0
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
"I was no longer enjoying Androiding", "Synergy is a linux guru. He is a master of the aosp build system and talented C programmer." " In light of recent revelations regarding government surveillance, many people are enjoying Android without the Google Services."

So, how much longer before we have a bootable linux system that will run genuine linux programs? Ubuntu touch failed us in this respect and many of us are looking for a solution.

Thanks!
 

bigrushdog

Inactive Recognized Developer
Apr 23, 2007
3,547
7,244
263
"I was no longer enjoying Androiding", "Synergy is a linux guru. He is a master of the aosp build system and talented C programmer." " In light of recent revelations regarding government surveillance, many people are enjoying Android without the Google Services."

So, how much longer before we have a bootable linux system that will run genuine linux programs? Ubuntu touch failed us in this respect and many of us are looking for a solution.

Thanks!
Man, you get right to the meat of the matter! Who knows? I can tell you we will be putting heavy focus on security and privacy.
 

armido

Senior Member
Jun 4, 2012
101
8
0
Man, you get right to the meat of the matter! Who knows? I can tell you we will be putting heavy focus on security and privacy.
This is definitely good news. My objection to having android for an operating system and Google behind it has always been the lack of privacy and security. Why should people have to open a Google account in order to use a device they have paid for? I've been a Linux user since Red hat 5.0 and over time Linux has continued to improve it's security features. Imagine, every file controlled as to what it can and cannot do (selinux) - not simply ownership and modal limitations. This is already built into Linux. Find a way to boot this operating system and all that's left to do is modify existing programs so they are more adaptable to use with small devices. I have no doubt Linux developers and programmers will rally behind such a development!
 
  • Like
Reactions: xavierleonelbr

tomcrown1

Senior Member
Nov 6, 2007
70
4
0
This is definitely good news. My objection to having android for an operating system and Google behind it has always been the lack of privacy and security. Why should people have to open a Google account in order to use a device they have paid for? I've been a Linux user since Red hat 5.0 and over time Linux has continued to improve it's security features. Imagine, every file controlled as to what it can and cannot do (selinux) - not simply ownership and modal limitations. This is already built into Linux. Find a way to boot this operating system and all that's left to do is modify existing programs so they are more adaptable to use with small devices. I have no doubt Linux developers and programmers will rally behind such a development!
I do not see a build for Zoom also can I use TWRP recovery to flash this ROM?
 

flight666

Senior Member
Mar 10, 2012
63
17
0
Sao Paulo - Brazil
Flashed Wingray + Banks Gapps, everything just fine! :)

Hey BRD, would you bring tablet UI as we had on former EOS builds?

Could you make wallpaper application to set a full picture file without having to crop it?

Thanks a lot for the wonderful work!
 
Last edited:
  • Like
Reactions: cunnie84

synergye

Senior Member
Jul 6, 2010
1,526
8,224
0
Let's make this easy! Here are all the xoom variants that need testing currently. Please quote this with a number and say if it's working or not :)

1) http://downloads.codefi.re/synergy/codefireXperiment-Umts_everest/testbuilds

2) http://downloads.codefi.re/synergy/codefireXperiment-Wingray/testbuilds

3) http://downloads.codefi.re/synergy/codefireXperiment-Stingray/testbuilds

4) http://downloads.codefi.re/synergy/codefireXperiment-Stingray_cdma/testbuilds

Whatever's good now may be able to get added to tonight's nightlies.

The gapps are HERE. Flash the "minimal" package.

Again, this is a TEAM PROJECT...some of us are just cuter than others. Right rush cheeks?
 
Last edited:

notbrodie

Senior Member
Sep 12, 2012
1,858
718
0
Portland

uzi2

Senior Member
Jun 6, 2008
2,528
638
113
Let's make this easy! Here are all the xoom variants that need testing currently. Please quote this with a number and say if it's working or not :)

1) http://downloads.codefi.re/synergy/codefireXperiment-Umts_everest/testbuilds

2) http://downloads.codefi.re/synergy/codefireXperiment-Wingray/testbuilds

3) http://downloads.codefi.re/synergy/codefireXperiment-Stingray/testbuilds

4) http://downloads.codefi.re/synergy/codefireXperiment-Stingray_cdma/testbuilds

Whatever's good now may be able to get added to tonight's nightlies.

The gapps are HERE. Flash the "minimal" package.

Again, this is a TEAM PROJECT...some of us are just cuter than others. Right rush cheeks?
2 working

Swyped from my xoom
 

bigrushdog

Inactive Recognized Developer
Apr 23, 2007
3,547
7,244
263
Wingray is working pretty well. Got all of my apps re-installed, a few of them seem to be experiencing issues. Only issues: 1) No custom QuickToggles, 2) No way to set live wallpaper, 3) (FF3, FF4, Super Hexagon, MorphWiz) all FC
Remember, all we're doing is testing hardware for now. But can you post up a logcat of one of your apps fc
 
  • Like
Reactions: notbrodie

Bux1982

Member
Feb 9, 2012
39
4
0
Münster
In recovery I did,...

-wipe data\ factory reset
-wipe cache
-wipe dalvik

After that I tried to install the Everest build in my MZ601 but it fails with...

Assert failed:"getprop ("ro. product.device") == "UMTS_Everest" || getprop (" ro. build. product") == "UMTS_Everest"

My fault or a problem with the build???
 
Last edited:

synergye

Senior Member
Jul 6, 2010
1,526
8,224
0
In recovery I did,...

-wipe data\ factory reset
-wipe cache
-wipe dalvik

After that I tried to install the Everest Bild in my MZ601 but it fails with...

Assert failed:"getprop ("ro. product.device") == "UMTS_Everest" || getprop (" ro. build. product") == "UMTS_Everest"

My fault or a problem with the build???
What does adb shell getprop ro.product.device say while you're in recovery?