yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] madmack:
No, this is old and still broken. There isn't any functional cm10.1 for our note 2 publicly available yet. Soon enough though, you guys should be able to download from get.cm directly :)

The price for working in a team with official status I guess: I can't publish or release any work given that it's not personal work anymore. At the same time, you get fixes and help from top devs. You also get less verbosity here from me due to all of these things. That's where we're at :cowboy: Sit tight though, official status will be here soon.
[AT&T Samsung Galaxy Note II] tino_b:
You just made my day! :D:victory:
[AT&T Samsung Galaxy Note II] snabben:
Sv: [ROM] [UNOFFICIAL] CyanogenMod 10.1 - Android 4.2 WIP

To bad the psu died in my Mirrorproxy, else I would have hosted it there after dl to give fast source too:)
[AT&T Samsung Galaxy Note II] jug6ernaut:
What is the official name this will be going under? n7105?
[AT&T Samsung Galaxy Note II] madmack:
t0lte
[AT&T Samsung Galaxy Note II] mjwhirly:
i believe t0lte, thats what is says under review on cm
[AT&T Samsung Galaxy Note II] jug6ernaut:
Ahh ok. Interesting! Thx.
[AT&T Samsung Galaxy Note II] MonsterBandit:
I guess the next question is will this thread change to Official status or will a new thread open? and will the new thread be in android development or original development (just kidding about that last one...hahaha)
[AT&T Samsung Galaxy Note II] :
That's a blessing and a curse. I miss the interaction with you. You are one of the friendliest devs I've run across and, more importantly, you've taken the time to teach and show what you've done out in public. I've learned a good deal sifting through your posts and it's a shame that you won't be able to post out in the open.
[AT&T Samsung Galaxy Note II] BlackPhantomX:
I didn't want to post something off topic, but I am curious... Will some of the Samsung based Note II-specific features be ported over? A few examples would be the palm swipe and S Pen features...
[AT&T Samsung Galaxy Note II] tino_b:
Most likely no because this an aosp rom. Pure Google.

EDIT: u can still use the spen but there's no fancy stuff from Samsung.
[AT&T Samsung Galaxy Note II] killa83:
Nope. It's a AOSP Rom and those types of roms doesn't support touchwiz framework. If I'm correct?

Sent from my SAMSUNG-SGH-I317's Galaxy Note 2 that was sent from it's Galaxy Note 2.
[AT&T Samsung Galaxy Note II] shaggyskunk:
You are correct ;)

But that's not to say that some of these Dev geniuses won't come up with something that's not dependent on tw.
[AT&T Samsung Galaxy Note II] robstunner:
4.2 is too epic to be overlooked because of SPen features. Once the in call audio issue gets figured out this ROM will be my daily driver
[AT&T Samsung Galaxy Note II] Hoezack:
How do I flash this on tmobile note 2?
[AT&T Samsung Galaxy Note II] jug6ernaut:
Again ppl I have to ask you to keep the conversation on topic. This is a development thread. If what your thinking about saying doesn't in some way help the development of the ROM( let's be honest most of what we have said doesn't ) then it does NOT belong in this thread.
[AT&T Samsung Galaxy Note II] sabre31:
Nice work can't wait.
[AT&T Samsung Galaxy Note II] BlackHoleSlam:
this is going to be awesome quick question do you guys have any insider info on what cm 10.1 will have in store for the s pen.
[AT&T Samsung Galaxy Note II] Uss_Defiant:
Read above.
[AT&T Samsung Galaxy Note II] BlackHoleSlam:
okay thank you
[AT&T Samsung Galaxy Note II] mjwhirly:
hehehe....everybody is in for a surprise soon:D

madmack and codeworkx--you guys did some amazing work quickly, can't believe how stable its been running on my phone since last night everything besides BT seems to be work great on my device at least will test again later to see if it was just the other device i was using that was causing the problem, hopefully sometime today CM will give the Note 2 official support!!!!
[AT&T Samsung Galaxy Note II] shaggyskunk:
Drooling :P

And whose the the Glass half Empty character that said that the I317 "will never get official support" :raspberry to you :D
[AT&T Samsung Galaxy Note II] madmack:
http://xdaforums.com/showthread.php?t=2105917

;)

It's a placeholder. I'll give you guys an image file to test on that other thread for now until you get the official nightlies bot building these out for you instead.
[AT&T Samsung Galaxy Note II] DAGr8:
Lock thread?
[AT&T Samsung Galaxy Note II] madmack:
Yes. Oui
[AT&T Samsung Galaxy Note II] Woody:
Per OP, this thread is closed
[AT&T Samsung Galaxy Note II] cashyftw:
I wiped everything, and now GPS is working! Now I can go party Lol

Sent from my Galaxy Note 2
[AT&T Samsung Galaxy Note II] pegapega02:
Voice calls are not working how can I fix this
[AT&T Samsung Galaxy Note II] cashyftw:
There's an OP... You should read it.

Sent from my Galaxy Note 2
[AT&T Samsung Galaxy Note II] MonsterBandit:
Madmack - Any word on if you will be getting official support from CM? I know you were going to contact the CM admin team and wanted to see if you got a response?
[AT&T Samsung Galaxy Note II] madmack:
no reply yet.

my gerrit submission is getting some feedback however so that is moving in the right track.

it might take a little while before everything is approved and merged.

of course all of this is for cm10. Not the version in this topic. I'm personally using cm10 as a dd and I think it's stable to be merged into the mainline cm nightlies.

cm10.1 is a whole different story.
[AT&T Samsung Galaxy Note II] MonsterBandit:
Fair enough I'm using cm 10 as a dd too and I can understand that...hopefully the gerrit response will help in the 10.1 development too...thanks again dude
[AT&T Samsung Galaxy Note II] volcomguyaz:
Wake wakey
[AT&T Samsung Galaxy Note II] :
Been moving between this, CM10 and the stock backup. I just finished reformatting the 64 mSD to FAT32 via HP USB tool. I can, via TWRP, make backups, restore, transfer files via file manager and recognize the correct storage amount. I boot back into any ROM and I get damaged SD notification. Thoughts?

Tested perfect in both W7/Dell and a newer iMac. And yes I've flashed the patch. Tested a 16GB and that works fine in the Note. Frustrated.
[AT&T Samsung Galaxy Note II] codeninja99:
I must say if you havent read from other thread. I re-tract my idea to move onto 10.1. I think 10.0 should be 100% and merged and 10.1->20.1 will come after. I think the goal should be to getting this device merged. See my notes on the other thread.
[AT&T Samsung Galaxy Note II] madmack:
no idea man. i don't have that issue here. when you boot back to "any rom", maybe that any rom is not liking fat32 although i highly doubt it.

I disagree. Getting cm10 merged will not magically pop cm10.1 out. We have a serious pending open source audio issue here and merging cm10 won't help it in any way.

For me personally I couldn't care less whether CM10 gets officially supported or not. I just don't want to see anybody merge my work without any creds. I personally use the build in the CM10 OP as a daily driver and I'm very happy with it. This cm10.1 in call audio is more of a "fun project" so I do flash 4.2 from time to time to see if I can somehow fix it. Would love to see someone else with ril audio experience join and chime in. I tried my best to make my sources as readily available as possible.
[AT&T Samsung Galaxy Note II] jug6ernaut:
(warning bs incoming, no experience in rom dev of any kind, much less specific hw components.)

Without source or at least hw specific understanding of what is going on arnt we just basically putting shots in the dark and hoping ital work as far as opensouce audio goes? I mean we can throw code at it for devices we believe might have a similar setup but its still just hit & miss.

Can we get raw data from the hardware and from that try to extrapolate whats going on from there? Obviously we would need to get someone who can interpret the raw data.

Edit: (further thought above seems stupid). /me is thinking...i need to actually dig into this b4 making any comments, ignore above :)
[AT&T Samsung Galaxy Note II] :
no idea man. i don't have that issue here. when you boot back to "any rom", maybe that any rom is not liking fat32 although i highly doubt it.

"Any ROM" means your CM10, CM10.1 and Stock TW. Anyway, I frustratingly agree. Somethings wrong, but who the hell knows. I have such bad luck with these 64 mSD's.

Either way I agree with you: Your CM10 has been rock solid for the last couple days, with nary a peep. But 10.1 is where it's at, no use in directing energy towards something that is developmentally dead.
[AT&T Samsung Galaxy Note II] cashyftw:
I agree, I think we should focus more on cm10.1

Sent from my Galaxy Note 2
[AT&T Samsung Galaxy Note II] tino_b:
Couldn't agree more. It makes much more sense to get 10.1 up and running than trying to fix something that's not broken (at least for me :p). Good job on this madmack! :)
[AT&T Samsung Galaxy Note II] codeninja99:
The blobs used to get things to work will get harder and harder to make work with new versions of android. CM10 should be the main focus. Getting merged into the mainline (and yes you will have full credit and even be the maintainer)

No one is trying to steal your credit. not sure where that came from
[AT&T Samsung Galaxy Note II] madmack:
You're kidding right? Do you have any idea what you're talking about? The current state in CM10 is that we're dumping in a black box to get audio to work. There is absolutely ZERO prior work with in call audio with qualcomm modem + exynos board. Translation: CM10's closed source hack or "solution" is stuck at Android 4.1.x and will not be compatible with any Android version that is higher than that. If you think getting the hacked HAL framework merged into CM will magically get you CM10.1, think again.

I'm happy with the way things are now. My CM10 work has already paved the way for at least one other AOSP ROM in the dev section for now so I'm genuinely happy about that.

The stealing my work part is my 2 cents. I'm not accusing you or anybody of stealing anything, merely pointing it out. I'm not sure I'm interested in being the maintainer given how much time that will take from me. So that's why if someone does merge and maintain it, I'll have to ask for the creds to be in place. C'est tout.

Back to the issue at hand: I'm finding some interesting material in the alsa qcom subdir.. :cool:
[AT&T Samsung Galaxy Note II] jug6ernaut:
http://www.youtube.com/watch?v=fCVHpnixj88

carry on lol.
[AT&T Samsung Galaxy Note II] MonsterBandit:
Lmao awesome absolutely awesome...back OT

Madmack...did you by chance pull in the patch to fix the security exploit being discussed In dev forum? Just wondering and I'm not sure it effects AOSP or not but wanted to ask anyway.
[AT&T Samsung Galaxy Note II] madmack:
I haven't done anything about it explicitly. I follow both supercurio and chainfire on twitter though so I've been following the news closely. Did any of you guys try to load one of their app to check whether the vulnerability is there? I haven't seen any commits regarding that in the kernel tree in CM for our device so I haven't acted yet. I guess I'll check that tomorrow and see what exactly is the deal.

I've made some tiny progress today in the audio department otherwise. I got some more ideas to try tomorrow so stay tuned for more "blogging".
[AT&T Samsung Galaxy Note II] MonsterBandit:
I'll check it out in a bit...trying to track down my SD issue...what permissions is your SD set to I think mine "broken" is set at 775...thoughts?
[AT&T Samsung Galaxy Note II] madmack:
which path exactly ? the sdcard has been symlinked to many places with JB.
[AT&T Samsung Galaxy Note II] MonsterBandit:
Solid explorer sdcard1 is what's linked via extsdcard and I'm getting 775 perm. Card is formated to FAT32 put it in while booted, rebooted into recovery and flashed ur cm10 on top itself (already running ur cm10) wiped cache/dalvick rebooted and got nothing...pulled SD card, it booted, put SD card back in and then pulled SD card, system yelled at me that SD card has been removed...put it back in and rebooted and stuck on boot animation...pulled SD card and it finishes boot...idk its frustrating because I know its not the card, and because you don't have the issue lol...suppose for a moment you have the issue what could I provide to maybe show you what I'm talking about...my last resort is to do a full system wipe and reinstall to see if that fixes it, but that's last ditch.

Also in relation to the security exploit, I downloaded supercuiro's voodoo app and it says that I am vulnerable...I will be applying the fix shortly to figure out if it breaks camera and go from there. It also seems that cm10.1 merged the fix into their repos already so you shouldn't have to worry about it going forward.

Edit: quick fix does not break camera for me...now I'm disabling quick fix and enabling fix at boot.

Edit 2: enabled fix at boot and it does not break camera and fixes exploit.
[AT&T Samsung Galaxy Note II] jug6ernaut:
The note is is vulnerable. I applied Chainfires fix and it does not kill the camera on CM.
[AT&T Samsung Galaxy Note II] MonsterBandit:
Cool so both chainfire and supercurios apps fix this exploit and won't break the camera for all who are concerned and want to fix the exploit...also for the newer member this does not remove root access it just fixes an app bypassing asking for root access rights...meaning when you select titanium back up for the first time either superuser or super su ask u to allow root access or not that is the correct way for that to happen...the I exploit allows apps the bypass that question and allow the app root access and it can then pull everything stored in RAM memory...what's stored in RAM I'm not sure and I hope someone who knows chimes in...but both fixes out there work and will not break camera for cm10
[AT&T Samsung Galaxy Note II] MonsterBandit:
OK not going to quote that whole thing...I'll try and grab you a log and post it for you...thanks for that whole thing about ril audio very enlightening...as someone who is just learning about the deeper workings of android its an eye opener...as for our difficulties it really does seem to hinge on Samsung at this point esp seeing that the exynos expolit which can easily root a device or access all your RAM memory is connected to the camera...cuz that connection seems logical lol...and as for the what's in the RAM that's kind of what I feared lol...I'll get the log up later today thanks again for everything
[AT&T Samsung Galaxy Note II] MonsterBandit:
Madmack - here is the link to my logcat I hope it helps. The steps I did;

reboot phone

start adb logcat

let it loop for a few minutes

pull sd card

finish boot

let the log settle

stop log

I hope its as verbose as possible and I hope this might help myself and anyone else with the sd card issue.

https://www.dropbox.com/s/bbemv1d7k6w7x00/MBLogcat_bootloop_sdcard_20121912.txt
[AT&T Samsung Galaxy Note II] madmack:
This looks bad man. Did you copy and paste that into some windows notepad program before putting it up on dropbox? The new line characters are all gone so we end up with a big wall of text that is so hard to read.

For example, the very first line "( 1984): Welcome to Android 4.1.2" This should start a new line and continue from the existing one. I recommend pasting the goodies into notepad++ if you're using windows or simply just put up the log.txt file that you've piped to using "adb logcat > log.txt".
[AT&T Samsung Galaxy Note II] MonsterBandit:
stand by ill fix it post haste

formating doesn't like me...working on it tho

there we go...here is new link and it is saved as an xml file to retain formatting

https://www.dropbox.com/s/bojr2aehdrqb73x/MBLogcat_bootloop_sdcard_20121912.xml

I even reinserted the sd card at the end of the log just to add more info for you
[AT&T Samsung Galaxy Note II] madmack:
that looks like your problem:

E/JavaBinder( 4789): !!! FAILED BINDER TRANSACTION !!!

I'm not sure how a userland app is able to bring down the entire zygote system but it really does look like an app or system partition issue.

Factory reset, wipe system. flash cm10 without any gapps data.. put in your sdcard and see if you can boot.
[AT&T Samsung Galaxy Note II] MonsterBandit:
ill give it shot...gunna take me a little bit have to charge up lol

---------- Post added at 11:54 AM ---------- Previous post was at 11:46 AM ----------

yay

http://www.androidpolice.com/2012/1...national-galaxy-note-n7000-and-note-ii-n7100/

i hope they credit it you for some of this...here the link to the get.cm

http://get.cm/?device=n7100&type=nightly
[AT&T Samsung Galaxy Note II] :
How is that possible?
[AT&T Samsung Galaxy Note II] jug6ernaut:
umm...you are aware 7100 != 7105 right?
[AT&T Samsung Galaxy Note II] madmack:
These are GSM phones. Audio was never an issue for them :)

Credit me? No man, I actually used their work to get stuff working on this rom. lol. They did most of the heavy weightlifting: camera, audio, hwcomposer, sdcards, sensors.. I only put in gps and radio given that this is where we differ.

No CM (or AOSP) is out for any LTE Exynos phone so far afaik. So we're even further from being rolled as a nightly. I might be able to get our current CM10 into the nightlies but that's about it.

Of course if we can figure that audio routing issue. Getting the I317 (and all LTE variants) into CM (both 10 and 10.1) will be much easier.
[AT&T Samsung Galaxy Note II] MonsterBandit:
blasted...i got all excited...i was thinking of the porting of 7100 to 7105 stuff you were doing earlier...but you're right its better to work with what we have and go from there...but when not if we get official support we'll be here and watch the audio issues are going to be tied to something rediculous like the accelorometer or something like that...esp if the RAM exploit is tied the the camera...thanks samsung
[AT&T Samsung Galaxy Note II] Entropy512:
1 and 2) is basically where ALL of the opensource audio HALs on every other Samsung device came from. We received ZERO assistance from Samsung for any of this. Not even header files for anything. For 4412 devices (which all have Wolfson audio) - the original source came from another Wolfson-based device (Nexus 7 I think...) and was adapted to I9300 by codeworkx (likely with some RE and some trial and error), adding the ril interface stuff (which he might have received some inspiration from via crespo). For Yamahell (4210 devices) it was initially a major reverse engineering effort by paulk of the Replicant project.

3) This is what you probably need to do. Look at how the qcom audio HAL for pure Qualcomm devices talks to libcsd-client. Look at places where the I9300 HAL is doing similar things with libsecril-client - then swap things. You're probably going to have to change the mappings around a bit and there WILL be trial and error. I had to do a similar thing with the Yamahell HAL - the original Replicant implementation was designed to talk to their RIL. I looked at it, and looked at how codeworkx did things on I9300, and started moving things over. For example, Replicant's source did some remappings internally to one of their RIL libraries, while the I9300 HAL had to do the same remapping before passing things to libsecril-client, so I needed to implement those remappings in the HAL. You might need to do the exact opposite as libcsd-client might use Android's standard enums (like Replicant's did) and not Samsung's screwy ones.

4) Having to do this too often is why most of the prior exynos4 maintainers have declared their current devices to be the last ones they'll mess with.

IF no one has succeeded by mid-late January, I *MIGHT* be willing to accept a temporary loaner device for 2-3 weeks so I can take a crack at it. No guarantees of success and I am NOT accepting a permanent donation (only a loan), I don't want to be stuck with another Exynos device sucking my time for more than a short attempt. I would rather that someone else do it though, both for the sake of my free time and so others can gain more experience... Teach a man to fish and all that...
[AT&T Samsung Galaxy Note II] MonsterBandit:
alright...did a factory rest, system wipe, dalvick and cache, nothing else but ROM flash...card is formated to FAT32...and I got nothing...boot loop until card is removed...finishing up a log for you sir

https://docs.google.com/open?id=0BzJOrW_SUj_-QkJ1MlFxYUVVLXc

in xml format should hopefully be able to download that
[AT&T Samsung Galaxy Note II] jug6ernaut:
Have you considered there might be a problem with you sd-card? What EXACT model is it.
[AT&T Samsung Galaxy Note II] MonsterBandit:
i have considered it but it mounts fine to a computer (with adapter) no problem i can delete the partition and make it whatever i want, transfer stuff to and from it no problem, but i get nothing when its in the phone...here is the link to the exact card on newegg

http://www.newegg.com/Product/Product.aspx?Item=N82E16820171582

only thing i can think of is the class is messing with something, but it worked just fine out of the package in the Stock TW based ROMs

found this not sure if it helps

E/kickstart-qcks( 1998): Spawning efsks

I/kickstart-efsks( 2984): EFS_TTY='/dev/ttyUSB0'

I/kickstart-efsks( 2984): Parsing 'where to save memorydump' options

I/kickstart-efsks( 2984): PathToSaveFiles='/dev/block/platform/dw_mmc/by-name/'

I/kickstart-efsks( 2984): EFSKS parameters

I/kickstart-efsks( 2984): EFS_TTY='/dev/ttyUSB0'

I/kickstart-efsks( 2984): ks_path='/system/bin/ks'

I/kickstart-efsks( 2984): PathToSaveFiles='/dev/block/platform/dw_mmc/by-name/'

I/kickstart-efsks( 2984): RX_Timeout=-1

E/kickstart-efsks( 2984): File '/dev/ttyUSB0' was not found

E/kickstart-efsks( 2984): /dev/ttyUSB0 does not exist.

E/installd( 2007): eof

E/installd( 2007): failed to read size

I/installd( 2007): closing connection

I/Zygote ( 2003): Exit zygote because system server (2444) has terminated

I/ServiceManager( 1996): service 'SecTVOutService' died

I/ServiceManager( 1996): service 'media.audio_flinger' died

I/ServiceManager( 1996): service 'media.player' died

I/ServiceManager( 1996): service 'media.camera' died

I/ServiceManager( 1996): service 'media.audio_policy' died

I/Netd ( 3113): Netd 1.0 starting

D/AndroidRuntime( 3112):

D/AndroidRuntime( 3112): >>>>>> AndroidRuntime START com.android.internal.os.ZygoteInit <<<<<<
[AT&T Samsung Galaxy Note II] madmack:
no friggin' clue. can't see anything meaningful in the logs. thing won't boot without the sdcard inserted you say?
[AT&T Samsung Galaxy Note II] MonsterBandit:
no thing wont boot with the card inserted...if its out or removed during boot everything is fine...as you can see in the last lines of the logs:

D/Vold ( 1997): Volume sdcard1 state changing 0 (No-Media) -> 2 (Pending)

D/VoldCmdListener( 1997): volume mount /storage/sdcard1

D/DirectVolume( 1997): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 49, PARTN 1

W/MountService( 8999): Insertion mount failed (-1)

D/DirectVolume( 1997): DirectVolume::handlePartitionAdded -> MAJOR 179, MINOR 53, PARTN 5

E/DirectVolume( 1997): Invalid 'PARTN' value

thats when i put in the sdcard after phone has fully booted

I can try messing with the partition again and see where that gets me but idk
[AT&T Samsung Galaxy Note II] madmack:
have cm partition the thing for you. I haven't tried it but you could delete the partition table in windows and all partitions. boot up cm, go to the storage menu and have it format it for you. maybe that only works on stock tw roms but it's worth a try.

I have 64 gb SanDisk as well, so the issue is definitely in your sdcard