Hi,
I have android running on beagle.
I have usb webcam Logitect QuickCam Express connected to beagle board.
The v4l2 driver recognizes the camera.
Using v4l-info i can query the video device.
Now, from android, if i run Camera.apk, only black and white checked screens
(as like in emulator)
It seems that the kernel that comes with the eee_701 port is based on
2.6.25 while
the sources are based on 2.6.27.
I also noticed that the kernel.config in vendor/asus/eee_701 is not
exactly
the config file used when building the 2.6.25, for example the i915
and drm driver
aren't enabled there.
It would be nice if you could tell us exactly what you're trying to build,
and how you did setup the build.
On Tue, Mar 24, 2009 at 5:40 AM, Andy Quan androidr...@gmail.com wrote:
Hi,
Anybody understands what the following error message means? I got these
errors during system image building.
Hi All,
When I am compiling the latest android from main branch the ApiDemos.apk
is not getting generated in myandroid\out\target\product\generic\data\app
while in my previous setup this was getting generated.
Do I need to enable somewhere to include this application?
Regards,
Manish
hi all, I got 5 files from
http://sites.google.com/site/androidgroupkorea/download-1
: s3c6410-android.1.a**(00 - 04) at S3C6410(arm1176core) ( if they
are in alz format, a *.alz file is necessary ). But I dont know how to
join or extract them, please tell me.Thanks you very much.
I am developing a board using DM6467 and aiming to port Linux using
NFS on the same. I have seen some boards like EVM6467 which are having
Linux Booting Facility though NFS.
While implementing this I have some basic doubts.
1. When I say DM6467 will boot in Linux via NFS there has to be a boot
Hi All,
I'm trying to port dalvik VM onto PPC.
I could able to build 'dalvikvm' binary and the respective 'jar' files
that are needed for the execution of 'dalvikvm'('core.jar' ,
'ext.jar','framework.jar',android.policy.jar' and 'services.jar')
To test dalvikvm i followed the following steps:-
Jean-Baptiste Queru wrote:
[still bcc android-platform, android-framework, android-porting]
We're now one step closer. Change 9356 was submitted, so that the
source tree as is can be compiled.
You still need to set BUILD_WITHOUT_PV=true.
JBQ
On Sat, Mar 21, 2009 at 10:35 PM,
we supply apparels,shoes,handbags,sunglasses,wigs,bikinis.
if you need to place an order.
i will quote the best price for you.
please kindly visite our website: http://www.nikestore88.com
msn: nikestore2...@hotmail.com
email: nikestore2...@gmail.com
I have a lot of questions about alsa, here i go..
I am trying to use alsa api in a native C application to play some
sound on the HTC Dream. If i cross-compile the application for ARM
with the tools provided in the sdk and with the include files from
WindRiver's alsa-lib, and then link it with
On 3月21日, 上午10时25分, Jean-Baptiste Queru j...@android.com wrote:
From our internal revision control system:
---8---
Remove support for System V IPCs in our C library.
This is done to avoid potential nasty denial of service that may
require rebooting the phone. For more details, see the new
Hi,
I am 95% sure that the answer to all your questions below is no.
adumitru007 wrote:
I have a lot of questions about alsa, here i go..
I am trying to use alsa api in a native C application to play some
sound on the HTC Dream. If i cross-compile the application for ARM
with the tools
archerypp wrote:
I have updated my Android to the latest one using 'repo sync'.
That was a mistake. The main Android repo is currently broken. ALSA will
not be updated until main can be compiled without ALSA.
But I met this error while compiling it.
The log is :
target arm C++:
13 matches
Mail list logo
