using stdout library it will maybe pass data to logcat or somewhere else which is not heading toward to display screen.
How can I manage to display what I want using native code with out passing dalvik…T_T
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
using stdout library it will maybe pass data to logcat or somewhere else which is not heading toward to display screen.
How can I manage to display what I want using native code with out passing dalvik…T_T
There may well be no officially supported way to do that. Android is fairly fundamentally based around java code running in the dalvik virtual machine.
It used to be your only option was to use jni between your own native and java code to pass the data through to the java-level Android display APIs.
In more recent versions, it is possible to write a so-called native activity where all of your code is C or C++. However, such an activity still runs in a process built around a dalvik virtual machine running platform-supplied java code, and calling into your code via jni.
There is an embedded Open GL native API which you could use to plot text, but it is quite likely that behind the scenes some jni is still involved, at the very least in the setup of the views.
Both the native activity and native use of open GL have examples in the ndk distribution.
I suppose you could also have you code interact via pipes or sockets with a different process which would display its output, but that’s just moving the use of dalvik elsewhere.