Related
hi everyone,
As you see the topic its about AOKP team which they have a new version of ICS porting method. First they started moding the devices like Nexus-S and Galaxy nexus. After succeding they came up with other new devices and ported ICS base rom to other devices such as HTC, Xoom,Galaxy Tab.Today i talked to Roman the Dev guy from this team about our beloved TF.Unfortunately he said they wont port this rom to TF. I just started this thread to ask this team for porting this rom. I think if they see our requests they might put their efforts to make it work on our devices. Im currently using build 23 of this rom on my Nexus-s.it comes with lots og built in features.
here is the link for the website.Head over it might be interesting for you.
http://aokp.co
Sent from my Nexus S using xda premium
You said yourself they already said no. Respect their decision and leave them alone; if you don't like the decision you can port it yourself.
From their point of view, I can see why they said no. We will--eventually, one day--get an update from Asus themselves, which will satisfy 99% of users. The remaining 1% will get mods based on the Asus stock roms, just like they do now. There's also already a partially completed port underway by somebody else.
Why would they waste their resources on the TF101 when there are plenty of other devices that have no ICS port, and no chance of getting one from their manufacturer, which they could work on?
Actually, the correct guy to ask for a port is this guy @ProTekkFZS . He recently went on a spree porting aokp to many devices. Roman only port to devices that he is currently using which are gal nexus, nexus s and gal tab.
Sent from my Galaxy Nexus using XDA App
if they dont want to port it got to respect that decision but if they would i would be sooooo happy a really great rom would use it
roman recieved a htc sensation from rootzwiki and he hasnt even ported it there yet so i wouldnt hold my breath dude... although it would be epic...
Sent from my Revolver Powered Asus Transformer
there is a plan for cm this is nothing compared to that and then there will be miui
pashinator said:
there is a plan for cm this is nothing compared to that and then there will be miui
Click to expand...
Click to collapse
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
fonix232 said:
1, MIUI won't come to tablets until Xiaomi makes a tablet UI version
2, CM is nowhere yet for the TF
3, Currently AOKP provides more control and access to things than CM. It was stated Cyanogen by himself that CM9 will NOT contain the old CMParts style settings, but rather have them in their respective submenus. AOKP goes on the CM7 way, having a separate app what can switch controls on-off. I'm already using it on my phone (ZTE Blade), and it's currently more stable than CM or even an AOSP build.
Click to expand...
Click to collapse
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
kptnk said:
1, Miui for tablets could become a reality without Xiaomi since they decided recently to change their code in Open source...so maybe one day
2, not yet, sure, even if CM has already talked about TF cm9 to come
3, here i think it really depends on the phone : with my Nexus S, aokp is pretty stable and smooth, but not as some other aosp (Pete Alfonso's) or CM (fitsnugly's kangs) for example.
Let's first get next Paul's builds, Asus's release then, and CM9 eventually.....at this point we all should be Fulfilled.
Click to expand...
Click to collapse
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
fonix232 said:
1. First of all, they haven't gone totally open source yet. And to include a tablet overlay, that would be a huge work. Not just graphics, but compatibility, screen issues, alignments, and such.
2. There will be a CM9 build, but only after CM9 is stable enough, and Asus released theirs so Bumble-Bee, RaYmAn, Roach, and the others can make a working one. So no CM9 for now
3. Yes it depends on that too, but show me any point of CM9 having more feature than AOKP. AOKP derives directly from CM9 sources, with the additional apps and features, plus fixes. So I consider it more mature.
Paul already published his sources for the TF, so we could easily grab his tree, change some stuff for AOKP, and make a build. I don't have quite the PC for such building processes, it would take days, and my electricity bill is already over the limit - so I can't do it definitely. But if there's someone else willing, everything can be made
Click to expand...
Click to collapse
1 & 2, i agree, that's sure.
3, aokp has indeed for now more features than cm9 and kept cm7 idea with nominated menu, which is more than rich of full customization possibilities. My point was in fact on the stability, efficiency and smoothness : there are, for nexus s at least, aosp roms and some cm9 builds which are better than aokp. So not in terms of "quantity" but of a certain idea of quality. Certain idea, because it is of course a question of point of view. That said, i love Roman's work.
I wish i could build on Paul's and Roman's sources for our beloved TF, but even if my electricity bill could eventuelly bear it (for a time), i have neither the pc, nor the knowledge to do so, which is worse .....here's just a very greatful and curious user....
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025
aokp is good man...there is no difference
I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse
Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).
Thanks everyone.
simms22 said:
you are looking for any aosp(android open source project) based rom, based on pure android. the nexus 4, as well as all other nexus, are aosp devices. rasbean jelly is one of the best, if not the best http://forum.xda-developers.com/showthread.php?t=2028025
Click to expand...
Click to collapse
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
[email protected] said:
I guess you should understand that all of the Roms you have mentioned are actually built from the Nexus Software. PAC and PUB are basically offshoots of AOSP /AOKP /Cyanogen / Paranoid. The nexus is the test bed, if you will. These ROMS are specifically for our phone, built from our phones ROM, with additions in order to better them. That is as straightforward of an answer as I can get you. You should give ALL of the roms a try and see what fits your taste best, hope this helps.
Click to expand...
Click to collapse
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Ace42 said:
Pac(Vertigo & Blue) has Linaro, Krait, and whatever the A15 patches are called(memspy?).
Click to expand...
Click to collapse
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?
the information is there, screenshots arent needed. but you should stay with cm then, if youre looking for an op and not a rom.
anyways, you do realize that all the nexus 4 roms are built from source? there no need to port roms to any nexus since all the sources are available for every nexus. so to say, all nexus roms are built specifically for the nexus 4, even cm. just because a rom exists on multiple devices, doesnt mean that its ported. most non nexus roms are ported to non nexus devices because they dont have sources available. this doesnt happen to nexus devices.
this is identical with a thread i remember seeing in the gnex forums a while back. anyways, they are all made for the nexus 4. they use drivers that are specific to our phone. if you flash it on another device, it wont work. AOSP is AOSP, that's the point of it. you won't get any extra device specific features if a rom is only built for the nexus 4 vs cyanogenmod which is out for a bunch of phones. the only way that happens is if your phone has a hardware feature another one doesn't ie: NFC.
TheeWolf said:
Hi,
Many custom ROMs, like CyanogenMod, AOKP, Slim etc. are ROMs made for a wide range of devices, and are therefore not suited perfectly for the Nexus 4. These ROMs are great, of course, but after flashing lots of them I understood I want a ROM that is made specifically for the Nexus 4, as I think they would function better.
For example, I understood there is a thing called Krait optimization and I don't believe any of the ROMs I listed above have it.
I would appreciate if anyone could recommend such a ROM,that is also very customizable (well it is a Nexus...). I'm talking in a CM + AOKP level of customization
From my searching I have found two ROMs, would also appreciate if you could give me opinions about them/compare them:
PACman ROM - http://forum.xda-developers.com/showthread.php?t=2146879
PUB - http://forum.xda-developers.com/showthread.php?t=2146885
Thanks!
Click to expand...
Click to collapse
Hi. There are many things to argue here is this post but I will try to help to get you some information to get you on the right track. First off there are two versions if you will of Android, one being "AOSP" or the "Android Open Source Project" and "Google Android". Google Android is what shipped with your device, and has Google owned proprietary in it that is closed sourced, most of the development done in a Nexus forum will come from using AOSP Android. Its the same Android that ships with your device but it does not contain any of Google's proprietary and its completely open-source, however some of the coding needed for a specific devices hardware is not open-source, there's more I can go into on that but I'll stop in short by saying the Nexus4 is probably one of the best devices to be working on platform level coding since all of the binaries needed are properly licensed and most of the hardware coding is open-source. So now that's out of the way. Most of the roms here are forks of AOSP with some being forked from AOKP, CyanogenMod and PA, in order for a developer to build a Nexus4 rom they have to use the provided hardware binaries in combination to the software coding to produce said roms, so ALL of the roms here are built directly for this device. Where confusion come in at is that some of the developers do not have a Nexus4 and build based of the availability of someone being a guinea pig. Also you will have to know whats in you device, such words as "krait optimizations" should not be a hook to get you to try a rom nor should a screen shot since most of the roms look stock besides the few that are themed, ok if they're themed they probably should have a pic, but seriously know your hardware so that you are not just letting a buzzword give you a placebo effect, and remember a roms OP most times doesn't do any justice for the experience you will have from that rom so its best to just try what ever sounds interesting blindly...
TheeWolf said:
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Click to expand...
Click to collapse
you can't really optimize a rom for a specific device.
they are nearly the same for all devices, and there is no point in optimizing it for specific hardware.
what you can optimize is the kernel, the part that contains the device specific drivers and basically controls the hardware. these are already built and optimized for the nexus 4.
but that doesn't mean that fixes and improvements for other devices have negative effects on the nexus 4.
also, device specific changes in changelogs are mostly kernel related.
TheeWolf said:
Thanks everyone.
I have to say that in my opinion, this ROM looks somewhat unprofessional. Its not that I tried it, but I can't understand the basic things from the OP as I should, for example the ROM's features, bugs, screenshots...
Yes but I mean that all these ROMs are ports. Cyanogen, for example, exists for almost every device out there. Look at its changelog, you'll see every bit of change incorporated in the ROM's version for every device. What I mean is, they have not done anything (correct me if I'm wrong) to optimize their ROM for the Nexus 4. The ROM exists and functions the same for the S1, the Galaxy Nexus, the Nexus 4 and the HTC Sensation. Again, I may be wrong so correct me if this is the case.
Vertigo is the username of the Pac ROM developer as I can see. Is there a version of a developer Blue? I don't really understand.
And what is memspy?
Click to expand...
Click to collapse
Dude, first try and test a rom before you form and vent your opinion based on nothing.
Thank you everyone for the explanations.
gee2012 said:
Dude, first try and test a rom before you form and vent your opinion based on nothing.
Click to expand...
Click to collapse
As I have said, I have already flashed many ROMs, I am not basing my opinion on nothing. I have not opened this thread is not to find out "what is the best ROM" - more than a year of messing with Android and being here in XDA got me understanding there is no such thing, no best ROM. The purpose of this thread is get me some answers, to see if what I am saying is even true.
If Cyanogenmod is the same for every device then riddle me this:
Why is there a different .zip for each device?
You are not going to find a better all around ROM than CM dude. In CM each device has its own tree with many device specific commits and custom changes. You sound very ill-informed asking the questions you are asking; I am surprised you haven't received a lot more flame for it.
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?
s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
What about devices that have CM10 only?
lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.
JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app
XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)
lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.
Please, support for RAZR i (x86)
lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)
Hello! I have been studying a lot of topics related (if not required) to android ROM development since I was 15. I am age 18 now and I believe that I am ready to do what I set out to do when I rooted my first phone. I had originally purchased a nexus 4 to practice development on, only to have it suffer from irreparable water damage. I purchased the AT&T Galaxy S4 "jflteatt" to replace the nexus, and am currently using this phone. I have several questions and would appreciate any advice and input on how to further my knowledge of android development.
Is the S4 an ideal device to practice building from source and porting ROM's too?
Just how hard is it to "build from source"? I notice that most of the esteemed developers here on XDA have incredible experience in computer science fields.
I didn't list the experience I currently have because I would love for readers to list what areas they think are required to be an effective android developer. What areas would you suggest?
Is it acceptable to us a Virtual Machine to contain my Ubunut (64 bit) build environment? I plan on upgrading to a solid state drive when I can afford it. I have 8 out of 16 GB of RAM and 150 out of 500 GB of storage dedicated to my the Virtual Machine.
What would you suggest for a first project that I can do to get the hang of what non-app android developers do?
I am not finished with this post, I really need to go study for class and get off my XDA addiction. I am going to revisit this very soon to add anything I am forgetting and read the feedback.
NOTE: I have a tendency to really make people angry on XDA (well everywhere) without meaning to. So if I have offended anyone in any way shape or form, broken any rules, misplaced this thread, etc. Don't hesitate to let me know and I will promptly fix the problem to the best of my ability. I am very human and make mistakes, more than I care to admit.
I would say our s4 variant isnt the best choice, due to our locked bootloader...if you are on anything after MF3 than you wont even be able to test your source built roms since we have no real recovery after MF3.
With that said...your best device would be a nexus device...but looks like you already got the S4
And lastly, porting/buulding a preexisting rom from source is not that difficult, I have taken no computer science or coding classes and have successfully ported many roms through source.
Building your own custom rom from the ground based off pure aosp however is a diffenrt story and requires quite a bit if coding knowledge
Virtual machine will work, however dualbooting and building in a real linix environment will provide a faster build speeds
Hope that helps you...
Sent from my SAMSUNG-SGH-I337 using Tapatalk
mg2195 said:
I would say our s4 variant isnt the best choice, due to our locked bootloader...if you are on anything after MF3 than you wont even be able to test your source built roms since we have no real recovery after MF3.
With that said...your best device would be a nexus device...but looks like you already got the S4
And lastly, porting/buulding a preexisting rom from source is not that difficult, I have taken no computer science or coding classes and have successfully ported many roms through source.
Building your own custom rom from the ground based off pure aosp however is a diffenrt story and requires quite a bit if coding knowledge
Virtual machine will work, however dualbooting and building in a real linix environment will provide a faster build speeds
Hope that helps you...
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Building from pure AOSP is my ultimate goal, I should have worded that better. Adding my own features to android (hopefully useful ones) is something I have always sought to be able to do. I don't want to sound as though I want to leach off of other's hard work rather than contribute. More than anything, I want to be able to make useful contributions! Just thought I would specify. On another note, thank you for your suggestion and advice!
Hello Guys,
welcome to the world of Team-Exodus.
What is Team-Exodus ?
We are a small group of entusiasts that like to learn more about Android and the Android-ROM developement.
We aren't exactly beginners But there is still room to learn more (you never end learning).
What is Exodus-Rom ?
Maybe, we better should start, what Exodus-Rom isn't: It isn't a (semi)professional mainstream ROM like CyanogenMod,AOKP or similar Roms. We don't focus on buzzword features, nor are we into "bling bling" options. We don't need a "change clock color" option, just because we can do it. These are "low hanging fruits", something nearly everybody can do, who has a computer to compile Android.
So what is Exodus-Rom, what is our focus on ?
We mainly focus on learning how things can be done. We are more into "quality over quantity". We prefer to have 4 or 5 real good and stable working features and not 20-30 features that work... somehow... sometimes...
We want performance, a fast, smooth fluid UI, a real good user experience, not a overbloated kang rom.
For instant that's the main reason why we currently don't have a Marshmallow Rom online, but I will give you a little more information regarding Exodus-6.0 (marshmallow) later.
But before that, who are we, who is "Team-Exodus" ?
The core team of "Team-Exodus" consists of the following guys:
@PrimeDirective - Dave, a very talented developer from the US, founder and Team Leader of Team-Exodus, specialist in App developement (for instant our Exodus Updater or the Drop Wallpaper App) and also our specialist for in deep functionalities of the Android Rom (like a complete rewritten Navbar customization). He currently uses bacon (Oneplus One) and Flounder (Nexus 9) for developenemt
@Raja.M - Raja, a real nice guy from India, he is our java specialist, he started Android developement something link 6 month ago but his knowledge is fast growing. He developes on the bacon (Oneplus One)
@TheCrazyLex - Alex, a kernel specialist from germany, he joined Team-Exodus like 3 month ago, mainly responsible to optimize and unify our kernels where possible. He also uses the Bacon (Oneplus One) as developement device.
@usmcamgrimm - Adrian, our graphics and theme specialist. Beside his amazing wallpapers, he is also responsible for all our LGE G3 devices. He mainly developes on the VS985.
@Martin_Ro - myself, Martin, also from germany, mostly responsible for the server with the build system, gerrit and download page. I'm also developing here and there if I find some time as I'm a married guy with to young boys. I'm developing on shamu (Nexus 6).
But beside this core team, there are a lot more ppl that help us making the Exodus Rom as amazing as possible, I will add some more of them step by step
So, now, back to Marshmallow and why it takes so much more time to bring an Exodus-6.0 to you guys:
For this to understand, you need to know more about where we come from.
On late 2014 we (Dave and Me) parted from VanirAOSP (that wasn't really AOSP but also used CM as base at that time btw) because we feeled like it started to get more and more into that mainstream "feature count is everything".
With 5.1 we started to directly use CyanogenMod (cm-12.1) as base, but was somewhat annoyed by upcomming issues because they used their open source branch as testfield for unfinished stuff, so for 6.0 we decided to go as near as possible back to strict AOSP.
But a matter of fact is: With strict AOSP you aren't able to support every device, and not as many devices as we want to support. So we have had to make some decisions and try some stuff. In the end we started developing Exodus-6.0 with a Mixture of strict AOSP and CAF as base, with the really amazing wide support of CyanogenMod regarding devices.
But with this, we got back to one of our main concerns: CyanogenMod is doing a fantastic job regarding device support (nobody can beat them in that department) but they are cluttering their stuff more and more. In the past few month, they started to create their own SDK, their own framework. And their SDK started to grow like a octupus, sticking his arms into every aspect of android. But we don't want to use their sdk, so we needed to remove it from everywhere.
And that was, what took so long. We wanted the device-tree and their hardware layer, but not their feature, and for sure not their SDK. And removing that stuff from everywhere inside the device-trees and Hardware layer.
Also we needed to use some of their code stuff in various places to make the connection between our AOSP/CAF based ROM and their hardware/device stuff.
So that took us nearly a month to finish up, but now we have first working experimental builds for bacon, shamu and VS985 so we can go into the real developing stuff.
There is still a lot to do (bring back all the features we want to, make the rom that fluid that you might be used to from EXODUS-5.1 etc.) But the real hard part is done now and we are way neared to a first public beta. Depending on the time Dave can find for Exodus (he is really really busy currently because of a new job), we expect to have a public beta by the end of the month...
So stay tuned and be patient
Made sticky
Hello! I enjoyed the 1/2 of the core team's and the new teams work since JB VanirAOSP to Exodus .
Just wondering, it would be cool to say what you do to seperate you guys from the rest. I know you guys build with jdk8 instead of jdk7 for the lollipop builds and use Linaro with some optimization flags.
I'd like to know if you do more than that and also I am wondering how JDK8 especially helps with optimization.
If you need a tester for bacon. I'm here very big fan of 5.1.
Nice to hear the updates... waiting patiently...
Sounds like the beta will become a christmas present.
Gesendet von meinem Nexus 5 mit Tapatalk
big fan/user of Exodus 5.1 on falcon. out of all the LP ROMs i've tried this has to be one of the most stable and lean ROMs out there. love the amount of essential customization catered here and skipping of cliche features that no one bothers to use (atleast me).
big thanks to @sachoosaini for introducing me to the ROM.
Well here it goes on
@PrimeDirective always a great human and great developer who supported Falcon despite the fact that i can never able to contribute the device to you. I find a best buddy out there who will always be my friend... Now @koshikas thanks Dave for supporting this phone, i never did anything for exodus.. But i am committed for future. If Dave continues the journey for exodus i will be with him in all way... Well what he told me around 6-7 months back is now coming to the real world. Now they support falcon or not. But I am honored by Dave for being there with all the silly questions people ask in community, falcon has great life indeed now its upto the team they develope for it not. I will donating device as soon as I am getting my salary which i am for sure going to get soon..... Wish Luck to exodus....6.0 is on the horizon
If you need a tester...
Hey, if you guys need an experienced tester for bacon, look no further. :good:
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I'm with this guy
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Coolkid90 said:
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Click to expand...
Click to collapse
Hm, ok, might be, because english is not my mother language, but for me this sound like "too much drugs and not enough sleep"....
Oh, and by the way:
we just prepared the open source manifest so you can start contribute
I will write a short Facts thread for Exodus-6.0 so you know how to build, and what we changed regarding device-support...
Excelente
Looking real forward to Exodus MM!
sir I am with you here.
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I m new here and wish to get some knowledge from senior member.
Thanks for this great rom
Exodus seems cool... hyped for MM release!
delete : found it
"err on the side of kindness"
Hi guys
Only to keep you informed: We started publishing official release builds for Exodus-6.0.
Look into your devide Android Developement sections for more information or on our g+ community: https://plus.google.com/communities/106801227383087889476