yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] dlumberg:
the 4.2.2 drop builds and boots...
[HTC Rezound] mjones73:
Nice, it looks like it fixes a bug in bluetooth audio, I know mine likes to skip from time to time with cm10.1...
[HTC Rezound] kkozma:
I've got a build 4.2.1 build running right now with the 4.2.2 bluetooth changes. I'll report back later this evening if it works.

In the meantime, you can get the BT audio to stop skipping if you turn off wifi.
[HTC Rezound] kkozma:
Looks like it worked. :) Just got back from the garage where I listened to two complete songs on Pandora. I tried with wifi on, off, toggled it on and off a bunch of times, and finally left it on but not connected to any networks. It didn't cut out or skip once, so I'm pretty pleased. However, I've been snookered before on this though, so I'll reserve final judgement until I can drive up the street from my house until I lose signal. That seems to be when it was the worst for me. Stupidly, I didn't think to try a phone call so I can't comment if that still works, but I'm fairly certain it does.

I've made a few other changes to bluetooth to try and improve sound quality and I feel it sounds pretty damned awesome. If you guys think we need yet another vanilla CM10.1 rom, I'd be happy to post it.
[HTC Rezound] kkozma:
Oops! A mod can nuke this if needed.
[HTC Rezound] lmt1979:
What was the fix?

The thread never states how this was fixed or worked around after discussing it for building 10.1. Same error as quoted above build/core/base_rules.mk:130: *** hardware/qcom/media/libstagefrighthw: MODULE.TARGET.SHARED_LIBRARIES.libstagefrighthw already defined by device/htc/vigor/media/libstagefrighthw. Stop.

Here's the error:

https://docs.google.com/file/d/0B3qV-scfklSkSFVseFVHOGVQeFU/edit?usp=sharing

Thanks
[HTC Rezound] shrike1978:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Revert the commit from hardware_qcom_media that is described as allows msm8660 into repo.
[HTC Rezound] wildstang83:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

I gotta say thanks to shrike because he did say how to fix that error and that error has been discussed numerous times. His tip to cd to hardware/qcom/media and run "git log" has been so helpful. If you run git log in the media folder you can easily find the faulty commit and remove it.
[HTC Rezound] Snuzzo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Who here is into using emmc as primary storage for our aosp ROMs?
[HTC Rezound] a.mcdear:
I would prefer the EMMC storage be /sdcard so that the system uses it by default, and the removable sdcard set to /sdcard1 or /ext-sd or something like that. Seems to be the way its usually done. Even the internal storage on my Nexus 7 is called /sdcard
[HTC Rezound] Snuzzo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

But the nexus 7 doesn't have an SD card slot. Again who wants emmc as primary?
[HTC Rezound] apophis9283:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Yeah, nexus devices have no external sd card. Although it does have the ability for OTG.

Sent from my Gnex running the most awesome AOKP build
[HTC Rezound] kingpin003:
That's snuzzo's point. There is no issue on Nexus devices because they do not have an sdcard to cause conflict, so it doesn't matter what they call it.

@Snuzzo I personally think as long as all AOSP stays consistent, there's nothing wrong with it how it is. It's annoying when you do a full wipe and it erases the unlocker keys(such as TiBu) on /emmc. I get that the EMMC issue is the number one source of confusion when people first flash AOSP. It makes sense to me why it is labeled how it is, but I also think it creates just as many issues and we can't keep switching back and forth.

I honestly wish all android was consistent:

/internal = emmc and Nexus storage

/sdcard = actual sdcards

*shrug* what can you do?
[HTC Rezound] dlumberg:
Why not just mount it in both places?
[HTC Rezound] Snuzzo:
Guess all I can say is for those who wish to try it....

https://github.com/VigorCM9/device_htc_vigor/commit/117d57d3417f9a9d161d90026a75c3e2081bfd11

Its not a modification of mountpoints but tells the frameworks what mount to use.
[HTC Rezound] kkozma:
So what exactly is the purpose of this?
[HTC Rezound] Snuzzo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Just trying to give better utilization of storage space.
[HTC Rezound] nbhnohome:
I do because all of my gps data is on the Internal SD.
[HTC Rezound] IrvChynaman:
http://www.villec2.info/kernel-source-released/

Jelly Bean Kernel Source released for the Ville C2 (HTC One S w/ Snapdragon S3 processor for those that dont know.) Just wanted to leave this here in case the devs didn't catch on yet.

EDIT: I do realize this isnt a direct link to the kernel source. I tried browsing through the HTCDEV website and i can't seem to figure out which one it is to give a direct link, but maybe you guys know better.

EDIT 2: NVM It clearly states in the download links which version it's for. Here's a link to the HTC Asia WWE source http://dl4.htc.com/RomCode/Source_and_Binaries/villec2-jb-crc-3.4.10-055bd56.zip
[HTC Rezound] shrike1978:
FYI, looks like CM finally fixed the issue with hardware_qcom_media.
[HTC Rezound] GrayBoltWolf:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

So we can just sync and brunch now?
[HTC Rezound] shrike1978:
I just built PAC with the qcom_media from CM sources, so you should be able to do so with CM10.1 as well.
[HTC Rezound] GrayBoltWolf:
Hell, I'm going to try CM9. I haven't updated that thread in 6 months.
[HTC Rezound] brenuga:
Well I was wondering today why when I tried to git revert 333d0e460bc6a6579c5193438fa69560abea658f that it was messing up the syntax of hardware/qcom/media/Android.mk

Neo thought I was crazy.

So yeah, no need to do that git revert anymore.
[HTC Rezound] Snuzzo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Check out github.com/vigorcm9

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Max725:
Sorry to be the non-developer asking questions in the development thread, but will this have any effect on the final ROMs, or does it just make building more convenient?
[HTC Rezound] shrike1978:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

Just fixes building. Before, we had to revert a commit to get the build to finish.
[HTC Rezound] GrayBoltWolf:
That's the repo I am building from.
[HTC Rezound] brenuga:
So I found this on the codeaurora project last night:

Chromium Browser for Snapdragon

Snapdragon optimized Chromium browser environment

https://www.codeaurora.org/gitweb/quic/chrome4sdp/

Think someone might try building it? I wonder what the performance gains over stock Chrome would be.

Found this thread where someone in Galaxy S III forum has been building nightlies of this project. Ppl say it's fast, but currently there are a couple of bugs (like can't save and download files.)
[HTC Rezound] Snuzzo:
Gonna look into that later.

Just finished up DSB's aosp branches https://github.com/Snuzzo/DSB_Kernel going to work on brunching with it included.
[HTC Rezound] Jonman409:
Been away for a while, and have some free time to spend on the Rezound. Any info on ION support?
[HTC Rezound] El Schisne:
All I know, from a lay (non-dev) perspective:

1. Chad got a Droid DNA and has been working on that since.

2. The One S C2's Jellybean kernel source was released: http://dl4.htc.com/RomCode/Source_and_Binaries/villec2-jb-crc-3.4.10-055bd56.zip

The C2 uses a Snapdragon S3 like the Rezound and unlike every other phone that HTC has upgraded to Jellybean. I haven't read that anyone has done anything with the C2 source yet wrt the Rezound, and I'm not sure exactly how helpful it will be.

If anyone has any other info, feel free to chime in...
[HTC Rezound] shrike1978:
Last I knew, Chad had stepped back from ION because the cameras were just not happening. 10.1 is PMEM only. 10.1 is really smoothed out in comparison to 10. The biggest problem with 10.1 right now is the video tearing issue on HD playback. We've alleviated a lot of it in the custom kernels, but it's still an issue. Other issues are no video chat support, and the camcorder sometimes completely corrupts the video file it's recording (1 time out of 50 or so).
[HTC Rezound] Snuzzo:
Re: [R&D]CM10/AOKP/AOSP Jellybean Development/Progress Thread

@El Chisne

The only thing useful I found from the source was v4l2 camera drivers. Can I eithererge some of it in to our current source based from chad or can rewrite the whole ion implementation to base it off the 3.4.10 source. Odds are ill be trying to merge in the camera driver in an attempt to correct the purple tint.

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Jonman409:
Interesting. Have you created libcamera stubs to debug the callbacks?

Edit:

Also, why not just rebase off of 3.4?
[HTC Rezound] Hobox10:
Every JB rom I've tried has problems with all video playback, not just HD. Not sure why.
[HTC Rezound] Snuzzo:
Not yet. I just feel like it would be 3x easier to just do a merge of code on the current driver over anything.
[HTC Rezound] badogg:
Not sure if our device is a WVGA device, but this came up in my FB feed this morning: http://xdaforums.com/showthread.php?p=39922386#post39922386
[HTC Rezound] Snuzzo:
Our device is considered HD.
[HTC Rezound] TheBr0ken:
Interesting, looks as if CM is making some more changes to support ancient devices like ours

https://github.com/CyanogenMod/andr...mmit/c7d21c231165576dc33ccd93dafcc1d87c9bdc1d

I forked it and everything related, made the patches to use CM's Frameworks AV, Native and their msm8660-common. I obviously had to rm our media, display-legacy from device_htc_vigor to build. I just booted up and everything seems to work so far, will do further testing. In all it may not be any different than the way Chad had legacy routed, but this way it would require less maintenance and upkeep on our end.

in case anyone is interested and wants to use the already patched repos, just fork ->

https://github.com/TheBr0ken/android_frameworks_av

https://github.com/TheBr0ken/android_frameworks_native

https://github.com/CyanogenMod/android_device_htc_msm8660-common

https://github.com/TheBr0ken/android_hardware_qcom_display-legacy

https://github.com/TheBr0ken/android_hardware_qcom_media-legacy

and

-rm device_htc_vigor_display-legacy

-rm device_htc_vigor_media

I'm assuming since the msm8660-common changes for legacy devices were merged that the others will be too and we wont need our own av, native, display-legacy, media-legacy. Once that is done and everything works as it should without having to patch anything I will send Chad a pull request with the changes
[HTC Rezound] kkozma:
Wow, never thought I'd see the day that they would sorta support our phone.
[HTC Rezound] shrike1978:
They're not supporting us directly. We'll still have the android_device_vigor separate for now. They've just added some directives to detect and handle legacy devices better, so we can use more of the unmodified CM code.
[HTC Rezound] kkozma:
Well FWIW, my Asus Transformer is officially supported but the kernel and device tree don't work for sh!t. In fact, it flat won't boot if you don't use someone else's kernel and device tree. Soooo... Basically the same thing....
[HTC Rezound] TheBr0ken:
I would just say that we would have more CM support by proxy. Just good for us that there are still many, many legacy devices out there. I'm just liking the fact that more device drivers have the potential of being moved away from our device tree. As I mentioned before, by doing this it will put the legacy code into the hands of more developers, which could mean an increased chance if getting some issues resolved for all of us :good:

---------- Post added at 03:06 PM ---------- Previous post was at 03:00 PM ----------

Official is just a title, it would still fall into the hands of the device maintainer to keep up with device specific changes. Last I heard the Rezound was officially supported by AOKP. I wouldn't suggest you build it though. Think things came to a halt at jb 4.2.1
[HTC Rezound] TheBr0ken:
Well a day later and it's just as any other build. mainly just wanted to see of it would build and work. No noticeable improvements or degradations.
[HTC Rezound] shrike1978:
Update on this. CM has done more merging.

I built successfully using only device_htc_vigor, vendor_htc_vigor, and vigor_aosp_kernel from Chad. I got everything else from CyanogenMod. I still had to delete device/htc/vigor/legacy-display and device/htc/vigor/media to get the build to finish.

Does anyone know how to get rid of those without manually deleting? They don't exist in the repo, but they are there after you sync, so I don't know where they are coming from.
[HTC Rezound] Flyhalf205:
They are inside the device_vigor git. Make sure you camera app is still in the apps list. After deleting those two folders like you and building how the msm8660 cm-10.1 git is set up. I lost my camera.
[HTC Rezound] kkozma:
You could always fork device_htc_vigor from Chad and remove them from your local repo.
[HTC Rezound] TheBr0ken:
They are in the repo. You sure you are looking at the right branch? Chads defaults to jellybean, not cm-10.1

Gets me quite often
[HTC Rezound] shrike1978:
Wow...I'm a n00b. LOL
[HTC Rezound] TheBr0ken:
Lmao, I won't tell anybody
[HTC Rezound] Neo:
I do that more often than not.. Simply because it defaults to that branch
[HTC Rezound] TheBr0ken:
You didn't lose your camera because you deleted those two folders, you lost it because you used CM's frameworks_av. You can either stay with Evervolvs or cherry-pick this -> http://review.cyanogenmod.org/#/c/34409 to get your camera back
[HTC Rezound] kkozma:
Nevermind. Stupid type-o's!
[HTC Rezound] Neo:
It was happening a few times yesterday for me. Just gotta keep at it
[HTC Rezound] kkozma:
Thanks, but I *THINK* I figured it out... Had a mistake in my local manifest. It's syncing now and appears to look like it's going to finish,
[HTC Rezound] kkozma:
Ok, I've finally got a brunch running off a straight CM10.1 base and my own local manifest. Looks like it should be good to go.

Here's my local manifest if anyone wants to use it to save some time.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/htc/vigor" name="Chad0989/device_htc_vigor" />
<project path="device/htc/msm8660-common" name="CyanogenMod/android_device_htc_msm8660-common" revision="cm-10.1" />
<project path="kernel/htc/vigor-3.0" name="Chad0989/vigor_aosp_kernel" revision="jellybean" />
<project path="vendor/htc/vigor" name="Chad0989/vendor_htc_vigor" />
<remove-project name="CyanogenMod/android_frameworks_av"/>
<project path="frameworks/av" name="Evervolv/android_frameworks_av" revision="jellybean" />
</manifest>

Once/if CM merges that last patch set for framesworks_av, we can get rid of the last two lines.

AND just like that my build failed. *sigh*

In file included from hardware/qcom/audio-caf/mm-audio/aenc-aac/qdsp6/src/omx_aac_aenc.cpp:41:0:
hardware/qcom/audio-caf/mm-audio/aenc-aac/qdsp6/inc/omx_aac_aenc.h:52:34: fatal error: QOMX_AudioExtensions.h: No such file or directory compilation terminated.

Shrike: Can you share how you got yours to build?
[HTC Rezound] dlumberg:
nvm
[HTC Rezound] shrike1978:
I built today's release of PAC with the older stuff that I know works. I'm still messing with the new stuff.
[HTC Rezound] TheBr0ken:
Bunch of things still need merging. Below lists what you will need to build, cause that's how I was able to build. Needed to make some patches to make it work. We can't build with just cm, but soon.

Right now we're not gaining anything by doing this. Just build with the normal tree we have been using
[HTC Rezound] Flyhalf205:
In file included from hardware/qcom/audio-caf/mm-audio/aenc-aac/qdsp6/src/omx_aac_aenc.cpp:41:0:

hardware/qcom/audio-caf/mm-audio/aenc-aac/qdsp6/inc/omx_aac_aenc.h:52:34: fatal error: QOMX_AudioExtensions.h: No such file or directory

We ever figured out a way past this? without editing CM source.
[HTC Rezound] Flyhalf205:
Did some heavy work on the device tree.

We running off of CyanogenMod framework _av and _native now.... https://github.com/Chad0989/android/commit/f14c92f8e6758bf7077b894b31216cd3c043bc23
​

Legacy camera to add Camera back in with CM framework. https://github.com/Chad0989/android...mmit/11f1e3d93610c2788937eb23d662ebdd406ba373 This is what it exactly does. http://review.cyanogenmod.org/#/c/34409
​

1080p recording. https://github.com/Chad0989/android...mmit/fd18b3b5faa506378cba272a6d12fee671bfa1d9​

Just letting you guys know so if you sync from chad there is a lot of changes. I wouldn't recomend dirty flashes to the next newer builds.

Looks like I have to add liblights back into it for some small things.
[HTC Rezound] TheBr0ken:
Doing a fresh AOKP build with all those changes ;)

Thanks for the continued work, its greatly appreciated!
[HTC Rezound] shrike1978:
Do the camera changes do anything to address the recorded video corruption issue?
[HTC Rezound] Flyhalf205:
I would think it would. I can upload my build for one to test?
[HTC Rezound] shrike1978:
Can't really reliably replicate it. I'm getting ready to do a test build of PAC with the changes. What are the small things that added liblights back in will fix?
[HTC Rezound] Deathbyfugu:
Will any of these changes positively impact the video playback issues, namely artifacts?
[HTC Rezound] shrike1978:
Negative
[HTC Rezound] Neo:
Look what I learned how to do ;)

If this builds out, it will be a rom built completely linaro and not just "optimizing" the build with the prebuilt like we've been doing.

If it works I will post information somewhere on how to build a full linaro rom.

-Neo
[HTC Rezound] brenuga:
I can haz cheezeburger linaro?!
[HTC Rezound] Flyhalf205:
Got ion booting with cm-10.1... :)
[HTC Rezound] TheBr0ken:
now your just showing off :p
[HTC Rezound] Flyhalf205:
If I was to show off. I would say I fixed video tear in CM-10.1. haha

Yes. video tear is fixed.
[HTC Rezound] TheBr0ken:
Ok, I'll just hold off my "your just showing off" till your next post then ;)
[HTC Rezound] TheBr0ken:
Can I say your showing off now?????
[HTC Rezound] Flyhalf205:
Yes. Now I am. Because now I know it actually works lol

Guys!! Anything else that needs working on besides HDMI ?
[HTC Rezound] king.james:
Did you really fix video tearing? Or is that just playful banter?
[HTC Rezound] TheBr0ken:
Yes and yes
[HTC Rezound] dplane:
I'm so confused :eek:
[HTC Rezound] shrike1978:
Are the cameras still FUBARed in ION?
[HTC Rezound] dmeadows013:
Been busy this week with papers and exams but this weekend I'm gonna make jb my ***** :)

Via my Google Galaxy S3 running AOKP goodness
[HTC Rezound] chad0989:
Got it booting with no more crashes.

Mass storage works.

Mic works fine.

Can make and receive calls

Data works

Camera works.

Sorry I haven't gotten it posted yet. Still need to organize since kernel / ramdisk are separate and not building with it at the moment. I've had tons of other stuff going on and haven't really had the time.

Hang tight though.
[HTC Rezound] chad0989:
Everything is up. A few things:

Please

DO NOT

post a ROM built from this yet. There are a couple issues still and you never know if it can cause bricks etc. It needs to be thoroughly tested before anything is posted. If you're adventurous, you're welcome to build it yourself, test, and work on it. If you fix anything please send a pull request back.

Graphics are a little slow. Its is likely because its not using any updates in the kernel to kgsl / msmfb. Could also be the libs. I haven't explored it further yet.

It is currently using a prebuilt ICS init binary. Init scripts need to be updated to build and use the JB init binary.

Camcorder doesn't work currently. Probably something simple but I haven't played with it.

Important:

Ring and alarm don't work. But the speaker does. I think it might be a media codec issue.
[HTC Rezound] dmeadows013:
I'll have AOKP for testing on Friday. Had 4 games this weekend so I didn't have time to do anything

Via my Google Galaxy S3 running sweet sweet Jelly Bean
[HTC Rezound] Neo:
Thanks Chad. I'm curious if dropping the Nexus 4.2 camera into it will change anything. Have you attempted this? I may build this again with your repos exclusively. Grats on the boot
[HTC Rezound] chad0989:
No idea. I try to stick with vanilla CM with only what fixes we need to run it.

Ringtones/alarm fixed thanks to MaulingDeOso. I think I'll work on the camcorder tonight.
[HTC Rezound] chad0989:
Got recording to work but not playback. This includes YouTube playback.
[HTC Rezound] SynisterWolf:
For safe keeping.

Sent from my iPhone...
[HTC Rezound] chad0989:
Fixed video recording. Playback is working now also (youtube included), however the other EGL issues cause it to lag/distort at times.
[HTC Rezound] chad0989:
Memory. Should make future transitioning easier... provided that I can implement it.

I didn't know the device existed.... haha
[HTC Rezound] chad0989:
You can specify a base and size like with PMEM. That way you don't get overlaps. I've moved over SF already and have gotten it to boot by building with the TARGET_USES_ION flag. I'm going to specify specific blocks until I get everything moved over, then I'll let it allocate blocks on its own. If its not possible to move something, then I'll allocate a small separate pmem block for it.

Will ION help with you bringing over the latest msmfb stuff?
[HTC Rezound] chad0989:
Got everything moved over but audio. It actually runs a lot smoother surprisingly. I didn't expect that. Now I just need to figure out how I'm going to arrange everything in the old memory region since currently I'm running with 100mb less ram.
[HTC Rezound] chad0989:
The only thing that is holding me back on the ion transition is that the camera HAL is prebuilt and uses PMEM. I'm going to try to build an updated HAL from the codeaurora source. If that doesn't work I'll have to figure out a workaround.

@siul: the RIL realistically needs the changes I made to the ICS one to fully work. At some point I may make them and submit them upstream.
[HTC Rezound] Neo:
Built CM10 today and it runs beautifully. I haven't encountered a single force close and everything I've tested thus far appears to work ok :)

I noticed after building the rom that I wasn't able to rezip the rom due to duplicate file names existing in same folders. I'm not sure if these attribute to any conflicts within the rom before, but I deleted all the duplicates and haven't had any issues in rom. They are all located in subfolders within /system/etc/terminfo
[HTC Rezound] SynisterWolf:
new gapps are out too.
[HTC Rezound] Neo:
Status Update

I and a few others have been testing my cm10 build for the past 24 hours now. I have not had 1 reboot or error of any kind. Last night I also tethered my tablet through netflix for a couple hours without hiccups or issues via native tether. I have entered every possible setting with no issue.

The only thing I and the others can find is the obvious mms issue and lag from time to time that Chad mentioned. For normal end user use (non dev) I do not feel like there is the possibility for bricking.

I have just completed a second build using the Linaro 4.7 toolchain in hopes that the rom will perform more smoothly. Will report back later.

We of course will continue to test until Chad has given his seal of approval for public release.

-Neo

EDIT: aside from the testers I already have from last night, I do not need any more at this time so please don't pm for it. :)

It's coming guys and a lot faster than anticipated thanks to Chad. We just need to hear the All clear.
[HTC Rezound] Snuzzo:
@Neo

Testing didn't go too well on my end. I couldn't get gapps to load.

Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
[HTC Rezound] SynisterWolf:
Use the 4.2 gapps. They work great.

Sent from my iPhone...
[HTC Rezound] Neo:
I flashed the official Gapps and got them all. Which release did you flash? Should have been this one: http://goo.im/gapps/gapps-jb-20121011-signed.zip (oct 11th)

I also flashed the 4.2 Gapps in another flash just fine.