Hey guys, was browsing through the list of ROMs in ROM Manager when I came across a ROM by "the orca project"
I went to their website which had a link to their stable version (8th February) and downloaded and tried it out.
Coming from AOKP Milestone 3, I found this ROM to be amazing in performance! I've had the highest Antutu benchmark score with this ROM as opposed to others (namely ARHD 2.1.5 and Milestone 3) and everything just works great.
The default kernel is leankernel by Imoseyon (although I updated to his 1.10.0 version which I found was slightly better).
The ROM itself is probably more similar to AOKP Milestone 3 than any other ROM due to its settings and features, however I found this to be more smooth and stable than any other ROM.
I'm in no way associated with these guys, just thought I'd share my experience with you guys about this ROM (which isn't on XDA or Rootzwiki.com)
So try it yourself if you want, you won't be disappointed!
-Cheers
Look at the github commits for the ROM, and you'll see it's essentially a kang ROM where the developer pulled most of his stuff from AOKP/CM9. He even went so far as to rename the Trebuchet launcher without doing much of anything to it.
So sad people copy people's works and renames it as their own. This thread should be closed.
edit:yes you are right zephik
being a maintainer for bamtaumod i can tell you that they have not uploaded their sources to github yet, they have forked from some accounts but the current sources that they use is in a private repo on bitbucket.
However, the orca project is shut down anyways so whats it matter.
Related
So, what's the difference between "4.0.4 merged into build" vs true 4.0.4 AOSP builds?
And the same question for kernels with "4.0.4 merged into build" vs true 4.0.4 kernels?
Will it get better when the devs are going to build from 4.0.4 source from the ground up?
Cuz until now I'm not really that impressed with the 4.0.3/4 "hybrid" builds (i.e. I find LiquidSmooth v1.2 a lot smoother/ faster/ better on battery than the AOKP b29 "4.0.4 merged" build)
Just curious
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
adrynalyne said:
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
Click to expand...
Click to collapse
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Ti2 said:
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Click to expand...
Click to collapse
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Ti2 said:
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Click to expand...
Click to collapse
There are some things in the work (besides 4.0.4) that need to be finished yet, but I would say it won't be much longer.
adrynalyne said:
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Click to expand...
Click to collapse
Have you released a 4.0.4 rom mate?
Stretlow said:
Have you released a 4.0.4 rom mate?
Click to expand...
Click to collapse
We have merged with 4.0.4, but we havent released an update yet, no.
Hi Everyone,
I was wondering if anyone could say what the difference between the two builds of CM9 are. There's the team chopsticks version found here: http://www.teamchopsticks.org/p/install-guide.html. And there is the, I guess more or less, official release here: http://www.cyanogenmod.com/blog/cyanogenmod-9-rc2
Am I right in thinking that the team chopsticks version is an unofficial attempt to port it over at the same time that the CM team came out with official support.
Has anyone compated the two? I've often heard a lot about CM, but have never tried it. I'm currently running Darkside Evolution 3 v8 with Touch0Color theme and I love it.
Thought?
I too was thinking about giving the latest CM9 RC2 a try. Kind of waiting to see if anyone else gives it try and reports back. I might do it before end of day today though.
http://download.cyanogenmod.com/?device=hercules&type=RC
I am currently running same Rom as you but a version behind, V7. I am just hoping that I can install it with the same version of Clockwork that I used for Darkside.
Team Chopsticks are the official maintainers for CM on T989. They are the ones who incorporate and create the code for our device. CM requires that all code be checked and approved before being merged. The "unofficial" builds from team chopsticks represent experimental, unapproved changes yet to be fully merged into CM.
Essentially, they are one and the same.
ive been wondering the exact same thing. im currently running darksidev8 as a dd but recently tested aokp which was nice as well. now im interested in seeing what cm9 has to offer.
Try the Cm9 rc2 its a daily driver for me.
Sent from my SAMSUNG-SGH-T989 using xda premium
Best advice download and try roms from this site as opposed to searching the web and as others have said yes Team Chopsticks are the maintainers for our phone so what they do to CM9 will be strictly for our phones.
If you are new to CM9 just stick with the thread we have here and get goo.im which will help facilitate your downloads of updates.
My lack of posts doesn't allow me to post directly in the ROM thread currently, but I wanted to let the PA team know that the game Bladeslinger is broke on toro.
I was on the latest nightly from fairct, 3/28.I was on the AK kernel, and the stock one that came with PA, but the game would always crash on chapter load.
I'm currently using the "Shiny" ROM from rootz, which is basically stock, and it runs fine there.
Just the question:
What ist the difference between Rubik ROM and AOSPA-L?
http://forum.xda-developers.com/showthread.php?t=2220239
http://forum.xda-developers.com/showthread.php?t=2276511
As I see it, Rubik is based on an older PA version, but both are built out of PA with Linaro.
Is there anything else?
Are the Linaro Builds faster than normal builds, when not playing?
nobody?
Basically, the Rubik builds are maintained by the same guy who's currently maintaining the official AOSPA builds. The AOSPAL builds are updated as quickly as the official builds, and, apart from the Linaro, they're currently the same, more or less, as the official builds. The devs have said that they have cherry-picks in mind for it, though.
Also, the Rubik builds have more features, compared to the official builds and AOSPAL. However, Rubik is not updated as promptly as either of the others.
Hope I helped
Hi guys, wondering what is rocking our OP3s around?
Let's put it together with this month' mega-poll!
Totally stock here
CM-based ROM + Standard CM kernel
Sultanxda cm13, Could you had it to the poll ?
olimar7184 said:
Sultanxda cm13, Could you had it to the poll ?
Click to expand...
Click to collapse
I literally had it already in the poll, but before submitting it thought that there might be other ROM worth mentioning and the poll would soon become incomplete. Because of this I preferred to insert a "generic" point at last.
Quick summary after one day of votes:
65% is running OxygenOS (or OOS-based ROMs)
35% is running CyanogenMod (or CM-based ROMs)
Let's see how these results will change with the steady improvements made by both worlds!
Running oos + ex kernel. Just because of camera apk
Just bumping this poll 'cause I'm curious to know what everyone is running! ^__^
Damn! I seem to be the only with Stock OOS + Blue spark kernel
Happy with Freedom OS 1.6 CB with Blu Spark
You totally forgot AOSP based Rom like Slim, Tipsy, Cardinal, Orion, Exodus...
Cm only cm
@Striatum_bdr, I hear you but that's the purpose of the last choice in the poll.
The poll would become obsolete too soon if I were to list each and every possible ROM, which we all know is a moving target.
As you can see less than 7% chose the 'Other combo' item, so I guess we can call the information near complete, while not perfect.
Come on guys, let's keep it up!
Whats best fort battery? Stock with ElementalX kernal? Or sultanxda CM?
Standard CM + ElementalX kernel
Stock 3.2.4
Come on guys, let's do your coming-out! ^__^
Nuclearom+kernel
OOS Community build 3.5.2 and stock kernel.
RR + Boeffla Kernel