yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] MonsterBandit:
I'll give it a shot and report back...its not a huge issue but its enough to drive mW batty lol I appreciate the help thank you

Edit: SUCCESS!!!! Heres what I did for anyone else having this issue...I suggest using Mini Partition Tool Home Edition to do this...wipe all partitions off sd card and insert into phone...go to storage and try to mount sd card...it wont...try having cm reformat your sd card for you...it will hang on unmounting sd card...have no fear...remove sd card from phone...put into computer and fire up mini partition tool (MPT)...format partitions and fill with 0s...apply changes...create partition set it from Logical to Primary (VERY IMPORTANT)...change format to FAT32...apply changes...once done...pop sd card into phone and it should say "preparing sd card"...you have now fixed your sd card...yay...i just checked and rebooted phone...all is well...yay...thank you to madmack, and all who helped look at my logs...cheers
[AT&T Samsung Galaxy Note II] madmack:
awesome. Happy for you man. It was begging for a primary partition after all.
[AT&T Samsung Galaxy Note II] MonsterBandit:
so correct me if im wrong but it looks like CM merged our devices t0lteatt (vzw, spr, tmo, international) into their git a few day ago...Koush looks like he's working on our device...https://github.com/CyanogenMod/android_device_samsung_t0lteatt ...heres the link, but the site is down ATM...looks like its for the 10.1 branch..thoughts?

Edit: In looking at it, it looks like its just the initial merger, with really nothing of substance there...so a clean base to start from...looks interesting...i'll be watching that repo like a freakin hawk lol
[AT&T Samsung Galaxy Note II] madmack:
Wow ! Thanks man. This is very surprising to be honest. I'm not sure what to think, lol.

Here is what it does look like: CyanogenMod has two (more?) sets or blocks of maintainers when it comes to Samsung devices: TeamHacksung (codeworkx, xplodid..) taking care of most Exynos boards, and you have Koush, Cyanogen and others taking care of other branches and definitely the Qualcomm based S3's in the US. i.e. D2 variants.

I've so far contacted only teamhacksung members regarding my commits and merges. I wouldn't be surprised if Koush actually doesn't even know about the work I've done here.

I don't know if these two groups are in much contact at all seeing as that Koush just created a bare tree for our device (not forked) and the naming convention: TeamHacksung explicitly asked me to change the name of the tree from t0 to i317 because of their naming convention. I do know that we use samsung board names in CM like the D2s so it was a little confusing. And now of course we have Koush creating a t0 tree officially in the repos. lol.

This is awesome. I guess I should stop working on that little audio issue and start watching like you guys :) This will be an interesting one. Koush working on an Exynos device that I happen to own :laugh::laugh:. Is he going to use the smdk4x12-common tree at all? let's see. He is.

awesome find :good:
[AT&T Samsung Galaxy Note II] MarcianoS:
Madmack, sorry for stating the obvious, but I guess it would be useful if you contacted Koush & co. so they're up to speed on your efforts and achievements. Not to mention the fact that you deserve tons of credit for bringing up cm10!
[AT&T Samsung Galaxy Note II] MonsterBandit:
I can't take full credit i was really just "forwarding" dman3285's post from your original thread...but anyway...maybe try and get in contact with Koush...I think you should hop on with teamhacksung and him and maybe take a look at what you've done so far, a collaboration from you and those two teams with (for lack of a better term) a private gerrit could prove useful...have Koush look at what you've done so far and maybe they have a diff idea for something that might get open source audio working or at least some baby steps in that direction...just a thought...im so stoked now its not even funny lol

and i am proud to say i was the first to star and watch his git repo lol...im a loser i know
[AT&T Samsung Galaxy Note II] madmack:
In other news, my defconfig has just been merged into the official repos: :eek::eek: Koush should definitely see the work here. I have contacted him to hopefully prevent any more conflicts.

http://review.cyanogenmod.org/#/c/28214/
[AT&T Samsung Galaxy Note II] MonsterBandit:
sweet dude...i think you should keep pluggin away...you're already so far adding koush and the cm team will add a whole bunch of eyes and minds to work on this and tweak what you already have, open source audio should be that far behind esp with the addition of more minds...just my 0.02
[AT&T Samsung Galaxy Note II] codeninja99:
I said it would get merged. and magically they are working on 10.1 :)

The people that were on your commits @madmack had no clue what they did nor what they can do to the whole repo. So, extra people were pulled in who actually know.

Im glad to see your kenrel get committed. Get on gerrit some more and post stuff. if you find anything. the more help the better, thats the point of getting things merged.
[AT&T Samsung Galaxy Note II] MonsterBandit:
I know its kind of a long shot and a dream but I would love some of those guys from teamhacksung and/or koush stick their heads in here and share what they're working on...i think the idea that madmack started with being open about what he is doing shareing his troubles and showing us "beginners" a deeper view of how to build these ROMs...again just my 0.02
[AT&T Samsung Galaxy Note II] Koush:
Guys, this is just for recovery.
[AT&T Samsung Galaxy Note II] madmack:
hey Koush

Thanks for chiming in. Would have been nice to have you on board. :o

Time to put back my audio fixing hat
[AT&T Samsung Galaxy Note II] mjwhirly:
Well maybe it shouldn't be ;)
[AT&T Samsung Galaxy Note II] cdshepherd:
You made the front Page pal. Good job!
[AT&T Samsung Galaxy Note II] slicingtaco:
Ohhh, Here we go baby:silly:
[AT&T Samsung Galaxy Note II] madmack:
Thanks man, awesome :good::good:
[AT&T Samsung Galaxy Note II] Entropy512:
Looks like Koush already chimed in, but those were just for the purposes of building recovery.

It's possible to build recovery for a device with FAR less in place than what is needed for a remotely working CM bringup. Pretty much if you see Koush creating a repo within CM's tree, it means: He's working on official CWM recovery. It does not mean ANYTHING else in terms of whether a particular device will receive any official CM support.

See above. There's a possibility cyanogen himself might eventually mess with one of the Note2 variants (he owns one, not sure which), however it seems to be his work device. He really has been focusing on d2 lately.

Right now, I think madmack is the only one working Exynos4 + Qualcomm radio.
[AT&T Samsung Galaxy Note II] slick_rick:
Sbrissen is also but for the Sprint and VZW gnotes. Maybe you guys can run ideas off each other? I know he was focusing on getting audio working for his early CM10.1 builds.
[AT&T Samsung Galaxy Note II] codeninja99:
This is my idea. the variants are almost all alike except for the INTL version.

The idea would be to get an Exynos team together, madmack doesn't seem to like irc or gtalk, so, its quite hard.

Sbrissen and the others are all in #teamhacksung and other chans on freenode.
[AT&T Samsung Galaxy Note II] madmack:
Not very good at talking nicely are we.

*sigh*

I don't like gtalk, that's true. gtalk == personal life for me. friends and family, not exynos and xda.

Chat.. who said I don't like to chat in IRC? I don't know where that "seems" came from. I would like to share and discuss what we have. Heck, I could really use some help in that.
[AT&T Samsung Galaxy Note II] codeninja99:
I speak blunt. If you want help, hop on irc.freenode.net #teamhacksung look for cody and the rest. Possibly look for other note2 maintainers. Thats all I meant by it.

most of us all use gtalk, due to people being in diff time zones and other things. You can have more then one gtalk on your phone. for when you want to talk and dont also. Just as a idea for you.
[AT&T Samsung Galaxy Note II] antiochasylum:
Gotta love people trying to steal you work madmack. He said he compiled it... read the second to last post.

I imagine if he would have asked to port it you would have been OK. But saying HE compiled it, that gets on my nerves. And frankly should not be tolerated.

http://xdaforums.com/showthread.php?t=2062780
[AT&T Samsung Galaxy Note II] madmack:
damn.. that guy actually PMed me and asked if he can post in the t-mo section if he recompiles the work and I granted that. So much for "compiling".

thanks for pointing it out antiochasylum.. gotta love the XDA community. You guys got my back :)
[AT&T Samsung Galaxy Note II] Artimus009:
First off...Merry Christmas everyone.

Second...my chocolate milk shot out of my nose from lol'ing so much.

Thirdly... ITS A CHRISTMAS MIRACLE!!! THIS DUDE GOT BUSTED.

Back on topic now. Great build sir. Loving this rom.
[AT&T Samsung Galaxy Note II] antiochasylum:
You got farther than I was able to get with CM, so my up-most respect.

Of course I got your back, and anyone else who gives back to the community like you have. I may not have super super coding knowledge, but I know the android ecosystem and how it works front to back. There are many things to prove he did not compile it.

I wasn't going to post it in public. But someone else pointed it out. So game on.
[AT&T Samsung Galaxy Note II] slick_rick:
Yea wasn't going to let this guy rip you off madmack. Keep up the great work but like I said you should try and get in contact with sbrissen and I'll tell him about you. Both of you are fighting the same uphill battle with audio problems in CM10.1 two heads are better than one lol.
[AT&T Samsung Galaxy Note II] PlankLongBeard:
Hey Madmack, Im Currently Running the Build that Juggz Put Together for the Tmobile Note 2 but it Seems It Was a Copy with Juggz Changing the Build.prop I would like to know... Can I flash this 10.1 on my t889?

Thread Can Be Found Here: http://xdaforums.com/showthread.php?t=2062780

Thanks In Advance!
[AT&T Samsung Galaxy Note II] madmack:
flash the one in this thread. go with the original, stay away from copies ;)

I should modify the OP to indicate that its ok to flash this on the n7105 and the tmo note 2
[AT&T Samsung Galaxy Note II] tino_b:
Yes, you can, but you will not have in-call audio. I tried it on my T889 also and it works flawlessly except for that one known issue which is listed in the OP of this thread.

EDIT: Like madmack said, I am sticking with the original build and not the copy version...
[AT&T Samsung Galaxy Note II] MonsterBandit:
did you try making three calls to see if it fixes audio...its an "old fix" but it might work...if not then idk
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
.... he didn't compile anything. madmack, light him up!
[AT&T Samsung Galaxy Note II] tino_b:
I had to make the 3 calls on the DEC 8 release but for the DEC 13 it worked out of the box :) (this is for cm10). For cm10.1 I do know that in-call audio is a no go yet.
[AT&T Samsung Galaxy Note II] MonsterBandit:
yea i was holding out hope that thatfix might have worked...you just gave me a reason to find out...lol...i know hes working on getting open source audio working, but might have to go with the HAL for now to at least get it working, and then back trace maybe...my guess is once the holidays are in the rear view things might start happening really fast...thats my hope lol

on a related note too (like what i did there lol...sry slow day at work) for someone just starting out in linux development period, what is the difference and/or advantages/disadvantages of open source audio vs HAL audio...im assuming open source means we don't have to rely on Samsung at all but im just not sure and my google-fu isn't helping me lol
[AT&T Samsung Galaxy Note II] tino_b:
I didn't really wanted to let go of cm10.1 to be honest.

I just made a small research on audio (I'm a beginner on Linux too) and what I understood is that the difference between HAL and open source is standardization, meaning that Linux developers/maintainers are trying to find a way to bring together different HALS from different vendors and create a standard (open source) that can be implemented across different devices. Here's what I found though its not much: http://events.linuxfoundation.org/events/android-builders-summit/brown

Anyone with better knowledge on this please correct me if I'm missing anything.
[AT&T Samsung Galaxy Note II] MonsterBandit:
that makes total sense now lol...thanks dude...reading that link now...seems very promising...something def. worth paying attention too...that at its aim seems to (in theory at least) help reduce the android fragmentation going on...i know google is working hard to bring that to heel...and OSA (open source audio) seems to be another step in that direction.
[AT&T Samsung Galaxy Note II] tino_b:
In that sense you're right too. Open source = no reliance on Samsung for audio.
[AT&T Samsung Galaxy Note II] MonsterBandit:
check this out...http://opensource.wolfsonmicro.com/content/tinyhal

could any of this help (looks like its for the Nexus 4) Audio is where I live (Sound Engineer for Live Theatre) so this really intrigues me...I'd love to learn more about the Open Source Audio, TinyHAL, and TinyALSA

http://opensource.wolfsonmicro.com/...4;hb=7988b702dd1b0671987269c94fd0ac420becf8b8
[AT&T Samsung Galaxy Note II] tino_b:
I like TinyHAL's concept of not having to change the source code but instead make configurations through files. I believe that will save tons of time for the android developers such as cm and madmack.
[AT&T Samsung Galaxy Note II] madmack:
nice research you guys.

we're already using that tinyHAL in our open source implementation. Look under audio/ in the dev tree. libtinyalsa is also under the external/ folder.

Samsung's audio files require us to pull in a bunch of libraries due to dependencies, give us less control over tweaking stuff like bitrates, volumes and what not (not an audio expert here) and are not compatible going forward. There are API versions for each audio module, google moved forward in Android 4.2 so the APIs in any audio implementation will have to be updated. It's not a simple check for the version either: some functions in mediaserver for example call new APIs that the old audio files simply don't have. That's why we can't bring stock HAL into 4.2 without more hacking and downgrading.

Solution: use the open source hal that we have and that we can upgrade to match the new APIs easily.

We were lucky with CM10. The dependencies for audio HAL didn't spiral all over the place so I was able to contain the port to several libs (~18 libs). In some other systems, you'll have to move in even more libs that the system won't really use but will be required during link time for the precious stock hal to work. Sometimes these stuff that you have to move are in direct conflict with CM libs so this breaks audio stock HAL.
[AT&T Samsung Galaxy Note II] tino_b:
Interesting...
[AT&T Samsung Galaxy Note II] MonsterBandit:
Yea i saw that ur using tinyHAL...i was poking around in the TinyHAL git and your git looking at what u have vs what they have in the nexus 4 one they had posted. I have 0 knowledge about linux code so ill have to start somewhere i guess...that pdf i linked to has a nice "smartphone codec" graphic...i wish i had sonething similar for our phone and compare what is needed vs what we have and go from there...i guess ill be going back to.c++ and linux dev reading and see if i can teach myself this audio stuff...any tips would be great but not expected
[AT&T Samsung Galaxy Note II] PlankLongBeard:
Thanks MadMack!! Your the Man... I Appreciate the Love Good Sir and Yes I Will stick With the Original LoL!! Also... It Would Be Great To Have the OP Updated to show Compatibility... Thanks A Million!

Yup... I'm Doing the Same!!

No... I Didnt Do So But Thanks For the Suggestion!
[AT&T Samsung Galaxy Note II] sjkoon:
I'm Korean Galaxy Note2 LTE user.

i can't boot CM 10.1.

i got Android OS Upgrade Progress,,,

and final stage " Starting apps.. " loading is no end.

AND reboot, i got Boot animation no end.

Korean Galaxy note 2 Has completely work at AT&T CM10.

but cm 10.1 is not.

what's the problem is it?
[AT&T Samsung Galaxy Note II] madmack:
I'm not supporting other devices at the moment but I can have a look if you'd provide a logcat of the crashing event. Just logcat while the phone is bootlooping and pastebin the file.
[AT&T Samsung Galaxy Note II] MonsterBandit:
really stupid question...have you tried the pure vanilla TinyHW initial release? Most of whats there is identical to what you already have in audio_hw.c and i'm guessing that the additional preprocessor directives;

#include <audio_utils/echo_reference.h>

#include <audio_effects/effect_aec.h>

#include "audio_hw.h"

#include "ril_interface.h"

are to get things working...i mean for the most part i would say 80-85% of what you have is identical to the inital public release of TinyHAL I'm looking at...just curious.
[AT&T Samsung Galaxy Note II] codeninja99:
Most of the Samsung devices are using this oss hal. There is a bin called tinymux or tiny(something ) that will spit out the values.

I fooled with it on the n7100 port.

The mentioned header files set the volumes and sound effects for different outputs.
[AT&T Samsung Galaxy Note II] Entropy512:
It will fail. The vanilla TinyHAL implementation has zero RIL interface implemented to my knowledge.

IF you read through this thread, you'll see that the problem has been identified to be the RIL audio interface - audio HAL needs to talk to the RIL and that's not working due to a significantly different RIL interface. (Infineon/Intel XMM6260 modem vs. Qualcomm MDM9615 modem).

There are currently no opensource HALs for MDM9615 + WM1811. However, with a bit of work, madmack should be able to adapt the MDM9615 stuff (csd-client IIRC?) from mako and replace the XMM6260 (secril-client) **** in our HAL.
[AT&T Samsung Galaxy Note II] ceo.mtcl:
All hail Entropy512... bow down.

I like how you said "our hal" :)
[AT&T Samsung Galaxy Note II] pickneters:
Wow this is awesome, I really considered using this... do I really need to make phone calls? Lol keep up the great work!
[AT&T Samsung Galaxy Note II] geekasso:
Thanks a lot for the goodies you continue to provide us with. Though I cannot get bluetooth turned on in 10.0, I tried 10.1, and it works fine. I guess now I just wait until 10.1 is out to switch to CM.
[AT&T Samsung Galaxy Note II] MonsterBandit:
seconded...im right there with ya...i wish i knew.where to start...square one to this type of stuff seems so far away its not even funny
[AT&T Samsung Galaxy Note II] tino_b:
@madmack. I would like to offer my help as well for this project. I'm sure will we learn a lot from this.
[AT&T Samsung Galaxy Note II] :
The old school way is to hire someone to take a look at it for us, with the rider that he/she posts in the open so everyone can learn from it. Anyone know what the hourly or daily rate of an elite developer goes for? I'm open to starting a fund.
[AT&T Samsung Galaxy Note II] Artimus009:
I know it's alot. There is a guy in the att sgs3 forum that helped out in the beginning...Task650 AOKP thread.
[AT&T Samsung Galaxy Note II] meleii:
I've had 2 devices task developed for and I truly believe he wouldn't help with this phone. I can't speak for him but I recall him saying the note is too much of a (for lack of better words) novelty.

But hey I could be wrong.
[AT&T Samsung Galaxy Note II] cdshepherd:
You must not be familiar with exynos:D
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
hahaha... as much as i agree with this comment, i think it comes down to personal preferences. i know quite some devs who really hate the note 2, but at the same time have the devs who freaken love the phone.
[AT&T Samsung Galaxy Note II] cdshepherd:
Sure its all personal preference. But I think exynos has a lack of documentation or something like that. Makes it hard as hell for devs to build a fully functional aosp rom.

Here's a good examplehttp://rootzwiki.com/news/_/article...veloper-support-for-exynos-based-phones-r1151

Note: im not in any way at all trying to discourage development and im not sure if samsung has done anything about this as of yet. The link above was just the result of a quick Google search.:thumbup:
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
yup yup yup, i agree. actually, that's a very good article. surprised i missed it. thanks for it! :good:

but do you know what's funny? even with the lack of info released by samsung, many devs picked up the on the exploit... and even managed to patch it. damn, i wish samsung could get it's game back on. i fear sometimes it'll be like apple...

Edit - OP sorry for the tangent conversation.
[AT&T Samsung Galaxy Note II] madmack:
no problem.

I think I've posted it earlier but for those that want to help: the problem is precisely in the dev tree under folder audio/ The two files ril_interface.c and .h are useless for us because they link to functions in libsecril-client which we don't use. We need to figure out what Samsung is doing in their proprietary libaudio-ril.so file. What I do know is that it does talk to libcsd-client.so which is the Qualcomm proprietary ril audio interface. It does set some "magic" with other libs as well but that should be negligible. Decompile and figure out what libaudio-ril.so does and we have a functional audio ril. Once you figure out what you need to do, just replace the functions in ril_interface.* (our audio/ folder under dev tree) and replicate what libaudio-ril.so does.

It's not a tiny alsa issue nor a routing issue.. simply a connection issue between the modem audio device and our functional tinyhal implementation.

I'm not very familiar with ARM decompilers. If anyone knows of a good one that is able to decompile arm instructions, please let me know.
[AT&T Samsung Galaxy Note II] MonsterBandit:
I know nothing about ARM decompilers but a quick Google search turned up Hex-Rays.com but that is seemingly ALOT of money...i would kick in but we would need a lot more backers for it

unless we can find someone who has it and would be willing to decompile it for us/you

i wonder if there would be an interest in maybe setting up a "Developer Wanted Section" think strictly monitored so there's no "i need someone to make me a theme" but more along the lines of this "Wanted: Use of ARM Decompiler" (maybe even allow a "bounty/reward"). sorry for the OT madmack...but if there is enough interest i'd be willing to work up a proposal for garyd9 and see if he'd be willing to add it to the Developer section
[AT&T Samsung Galaxy Note II] Artimus009:
I wasn't talking about Task...in the early part of his thread, there was a guy who worked with this type of stuff...not sure what was his name but if you search the first few 10's of pages, you'll find it.
[AT&T Samsung Galaxy Note II] Dazog:
What files exactly need decompiling?
[AT&T Samsung Galaxy Note II] MonsterBandit:
according to madmack this one: libaudio-ril.so
[AT&T Samsung Galaxy Note II] chrisaw:
A novelty? Seems that having a 22Mbit connection on anything less than a 5.5" screen is the novelty.
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
i checked origenboard, looks like it's under maintenance. i don't know if it's been down for awhile, but im hoping it's because samsung is ready to release some source man!

-EDIT- spoke too soon, it just looks like regular maintenance, but samsung's git http://git.insignal.co.kr seems start adding things to the exynos 4412

damn... seems pretty darn legit though. i'll try snooping around. but to get the general understanding, madmack cm10 release audio worked because it was still using samsung's hal and not open source?
[AT&T Samsung Galaxy Note II] MonsterBandit:
correct
[AT&T Samsung Galaxy Note II] jee'sgalaxy:
actually, monster, i've been browsing through samsung's git..

im just browsing though, does any of this help in anyway? http://git.insignal.co.kr/insignal/android/vendor/insignal/hal/tinyhal/
[AT&T Samsung Galaxy Note II] tino_b:
So, let me understand, libaudio-ril.so is the file we need to decompile?