Develop Bugs

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

"Fully compiled from aosp source"...

Can somebody englighten me why the aosp rom devs say that they write the code for their rom from zero and then as we can see all the aosp roms are almost 100% identical and even their bugs are identical? Wouldnt one expect these roms to have different bugs since the devs claim that they write their own code?

ROMs that are compiled from source just means they were compiled using Google's source code, that doesn't mean they don't integrate other people's work, or "cherry picking" as CM calls it. It comes down to why re-code something that's already been made? Most things have already been made, and the few that haven't are either too hard or there's not much interest.
I'm sure most devs do have their own tweaks and whatnot, but not everything in a ROM has been made by them and a lot of stuff is borrowed or shared.
From build.prop tweaks to smali edits, to even simple framework tweaks, this is what devs could be talking about, nothing cosmetic that can be seen or merely felt, but that doesn't mean it's not there.

A Google search will tell you what it takes and what it is to compile a ROM from source. That shoulld enlighten you to these mysteries.
Sent from my HTC Glacier using xda premium

Yeah but whenever they talki g about compiling from source instead of porting they sound likr showing off as if they invented the whole code themselves. To me they all seem the same, the only difference is the way they organize the order of the menus in the settings. One bug that is common for all aosp for example is alarm clock that has been there for months, or camera problems that existed in the past. I just wanted to make this clear cuz it seems like this compiled from aosp has become exageratted way of showing off and people new to android feel like wow omg what impressing things this or that dev has done, while in fact only very few devs are the ones that deserve the credit for first "inventing" smthing/"fixing" bug and the rest simple get it from their source tree.

romuloxiii said:
A Google search will tell you what it takes and what it is to compile a ROM from source. That shoulld enlighten you to these mysteries.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Iknow what it takes.

lazarat said:
Yeah but whenever they talki g about compiling from source instead of porting they sound likr showing off as if they invented the whole code themselves. To me they all seem the same, the only difference is the way they organize the order of the menus in the settings. One bug that is common for all aosp for example is alarm clock that has been there for months, or camera problems that existed in the past. I just wanted to make this clear cuz it seems like this compiled from aosp has become exageratted way of showing off and people new to android feel like wow omg what impressing things this or that dev has done, while in fact only very few devs are the ones that deserve the credit for first "inventing" smthing/"fixing" bug and the rest simple get it from their source tree.
Click to expand...
Click to collapse
Unfortunately, I do agree with what you're saying, but in a way, the devs aren't lying. Most devs do indeed compile from source instead of using someone's base.
This phone didn't get as many devs as I expected it to.
A lot of real amazing devs are on other devices, it would be great if we could get one or two devs in here. Now I'm not taking any credit away from our devs, but it's nice when devs have a team like Hawk and Roman, Team Whiskey, man I loved their ROMs, everything seems to progress faster and have a lot more options. Take CodenameAndroid for example, that's a team of devs.

theexel said:
Unfortunately, I do agree with what you're saying, but in a way, the devs aren't lying. Most devs do indeed compile from source instead of using someone's base.
This phone didn't get as many devs as I expected it to.
A lot of real amazing devs are on other devices, it would be great if we could get one or two devs in here. Now I'm not taking any credit away from our devs, but it's nice when devs have a team like Hawk and Roman, Team Whiskey, man I loved their ROMs, everything seems to progress faster and have a lot more options. Take CodenameAndroid for example, that's a team of devs.
Click to expand...
Click to collapse
Eh... time to get lg nexus maybe lol

While some may be trying to look good or appear smart or whatever like you're saying, I think the majority do not have these sort of intentions.
I can say that if I were to release a rom that I compiled from source, I would put that in the op. Not to brag or anything like that, but just to inform. If I used someone elses as a base, I would mention it just the same.
If I were to compile from source, but not tell people I did, how long would it take for someone to ask where the base is from? To me its just another info point for the rom, and personally, I like to know where a dev got their base.
Also, as I understand it, while the mods and tweaks may or may not be their own, they most likely implement their changes before compiling, so the source will be different than original. Of course the vast majority of code will not be written/invented by them. Its Android source code. Open Source!
Maybe ive got it completely wrong, but to me, its just never been a big deal. I honestly never even thought about it in this context until this thread. (I don't use aokp or cm very much, so maybe that's why)
I know that you are right about some people, i just dont think they are in a majority here. Just thought id share my thoughts! Not sayin anyone else who's posted here is wrong. Its just my opinion based on how I understand it.
Sent from my SGH-T999 using xda app-developers app

[Q] Build CM (CyanogenMod) for the hltetmo

Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht

gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
It looks like it's progress or at least people are tinkering around with it. However, you would need a full tree for the device if you wanted to build it from source, know enough to get your own tree, or be able to fork from other device tree's to get something going. The new Nexus has the same chip so that may make things quicker with getting a full working device tree. I'm just quoting based on my own understanding of things, so please correct me if I'm wrong.

I've been wanting to know the same. I've built AOSP ROMs before (namely AOKP for my Note 1 pulling from CM's device tree) and would do the same if the files were available for the Note 3. A few devs have teased the community with screenshots, but until they post their code a tease and a cruel joke is all that it is. I really wish these devs would put their source code up even if it is incomplete and let the community at large get this thing in gear since obviously they can't do it fast enough single-handedly. Holding back code until it's "ready" defeats the entire purpose of open source development in the first place! We have the kernel but no one has a full device tree out yet, only a limited one for recovery purposes (mainly the TeamWin one from TWRP).

Any updates on cm10 or cm11 for the note 3
Sent from my SM-N900T

Within hours of any (usable) device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.

CrashTestDroid said:
Within hours of any device tree updates you'll see an explosion of new CM-based firmwares in the Dev sections.
I'll be building BeanStalk for hltetmo, probably 100 ppl will upload unofficial CM 11, it'll be a giant party for all.
Click to expand...
Click to collapse
Sooo... When's this party begin? :angel::fingers-crossed:

Can't wait for this
Sent from my SM-N900T using Tapatalk

Me neither even got rid of my note and went with n5 cause I couldn't wait but im back tk the beast just need cm
Sent from my SM-N900T

Ker~Man said:
Sooo... When's this party begin? :angel::fingers-crossed:
Click to expand...
Click to collapse
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom

gakio12 said:
Okay, so after no updates for a month and no sign of any sign of AOSP for the Note 3, I have decided to take things into my own hands. Or so I would like to believe. The problem? I have never built AOSP or Cyanogenmod before, let alone for a device that isn't even supported. So I was hoping the wonderful XDA community could help me out.
The only thing I really can't figure out is how to build CM/AOSP for an unsupported device using a device tree. Someone posted this tree on Github a month ago - https://github.com/OUDhs/android_device_samsung_hltetmo
Then there is a Cyanogenmod kernel for just regular hlte (not hltetmo), posted 10 days ago - https://github.com/CyanogenMod/android_kernel_samsung_hlte
And then there are blobs for mi5 (not mi7), posted 2 days ago - https://github.com/DoItForTheRatchets/vendor_hlte
So my questions are:
Are these any indication of progress on AOSP for the Note 3?
Can I/anyone build CM/AOSP from these for the hltetmo.
I know people have gotten CM on the Note 3; we have all seen the blurry pic one, but here is someone else on October 24th - https://plus.google.com/u/0/+TonyLayher/posts/A4J8eRH8Rht
Click to expand...
Click to collapse
Its getting real close. I imagine some other stuff is needed like qcom hardware updates and stuff. I'd give it another few weeks or so. BUT I imagine it'll be available soon.

I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.

CrashTestDroid said:
When a hlte device tree is buildable, looks like CM is making additions and others like nikkdotcom
Click to expand...
Click to collapse
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
gakio12 said:
I noticed nikkdotcom has a thread over in general for trying to get it running; he is asking for assistance in getting it to work.
Click to expand...
Click to collapse
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!

What blobs do you need? I thought blobs had to be extracted from the TW stock ROM. GPU blobs should be able to come from any other S800 device right (like the Nexus 5)?
Sent from my SM-N900T using xda app-developers app

geekcentercreations said:
That would be accurate.
Nikkdotcom GitHub here: https://github.com/nikkdotcom/android_device_samsung_hltetmo
---------- Post added at 01:18 AM ---------- Previous post was at 01:10 AM ----------
Im looking for someone who knows a little better than me about building without the proper blobs for the device. Once the right blobs are available, it will be custom ROMs galore!
Click to expand...
Click to collapse
I'd be more than happy to lend a hand.

ProTekk said:
I'd be more than happy to lend a hand.
Click to expand...
Click to collapse
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?

idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
There's enough on GitHub right now for a starting point. I've just started to poke around this morning so I can't say much. Tbh, I've been fairly content with TouchWiz so that's been one reason I haven't had a strong interest in working on AOSP

idtheftvictim said:
That is great news! We need someone with experience like you. I remember you from other devices, namely the s3.
Would you be able to reach out to the OP and try and get things rolling?
Have you found anything useful on github?
Click to expand...
Click to collapse
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app

Here is the most likely furthest along tree for anyone.
https://github.com/utkanos/android_device_samsung_hltetmo
It just seems like we might not see stuff on this device. Looking back on this thread people talked like it would be released in a week but I think it's going to be a lot longer than that.

idtheftvictim said:
Really? Content with touchwiz? Hmmm...I wish I knew more, I would be started trying to build cm awhile ago
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
That stuff is 2 months old. Nothing in two months? Man...no progress
Sent from my SM-N900T using xda app-developers app

I've never seen a device of this caliber take this long to receive an AOSP ROM! Wish I knew how guys, I'm tired of the TW ROMS, need some action in this forum already

[ROM][SGH-I317 / T0LTEATT][4.4.4][UNOFFICIAL] CyanogenMod 11 - Builds of opportunity

As many of you know the GSM Note 2 is supported by CyanogenMod in a unified build format. This work is simply monumental with a beautiful product. Many in the US Note 2 community are reluctant to use the unified build for a variety of reasons.
Nicktastique and rmanne picked up the mantle and provided the SGH-T889 community with device specific unofficial CM11 builds. As rmanne has transitioned to a new device, I saw that I would be able to give back to the T889 community and pick up the yoke and keep us moving forward. The SGH-I317 is very similar to the T889 and use nearly all the same build configuration.
My product is no more than a straight source built t0lteatt build as the CM11 spec is drawn up for the t0lteatt on the CM github. All source is available at the CM git. I make no changes unless noted (in the remote chance that changes occur they will be documented/git referrenced).
I make no promises or warranty of any kind, all flashing is done at your own risk and should not be thought to be the responsibility of anyone other than the person deciding to flash the ROM. While I will attempt to help you work through issues, I do not plan on integrating non-CM commits or "fixes" with very few exceptions (carrier network labeling is one such exception).
I plan on putting up new builds weekly if not a bit more frequently if I am inspired. If I see a change in CM commits that looks promising I expect that I would post a new build. I will not promise a timeline, I simply plan on weekly builds.
Let me know if anything is goofy.
Flashing instructions:
Using the most current TWRP, ClockworkMod, or PhilzTouch recovery; wipe data, system, cache, and dalvik (especially if coming from a different ROM).
Flash the unofficial CM .zip file from the link below
Flash the gapps of your choice (CM or PA are good)
Boot phone and let sit on a stationary flat surface.
Do not touch the device for 10 minutes to allow the caches to build.
Reboot the device and set up to your liking
DOWNLOADS
cm-11-20150322-COUGMADE-t0lteatt.zip
cm-11-20150313-COUGMADE-t0lteatt.zip
cm-11-20150222-COUGMADE-t0lteatt.zip
cm-11-20150206-COUGMADE-t0lteatt.zip
cm-11-20150130-COUGMADE-t0lteatt.zip
cm-11-20150116-COUGMADE-t0lteatt.zip
cm-11-20150107-COUGMADE-t0lteatt.zip
cm-11-20150101-COUGMADE-t0lteatt.zip
cm-11-20141220-COUGMADE-t0lteatt.zip
cm-11-20141212-COUGMADE-t0lteatt.zip
cm-11-20141209-COUGMADE-t0lteatt.zip
cm-11-20141206-COUGMADE-t0lteatt.zip
cm-11-20141201-COUGMADE-t0lteatt.zip
cm-11-20141126-COUGMADE-t0lteatt.zip
cm-11-20141027-COUGMADE-t0lteatt.zip
cm-11-20141020-COUGMADE-t0lteatt.zip
cm-11-20141011-UNOFFICIAL-t0lteatt.zip
cm-11-20141002-UNOFFICIAL-t0lteatt.zip
cm-11-20140921-UNOFFICIAL-t0lteatt.zip
cm-11-20140914-UNOFFICIAL-t0lteatt.zip
cm-11-20140906-UNOFFICIAL-t0lteatt.zip
cm-11-20140902-UNOFFICIAL-t0lteatt.zip
cm-11-20140826-UNOFFICIAL-t0lteatt.zip
cm-11-20140818-UNOFFICIAL-t0lteatt.zip
cm-11-20140810-UNOFFICIAL-t0lteatt.zip
CyanogenMod Gapps
PA Gapps (good variety of options)
All source code for CyanogenMod is available in the CyanogenMod Github.
CM t0lte git
CM t0lteatt git
DonkeyCoyote Samsung Vendor git
Props and credit to:
CyanogenMod team (especially t0lte maintainers codeworkx and madmack for their hardwork toward insuring that the Note 2 is kept in the loop).
UtkarshGupta for providing advice in working through build issues on compiling Omni that translated to quick work on CM.
Rmanne for assistance in getting running by help with troubleshooting the build process.
And certainly not least mattlowry for being solid from his first posts in the doubleshot community, evolving along with weekendsR2short to porting for the doubleshot, and elevating his game on the Note 2. His advice and example made the unfathomable become doable.
Hastily spouted for your befuddlement

Mine

Gimme

Will you be adding support for gear manager and Samsung apps store for people such as myself who has a galaxy gear (2 neo). I ask because it can be pre-built into the ROM and well I can't personally get it working otherwise lol. Thanks for taking the time :thumbup:

fatjoejr2001 said:
Will you be adding support for gear manager and Samsung apps store for people such as myself who has a galaxy gear (2 neo). I ask because it can be pre-built into the ROM and well I can't personally get it working otherwise lol. Thanks for taking the time [emoji106]
Click to expand...
Click to collapse
Not immediately. I have some stuff to focus on and figure out first. I'll look at it down the road.

Does it comes with the CM Themer?
Sent from my SHIELD Tablet using XDA Free mobile app

ShrekOpher said:
Does it comes with the CM Themer?
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Based on OP it sounds like it is in ever way shape and form the same.
Trying to figure out why I should prefer this over official.. No added bells and whistles...
Great to see the Note 2 is continuing. Leaving for one plus one. Best of luck!!

frewys said:
Based on OP it sounds like it is in ever way shape and form the same.
Trying to figure out why I should prefer this over official.. No added bells and whistles...
Great to see the Note 2 is continuing. Leaving for one plus one. Best of luck!!
Click to expand...
Click to collapse
Some folks really want to have a build that doesn't show some other phones build ID. Those folks may not be numerous but they are around.
I may play with it after I figure another project I'm working on. If I feel I'm wasting my time building it, I'll stop. I thought the AT&T community might want something like this as I was putting a similar build together for the T-Mobile community.

Coug76 said:
Some folks really want to have a build that doesn't show some other phones build ID. Those folks may not be numerous but they are around.
I may play with it after I figure another project I'm working on. If I feel I'm wasting my time building it, I'll stop. I thought the AT&T community might want something like this as I was putting a similar build together for the T-Mobile community.
Click to expand...
Click to collapse
the builds are functionally the same(right?)

xda1zero said:
the builds are functionally the same(right?)
Click to expand...
Click to collapse
Yup. They are purely CM source home builds.
Eventually I will start doing subtle things to try learn more. Any changes to the I317 ROM will be tested on the T889 ROM first and documented in the OP.
If anyone out there has flashed this, how is your network being reported? Does it show AT&T?
New build is up.

Thanks for bringing this over to ATT, 6/18 running rock solid so far.
EDIT: Found a bug this morning, while the headphones are plugged in and play music is going the music will stop once the screen shuts off

Does this ROM have the camera blobs or whatever the correct term in it? I'm running OmniROM right now because they do and my photos have been significantly better.

edfuhr1 said:
Thanks for bringing this over to ATT, 6/18 running rock solid so far.
EDIT: Found a bug this morning, while the headphones are plugged in and play music is going the music will stop once the screen shuts off
Click to expand...
Click to collapse
I can't duplicate your bug on my T889. Both play music and Apollo work fine for me when the screen shuts off or times out. Are you running any battery saving settings?

New build posted in OP. Nothing changed other than the CM nightly changes and those from source. In what spare time I have I am digging through what I can find for ways to address the little things that bug me.

New build posted.
Hastily spouted for your befuddlement

Does this have the camera blobs and all that junk? I'm not sure on the specifics.. I was going to try and roll my own rom to learn, but then I saw this thread!
Thanks for your work, going to give this a test shortly.
EDIT: You might wanna fix that spelling error in the thread title too!

tetrahedonism said:
Does this have the camera blobs and all that junk? I'm not sure on the specifics.. I was going to try and roll my own rom to learn, but then I saw this thread!
Thanks for your work, going to give this a test shortly.
EDIT: You might wanna fix that spelling error in the thread title too!
Click to expand...
Click to collapse
This build is strictly CM without edit. If there is a compelling reason to change something I might, the only thing I am spending time on presently is the carrier labeling bit.

Coug76 said:
This build is strictly CM without edit. If there is a compelling reason to change something I might, the only thing I am spending time on presently is the carrier labeling bit.
Click to expand...
Click to collapse
The camera blobs (the ones Samsung released that are included in OmniROM these days) significantly improve camera performance and clarity. You might wanna take a look. Thanks for the reply too!

tetrahedonism said:
The camera blobs (the ones Samsung released that are included in OmniROM these days) significantly improve camera performance and clarity. You might wanna take a look. Thanks for the reply too!
Click to expand...
Click to collapse
IIRC they broke my OmniRom home builds camera. I might mess with them on my Omni home builds. It will take a while and I doubt I'll add them unless it makes a huge difference and documenting the change is easy.

Coug76 said:
IIRC they broke my OmniRom home builds camera. I might mess with them on my Omni home builds. It will take a while and I doubt I'll add them unless it makes a huge difference and documenting the change is easy.
Click to expand...
Click to collapse
Understandable! Good luck!