PV omx_test_app missing in Froyo source code

by praji » Thu, 22 Jul 2010 01:08:24 GMT


Sponsored Links
 Hi Guys,

In the froyo source code, the PV omx_test_app & omx_test_app_enc
folders are missing.
path - external/opencore/codecs_V2/omx/
But i can see these folders in the android GIT.

I want to run the PV test application for testing MP4 files.
For that, i compiled the froyo code after adding these folders. The
build was fine.

But when i tried running the test app exe for NORMAL_SEQ_TEST, i was
getting segmentation fault.

syntax -> test_omx_client /data/test.mp4 -o /data/output.yuv -c mpeg4 -
t 11 11

Have any tried running PV omx_test_app on froyo?

Expecting valuable inputs from you guys.

Thanks,
Prajeesh

--



PV omx_test_app missing in Froyo source code

by praji » Thu, 22 Jul 2010 11:48:10 GMT


 Hi Guys,

In the Froyo release code, the PV omx_test_app & omx_test_app_enc
folders are missing.
path - external/opencore/codecs_V2/omx/

But these folders are available in the android GIT.

I wanted to run the decoder test application for MP4.

Since the test app is not available in the source package, i
downloaded the same from GIT and compiled. The build was fine.

But when i run the test application for NORMAL_SEQ_TEST, it was giving
segmentation fault.

syntax -> test_omx_client /data/test.mp4 -o /data/output.yuv -c mpeg4 -
t 11 11

Have anyone tried running the PV omx_test_app in froyo?

Please give your valuable inputs.

Thanks,
Prajeesh

--


Sponsored Links


PV omx_test_app missing in Froyo source code

by praji » Mon, 26 Jul 2010 21:31:30 GMT


 Hi Guys,

I got the problem.
Its a mistake from my side.
I was giving an MP4 container format stream(test.mp4) for the PV OMX
mpeg4 component.

We need to give elementary streams(e.g. test.m4v) for the component
(M4V).

Sorry for the confusions.

Thanks,
Prajeesh




--



Other Threads

1. an android bug?

Hi,
 
Not sure how I got into this state, but none of my events are firing. I
have a bunch of onClickListeners and onFocusChangeListeners and so on,
and none of them are firing. I placed method breakpoints in Eclipse in
all of the event handlers, and none get called. After much poking, I
noticed this in logcat which maybe related:
 
DEBUG/dalvikvm(817): threadid=15: still suspended after undo (s=1 d=1)
DEBUG/dalvikvm(817): threadid=3: still suspended after undo (s=1 d=1)

 
Thread 3 is my main UI thread, and thread 15 is a service thread. What
gives? Anybody seen this before/know how I can get more information as
to what the heck is happening or what I may be screwing up? A threaddump
of the VM may be handy, anyone know how to do that?
 
Also, what's the breakpoint limit? As I placed them in different places
I got an error in LogCat about max breakpoints exceeded...
 
Any and all insights much appreciated. I don't know what else to post in
here to provide information, so if there's anything else i can
provide...
 
Thanks,
Ahmad   

--~--~---------~--~----~------------~-------~--~----~

2. A cheap ($150) android development platform?

euedge reported that "Android should run on any device with an ARMv5TE
CPU + suitable amounts of RAM and Flash. "
http://euedge.com/blog/2007/12/06/google-android-runs-on-sharp-zaurus-sl-c760/

Android wiki reports "the minimum requirements for Android handsets
are 32 MB of RAM, 32 MB of flash memory, and a 200 MHz online
processor." http://androidwiki.com/wiki/Handsets

Zipit Wireless's Z2 messenger fits both requirements:
Main Board Feature       Details
Processor       Marvell XScale PXA270 (FWPXA270C5C312) ARM Processor
running at 312MHz min.
Flash Memory    8MB in single 64Mb (4Mb x 16) FLASH chip
System Memory   32MB SDRAM

(according to wikipedia's xscale site, that processor is an ARMv5TE)

It also costs $150.

I'm no expert, so I'm asking, Can anyone advise if i've just found the
cheapest Android development platform available?
--~--~---------~--~----~------------~-------~--~----~

3. Cannot use Lucene with Android

4. Error in HelloAndroid: Could not find /bin/HelloAndroid.apk!

5. About Ipod as Rival of Android.

6. What about the hardware?

7. Handset ETA