I also get the same failed error code in prepare. I trace the cause is
in PVMFOMXEncNode::NegotiateAudioComponentParameters(), that output
channels number is be set to 10 in a former calling. But i cannot find
any place where PVMFOMXEncNode::SetOutputNumChannel(10) be called.
Have you fixed the
In Android,
who will decide the threading priority for the OpenMax components
which are not there in the Android frame work and where is this
threading priority set.
Regards,
Varma IVS
--~--~-~--~~~---~--~~
You received this message because you are subscribed to
printing to the console will probably not work unless your code is
running as root. Android provides an easy way of obtaining logs
through logcat. The following are the changes that would be required
to get logs on native code:
(1) Include the header file utils/Log.h
#include utils/Log.h
(2)
Which codebase are you looking at?
-Ravi
On Mar 16, 3:59 am, waterblood guoyin.c...@gmail.com wrote:
I also get the same failed error code in prepare. I trace the cause is
in PVMFOMXEncNode::NegotiateAudioComponentParameters(), that output
channels number is be set to 10 in a former calling.
The OMX components are tied to the OMX core. It is the core
responsibility to either launch a separate thread (and also assign the
thread priority) or run them in the same thread.
For the OpenCORE framework, i.e., the PV OMX core, currently, there is
no way to explicitly mention the thread
Missed the most important part ...
To get the logs, you would need to issue and adb command ... adb
logcat
On Mar 16, 8:37 am, rktb yend...@pv.com wrote:
printing to the console will probably not work unless your code is
running as root. Android provides an easy way of obtaining logs
through
Trying to build cupcake. Synchronized all repositories today. When
building frameworks/base/core/jni/android_emoji_EmojiFactory.cpp it
references a file named EmojiFactory.h which is nowhere to be found.
Looking at the makefile I assume it should have been placed in
frameworks/opt but this
http://android.git.kernel.org/?p=platform/frameworks/opt/emoji.git;a=tree;h=refs/heads/cupcake;hb=cupcake
On Mar 16, 9:20 am, /dev/null mmm...@gmail.com wrote:
Trying to build cupcake. Synchronized all repositories today. When
building frameworks/base/core/jni/android_emoji_EmojiFactory.cpp it
Try to re-sync. There's been a point in time where the emoji code was
missing from the manifest, and you might have done your sync at that
point.
JBQ
On Mon, Mar 16, 2009 at 7:20 AM, /dev/null mmm...@gmail.com wrote:
Trying to build cupcake. Synchronized all repositories today. When
building
Really appreciate your help, Ravi. !!
Thanks a lot
Vincent
On Mon, Mar 16, 2009 at 10:09 PM, rktb yend...@pv.com wrote:
Missed the most important part ...
To get the logs, you would need to issue and adb command ... adb
logcat
On Mar 16, 8:37 am, rktb yend...@pv.com wrote:
printing to
Unless otherwise specified, all binder calls are synchronous to the
calling process (usually referred to as the client process). They are
completely asynchronous to the callee (usually referred to as the
server process).
What this means is that the caller will block in the binder call until
the
Sorry I really don't understand what you are doing.
InputMethodService.onKeyDown() and InputMethodService.onKeyUp() are called
for every single key event being sent to the application, before it does its
normal event dispatching. You don't need to do anything special to see
them.
On Mon, Mar 16,
Hi I just posted this in Android Platforms groups but wasn't sure
where it belonged so posting it here again.
I have this question about the system.img files that come as a part of
the standard android SDK (any release but i run 1.1) and the ones
that are generated by doing a make in the source
Hi
The communication between GSM stack and RIL daemon is done using Local
unix socket instead of Binder ipc.
Why was it done like that?
Are there any exceptions to when one can use Binder based ipc?
Thanks
Videoguy
--~--~-~--~~~---~--~~
You received this message
Thanks Dave.
On Mar 16, 12:04 pm, Dave Sparks davidspa...@android.com wrote:
Unless otherwise specified, all binder calls are synchronous to the
calling process (usually referred to as the client process). They are
completely asynchronous to the callee (usually referred to as the
server
Hi I am trying to simulate a vibrator device in the emulator
The timed_output class driver is in place and is verified to work
( did a echo 1000 to /sys/class/timed_output/vibrator/enable to the
device and it has been verified to work ).
--- I wanted to invoke this device node from a app
2.01 Release
On Mar 16, 9:40 pm, rktb yend...@pv.com wrote:
Which codebase are you looking at?
-Ravi
On Mar 16, 3:59 am, waterblood guoyin.c...@gmail.com wrote:
I also get the same failed error code in prepare. I trace the cause is
in
Basically because that is how it was implemented. *shrug* And it was
written long before there was any Binder IPC facility.
On Mon, Mar 16, 2009 at 1:47 PM, Videoguy puri_mall...@yahoo.com wrote:
Hi
The communication between GSM stack and RIL daemon is done using Local
unix socket instead
Hi,
Can anyone please suggest any tools to check memory leaks in Opencore
source code.
Can we check memory leaks with Valgrind tool?
ThanksRegards,
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
android-framework
19 matches
Mail list logo
