yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] antp121:
Yeah. I love seeing community coming together, helping each other delve into the mystical world of android development :)
[HTC Rezound] apophis9283:
The way it should be. Truth being yes, im in pain all the time. I didnt give my rom up because of that. I gave my rom up to see how many people i could get to make it awesome. Snuzzo, Neo, Shrike and a few others all jumped into help. Yes i know that makes me a liar but see what i accomplished?

---------- Post added at 04:27 PM ---------- Previous post was at 04:14 PM ----------

Also btw, im trying to see if i cant get paradigm working on the Rezound. Waiting back for a response from team BAMF
[HTC Rezound] Obaterista93:
Ran Paradigm on my mom's gnex. It was really fast
[HTC Rezound] dmeadows013:
Interesting... I'll take a look at that when I can actually get it building lol. MSM8660 Gralloc is being a bad lib :p
[HTC Rezound] MaulingDeOso:
I've actually got the 4.1.2 CM tree building and running with logs (and crashing/rebooting on video because I haven't updated it far enough yet). What exactly is the problem you're running into?
[HTC Rezound] dmeadows013:
Can you send me your tree so I can try and build AOKP?
[HTC Rezound] chad0989:
I haven't fallen off the face of the earth. I've been really busy with other stuff. Still working on everything periodically, just nothing major to report.
[HTC Rezound] badogg:
:cool:
[HTC Rezound] Neo:
No problem man. I've been pulling from your JB repos and hoping for the best lol been at it all day. Take your time
[HTC Rezound] MaulingDeOso:
I scrapped the ramdisk messing with it, but once I get it going again I'll put it and the other trees up next to the kernel at my github account: https://github.com/BearOso

Chances are for gralloc you just to update the headers in your msm8660-common device tree.
[HTC Rezound] dmeadows013:
Yea that's what I was doing. Couldn't figure out exactly what though. Everything I tried either didn't fix it or fixed it and broke something else lol

Via my Google Galaxy S3 running AOKP goodness
[HTC Rezound] dmeadows013:
Took a couple things from your tree to get building. Thanks. Working on video now. JB R&D thread is http://xdaforums.com/showthread.php?t=1952346
[HTC Rezound] Snuzzo:
Chad (and anyone else who wants to look)

I made a small change I haven't utilized yet. I changed where broadcom wlan binaries get placed inside the rom. Using those I found to nearly remove all wifi wake lock on our devices and gets native tether near functional. Should also bring uniformity to kernals as well for aosp based builds.

Will edit this with a link later and better description.
[HTC Rezound] squidder:
Just wanted to bring something up to u guys about the data dropping..it happens a million times a day but I've noticed that whenever I'm downloading something I have NEVER lost data even if it takes hours to download. Not sure if that helps y'all but maybe u can use that to fix it.
[HTC Rezound] Snuzzo:
OK rather than an edit

https://github.com/Snuzzo/android_h...mmit/0515d17bd502e4986db0e20cc1c11d0bc330f61e

There's what I changed.

If you look into the line "CONFIG_BCMDHD_FW_PATH=" of all current kernels you may notice they reference to "/system/etc/firmware/fw_bcm4330.bin" compare it to the Wifi blob in vigor.mk in device in my forked repo in the aokp-ics branch you will see what I am speaking of. This should kill the wifi wakelock some users have and also get native tethering working along with bringing in some uniformity for kernels.

IXNAY on that:

In device-bcm.mk, should be bcmdhd**
[HTC Rezound] dlumberg:
Not sure if any Devs had a logcat of the Bluetooth calling issue so I made one. I've been staring at it for a while and I'm guessing that it might be something with this line:

D/ACDB-LOADER( 127): ACDB -> ACDB_CMD_GET_AUDPROC_GAIN_DEP_VOLTBL_STEP_COPP

as the audio is coming through, just incredibly distorted and then it sounds like some process kicks on to suppress the fuzz.
[HTC Rezound] apophis9283:
I just want everyone to know that there is someone working on BT as we speak. Have faith my friends. It will come.
[HTC Rezound] MaulingDeOso:
We might try enabling ACDB in our global CFLAGS, that might do it.

Try adding the line:

COMMON_GLOBAL_CFLAGS += -DQCOM_ACDB_ENABLED

to the bottom of the device/htc/vigor tree's BoardConfig.mk and rebuild. I don't have any bluetooth devices, so I can't see if it makes a difference.
[HTC Rezound] shrike1978:
I'll try this today and report.
[HTC Rezound] Neo:
I'm compiling a fresh cm build this morning and will try this as well. Report back later

EDIT: Added to the mk
[HTC Rezound] Flyhalf205:
It didn't make a difference in my build :(
[HTC Rezound] Neo:
and you added

COMMON_GLOBAL_CFLAGS += -DQCOM_ACDB_ENABLED

exactly as printed to the bottom of the mk? :/
[HTC Rezound] Flyhalf205:
Copy and pasted word for word.. Did a clobber then brunch. So hopefully your build will turn out different.
[HTC Rezound] erishasnobattery:
FWIW, the ACDB flag doesn't actually do anything in the base CM code. That was added to the msm8660 hardware for a Sony device that was having issues when it was enabled.
[HTC Rezound] Snuzzo:
Eris

You think its an issue with the Blutonium firmware driver used along with pairing to the binary used? Just trying to give some insight here cause ive been everywhere in kernel trying different things.
[HTC Rezound] erishasnobattery:
What I know so far is that the audio subsystem is routing it correctly. Hence the fact that we do get some garbled audio through on occasion and it's not going anywhere else (ie Handset or Speaker) at the time.

I am going to assume that the kernel knows what to do with bluetooth, since from scanning the commits, nothing has really been changed from stock and it does work on Sense.

This leads me to believe that about the only thing left is a binary issue. In reading logs from Sense vs AOSP, about the only thing that really differs is some Bluetooth initialization that occurs after the initial routing to the device that either 1) isn't happening in AOSP or 2) isn't being logged in AOSP. Just judging from the insane level of logging in the AOSP stuff, I assume it's the former.

In between doing the things I actually get paid for, I'm pushing binaries around testing my theory.
[HTC Rezound] Snuzzo:
OK guys, just brought in old himax driver/pmem buffer increase to 64MB to my kernel and it works on Sense 3.6 Global along with current CM9 based builds (I need to update AOKP). I have working wifi fine on a build using HTC binaries. Looks promising guys. Tested using both my source and apophis source on his personal usage only kernel build. Looks like we're going to get some uniformity. :)
[HTC Rezound] MaulingDeOso:
The stock kernel has stuff that relies on the HTC framework to initialize correctly, as evidenced by the touchscreen and mono sound channel problems, so it still could be there. Though I'll agree with your guess that the issue is in user-space somewhere, probably having to do with missing encoding or noise cancellation.
[HTC Rezound] imparables:
Man, you guys are freaking awesome.
[HTC Rezound] Snuzzo:
Still no headway made on BT phone call audio on my end.
[HTC Rezound] Snuzzo:
Ok guys sent Chad a pull request that will fix wifi wakelock that heavy wifi users been having. It has been tested by 3 people so far. Not only does it get rid of most of the wakelocks the different firmware is also a little easier on the battery.

https://github.com/Snuzzo/vendor_htc_vigor/commit/645495026ac680e7d0ee49b7478da6ec6d2d82ea
[HTC Rezound] Snuzzo:
Don't yet.

Read my comments on it

https://github.com/Chad0989/vendor_htc_vigor/pull/1
[HTC Rezound] Snuzzo:
This works fine with source drivers.
[HTC Rezound] Snuzzo:
You can. I'm staying here.

Sent from my ADR6425LVW using Xparent Green Tapatalk 2
[HTC Rezound] chad0989:
Where's the cleanup crew?
[HTC Rezound] erishasnobattery:
Back on topic... Chad, I think there's a pmem allocation problem with Bluetooth. It's not my area of expertise and I don't think it will cure all our woes, but it's worth looking into.
[HTC Rezound] shrike1978:
Chad,

The CM team committed to the ICS branch 13 days ago and broke the build. You need to pull in https://github.com/CyanogenMod/andr...mmit/c0b1c0f5818e451725d2385df356ba666fead90c to android_frameworks_base to match the commit that was made in android_packages_apps_Phone.
[HTC Rezound] The-Captain:
Someone call me? :D

My inbox is always there or the report button, can't watch every thread!

I''ll go through last few pages now, but please remember that the report button is there! (or just PM me, whichever is convenient for you.)
[HTC Rezound] dlumberg:
I noticed that this never got put into my logcat

ALOGI("Turning noise reduction and echo cancellation off for BT "

around line 1340 of qcom/Audio/msm8660/AudioHardware.cpp

I put some debugging to see if it was getting turned on on the line above it

key = String8(BT_NREC_KEY);
if (param.get(key, value) == NO_ERROR) {
if (value == BT_NREC_VALUE_ON) {
mBluetoothNrec = true;
ALOGI("Turning noise reduction and echo cancellation ON for BT qcom/Audio/msm8660/AudioHardware.cpp 1337"
"headset");
} else {
mBluetoothNrec = false;
ALOGI("Turning noise reduction and echo cancellation off for BT "
"headset");
}
}

but I bricked my Rez trying to replace the digitizer before I could flash the build.
[HTC Rezound] dlumberg:
Got my replacement Rez... I tried this bluetooth fix with the code changes here. It didn't work, although it seems like the static sounds a little bit better...

I don't remember the audio coming back after it fades out but with this "fix" it fades back in. It seems to be making the connection and the audio is getting routed to the bluetooth device and the bluetooth stack isn't crashing so I'm convinced that the echo/noise cancellation isn't getting turned off for bluetooth connections.

I'm gonna keep at this if anyone has any ideas I'd appreciate the input.
[HTC Rezound] chad0989:
Did you try turning off the noise cancellation completely and see if it works?
[HTC Rezound] dlumberg:
That was my next step... I'll do that tonight. I was also thinking about completely disabling HTC_ACOUSTIC_AUDIO to see if that made a difference.
[HTC Rezound] dlumberg:
My VM got too big and win7 was giving me errors so I'll have to play with my dual boot and move some stuff around before I can build again...
[HTC Rezound] GrayBoltWolf:
It's not that bad.

Make sure you download and burn boot repair.

Goes like this:

Install windows

Install Ubuntu

Use bootrepair's automatic thing to restore grub.
[HTC Rezound] mavpts:
I had real bad issues with grub and win 7. I actually use win now to boot the mbr of my ubuntu drive. Don't remember what the app is called now to do it though
[HTC Rezound] apophis9283:
Use easy bcd to control the boot process.
[HTC Rezound] dlumberg:
I've got ubuntu setup no problem (x with emerald), it's that I tried moving the repo out of the vdi onto an NTFS partition and nuked the permissions.

Edit: I think I got it fixed with

repo forall -p -c 'git checkout -f'
[HTC Rezound] GrayBoltWolf:
We need to get out of the dev thread.
[HTC Rezound] dragonstalker:
Thank you.

Lets try to keep this focused on Devs and helping other Devs with control over making faster smoother roms. If you have questions, please move them to the correct section.

Thanks,

DragonStalker
[HTC Rezound] cslingerland:
I imported the binaries from the htc evo 3d bluetooth module which enabled voice over bluetooth calling to work, but at the expense of the audio streaming. To overcome this, i believe we have to merge the source of the lg intuition with the evo 3d binaries and make sure we are sync'd to the right repo in order to create the correct framework. If we do all of this correctly, i believe that the ultimate rom will be created and life itself will never be the same.

edit: i almost forgot to tell everyone, the source binaries are incompatible with the sense binaries . trying to merge them will cause all your commits to commit suicide.
[HTC Rezound] dlumberg:
disabling HTC_ACOUSTIC_AUDIO didn't change anything.
[HTC Rezound] cslingerland:
I know im not a dev and if this is out of line, forgive me. but i have info.

from the logs provided from SirGatez, http://xdaforums.com/showpost.php?p=35040055&postcount=618 , we found that we are missing some files for MHL to work.

android/hardware/display seems to be the directory we are missing

Snuzzo found a file that is called on in a few files called DisplayManagerGlobal located in android/hardware/display

I have created this folder and placed the DisplayManagerGlobal file in it. I also have found a few files that look necessary and call on the display folder and included them. if you wish to hear everything i added/changed, pm me or gtalk me.

as for what's next, i believe that we need to find this and get it working. http://developer.android.com/reference/android/hardware/display/DisplayManager.DisplayListener.html

i am more than willing to build and test once i think all the required files are there, but my skills with code are not the greatest so i would love for someone to check it out and see what they can find out and/or fix!

Thanks to SirGatez for the logs and Snuzzo for the Global file.
[HTC Rezound] kkozma:
OK, I'd like to throw my resources into the hat of trying to help fix bluetooth. I'm good with reading and understanding code, no problems there. Problem is I'm not sure where I need to be looking since I've never worked with Android. I took a look around at some of the files in qcom/audio/msm8660 but I'm not sure if that's the right place to start.

Any pointers of where I can start would be greatly appreciated.

Thanks in advance!
[HTC Rezound] cslingerland:
building right now with a potential fix for mhl... crossing my fingers. dont get your hopes up too high though as i am a noob and probably didnt accomplish anything. but its worth a try. :) will report back with results in the morning

Update: build broke. right at the end.... very depressing... Hoping its just my java version. Updated and rebuilding. Off to bed.
[HTC Rezound] dlumberg:
So it looks like BT phone is connecting to these

static const uint32_t SND_DEVICE_NO_MIC_ANC_HEADSET = 17;
static const uint32_t SND_DEVICE_HEADPHONE_AND_SPEAKER = 18;

from this logcat:

E/AudioHardwareMSM8660( 142): value of device and enable is 17 0 ALSA dev id:37
E/AudioHardwareMSM8660( 142): value of device and enable is 18 0 ALSA dev id:38
D/AudioHardwareMSM8660( 142): deleteFromTable stream 3
D/AudioHardwareMSM8660( 142): updateDeviceInfo: E
D/AudioHardwareMSM8660( 142): The node type is 1
E/AudioHardwareMSM8660( 142): value of device and enable is 17 0 ALSA dev id:37
E/AudioHardwareMSM8660( 142): value of device and enable is 0 1 ALSA dev id:0

Most of the code for the audio routing is in qcom/audio/msm8660/AudioHardware.cpp

The device definitions are in device/htc/msm8660-common/BoardConfigCommon.mk

I think the bluetooth binary source is at system/bluetooth although I'm mostly a web developer and mucking around in C is new to me.
[HTC Rezound] Snuzzo:
See anything in your logcat with a dev id: 6 ?
[HTC Rezound] dlumberg:
nope, just 0, 37, 38
[HTC Rezound] Snuzzo:
Sounds like we need to re-route then. ;) Dev ID 6 is Bluetooth. Now what kind of device were you trying to connect to? Either that or it's attempting to connect Alsa sound from the above(assumption). Checking kernel......
[HTC Rezound] dlumberg:
It's the bluetooth in my car (non-OEM stereo with a very basic profile) but I have an old logcat from connecting to my Win7 box (with BT3 drivers and full headset support) and it does the same thing there so it's not that the stereo should be using the carkit which looks disabled.
[HTC Rezound] kkozma:
If you think it'll help, I have a thunderbolt I can load liquid ICS CM9 on to connect and make a BT call with and compare logs. Can't imagine it would be completely useless to try.
[HTC Rezound] kkozma:
So unless I'm missing something... I don't see where dev id:37 or 38 are defined.

And to make sure I'm understanding this right..

SND_DEVICE_NO_MIC_ANC_HEADSET should be the BT headset

-and-

SND_DEVICE_HEADPHONE_AND_SPEAKER should be the A2DP streaming device?
[HTC Rezound] kkozma:
Anyone? I feel like I'm banging my head against the wall trying to figure this all out by myself! haha

Looks like the HTC Amaze 4G (also MSM8660) which is an officially supported CM device has no working BT calling either.
[HTC Rezound] dlumberg:
The 37 and 38 are ALSA ids so they would be defined somewhere in the ALSA code, the 17 and 18 are the actual device layer and probably closer to what we're trying to find (It's connected and getting sound but then dropping out). I feel like it should be running through 6 (SND_DEVICE_BT).

A bluetooth call logcat of the TBolt would be great, a sense rom would probably be useful too.

You're not alone...
[HTC Rezound] TheBr0ken:
Or a logcat of a sensation which is an msm8660 device with working BT on aosp I believe
[HTC Rezound] dlumberg:
Whoops, just saw this further in the file

static const uint32_t DEVICE_BT_SCO_RX = 17; //bt_sco_rx
static const uint32_t DEVICE_BT_SCO_TX = 18; //bt_sco_tx

---------- Post added at 08:04 PM ---------- Previous post was at 07:25 PM ----------

So this is interesting... I swapped these 2 to see if maybe transmit and receive were opposite on vigor and it did the same thing as before...
[HTC Rezound] kkozma:
Ooops poor word choice, didn't mean I was alone in solving the problem. Hopefully I didn't offend anyone Just that I was looking for some more help as to where I might find the bits of code that are important to the process here. Still very new to this and am trying my hardest to figure it all out.

Ok, I'll load up CM9 on the t-bolt tomorrow and see what we can figure out.

If you look in the Amaze 4g CM10 thread, there's a logcat of on the last page of a BT call from a sense rom.
[HTC Rezound] dlumberg:
I got what you were saying... I meant that I'm a web developer/troubleshooter this is all new to me too...

I'll checkout that logcat and see if it helps.

EDIT:

This is interesting:

D/AudioHardwareMSM8660( 125): ACDB -> Sent VocProc Cal!
D/AudioHardwareMSM8660( 125): enableDevice(17 0)
D/AudioHardwareMSM8660( 125): enableDevice(18 0)
D/AudioHardwareMSM8660( 125): android::status_t android_audio_legacy::updateDeviceInfo(int, int, bool, bool, int) Enable New Device (VOICE_CALL, PCM_PLAY, FM_RADIO, LPA_DECODE) = (1, 0, 0, 0)
I/HTC Acoustic( 125): set_audio_effect: Phone_Handset_Dualmic
I/HTC Acoustic( 125): set_audio_effect: match with name Phone_Handset_Dualmic (4)
I/HTC Acoustic( 125): found enabled DSP firmwares and return 0
I/AudioHardwareMSM8660( 125): aic3254_config: sound effect (Phone_Handset_Dualmic) 0 0 2
D/AudioHardwareMSM8660( 125): enableDevice(0 1)
D/Bluetooth HSHFP( 539): AudioStateIntent: 60:38:0E:AD:AA9 State: 10 PrevState: 12

I haven't seen any ALOGs from HTC Acoustic before even though AudioHardware.cpp is littered with references to it... might be the problem and explain the handset echo that people complain about...

Can anybody who is more kernel savvy confirm that CM is actually loading and using the htc_acoustic lib
[HTC Rezound] kkozma:
I was thinking kernel too, but then I thought that you can use Snuzzo's kernel for both sense and AOSP and BT works fine with sense... So, unless I'm over simplifying things here, that would seem to indicate something with CM itself rather than the kernel. The only other thing I can think of is that it's got to be something with the BT stack CM uses versus the proprietary junk that HTC uses.
[HTC Rezound] Flyhalf205:
It still could be kernel. His AOSP kernel should be based off of Chad's source and his sense off of stock. Chad has modified the stock kernel a lot to get AOSP to boot.
[HTC Rezound] Snuzzo:
You are quite correct. I've been in & out of bluetooth and sound so many times and messed with almost everything. I had pretty much given up on getting the rest of BT working.
[HTC Rezound] kkozma:
Snuzzo, can you point me in the right direction? Not sure where I should be looking and a fresh set of eyes can't hurt.
[HTC Rezound] chad0989:
What instructions are you following to build?

It sounds like the whole repo may not have synced.
[HTC Rezound] zone23:
I'm piecing it together but mostly this:

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

I'm taking notes and if/when I ever getting working I will post them. BTW I'm on OSX Mountain Lion.
[HTC Rezound] Jonman409:
Here's what I do

"repo sync"

". build/envsetup.sh && brunch vigor"

And to clean:

"make clobber"

---------- Post added at 12:20 PM ---------- Previous post was at 12:17 PM ----------

Chad: I'm sure you have, but if you haven't seen this commit it may be helpful with some ril options/debugging

http://review.cyanogenmod.com/#/c/19912/1

http://review.cyanogenmod.com/#/c/19919/
[HTC Rezound] chad0989:
That actually might be able to replace my RIL if it gets merged. I might try it.

Edit: Definitely going to give the svlte a shot also.
[HTC Rezound] Jonman409:
Yeah, I just cherry-picked it and was going to give it a shot.
[HTC Rezound] zone23:
Thanks I might have to just start over one more time and see if I can get it. Its been a while since I've done this and last time was for the Xoom in Ubuntu so OSX has been a bit of a learning curve.
[HTC Rezound] kaliblazin707:
I made cm 10 bootloop at the splash. :)

Ty chad lol, finally, I can compile aosp/kp now. U Guys are the best!
[HTC Rezound] renzo.olivares:
meh im stuck at bootanimation
[HTC Rezound] chad0989:
Well, you guys keep working on getting CM10 to boot. I'm going to keep working on radio stuff. I wish vzw would hurry up and let the ics ota go so htc can post the kernel source.
[HTC Rezound] d.kozzer:
I hope I'm not out of line to post that it appears that the OTA is starting to go out. I've seen a few posts and articles to that effect, here's one. Let's hope for a speedy release of the kernel source!

Edit: here's another one'

Edit 2: The update PDF on Verizon's site has been updated with the ICS OTA info!
[HTC Rezound] Sheldor1967:
Thanks! and this should be in Rezound General, not this thread...
[HTC Rezound] Jonman409:
Chad, I think I finally got the RIL working 100% with the default ril class "HTCQualcommRIL". I also have External SD working 100% and just disabled the internal until I get higher priority stuff sorted out. I'll clean up my github for you. Would I possibly be able to help with the kernel source to enable some networking modules as well as "xt_qtaguid"?

Edit: Good news is all of the requirements are already merged into JellyBean
[HTC Rezound] chad0989:
That's awesome. You're the man.

I've been meaning to push the source and reorganize so the kernel is built instead of using the prebuilt anyway. I'll work on that tonight.
[HTC Rezound] antp121:
Warning. Meadows used your work, jonman, on a cm build and it bricked hard. Just a warning to any builders out there.
[HTC Rezound] chad0989:
I bricked also. Twice. So did another user. I *think* whats happening is that a partition is getting mounted that shouldn't be and is getting jacked up in the process. Was meadows s-off? I think our best bet is to stay s-on (I talked to jonman about it, he's s-on still) so that the other partitions can't be written unintentionally until we figure out the issue.

Maybe a vold issue?? I believe that could cause it. I know the first brick I had the only changes I had really made was a vendor cleanup (since I ruled out the reworked RIL during the second brick). Maybe we need to use the htc volume daemon instead.

The good news is that once we figure out the brick issue we're going to have a pretty awesome build.
[HTC Rezound] dmeadows013:
I was s-off. Phone just froze while I was playing with it. Then nothing
[HTC Rezound] chad0989:
@ jonman:

I pushed the kernel source and updated the BoardConfig to build the kernel from source instead of using the prebuilt. I also added the needed config options for data monitoring. There may be a couple more but I'm unable to test.
[HTC Rezound] Jonman409:
Wow.. ok. I'm gonna set mine to S-OFF and reflash and see if mine bricks.
[HTC Rezound] pwned3:
Brave man...