As we all know that CM roms the CM team make it ... it already has many bugs so while we build it for our devices we just get new bugs so why don't we start building rom from android source that google shared it this source it already hasn't any bugs like CM so it will be better to start into building roms...""YOU MUST KNOW THAT YOUR DEVICE GALAXY STAR HASN'T ANY SUPPORT ANY MORE FORM SAMSUNG "" ...
/**********************************************\
THE MOST IMPORTANT THING ::RGANIZATION:::
we must organize our self to know what are going to do .... and devide working ... some developers work on kernel and others do other works and testers and we comunicate with each others ....:angel::angel::angel:
/***********************************************\
and a cups of tea and bring your BRAIN ....
if you have any advice plz write it here
LahKeda said:
As we all know that CM roms the CM team make it ... it already has many bugs so while we build it for our devices we just get new bugs so why don't we start building rom from android source that google shared it this source it already hasn't any bugs like CM so it will be better to start into building roms...""YOU MUST KNOW THAT YOUR DEVICE GALAXY STAR HASN'T ANY SUPPORT ANY MORE FORM SAMSUNG "" ...
/**********************************************\
THE MOST IMPORTANT THING ::RGANIZATION:::
we must organize our self to know what are going to do .... and devide working ... some developers work on kernel and others do other works and testers and we comunicate with each others ....:angel::angel::angel:
/***********************************************\
and a cups of tea and bring your BRAIN ....
if you have any advice plz write it here
Click to expand...
Click to collapse
That is if we had devs
The source has to be proper if we or any1 has to do something.
nice advise
nice advise man :good:
Related
So i saw that in other devices fourms they ported the Sense 4.0 multitasking screen. But it's not working for all devices or builds.
So a dev/ or user has to port the code to our builds . I myself don't have the time to port it but i am looking forward to seeing this on out beloved device.
Here's the source thread. http://forum.xda-developers.com/showthread.php?t=1589963
Deonix said:
So i saw that in other devices fourms they ported the Sense 4.0 multitasking screen. But it's not working for all devices or builds.
So a dev/ or user has to port the code to our builds . I myself don't have the time to port it but i am looking forward to seeing this on out beloved device.
Here's the source thread. http://forum.xda-developers.com/showthread.php?t=1589963
Click to expand...
Click to collapse
It's quite easy I have this running now on my defy ...... U need to source code to apply no porting necessary
I will help you make one for yourself after my exams are done
There's already a thread that has a flashable zip that works for older nightlys.
it may look neat but it hardly promotes multitasking that the inbuilt ics carousel provides...you can barely see the next two open apps using the sense "multitasker"
Kayant said:
It's quite easy I have this running now on my defy ...... U need to source code to apply no porting necessary
I will help you make one for yourself after my exams are done
Click to expand...
Click to collapse
Thanks. I have exams as well ) i will try to port it. If i stumble i will let you know. Maybe i will like it.
Good luck on your exams.
Hello there guys,
As we all know we only have 3? 4? developers for the HOX+ . And they are really doing all they can to help keep the phone upto date.
But as we all know they are all busy and can't update their roms that much any longer.
EDIT: Lloir already has a guide : http://forum.xda-developers.com/showthread.php?t=2187266 but I don't think he covers how to fix camera and gps and stuff
So! Is it possible to make guide on how to compile the rom from the source? I know tombridden and lloir already made a one post guide on how to build some roms but it was too specific.
I now have an extra machine (a laptop) with 500gb free storage and ubuntu as the main OS. It's quite powerful too with 6gb RAM and i7. So Why not use it to help the community while others are busy? In the meantime I will look around for some guides for other phones but I don't think they will help that much.
And please include the answers to those questions if you make a guide:
1- What to do to fix camera/GPS/wifi/Data/sensors ?
2- What approach should I take when compiling a new ROM. For example: there are no developers for PACMAN , how will it differ during compiling between it and AOKP/CM/AOSP .
I am talking about a rom that wasn't approached by Lloir so he won't have the repos for them. What to do then?
Thanks a lot and I can't wait to help
@Lloir @tombriden @PippoX3 @mike1986. and any other developer out there.
you can start by looking at XDA-University
The reply is correct. All of us moved first steps studying at XDA University.
Anyway the case is more complex than others.
For this device there are really few developers. Other device have a lot of support from constructors, many dev and the team-work result in a lot of kernels/roms to flash for the final user.
If you wanna taste the happyness for build a rom, I'll send you a guide to setup your ubuntu, download the sources and build.
But in this case, where enrc2b is not officially support, the things are more difficult.
You must have a minimal practical with java, cpp, android and kernel code (if so).
For the moment I'm in trouble to build an AOKP 4.2.2 with new kernel. I haven't device to try, 'cause the hard is build&&try continuosly.
Not the fact to have a pc turned on for hours and hours.... and the eyes&&mind open for hours and hours... but the patience to continuously try time after time.
Now I am in a dead point... many users like have S2W enable on new CM kernel... but.... the kernel won't!
Thanks a lot anyway. Thanks to @Lloir, @tombriden, @maxwen and alls who's workin' for this device.
Stay tuned....
PippoX3 said:
The reply is correct. All of us moved first steps studying at XDA University.
Anyway the case is more complex than others.
For this device there are really few developers. Other device have a lot of support from constructors, many dev and the team-work result in a lot of kernels/roms to flash for the final user.
If you wanna taste the happyness for build a rom, I'll send you a guide to setup your ubuntu, download the sources and build.
But in this case, where enrc2b is not officially support, the things are more difficult.
You must have a minimal practical with java, cpp, android and kernel code (if so).
For the moment I'm in trouble to build an AOKP 4.2.2 with new kernel. I haven't device to try, 'cause the hard is build&&try continuosly.
Not the fact to have a pc turned on for hours and hours.... and the eyes&&mind open for hours and hours... but the patience to continuously try time after time.
Now I am in a dead point... many users like have S2W enable on new CM kernel... but.... the kernel won't!
Thanks a lot anyway. Thanks to @Lloir, @tombriden, @maxwen and alls who's workin' for this device.
Stay tuned....
Click to expand...
Click to collapse
That's what i did already. I set up the periphals/kernel/device info GITs and now i am looking for the roms, I found CM and stuff but I can't find PURE AOSP , does that mean i must download it and upload it?
I also have Oracle java installed. Do I have to have open JDK?
Ghand0ur said:
That's what i did already. I set up the periphals/kernel/device info GITs and now i am looking for the roms, I found CM and stuff but I can't find PURE AOSP , does that mean i must download it and upload it?
I also have Oracle java installed. Do I have to have open JDK?
Click to expand...
Click to collapse
https://github.com/pure-aosp/android
Lloir said:
https://github.com/pure-aosp/android
Click to expand...
Click to collapse
Now that we begin to have a solid CM base, will possible to build at least CM for enrc2b for noobs too.
And eventually "port" device/kernel" parts to others platforms. So who like e.g. PA can do...
If you agree, I can paste my personal appoints to a guide, from client setup (Sun java don't works) to the build zip rom.
Updated and corrected to last KK.
PippoX3 said:
Now that we begin to have a solid CM base, will possible to build at least CM for enrc2b for noobs too.
And eventually "port" device/kernel" parts to others platforms. So who like e.g. PA can do...
If you agree, I can paste my personal appoints to a guide, from client setup (Sun java don't works) updated and corrected to last KK.
Click to expand...
Click to collapse
Go for it. Saves me doing it which I was about to do
Sent from my One X+ using Tapatalk
Hello ,
After 3 years of development different roms from all versions ( from android 2.3 and up ) , in the last days , developers turned to work on the latest android version ( 4.4 kitkat ) and leaving the older ones , they are right anyways newer is better of caurse , actually all development section is filled up with 10 active threads of kitkat roms and one or two of ics .
Well , that's not the problem , the problem is that there are 10 threads means 10 devs who are working on their ported roms , yes , but they are all based on Mike's "infinished" cm11 . And because Mike is working alone on it , development is slow , and as a result the other's one will be slow as well , and that's the case from the begining !
My point is , developers who are wishing to base their work on a "infinished" one , they should first help in finishing it as quick as possible then they do what ever they want ,there are great devs out there , I mean why they don't try to make a team and work together on big processes like porting a propre cm11 or like what you have done with nAa and 3.4 kernel ? that will help a lot the devs and the community , and Mike has always said "On the i9001, 8 devs work on 1 device, while on our side, 1 dev works on 8 devices" about how cm11 development goes with other devices .
If you agree with me make your move and form your team to do things faster !
devs :
- @mikeioannina
- @alinolaw71
- @Dark Raven
- @vishal_android freak
- @Amir Hoseinina
- @Langes
- @3andala
- @evil.demon_s
- @cr3pt
- @sud.vastav
- @skull47
- @vampent0026
- @HeadFox
- @Achotjan
- ... ( tell me if I missed an other kitkat developer )
If the thread is in the wrong section , please MODs move it to the right section . And if you find it unuseful , please delete it
Thank you very much .
job.
in the past few days i was thinking about making such thread like this...but u made my work easy ...completely agree with u man...thanks alot
If I'm not wrong, many people you named are only themers, code developing and zip editing are different things.
Keep in mind, that there aren't many people with at least basic knowledge of building Android.
kinda agree with this one, there's no significant differences between those kitkat rom (except PAC )
yep, most of "developers" just change apps/icons not code like @mikeioannina
yes maybe cause I didn't pay attention to who is expert or not but everyone can help at least with his current knowledge , in addition to the others who are experts in coding roms and kernels mentioned there .
If Mike , as the main cm11 dev , make request to developers , that will help a lot like what nAa did in the past .
job.
godlesplay said:
yep, most of "developers" just change apps/icons not code like @mikeioannina
Click to expand...
Click to collapse
Vynikal said:
If I'm not wrong, many people you named are only themers, code developing and zip editing are different things.
Keep in mind, that there aren't many people with at least basic knowledge of building Android.
Click to expand...
Click to collapse
job.bousix said:
yes maybe cause I didn't pay attention to who is expert or not but everyone can help at least with his current knowledge , in addition to the others who are experts in coding roms and kernels mentioned there .
If @mikeioannina , as the main cm11 dev , make request to developers , that will help a lot like what nAa did in the past .
job.
Click to expand...
Click to collapse
Its very easy to say that " many people you named are only themers and most of them just change apps/icons not code "
Just try once to make a z1 or z2 framework for cm...!!!
It takes alot of efforts just to port z1 or z2 framework compatible to themes
And most of the rom dev prefer to work on mike's rom because they feel easy to download a 200mb zip file and work on it instead of downloading 50gb of source code
And now a days there are.many users who have downloaded the source code and building their "self compiled " build
But they are just downloading the new commits and compiling a build
There's a difference between source coding and only compiling some commits
Ya...compiling sources is also not a simple job as bugs reports are given..no doubt about that
So devs like mike langs dark revan and mardon who are actually working on cm 11 should be given their time to give us a stable cm 11 as we dont have enough knowledge about making changes in the source code
Sent from my Xperia Live with Walkman using XDA Premium 4 mobile app
Please don't keep tagging Mike here again and again, he will not like it... he has already been tagged once in the OP
also, as has already been stated above, off the top of my head, only Langes and Mike have the expertise to work at kernel level, most of the other JB+ kernel developers have abandoned our devices...
Hmmm...honestly there only a few real developer for our 2011 devices....other just some that port roms from different version of custom roms...most of them just download from mike source and build up them there.....those were the guys can give us variety of custom roms for 2011 devices...there also other than just maintainer from certain team....there are also the one that mostly help mike by submitting same patches to fix and bug on mike build....
all of them depending on mike source code to build their own version of custom roms....remember their might be the developer of the certain roms but there are all depending on mike just like we user do....
rahimali said:
Please don't keep tagging Mike here again and again, he will not like it... he has already been tagged once in the OP
Click to expand...
Click to collapse
Yes , yes , you are right ..
Hello there.
Since there are so many requests about a CM Port.
I wanted to make something.. There is no port coming soon nor is a official one
BUT, if all of us (the ones that want that port) email CM and ask for a CM for n7505 and 750 we maybe see a port soon!
If I do it alone I wouldnt get a response back. But if we all do it. Maybe we will!
Because, with more people, we stand stronger
Thanks for reading
Leave a comment about what you think of this idea!
Greets.
bro it doesnt work like that....simply requesting them wont work....first someone from our device have to make an unofficial cm build by himself....then we have to remove all the bugs and we have to submit that rom to cm team....then they will review the rom and if they are convinced that the rom is bugless and the sources used are appropraite then they will announce our device as officially supported....but even after that we need an active developer to maintain cm for our device so that future updates are correctly implemented in our device.....
so asking them will do nothing we have to build our own cm and even after building we have to maintain it to make it officially supported by them....
There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
hareshsangar said:
There are Lott's of threads for porting for Rom's to any device..
But most of describes to use same android versions for base and port...
But i want try porting CM12 for Galaxy Core...
I am not a developer but still want to use Cm12 on my device .. So instead of asking some one i would love to port it by myself:thumbup:
Click to expand...
Click to collapse
That is hard to do without a background in building from source and knowing some coding and kernel stuff. You don't have lollipop yet on that device so it will be even harded. You can't just copy some files. You need a device tree and modify the kernel and then build cm12 from source.
Thanks for taking time .. But i would if i can port CM11 at least
hareshsangar said:
Thanks for taking time .. But i would if i can port CM11 at least
Click to expand...
Click to collapse
Well I don't know about your device (it's basically the same for all Qcom device, I don't know about MTK). Porting by copying files is less reliable then building from source (well it's way easier). It's very very hard to solve bugs when copying files and if the base has bugs the port might be even more buggy.