yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] kkozma:
Exactly right, this is a challenge now. I just wish I knew more about it so when I run into issues like this, I don't feel like an idiot.

I have a 55 mile one way commute to work and I rely heavily on bluetooth for my audio needs in the car. I also suffer from the misfortune of being an audiophile with a touch of OCD about wires being all over the place. I have a car dock (modded thunderbolt dock to hold this phone) with a hidden USB wire routed under my dash for charging. It all looks really nice and neat. The only problem is that with sense it sounds like complete ass because HTC has determined that the default setting for A2DP bitpool is sufficient. They couldn't possibly be more wrong lol. Since all of their BT crap is proprietary, no one can do anything about it so CM and AOSP are my only hopes for acceptable audio quality.

I did read something recently that CM10.1 no longer uses the bluez stack and has moved to a broadcom stack, so maybe if we can get CM10.1 to work it'll magically fix itself. yeah right!

I'll give it a go a little later on.

Something else I noticed in my logcat...

logcat | grep msm
I/Adreno200-EGL( 2787): <qeglDrvAPI_eglInitialize:294>: EGL 1.4 QUALCOMM build:
AU_LINUX_ANDROID_JB.04.01.01.00.036_msm8960_JB_CL2644550_release_AU (CL2644550)

msm8960? I saw that in the build I just made as well as my build I've been using for over a week which is a straight pull from Chads JB pre-ion branch.
[HTC Rezound] kkozma:
Found some interesting stuff here I may give a shot... It's only time right? lol

https://github.com/Evervolv/android_hardware_qcom_audio-legacy
[HTC Rezound] Flyhalf205:
Interesting find. I can work on it tonight if you don't get around to it.
[HTC Rezound] kkozma:
Yeah, I thought so. Especially when I was looking through the commits and I saw most of the things I have to do to get bruces qcom_audio to build. The only thing that concerns me is the commit to audio_policy_hal to bring it to 4.2.1. I suppose we don't have to include that one.

I more than likely won't get to it much this weekend. It's the wifey's birthday tomorrow and she'd probably double tap me in the nads with a wooden spoon if I spent all weekend at this. LOL
[HTC Rezound] Flyhalf205:
hahaha....

I thought the last 2 commits seemed interesting. I might just pull the entire thing and see if it builds

But even if we used https://github.com/CyanogenMod/android_hardware_qcom_audio/tree/jellybean we still get the exact same results.

---------- Post added at 06:03 PM ---------- Previous post was at 05:50 PM ----------

Audio errors when building happens 7-9 minutes into the build for me. So far it has been 10min. So looks good. I'll test my build after I get home tonight. I just pulled the complete repository https://github.com/Evervolv/android_hardware_qcom_audio-legacy
[HTC Rezound] dlumberg:
I hope it builds, I was playing with BOARD_USE_QCOM_LPA := true and it didn't fail until at least an hour in.

I decided to clone Evervolv's audio and try.... things seem to be moving a little faster now that I'm not watching it through VNC...

Also I noticed that there's ION stuff in AudioHarware.cpp, has anyone tried BT on an ION build yet?

---------- Post added at 12:53 AM ---------- Previous post was at sometime USA PM ----------

Who would have thought that exporting OUT_DIR_COMMON_BASE=/home/monkey/sd/out (SDCARD) would make it compile 3x slower
[HTC Rezound] kkozma:
How'd you guys make out?
[HTC Rezound] dlumberg:
I just flashed it and there is no change...
[HTC Rezound] MaulingDeOso:
You're supposed to target a faster device. That's the whole working directory for the build, and an sdcard is extremely slow. The compile is also many, many gigabytes in size, so if you recompile often you're going to eat up write cycles and quickly kill anything worse than an enterprise-class SSD.
[HTC Rezound] dlumberg:
I don't really care about the SD card, I've got a ton of them lying around. I figured I'd try it out just to split the read and write to different disks. It didn't fit on the card anyway.
[HTC Rezound] Flyhalf205:
My build didn't changed. I made a few changes and i'm building both JB and ICS so fingers crossed. It can't be with the android_hardware_qcom_media because I can clone others with no change. Maybe we should start looking either in the kernel_htc_msm8660 or device_htc_msm8660 but I don't even have a folder for the msm8660 kernel??

Should there be a folder for the msm8660 kernel?

Just saw something about MHL inside of the kernel. I'm going to look more into it later.
[HTC Rezound] TheBr0ken:
Only folder for kernel is kernel/htc/vigor-3.0, though there are kernel related entries in device/htc/msm8660-common
[HTC Rezound] dlumberg:
Progress!??!!!

I just built ION with Evervolv's audio and it connects and I can hear the call happenening. It's still fuzzy but it doesn't cut out for a lot longer and comes back fairly quickly.

I'm gonna rebuild with the cm audio from Chad's manifest and see if it's working...

I tried changing the BT volume level while in a call and there was no response. Also it's acting like when you're listening to a BT audio stream and you get a notification IE: the volume drops, but that's happening to the BT call audio.

It's incredibly inconsistent, most of the time it's just silence with an occasional popping sound coming through. It seems to work if you turn BT on and make a call right away.
[HTC Rezound] kkozma:
awesome!

I noticed something today that struck me as odd. I was messing around with dsp manager and with wired headphones connected, the only thing that affected the sound was changing the Bluetooth settings. Headphone settings didn't do jack. So it's like my phone thinks bt audio is always connected, even when it isn't.
[HTC Rezound] dlumberg:
Interesting... I'm building right now with Very Verbose Logging in AudioPolicyManager.cpp, maybe something will jump out.
[HTC Rezound] wildstang83:
Chad, I'm wanting to try my hand in developing a cm10 rom, but I can't even repo sync.

repo init -u git://github.com/Chad0989/android.git -b jellybean
repo sync

After syncing for a good while it's giving this error:

remote: aborting due to possible repository corruption on the remote side.
fatal: early EOF
fatal: index-pack failed

According to status.github all systems are normal, so maybe something is wrong with the repo?

Maybe not, idk, but figured I'd mention it real quick :)
[HTC Rezound] Flyhalf205:
Maybe this can help?

http://stackoverflow.com/questions/4929674/what-can-i-do-with-git-corruption-due-to-a-missing-object
[HTC Rezound] heyis4horses:
Gray had a similar problem. They started discussing it in the cm10 development thread then finished up in shrikes guide thread
[HTC Rezound] GrayBoltWolf:
Yep. But then it just started working. So, I really don't know what to say.

I am having building issues now though.
[HTC Rezound] dlumberg:
So both Chad's and Evervolv's audio trees are doing the same thing. I figured out that if you don't route the phone audio through the handset or speaker before BT it will connect but be silent.

I'm attaching 2 logcats, I turned on BT and then made a call and hung up on both of them. I think it's interesting how much is happening even before a call is made (search for dat=tel:xxxxxxxxx-xxxx) and also that it seems like it's constantly setting the routing over and over (I noticed that in the PMEM builds too).

I feel like there isn't really anything different happening except that ION is allocating memory more efficiently and so it's taking longer to crash and recovering faster. The extra AudioPolicy info came from uncommenting the 2 debugging lines at the top of AudioPolicyManager.cpp

My brain is fried at this point.... enjoy
[HTC Rezound] kkozma:
I don't know what else to do at this point. I think we need someone a whole lot smarter than me looking into this... :(

I wonder, does anyone know what Chad did to get this working? I know when he first started, there was no BT at all. Maybe if we retrace the steps something will jump out?
[HTC Rezound] dlumberg:
It looks like he pulled in some stuff from Code Aurora

https://github.com/Chad0989/vigor_aosp_kernel/commits/ics
[HTC Rezound] Snuzzo:
OK guys I know the primary focus has been jellybean, specifically cm10 as of late but who would be into like a more unified kernel situation based off most of Chad's source?

I'll be updating my cm9 manifest/device trees soon that will bring back to using CM's wifi binaries. What it would do is seperate a few sources, ICS AOSP, JB PMEM AOSP, & JB ION AOSP. It would be more a refined way to bring in maybe some more people to "jump in on the kernel train" since I have been very very busy with personal life situations and may not have an updated build this week even though I want to add in a couple extras. What I am saying is changing back could be for the better of the whole Rez community as of right now there could be some confusion between what runs on AOKP ICS and what runs on CM9/ParanoidAndroid ICS.
[HTC Rezound] Hanger84:
I'm all for it. For my, ICS has run horribly since the WiFi changes. Ever since then, I get constant system FCs every time I install an app from the market or sideload one...and sometimes even when launching a non-cached app.
[HTC Rezound] DontPushButtons:
I think that's an excellent idea. Like you mentioned, having so many installers for the same kernels seems a little much.

Are there any cons to unifying? So far as I can see it will probably just clean up a lot of the mess and potentially get more people involved, which is certainly a big pro.
[HTC Rezound] CharliesTheMan:
From the little I know, I think that making things more clearly defined and having standardization would be for the better. I'm learning a lot because Snuzzo has taken the time to teach me about building kernels and using git. Any confusion that can be eliminated when we're talking about learning something that's already so much data to take in, is a very good thing. Snuzzo's kernel development is the reason I'm still on the rezound. I appreciate everybody's efforts, I KNOW what a huge accomplishment AOSP was and still is, Chad amazes me. And There's too many rom developers who have made significant leaps to only name a few, you guys know who you are. But for me personally, kernels is where my interest lies.

Snuzzo has been giving us everything he's got time and energy wise. Seriously, he doesn't sleep. Often he and I are brainstorming and working on new kernel advancements in the middle of the night up until it's almost time to go to work at the day job. I would love to contribute more, and I plan to as I learn to build and modify kernels. But with snuzzo working himself to death and still not getting to everything he wants to fit into each weekly build, I can't help but think about what's left to squeeze out of this phone when there are some more people learning to build and building onto snuzzos kernel source and their own kernel source. Snuzzo if you think this change back is a way to accomplish more, I'm all for it.
[HTC Rezound] shrike1978:
I've been thinking about trying my hand at the kernel thing. I want a minimalized kernel for my own use, so I'll have learn something and do it myself to get exactly what I want. ;) I may attempt to start on that after I explore a couple of options I have on the table for PAC.
[HTC Rezound] wildstang83:
I think you would make a great kernel dev. I've noticed a certain little drive in ya that's kinda unique amongst most devs and that's troubleshooting. Your doing good, keep it up. I'm no super hero and I did retire from android deving last night but if you need any help I'll do my best to help ya out.
[HTC Rezound] Snuzzo:
Yeah, my mention of all this is basically to get more of a "standard" going because no offense to anyone, since the split, it's been driving me nuts maintaining like 6 different branches when it could be (when ion is ironed out for now 4) down to 3.
[HTC Rezound] Neo:
@ Hanger: You're alive!!!

@ Snuzzo: As discussed, I too agree with this staying with the working wifi drivers. Hopefully that solves the misc tether issues and power drain
[HTC Rezound] dlumberg:
Any interest in a Rezound github organization?
[HTC Rezound] Snuzzo:
Give it a few more moments. Me and Neo working on getting you guys standards. So far here's what we came up with

https://github.com/VigorCM9
[HTC Rezound] tonekneeo:
All for this. I am all for organization in any fashion.

I am a big boy now.
[HTC Rezound] dlumberg:
I have http://github.com/Rezound

I just added a few people as owners if you want to use it.
[HTC Rezound] Neo:
I believe I got the frameworks/base source fixed to work for building but am doing a test build real quick to make sure it's truly fixed. I also modified my android manifest that we will pull over to VigorCM9 group once I confirm that the build is functional (and has data). If so, the manifest will get you a Stock Linaro build of CM9 without having to modify anything. Simply sync, build the setup, pull pre-builts, lunch & brunch.
[HTC Rezound] wildstang83:
I am at a loss here. What are you guys doing this for? What if other folks wanted to build their own repo's and such, are you saying they can't and have to use this new group thingy you're creating?

....or I'm just totally lost as usual :p
[HTC Rezound] shrike1978:
Once we've confirmed this, I'll update my build guide to point here as well.

---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------

Some stuff is screwed up in Chad's CM9 tree because of some bad merges, and most of us that have it forked have our own stuff in it that deviates from baseline. This will provide everyone a clean, working baseline to pull and fork from.
[HTC Rezound] Neo:
Snuzzo forked my old one temporarily for safe keeping, I deleted mine, forked a fresh ics one from CM, and then merged all 5 of Chad's commits from back in July when Ril was fixed for Vigor. Just hoping it builds out and is fully operational.
[HTC Rezound] Snuzzo:
This plus, give you guys standardized kernel, no wifi wakelock, very little BT wakelock, working native tether.
[HTC Rezound] Neo:
Talking with Snuzzo, we have even bigger exciting plans ahead for centralization in mind. Going to take some time but will be epic once it's complete
[HTC Rezound] Flyhalf205:
Are we going to have a new repo to sync from this github?

Made a little progress on MHL if anyone wanted to know this.
[HTC Rezound] Neo:
yes. For now it will just be for cm9. It's the ics branch of my android.git but will get forked over along with the framework/base in my git should this build complete and function properly. Which of course means frameworks base in the default.xml will need to be modified to reflect the base change-over to our VigorCM9 repo
[HTC Rezound] dlumberg:
What's the progress?
[HTC Rezound] Neo:
Still building. Once it completes and I've tested to make sure data works, I will pull the repo over, make the manifest modifications, and let you guys know when it's ready

EDIT: Just realized this wasn't addressed to me.. Muh baaaaad..
[HTC Rezound] Flyhalf205:
It's a whole complete different list of errors than last month :p.

I will get a log up later tonight or tomorrow when i'm not at work.

The TV does see signal coming through and every now it will flicker a extremely distorted green picture on the screen.

I would build it here at work on my laptop takes forever though. My PC at home gets it done in 28min :)
[HTC Rezound] dlumberg:
That's always strangely satisfying. Not as satisfying as it working but...

Setup an ssh tunnel to your home computer :cool:
[HTC Rezound] kkozma:
Yeah, more progress than the countless hours we've spent spinning wheels on bt calling.

SSH tunnel was how I used to get around our internet filters at my old job. lol
[HTC Rezound] iHateWebOS:
I'm also learning kernel developing! We can all be kernel tweaking brothers! Kernelnewbies.org all day!!! My main issue right now is that my only internet connection is my phone. I had to make most of my github commits by editing my files on the github website directly :banghead:
[HTC Rezound] wlmeng11:
Tether?
[HTC Rezound] iHateWebOS:
Yes tether is my only option, and I only get 4g in 3 places in my house so my connection drops constantly. I have to hit airplane mode to get my signal back. Very frustrating to say the least. My only solution for a steady connection is to flash a stock ROM, do what I have to do then flash jellybean and test/repeat
[HTC Rezound] wildstang83:
Group hugs :highfive:

:eek:
[HTC Rezound] Neo:
Ftp'd from phone. Build completed. Going to flash it here in a min and report back once git is restructured a bit

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

Works beautifully. Going to make the changes then fork them to our group repo
[HTC Rezound] Snuzzo:
Here's where the manifest is located fellahs. I am brunching up a vanilla build as we speak.

https://github.com/VigorCM9/android
[HTC Rezound] Neo:
It is done.

You can now build cm9 once again.

As an added bonus, they will also be Linaro optimized.

Https://github.com/VigorCM9

Build it tonight!

repo init -u git://github.com/VigorCM9/android.git -b ics

In the future, we will be modifying this report group to include other roms. We will announce it as they become available.

-Neo
[HTC Rezound] TuxDroid:
What's broken on this variant?
[HTC Rezound] Neo:
The usual problems that were present before. Bluetooth calling for one.

All we have done is re-enabled cm9 building ability, and used the old wifi drivers so tethering and wifi work flawlessly and with less power consumption
[HTC Rezound] Snuzzo:
What IS broken or what WAS broken?
[HTC Rezound] wildstang83:
Easy, don't answer his question with a two sided question, you'll kill the internetz :p
[HTC Rezound] GrayBoltWolf:
Sweet. I will attempt to build in a separate folder tonight if cm10 works.

I will post it in the megathread.
[HTC Rezound] Snuzzo:
Please do so. I am about to take down the current link to the CM9 installer.
[HTC Rezound] GrayBoltWolf:
CM9 installer?

And CM10 just finished so I will build CM9 now.
[HTC Rezound] Snuzzo:
Kernel; v2.0.
[HTC Rezound] GrayBoltWolf:
I'm getting lots of 404s syncing the ICS repo Neo just posted.
[HTC Rezound] shrike1978:
Are they followed by "Server does not provide clone.bundle; ignoring"? Because that's normal.
[HTC Rezound] Neo:
^ ^ ^ ^ What he said ^ ^ ^ ^
[HTC Rezound] iHateWebOS:
Has anyone built paranoid android lately? I'm trying to and I'm having trouble figuring out what to put in the vigor.proprietaries file. It should be generic for all HTC devices, but I'm having trouble finding an example if this file.
[HTC Rezound] GrayBoltWolf:
Yup. I'll try to build in a bit.
[HTC Rezound] Flyhalf205:
Still working with MHL

I'm still working on MHL. I was able to get rid of error

E/AudioPolicyService( 133): bool android::isHDMIMode(): Node /sys/devices/virtual/graphics/fb1/hdmi_mode not found

and now it's just a repetitive

E/OverlayLIB( 124): mRotInfo:
E/OverlayLIB( 124): session_id 0 dst_x 0 dst_y 0 rotations 0 enable 1
E/OverlayLIB( 124): src: width 736 height 1280 format MDP_BGRA_8888
E/OverlayLIB( 124): dst: width 736 height 1280 format MDP_BGRA_8888
E/OverlayLIB( 124): src_rect: x 0 y 0 w 736 h 1280
E/OverlayLIB( 124): decZ: freeing the pipe with zorder = 0 for fbdev = 1
E/OverlayLIB( 124): decZ: Pipes in use = 0
E/OverlayLIB( 124): startChannel for fb1 failed
E/OverlayLIB( 124): setTransform:Unknown state -1
E/OverlayLIB( 124): getZ: return zorder = 0 for fbdev = 1, pipesinUse = 1
E/OverlayLIB( 124): Rotator session failed

I/Adreno200-EGLSUB( 124): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 124): <GetImageAttributes:1102>: RGBA_8888

Any ideas guys?
[HTC Rezound] wildstang83:
No clue, but congrats on RC status! :)
[HTC Rezound] scy1192:
admittedly I don't know a lot about these things, but the resolution seems wrong (736px wide?) and it looks like it might be outputting to a Mini DisplayPort format (MDP_BGRA_8888) which our Rezound doesn't have. Does this match up to a logcat on Sense?

edit: MDP could be Media Dispatch Protocol, not Mini DisplayPort
[HTC Rezound] Flyhalf205:
Sense log shows nothinga bout BGRA_8888.

Here is a log http://xdaforums.com/showpost.php?p=35040055&postcount=618&nocache=1&nocache=1
[HTC Rezound] TuxDroid:
I am wondering what is currently broken besides Bluetooth just so I have an idea what to expect. Thanks!
[HTC Rezound] TheBr0ken:
On pmem which is mostly what's out right now, Bluetooth call audio (streaming works) and hardware accelerated features such as hd video at times can be choppy. Not sure about gameplay, but I bet that too suffers.
[HTC Rezound] Snuzzo:
Building from that manifest, only bt in call audio.
[HTC Rezound] kkozma:
Ok, has anyone synced up CM10 recently and built? I think the CM team pushed something that has broken bluetooth for us again. I just built a 100% vanilla build from Chad's manifest and BT won't even turn on. Anyone else?
[HTC Rezound] GrayBoltWolf:
Works great for me.
[HTC Rezound] kkozma:
*sigh*

Will try another make clobber and try again.
[HTC Rezound] Flyhalf205:
You can try deleting everything in your cm10 folder. Don't delete the actual folder or you will have to re-download everything.

You will repo sync. It will add all the files back without downloading

then the vendor/cm/get-prebuilts

then . build/envsetup.sh

time brunch vigor

This way you will start basically completely fresh files.
[HTC Rezound] nolimit78:
I've done this a few times because I was tinkering and redoing everything was easier than trying to figure out how to fix it.
[HTC Rezound] shrike1978:
FYI for future reference "git reset --hard HEAD" will reset whatever project you are in to the most recent commit. "repo status" will give you a list of all changes in the entire tree, grouped by project. (a "-" meaning no changes)
[HTC Rezound] Neo:
I agree that the --hard HEAD command works well for me also. It's the fix all
[HTC Rezound] TheBr0ken:
So essentially if you mess up to the point of no return, git reset --hard HEAD ?
[HTC Rezound] kkozma:
I got it going again. Thanks guys. I was messing around with some stuff and forgot to revert one tiny change that broke BT. *banghead*
[HTC Rezound] Neo:
True story.

A lot of times however I'll just say screw it and do the whole thing over from start to finish again.

It's just easier to delete and clone it back then to try and undo what's been done.
[HTC Rezound] kkozma:
FYI: I tried that and got some kind of weird git error. I just nuked the directories I knew I was working in and let it sync again.