Hi , lot of developper Jerpelea , Zdzihu & TripNRaVeRs and i dont forget Binary & Maxrfon & goroh "
try hardly to put custom rom for our X10 ,
strategy : why focusing on 2.2 or 2.1 AOSP : 2.3.1 is more attractive we have a lot of delay stop viewing the past :
Synergy : each developer work hard but alone "not enough fast" maybe the creation of one Dev-team & one project " avoid the personal conflicts" is a better way to escape from SE Curse they develop 2.1 and 2.2 is already in the Market
PS: i am very proud by our Devs , I only think that 1+1+1+1 ..... is better than BIG One
its a democracy but consensus is better
+1
agree with u , all of them are proffisor alone but if thy work together we don`t know what they can do !
I support your initiative. I would love to have ONE great ROM (with full hardware support) rather than several "half implemented" ROMs like we have today.
IMO most developers here prefer to work alone (don't know if it's related to donations...), but it's really easy to see that if all of them join a single project we would definetly have a better and more optimized ROM.
One good thing is that Google seems to slow down the new major releases to two a year, so our developers will also have more time to debug and keep up.
I can only assume that they have put a lot of time looking at and understanding how the previous versions run, now they have an understanding they are putting it to good use and developing us a custom rom free of charge. To inhance our phones
I dare say they are probably looking at the gingerbread stuff now but you can only you can only do what you can do, there is no point stopping a development everytime new software came out because that way you would never have anything finished.
Patience is key, these guys do have lives, there is a order to everything and just because you dont understand it doesnt mean it is wrong
the dev's are amazing and i wish i had the knowledge to help more, icecream is coming out in the summer will the devs be expected to down tools and move on from gingerbread then?
just be patient and let the devs do their magic
My (limited) understanding is that since the bootloader is still locked, they are developing these custom ROMs on the existing 2.1 kernel that SE has put out for the X10. That means that certain core components are Android 2.1, and can't be replaced without bootloader access.
As such, it makes sense that the further an OS version is from 2.1, the more likely it is that it will require specific features not available in the 2.1 kernel.
So developing stock 2.1 for the X10 would be easiest, 2.2 would be more difficult, 2.3 even moreso, and so on.
maybe its true but developing 2.1 AOSP or 2.1 with sense take a ot of time and confir the stupid idea from SE Eclair 2.1 plus SE soft is better than Froyo ,
Creating a team will reduce time of developement and may be improve the quality of the rom build , my idea it just to say that and unify the X10 community in supporting one effective project thant wasting a lot of creativity & effort in incomplete work its easy to say the difficulty is to DOING the Job
Just a little bit of insight here from someone who isn't a developer of ROMS....
I agree that combining their efforts would most likely give us better results with regards to hardware. Here's what I think may be happening. Now that they're able to create functioning ROMs, they're each taking the time to hammer out their skills. When you learn something new, you generally spend your time redoing the same thing over and over until you've got it down pat.
That being said, they're each learning more and more as they attempt new ROMs. I think once the fascination of "Hey I got a working port of *this* ROM first!" wears off, maybe they'll work together to create a fully functioning ROM. Who knows, one of them may actually sit still for a moment and finish up one of their own ROMs.
I hope that all of the developers working on different ROMs at the very least keep a line of communication open between them so as to share fixes and work arounds.
speaking of GB
http://forum.xda-developers.com/showthread.php?t=911364
Yes! I Agree With You!!!!
+1
I love all the dev here, but i too just don't get it..
either i get a working camera or working wifi ? Come ON...
i hope you guys see this posts as friendly talk, we are so lucky that we have all of you here you all understand the need of one functional AOSP Rom 2.2, 2.3 whatever
I feel the same way maybe the devs should team up and create a monster ROM that works.
I agree. It's been proven time and time again, teams work better than individuals. Please unite Devs! Think of what could be accomplished
I havn't even tested a ROM yet since their all incomplete, simple as that.
All the different ideas and "wishes" posted on this thread are of course appealing but until the bootloader is cracked it's practically impossible to have a fully working ROM on any other version other than the 2.1, at least from a short term perspective.
Correct me if im wrong, but from my understanding they started to work with 2.1 just to make it simpler to mod the code to 2.2 later.
The reason is that SE have released some code for 2.1, but of course not for 2.2. So they used SEs 2.1 code to develop the 2.1 AOSP rom. And could therefore much easier convert the code to 2.2.
It seems like you guys haven't been paying attention to dev work for the x10. Maybe it's because you didn't lurk the sub-forum since the beginning or maybe you don't understand what the devs are actually doing.
The devs ARE working together. jerpelea, zdzidu, bin4ry, goro-kun, maxfron, and many others DO communicate.
What one person said about having 2.2+ functions are strictly related to the kernal and bootloaders is the final word. Sony implemented special drivers for the camera and video decoding.
Until someone writes the drivers from scratch AND unlock the bootloader, we will have less than 100% functioning 2.2+ roms.
on that 2.3.1 HTC rom camera is working ... if they can get the BT and Wifi working it will be awesome . but i have a question . will we get the (MT) on these roms after SE release? i mean for 2.2 and 2.3
robbyf66 said:
I havn't even tested a ROM yet since their all incomplete, simple as that.
Click to expand...
Click to collapse
Yep.
Me neither.
And only because the camera and HD are not working
hemo1001 said:
on that 2.3.1 HTC rom camera is working ... if they can get the BT and Wifi working it will be awesome . but i have a question . will we get the (MT) on these roms after SE release? i mean for 2.2 and 2.3
Click to expand...
Click to collapse
The htc rom mentioned by you is 2.1. That thread is for 2 roms. 2.1 htc and gingerbread. So no, camera is not working on 2.2+ yet. Z got some progress making the camera atleast respond, but so far, if he implements full camera function, he looses other key functions in the rom. Not a good trade.
Sent from my x10 running 2.2
No pressrue on the devs and they can do what they please with their work. But as other have said it sounds like a great idea. Any devs care to comment on this idea?
Sent from my X10a using XDA App
Well, there are only two kernel developers here in the P500 forum, franco and fserve. There is no doubt that the work both of you have done is off the charts, tweaking every little thing that can be tweaked to such an extent that there hardly is anything left to tweak. And there is no doubt that most, if not all, of the people using your kernels love the work you guys put out.
With that in mind, however, there are a couple of things (specifically bugs) that we request, not demand, to be fixed. As we all know, our phone is affected by two things that I, as well as many other users, believe are two major bugs: the cpu spiking to 100% when touching the screen and the axis inversion bugs. Even with both of your kernels as good as they are now, these bugs hinder their true capability, thus hindering the phone's true capability. Both of you might just be thinking, "Well, there is paolo's kernel, go use that." And as kernel developers, you have every right to think that and decline this request. But seeing how good both of your kernels are, why not make it better?
Please consider this, as many of us believe both of your kernels can be made better with these bugfixes.
The poll is there as an estimate and measure of how many users believe that these bugfixes will make your kernels better.
sweetnsour said:
Well, there are only two kernel developers here in the P500 forum, franco and fserve. There is no doubt that the work both of you have done is off the charts, tweaking every little thing that can be tweaked to such an extent that there hardly is anything left to tweak. And there is no doubt that most, if not all, of the people using your kernels love the work you guys put out.
With that in mind, however, there are a couple of things (specifically bugs) that we request, not demand, to be fixed. As we all know, our phone is affected by two things that I, as well as many other users, believe are two big bugs: the cpu spiking to 100% when touching the screen and the axis inversion bugs. Even with both of your kernels as good as they are now, these bugs hinder their true capability. Both of you might just be thinking, "Well, there is paolo's kernel, go use that." And as kernel developers, you have every right to think that and decline this request. But seeing how good both of your kernels are, why not make it better?
Please consider this, as many of us believe both of your kernels can be made better with these bugfixes.
Click to expand...
Click to collapse
Agreed
PES2012 is hard to play with the lags but suprisingly Pes2011 does not have lag...I read once that Sippolo said its a 2 minute fix for the cpu spike bug
i think its ok to fix bugs even when most users can profit.
but, what about users who have new/other phones now?
i know from franco he's not developing on .35 currently because he has a new phone
and the P500 is used by his father - no way to develop on every day. the next reason is as we
all know, the P500 is a nice device for android beginners but most of us have seen
the new things like Nexus S, Galaxy S-2, HTC devices or other high end phones. I'm sorry
to say that but the P500 is some old and almost used in countries where such high end
devices cant be payed for, or, in most cases too - most users who bought this device
are very young (when i think how old i'm) - and, good developers have a real job to get
enough money for high end devices ... so, these developers cant support such low budget
devices all the time.
For me this means, i'm developing on P500 because its most funny for me to see all these
**** LG hardware bugs, but decided too that there is no way to develop on P500 the next year
too, so the next phoenix-android gingerbread will be the last release for the P500 device too.
I dont know what mik_os is doing, i think he has a real job too and no time to develop all
the time for this device ...
But, ok, these words sounds very sad for most users - i think, there are other ways or users
who take the developers work and can support such devices for a few months. for me it
doesnt matter if users are coming to me and asking how they can develop on my code.
Android should be open source, that means for me there is a community who want to develop
on - and not everybody is a real developer but can learn something, and that can only be reached
with help and understanding each other. Everybody can say "I want Gingerbread on my phone, i want
ICS on my phone, i want a hell kernel on my phone" - but these work cant be developed by google,
its the task for the community, so lets start here and now and stop crying for franco, fserve, mik or
others! Learn to help your self! Be a part of a real community!
I understand what you are trying to say andy, and after reading your post, i must say that i have to agree with you.
As much as I want to start developing myself, I have no idea where to begin. Just a question, which language must I learn to start android development? (is it java or c++? ive seen both languages mentioned but i do not know which one. is there one specific for roms and one specific for kernels? because i think i might give kernel development a try once i learn the appropriate language)
sweetnsour said:
Ah, this thread was short-lived
I understand what you are trying to say andy, and after reading your post, i must say that i have to agree with you.
As much as I want to start developing myself, I have no idea where to begin. Just a question, which language must I learn to start android development? (is it java or c++? ive seen both languages mentioned but i do not know which one. is there one specific for roms and one specific for kernels? because i think i might give kernel development a try once i learn the appropriate language)
Click to expand...
Click to collapse
Developing on android doesnt mean you have to write code by yourself all the time.
Sure, its good to know about C/C++, Java, Shell scripting, makefile reading/writing and other things
but in most time we can copy or integrate existing patches. So, you only know about the bug and
where to fix it with what programming language. For the first time, search for the bug on google
and/or github - with some luck users can find a fix that needs only to copied in the local code.
To start developing on android, its a good choice to understand in details how android is working
and even a good thing is to know about Linux. On windows, you cant develop on Android OS so
you need at least a small Ubuntu/Linux Mint/RedHat or SuSE system with compilers and Java installed.
The next required knowledge is to know how Android is interacting with files:
What is Java for, what is C/C++ for, how Android is booting and what are JNI libraries.
We can open a thread so we can explain something or users can ask for specific things there.
andy572 said:
Developing on android doesnt mean you have to write code by yourself all the time.
Sure, its good to know about C/C++, Java, Shell scripting, makefile reading/writing and other things
but in most time we can copy or integrate existing patches. So, you only know about the bug and
where to fix it with what programming language. For the first time, search for the bug on google
and/or github - with some luck users can find a fix that needs only to copied in the local code.
To start developing on android, its a good choice to understand in details how android is working
and even a good thing is to know about Linux. On windows, you cant develop on Android OS so
you need at least a small Ubuntu/Linux Mint/RedHat or SuSE system with compilers and Java installed.
The next required knowledge is to know how Android is interacting with files:
What is Java for, what is C/C++ for, how Android is booting and what are JNI libraries.
Click to expand...
Click to collapse
Thanks for the info! I will keep this in mind.
andy572 said:
We can open a thread so we can explain something or users can ask for specific things there.
Click to expand...
Click to collapse
good idea (this sounds like sticky material)! would you like to open it? it would not make sense for me to open it since I'm not a developer
First of all i would like to thank andy, mik_os, franciscofranco, fserve, ciaox,knzo, docotornotor and many others who i may have forgotten for their impeccable work towards this community and for working their asses off. You'll are invaluable assets to the community and i could'nt imagine using my phone without you'll.
Reading andy's post i must have to agree with him because you devs have worked so hard towards our phone even though many of you''ll don't own one. Also you bared with the many spams, useless comments on your threads without saying a word. Also many of you have jobs in RL for which you have to work hard, and developing for a phone which you don't even own/primitive phone would seem to you as a waste of time and i can thoroughly understand that. Even though i dunno scat about developing, i do know that it is highly time consuming and resource oriented.
So as you'll probably know that the 2 most irritating bugs on our phone are the touchscreen driver lags, and the axis inversion bugs. Me, as well as thousands of p500 users can't thank franciscofranco and fserve for their dedicated work towards our phone and for developing two awesome kernels which made our p500 superfast. Any p500 user could match his phone's performance to our higher end phones and show its capablities off even though it being a low-ish end phone. I think i am speaking for the thousands of p500 owners all around the world and i would like to take this opportunity to request you kernel developers to fix these bugs and include them in your fanstastic kernels. India itself has the largest number of p500 owners all around the world and this phone is still popular as of today and if you'll didn;t know it is THE BEST SELLING SMARTPHONE phone in India. Therfore tons of us users would love if u fixed these two final bugs as they in my opinion are the biggest performance drainers all credits to ******y LG developers. As sweetnsour said, you devs have every right to decline this request as there is already the paulos kernel and plus you devs have worked your asses off to tweak our phones to its fullest extent and i don't think there may be any more tweaking left to do
However i do believe you devs collaborate in this one final project. Me, as well as every member of this community can't thank you enough for your hard work! We also have many talented devs [ciaox is 13 wtf? ] who can continue development of this phone. Looking at the dev section, many new roms have come up since mik's cm7 port and each rom outperforms the other[no disrespect to mik_os, he started the cm7 era!].
I hope fserve and franciscofranco take this post in regard and work towards fixing these bugs !
Thank you.
ps. sorry for my bad english.
@ andy572
Open ur own website and tell us more! I wanna build my own ROMs but i kinda fail it... With ur small free time? Can u exxplain?? It would be grateful to others!
Sent from my Nexus One using Tapatalk
Uhm... Fserve has already patched his Goldenleaf Kernel with Der_Caveman + Waleedq + Sippolo's workaround to fix axes inversion and cpu spikes.
The related Fserve's kernels are Goldenleaf 111107 and 111108 (I prefer this one). Cheers!
if u didnt know, axis inversion is not possible to fix 100% because it is a hardware issue.........
there is only little you can do about it in the coding part
Yes, I know it's an hardware problem, however a workaround is better than nothing!
Sent from my LG-P500 using XDA App
for me it
doesnt matter if users are coming to me and asking how they can develop on my code.
Android should be open source, that means for me there is a community who want to develop
on - and not everybody is a real developer but can learn something, and that can only be reached
with help and understanding each other. Everybody can say "I want Gingerbread on my phone, i want
ICS on my phone, i want a hell kernel on my phone" - but these work cant be developed by google,
its the task for the community, so lets start here and now and stop crying for franco, fserve, mik or
others! Learn to help your self! Be a part of a real community!
Click to expand...
Click to collapse
well said~
fserve's goldenleaf has added Sippolo's workaround
For me as a user, i would say THANK YOU to you guys for bringing this community alive. Thank you for your hardwork and effort that you put in. I would say that my p500 runs fastest than galaxy s stock 2.3.3. Im not joking as my phone is smooth thanks to you guys. no bugs for most of the roms i tested. I may not be a dev but i understand a lil bit. So once again thank you guys
Sent from my LG-P500 using XDA App
I agree with most of what Andy said, except the part that our phone is obsolete.
I'm not a dev but I found plenty of tutorials available that explained how to successfully compile a kernel from source and extract a .config from an existing kernel. I never found a perfect how to but by meshing various methods together I was eventually successful. After reading francos github commits I discovered the toolchain he was using which was the final ingredient.
From there I used a diff tool to compare franco and Paulos sources, this is how I found the camera flicker fix. When I saw big differences in the source I googled it and/or copied it over then compiled and tested it. It took about 5 tries before I found the flicker fix. This learning process took more than just a couple of hours, it was frustrating but eventually rewarding. I still don't know anything about C or Java, so Andy is right, read/research, copy/paste, trial and error actually works.
Considering that Paulos kernel has resolved these issues and franco hasn't means you should be able to use the same technique. These bugs seem to affect gaming the most, which I don't do, so I haven't had the motivation to look into it.
franco and fserve are more than willing to include fixes. fserve posted a test kernel that included my find within a day. Within a week franco had released a new version that included it.
Open a discussion thread, I think it's a great idea! This is a developers forum after all. Thousands of noobs should be able to combine their efforts to fix these issues. Let's make it happen instead of waiting for it to happen.
Thank You !!!
Suggestion : Why dont Fserve or Franco use and edit Paulo's V6 Kernel'?
is it possible'?
OT.. .
Mistakes are the PORTALS of DISCOVERY .. .
so Cmon.. . Lets commit mistakes
Why don't ask them yourself?
Btw: PaoloM70's 2.6.35.14 V6 Kernel source:
http://www.multiupload.com/18Y712HS9G
so there is no multitouch bug and screen touch lag in paolao kernel?
@sweetnsour . I feel like Ciao X would be a good person to ask about this one. He is young so I feel will continue to work on our p500. I could be wrong. But I also think you could learn much about your goal( which by the way I think it's WONDERFUL you want to learn to develope ) I KNOW I'm not cut out for it, and so I can be honest while I am no actually HELP to this community when it comes to developing. I AM. A HUGE fan, supporter and appreciate of all the passion and art and great works that come out of this wonderful community!!! Anyway, I digress CIAO CAN YOU WEIGH IN ON THIS???
Optimus T
OpenOptimus (froyo)
latest franco kernal
748/480
Interactive X
Jonny Green
"im not a Dev but I flash alot"
TL;DR
If you want to help me, post on MY thread about my kernel bugs. --REALLY--
(or dev something, lol)
(or donate me, i really love that )
FOR NOW, i need people to tell me which is the WORST game to play on p500 using gbs v19 kernel, AND it need to be free (or not if you give me the money).
So i can test this touchscreen bug.
Please, post, on my thread for .32 kernels and on franco thread for .35 kernel.
Thanks
fserve said:
TL;DR
If you want to help me, post on MY thread about my kernel bugs. --REALLY--
(or dev something, lol)
(or donate me, i really love that )
FOR NOW, i need people to tell me which is the WORST game to play on p500 using gbs v19 kernel, AND it need to be free (or not if you give me the money).
So i can test this touchscreen bug.
Please, post, on my thread for .32 kernels and on franco thread for .35 kernel.
Thanks
Click to expand...
Click to collapse
Thanks for weighing in! There are two apps you can try using:
For a game, try playing glow hockey (use the two player mode). When your fingers cross, you will be controlling the opposite puck.
To see what is really going on, check out the app "multitouch vis test". You will see the bug when you cross your finger either horizontally or vertically.
Sent from my LG-P509 using xda premium
EDIT: I was talking about the axis inversion bug, not the CPU lag bug. Not sure what the worst free game for that would be, but neocore would be good for testing this bug.
Before I start, I need to pay my respects to the developers for all the great effort trying to make our ACES one hell of a phone.
Ok, if we were to sum it up as far as cyanogenmod development goes for the Samsung Galaxy Ace we have the following:
1. BehradGH Rom stable but some bugs or apps that don't work. A bit heavier than the following
2. Grif_07 Rom which appears to be the most stable
3. CM7.2 BY J.A.F which is developed by Russians who made a very good job and this one seems to be the fastest so far and very stable. This based on Grif_07 if I am not wrong. A thread started for this one, I believe this one has minor bugs cause I am testing it.
...And of course lots of others that diserve recognition
So if there's going to be an official version on which version is going to be based on and who's deciding for that? How's the whole thing going? Cause as far as I can see we get new roms probably from different working groups quite often but what's the point if they all choose their own path? I mean someone should decide the path so all the developers can work it out and reach the destination --> The Official version of Cyanogen for Ace. I would appreciate and I believe not only me but a whole lotta bunch of people if we were told what's the plan. Just a few words.
I see many great ideas in here, for example jusada took the first two roms and modified them to barebones. Really nice move and quite impressive roms, fast and quite stable but again not bug free (oh man, why you stopped dealing with this???).
Anyway, a few words from the right people would be great. I love cyanogen and I would go donate if we ever get an official rom. Thanks!
Belongs to the general subforum.
The 3 roms has problem with Facebook login on 3rd party programs Like IM+ , Meebo, etc, the only way for me to get facebook chat on a third party was making a meebo account and adding all my accounts into my meebo account and then loging in with my meebo account on the meebo app for android rofl. also CM7.2 BY J.A.F has problem after flashing gapps and everytime my device start it force close gmail and doesn´t connect to Google server to add my google account in the device.
itasoulas said:
Before I start, I need to pay my respects to the developers for all the great effort trying to make our ACES one hell of a phone.
Ok, if we were to sum it up as far as cyanogenmod development goes for the Samsung Galaxy Ace we have the following:
1. BehradGH Rom stable but some bugs or apps that don't work. A bit heavier than the following
2. Grif_07 Rom which appears to be the most stable
3. CM7.2 BY J.A.F which is developed by Russians who made a very good job and this one seems to be the fastest so far and very stable. This based on Grif_07 if I am not wrong. A thread started for this one, I believe this one has minor bugs cause I am testing it.
...And of course lots of others that diserve recognition
So if there's going to be an official version on which version is going to be based on and who's deciding for that? How's the whole thing going? Cause as far as I can see we get new roms probably from different working groups quite often but what's the point if they all choose their own path? I mean someone should decide the path so all the developers can work it out and reach the destination --> The Official version of Cyanogen for Ace. I would appreciate and I believe not only me but a whole lotta bunch of people if we were told what's the plan. Just a few words.
I see many great ideas in here, for example jusada took the first two roms and modified them to barebones. Really nice move and quite impressive roms, fast and quite stable but again not bug free (oh man, why you stopped dealing with this???).
Anyway, a few words from the right people would be great. I love cyanogen and I would go donate if we ever get an official rom. Thanks!
Click to expand...
Click to collapse
Yeah, I understand what you're saying. All the devs work on one beast godlike rom. That would be pretty epic.
itasoulas said:
So if there's going to be an official version on which version is going to be based on and who's deciding for that? How's the whole thing going? Cause as far as I can see we get new roms probably from different working groups quite often but what's the point if they all choose their own path? I mean someone should decide the path so all the developers can work it out and reach the destination --> The Official version of Cyanogen for Ace. I would appreciate and I believe not only me but a whole lotta bunch of people if we were told what's the plan. Just a few words.
Click to expand...
Click to collapse
The Official CyanogenMod for Ace would be developed by official CyanogenMod developers, AFAIK (CMIIW). It wouldn't be based on either because the CM developers would use their own source code (if I'm not mistaken, Behrad's CM7 port was taken from Galaxy Mini's CM7 port, and only recently has it been identified as device "cooper").
I agree that things might be better if all those wicked devs worked together to get one demigod ROM, but we like variety. For me, between one universal ROM and hundreds of specialty ROMs, I'd choose the latter.
kurama72 said:
The 3 roms has problem with Facebook login on 3rd party programs Like IM+ , Meebo, etc, the only way for me to get facebook chat on a third party was making a meebo account and adding all my accounts into my meebo account and then loging in with my meebo account on the meebo app for android rofl. also CM7.2 BY J.A.F has problem after flashing gapps and everytime my device start it force close gmail and doesn´t connect to Google server to add my google account in the device.
Click to expand...
Click to collapse
For the gapps problem in 7.2 i think you have to reflash the rom and this time not flash the ICS theme + animation. I believe that is what causes the apps to crash.
I think we should unite efforts on this cause. Couple of weeks back, I tried to move the crowd a little by making a campaign. Then we received a notice saying that CM7 was coming to our SGA.
ALL DEVELOPERS STOPPED WORKING ON ANY CM7 PORT.
I suggested to keep up working on the roms, since we don't have the certainty that the port is coming for real, which it seems (now) really farfetched. What I'm trying to say is that maybe if kept our noses to the ground and continue developing ONE HUGE MASSIVE CM7 port, then we may finally caught up some attention.
adeklipse said:
The Official CyanogenMod for Ace would be developed by official CyanogenMod developers, AFAIK (CMIIW). It wouldn't be based on either because the CM developers would use their own source code (if I'm not mistaken, Behrad's CM7 port was taken from Galaxy Mini's CM7 port, and only recently has it been identified as device "cooper").
I agree that things might be better if all those wicked devs worked together to get one demigod ROM, but we like variety. For me, between one universal ROM and hundreds of specialty ROMs, I'd choose the latter.
Click to expand...
Click to collapse
I see, so every rom in here won't have anything to do with the official version that is if we ever get one....why then the CM7.1 Cooper is stated as UNOFFICIAL? And if it gets OFFICIAL again it won't be the real official cyanogen, is that what you're saying?
itasoulas said:
why then the CM7.1 Cooper is stated as UNOFFICIAL?
Click to expand...
Click to collapse
I believe it's UNOFFICIAL because it's not developed by CyanogenMod developers (Team Douche or related).
itasoulas said:
And if it gets OFFICIAL again it won't be the real official cyanogen, is that what you're saying?
Click to expand...
Click to collapse
If I'm not mistaken, unofficial ports of CM are called KANGs. Behrad's CM7 port (according to that definition) is also a KANG build.
If CyanogenMod developers roll out official support for the galaxy ace (as "cooper"), then that CM7 build would be official.
*did I understand & answer your question correctly?
As always, CMIIW. I'm no expert, I'm no developer, I'm just an extremely happy user.