yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] dlumberg:
I haven't given up on BT for ICS/CM10...

yesterday I finally understood enough about the code to truly disable the Noise Cancellation in BT calling

mInit(false), mMicMute(true), mBluetoothNrec(false), mBluetoothId(0),

which lead to a (more) stable connection but still very fuzzy sound in BT calling. I then noticed that there was some stuff to load Timpani in the kernel for Pyramid and Ruby that wasn't in Vigor in the board-vigor-audio.c that I added.

void vigor_get_acoustic_tables(struct acoustic_tables *tb)
{
switch (system_rev) {
case 0:
case 1:
strcpy(tb->tpa2051, "TPA2051_CFG.csv");
break;
case 2:
strcpy(tb->tpa2051, "TPA2051_CFG_XC.csv");
break;
default:
strcpy(tb->tpa2051, "TPA2051_CFG_XC.csv");
break;
}
}

static struct acoustic_ops acoustic = {
.enable_mic_bias = vigor_mic_enable,
.support_aic3254 = vigor_support_aic3254,
.support_adie = vigor_support_adie,
.support_back_mic = vigor_support_back_mic,
.get_acoustic_tables = vigor_get_acoustic_tables,
.get_speaker_channels = vigor_get_speaker_channels,
.support_beats = vigor_support_beats,
.enable_beats = vigor_enable_beats,
.set_q6_effect = vigor_set_q6_effect_mode,
};

just the line .get_acoustic_tables

Then I compiled and flashed and no surprise the audio was coming through but really fuzzy(same as the ION build). For s&g's I ran a logcat and got a new error !!!!!!

VGS is the audio gain for the headset profile for bluetooth... So I'm back to believing that this is not necessarily a routing issue but an issue of the gain not getting set properly, probably somewhere within libACDB or the ACDB loader (which are proprietary libs).

My current theory is that the gain is set too high and the echo cancellation is trying to compensate for it and creating a memory problem and the entire BT connection is getting reset and the process starts over.

Has anyone seen in their travels a place where VGS values are getting set?

I'm going to keep looking but if anyone has any suggestions they would be greatly appreciated.
[HTC Rezound] TheBr0ken:
Just for s&g's try running a logcat for a call w/bt connection, then one with headphones for just the audio, then a final one with the stock headphone w/mic and see if anything interesting pops up. Try last two with bt on and off, but not near another bt capable device such a car or ear piece, so it doesn't try and connect. I'd be curious if there was a difference in the last two logcats with or without bt on.
[HTC Rezound] kkozma:
Can you post me the exact code changes for those two fixes? Line #'s and files please. I'd like to mess around with them as well.

Awesome job man!

Another thought... Looking at the new error and the page you linked, AT VGS is speaker gain and it's trying to set it to 16 which according to that site has a range of 0-15. From my logcat, I know that the mic and speaker connect and then the speaker drops... I think you're definitely on to something now. :)
[HTC Rezound] dlumberg:
in vigor-3.0/arch/arm/mach-msm/qdsp6v2_1x/audio_acdb.c around line 300 I added

void vigor_get_acoustic_tables(struct acoustic_tables *tb)
{
switch (system_rev) {
case 0:
case 1:
strcpy(tb->tpa2051, "TPA2051_CFG.csv");
break;
case 2:
strcpy(tb->tpa2051, "TPA2051_CFG_XC.csv");
break;
default:
strcpy(tb->tpa2051, "TPA2051_CFG_XC.csv");
break;
}
}

Then around line 400 there's

static struct acoustic_ops acoustic = {

and I added

.get_acoustic_tables = vigor_get_acoustic_tables,

to the list of ops

Then in hardware/qcom/audio/msm8660/AudioHardware.cpp on line 676 I changed the mBluetoothNrec value to false which in theory should always turn the noise cancellation off...
[HTC Rezound] kkozma:
For kicks. Did you try those changes without turning noise cancellation off?

I compared the hashes for our acdb libraries with those of the pyramid and they are the same, so I doubt there's anything in those that are keeping it from working since we know theirs works.

Also, I tracked that error message down to frameworks/base/core/java/android/bluetooth/HeadsetBase.java

So, I'm wondering if there's a modified frameworks/base they're using?
[HTC Rezound] dlumberg:
Chad got CM booting with code from pyramid, I'm assuming he pulled in the acdb libs. The sense vigor libs are different... sound breaks using the original vigor ones...

Also pyramid is officially supported so the frameworks/base they are using should be the same that we have. Bruce doesn't have a repo for it and looking here I don't see anything that jumps out for this board.
[HTC Rezound] kkozma:
I've got a build running now with the frameworks base from intervigillum or however he spells it... One thing you'll notice in Evervolv's frameworks is that HeadsetBase.java is not present.

If this one doesn't work, I'll try Evervolv's.
[HTC Rezound] kkozma:
No dice on either...
[HTC Rezound] dlumberg:
Also here's some various greps of the CM10 tree... [looks at filesystem for uploads]...weird... I thought I had more that weren't 0byte files
[HTC Rezound] kkozma:
I got to thinking about it again the other day and none of this makes any sense. 95% of these CM builds is from CM sources and that stuff all works. So I personally think the answer lies somewhere in the stuff that isn't original CM.

So for that we have:

kernel

msm8660-common

device-htc-vigor

vendor-htc-vigor

I know I've been pretty adamant about it being a routing issue, but now after wasting so many freakin hours on it and getting absolutely nowhere, I do agree that the answer lies in the kernel somewhere. There are some pretty significant differences in the board files (arch/arm/mach-msm) between our phone and the pyramid and I think in the bluetooth files as well.
[HTC Rezound] Flyhalf205:
How about the msm8660 kernel. Well that help? We can look at that.
[HTC Rezound] puhleez:
Chad mentioned that he got BT to work in CM10.1 using the new BT stack. Is it possible to back port that to CM9/CM10/AOKP? Pardon my ignorance if this is a dumb question.
[HTC Rezound] dlumberg:
It looks like the entire audio system was rewritten for 10.1, I'm not sure if it is possible.
[HTC Rezound] MaulingDeOso:
pr_debug is probably being defined to nothing. You likely need to set a debug flag somewhere to enable it. Instead, just add some of your own printk statements where you want to find out what's going on. You can use dump_stack() to get a stack trace wherever you want, too. That'll help in finding out what's calling what.
[HTC Rezound] Snuzzo:
Found something interesting in abandoned gerrit

http://review.cyanogenmod.org/#/c/14617/

I wonder if this would be needed.
[HTC Rezound] Snuzzo:
A good friend of mine was playing with BT on ICS. Consider it solved.
[HTC Rezound] kkozma:
ORLY? Mind sharing?

I mean, I've moved on to JB and have given up on ICS but it would be nice to know what it was...
[HTC Rezound] Snuzzo:
Nope false alarm. Works on 4.1.2 but not 4.0.x based aosp.
[HTC Rezound] Neo:
lol XD
[HTC Rezound] TheBr0ken:
So I see some changes have been made to Chads manifest for cm10.1. To work with 4.2.2, what I notice that changes besides the obvious revision, was that frameworks_native no longer points to chads repo and frameworks_av no longer points to Evervolvs repo. This intentional or was accidentally forgotten? I haven't tried to sync or build so just questioning before I do

edit: Looks like Chad's frameworks_native just reverts commit be1b753
[HTC Rezound] chad0989:
Frameworks native still points to mine, and we still use evervolvs frameworks_av.

My frameworks native reverts two commits that break our builds.
[HTC Rezound] wildstang83:
Chad I have a question, and mainly only because a user asked me this question in my CM10.1 UNOFFICIAL thread. Are my builds built using your manifest pulling in the M2 updates, or how does that work? I noticed the JDQ39 binaries got merged in, I just don't know if that is what makes the CM M2 update or not...
[HTC Rezound] Flyhalf205:
Just giving you guys a heads up people building with cm-10.1. Koush had two commits to Cyanogenmod/android if you want to merge in with your android or Chad's. https://github.com/CyanogenMod/android/commits/cm-10.1
[HTC Rezound] shrike1978:
Grrr....we just merged in the changes from before.
[HTC Rezound] Snuzzo:
Anyone care to sync this for me and double check that it goes through the paces ok?

https://github.com/VigorAOKP/aokp_manifest
[HTC Rezound] lepa71:
I just want to reconfirm this. We are not going to get HW acceleration in our AOSP, aren't we? :(:confused:
[HTC Rezound] siulmagic:
we have hw aceleration, what we need is a updated frame buffer, to match jellybean's, ie use the ville c2 source code to get it. im pretty sure chad is aware of it, but hey hes a one man army so yea be patient.
[HTC Rezound] brenuga:
I have my mac at work set up to build now, I can try this Monday. You just want to test whether I can sync the repo ok or try an actual build?

On another note, trying my first cm build tomorrow. Neo says I need to sync chads manifest then revert the qcom/media commit. But I noticed shrike forked the vigor cm repo, is there a manifest that is more up to date or is chads with the cm 10.1 branch still the one to use?
[HTC Rezound] Snuzzo:
Chad's is the most up to date. Try both if you can, mainly interested in seeing someone else at least sync.
[HTC Rezound] Neo:
I synced and built just fine Friday
[HTC Rezound] Snuzzo:
The aokp-ics manifest?
[HTC Rezound] Neo:
No, CM-10.1 that Brenuga was referring to..

Looking back I see now that you were more concerned about AOKP
[HTC Rezound] TheBr0ken:
I'm syncing that now. Will let ya know how it turns out
[HTC Rezound] brenuga:
What was the word on Snuzzo's aokp manifest? I have been busy on an epic week long attempt to build cm 10.1 myself for the first time. Started out on Mac OS X, then switched to Ubuntu.

I've been typing out all the prerequisites I have discovered and the steps neo told me from his memory lol so hopefully once I get my build finished with no errors there will be a guide for others to follow.

Neo keeps mentioning I will have to do some sort of symlink at some point in the build? Is anyone familiar with whether that's still necessary?

Left my build running overnight on work machine so I guess I will find out in the AM.
[HTC Rezound] shrike1978:
If you're having trouble, this guide works for CM10.1 as well as long as you're using the correct manifest and branch: http://xdaforums.com/showthread.php?t=1920107

It's written for the 12.04.01 LTS release, but it has worked fine with newer releases of Ubuntu as well. I can also verify it works mostly with Kubuntu and Lubuntu. You'll get a dependencies error at one point when you're getting packages, but add those into the apt-get, and it'll be fine.
[HTC Rezound] Snuzzo:
So far Ive had 2 other users sync the AOKP repo fine.
[HTC Rezound] brenuga:
Thanks Shrike. I actually did depend on your CM9 guide for getting my build environment set up. Neo got me set up with the correct repo and latest linaro toolchain.

When I checked on my build today, it gave some sort of error with libwebcore . I *think* this is the missing symlink roadblock Neo talks about. He recommended the following code:

sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so

I did that and restarted the build, so we'll see what happens. I am using lubuntu in a virtual box VM running on my mac. I may try to rebuild on the mac in the future--the first time I ran into the issue that by default, macs run on case-insensitive filesystems for compatibility with older mac apps (including Photoshop CS). But then I figured out you can create a virtual hard drive image that is case-sensitive using darwin's hdiutil. As it was, I went out and bought a 2 TB external hard drive to store my repos and linux :)
[HTC Rezound] Snuzzo:
Has anyone ever seen this?

This is brunching AOKP milestone6 with GCC 4.7.2/Linaro 13.02 on Linux Mint 14

http://pastie.org/7290619
[HTC Rezound] Neo:
I was able to do cm9 with GCC 4.7.2 two days ago but g++ needed to remain 4.6. That's how we should do all of the ICS builds (IMO of course)
[HTC Rezound] GrayBoltWolf:
So maybe that is my problem......
[HTC Rezound] pwned3:
I'm curious though. If you do brick will you get a replacement?
[HTC Rezound] Jonman409:
I don't think it's a vold issue. Whenever I was going back and forth messing with vold, the overlays and the ramdisk it would always just cause a boot-loop. To my knowledge vold only handles the mounting and symlinks. I may be wrong though...

I'm fairly confident the issue resides in the ramdisk somewhere. I am going to go through it all again and compare my notes as well as check mobilizations against the new ICS leak.

EDIT: I figured out the vold issue as well. I have my internal sd mounting to /mnt/emmc and my external mounting to /mnt/sdcard as the default storage location.
[HTC Rezound] imparables:
Man, between you and Chad......you guys are awesome. The entire Rezound community thanks you guys. You're pioneers in this game....thanks.

Sent from my ADR6425LVW
[HTC Rezound] chad0989:
@jonman:

I see you're working on bringing the vigor stuff over to the newer holiday kernel source. Not sure if you've seen this but I already had a booting kernel based on the holiday source. I was just having some stability issues and put it on the backburner for a bit. Might help out a bit and make your life easier though:

https://github.com/Chad0989/vigor-ics-kernel
[HTC Rezound] renzo.olivares:
+1000 ramdisk lol......i bricked my phone with AOSP too before....my tree looked fine basically the same everything but ramdisk and kernel were different [ i used stock ics leak one] id say most likely the init.vigor.rc
[HTC Rezound] chad0989:
Finally able to confirm that I fixed the roaming indicator bug.

This runs pretty great. Now if we can just figure out that minor little brick issue. Kernel source would be nice too.
[HTC Rezound] wlmeng11:
The bricking issue?

Some of the changes he committed brick S-off devices.

Apparently it's unintentionally messing up the hboot or radios.

Sent from my NeoMax Rezound
[HTC Rezound] antp121:
Is anyone working on JB? If so, the inclusions of the new jb adreno graphics driver makes a world's of a difference.
[HTC Rezound] keolawills:
I heard JoelZ was but couldnt get it to boot. one other said they got jb to boot but i forget who.
[HTC Rezound] antp121:
I'm just trying to help. The new adreno drivers can help a lot with overall fluidity and stability on JB. I'm aware that this may not be the most development related post but don't get your panties in a bunch. I know jb is already booting and working but this can add to any stability and make project butter show more.
[HTC Rezound] dmeadows013:
The new adreno drivers are being used by JonMan I think. Also iirc Butter isn't something that works oob.
[HTC Rezound] chad0989:
Fixed USB mounting. Change is on github.

Still can't quite hammer down the bricking bug yet though.
[HTC Rezound] vinylfreak89:
I haven't looked at the source, but two places you may want to look are in bootclasspaths and any partitions being mounted with the wrong partition number.
[HTC Rezound] antp121:
Could it maybe be the hboot dev block being mounted incorrectly? Seems like the only thing that could possible mess up between s-on and s-off devices. Our hboot block is 12 if that helps...
[HTC Rezound] dmeadows013:
Got my new rez. I just unlocked and will be doing stuff later.
[HTC Rezound] Jonman409:
Yeah I was just experimenting with porting vigor support, should've figured I was super late, lol I'll pick your changes and start experimenting. I hadn't been able to test anything really the past few days with work.

---------- Post added at 09:08 PM ---------- Previous post was at 09:06 PM ----------

I had JB booting but it was throwing so many errors that I reflashed back to CM9 almost instantly. I'm actually setting up a clean repo now dedicated to cm10
[HTC Rezound] chad0989:
I believe I may have solved the brick issue. With my changes I can't seem to induce the behavior that occurred while s-on that I think might be what causes the brick. I'm going to let it run overnight and see if the behavior occurs. If not I will need a very brave tester, someone who is already sending a phone back is preferred. If its fixed we'll be able to post builds again. Pretty much everything works but bluetooth and camera.
[HTC Rezound] DownRiver_Droid:
I was about to send my old phone back, it only had sensor issues. Will test whatever you need after I get home tonight.
[HTC Rezound] chad0989:
Sounds good. I'll pm you a link.
[HTC Rezound] bbeaulieu:
I could also test for you. I'm not sending my phone out or anything but I have an old backup phone in case anything happens.
[HTC Rezound] Snuzzo:
Tried reverting G++ to 4.6.3, still no go. I can brunch it, but in VMware on my Windows installation with Ubuntu 12.04, GCC/G++ 4.6.2.
[HTC Rezound] GrayBoltWolf:
So, is CM9 dead?

I have been trying to sync from VigorCM9 and I keep getting 404s and fetch errors.

Edit:

Tried again and it worked. Still a few 404s though.

It is building now, seems to me moving along quite nicely. Just waiting for it to stop and display some cryptic error like always.
[HTC Rezound] Snuzzo:
VigorCM9 should be fully up to date with CM's git. If you wish to pull in CM9 with the bells/whistles

repo init -u https://github/VigorCM9/android.git -b ics-exp
[HTC Rezound] GrayBoltWolf:
Built perfectly.

What sort of bells and whistles?
[HTC Rezound] Snuzzo:
Bottom status bar. Center clock ....

... take a peak over the ics-exp branches of each project tree.
[HTC Rezound] GrayBoltWolf:
Built CM9 again last night. I built from the ics-exp branch.

I didn't have time to trace commits but I assume that includes flyhalf's changes yesterday.

I am running it right now and it is extremely smooth, better than any other ROM I have ever tested.

Build is available here:

http://goo.im/devs/GrayTheWolf/CM9 Extended

Not sure if I like the status bar at the bottom or the top......
[HTC Rezound] Neo:
LINARO!

Well look at that!

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

HOW TO BUILD A ROM FULL LINARO - by Neo
[HTC Rezound] Snuzzo:
Any jb aosp guys want to run a beta ? Need 1 s on tester and a 2nd opinion from an s off tester.
[HTC Rezound] mavpts:
Sure. S-off
[HTC Rezound] Snuzzo:
Send you a pm in a moment, adb/fastboot general knowledge is all that i require you to know. S on tester still needed. If you don't have enough posts just pm me.
[HTC Rezound] gleggie:
I'm S-On and i can test it
[HTC Rezound] Uzephi:
Not a dev, but know how to pull ADB debug logs. S on

Edit: gleggie may be better s on tester
[HTC Rezound] Snuzzo:
I'll send it over anyway

Check your pm's in a moment.
[HTC Rezound] REV3NT3CH:
I'll take a tester...s-off hboot 2.28 with updated radios on gsm sim card...

Edit: I know how to adb and pull logs as well as a few other odds and ends
[HTC Rezound] Snuzzo:
Why don't you just make the md5 of the new file a string variable?

MD5='md5sum $file'
[HTC Rezound] Snuzzo:
If you still need help Neo send me your copy of the script of what you have so far via pm with pastebin link or email it.
[HTC Rezound] Neo:
Thanks buddy but an xda member wrote one up for me the other day and I incorporated it into the build script from you :) I am testing it today. It's pretty nice and there's no way I could have come up with it.
[HTC Rezound] Flyhalf205:
When are you guys going to build lollipop?
[HTC Rezound] kkozma:
I'll just leave this here really quick. :p
[HTC Rezound] vinylfreak89:
what did you determine was causing the brick?
[HTC Rezound] Hanger84:
I'll test it too.
[HTC Rezound] flying_pigs:
I'm S-OFF, but I'll test.
[HTC Rezound] chad0989:
If the fix works it was a mounting and permissions thing.

@everyone: only need one tester for now. Don't want to brick more than one phone if it doesn't work. If it does work fine I'll have a couple more confirm and then we can start posting builds again.
[HTC Rezound] Argumentation:
If it doesn't brick, I can confirm for you. :good:
[HTC Rezound] mbobino:
Have you pushed the fix to github? I'm interested to see what exactly it is thats causing it.
[HTC Rezound] DownRiver_Droid:
Chad, check your PM.
[HTC Rezound] chad0989:
Fix didn't work. Seemed like it did at first but it eventually bricked. Got some useful info though.
[HTC Rezound] antp121:
Were you s-off? Or does it still even with s-on?
[HTC Rezound] chad0989:
Still only bricks when s off. Can't truly soft brick while s on.
[HTC Rezound] antp121:
That's what I thought. Can't be too safe though lol thanks.
[HTC Rezound] chad0989:
Anyone else getting ready to send one back who can test?
[HTC Rezound] apophis9283:
If you cant find anyone, mine is still covered. As long as they cant see i have been s-off I dont care. Apophis9283 = brave soul
[HTC Rezound] DownRiver_Droid:
I will try it again once they receive my paperweight back if you still need testers.
[HTC Rezound] TXI Kaze:
I can. Just got my replacement today so I have some time before I have to send the other back.
[HTC Rezound] chad0989:
PM sent.
[HTC Rezound] TXI Kaze:
Well, that was an interesting turn of events. I was switching everything over to the phone I was going to test (SIM, battery, SD card) and somehow managed to sling my SD card somewhere. I was just trying to slide it out and it turned into Usain Bolt and shot like a rocket from my phone. Unless my SD card is the magic bullet from the Kennedy shooting and it somehow ricocheted ten feet away, I have no clue. I can't find it, and it could have only gone four feet. So, going to look for it and see if I can find my old 16GB card for now. Chad, I'll message you once I get everything sorted, installed, and booted.

EDIT:

Good news, everyone!

All jokes aside, found. My computer, 360, router, etc. all sit on my dresser. My SD card somehow went into a drawer that was slightly ajar. Time to get back to it lol.
[HTC Rezound] killahrey:
I got a rezy that I'm sending back. Buttons wont light up, I know how to fix it probably but I want a new one anyway lol. Warranty ends 9/30/12
[HTC Rezound] chad0989:
So far so good with the latest tester. Hopefully new builds can be posted soon.
[HTC Rezound] chad0989:
@jonman, meadows, joelz, anyone else:

You guys working on anything? I haven't noticed much activity around here. Got JB going strong?
[HTC Rezound] dmeadows013:
Not really lately. Been busy with school starting and all. I'll try to do some more this weekend. I'm waiting for Jonman to get his 3.0 kernel to compile and then I'll try it with my AOKP JB tree.
[HTC Rezound] renzo.olivares:
I haven't tried beyond boot animation preoccupied with school atm
[HTC Rezound] a.mcdear:
Did you create a new tree for JB or are you just building off the ICS one? Just curious cause I was just about to start working on a JB port but was gonna use the ICS tree that you made way back when..

Also, what is this Arizona from your sig?
[HTC Rezound] RLKirk:
Haha I'm gonna guess he meant Arizona drink. Watermelon is my favorite.
[HTC Rezound] dmeadows013:
I built a fresh one.

Aww yea man. Southern Sweet is the bomb.
[HTC Rezound] TXI Kaze:
Still going, no brick.
[HTC Rezound] Snuzzo:
Edited.....

Delete. I don't like to read LOL
[HTC Rezound] localceleb:
S-off?
[HTC Rezound] TXI Kaze:
Yes.
[HTC Rezound] killahrey:
Damn straight :D
[HTC Rezound] chad0989:
Sorry, I missed this. Turns out it was a vold issue exacerbated by some init.rc stuff.
[HTC Rezound] excellentnuke:
Is the RIL fix going to be in the next update?
[HTC Rezound] mbobino:
The RIL fix is already present and has been for 24 days (according to Chad's GitHub). If you are talking about the network indicator fix then I'd imagine anyone that does builds will clone Chad's repo's which will include the fix.

Here is a link to the GitHub commit
[HTC Rezound] SynisterWolf:
same
[HTC Rezound] dmeadows013:
So builds can get posted now?
[HTC Rezound] mbobino:
Looks like the fix was uploaded to github earlier. Im doing a build right now to test for myself. Hopefully I wont brick xD
[HTC Rezound] killahrey:
Build it, i will test :D
[HTC Rezound] dmeadows013:
Which commit was it? Sorry missed all this lol