yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] chrisaw:
I do completely see your points and agree with them to a degree *BUT* the situation is this - the Linux kernel source tree is released entirely under GPL. The license agreement of GPL dictates that if you modify the source code in ANY way, you must provide source code upon request. The people who are building these kernels are breaking that license agreement. The fact is - those guys are taking an open source project (Linux), using its source code and then breaking the terms of its license agreement. It's a pretty scummy way to develop since it means if there are indeed any improvements in that kernel, we don't know what they are because the source code isn't released.

Basically, it's a very scummy tactic and isn't tolerated on xda-developers. If you torrent or break your Samsung TOS, you hurt yourself and possibly Samsung. If you don't release your source code you hurt the XDA community and that just plain SUCKS! :)

Hope this is clearer now - it's not about being an 'angel' - it's about sharing what you learn so that others may learn too. Most open source projects are a community effort - if nobody shared, nothing would ever improve.
[AT&T Samsung Galaxy Note II] jug6ernaut:
I don't think you understand. For example, posting TriangleAway in itself is not illegal in any way, it may void your warranty if used, but thats on the user.

Posting a kernel without source by it self IS ILLEGAL. Its not a matter of not liking it, XDA is on the hock when ppl do this. Even posting links is endorsing this. There is no grey area to it.

Maybe someone else can explain this better.
[AT&T Samsung Galaxy Note II] LvDisturbed1:
Read this. Posting a kernal without the source is breaking the GPL, and as such, linking to such kernal is against XDA rules. I understand your intentions are good, but rules are rules.
[AT&T Samsung Galaxy Note II] mjwhirly:
30GB is not enough space to be able to compile multiple builds on CM. Look towards this thread for help setting up your build environment, most of it will be useful up until the first part of step 6, where the rest is intended solely for the Skyrocket build.

http://xdaforums.com/showthread.php?t=1798056

---------- Post added at 04:19 PM ---------- Previous post was at 04:12 PM ----------

I appreciate you all clearing it up for me, I understood that not having your source available is against GPL, just didn't realize having a link to it was such a big deal. Would hate to get XDA in trouble for it, and I also wasn't trying to attack Entropy512 about it. I think i was just excited to see another kernel available for our phone and felt personally attacked for posting a link towards it but now see that it was me at fault. I apologize for bring this thread off topic, but hopefully this while clear up the rules of XDA for others as well.
[AT&T Samsung Galaxy Note II] MonsterBandit:
no worries dude...hat tip for the kernel tho if only he did have his source tree available it might help madmack with something he didn't know or missed that might help with open source audio...and it looks like that kernel still breaks exfat sd cards...thats the issue im having now...trying to get that sorted...just not sure where to begin...couple of the guys have looked at my logs and still got nothing lol
[AT&T Samsung Galaxy Note II] LvDisturbed1:
Thanks for the link. This should definitely be helpful.
[AT&T Samsung Galaxy Note II] Woody:
GPL issues aside because that is a whole other ball of wax there. The link you posted was to a forum that requires registration to download and view items posted. So if it wasn't a GPL issue, then it was an XDA Rule 11 violation.

Seems from the past few posts that lesson learned.
[AT&T Samsung Galaxy Note II] mjwhirly:
AHHHH!!!! Too many rules to keep track of lol and yes the past few posts helped clear it all up, I will be more careful next time before I post :good:
[AT&T Samsung Galaxy Note II] otisman:
Does the kernel work this ROM away

Sent from my SAMSUNG-SGH-I747 using Xparent Red Tapatalk 2
[AT&T Samsung Galaxy Note II] LvDisturbed1:
Ok almost ready to compile...just need to know how to use sources from madmack so I can sync. I don't know what I'm looking for. The guides show how to build from CM source...but how do I use madmack's? What exactly so I do after making a work directory?

$ repo init -u git://github.com/CyanogenMod/android.git -b jellybean

What do I type instead of this? And what about the local manifest.xml? Where do I find it?
[AT&T Samsung Galaxy Note II] chrisaw:
If you're just trying to get the latest version of this - it's at the bottom of post #1. I would assume anyone who is planning to do development work would already know this stuff. Essentially, you need to pull the base CM source tree as you mentioned (correct command), then pull the extra components to the relevant directories from github.

As I say though, you wont need to go to this length just to use the latest build. :)
[AT&T Samsung Galaxy Note II] :
This has been a remarkable build as far as stability goes. I've been running this for the last week? Nary a hiccup. Hats off!
[AT&T Samsung Galaxy Note II] dw9906:
No offense, but the second post tells you exactly what you need to do. http://xdaforums.com/showthread.php?p=34897600
[AT&T Samsung Galaxy Note II] dman3285:
Just in case y'all missed it.

http://github.com/CyanogenMod/android_device_samsung_t0lteatt

Official support...:thumbup:
[AT&T Samsung Galaxy Note II] cashyftw:
That's awesome!

Sent from my Galaxy Note 2
[AT&T Samsung Galaxy Note II] LvDisturbed1:
No offence taken. I have never used ubuntu (or any other linux distro) before and am not familiar with how to pull files from git. I understand the second post says what to do...I just didn't know how to do it! Its all a learning experience for me, and I am starting from rock bottom. That said, I figured out how to pull the files using

git clone "address of repo here"

so I can finally proceed. Gotta crawl before you walk so to speak, but I'm falling on my face trying to crawl. Feel free to tell me I'm in over my head.

EDIT: And I ****ed up somewhere because I'm getting an error trying to build.

$ breakfast t0att & make
[1] 12744
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:196: *** _nic.PRODUCTS.[[device/samsung/t0att/android_device_samsung_t0att/full_t0att.mk]]: "hardware/samsung/exynos4x12.mk" does not exist. Stop.
cameron@cameron-Aspire-5750:~$ build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/t0att/cm.mk]]: "hardware/samsung/exynos4x12.mk" does not exist. Stop.
Device t0att not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for t0att not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/t0att/cm.mk]]: "hardware/samsung/exynos4x12.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_t0att'
** Do you have the right repo manifest?

Looks like I'm missing exynos4x12.mk file...I sync'd with CM repo...and put madmacks sources in the relevant directories so WTF! I'm sure it's something simple and it's just laughing at me...
[AT&T Samsung Galaxy Note II] :
If I read that branch right it's 10.1. Even better.
[AT&T Samsung Galaxy Note II] madmack:
I did indeed miss it. Thanks man :good::good:
[AT&T Samsung Galaxy Note II] pvtjoker42:
Hopefully now with official support we'll see nightlies soon!
[AT&T Samsung Galaxy Note II] codeninja99:
Do not count on it.
[AT&T Samsung Galaxy Note II] dman3285:
Nice positive attitude.. that's what they said about the captivate glide. Now were getting support.. have faith..:thumbup:
[AT&T Samsung Galaxy Note II] turilo:
Oh codeninja99 go play with your iphone 5 than :p
[AT&T Samsung Galaxy Note II] codeninja99:
Just saying don't count on anything soon. If there are enough of us here. We can set up a Jenkins build bot.
[AT&T Samsung Galaxy Note II] madmack:
Koush wrote in the other thread that this tree is for CWM only. So we aren't going to get help with that.

My defconfig has been merged in CM10, I can get us official support (read: nightlies) with a little more effort so stay tuned. We're working out the little remaining issues. Mainly naming stuff.

I was hoping to fix audio and make it work with open source instead of HAL before we get official but I might have to just accept things the way they are now given how hard it's been to fix that in call audio problem that we have.
[AT&T Samsung Galaxy Note II] arthurbrownleeiv:
Will this only be for the I317? Or with a little work can we get the T889 included?
[AT&T Samsung Galaxy Note II] madmack:
should work as is on the t-mo note 2.

flash it following the OP's instructions
[AT&T Samsung Galaxy Note II] codeninja99:
Works fine on the t889 . With the known quirks. I'm on it now
[AT&T Samsung Galaxy Note II] shadow666:
It works fine, been using it without flashing anything else, kernel or modem.
[AT&T Samsung Galaxy Note II] truthkillszz:
Out of curiosity I have been running the 12/13 build since its release and i noticed my battery not lasting as long as it did on TW. Has anyone noticed less battery life on this build?
[AT&T Samsung Galaxy Note II] codeninja99:
Ah its not exactly official nor beta even. Lot of debugging and other stuff so yes you will notice drain
[AT&T Samsung Galaxy Note II] madmack:
I have similar battery drain to stock.

try finding the culprit using betterybatterystats or similar apps. Look for wakelocks
[AT&T Samsung Galaxy Note II] ManelScout4Life:
madmack, I built two other aosp ROMs today and for some reason when they both boot up the phone.process crashes non-stop, the baseband is unknown and there is no service.

I've played with them all day but can't figure it out, any insight?
[AT&T Samsung Galaxy Note II] slick_rick:
Sounds like you arent cherry picking the RIL from CM review.
[AT&T Samsung Galaxy Note II] ManelScout4Life:
I manually added it because adding the commit (the way I know how) would replace the framework base with the cm one.
[AT&T Samsung Galaxy Note II] slick_rick:
It doesnt replace the whole frameworks/base directory. It just places that file in there. Idk if thats what you thought?
[AT&T Samsung Galaxy Note II] madmack:
I agree.

RILJ issue. Make sure you compile the file that you pick to be in your build.prop. It always helps to look at logs in these situations as well.

Keep in mind the one in gerrit has been renamed. Rename it back to match whatever is in your dev tree.

if you're compiling mr1, make sure you use D2RIL, my file needs to be ported and I haven't worked on that yet.
[AT&T Samsung Galaxy Note II] ManelScout4Life:
So

git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/12/28212/6 && git cherry-pick FETCH_HEAD

?
[AT&T Samsung Galaxy Note II] slick_rick:
Yup. Just as OP says to do :)
[AT&T Samsung Galaxy Note II] ManelScout4Life:
Thanks guys, I'm pretty sure the name changing in patch 6 is what was throwing it off.
[AT&T Samsung Galaxy Note II] truthkillszz:
I went back to TW to compare the battery drain. I am going to restore my nandroid and monitor with betterbatterystats
[AT&T Samsung Galaxy Note II] madmack:
cleanup day.

I've been working on renaming the build from t0att to i317 and cleaning up some stuff that we no longer need to build 4.1.x.

1. The kernel requirement is gone given that my defconfig has been officially merged. You can just pull stuff from the CyanogenMod github account.

2. vendor and dev trees are updated to use i317 instead of t0att.

3. The framework RILJ requirement has also been renamed properly in the dev tree. You can pull patch 6 from gerrit and use that.

You now need to use "breakfast i317" instead of "breakfast t0att". I've updated the second post with the latest.

I'm currently compiling a fresh build with the latest from cm. Expect it to be up in a bit. It'll have the kernel patch for that mem write vulnerability as well.

To compilers: I've renamed my repo as well. Make sure you reflect that change in your local_manifest. The old t0att repo is gone.

Edit: links updated on the OP.
[AT&T Samsung Galaxy Note II] arthurbrownleeiv:
Yep, been running it. I was more wondering what it would take to get the T889 to be "officially" supported when the I317 gets official support. Considering how the devices are technically different models, I was just asking what would need to be done.

Thanks a lot for your work on this!
[AT&T Samsung Galaxy Note II] :
Running good so far. No problems. The last one was bullet proof so I'd expect this build to be even better given the quality of work you do.
[AT&T Samsung Galaxy Note II] xey3x:
I have a few scroll jitters which I did not have in the previous version, other than that smooth sailing so far!
[AT&T Samsung Galaxy Note II] redrider54:
which gapps are working for everyone?
[AT&T Samsung Galaxy Note II] madmack:
not much really. we'll need to replace the proprietary binaries with ones from stock tmom see if we need to change anything in the kernel config.. some renaming, and voila.
[AT&T Samsung Galaxy Note II] :
October.
[AT&T Samsung Galaxy Note II] baka2x:
md5 for the latest build?
[AT&T Samsung Galaxy Note II] madmack:
8317ff113741d18983283db57bcaf632
[AT&T Samsung Galaxy Note II] codeninja99:
Very nice. Going to flash the new one in a few. Glad to see things getting merged and renamed
[AT&T Samsung Galaxy Note II] baka2x:
Thanks to madmack for this. I just flashed this on my T889 and it's great. I will say that there is slight system wide lag like others are reporting.
[AT&T Samsung Galaxy Note II] tino_b:
- Computer [Check]

- ROM ]Check]

- Beer [Check]

Mission control, we're ready for some flashing... :silly:

Thank you madmack!
[AT&T Samsung Galaxy Note II] codeninja99:
On the new build now :)
[AT&T Samsung Galaxy Note II] tetrahedonism:
Just flashed it myself and it seems really... laggy. Everything is chunky and weird. I cleared both cache and dalvik, and it still seems to be running pretty slowly. Any suggestions?
[AT&T Samsung Galaxy Note II] Sebastianq28:
Can't wait for this to be official with no bugs! Haha so excited!
[AT&T Samsung Galaxy Note II] tetrahedonism:
A lot of us are. I could dance. But I won't due to apathy.
[AT&T Samsung Galaxy Note II] otisman:
Boooyaaaah this thing is sick and quick much alohas madmack as far as lag I'm good none what's so ever alohas bradahs

Sent from my SGH-I317 using Xparent Red Tapatalk 2
[AT&T Samsung Galaxy Note II] madmack:
Strange that you guys are getting some lag. Nothing has been changed in the hwcomposer/gralloc department. Could the memory leak bug fix be causing this? I'm not facing any over here.

You guys can try to load boot.img from the Dec 13th ROM and flash that by replacing the file in the latest zip file. See if it fixes the lagging problem. If it does, then it's the memory leak bug "fix" that is causing it.
[AT&T Samsung Galaxy Note II] otisman:
Lte speed is unreal on this ROM too

Much alohas

Sent from my SGH-I317 using Xparent Red Tapatalk 2
[AT&T Samsung Galaxy Note II] tetrahedonism:
I'll see what I can do!
[AT&T Samsung Galaxy Note II] prmcmanus:
I'm getting identical LTE speeds in comparison to stock ROM. I'm also getting a laggy ui with the latest build though. N7105
[AT&T Samsung Galaxy Note II] tetrahedonism:
That seems to have fixed it, now everything is buttery smooth. Hoooly craps. Ahah, thanks for the tip! If there's anything else you want me to try, let me know.
[AT&T Samsung Galaxy Note II] madmack:
great. I love it when first guesses are right !

I think codeworkx already knows about this issue. Let's wait til he fixes it. I can also provide the old kernel as a flashable cwm for those that want to override the current build with the old kernel without having to play with cwm files.
[AT&T Samsung Galaxy Note II] MonsterBandit:
sounds good to me...thanx
[AT&T Samsung Galaxy Note II] tetrahedonism:
I don't mind doing it myself and I can always upload it if you want, it's no big deal to me! Never hurts to wait either. I came from the Optimus 2X to this, so I'm fairly used to waiting. Ahah

Thanks for your work Madmack :D
[AT&T Samsung Galaxy Note II] madmack:
For those that are suffering from jerky/laggy UI, flash THIS FILE after flashing the Dec 26 build
[AT&T Samsung Galaxy Note II] tino_b:
I'm not getting any lag whatsoever... :)
[AT&T Samsung Galaxy Note II] codeninja99:
Same here no lag on Tmo. Just GPS sensors are whacked to hell.

Going to try to swap out the gpsd and not sure what else
[AT&T Samsung Galaxy Note II] tino_b:
GPS works fine for me.
[AT&T Samsung Galaxy Note II] fix-this!:
Any way to fix the incall volume? Love the rom but its a deal breaker when i cant hear whos calling me.
[AT&T Samsung Galaxy Note II] ManelScout4Life:
lower it and raise it and it will be very loud.
[AT&T Samsung Galaxy Note II] fix-this!:
I tried and that doesnt work. It doesnt happen all the time.
[AT&T Samsung Galaxy Note II] codeninja99:
Same here. Same issue.
[AT&T Samsung Galaxy Note II] ManelScout4Life:
fix permissions
[AT&T Samsung Galaxy Note II] fix-this!:
Done that too lol. Tried everything also happens on jellybeer.
[AT&T Samsung Galaxy Note II] codeninja99:
Did it here too.

Not sure if it will fix anything. But it seems to be on incoming calls and the GPS bug I said is not locking. Its when in Google maps it doesn't track
[AT&T Samsung Galaxy Note II] mikeyinid:
quick question madmack. trying to build now for tmo n2. no errors so far. I used your prop blobs, and modified your device tree. do you mind if I post it in the tmo section? im tired of my phone thinking its an att note. full credit will go to you.

also I notice the tmo note has a tree on cm git. is it good, or should I stay with yours?
[AT&T Samsung Galaxy Note II] antiochasylum:
As long as you compile it, I think he's ok with it.

That's not a device tree on CMs git. That's only for recovery. Stay with madmacks.
[AT&T Samsung Galaxy Note II] mikeyinid:
I didn't look aat it. when I started the build it said t0ltetmo already existed on cm git. idk.

and of course im compiling it myself. feel free to go through it
[AT&T Samsung Galaxy Note II] shadow666:
Making one for our beloved TMO would be greatly appreciated
[AT&T Samsung Galaxy Note II] codeninja99:
Using the blobs from the Att won't help much. Try to use the tmo files from stock rom
[AT&T Samsung Galaxy Note II] mikeyinid:
why wont it help? they should be almost the same. usable at least. and i didnt do anything but change some stuff to reflect that its running on a tmo instead of att n2. everything is the same.

anyway, not that it matters. build finishes but im not doing something right. no kernel and odexed apks. lol. idk, im a noob so i dont really know what to do next.
[AT&T Samsung Galaxy Note II] codeninja99:
When it gets to cm repo try. Till then just cross post with a edited build.prop for tmo pretty simple
[AT&T Samsung Galaxy Note II] ManelScout4Life:
Not sure why you're trying to build for the tmobile version when you could just flash the ATT one....
[AT&T Samsung Galaxy Note II] mikeyinid:
Because I have the tmo note. And really I'm just trying to get a decent device tree together for it so I can get aokp going. Guess it will just be easier to use everything as is. I'm kind of ocd, seeing the build info kind of bothers me.
[AT&T Samsung Galaxy Note II] deeznutz1977:
Mikey u got the note 2 huh?.!?.. Sweet. BTW. cmenard posted aokp for the Tmobile note 2 this morning !!!:)

http://xdaforums.com/showthread.php?t=2070240
[AT&T Samsung Galaxy Note II] mikeyinid:
Sweet. I stopped looking over there. Pretty dead.
[AT&T Samsung Galaxy Note II] codeninja99:
Well, For those on TMO and having GPS issues with this rom. I'd use the one cmnerd posted. It seems to be a prop issue. I tracked back today testing it and it landed me home 100% with no sat drops. All of the roms suffer the audio bug. which is an issue in the hal settings, I think the VZW/Sprint roms dont have this issue.

@madmack, Any news RE: Getting this merged? Id like to lend a hand, but, only when its merged.
[AT&T Samsung Galaxy Note II] madmack:
like they said, as long as you compile and put proper credits, im happy and more than fine with it. All of this is open source after all :)

no news. Apparently merging crap has changed recently. It used to go through vendor/cm and now its detached and has to be done via Hudson repo on github. its a chicken and an egg problem. We can add the device to Hudson only after we have the dev tree pushed to cm and so far I dont know who would push the dev tree for us.

understand that excitement isnt really there when you re talking about cm10. Everybody is merging cm10.1 so if we have that ready, it'll be a different story.
[AT&T Samsung Galaxy Note II] codeninja99:
Well. Cm10 is not exactly 100% . We all know the audio is not right. And the rilj is not 100% yet.

More and more kangs are being made which closes the doors on a merge. Hence why you will see most cm devices as preview videos and no source till its near 100%

I'll speak to jeff and Cody and few others later on and see if I can speed this up.

I mean you should be proud people are stealing your stuff. Must be half decent :p
[AT&T Samsung Galaxy Note II] cashyftw:
Cmeard, being a kanger? No.

Sent from my Galaxy Note 2
[AT&T Samsung Galaxy Note II] deeznutz1977:
Well he is part of aokp...... android- open-kang-project __lol :)
[AT&T Samsung Galaxy Note II] oka1:
From the moderator

To In this thread, Post Respectfully, stay on topic or do not post. If you have some Issue pm the Moderators and let us deal with it that is what we are here for........

Thanks ~~~ oka1
[AT&T Samsung Galaxy Note II] Entropy512:
If the I317 builds work 100% on T889, then maybe it's time for some assert/naming hackery...

There's a bit of pressure to try and cut down on numbers of builds when possible. For example one of my top priorities when I get home is renaming N8013 to N801x.

As to merging - tbh until the audio issues are fixed, I'm going to say no-go on a merge.

Merging the device trees would probably be via jeagoss - but he's going to come to codeworkx, myself, and others to ask questions, and I will personally no-go anything that's using blob audio. Yeah it delays the merge, but getting opensource audio properly working should eliminate all the wacky bugs and make future maintenance easier.
[AT&T Samsung Galaxy Note II] MonsterBandit:
i know you don't have a device...but any thoughts as to the audio issue? your imput is always appreciated

ignore you beat me to it in the other thread...thank you sir
[AT&T Samsung Galaxy Note II] chrisaw:
Fix in-call volume

I'm absolutely LOVING this ROM but the one thing that annoys me about it is the in-call audio so here's a fix I threw together:

Download https://dl.dropbox.com/u/9679985/default_gain.conf and run the following:

Now reboot your phone and you should be all set. You may wish to take a nandroid backup before attempting this to be on the safe side but it worked great for me. :)
[AT&T Samsung Galaxy Note II] drakeymcmb:
can u reupload it as an attachment to your post so people on mobile can download It thank you
[AT&T Samsung Galaxy Note II] chrisaw:
Sure, I've attached it as a text file - just rename the file, moved it in to place, change the ownership and permissions, reboot and you should be good to go. :)
[AT&T Samsung Galaxy Note II] madmack:
why not make a pull request? that way everybody benefits with the next release.
[AT&T Samsung Galaxy Note II] chrisaw:
Sure, will do when I get chance. :)

Edit: Done :)
[AT&T Samsung Galaxy Note II] fix-this!:
Thanks for the mod but it still doesnt fix the low volume when someone calls you.
[AT&T Samsung Galaxy Note II] brashmadcap:
Facebook

Anyone else getting really jumpy/erratic scrolling in Facebook?
[AT&T Samsung Galaxy Note II] pvtjoker42:
Not just fb that does it.. Most things that scroll like that do it for me..
[AT&T Samsung Galaxy Note II] devoureddreams:
only does it here, whenever it gets to the images other than that its fluid.
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
i experienced this on jellybeer. disabling hw overlay may help.