yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] madmack:
It will definitely help us going forward. If we get this fixed, we will have a complete open source audio hal. We will basically be on par with all other gsm variants for the other drivers (i9300, n7100.. etc). So from this point onward, if they get 4.2+, we do as well. First is first though, we gotta fix that audio issue before we think future.
[AT&T Samsung Galaxy Note II] MonsterBandit:
Not to mention having open source audio should hopefully gain us offical CM support so it will add more minds to development.
[AT&T Samsung Galaxy Note II] Dazog:
Sorry but read his post he asked what would the devs have to do POST 4.2 Unless you have a crystal ball to tell us what google is planing no one knows, so don't be quick to say FAIL and bash people, please read.
[AT&T Samsung Galaxy Note II] MonsterBandit:
Yes he did ask about post 4.2, it was a great question and jug responded with a great answer saying that we aren't sure but more likely then not some work will have to be done but not to the extent of what madmack is doing now....
[AT&T Samsung Galaxy Note II] codeninja99:
Not to fire up the people again, per that guys comment and simple "Who knows" , "We dont know" would have worked.

The audio file is coming soon as per madmacks request :)
[AT&T Samsung Galaxy Note II] epicbeardman911:
Sorry, but what exactly do you mean with no in call audio

Phone calls don't work all together?
[AT&T Samsung Galaxy Note II] codeninja99:
As promised here is the other file asked to decompile: https://docs.google.com/open?id=0B0g-ojj_rL70OXVOR2thV0VRdEU

If you feel the need to donate to me and thank me here is my link: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=UADHYRAX78AFQ
[AT&T Samsung Galaxy Note II] jug6ernaut:
Im going to assume you only read the first line of my post and ill leave it at that.

Nice. Good work.
[AT&T Samsung Galaxy Note II] codeninja99:
@madmack

Since i provided you these two files.

Could you do me a favor? Fix up CM10. Data / Audio and perhaps BT?

That would be cool. Id love to use it as a daily. But, those 3 things are very annoying. hope thats not too much to ask
[AT&T Samsung Galaxy Note II] madmack:
what data issue? I'm not aware of any BT issues either.

The audio issue is not a priority at the moment given that we're moving away from the stock hal and these wonky volume issues are due to that. but If you can play around with default_gains.conf, the problem is most likely there. Change all volumes from 96 to 100 and let me know if it works. If it does, we'll push these changes and release a new build.
[AT&T Samsung Galaxy Note II] jug6ernaut:
No idea on data issues. BT has range issues, u loose a good (audio at least) connection beyond like 10'. Where stock roms have good range well > 30'.
[AT&T Samsung Galaxy Note II] mjwhirly:
I believe the data issues he's talking about at least from what I remember from the irc chat log is that the connection seems to always be changing from 4g to H to 3g, and never staying at a stable one for a while... But I didn't seem to have that problem when on cm10,what I did notice was that the modem seemed weaker for example when in my basement when on cm I would have either one bar at 3g or no service at all, while on touch wiz I would have 2 bars of H+ at all times minimum, though this could have been due to me sitting in different spots when I was looking as my basement is quite large
[AT&T Samsung Galaxy Note II] jug6ernaut:
I also can only speak from personal experience but i haven't had any issues with constant switching or lack of reception. Maybe i always have really good reception? Idk.
[AT&T Samsung Galaxy Note II] madmack:
download setcpu and set min freq to 1500. Try pairing your device again, does it work better? It could be a voltage starvation issue.

The radio switching between 3g, + and 4G is normal. This is the way it is intended to work. The radios down scale to save your battery.

Next time guys please direct your observations, requests and dev questions in the appropriate thread. This is strictly 10.1
[AT&T Samsung Galaxy Note II] jug6ernaut:
ill try that.

& arg ur right sorry, apologies.
[AT&T Samsung Galaxy Note II] mjwhirly:
Was only answering your question that's why I brought up cm10, will try and keep this thread on topic from now on.
[AT&T Samsung Galaxy Note II] jug6ernaut:
i locked cpu at 1500 and 1600mhz and also plugged phone into power nether seemed to have any effect on bluetooth audio skipping.
[AT&T Samsung Galaxy Note II] peoples_flip:
I'm using your CM10 and it works great... Looking forward to getting 4.2 on my Note II
[AT&T Samsung Galaxy Note II] volcomguyaz:
Yes its sweet... we all are brother. Someone here is

close I can feel it in my bones!
[AT&T Samsung Galaxy Note II] Entropy512:
As far as post-4.2 - remember, all of the current exynos4 maintainers are retiring... Hell, we barely can motivate ourselves to **** with this **** at all any more as it is. So basically, any post-4.2 work is going to be done by an entirely new team. So far that's just madmack and maybe sbrissen.
[AT&T Samsung Galaxy Note II] MonsterBandit:
Id love to learn from the master...nudge nudge wink wink...lol...i haven't had the pleasure to enjoy your work for these devices but in my limited interaction with you, you've been a gentleman and a scholar and ive learned a lot...and i thank you sir
[AT&T Samsung Galaxy Note II] slick_rick:
Seems like it. Madmack on GSM side and sbrissen on CDMA side for the US GN2 variants.
[AT&T Samsung Galaxy Note II] codeninja99:
I just hope my decompiles help.
[AT&T Samsung Galaxy Note II] Entropy512:
That's pretty much for madmack.

We have gone through a few rounds of hwcomposer decompiles, and it's enough to demotivate us... It proves just how full of bull**** Samsung was when they made their promises in October.

As is obvious - decompiled source code is a royal ***** to read - EVEN if you do the iterative process of "hinting" hex-rays with headers and such.

I might do another round of such things with HWC next week... but it's just really hard to motivate ourselves these days.
[AT&T Samsung Galaxy Note II] codeninja99:
The motivation is to make it work. Last I checked people do this stuff because it "cant be done" and want to do it to show it "can be done". its fun so im told. So unless im missing something. I see plenty of motivation.

If motivation is money? Im sure people would be more then willing to donate to keep these devices maintained and working proper.

Again, this is my two cents.
[AT&T Samsung Galaxy Note II] lennie:
It's easy to say when you're not the one doing it. I Just my 2 cents
[AT&T Samsung Galaxy Note II] Entropy512:
Exactly. I've spent hundreds of hours making Samsung's devices more attractive to a particular user base, and they have done nothing in return but lie, violate the GPL (and lie about it), make promises they never deliver on (nearly every post in SamsungJohn's posting history, and the spectacular failure that was their big BABBQ announcement), and throw grenades in the face of the community like I9100 XWLPM.

I do this because I want to make my device better - I fundamentally can't do that with a Samsung, especially an Exynos-based Samsung, as I am constantly reverse engineering EVERYTHING to fix it. Now, on almost any device there's some amount of RE that needs to be done - but on Exynos-based Samsungs the list is without end and at some point you just say "**** it, even if I fix this, all these other things will be broken and I have better things to do with my time."

See, for example, the Xperia T - it's in such good shape that the only things remaining for 10.0 are:

WPA tethering (already fixed in 10.1 thanks to a newer kernel)

HDMI scaling of anamorphic video (this **** doesn't work at all on exynos4 in AOSP)

Polish of little stuff, like making the brightness control a bit more user-friendly

As to why 10.1 hasn't gone to nightlies yet - the team decided to pull an Aries and rebase onto the Mako kernel and as many Mako HALs as possible, which takes quite a bit of time when you first do it but pays off in the long run by making it easy to update for new Android versions (see the Galaxy S1 series). Doing something like that is unimaginable on an Exynos4 Samsung, partly due to the list of closed-source broken blobs being WAY too long and partly because we have no reference source that is updated in a timely fashion to rebase onto.

It leaves me the time to focus on some of my other hobby projects which I have not had the time to even think about thanks to Android hacking, or to focus on more interesting projects like a "deep dive" down into a power management subsystem somewhere.
[AT&T Samsung Galaxy Note II] codeninja99:
So, in short. we wont be seeing any official CM support for these 2 devices.

So, it seems quite simple to me. sbrissen / madmack / cmnerd / whoever else knows this base helps. cmerd is maintaing his AOKP port and I must say its much more fluid, because hes using blobs from 4.1.2 INTL version (LTE)
[AT&T Samsung Galaxy Note II] Entropy512:
If madmack has success it'll get officially merged and he'll be maintainer... but past 4.2 he's likely on his own. :)
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
hey guys im preparing to go to officer training for the air force, so i literally have no time. but has anyone checked the new origenboard?

http://www.origenboard.org/wiki/index.php/Resources#Samsung_Exynos_4412_Origen_Quad

http://www.origenboard.org/wiki/index.php/WiKi

seems like they added guides for exynos 4412 boards.
[AT&T Samsung Galaxy Note II] Kevin36:
I was just checking the n7100 thread and they have all kinds of 4.2.1 and cm10.1 running perfectly is thier device that different from our maybe we can find the missing files over at there roms
[AT&T Samsung Galaxy Note II] MonsterBandit:
Different hardware...thats the issue
[AT&T Samsung Galaxy Note II] Kevin36:
we have ports from thier roms and they work fine
[AT&T Samsung Galaxy Note II] MonsterBandit:
Yes but with blobs and HALs that aren't wanted/needed...and most of what we have ported over is 4.1 mainly because thats what the phone came with and things work with minimal difficulty...with 4.2 those things changed...and when madmack got cm10 in call audio working he basically posted and moved to 10.1 and in call audio broke...and in order to get that working without all the blobs and HALs hacked together, open source was the way to go...and with Samsung not releasing ANY docs on Exynos stuff (no routing or how things are talking to eachother) its not easy and may not happen...we will all have to wait and see.

So one correct me if im wrong or missed something.
[AT&T Samsung Galaxy Note II] mjwhirly:
Well the good thing is that Madmack will have some extra help soon if we can raise the money:fingers-crossed:

http://xdaforums.com/showthread.php?t=2094919
[AT&T Samsung Galaxy Note II] sheep_duck:
Wow. Okay then this is awesome news. Him and madmack together will be a huge deal for our device... rejoice!
[AT&T Samsung Galaxy Note II] MonsterBandit:
Count me in for 10
[AT&T Samsung Galaxy Note II] tino_b:
I'll be paid next Tuesday so I will be able to donate until then...
[AT&T Samsung Galaxy Note II] codeninja99:
There is a thread to donate a device to codeworkx its in general. I got official support if we can get the money for a device for him
[AT&T Samsung Galaxy Note II] madmack:
awesome news :) that guy is the most experienced cm maintainer that I know for exynos devices.
[AT&T Samsung Galaxy Note II] mjwhirly:
Yeah things are about to get interesting here:D
[AT&T Samsung Galaxy Note II] fightingcrest:
Any word on the remaining balance?
[AT&T Samsung Galaxy Note II] MonsterBandit:
If they were interesting enough already...lol...with madmack getting is this far, codeninja decompiling stuff with hex, and now CW might be joining the mix...not to mention entropy droppin in every once in awhile...im more excited then a 5yr old xmas morning...lol
[AT&T Samsung Galaxy Note II] jerdog:
Seeing as this is not official CM and is not original work, this will be moved to Android Development.
[AT&T Samsung Galaxy Note II] dw9906:
I somewhat disagree. Lots of original work went into this. But ok
[AT&T Samsung Galaxy Note II] madmack:
no original work? no one had anything remotely as close as this for any exynos lte device. we literally have everything working except in call audio which we're actively "originally working on".

my original work can be seen in my github commits.

Sorry bud, this doesn't belong in the development section. Please bring it back where it belongs.
[AT&T Samsung Galaxy Note II] dw9906:
Totally agree!

---------- Post added at 09:06 AM ---------- Previous post was at 08:51 AM ----------

You know, you Mods are always telling people to read read read before posting. Then you guys drop in on a thread without reading any posts but maybe the last two and without doing any kind of research and just shut down or move a thread. Had you done any reading whatsoever, then you may have realized what you said and did was wrong. Just because he didn't code any of the particular "features" doesn't mean a lot of time and original work didn't go into this. But....I'm sure you'll do what you want anyways. What do I know, I just post here.
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
you're right it's not official CM, but it's pretty darn original....
[AT&T Samsung Galaxy Note II] jerdog:
Guidelines for inclusion in Original Dev:

Good work is going on here.
[AT&T Samsung Galaxy Note II] v36sedan:
Is there anyway to get this to work on the vzw note 2?
[AT&T Samsung Galaxy Note II] madmack:
stop it man. the very bullets that you're quoting apply here:

Please bring this back. This is borderline offensive frankly and is becoming a joke. How do you expect devs to be motivated in your forums when you're downgrading their threads unjustly. I've rarely seen as open a discussion as the one I'm providing here where I post my findings, methods of porting, and my custom additions in these details. Taking this off of "original work" is unacceptable.
[AT&T Samsung Galaxy Note II] MonsterBandit:
For madmack to become the maintainer he has to have it merged with CM, its not. and his focus has shifted to 10.1...rightly so there is a ton of "original" work put into this ROM, and yes there are parallels to the n7100 but that doesn't mean this should be moved just beacuse its not official....secondly he's obviously working to become the maintainer of 10.1, no one else is. Yes we, as the note 2 community are working to get more ppl like codeworks behind this, madmack still is the first to work on 10.1, its his defconfig that was merged into CM, he is the only one actively working to get in-call audio working to get official support, he is also the only dev i've seen go into the detail he's gone into in these threads to show what he's done, whats wrong, whats broken, potential fixes or areas to look at to find fixes. These two ROMs, IMO, are both original to this device i317 an lte phone, not the n7100 a non lte phone (notice the hardware differences, which requires original work to be done to make the different hardware work). Fine, move the CM10 as official support is unlikely but keep the CM10.1 thread, its not like madmack isn't working toward official support...

we are behind you madmack
[AT&T Samsung Galaxy Note II] MarcianoS:
Indeed, move this thread back. Just ask entropy512 how hard it is to do what madmack is doing here!!!
[AT&T Samsung Galaxy Note II] DAGr8:
Please dont take this the wrong way both of you..

I tend to agree this is somewhat debatable if this is deemed original or not (as per xda standards ofc).. ive always consider my tw work as original(pushing boundaries making front page being unique etc etc) yet ive never seen it moved' up'..

Part of the problem is there is something elitist about this original section... ive brought that up in the past and got ignored way to much stuff is allowed in 'standard' dev section taking away from the 'real' development

If you guys grant us our ported rom section you will then see only a hand full of roms and imho that would give this thread the visibility it deserves ..

@mod visibility here is a key word nobody other then us here will make this happen exynos is being hated on and without threads like this no roms will ever be posted in this section might aswell remove it all together..
[AT&T Samsung Galaxy Note II] Entropy512:
We've had their reference source for ages. The "big changes" they promised at BABBQ were bull****. Also, the audio chips used on OrigenBoard are not present on any phone or handset, and also, the OrigenBoard doesn't have a cell radio. Guess where the Exynos4+LTE devices have problems? The modem/radio interface!

For more on how worthless their reference source is (it's older than anything that has ever been used to produce a shipped firmware release for any device) - https://plus.google.com/u/0/101093310520661581786/posts/ZEKu52oo8cA

Different modem with different way of controlling its audio.

If any thread deserves original status it's this one - this is pretty much where any work I know of in terms of integrating libcsd-client support into the wm1811 audio HAL is being done.
[AT&T Samsung Galaxy Note II] jerdog:
Guys - after talking with Entropy it's agreed this can go in Original Development. Technically works like this do not qualify, but the level of work being done is above those other works.
[AT&T Samsung Galaxy Note II] madmack:
@Entropy512. Thanks for chipping in.

Back to libcsd work.
[AT&T Samsung Galaxy Note II] Entropy512:
Actually I had an idea...

We have the relatively new "Note II Development Discussion" forum for items that are common to all Note II units.

I think a possibly good approach might be to move this there, rename to something like "MDM9615 Call Control Discussion" - since that is THE big blocker in terms of getting all Exynos4+MDM9615 devices working (I9305, N7105, I317, and the Tmo/VZW/Sprint variants).

Of course, no more user discussion would be permitted but that would help the SNR.
[AT&T Samsung Galaxy Note II] madmack:
I don't mind that but I personally prefer to keep the thread here.
[AT&T Samsung Galaxy Note II] MonsterBandit:
as an non-dev looking in and trying to learn about this stuff that sounds like a great idea, you might have more developer eyes looking at it from different angles...would def. add to this...just my .02

edit: you could still keep this thread, just add another to the dev section for more advanced discussion
[AT&T Samsung Galaxy Note II] ceo.mtcl:
No offense but what a wasteful discussion you added to the development of this rom in past few pages. Why don't you do such discussions in private messages like you recommend regular users to do?

Now, if you can please do your job and cleanup this thread with your and other non development related discussion you started then that would be nice.
[AT&T Samsung Galaxy Note II] pickneters:
Forgive me for just missing stinging stupid, but I'm on PA which is an aosp base correct? I have no audio issues... Couldn't we use anything from that ROM? Again I know absolutely nothing about ROM development, just basic Linux guy here... If I wanted to learn so I can contribute any recommendations?
[AT&T Samsung Galaxy Note II] slick_rick:
That PA build is based off Android 4.1.2 and madmacks CM10 source. CM10.1 is a whole different ballpark when it comes to audio.
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
Dude... Im not trying to cast you down, but it is your part to read literally all the post to catch yourself up to the current post. Ill explain this time but please read all the pages before asking.
[AT&T Samsung Galaxy Note II] mattern1974:
Did in call audio work?
[AT&T Samsung Galaxy Note II] jug6ernaut:
ppl, this is a DEVELOPMENT THREAD. Stop with the bs posts please.
[AT&T Samsung Galaxy Note II] oka1:
From the moderator

People....... this is development thread....... stay on topic post respectfully or

......Do Not Post..........

Thanks. ~~ oka1
[AT&T Samsung Galaxy Note II] tyshemi:
Operation iron fist needs to be in operation imo
[AT&T Samsung Galaxy Note II] faslane:
Pls forgive my ignorance..lol What is meant by no in-call audio? Because I see what IS working is the speaker audio and headphones....does this mean if using handset audio I won't hear but if I use speakers and/or BT it will? Thanks a million and You ROCK!!!!

---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------

so, by no issues did you handset audio work ok? Thanks :)

---------- Post added at 06:43 PM ---------- Previous post was at 06:22 PM ----------

By no issues so far, do you mean the handset audio is working also?

Thank you :)
[AT&T Samsung Galaxy Note II] tino_b:
In-call audio bug in this ROM means that even though u can place a call or receive a call, u will NOT be able to hear the person on the other end nor the other party will be able to hear u. You are pretty much left with an expensive mp3 player with Internet access and running jelly Bean 4.2.1; however, madmack is working on an audio fix for this build. Everything else works fine.
[AT&T Samsung Galaxy Note II] MonsterBandit:
I don't want to sound like im asking for an ETA, cuz thats not cool...i did however wanted to see if you've made any headway? And i wanted to see how you're manipulating the libaudio-ril.so file?
[AT&T Samsung Galaxy Note II] madmack:
here is a little status update coz I know how much you guys love em :

we're close to getting cm10.1 with stock audio hal (read: closed source samsung stuff) that I used in cm10 running.

This should pave the way for official support but with the stock hal kinks. Once we roll this out, we'll continue working on disecting the decompiled library to hopefully get open source audio rolling eventually.

In any case, I don't think we're far from seeing official cm10.1 support. No precise ETA. We'll also try to roll one ROM for three devices : at&t's, tmobile and the international variant.
[AT&T Samsung Galaxy Note II] sheep_duck:
Nice! Hopefully codewordx gets his device soon and then we can get some serious **** going down in here!

Le super excited ^_^
[AT&T Samsung Galaxy Note II] :
Madmack: What Gapps package do you recommend for use with your new build(s)?
[AT&T Samsung Galaxy Note II] madmack:
I'm still using the one indicated by the OP even with the new test builds.
[AT&T Samsung Galaxy Note II] mykeldrip:
No disrespect to codewordx because he will be a huge help to mad and team...but I feel we already have some serious **** going down so good job mad and guys already making huge headway in this!!
[AT&T Samsung Galaxy Note II] mjwhirly:
Should we be expecting a new test build soon ;-P I see a lot of action on the irc logs
[AT&T Samsung Galaxy Note II] turilo:
I believe ril has been updated for audio or am I wrong?
[AT&T Samsung Galaxy Note II] madmack:
yes, very very soon.

:good::good: the recent 10.1 test builds are working like they did in cm10 in terms of in call audio and what not.
[AT&T Samsung Galaxy Note II] dkotoric:
Can't wait
[AT&T Samsung Galaxy Note II] otisman:
So three calls and audio or still no audio much alohas

Sent from my SGH-I317 using Xparent Red Tapatalk 2
[AT&T Samsung Galaxy Note II] madmack:
cm10 doesn't require three calls anymore. cm10.1 won't either. it'll just work on first call.
[AT&T Samsung Galaxy Note II] otisman:
Sorry madmack so with the latest build up in the op in call audio works that what I was asking much alohas

Sent from my SGH-I317 using Xparent Red Tapatalk 2
[AT&T Samsung Galaxy Note II] mjwhirly:
No it doesn't, he said the test builds (the ones between probably him and codeworkx) having working call audio, very soon he will post a new build for us to mess with