5,604,050 Members 48,145 Now Online
XDA Developers Android and Mobile Development Forum

Media-Caf Error

Tip us?
 
matrixzone
Old
#1  
matrixzone's Avatar
Senior Member - OP
Thanks Meter 607
Posts: 2,002
Join Date: Mar 2012
Default Media-Caf Error

So now I am getting the below error while compiling Omni ROM:
hardware/qcom/media-caf/mm-video/vidc/venc/src/video_encoder_device.cpp:2450:17: error: 'struct venc_entropycfg' has no member named 'longentropysel'

Full Log:
http://hastebin.com/kudarekaqo.vhdl

Please help me in killing this last error
If this is helpful or useful, please hit "Thanks" and its free
 
tilal6991
Old
#2  
Recognized Developer
Thanks Meter 2444
Posts: 1,550
Join Date: Dec 2010
https://gerrit.omnirom.org/#/c/2940/

You need the equivalent of this patch for your kernel.
Please don't send me PMs asking for help about any of my ROMs. I will not respond. I am much more interested in helping people posting in the relevant thread. Also don't PM or ask about ETAs for any of my ROMs - I don't have any.

HoloIRC - a lightweight, easy to use IRC app for Android - http://forum.xda-developers.com/show....php?t=2306025
Follow me on Twitter: https://twitter.com/tilal6991 or on G+: https://plus.google.com/u/0/110275089424166293093
My current device(s): Sony Xperia T
My retired device(s): Huawei Ideos (U8150-D), ZTE Skate
 
matrixzone
Old
#3  
matrixzone's Avatar
Senior Member - OP
Thanks Meter 607
Posts: 2,002
Join Date: Mar 2012
Quote:
Originally Posted by tilal6991 View Post
https://gerrit.omnirom.org/#/c/2940/

You need the equivalent of this patch for your kernel.
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3
If this is helpful or useful, please hit "Thanks" and its free
 
tilal6991
Old
#4  
Recognized Developer
Thanks Meter 2444
Posts: 1,550
Join Date: Dec 2010
Quote:
Originally Posted by matrixzone View Post
The commit you shared seems to be related to Sony. I am building for AT&T Samsung Galaxy S3. So will that be applicable, if yes how to integrate the same into my setup considering Omni does not support AT&T S3
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.
Please don't send me PMs asking for help about any of my ROMs. I will not respond. I am much more interested in helping people posting in the relevant thread. Also don't PM or ask about ETAs for any of my ROMs - I don't have any.

HoloIRC - a lightweight, easy to use IRC app for Android - http://forum.xda-developers.com/show....php?t=2306025
Follow me on Twitter: https://twitter.com/tilal6991 or on G+: https://plus.google.com/u/0/110275089424166293093
My current device(s): Sony Xperia T
My retired device(s): Huawei Ideos (U8150-D), ZTE Skate
 
matrixzone
Old
#5  
matrixzone's Avatar
Senior Member - OP
Thanks Meter 607
Posts: 2,002
Join Date: Mar 2012
Quote:
Originally Posted by tilal6991 View Post
That's why I said equivalent of that commit. If you make the same changes as was made in that change the error should be fixed.
thanks man. How to see the code change from gerrit, checking the code change in github is very easy
If this is helpful or useful, please hit "Thanks" and its free
 
chasmodo
Old
#6  
chasmodo's Avatar
Senior Member
Thanks Meter 37772
Posts: 11,618
Join Date: Dec 2011
Location: Novi Sad

 
DONATE TO ME
Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.
 
Entropy512
Old
#7  
Senior Recognized Developer
Thanks Meter 23431
Posts: 12,789
Join Date: Aug 2007
Location: Owego, NY

 
DONATE TO ME
Quote:
Originally Posted by chasmodo View Post
Go to Omni github, find android_kernel_sony_msm8960 project, switch to android-4.4 branch, click on commits and scroll down until you find Nov 29.
In this particular case - look at the files changed by the commit and pull up the commit history for one of them - saves a lot of time.
*so much sig updating needed*

My Github profile - Some Android stuff, some AVR stuff

An excellent post on "noobs vs. developers"

A few opinions on kernel development "good practices"

Note: I have chosen not to use XDA's "friends" feature - I will reject all incoming "friend" requests.

Code:
<MikeyMike01> Smali is a spawn of hell
<shoman94> ^^^ +!
Code:
<Entropy512> gotta be careful not to step on each other's work.  :)
<Bumble-Bee> thats true
<jerdog> compeete for donations
 
Entropy512
Old
#8  
Senior Recognized Developer
Thanks Meter 23431
Posts: 12,789
Join Date: Aug 2007
Location: Owego, NY

 
DONATE TO ME
Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.

We should have just fixed the remaining broken devices two weeks ago, oh well.

As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.
*so much sig updating needed*

My Github profile - Some Android stuff, some AVR stuff

An excellent post on "noobs vs. developers"

A few opinions on kernel development "good practices"

Note: I have chosen not to use XDA's "friends" feature - I will reject all incoming "friend" requests.

Code:
<MikeyMike01> Smali is a spawn of hell
<shoman94> ^^^ +!
Code:
<Entropy512> gotta be careful not to step on each other's work.  :)
<Bumble-Bee> thats true
<jerdog> compeete for donations
 
mithun46
Old
(Last edited by mithun46; 17th December 2013 at 01:29 PM.)
#9  
mithun46's Avatar
Recognized Contributor
Thanks Meter 1633
Posts: 1,230
Join Date: Oct 2012
Location: ▒▅|▆|█|▆|▅▒

 
DONATE TO ME
Quote:
Originally Posted by Entropy512 View Post
Although, to be honest, we need to move to the fixed patch rather than continuing to revert kernels in this case.

We should have just fixed the remaining broken devices two weeks ago, oh well.

As to it appearing to be "sony" specific - keep in mind that many patches are merely "qualcomm specific" and apply to any Qualcomm-based device. This is one of them.
Also qcom devices that has "TARGET_QCOM_MEDIA_VARIANT := caf" in BoardConfig
I said that cause there are qcom devices that can work with no caf repos tbh..

An example would be Sony fusion3 devices.....
They worked on our android-4.4 branches perfectly fine prior to the qcom-4.4_2.7 merge
And fusion3 OmniROM/CyanogenMod Nightlies don't use any of the caf repos tbh . Though AOKP does
If you consider my efforts worthwhile then Donate or Thank me

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes