Hi all,
say that I'd like to try a CM7 custom compilation (e.g., removes half of packages, ...) for the sake of learning, what steps do you suggest to get into?
Compiling a full debuggable ROM and test it in the Android emulator?
Could I test It along with SE kernel (e.g., with the latest)?
In the emulator should i to install the SE related packages in order to set up the Xperia HW emulation?
Cheers!
There's a package of scripts named kitchen, made of a member here that let you customize a rom. There is even a root method that we were talking about the other day.
https://github.com/dsixda/Android-Kitchen
Hi kissmyarch,
i meant bulid It from the sources, not through the kitchen way ;-)
Oook sorry then.
LoL take a rom add ur theme, choose ur fav apps! Choose ur modules! And ur done! Custom rom is ready!
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
LoL nevermind then! This is what happening lately on mini pro forums, I just revealed how its being done!
Ravencz said:
You know, I don't think people (including me) want to make a "repack" of an existing ROM, but build their own from sources instead, galvic
Click to expand...
Click to collapse
I agree with Ravencz, building from sources is more funny than cooking... the fact is that you find a tutorial on cooking in the forum (and it's simplistic as hell) and no an hint on how to port your own CyanogenMod on your mini pro... what a pity...
Hoping someone on the devs' side will read this post ;-D... Cheers!
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
galvic said:
First of all cyanogenmod is already a cooked rom! If u want to port cyanogenmod u've to open it and then make it compatible for mini pro and repack it!
But you dont want that so rename the thread how to create custom gingerbread rom!
then use Sources from AOSP rom! Then repack 'em! Thats how its done, kitchen just provides an enviorenment for this!
Click to expand...
Click to collapse
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
@galvic: CM doesn't seem a cooked ROM to me, since they provide the repository from which you could clone the sources. CM seems more a fork (with enrichments/improvements) of AOSP and cooking a CM isn't the same of building its source.
So the thread is correct, because if i fetch and edit the Gingerbread branch of CM source, actually i've built a custom CM7.
Instead of linking those megabytes of ROMs, shouldn't be better working on CM's branch and attach the related patches that brought to a custom CM ROMs, as patches for kernel modules and so on? Benefits of patches are small downloads size, learning what people do in making your beloved ROM, ... On the other side you've to set up a developer's environment, that is a bit expensive (Gingerbread sources are around 7 Gigabytes, if i'm not wrong).
I don't know if Gingerbread is the best choice with the unchangeable kernel that SE stuck on our smartphone, but say Gingerbread or Froyo or whatever the fix you've to make on a CM are (logically) the same until someone will make an hackish strike and take down that damned bootloader.
See you!
Ravencz said:
I'm sorry, but that's not completely true. CyanogenMod has it's sources as well. Sure, you can download a clean build from their website, but you can also build CM on your own.
Click to expand...
Click to collapse
Sorry but CM is also bult on sources of AOSP
galvic said:
Sorry but CM is also bult on sources of AOSP
Click to expand...
Click to collapse
Of course it is, but it's modified
Ravencz said:
Of course it is, but it's modified
Click to expand...
Click to collapse
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
thats what free-xperia project did, use miniCM resources!
galvic said:
So we should also modify them exclusively for mini pro, then it'll be called a perfect ROM?
Click to expand...
Click to collapse
Nope, compiling gives you control over things such as source code, compiling options/flags for optimization (say that our mini pros have ARMv6 processor, why having a ROM built for generic ARM architecture? It doesn't make any sense... that's the source-oriented GNU/Linux distro way as Gentoo: compiling kernel and all application for your machine in order to have best performances and responses), possibility of adding removing code (e.g. libraries, system applications) and so on.
Cooking let's you modify something pre-made and doesn't give you *full* control on it ;-)
If we've to take over the world, we've to do it in the proper way! :-D
Cheers
Related
can i install CM6 on any rom so it can be an unofficial CM based rom? like the custom apk apps that CM has on any ROM
XxSilent.NightmarexX said:
can i install CM6 on any rom so it can be an unofficial CM based rom? like the custom apk apps that CM has on any ROM
Click to expand...
Click to collapse
CM6 is a Froyo rom and the only roms we have that are froyo are either CM or CM based or with CM stuff already in them. As far as adding them to Eclair roms I'm not sure if they would work, but feel free to test and tune
refthemc said:
CM6 is a Froyo rom and the only roms we have that are froyo are either CM or CM based or with CM stuff already in them. As far as adding them to Eclair roms I'm not sure if they would work, but feel free to test and tune
Click to expand...
Click to collapse
how bout cm5
Is it possible to take the latest CyanogenMod Settings and put it on Froyo Rom so that I can have all the features (I have the Elelinux special edition) like Battery percentage in the Topbar or customizing the colors, integrated SetCPU and so on?
Edit: This is for hero, but I figured, I do not need to open a separate Topic as its essentially the same question.
SchinTeth said:
Is it possible to take the latest CyanogenMod Settings and put it on Froyo Rom so that I can have all the features (I have the Elelinux special edition) like Battery percentage in the Topbar or customizing the colors, integrated SetCPU and so on?
Edit: This is for hero, but I figured, I do not need to open a separate Topic as its essentially the same question.
Click to expand...
Click to collapse
I doubt it, but if you try it before anyone else does, you can let us know if it works or doesn't.
This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Added splboot.ko compiled with X10 mini pro kernel sources (same config as zImage) , address 0x00200000
Also included a nice sh for insmodding, and dmesg modules.
SPLBOOT MODDED SOURCES ON MY APPORTS INDEX!
Original sources can be found on FreeXperia git, and ARMv6 by nAa at X8 bootloader bypass thread
Thanks to nobodyAtall for porting splboot to ARMv6. Thanks to aZuZu and doixanh for helping and side tips.
D4rKn3sSyS said:
This is a dev thread, and only for developers, please avoid of posting UNUSEFUL things. Thanks
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.g z sources, built with semc_mimmi_defconfig. I would recommend to devs to go here, seems like it's more active that old threads.
Thanks to aZuZu and doixanh for helping me compiling.
Click to expand...
Click to collapse
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
Just read the wikipedia article on zImage. Here.
wikipedia said:
The filename of the bootable image is not important, but by convention it is called vmlinuz or zImage.
Click to expand...
Click to collapse
can you make bzImage? 2.3 Mb is to big for download... Thanks! Nice work!
Any progress on bootloader bypass?
PTGamer said:
it seems to be great news! but what is zImage for? how can it improve the Custom roms?
Click to expand...
Click to collapse
This is a dev thread, why it's supposed that this is related with custom roms?. zImage it's kernel executable (compressed btw).
Uploaded splboot.ko module, seems working well, if you are gonna try, be sure that you chmod to 777.
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Snoopo said:
For development & testing you can use chmod 777 but never forget to set permissions correctly before releasing something!
Click to expand...
Click to collapse
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
D4rKn3sSyS said:
I'm sorry, don't get your point. If i get you ok then you mean that I need to chmod +x or 777 on linux, before publishing some?... then why people can use on windows, and then release?? (Yes windows simply damages permissions)
You just need to chmod on phone (or use unyaffs.. chmod sounds easier)
Click to expand...
Click to collapse
i think he mean you can use chmod 777 while For development & testing
but set correct permissions before releasing
mean dont keep 777 but correct it if 777 not needed
(+x or what ever i dont know more permissions type lol )
heh yeah... Maybe it's my linux administration thinking:
Permission 777 is bad ^^
You should better find out which user or group shall have execute ,rewad or write-rights and then set the correct permission...
for example:
chown 0:2000 /foo
chmod 750 /foo
you see? Okay on a mobile it's really not that important but think of that there is someone who writes a bad app that exploits just a permission of CM7 or CM6 that is used in every phone... and woops ^^ or whatever ^^
D4rKn3sSyS said:
Guys, there you go, this is zImage compiled with x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz sources, built with semc_mimmi_defconfig.
Click to expand...
Click to collapse
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
What's splboot module for? Does anybody try to kexec-tool way?
Cheers,
ff0000.it
... I almost forget: this is the best thread on the forum, thanks D4! ;-D
ff0000.it said:
Hi D4rKn3sSyS (toughest nickname to write :-D),
Where do you get the sources? From SE developers' site?
Click to expand...
Click to collapse
Yes... i think.
ff0000.it said:
What's that kernel version? If it's to 2.6.29, it should be patched to reach 2.6.32, am i wrong?
Click to expand...
Click to collapse
no... more source required.
ff0000.it said:
What's splboot module for? Does anybody try to kexec-tool way?
Click to expand...
Click to collapse
bootloader bypass.
Or at least, i think i'm right.
OmegaRED^ said:
Yes... i think.
no... more source required.
bootloader bypass.
Or at least, i think i'm right.
Click to expand...
Click to collapse
Right, s.e site, right, and right
OmegaRED^ said:
no... more source required.
Click to expand...
Click to collapse
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
OmegaRED^ said:
bootloader bypass.
Click to expand...
Click to collapse
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
ff0000.it said:
Not such a big answer , i downloaded the sources from SE and it's a 2.6.29 kernel release as the one actually found in SE roms... now suppose i'd like to build a custom Android ROM based on Gingerbread branch that comes with kernel 2.6.35, it should be a good thing patch the kernel in order to take the SE one up to 2.6.35, isn't it?
To do that i think we've to take the Android kernel source git clone, extract all the patches from 2.6.29 to 2.6.35 (dealing with a single patch is harder than a small set of patches) and apply one by one crossing our fingers and hoping SE doesn't make so much modifications to the base parts of the kernel.
If we succeed we could maintain a custom kernel through patches.
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flash-able via Xrecovery
It's hard to isolate what to patch... consider that the big x10 threads have been messing with modified kernels for quite some time now..
Ip-tables, (CPU undervolt, overvolt and overclock) and many other mods directly implemented into the kernels.
And even so they are still stuck on the same kernel version.
SE has not even upgraded the kernel version with the 2.3.3 update.
So it may be possible but it makes alot of work for new drivers...ect..
It's best to try and optimize the current version and already working source instead of creating a whole new ball game.
OmegaRED^ said:
It's simple enough to flash using Xrecovery or CMW.
The x10 forums made almost everything flashable via Xrecovery
Click to expand...
Click to collapse
I think you don't get my point... i was saying (from my point of view) that a kernel upgrading is mandatory (or it should be)...
It's the same if i have a Linux 2.4.x kernel with a GNU distribution that relies on mechanism such as sysfs that isn't supported in 2.4.x kernels (>= 2.6.x); so to build a custom Gingerbread ROM it's a good choice having a related kernel (from wikipedia it's 2.6.35).
And what's within Xrecovery and CWM? Flashing differs from building...
Saying that i don't want bluetooth or GPS or wifi support in my ROM, disable it from kernel and ROM building... that's the benefit of having custom kernels and ROMS.
Still i don't understand why you answer me with Xrecovery and CWM
Please don't miss under stand.
All i am saying is that without source it becomes hard.
SE did not upgrade the kernel to 35 for the big x10 or the x8 so there is very little to work with.
It would be awesome to get the kernel to that level.
But it's easier to rather tweak the kernel we currently have.
ff0000.it said:
If the meaning of bootloader bypassing is only to load a custom kernel, what if kexec-tool works? Isn't it a simple way to deal with a custom kernel? I never use it but it sounds easier...
Click to expand...
Click to collapse
^^^
This is why i commented on CWM and Xrecovery.
Afair there are even custom kernels but they are not really stable and discontinued.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
What are you talking about?, we haven't already bypassed bootloader.
s0ftcorn said:
Afair there are even custom kernels but they are not really stable and discontinued.
Click to expand...
Click to collapse
The point is not the stability or the instability of a custom kernel, it's to have the chance of building a custom one...
It's my right to have a unstable custom kernel builded by me installed on my phone, isn't it? :-D
@D4: i'm going to learn more about "git" and then i'll try (in the spare time) to patch SE kernel up to 2.6.35 (with all git tags/branches) and the i'll upload it to github... no promise at all, by i'll try ;-D
D4rKn3sSyS said:
What are you talking about?, we haven't already bypassed bootloader.
Click to expand...
Click to collapse
Yeah my bad. Have read the custom kernel stuff while i was completely new to smartphones. The X10 has custom kernels, but theire development is afair discontinued.
Sorry for the irritation.
Hi all,
i would like to know what is so special about this ROM in this thread
http://forum.xda-developers.com/showthread.php?t=1212949
Because we all are using cm7 modded roms and cm6, what is so special about it? just wondering since the day that thread came into existence. Thats all.
Thank you
Tim
do you know the different already
I don't understand it either but I think that:
X10 mini is not supported officialy by CM6 or CM7 but we need to use port like miniCM6 to make it work.
If you look at the official webpage, there is no SE phone supported http://www.cyanogenmod.com/devices
So I think this new project is to build a CM7 Rom for the Xperia line which may be more stable and more complete than other custom ROM. Moreover I think that SE developpers are gonna help in this project by giving some code for special hardware.
(Look at this http://blogs.sonyericsson.com/wp/2011/09/28/sony-ericsson-supports-independent-developers/)
If someone know more about this, it would be interesting!!!
The general idea is, that every bit of software on the phone should be open source, i.e. Free for everyone.
The driver layer of stock firmware is not open source, therefore you either have to adapt your operating system to work with standard drivers in kernel (what most developers/chefs do) or build drivers from the ground up (which is what FXP team is doing).
Then you have a completely open system with source code available for everyone.
Sent from my U20i using xda premium
pfonck said:
The general idea is, that every bit of software on the phone should be open source, i.e. Free for everyone.
The driver layer of stock firmware is not open source, therefore you either have to adapt your operating system to work with standard drivers in kernel (what most developers/chefs do) or build drivers from the ground up (which is what FXP team is doing).
Then you have a completely open system with source code available for everyone.
Sent from my U20i using xda premium
Click to expand...
Click to collapse
FreeXperiaProjekt
all is FREE for the XPERIAS thats our PROJEKT
flex96 said:
FreeXperiaProjekt
all is FREE for the XPERIAS thats our PROJEKT
Click to expand...
Click to collapse
You can read that in many ways...
Sent from my U20i using xda premium
Thanks all! i didnt know all would be such interested in that.
But well, i guess that this project will be better because it is started from the base.
I use a x10 mini pro (2010) and cant use the stock rom, because im too fond of the gingerbread roms out here. all are special in some way. and im testing each one specifically. if i use the stock rom i miss out some features i like and do upgrade.
So i wondered, if this FXP is something different, like pfonck said, build from ground up, then it would work according to our needs. very good and i like it.
Keep it up devs (i mean, FXP team!).
regards,
Tim
If you know what is inside the source code of everything, all the way from bootloader to app it's much easier to bugfix... So all in all they should be able to create an up to date rom that rivals the old stock rom for stability.
Sent from my U20i using xda premium
thanks pfonck for the info. you are right. since we are porting the roms from something sles we dont get the "real deal" out of a gingerbread rom or froyobread rom. that speaks well because it is from the base.
hope soon everyone will jump to it
Thanks
regards
Tim
I think what will be special about this ROM is that it won't be special! It'll be a 'vanilla' CM7 which will be open source and made specifically for each device. I imagine it will, with regular bugfixing, become the most stable custon ROM, and I envisage that it'll be the basis for most other Mini Pro custom ROMs.
It won't be anything revolutionary that we haven't seen from other ported gingerbread ROM's, in fact it'll probably have less features. People may still prefer a port of GingerDX which has the GingerDX settings. Or MiniCM Pro with its Xloud and Bravia engine. But for those who want a pure CM7 experience from developers who now have access and help from Sony Ericsson to use official drivers, it should turn out great. (and also, no developers names written on the lockscreen)
Ok... i'm not new here, but Android has changed a lot since last time i used it. I see many new things here, and i tried looking other threads but still have some confusions.
1. I know AOSP is the original source, and AOKP is the modified one, but can someone still tell me what's the difference? what what in the hell do they modify, and why do they need to modify, i guess the original ROM is better than the Kang.
2. Is CM a AOKP ?
3. Which one is better AOSP or AOKP?
4. What is a Kerenel ?
5. If i flash my phone with a ROM, what happenes to my Beats Audio ? If its gone, can i get the app from somewhere, cause its there in the gplay.
Manish54 said:
Ok... i'm not new here, but Android has changed a lot since last time i used it. I see many new things here, and i tried looking other threads but still have some confusions.
1. I know AOSP is the original source, and AOKP is the modified one, but can someone still tell me what's the difference? what what in the hell do they modify, and why do they need to modify, i guess the original ROM is better than the Kang.
2. Is CM a AOKP ?
3. Which one is better AOSP or AOKP?
4. What is a Kerenel ?
5. If i flash my phone with a ROM, what happenes to my Beats Audio ? If its gone, can i get the app from somewhere, cause its there in the gplay.
Click to expand...
Click to collapse
1) http://aokp.co/about/
2) CM is CM and AOKP is AOKP
3) test it!
4) Kernel! http://en.wikipedia.org/wiki/Linux_kernel
5) Lloir includes a modified DSPManager with Beats sources
skdubg said:
1) http://aokp.co/about/
2) CM is CM and AOKP is AOKP
3) test it!
4) Kernel! http://en.wikipedia.org/wiki/Linux_kernel
5) Lloir includes a modified DSPManager with Beats sources
Click to expand...
Click to collapse
Ok, now i get it... AOKP is a custom ROM based on AOSP, just like CM.
Thanks, it helped
Manish54 said:
Ok, now i get it... AOKP is a custom ROM based on AOSP, just like CM.
Thanks, it helped
Click to expand...
Click to collapse
All roms have to be based on source, otherwise it's not android, it's just another mobile OS running on linux.
Kernels are not new, every OS has a kernel, GNU/Windows/OSX. A kernel is used for communication between the device at a H/W level and the software.
Sent from my HTC One X+ using Tapatalk 2
Hey xperia x8 users and devs,
I try to build a clean CM 10.1 on my PC
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on xperia x8 with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on xperia x8 working like cam, camcorder, Bluetooth, GPS, WIFI , SD-CARD.
afi1982 said:
Hey xperia x8 users and devs,
I try to build a clean CM 10.1 on my PC
The CM 7/9/10 development thread seems a bit overloaded and I want to collect all neccessary facts, when I try to build CM 10.1.
What will be needed here?
- Manifest files for build a clean repository (which devicetree, display libs ...)
- Which patches were used?
- Kernel configs and additional kernel driver
What will be the aim?
- Get a functional CM 10.1 on xperia x8 with most of the hardware features
Builds for testing pruposes will be posted here in this dev thread.
This thread is aimed for development purposes not for whishes like "Can you make feature xyz working?". It is the main task to get most of the things on xperia x8 working like cam, camcorder, Bluetooth, GPS, WIFI , SD-CARD.
Click to expand...
Click to collapse
Some time ago, was trying to port the 2.6.39 kernel from ZTE for android 4.2
Compiled but could not boot, and t MSM shakira/delta board fully ported into kernel
something was missing.
and to make a compilation of 4.2.2 need legacy libraries for old binaries
and build using miniphone and not fullphone in the configs.
u can read from here
https://github.com/androidarmv6
rom boot, but need more power into kernel
So now that you have done?
i'm compiling jb 4.2.2 right now and i have so many error's , but i managed to fix most of them so let's hope.
I don´t know but if this can help you: http://forum.xda-developers.com/showthread.php?t=2453085
Bro i thinnk need kernel 3.8 or kernel 3.4 for running JB 4.2.2 ?
SatrioDwiPrabowo said:
Bro i thinnk need kernel 3.8 or kernel 3.4 for running JB 4.2.2 ?
Click to expand...
Click to collapse
I have it up and running on 2.6 except the WiFi and storage.
@TeamMex do you have the shakira/delta board files from your try to port the ZTE kernel ?
afi1982 said:
I have it up and running on 2.6 except the WiFi and storage.
Click to expand...
Click to collapse
That's very interesting news! Well done!
I hope you resolve those issues and release something for us!:fingers-crossed:
afi1982 said:
I have it up and running on 2.6 except the WiFi and storage.
Click to expand...
Click to collapse
So first whats u plan bro ?
SatrioDwiPrabowo said:
So first whats u plan bro ?
Click to expand...
Click to collapse
first i'm working on a new kernel 2.6.35 , then I will focus on the ROM .
good luck with the work of the cm10.1 for xperia x8
afi1982 said:
first i'm working on a new kernel 2.6.35 , then I will focus on the ROM .
Click to expand...
Click to collapse
Greats bro I hope you win ported CM10.1 for shakira keep high spirit
Send from My Xperia X8 with Xperia J
i may release a pre-alpha build for you guys to test, but keep in mind that not everything works!!!
afi1982: I understand that not everything works as it is the first version, and from so that everything works can not be done for the first time.
I keep my fingers crossed for her work on this project
Greats master I wait and if you need help pm me maybe I can solved oke bro
Send from My Xperia X8 with Xperia J
as they go to work on CM 10 for Xperia X8 ?
guys this is DEV thread and not thank you or general discussion thread .
While we can't see any real contents (source, device config or prebuilt rom for testing) this project is THEORETICAL only, and we can't do more than talking about the NOTHING...
Without any concrete things nobody can help.
pilu1978 said:
While we can't see any real contents (source, device config or prebuilt rom for testing) this project is THEORETICAL only, and we can't do more than talking about the NOTHING...
Without any concrete things nobody can help.
Click to expand...
Click to collapse
go there and see if you can help with something ..
https://github.com/androidarmv6
I saw this project earlier, and Daveee10 opened a discussion about the 4.2 development (it was in the last year).
But you have a working version, why NOT post is?
The users can post feedback, and more member will be join, if they can test it.
As I wrote earlier in pm, I'm not interested in the cm10+ development, especially if need to start it from zero. But I think more easy to make a group what working on one project, if the possible members NOT need to start everything from the beginning.
EDIT: this is not offense, just a suggestion.