Develop Bugs

[Q] Source

I have a question, while everyone says that to get cm7 we need to wait for official gb. I understand that but we got official froyo didn't we? how come we don't have cm6 if it was official froyo and i would think it came with source within 30 days?
By all means, dont take this as a rant, i was just curious.

The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App

austin420 said:
The people working on cm6 didn't see any point in finishing the project even with source because gb and new source was supposedly around the corner. 6 months later, we still don't have gb, and imo may never, and cm6 is final. The real cyanogen team doesn't support 6 anymore afaik.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......

theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/ supposedly were getting them with gb but if not its gonna be hit or miss every step of the way since building aosp roms w/o source is like navigating a maze in the dark.......
Click to expand...
Click to collapse
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-

kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Let's clear a something up.
Official Cyanogenmod is 100% possible WITHOUT source code/drivers/etc. it just is not a practical endeavor to begin the arduous process of writing drivers and an AOSP kernel from scratch when there is a very real chance of source code being released in the near future.

kwazytazz said:
i thought they had to release source within 30 days? or is the driver source not part of that?
if they didn't release the driver source with official froyo release then they probably wont for gb, then its say bye bye to official cm -.-
Click to expand...
Click to collapse
Yeah its not impossible dude, just like 063_XBOX said..... I thought my metaphor explained it pretty well .... its possible to navigate your way out of a maze in the dark.... it'll just be a pain in the ass running into walls the whole way through..... "if we don't get any source with gb, Id think we would have nightly builds within 2-3 months assuming everyone pitched in and we had our best devs on the job..... " everything in the quotes is speculation and my personal guess so take it with a grain of salt or not at all.....
Ninja Edit: and as for source being released within 30 days of rom release, that's only for the kernel (and maybe rom?, I don't think roms have source??? I could be wrong)...... but drivers are closed source, which means they aren't required by license to give out.....

theduce102 said:
No I asked this same question the other day and a CyanogenMod dev said it was because we never got driver sources :/
Click to expand...
Click to collapse
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App

austin420 said:
I didn't think we ever had a sanctioned cyanogen mod dev working on the epic. Just other devs working on a port.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Naw we have had quite a few devs working on it but one of them just so happened to answer me....
But when I say CM dev I mean someone who actually contributed to the projects and made some progress in getting something to work in one of the builds.....

ICS Source is OUT ! (Ice Cream Sandwitch) Android 4.0.1

Hi All,
Below a message from google about releasing ICS Time to DEV !
Greatings
Antonius
https://groups.google.com/group/android-building/msg/c0e01b4619a1455a
Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.html
Check out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.

Yessssssss

now let the games begin!!

Good news! Hopefully the devs can do something magic!

What does this actually mean for us DHD users? is it simply a matter of putting 2 and 2 together, and bam we have a rom? or will it take a few weeks, and be extremely difficult because I notice everyone saying this is only for the Galaxy Nexus, so it is pretty much like porting I guess?

Repsys7 said:
What does this actually mean for us DHD users? is it simply a matter of putting 2 and 2 together, and bam we have a rom? or will it take a few weeks, and be extremely difficult because I notice everyone saying this is only for the Galaxy Nexus, so it is pretty much like porting I guess?
Click to expand...
Click to collapse
It will be very easy

Thanks for letting the devs know
Sent from my Desire HD using XDA App

@Antonius
Really? I hardly believe that.
Having the source code is very important, not everything. Release source code is for Galaxy Nexus, a different device. We need a working kernel and support for our hardware. Real devs are probably working on that now. The real work begins from here, and I hardly believe we will have something functional until CM9 starts having night builds... 1-2 months from now

Maybe we get the first nightly as a christmas gift.

alienmind said:
@Antonius
Really? I hardly believe that.
Having the source code is very important, not everything. Release source code is for Galaxy Nexus, a different device. We need a working kernel and support for our hardware. Real devs are probably working on that now. The real work begins from here, and I hardly believe we will have something functional until CM9 starts having night builds... 1-2 months from now
Click to expand...
Click to collapse
I think you need to read the post again this is the Source code it is a build up for gingerbread as i saw the code this night it was released the drivers and support are gonna be build very easaly but still it can take up to 1 a 2 weeks before release (Altrough i think some devs will release today for other devs to work on it) Also we need to keep in mind that there will be bugs in the system (Its still a child )
Greatings
Antonius

Multiple threads already on this. One is enough for development section. Moving to General

hahaha :-D at last.............waiting 4 it

In the words of many a drunk person at music festivals across the country
"HERE WE, HERE WE F*CKING GO"

Antonius123 said:
I think you need to read the post again this is the Source code it is a build up for gingerbread as i saw the code this night it was released the drivers and support are gonna be build very easaly but still it can take up to 1 a 2 weeks before release (Altrough i think some devs will release today for other devs to work on it) Also we need to keep in mind that there will be bugs in the system (Its still a child )
Greatings
Antonius
Click to expand...
Click to collapse
I think you need to read a bit harder
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus
Click to expand...
Click to collapse
This still needs porting, new kernel building, etc. I think a couple of months for alpha/nightly builds for DHD sounds about right.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.

I hope as soon as possibile!

You where mistaken my friend: http://forum.xda-developers.com/showthread.php?t=1343361
check this thread!
hopscotchjunkie said:
I think you need to read a bit harder
This still needs porting, new kernel building, etc. I think a couple of months for alpha/nightly builds for DHD sounds about right.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Click to expand...
Click to collapse

Being a photographer is not conducive to having ICS beta builds without camera... and i'm a flashaholic! What am I to flash?!

[INFO] Good News Abound - The state of DEV

I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.

there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on

I for one is not counting on it, frankly...
No matter how beautifully you phrase things, WE GOT NOTHING YET.
Sent from my SGH-T989 using XDA App

[A virgin sacrifice] =
SO FREK'IN EXCITED!!!!!

thanks for the info bro looking forward to it

jessejames111981 said:
there are a lot of other devices with cm9 alpha and we are still not an officially supported device. Still unofficially being worked on
Click to expand...
Click to collapse
the thing is, many of those are KANGed as in not officially supported by CM team
of the few that officially are supported is Nexus S i9020 and SGS i9000
even the "classic" SGS2 i9100 is not fully supported by CM yet, there's more bugs than... well it's not usable as a daily driver
that was just before the end of last year
they might have improved it a bit by now
even the Nexus S version of CM9 is still very buggy, that's why i have the stock official ICS4 instead on my Nexus S

Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium

iwasblown said:
Please please use words like
"death of an era." Instead of virgin sacrifice. I don't believe in that
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I don't believe in idiots, can you make them all go away?

It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.

Why this statement?
From a glaxay better than yours.

tl;dr
I am basing my entire post on the fact that Steve Kondik has our device and should theoretically be working on it.
Click to expand...
Click to collapse
Steve Kondik aka Mr. Cyanogen also works for Samsung. I am sure he gets ALL Samsung devices...

corwest said:
It takes time for this stuff guys. Anyone remember how long it took to jump from donut to eclair to get a stable rom? And look how few devices there were that actually ran android. This whole "if its not done in 2 weeks then its never happening" thing is a bit unfair. Let the devs dev and those who do not can wait for them quietly.
Click to expand...
Click to collapse
It only takes 2 weeks to modify the stock rom or cm7/9.
Its the expectation that is built when people act like quantity is all that matters. There are basically only 2 people making roms; Samsung and CM team, everyone else just waits on these 2 so that they could tweak and modify one of those 2. The funniest part is that the use of the word "kanging" is thrown around among these other people.

housecat93 said:
I thought I'd clear some things up.
If I'm wrong please don't flame me, I'm only doing my best to subdue the general discontent in [sgh-t989]/[android development]...
Steve Kondik, also known as the creator of the godfather of all ROMS (cyanogenmod) personally owns one of our t989s (source:twitter). That, combined with the fact that this is a FLAGSHIP t-mo device probably means that our phone will be supported from the day that 9.0.0 drops.
Now, let me tell you what this means.
As you all know, for a device get non-kang CM9 our hardware must be fully supported. Camera, GPS, bluetooth, egl drivers all must work.
When a huge scale ROM like CM9 is cooked for so many devices I understand it goes something like this
[AOSP modified by Cyanogenmod(teamdouce)] +
[Android Kernel, also modified by Cyanogenmod]+
[Device tree]+
[A virgin sacrifice]=
CYANOGENMOD
Now the interesting bit, is that as soon as the device tree (Eg. Specific driver modifications for GPS, Camera, GPU) includes our device the device tree can be used to power OTHER AOSP ROMS like Miui
I know that gingerbread MIUI already makes use of the CM7 device tree, so in all likelihood they will use the CM9 device tree as well!!!
So in conclusion.
-Because CM9 has a high likelihood of dropping on our devices as soon as it comes out (most likely within the next 30 days)
-Because other AOSP-Based roms depend on the cyanogenmod device tree
-WE WILL HAVE A LOT OF FLASHING OPTIONS SOON
-Probably including CM9 AND MIUI v4 <<<<--------THAT **** CRAY
Thanks for your time, hope it helped
Don't forget the thanks button feels good when you push it.
Click to expand...
Click to collapse
I'd like to believe, I really would. And I hope this does come to fruition. However, even if it doesn't, the few ROMS we do have are pretty good, and our phone still outperforms almost anything else available right now, so I'll still be happy.
I do have one request, though. Can we figure out a way to make CM based ROMS happen without a virgin sacrifice? There are so many other things in life that require those, that they are starting to become scarce

The fact that lots of other phones have alphas and repositories available to even make kangs does not fare well for our device.
Sent from my HTC_Amaze_4G using xda premium

guys chillax..slayher already has it booting..and that's news from december

good to know, thanks

Great phone, needs more dev time and hopefully that comes along with it when ics hits.
We got shafted early with the nexus release so close to the T989 and a dev that promised things but ran away.
New year brings new hope. Great respect for the devs that care about our phone.
Sent from my SGH-T989 using XDA App

Let's hope the mods don't ban what little devs we have left...
Sent from my HTC_Amaze_4G using xda premium

AznDud333 said:
guys chillax..slayher already has it booting..and that's news from december
Click to expand...
Click to collapse
I don't follow, what do you mean by booting?

synergeticink said:
I don't follow, what do you mean by booting?
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Booting

CM9 Stable

Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!

sf_smith said:
Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
Click to expand...
Click to collapse
We don't have the needed drivers/source code HTC backed out on us. Aside from that though Mimicry is VERY stable I'd recommend flashing it!

Many roms past GB are very stable now. From Sense 4.0, to ICS, to even JB nightlies are reportedly smooth.
I use this ICS as a daily driver and it's very stable (AOKP): http://forum.xda-developers.com/showthread.php?t=1642443
JB nightlies: http://forum.xda-developers.com/showthread.php?t=1605016 Weren't stable when I tried them, but I hear they're really good now. Might try later this week.
It all has to do with drivers being released or something from Qualcomm: http://forum.xda-developers.com/showthread.php?t=1822694
I don't know if it's true. The thread doesn't provide much information, maybe someone can clarify.
Are the drivers really released and being incorporated into roms? People are saying they are already being used in those JB nightlies.
As for not being out officially by CM... I don't even think they started working on it.

sf_smith said:
Looks like the G2 (Desire-Z) will not be getting CM9 stable as I have been keeping an eye on this list since last week's launch:
http://get.cm/?type=stable
Does anyone in this dev thread know why? I know there are unofficial RCs and the nightlies, but I avoid them and only go for stable. I was hoping it would get ICS stable but it appears 7.2 Gingerbread will be this device's final stable ROM.
Any insight would be greatly appreciated!
Click to expand...
Click to collapse
There are no official CM9 roms for the vision. The unofficial roms (Andromadus & the one by jerl92) are the closest thing, but they are only based on Cm9, not released by or associated with the actual Cyanogenmod team. The reason there even is a CM9 based rom is thanks to Andromadus.
That said, Mimicry will have a new version out this week based on the repo for CM9 stable. The non-device specific code anyway, the other branches are of course unofficial and not supplied by the CyanogenMod team.
Sent from my HTC Vision using xda premium
---------- Post added at 03:57 PM ---------- Previous post was at 03:54 PM ----------
.ili.music.ili. said:
Are the drivers really released and being incorporated into roms? People are saying they are already being used in those JB nightlies.
As for not being out officially by CM... I don't even think they started working on it.
Click to expand...
Click to collapse
Yes, the qualcomm drivers have always been incorporated into Andromadus roms as soon as they're available. Since the other roms are based on Andromadus (AOKP, jerl92's), they also incorporate the new drivers.
Sent from my HTC Vision using xda premium

eeeeey, and I thought that CM9 stable for Desire Z is already out, bad luck

I hate to be that guy, but while development related, I'm pretty sure this belongs in the Q&A or General Discussion section. Catch knowledge!

You guys are missing drivers to?? We're also missing them!! Dang HTC :banghead::banghead::banghead:
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2

The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF

DON_58 said:
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
Click to expand...
Click to collapse
There was a post by one of the developers stating that it will be coming. Everyone just needs to be patient.
Sent from planet Vegeta.

DON_58 said:
The word around the Cyanogenmod Google+ site is that its coming but that it will take some time given that the drivers need to basically be written from scratch. This is a list of devices that are being droppped from any further releases of CM past CM7. The vision is not included on the list so you could say there is a glimmer of hope but I guess you have to take it with a grain of salt.
https://plus.google.com/117962666888533781522/posts/MRnnvs3oFUF
Click to expand...
Click to collapse
Only mentions of the DesireZ/G2 in that posting is in the comment section, they're probably talking bout semi-newer devices. I still think we have a better chance of getting it 'fully' working under the Andramadus team's effort (still cM9 but probably the best it's going to be for our devices). ie: if drivers are written from scratch, it most likely won't be done by the CM team, but will probably be incorporated into their project when done.

kbeezie said:
Only mentions of the DesireZ/G2 in that posting is in the comment section, they're probably talking bout semi-newer devices. I still think we have a better chance of getting it 'fully' working under the Andramadus team's effort (still cM9 but probably the best it's going to be for our devices). ie: if drivers are written from scratch, it most likely won't be done by the CM team, but will probably be incorporated into their project when done.
Click to expand...
Click to collapse
Thats the point. Its not listed among those which are being discontinued and most of those devices are over 2 years old. Don't get me wrong I'm not trying to take anything away from the Andramadus team. I'll probably end up giving mimicry a run soon. I'm just trying to point out that the door hasnt been officially shut yet on this device as far as an official cm9 build goes.

DON_58 said:
Thats the point. Its not listed among those which are being discontinued and most of those devices are over 2 years old. Don't get me wrong I'm not trying to take anything away from the Andramadus team. I'll probably end up giving mimicry a run soon. I'm just trying to point out that the door hasnt been officially shut yet on this device as far as an official cm9 build goes.
Click to expand...
Click to collapse
Though here's something to think of: There is only one, I repeat one HTC device that is officially supported by Cyanogenmod 9. IF newer HTC devices aren't getting it, I doubt even more that a 2+ year old device would.

kbeezie said:
Though here's something to think of: There is only one, I repeat one HTC device that is officially supported by Cyanogenmod 9. IF newer HTC devices aren't getting it, I doubt even more that a 2+ year old device would.
Click to expand...
Click to collapse
I doubt the One S/One X aren't going to get CM9 Actually, I could complain about CM turning into SamsungMod, but I don't really give a damn. Just look through the supported device list yourselves, folks...

asp roms

When will we see a aosp rom for our note 3

Tomorrow when the clock strikes 12. I promise
Sent from my magic spaceship

When people stop asking for ETA's.
sent from my sm-9005.

Yerv Melkonian said:
When will we see a aosp rom for our note 3
Click to expand...
Click to collapse
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!

d12unk13astard said:
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
We're just excited. Let us wag our tails and scratch at the door until our owner opens the door for us. So to speak. LOL!

Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium

dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
I would love to see that
Sent from my SM-N900T

Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk

dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
You sir have just explained the reason I fell in love with android, aosp, the rooting community. A lot of people don't get and are unappreciative of the works of ROM devs. So much greed and selfishness I've seen on xda since after the g1 days. Its always *****ing and bickering and this and that and demanding. Thank you to all the devs out there. Without you guys, android will be a Disney Land that never opened its gates
Sent from my SM-N900T using xda app-developers app

pathtologos said:
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
+24

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
Why would you quote me and say exactly what i said in a long drawn out explanation. I'm guessing you missed the punctuation in my response. I mean you said everything i said, down to how the CM is a work in progress. Sheesh.

CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
DUDE I couldn't have said it better myself. You devs are wizards.