Camera Emulation on Android

by Thisara Rupasinghe » Thu, 22 Apr 2010 18:17:22 GMT


Sponsored Links
 Hi,

I'm studying emulators code to implement camera on android emulator. As i
get to know, i think i need to implement new HAL implementation for camera
which directs to the actual webcam device. therefore I would like to know
more details and possibility of doing that. in the emulator below the HAL
layer are there the normal driver manager, power manager etc models exists
as physical mobile phone?
I'm going to use GStreamer for that. how should this exactly need to happen?
Any ideas abt that?

-- 
Thanks & Regards,
Thisara.

-- 



Other Threads

1. HTC Magic is HTC Sapphire

Probably Magic is the commercial name of Sapphire, like G1 for Dream.
The shape of Magic you can see at MWC  is a bit different from the
shape of the Vodafone press release.
It has the some shape of the Sapphire prototype of HTC leaked photos.

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

2. Local communication with a service from another APK that runs in the same process

Hello,

In my application I have a need to separate components into two
different APKs.
One component (the first APK) needs to communicate with a service
provided by the other component (the second APK).

I was hoping I could use the shared-user-id mechanism, have both
applications run in the same process and by so avoid AIDL using the
same scheme as presented in the LocalService example in the ApiDemos.
The idea was to declare the following two classesin APK #1:
"LocalService" interface: would represent the service
"LocalServiceBinder": would have a "getService()" method that would
return a "LocalService" object
The two classes would be exported into a JAR and added to APK #2's
build path.

The actual service in the APK #2 would implement "LocalService" and
it's "onBind()" method would return an instance of
"LocalServiceBinder" whereas "getService()" would be overriden to
return a reference to the service itself.

I tried implementing it but failed due to a class-cast exception being
thrown in "onServiceConnected" when attempting to cast the Binder
returned by the Service to LocalServiceBinder. I gave up on the idea
and implemented the communication using AIDL.

As a result my application took quite a performance hit, primarily due
to the "serialization" and "deserialization" of the data being sent to
Service.
So now I'm again trying to implement the "local-communication" scheme.
However, when I tried to reconstruct the aforementioned implementation
the Binder received in "onServiceConnected" is null (even though I'm
definitely not returning null in the service's "onBind" method).

Bottom line is I would like to know if whether I'm attempting to do is
even possible using the Android framework, and if so how to do it. If
not, any suggestions on how to minimize the performance hit.

Thanks in advance!

Best regards,
Uri Kanonov

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

3. File explorer

4. My fix for white on white multi choice items - WTF! My dialog multichoice items have white text on white list background!

5. Is sluggishness the new in thing for UIs...

6. Porting to PPC (MPC7xxx)

7. Any reason for not supporting capital letters in image file names of aapt tool