yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] madmack:
not really. we're really just 1 or two guys working on it so we can trace our work in github :) I haven't done anything more than what I provided earlier. I am planning to have another look today given that imilka was kind enough to give me some pointers on where i should look to fix audio.

A lot has been done lately for our board (smdk4412). Just checkout review.cyanogenmod.org for the list of all pending mods by Daniel, Andy et al. I think we're moving away from proprietary HAL and hwcomposer which is just pure awesome!

Now, where were we.. yea, fixing that stupid audio rild routing issue.
[AT&T Samsung Galaxy Note II] razorbladex401:
I've been banging my head against the wall trying to figure out the audio routing issue.
[AT&T Samsung Galaxy Note II] madmack:
same here.

I'm thinking the problem might not be with the audio.primary package after all. It might be in another .so ril file that is responsible for routing modem pcm.

I'm logging audio_hw and it doesn't seem like anything is wrong. Our and n7100 audio routing is the same really (hence why audio works everywhere else).
[AT&T Samsung Galaxy Note II] MonsterBandit:
what about looking at the n1705, could the lte hardware be messing with something?
[AT&T Samsung Galaxy Note II] mick.wheelz:
Is the hardware in the note II similar to the i9305?
[AT&T Samsung Galaxy Note II] madmack:
The n7105 doesn't have cm10 support. our devices are pretty similar so if one device gets audio working, the other will as well.

I got some bad news otherwise.I've managed to completely disable the overlay audio files and rely instead on routing and configs from the stock ROM.Got audio to work again using only proprietary binaries and guess what, audio through phone calls is still broken.

there is no point to debug the audio_hw I think because even without them, we're still not getting audio during calls.

I'll start looking at the ramfs files and perhaps the kernel again.
[AT&T Samsung Galaxy Note II] madmack:
We have the same radio. Yes

If you know of any working aosp ROMs,let us know!
[AT&T Samsung Galaxy Note II] mick.wheelz:
I don't. I was hoping you might have had a working (or semi working) rom that I might be able to get running on my i9305
[AT&T Samsung Galaxy Note II] MonsterBandit:
Glad to see madmack make the Portal this morning...congrats dude...maybe with that you'll get some added help in the form of some CM devs helping out

---------- Post added at 07:36 AM ---------- Previous post was at 07:33 AM ----------

which kernel are you using?

nm got the source link from OP...duh...silly me lol

---------- Post added at 08:26 AM ---------- Previous post was at 07:36 AM ----------

Liquidsmooth ROM seems to be working

Thread: http://xdaforums.com/showthread.php?t=1993817

Github: https://github.com/liquidsmooth

not sure if that helps and not sure if this helps found this:

Kernel tree for Samsung systems on Android

https://android.googlesource.com/kernel/samsung.git
[AT&T Samsung Galaxy Note II] drakeymcmb:
Calling works to ?
[AT&T Samsung Galaxy Note II] razorbladex401:
I did notice the below in my logcat.when my phone had started up.

V/audio_hw_primary( 2005): Set 'MainMicBias Mode'.0 to 1

V/audio_hw_primary( 2005): Set 'IN2L Volume'.0 to 22

V/audio_hw_primary( 2005): Set 'MIXINL IN2L Switch'.0 to 1

V/audio_hw_primary( 2005): Set 'MIXINL IN2L Volume'.0 to 1

V/audio_hw_primary( 2005): Set 'AIF1ADCL Source'.0 to 0

V/audio_hw_primary( 2005): Set 'AIF1ADC1 HPF Mode'.0 to 0

V/audio_hw_primary( 2005): Set 'AIF1ADC1 HPF Switch'.0 to 1

V/audio_hw_primary( 2005): Set 'AIF1ADC1 HPF Switch'.1 to 1

V/audio_hw_primary( 2005): Set 'AIF1ADC1 Volume'.0 to 96

V/audio_hw_primary( 2005): Set 'AIF1ADC1 Volume'.1 to 96

I/AudioFlinger( 2005): loadHwModule() Loaded primary audio interface from M0 audio HW HAL (audio) handle 1

I/AudioFlinger( 2005): HAL output buffer size 1056 frames, normal mix buffer size 1056 frames

I/AudioMixer( 2005): found effect "Multichannel Downmix To Stereo" from The Android Open Source Project

I/AudioFlinger( 2005): Using module 1 has the primary audio interface

I/AudioFlinger( 2005): AudioFlinger's thread 0x41e4c330 ready to run

W/AudioFlinger( 2005): Thread AudioOut_2 cannot connect to the power manager service

W/AudioFlinger( 2005): Thread AudioOut_2 cannot connect to the power manager service

I/AudioFlinger( 2005): loadHwModule() Loaded a2dp audio interface from A2DP Audio HW HAL (audio) handle 4

I/AudioFlinger( 2005): loadHwModule() Loaded usb audio interface from USB audio HW HAL (audio) handle 5

I/AudioPolicyService( 2005): Loaded audio policy from LEGACY Audio Policy HAL (audio_policy)
[AT&T Samsung Galaxy Note II] jug6ernaut:
I believe thats a 7100 rom, in the least it does not specifically say it supports the 7105.
[AT&T Samsung Galaxy Note II] MonsterBandit:
seems to be, read the entire thread and there is no mention of in call audio not working...just some BT issues and dpi issues when modding...his issue tracker also has no mention of it...so short of putting it on my phone i would assume its safe to say in call audio works on Liquid

---------- Post added at 09:57 AM ---------- Previous post was at 09:53 AM ----------

true but correct me if I'm wrong but isn't madmack working off the n7100 device tree? I was only posting the link to Liquidsmooth to help with the in call audio issue...to my eyes its an AOSP ROM with working in call audio...thats the only reason I posted the link to hopefully help fix the in call audio issue.
[AT&T Samsung Galaxy Note II] jug6ernaut:
ah, i assumed the problems were caused by the differences between 7100 and 7105.
[AT&T Samsung Galaxy Note II] MonsterBandit:
thats what I thought at first too...lol

there's also the "neak 7100" kernel that's based off of the Samsung OSRC...but i doubt thats AOSP lol
[AT&T Samsung Galaxy Note II] madmack:
aosp definitely works fine on n7100.

our devices have different radio chips tho, so the work that i'm basing off, while it works for n7100, won't work on the i317. that's the "porting" part that we're working on.

we can use any previous work for any devices that is 1. exynos 2. LTE qualcomm. I think so far it's only two devices: Note 2 LTE and i9305. None of which have any AOSP projects that I can use information from.

The audio issues are pretty serious. I'm not an expert on audio routing nor on modem AT commands (which could also be the issue here). We might have to rewrite the RILJ (Java layer of RIL) because the stuff I'm using from the D2 devices (S3 LTE Qualcom chip) at the moment could be the culprit.

I'll continue investigating.
[AT&T Samsung Galaxy Note II] MonsterBandit:
do we know what qualcomm chip we have is?

found it its the qualcomm GTM801U
[AT&T Samsung Galaxy Note II] Entropy512:
I'd suggest instrumenting a stock kernel to look for differences and what the stock audio HAL does.

Also since you mentioned the stock HAL fails for call audio - look for possible differences at the kernel level in terms of codec setup/configuration.

As an example - look at all of the mc1n2_cfg.h variants in the 4210 tree - https://github.com/CyanogenMod/android_kernel_samsung_smdk4210/tree/jellybean/sound/soc/codecs/mc1n2 - the main difference between all of these is the radio audio DIO configuration. I have NO idea why it's different for nearly every device - The config is different for I9100, I777, and N7000! (I've often said how I777 and I9100 are 99% identical - the modem DIO config is one of the items in the remaining 1%).

Obviously you have Wolfson audio but your issues sound similar.

I suggest putting this up on gerrit instead of forking the kernel tree:

https://github.com/madmack/android_...mmit/be84d996752a467c794138e778bff0547b663a95

Same for https://github.com/madmack/android_...mmit/a263e956e954026ddc6e953a53628bc4661d7ba9 (What's the deal with hwcomposer? It should not be any different from any other 4412 device.)
[AT&T Samsung Galaxy Note II] snabben:
No calls this late. Can report that in the morning
[AT&T Samsung Galaxy Note II] madmack:
lte workshop?
[AT&T Samsung Galaxy Note II] snabben:
Damn autocorrekt. Supposed to be working, not workshop

:)
[AT&T Samsung Galaxy Note II] pickneters:
Mods keep deleting my question, it's the in call bug fixed? Robot voice?
[AT&T Samsung Galaxy Note II] snabben:
Didn't know of any in call bug on cm10. Thought that was on cm10.1.
[AT&T Samsung Galaxy Note II] madmack:
lte should work just fine. we might have some minor differences between our devices that are affecting your lte reception but it's highly unlikely.

No in call audio bug in cm10. Please read the OP next time. That's why people aren't responding. The information you need is in there.
[AT&T Samsung Galaxy Note II] pickneters:
I have the bug, every other time I answer the phone they are either not there or sound like a robot...
[AT&T Samsung Galaxy Note II] madmack:
I thought I fixed this.. :eek: I don't have that issue locally.
[AT&T Samsung Galaxy Note II] pickneters:
I'll download the newest build and give it a run today and report back. Latest AOKP had bug...
[AT&T Samsung Galaxy Note II] madmack:
dude. you can't report aokp bugs here. the in-call issue has been fixed for a while now in cm10. Only report bugs when you do know for certainty that the rom on the thread you're posting is having it otherwise you're really wasting our time.
[AT&T Samsung Galaxy Note II] snabben:
madmack. Yeah it's probably not the rom fault. Ran into same issue before. Only way to solve it is to odin back to stock. Then flash aosp again. Then lte work. If I then flash another aosp rom then it's gone again. I hope this is just happening to me.

Nice Work!!
[AT&T Samsung Galaxy Note II] seh6183:
I can't find a change log or anyone commenting on the matter. On the Jan 13 build were the following problems fixed:

Bluetooth range

Screen stutter

In call audio glitch

I had problems with all of those things on the Dec 26th build.
[AT&T Samsung Galaxy Note II] ante0:
Great, and finally!

Wish more roms were ported to the N7105 :D
[AT&T Samsung Galaxy Note II] prmcmanus:
I ran CM10 previously and had no issues with rotation. I went back to a stock ROM, and now I'm on CM10 again without rotation.

Tried completely wiping everything, still no joy.

If I can provide any information at all, let me know.

All the hard work that's gone into this ROM is appreciated
[AT&T Samsung Galaxy Note II] :
It's in thread and in General. You've gotta do the leg work yourself. Unfortunately I still haven't been able to fix mine completely and I've tried everything everyone has posted at this point. (Aside from a complete return to stock.)
[AT&T Samsung Galaxy Note II] Yoshiikim:
problems

it still needs more work. Download and give it a shot but you will immediately see that you will flash to another rom right away:laugh:
[AT&T Samsung Galaxy Note II] Xirta:
Flash the Perseus kernel over your cm10 and reboot. It won't work but give it a minute. Then pull your battery and reboot into recovery. Then reinstall cm10.

That worked for me when I had the rotation issue.
[AT&T Samsung Galaxy Note II] prmcmanus:
I've tried all the tricks listed. I just found it odd that it worked before, but now it doesn't. Didn't think it'd annoy me this much, lol. Cheers for replying

I just tried it with the latest Perseus, but still no change. Don't suppose you know which version you flashed previously?

The only thing I can think that has changed since when rotation worked, is my baseband version.

Can't remember which one I had previously though, or even if it's possible that it could affect it
[AT&T Samsung Galaxy Note II] Clark Joseph Kent:
Please move on from the OT talk and back to development, shall we. Any more OT type discussion, please utilize the PM system. Thank You.
[AT&T Samsung Galaxy Note II] ianyt77:
In an original 7105 ROM in the BIN folder there are files called - sensorhubservice and sensorservice could these have a bearing on the rotation and no sensor issues we are experiencing ????
[AT&T Samsung Galaxy Note II] ante0:
This might be a fix: http://xdaforums.com/showthread.php?t=2096960

found in http://xdaforums.com/showthread.php?t=2069164
[AT&T Samsung Galaxy Note II] prmcmanus:
Is discussion a rotation bug with this ROM off-topic?

Got it working.

Did a combo of things at the same time though, so I can single out what it was exactly.

1) Flashed Stock, Modem LL4, and Perseus Kernel

2) Booted up, and then back into recovery

3) Flashed latest CM10 and GAPPS

4) Booted up, then realised I forgot to wipe data....

5) Back to recovery, wipe Data and Cache

6) CM10 with Rotation

If it would be of benefit to any developer, I can try to replicate the fault and see what it was exactly that got it working
[AT&T Samsung Galaxy Note II] madmack:
Seems to be a reset issue of sorts. Perseus is resetting (or setting) a flag to get sensors to work and I think it's the stock behavior as well. These random errors that appear and disappear by flashing other boot images are hard to pin.
[AT&T Samsung Galaxy Note II] fix-this!:
i can confirm the incall volume low bug is still present on the new build. you still have to toggle your volume to hear the other person.
[AT&T Samsung Galaxy Note II] dkotoric:
man I have a note 2 on the way hope official CM10 comes soon.
[AT&T Samsung Galaxy Note II] MonsterBandit:
CM10 is here dude...official will never happen
[AT&T Samsung Galaxy Note II] dw9906:
Official will happen eventually.
[AT&T Samsung Galaxy Note II] MonsterBandit:
I don't think so...focus has shifted to 10.1 where we will get Official support but not for 10...its not worth it for them to merge a new device into a basically dead ROM...there's no forward development coming from CM for 10...therefore no offical support will ever happen for CM10...now CM10.1 is a different story...just follow the other thread to find out
[AT&T Samsung Galaxy Note II] dw9906:
Yes, I know that. CM support, is CM support. Of course they moved to 10.1. That's the most recent version.
[AT&T Samsung Galaxy Note II] dkotoric:
what i meant is cm in genereal cm10.1 is perfectly fine with me

i may try to trade my att note to for a n7100

btw i have a white one in the way but want a gray one if anyone wants to trade

Sent from my Nexus 4
[AT&T Samsung Galaxy Note II] :
I'm trying to use USB tethering and its not connecting my wifi on my phone to my PC. I even installed the Samsung driver on my PC and installed an app called easy tether it doesn't detect my phone. However cm10 USB to tethering works just no internet on my PC.
[AT&T Samsung Galaxy Note II] madmack:
you really should use cm10.1 as most of our time and development effort is focused there. USB tether should work fine on cm10.1

for the guys that are still using this rom: does google now voice recognition work?
[AT&T Samsung Galaxy Note II] jug6ernaut:
Last i used 10.0 it was working fine.
[AT&T Samsung Galaxy Note II] :
I'm on jelly beer 3.35.1 android 4.2.1 cm10.1 I think and when I turn on adv over network it turns off all functionality of USB debugging and it turns off connectivity to my PC.
[AT&T Samsung Galaxy Note II] Childofthehorn:
FYI,

Breakfast is made of: *clue is not bacon*

In fact, its only set for " t0att " for your make files.

Based on the latest source, it should be "breakfast t0att". Maybe its just a re-sync of your master git repo?

BTW got a local manifest set for this one for "mka bacon" (makin BACON!)

Thanks for your great work. I have mainly been dealing with 3 of the d2's and this looks a bit cleaner with the exynos sources.

For those doing the RILJ, the folder is /framworks/base/telephony/java/com/android/internal/telephony/ XXX_RILJ.java
[AT&T Samsung Galaxy Note II] Childofthehorn:
BTW - for those who didn't see.

You need to copy off the cyanogenmod _t0lte_defconfig and rename to cyanogenmod_t0att_defconfig in the kernel/smdk4412/arch/arm/configs/* of your CM10.1 directory.

From there make your required changes (especially if you want some additional features in the kernel like Serial USB), the defconfig will be copied to .config for the kernel.
[AT&T Samsung Galaxy Note II] rimaxzone:
Hi Thanks so much but, the link is not working :(.. is there anyway you can upload the link again?
[AT&T Samsung Galaxy Note II] softballjunkee13:
http://xdaforums.com/showthread.php?p=36873319

Sent from my SAMSUNG-SGH-I317 using Xparent Skyblue Tapatalk 2
[AT&T Samsung Galaxy Note II] madmack:
Entropy is in da house !! awesome :D

Before I go dig deeper into the kernel. I was thinking maybe the RILJ implementation is the culprit. How do you guys implement all of these RIL java custom layers? I see a whole lot of them in frameworks_base/...../telephony and I'm using the SamsungQualcommD2RIL which initiates a rild socket and calls just fine but perhaps it is not working with audio?

Another thing that makes me suspect RILJ is that when I put the phone in airplane mode, I'm getting a lot of RILJ wakelocks.

Appreciate your 2 cents :)
[AT&T Samsung Galaxy Note II] chrisaw:
I believe you have the same audio issue as the n7105 port we're working on.

I actually have a possible solution based on the original n7100 port. Testing it tonight or possibly tomorrow and will let you know how it goes.
[AT&T Samsung Galaxy Note II] Entropy512:
There's a fairly good chance the d2 RIL java files will fail. Those are intended for Qualcomm SoCs, not for Qualcomm modems hung off of Exynos SoCs.

So pretty much the main roadblock is the one I thought would be the case - no one has implemented a RIL interface for this particular modem configuration before.

I just remembered that also, the audio HAL does some interfacing to the RIL via secril-client - but I don't know if that's functional with a Qualcomm modem-based RIL.
[AT&T Samsung Galaxy Note II] DarthPiggie:
I just discovered something weird. system/bin/secstarter exists on my phone but not On the N7105. The plot thickens now because that's a core RIL binary.

Going to investigate.
[AT&T Samsung Galaxy Note II] madmack:
I've actually restored libsecril-client.so from stock as well and eliminated the cm10 open source ones. deleted libsecril-client-sap as well for good measure.

I think that's what it is. The java ril interface is broken, and I have no idea how to write one or debug the existing source. The basics work though, and monitoring logcat -b radio shows that the dialog between RILC and RILJ goes without errors. Worthy of note is that if I place a call to my phone, it does ring! Perhaps that qualcomm chip needs some extra RIL commands to activate the audio channels that are currently missing. :eek:

Anyways, thanks again for your help.
[AT&T Samsung Galaxy Note II] madmack:
not important. tried with and without it and it doesn't make a difference.

it's started by AT&T, that's why it's not there in the international variant. Look in init.carrier.rc for the juicy details.
[AT&T Samsung Galaxy Note II] slick_rick:
So if I wanted to build this myself, what exactly should be in my local_manifest.xml? I added the repos you have listed in your OP http://pastebin.com/Jht8GEjL but when I try building, error after error. Mind pasting yours madmack? I think I might be able to help with audio issues or know someone who can. Thanks.
[AT&T Samsung Galaxy Note II] madmack:
the local_manifest stuff should be irrelevant if you've setup your build directories correctly. My local manifest won't help you because I've detached from it (I no longer rely on repo to sync my directories, but I manually git clone the stuff you see in my github account).

make sure you checkout the right branch in each repo that you download.
[AT&T Samsung Galaxy Note II] chrisaw:
This is greatly useful mate, I did think this was causing a problem for me on the N7105 but it seems this isn't the problem. That's great news, means the issue is elsewhere and thus should be OK on my device without code changes.

Do you guys get reboots frequently on your device with this CM build, however? I seem to be which is why I'm curious - would be glad to get the reboot issue fixed on my N7105 - then I can get on with trying to get this audio issue sorted out!
[AT&T Samsung Galaxy Note II] madmack:
I personally don't care about the reboots. The audio issue is more pressing and without a proper java ril implementation, I'm stepping back for a while at least until this is sorted out.

It seems the reboots only happen when "I'm moving", i.e. when the radio towers change. If the phone just sits there on my desk, no reboots are encountered which all leads to the same culprit: RIL.

Using the D2 ril files don't make sense like Entropy posted earlier. I agree :)
[AT&T Samsung Galaxy Note II] chrisaw:
Sounds like I may need to cough up some cash and hire a dev to get this interface sorted out in that case.

Problem is, it's going to be very difficult (I would imagine) for a CM dev to work on this without the device to hand I would imagine.
[AT&T Samsung Galaxy Note II] jug6ernaut:
I will throw some cash at it if someone gets this working. Know the best way to go about it?
[AT&T Samsung Galaxy Note II] MonsterBandit:
Count me in...I'm holding out installing this till the audio gets fixed...then its off to the races lol
[AT&T Samsung Galaxy Note II] dafoxs:
Let me start by saying, I'm brain dead when it comes to this. When the note1 had this audio issue, the note2 system dump dropped. We fixed the audio problem by taking the audio_policy.conf file from the 2 and sticking it in the 1. What would happen if you did the opposite now? Just a thought.
[AT&T Samsung Galaxy Note II] :
In for the cash donation as well provided we can get a guarantee that it's 10.1 we are throwing our energy behind.
[AT&T Samsung Galaxy Note II] Entropy512:
See if possibly source built secril-client works on stock - then you'll at least know that it's in good shape, and, *more importantly*, you can instrument it to see what is being done.

For the main RILJ stuff, have you tried using Smdk4210RIL? (4210 is kinda misnamed - it's actually the one used for all Exynos4 devices so far including 4412, which is why I believe it's getting renamed for 4.2)

Huh? WTF are you talking about? Note1 for CM has used NOTHING from the Note2 for audio - the Yamahell audio_policy came from the I9300 CM tree, and was dependent on a hell of a lot of other things (like a complete replacement audio HAL). (However as part of the current move to opensource gralloc/hwc, we might upgrade to r3p1 Mali/EGL from a Note2.)

As to cash donations - my stance on this still stands. People could offer me a device and $1000 and I'd still say no. My N8013 is my last Exynos4 device unless Samsung makes major changes, and so far, it's unlikely they'll make those changes before I'm too deeply involved with other manufacturers. I know the other historical AT&T maintainer (atinm) is in the same category. I don't think codeworkx, xplodwild, or espenfjo have any intent on taking on new Samsungs either.

The one thing I MIGHT consider, although not right now since there are 327934270430792 other things to do with 4.2 bringup, is a temporary loaner for just a few weeks. If things are still broken in January I might consider that, but to be honest, I'd prefer if a new maintainer learns things the hard way like we have. :)

Seriously, stuff like this takes time. It doesn't help that you will receive zero help whatsoever from Samsung with anything that comes anywhere close to the RIL. Unsol response code meanings? Nope. Meaning of the pcmclkctrl "am" intent that Tab2 devices pop out with Bluetooth calls? Nope.