yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] kkozma:
I still can't get anything other than Edge on AT&T. I don't think WCDMA is working at all. I tried switching to WCDMA and stared at no service until I switched it back to GSM/WCDMA. Any RIL experts around? LOL
[HTC Rezound] dlumberg:
Yep, I re-synced and built and it's fine, I must have caught it in between commits or something.
[HTC Rezound] MikeX10A:
I'm running Neo's Infection 2.5 and the radio is horrible. Is this all related to the RIL from 10.1? Do I have to fall back to a 9 to get a proper signal again?
[HTC Rezound] Flyhalf205:
Do you get the same signal on let's say my latest build as an example?

I'm still making RIL changes. Hopefully I can update them soon.
[HTC Rezound] MikeX10A:
Thanks for the swift reply. I will give your next update a shot.
[HTC Rezound] Flyhalf205:
If anyone is getting in call audio feedback from the earpiece or sounds like earpiece is amplifying the mic. Trying flashing this boot.img. It will work on any cm10.1 rom. It's in a zip format so you can flash it in HBOOT. Just take out the NEW_

https://www.dropbox.com/s/ln18sf5u4o4l16k/NEW_PH98IMG.zip

Let me know if it does fix it. Thanks
[HTC Rezound] dplane:
Cant flash it myself atm but would be super awesome if that would fix it.
[HTC Rezound] GrayBoltWolf:
Is shrike's guide to set up the build environment still applicable?

Just wondering if it still works, so I can start posting builds again.
[HTC Rezound] Flyhalf205:
It should and I think it's pointed to Chads git which isn't updated anymore.
[HTC Rezound] TheBr0ken:
Gimme a sec and I'll send you a script that installs everything needed

Sent from my HTC Rezound infused with XenonHD on xda premium
[HTC Rezound] GrayBoltWolf:
Ooh. Very nice.
[HTC Rezound] TheBr0ken:
PM sent
[HTC Rezound] iHateWebOS:
Me too? :eek:
[HTC Rezound] tburns:
Same meee too?
[HTC Rezound] Flyhalf205:
Got USB tether to work but it breaks mass storage of the external sdcard. Any ideas?

I'll upload the commit to another branch and let someone else figure it out.
[HTC Rezound] Flyhalf205:
[MENTION=456191]hceuterpe[/MENTION] and anyone else

The commit to get USB tether to work is found here. It's the USB: gadget: use CAF android gadget at M8260AAABQNLZA30170

But I do loose usb mass storage of the external_sd. Anyone help me out?

https://github.com/CyanogenMod/android_kernel_htc_msm8660/commits/jellybean?page=4

After this I'll work on the encryption since I am closer to USB tether than encryption.

My testing kernel commits are here: https://github.com/Flyhalf205/vigor_aosp_kernel/commits/cm-10.1-testing
[HTC Rezound] hceuterpe:
Are you absolutely sure you need all of that code to enable tethering?

It looks like you may have pulled this from the Team Hydra commits:

https://github.com/Team-Hydra/andro...mmit/60a69cd4483158d6ce4a07af3dca38d8e379fb64

https://github.com/Team-Hydra/andro...mmit/fbc4d5e8eea89e16efa73f45f1857af4c8e82e4d

https://github.com/Team-Hydra/andro...mmit/98b69d3048a0904dae06f166abb59385875aab6a

Two commits are missing:

https://github.com/Team-Hydra/andro...mmit/d040683a08e3f31c8073c33a2c7569f557a98287

https://github.com/Team-Hydra/andro...mmit/b99972b919c2ee95c814f5d8910afbf66d96de54

Looks like you were trying to add DUN code (do you just need this??):

https://github.com/Team-Hydra/andro...mmit/c8d247e04522114a56cecab8854fa342547811ad

There's mention of this CAF gadget code being yanked from CM10.1 in the CM gerrit review, since they didn't like it:

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

and mention of using multiple LUN instead:

https://github.com/htc-msm8660/andr...mmit/af9fe112053d130d1ec7be04f0cf75b4daa40d24
[HTC Rezound] GrayBoltWolf:
Worked great. All I had to do after I ran the script was edit the .bashrc, get the repo binary, initialize the repo I wanted, get the prebuilts, and then build.

Built CM9 this morning perfectly for the first time in 6 months.
[HTC Rezound] hceuterpe:
Nah, looks like someone threw the CAF gadget code into the CM github anyway.

What if you add the two commits that were missing in my prior mess age (commit SHA1sum ending in 287 and e54) and also include this:

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

Wonder if multiple LUN support is also needed (d24)?
[HTC Rezound] Flyhalf205:
In my test builds. I did have everything you listed missing two post up but I did not have CONFIG_USB_HTC_SWITCH_STUB in the defconfig. I'll try it again with that included. I do wish we can get this working to make neo happy :)

EDIT: I will check out https://github.com/htc-msm8660/andr...mmit/af9fe112053d130d1ec7be04f0cf75b4daa40d24 If it does work then we will be all set to go :) I really think this will work.
[HTC Rezound] hceuterpe:
Did you get this too:

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

I'm not seeing it, at least not all of it.

For instance, at least with multiple board c files, they replace (line 103 in board-vigor.c)

-#include <linux/usb/android_composite.h>

with

+#include <linux/usb/android.h>

They manipulate more or less the exact same code (minus device specific addresses) on 5 different MSM8660 based HTC models.

Also, they add a few more include files under the same path as the new android.h. Not sure if those were modified with them upping the Kernel version that's much newer?

I love this comment :D :D :D

/* add cdrom support in normal mode */
[HTC Rezound] Flyhalf205:
Thanks [MENTION=456191]hceuterpe[/MENTION] for pointing that multiple LUN for me. That worked great. Only thing is I get 8 drives under "My Computer". I went ahead and pushed the commit. Working fine for me. I'll look into it later. But for now it's working :good:

Looking at the doubleshot they didn't touch

#include <linux/usb/android_composite.h>

with

+#include <linux/usb/android.h>

I'll still test around with it.
[HTC Rezound] hceuterpe:
Huh that alone worked, at least sorta?

I wonder if you yank out the code from board-vigor.c, similar to the commit against 5 devices? Also, the doubleshot board was imported like 8 days after the USB commits...wouldn't be surprised if it doesn't work right with that particular model?
[HTC Rezound] Flyhalf205:
I took out the code from the board-vigor.c and i wasn't able to mount external storage even with that commit. Could be that linux/usb/android.h was missing a line that CM code has...
[HTC Rezound] hceuterpe:
I don't think android.h even existed until that series of commits in the CM MSM8660 code. IIRC, I didn't see that file in your test branch?
[HTC Rezound] Flyhalf205:
https://github.com/Flyhalf205/vigor_aosp_kernel/commits/cm-10.1/include/linux/usb/android.h

It was created under USB: gadget: use CAF android gadget at M8260AAABQNLZA30170 and modified under the bulk change.
[HTC Rezound] Flyhalf205:
[MENTION=3419683]Snuzzo[/MENTION] and [MENTION=4803670]iHateWebOS[/MENTION]

You'll need to cherry-pick bb8dbe6b9950d7a9216231e2b0ce59e387bae19a and b101284a89b4b5da3dbad826e62dfde1a85400ec from https://github.com/Flyhalf205/vigor_aosp_kernel/commits/cm-10.1 to get USB Tether to work.
[HTC Rezound] hceuterpe:
Is the USB tethering still popping up 8 Mass storage devices on Windows?

Any reason why the radio gets conked out on enabling data encryption :) Seeing as how I think the error is early on the boot process I'm not aware of an easy way to capture a log for that particular incident??
[HTC Rezound] Flyhalf205:
Yes. Still popps up with 8 devices in Windows. Will hopefully get it fixed soon.

No idea about the radio. I'll look into the ramdisk if that needs to be changed. But is there any other msm8660 with encryption?

And I noticed when adding encryption on some devices. The recovery.fstab is modified. Does our /data partition need to be wiped a specific way?
[HTC Rezound] Flyhalf205:
Check this. You'll probably look into it before I get time later. https://github.com/htc-msm8660/andr...mmit/9f166fb6d8874d893829df986996e6244c8ea469
[HTC Rezound] GrayBoltWolf:
Have we abandoned CM10?
[HTC Rezound] Flyhalf205:
I think so because everything works in cm10.1 besides mhl of course
[HTC Rezound] shrike1978:
Plus, CM themselves have abandoned CM10.
[HTC Rezound] hceuterpe:
In order for your phone to properly wipe data you need this line back, in recovery.fstab.

/data ext4 /dev/block/mmcblk0p35 length=-16384

Then I had to rebuild TWRP recovery img and flash it, and wipe data. Without it, you will see in logcat that the cryptfs (I think it was that at least), will complain that the data partition extends into the footer and refuses to continue (it actually just "hangs", but you can hit back).

We have this in the right place (on post-fs-data)

# Set indication (checked by vold) that we have finished this action

setprop vold.post_fs_data_done 1

https://jira.cyanogenmod.org/browse...plugin.system.issuetabpanels:all-tabpanel#c34

The init.$device.rc file has to use the new "mount_all" command for mounting /data instead of the normal "mount" command. "mount_all" requires the device's boot image to contain an fstab file with information on the device's filesystems.

doubleshot doesn't actually have that at all, so I am really suspect if encrypt works on it at all. Also Team hydra can't possibly have encryption working for Sensation/Pyramid because their fstab is missing the encryptable OpenSensation appears to have the right pieces, so it wouldn't hurt to ask if encryption is working for them??

At this point, I suspect the issue is in init.vigor.rc. For instance, it has two qmuxd service definitions...that can't be right.
[HTC Rezound] GrayBoltWolf:
Even bluetooth calling?

I just built CM10.1 this morning, I may have a go. But the lack of smoothness has be stuck on CM9.

Edit-

Here is that build if anyone wants it: cm-10.1-20130531-UNOFFICIAL-vigor.zip

(geez, 36 downloads and I haven't even advertised it yet.)
[HTC Rezound] shrike1978:
Yep. The new AOSP bluetooth stack in 4.2 fixed BT calling for us with no effort on our parts.
[HTC Rezound] mavpts:
Did you try an ion build? Love it for smoothness.
[HTC Rezound] GrayBoltWolf:
I'm about 85% sure I have an ion build because it can actually keep up with my finger.
[HTC Rezound] Deathbyfugu:
I hope it is near done. Sounds great
[HTC Rezound] Flyhalf205:
For you CRT lovers out there. cm10.1 may be getting it soon if this merges. It will be a option in settings to use or not.

http://review.cyanogenmod.org/#/c/43544/
[HTC Rezound] bunchies:
Wrong thread :eek:
[HTC Rezound] Flyhalf205:
[MENTION=3419683]Snuzzo[/MENTION] and [MENTION=4803670]iHateWebOS[/MENTION]

Fix for the extra Mass Storage devices when plugged into pc.

EDIT: Only shows the extra devices on Windows PC

https://github.com/Flyhalf205/vigor_aosp_kernel/commit/09614f7774b5a0c03a4577c3375ff467208f8d64
[HTC Rezound] Snuzzo:
Thanks dude. I'll bring it over when the next upstream hits. Fyi; I don't show the extras when on linux

Sent from my ADR6425LVW using Xparent Red Tapatalk 2
[HTC Rezound] Flyhalf205:
Have you looked more into this or got it to work yet. I will need to rebuilt TWRP and CWM if you are able to get this to work.
[HTC Rezound] hceuterpe:
Not yet. I can't seem to tell what's different to the radio when the encryption is enabled. I do notice failures in logcat with the radio trying to turn on...
[HTC Rezound] Purpeltendire:
Deleted.
[HTC Rezound] GrayBoltWolf:
Do you guys think it is possible to get USB-On-The-Go working for the Rezound?

I just watched this video and I am so jelly.

https://www.youtube.com/watch?v=ciR50wDrLqI
[HTC Rezound] Flyhalf205:
Yes if we can get OTG to work properly.
[HTC Rezound] GrayBoltWolf:
I would donate $10 on the spot if you can get that working.

(I know that isn't much for the amount of work required)
[HTC Rezound] Neo:
If anyone can figure it out, it's Flyhalf205.
[HTC Rezound] Flyhalf205:
I know you run CM9 but have you tried this feature on CM10.1 yet? For example my latest build. Recently we have enable OTG in the kernel and a few other things but there are still a couple of OTG changes still to be done to the kernel.

EDIT: Definitely try out my 6/14 build of cm10.1. I have a commit I am going to test that enables OTG Host.
[HTC Rezound] GrayBoltWolf:
I have to get the cable first. :D
[HTC Rezound] Flyhalf205:
I have a cable. Not sure if I have a usb controller. Would the Xbox controller work? I do have a usb one. and what app should I use to test it with?
[HTC Rezound] Snuzzo:
Xbox controller yes and try Dead Trigger.
[HTC Rezound] GrayBoltWolf:
I will probably just make the cable if it is passive.

I think I have a female USB connector laying around.....
[HTC Rezound] twolasrnames:
What about this. https://play.google.com/store/apps/details?id=eu.chainfire.usbhostdiagnostics#?t=

Old rumor on this was you may need a powered usb hub to make this work, SebastianFM didn't think power was supplied out of the usb port, but that was back in the day, and never confirmed.

And, this would be awesome to have work, I'm dying to use Chainfire's dslr controller app, thought getting this to work on the Rez was dead, thanks for trying again. I have a few things I can test, if need be.
[HTC Rezound] Snuzzo:
There is a 5th pin that if ground is sensed or any resistance on it at that will give the necessary sensing that the cable is OTG.

[MENTION=4418505]twolasrnames[/MENTION]

You are correct!
[HTC Rezound] GrayBoltWolf:
So flyhalf, did the cable work?
[HTC Rezound] Flyhalf205:
Can't get anything otg to work for us :(
[HTC Rezound] Neo:
Wait...

You mean to say that you actually ran into something you couldn't fix???

(yet)
[HTC Rezound] Flyhalf205:
Afraid so...
[HTC Rezound] iHateWebOS:
Sebastion said this http://xdaforums.com/showthread.php?t=1820375 applies to us as well.

Edit: the last commit you added is needed for otg. If you check sebs git he already got otg working for the rez

https://github.com/SebastianFM/HTC-Rezound-overclocked-kernel/commits/master
[HTC Rezound] Flyhalf205:
I've made the same changes as him regarding OTG but does the OTG device need to be powered by a usb hub maybe?
[HTC Rezound] cloakzore:
That's the way it works on my Touchpad. It has OTG support but you need a USB Y cable hooking up to a power source. I don't think the micro USB on our Rezound has the ability to power.
[HTC Rezound] iHateWebOS:
First link I posted shows how to make it work

Edit: that guide actually references the Rez and sensation
[HTC Rezound] Flyhalf205:
Hmm Thanks for that info. :good: So maybe OTG works on the current build but I need it to be powered. Do you think a USB powered hub would do it?

---------- Post added at 11:46 AM ---------- Previous post was at 11:45 AM ----------

I've made those changes already. Just need a powered hub
[HTC Rezound] iHateWebOS:
The board of HTC Sensation isn't capable of giving power to USB peripherals, so USB Y Cable or USB Hub with external power supply is required to connect USB peripherals to the phone. You can connect different types of USB peripherals: USB Hub, USB mass storage devices (e. g. USB HDD, USB Stick, MP3 player), USB HID devices (e. g. USB mouse, USB keyboard, Wireless mouse or keyboard with USB receiver).
[HTC Rezound] cloakzore:
Should work.
[HTC Rezound] iHateWebOS:
I don't remember if it is or isn't, but I remember that disabling otg whitelist increases compatibility.
[HTC Rezound] GrayBoltWolf:
Ok, I found a female USB connector in one of my many many boxes of useless cables and electronic parts. (I just don't have the heart to get rid of them)

I am going to make a regular USB OTG cable first. If that doesn't work with a powered hub, then I am going to make one with a Y adapter thing to provide the power externally.

Time to heat up the soldering iron.....
[HTC Rezound] Snuzzo:
In case you missed it wolf.
[HTC Rezound] GrayBoltWolf:
Duh. I have gone through 2 cables already because the manufacturer didn't even bother to include the 4th pin.

If the next one doesn't have it then I am just going to buy one.

Edit:

Ok, so third time is the charm. Got one with a PCB breakout just waiting for me to hack it!
[HTC Rezound] GrayBoltWolf:
Welp, epic fail.

Since it is a homemade cable, I don't know if the problem is with my wiring or with the Rezound.

Generic IBM laser mouse = fail.

Powered USB hub = fail

Simple USB flash drive formatted to FAT 32 = fail

USB Y cable to provide external power = fail

I guess I will have to stick with my bluetooth mouse to look cool.
[HTC Rezound] Neo:
I will make a cable myself and test. Rezound charger male and USB extension female.
[HTC Rezound] GrayBoltWolf:
According to this it is possible:

http://usbhost.chainfire.eu/?search=vigor
[HTC Rezound] dlumberg:
It should just work, once you get the power situation figured out. Once the android USB gadget stuff is enabled and working in the kernel the rest of the stuff is just mainline kernel... At least from what I've seen with my Asus transformer (which has a built in USB hub in the dock).

I still can't wrap my head around a practical use for hooking a joystick or mouse up to a phone though...
[HTC Rezound] GrayBoltWolf:
I am mostly after flash drive support.
[HTC Rezound] TheBr0ken:
Just flash drive?

Man, I've got a USB steering wheel w/paddle shifter and pedals asking for some need for speed action on the Rezound. ;)
[HTC Rezound] GrayBoltWolf:
Play 30 seconds of that and watch the Rezound burn a hole in the table.
[HTC Rezound] TheBr0ken:
It may burn a hole in the table and light up, but it will be an oh so glorious ball of flames!
[HTC Rezound] Flyhalf205:
[MENTION=4803670]iHateWebOS[/MENTION] [MENTION=3419683]Snuzzo[/MENTION]

What is your opinion on this? https://github.com/Flyhalf205/vigor_aosp_kernel/commit/a92df1466fa5fb7ef9b0e85e8fcd0c73c771f832. It is running very nicely. Got rid of the graphic glitches/flickers.
[HTC Rezound] Snuzzo:
http://xdaforums.com/showpost.php?p=43942950&postcount=2494

For those interested in yet another kernel choice.

Works great. I will add it in later.
[HTC Rezound] kkozma:
Figured I'd move the discussion about 4.3 over to this thread rather than the CM10.1 thread.

I've hit a brick wall. Don't even have the foggiest of where to look on this one. Usually all the other errors you get have a bit more of a description other than, "Sorry".

hardware/qcom/display-legacy/libgralloc/gralloc.cpp:94:1: sorry, unimplemented: non-trivial designated initializers not supported
make: *** [/home/vwmofo/android/MofoROM-4.3/out/target/product/vigor/obj/SHARED_LIBRARIES/gralloc.msm8660_intermediates/gralloc.o] Error 1
make: *** Waiting for unfinished jobs....

Not quite sure I understand why this one isn't working. This particular code hasn't been modifed from CM10.1 and I built that just fine yesterday. idk.
[HTC Rezound] Flyhalf205:
Well in other news not related to 4.3. BT Tether is working now.

[MENTION=2658396]kkozma[/MENTION] I did get that error but somehow got past it. I'm not dealing with display-legacy errors.

hardware/qcom/display-legacy/libgralloc/pmemalloc.cpp: In function 'int mapSubRegion(int, int, size_t)':

hardware/qcom/display-legacy/libgralloc/pmemalloc.cpp:73:26: error: expected initializer before 'sub'

hardware/qcom/display-legacy/libgralloc/pmemalloc.cpp:74:30: error: 'sub' was not declared in this scope

hardware/qcom/display-legacy/libgralloc/pmemalloc.cpp: In function 'int unmapSubRegion(int, int, size_t)':

hardware/qcom/display-legacy/libgralloc/pmemalloc.cpp:80:26: error: expected initializer before 'sub'

hardware/qcom/display-legacy/libgralloc/pmemalloc.cpp:81:32: error: 'sub' was not declared in this scope

make: *** [/home/david/android/cm-10.1/out/target/product/vigor/obj/SHARED_LIBRARIES/libmemalloc_intermediates/pmemalloc.o] Error 1

make: *** Waiting for unfinished jobs....​
[HTC Rezound] kkozma:
I ran into that one too and I think I got passed it but then ran into my above issue.

Try this and see if it gets passed it.

static int mapSubRegion(int fd, int offset, size_t size) {
struct pmem_region sub = { (unsigned long)offset, size };
if (ioctl(fd, PMEM_MAP, &sub))
return -errno;
return 0;
}

static int unmapSubRegion(int fd, int offset, size_t size) {
struct pmem_region sub = { (unsigned long)offset, size };
if (ioctl(fd, PMEM_UNMAP, &sub))
return -errno;
return 0;
}
[HTC Rezound] Flyhalf205:
[MENTION=2658396]kkozma[/MENTION] I really don't understand libgralloc/gralloc.cpp:94:1 error

target SharedLib: local_time.default (/home/david/android/cm-10.1/out/target/product/vigor/obj/SHARED_LIBRARIES/local_time.default_intermediates/LINKED/local_time.default.so)

hardware/qcom/display-legacy/libgralloc/gralloc.cpp:94:1: sorry, unimplemented: non-trivial designated initializers not supported

make: *** [/home/david/android/cm-10.1/out/target/product/vigor/obj/SHARED_LIBRARIES/gralloc.msm8660_intermediates/gralloc.o] Error 1

make: *** Waiting for unfinished jobs....

target SharedLib: power.default (/home/david/android/cm-10.1/out/target/product/vigor/obj/SHARED_LIBRARIES/power.default_intermediates/LINKED/power.default.so)

hardware/qcom/display-legacy/libhwcomposer/hwc_mdpcomp.cpp: In static member function 'static bool qhwc::MDPComp::isDoable(hwc_context_t*, hwc_display_contents_1_t*)':

hardware/qcom/display-legacy/libhwcomposer/hwc_mdpcomp.cpp:264:53: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]

cc1plus: all warnings being treated as errors​

---------- Post added at 07:52 PM ---------- Previous post was at 07:07 PM ----------

[MENTION=2658396]kkozma[/MENTION]

Enjoy :) https://github.com/Flyhalf205/andro...mmit/8a20462547e83d602f4fbe3fead7581fa289445a

Now off to fix audio_policy :(
[HTC Rezound] kkozma:
Kickass! Thanks!

I'm not super good at this stuff, but if you compare audiopolicymanagerbase.cpp (hardware/libhardware_legacy/include/hardware_legacy) from 4.3 with 4.2.2 I'm pretty sure there's some clues in there as to how the functions are declared etc etc.

Now I'm getting a build error for tonegenerator.cpp

frameworks/av/media/libmedia/ToneGenerator.cpp: In member function 'bool android::ToneGenerator::initAudioTrack()':

frameworks/av/media/libmedia/ToneGenerator.cpp:1073:24: error: 'AUDIO_STREAM_INCALL_MUSIC' was not declared in this scope

frameworks/av/media/libmedia/ToneGenerator.cpp:1074:67: error: 'AUDIO_OUTPUT_FLAG_INCALL_MUSIC' was not declared in this scope
[HTC Rezound] Flyhalf205:
Got mine to build. No boot. Sad day.

Might know why
[HTC Rezound] kkozma:
They really broke something with that last merge of frameworks/av

I'm about to call it for the night. :(
[HTC Rezound] Flyhalf205:
I'm just satisfied that we got the device and display/media legacy gits building with no problem. Up to CM to get their end working.
[HTC Rezound] kkozma:
Yep, I suppose that's not bad for a day's work.
[HTC Rezound] bassmadrigal:
I came across this post while searching that error while trying to compile 10.2 for the Nexus 4 (mako). It seems that for my build, QCOM_HARDWARE isn't defined anywhere. I'm no programmer, and I'm not sure the proper way to fix it, but I just threw a #define QCOM_HARDWARE at the top of all the headers that had an ifdef for it. It is late and I need to go to bed, so I'm not sure if it will finish compiling, but this may help you as well.

The files that were found containing the ifdef after doing a recursive grep were:

system/core/include/system/audio.h

system/core/include/system/audio_policy.h

system/core/include/system/camera.h

hardware/libhardware/include/hardware/gralloc.h

hardware/libhardware/include/hardware/hardware.h

hardware/libhardware/include/hardware/hwcomposer_defs.h

hardware/libhardware/include/hardware/audio.h

hardware/libhardware_legacy/include/hardware_legacy/AudioHardwareInterface.h

hardware/libhardware_legacy/include/hardware_legacy/AudioSystemLegacy.h

hardware/libhardware_legacy/include/hardware_legacy/AudioPolicyManagerBase.h

frameworks/av/include/camera/CameraParameters.h

frameworks/av/include/media/stagefright/OMXCodec.h

frameworks/av/include/media/mediarecorder.h

I'm sure there is an easier way than manually modifying all these files to include the define, but I just don't know how or where to do it.

Hope this helps :)
[HTC Rezound] Flyhalf205:
Funny. I never ran into the issues above.. The skyrocket which is a samsung msm8660 device got theirs to boot. I wonder what we are doing wrong.