So, at the risk of being flamed, I still have to ask (since I did a half-assed search) what exactly this means? Does it mean the source of the ROM has been made availible to the public? Becuase I thought it already was.. or was that just for application developers to have the 2.0 environment to make/test their programs with..? I think that was the ADP..? Does this mean now that ROM modifiers such as Cyanogen have their hands on the source now to manipluate and develope it?
Go ahead and flame on if you must.. I would just like to get this cleared up becuase it is knowledge to be attained.
nopotential said:
So, at the risk of being flamed, I still have to ask (since I did a half-assed search) what exactly this means? Does it mean the source of the ROM has been made availible to the public? Becuase I thought it already was.. or was that just for application developers to have the 2.0 environment to make/test their programs with..? I think that was the ADP..? Does this mean now that ROM modifiers such as Cyanogen have their hands on the source now to manipluate and develope it?
Go ahead and flame on if you must.. I would just like to get this cleared up becuase it is knowledge to be attained.
Click to expand...
Click to collapse
This means that the 2.0 version of Android (or at least partially as of writing) has gone open source and people may begin building 2.0 from source.
i have the feeling 3.0 isnt so far away
JAguirre1231 said:
This means that the 2.0 version of Android (or at least partially as of writing) has gone open source and people may begin building 2.0 from source.
Click to expand...
Click to collapse
Thank you so much, I really appreciate you clearing that up for me.
Ace42 said:
i have the feeling 3.0 isnt so far away
Click to expand...
Click to collapse
what makes you think that....-_-
2.0 going "ASOP" means that the 2.0 source is officially released to the Android Open Source Project
the code has been dropped
Related
Not sure if this is helpful or not, but it looks like the 3.2 source code has been released:
http://groups.google.com/group/andr...1c225a11f5/6410b44798c19d61?#6410b44798c19d61
and
http://m.androidcentral.com/android-32-gpl-code-pushed-aosp
this is just the parts used for the 3.2 update that are using the GPL license, that requires
the source code to be available when the software is shipped.
Oh, gotcha. Oh well.. I had hoped it might be something useful
pretty sure google has said multiple times that honeycomb source will not be released. Going to have to wait till ICS for a truly customizable tablet platform
Yes, sadly we will not have 3.2 until samsung releases it or someone hacks a xoom rom to run on the gt10.1.
Huh?! Did you mean 3.2?
RustyNailz said:
Huh?! Did you mean 3.2?
Click to expand...
Click to collapse
Yes.
Updated ^
Are there any plans to build an ICS ROM for the N1 from the SDK?
My guess they will start making some when google release the AOSP.
Dude Random21 said:
My guess they will start making some when google release the AOSP.
Click to expand...
Click to collapse
I think the OP was asking if there will be ROMs based on the SDK (which is already out), not on AOSP...
Bohemus said:
Are there any plans to build an ICS ROM for the N1 from the SDK?
Click to expand...
Click to collapse
If you want to play around with it, just use the SDK and create an AVD. Actual ROMs based off the SDK do not work well, so might as well just play around with it on an AVD.
efrant said:
I think the OP was asking if there will be ROMs based on the SDK (which is already out), not on AOSP...
Click to expand...
Click to collapse
I know that, I was saying that there probably will only be ports to the N1 once the AOSP comes out.
I know CM will not port anything from SDK
Dude Random21 said:
I know that, I was saying that there probably will only be ports to the N1 once the AOSP comes out.
Click to expand...
Click to collapse
Folks will prob be putting out SDK builds now, given that the SDK is out, but the source is not . Once the source is available, we will see AOSP builds.
EDIT: What I was trying to say is that once the source is released to the AOSP, there certainly will be no SDK builds released. If SDK builds are coming (as they have in the past) they will come between the release of the SDK and before the release of the source...
Sent from my Nexus One using Tapatalk
Aside from installing what other devs make, I've never really been a part of the Android dev scene, despite being a programmer (mostly web dev and interpreted languages) myself. I'm not sure if its my inexperience or naivete talking, but isn't technically possible to compile AOSP with the kernel source Motorola posted and install that on a Moto X with an unlocked bootloader? Is there any real roadblock between me and my own custom rom (besides my lack of a linux computer to compile everything on)?
mrbradeli said:
Aside from installing what other devs make, I've never really been a part of the Android dev scene, despite being a programmer (mostly web dev and interpreted languages) myself. I'm not sure if its my inexperience or naivete talking, but isn't technically possible to compile AOSP with the kernel source Motorola posted and install that on a Moto X with an unlocked bootloader? Is there any real roadblock between me and my own custom rom (besides my lack of a linux computer to compile everything on)?
Click to expand...
Click to collapse
I dont see why you would want to... It basically ships with AOSP and a couple Motorola apps.. Unless you mean to compile 4.3 or 4.4 when it releases. Compiling 4.2.2 for the X would be kinda useless...
kernozlov said:
I dont see why you would want to... It basically ships with AOSP and a couple Motorola apps.. Unless you mean to compile 4.3 or 4.4 when it releases. Compiling 4.2.2 for the X would be kinda useless...
Click to expand...
Click to collapse
Useless or not I want to get into the custom rom game. Compiling AOSP from the source and installing it is a great start.
mrbradeli said:
Useless or not I want to get into the custom rom game. Compiling AOSP from the source and installing it is a great start.
Click to expand...
Click to collapse
If you know that then porting 4.3 could be a good start.
kernozlov said:
If you know that then porting 4.3 could be a good start.
Click to expand...
Click to collapse
Well I'm certainly up to looking into it. Is it as simple as compiling 4.3 with the kernel motorola gave us?
mrbradeli said:
Well I'm certainly up to looking into it. Is it as simple as compiling 4.3 with the kernel motorola gave us?
Click to expand...
Click to collapse
I cant really help you with that. Im not a dev, just a long time android tinkerer who saw an unanswered thread I could provide a little insight in.
Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......
There is no Cyanogen for our tablet for the moment
You can check here : http://download.cyanogenmod.org/
So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks
Dekan54 said:
So it is the CM Team that takes the time, energy, and resources to put it together for the S2?
I will keep an eye on the CM website and hope they put something together soon. I wish I had someway to contribute but my skill set is very limited.
Thanks
Click to expand...
Click to collapse
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Okay - That makes sense.... I will help test if you get to that point.
Would be nice with cm12 but probably with lots of drawbacks. Samsung won't release source code of drivers and could be problematic with exynos nor will fingerprintscanner work.
BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
You may want to ask @eousphoros for help. He got it rolling on the the tab s I bet he could help you big time!
BigBot96 said:
No.. it takes someone with enough knowledge to build it for our hardware. I've never done it, but I'm attempting. Learning as I go... emphasis on attempting.
Click to expand...
Click to collapse
Good to hear someone is working on it. ?
Sent from my not-so-stock SM-T810
CM is always buggy and lots of features wont work or plain buggy. Bloat is very minimal and works quite smoothly stock. Dont blame you if you like the "fun" of constantly flashing roms and waitkng for bug fixes.
Dekan54 said:
Could someone educate me on what it takes to get CM 12.1 on to the S2?
I understand that you have to root, install TWRP, and flash the ROM but who actually puts together CM 12.1 rom together and makes it compatible for the S2? Is it the official CM team or a developer on this forum who takes the time and energy to put it all together?
Thank you for your help in educating me......
Click to expand...
Click to collapse
Hey there. As a dev myself I will explain you the difference between official CM builds (build = the ROM) and unofficial builds. Official builds are made by the pros. The guys that are in the CyanogenMod group. They know how things work and patch them due their high knowledge. They will try to update the ROM regularly and fix it as well as they can. Then there are the unofficial builds from people like me. It depends what your skills are and with what board you are working (Exynos is a pain in the ass). Not to forget what version of android your device is currently running. Unofficial builds can be buggy and could take some time to get fixed. However devs will listen to the feedback of the community too.
~wrong devices kek
Cherry is Honor 4/4X - https://wiki.cyanogenmod.org/w/Cherry_Info
I think the Honor 6 codename was hwH60 or something like that.
Please delete the links or the entire thread as soon as possible, if people will start flashing this then we will likely have a lot of bricked devices. Venipa, this is horrible irresponsibility on your side to upload links to unknown stuff without even testing it yourself (even if you put a disclaimer)! And to all the guys thinking that we will magically get working CM one day, think again. You found a semi-official build of CM for some Huawei device and seriously thought it's a H60 build we didn't hear about before? If there is ever a proper CM release, it will take time to do it. But people posting stuff like "I've already posted the Full Source including Kernel Source and still no one wants to do it" will never understand how hard it is to make a ROM, or what exactly "full sources" mean...
MaRtYy01 said:
Cherry is Honor 4/4X -
I think the Honor 6 codename was hwH60 or something like that.
Click to expand...
Click to collapse
Honor 6 is mogolia
sado1 said:
Please delete the links or the entire thread as soon as possible, if people will start flashing this then we will likely have a lot of bricked devices. Venipa, this is horrible irresponsibility on your side to upload links to unknown stuff without even testing it yourself (even if you put a disclaimer)! And to all the guys thinking that we will magically get working CM one day, think again. You found a semi-official build of CM for some Huawei device and seriously thought it's a H60 build we didn't hear about before? If there is ever a proper CM release, it will take time to do it. But people posting stuff like "I've already posted the Full Source including Kernel Source and still no one wants to do it" will never understand how hard it is to make a ROM, or what exactly "full sources" mean...
Click to expand...
Click to collapse
Can you tell me what exactly is missing from the source provided by Huawei?
Henrikx said:
Can you tell me what exactly is missing from the source provided by Huawei?
Click to expand...
Click to collapse
I'm not a developer so somebody else should be able to explain it better, but in general, the sources provided by Huawei are at most only useful enough to make a AOSP-style ROM based on the same Android version as the EMUI ROM the source is released for. So, no CM, no newer Androids than Marshmallow, etc.
nooo, got my hopes up (
sado1 said:
I'm not a developer so somebody else should be able to explain it better, but in general, the sources provided by Huawei are at most only useful enough to make a AOSP-style ROM based on the same Android version as the EMUI ROM the source is released for. So, no CM, no newer Androids than Marshmallow, etc.
Click to expand...
Click to collapse
Not true.Then why kirin based p8 lite has cm14?
http://forum.xda-developers.com/p8lite/general/cyanogenmod-14-t3458451
Its because we dont have devs and our device isnt that popular.Kirins arent the most rom friendly cpus,but they arent totally useless.
MaRtYy01 said:
Not true.Then why kirin based p8 lite has cm14?
http://forum.xda-developers.com/p8lite/general/cyanogenmod-14-t3458451
Its because we dont have devs and our device isnt that popular.Kirins arent the most rom friendly cpus,but they arent totally useless.
Click to expand...
Click to collapse
Okay, this proves me wrong. And obviously, I completely ignored the fact that our device already had a CM port, so indeed with a dedicated developer we'd have a chance to get something. What I probably should've said is that a potential developer has a lot of work ahead because of poor sources quality from Huawei, and absolutely no chance to make an official CM port for example. Of course, this all is based on random stuff I read on XDA about it, so you guys should wait until someone more knowledgeable responds to have a clear picture on the problems the development for this device is facing.
Heartbreak.
Thread closed as per OP's request