To test the integrated codec

by Yogi » Tue, 09 Dec 2008 05:04:47 GMT

Sponsored Links
 Hi All,

I have integrated WMA codec onto android i.e compiled successfully but
i want to test that integrated codec without parser.

Can I test the integrated codec without building the complete audio
graph or by creating some dummy graph?

If I hard code elementry stream(output of parser) in codec and
forcefully try to execute WMA code, will it work?

Thanks in advance,
unsubscribe: [EMAIL PROTECTED]

To test the integrated codec

by freepine » Tue, 09 Dec 2008 12:14:31 GMT

 If you want to do integration test within PV framework, I think it's
necessary to integrate WMA file format parser node at the same time.

unsubscribe: [EMAIL PROTECTED]

Sponsored Links

To test the integrated codec

by Dave Sparks » Tue, 09 Dec 2008 16:24:06 GMT

 You could hack up a parser that takes a stream of raw WMA frames. I'd
probably start from the WAVE file parser.

unsubscribe: [EMAIL PROTECTED]

To test the integrated codec

by Yogi » Wed, 10 Dec 2008 03:59:40 GMT

 I have seen some test unit in android.
Can I used any of that to test codec only(without parser)?

unsubscribe: [EMAIL PROTECTED]

To test the integrated codec

by Dave Sparks » Wed, 10 Dec 2008 04:14:00 GMT

 I'm not aware of a unit test that tests just the decoder node. Maybe
someone from PV can enlighten us.

unsubscribe: [EMAIL PROTECTED]

Other Threads

1. Java N00b Test Question

Hi there,

I am brand new to both Java and Android, but I'm really interested in
Android development. Anyway, I'm trying to get going with TDD for the
platform. I found this in the API samples:

public class AllTests extends TestSuite {

    public static Test suite() {
        return new TestSuiteBuilder(AllTests.class)

I believe it's supposed to allow me to run all my tests, however, I
have a separate test file, and it's not being called or run when I run
the tests in Eclipse. Do I have to set up further config to have the
project find all my test files?

Thanks in advance.


2. Protecting /system/app packages from extraction


Is there any way for an OEM to give the same level of protection to
packages loaded into /system/app as is given to 'forward locked'
downloaded packages (which are placed in /data/app-private without
world read permission)?

I understand that the packages in /system/app should have had dexopt
run, so the APKs do not contain classes.dex, and there is a
separate .odex file alongside.  However, for a package that does not
require any 'signature' or 'signatureOrSystem' permissions, it seems
possible to extract the APK and odex, and create a new self-signed
package.  This would appear to need an 'undexopt' step, to get
classes.dex back from the .odex file - and, while I can't see any
tools available that would do this at the moment, it doesn't seem

Is there any particular reason why the files in /system/app are world-
readable?  Could a permission scheme like that used in /data/app-
private be used, uid=system, gid=app_XX, mode=0640?  I guess one issue
would be determining the correct gid.  Any other issues with doing


3. Jdbc driver problem

4. In Java application, how to load native library which depends on the third shared library

5. Needed reference to source code for adb shell command "input" that is used to inject keypresses.

6. display unnormal

7. What is the approx time taken to register as a developer and to be able to publish apps on the Android Market?