| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
This goes invisible on case-insensitive filesystems, but fails
when XCode is installed on a case-sensitive filesystem.
|
|
|
|
| |
Change-Id: Id2dbb227280f0c0e1b5708ef78b9f19b087f92d5
|
|
|
|
| |
Change-Id: I54897ca86b372d98c7a30a47ecf88a4df8ee0fe9
|
|
|
|
|
|
|
|
|
|
| |
Camera framework requires that certain frame dimensions must be supported by the
camera devices. Since on Windows and Mac we have no way of knowing the real
webcam capabilities, but camera API there pretty much allows us to choose any
frame dimensions that we want, we will hard-code those that are required by
the camera framework.
Change-Id: I625381776f374103d2ac1c62fabae23b1c5afa88
|
|
|
|
| |
Change-Id: I4f238bbd0175036b6003ebdf266de608d6acc6e7
|
|
|
|
|
|
|
| |
In some cases (when frame sizes for pixel formats are not available) the loop will
be not properly bounded, and may cause a crash.
Change-Id: I2f2380ab4e2f7454bff8eeabcaff4e3f238fe71e
|
|
|
|
| |
Change-Id: I7c4830ba7606bedcf462e967adad3358723c44ba
|
|
|
|
| |
Change-Id: I01609e8bfcdd8ee5ef876344d0a334ecd69a2b7a
|
|
|
|
| |
Change-Id: I7387eea3639d63b278b702100ee2d4584f87f4e2
|
|
|
|
|
|
|
| |
Currently camera app will crash on an attempt to switch cameras if camera 0 and 1 are
facing in the same direction. So, user should be warned about that on emulator start.
Change-Id: Ic85da614d30295b04d2a318fb1c2015cc52f1140
|
|
|
|
|
|
|
|
|
|
|
| |
It has been observed on some of the MS camera devices, that device may got stuck on something
that would alwais return EAGAIN when queried for the next video frame. This requires us to
timeout the loop that repeats attempts to acquire first frame from the device. Also added
detection and reporting of I/O errors occurred during frame capturing.
Also, this CL contains some cosmetick changes to error and warning reporting.
Change-Id: I81edaf5ff8bfe147dbe4510e1446e77a87817f37
|
|
|
|
| |
Change-Id: Ia748fe3f38e8366d0507fcee995eac311dd8c72a
|
|
|
|
|
|
|
| |
Reseting capture windows on each "stop capture" + setting capture parameters allow to
change video frame dimensions.
Change-Id: I0ce8ed77dfa9838894acb9e9e84d84692bb3d520
|
|
|
|
|
|
|
| |
Apparently, bitmap obtained through the capXxx + clipboard API is formatted
with BRG, not RGB format.
Change-Id: Ib161be50d2d3258045a467b152a5a750e1a8fb42
|
|
|
|
|
|
| |
Also adds support for YU12 pixel format that is used in video frames
Change-Id: I613beef8b3e2296fd1fab7e2b9d2956fba1ac788
|
|
|
|
| |
Change-Id: I94939964890c4304a47ba86c582baf3a9544b5aa
|
|
|
|
| |
Change-Id: I8d074590bb1efd68789e341e37356bc9fb2c9c08
|
|
|
|
| |
Change-Id: I0acc651be93eb9b5bea49280a7dccd18c1386d48
|
|
|
|
| |
Change-Id: I68abaa8b89e2b46dc57bff1d7dbd6d9fda213dc8
|
|
|
|
|
|
| |
-webcam name=<name>[,dir=<direction>] options controls web cameras to use for emulation.
Change-Id: I961fd399c7e041541adda040dd24f194cc383cb9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current conversion implementation was laking flexibility as far as adding support
for new formats was concerned. In particular, adding support for each new format meant
adding four converter routines: new format <--> RGB, new format <--> YUV. This was not
scalable, so had to be rewritten.
The new conversion implementation consists of four generic converters between different
flavors og RGB/YUV formats, and array of descriptors for each supported format. Each
descriptor contains information that is sufficient for the converter routines to perform
its job. So, adding new format is just creating a new descriptor for that format, and
adding it to the array of supported descriptors.
Change-Id: Ica107d14fa03fa8f41eb9192f2c023a97f54b62c
|
|
|
|
| |
Change-Id: I4bea0f3678b2ac21f3c6cf80581e997145e2a58d
|
|
|
|
|
|
|
|
| |
Apparently, video driver doesn't allow frame size change, once it has been
explicitly set. In order to get around this we need to reset the handle to the
camera device by closing, and then reopening it.
Change-Id: Icfd37b3c196d2643507218b965c5015884ed455b
|
|
|
|
|
|
| |
Remove Windows artifact
Change-Id: I2ffd5979674619786742f14995edbf10edfff23a
|
|
|
|
|
|
| |
Add dummy rutines implementing public camera API on Mac
Change-Id: Id3c9d99d863785b0e00d1bdf6deb0a1af49ce91c
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is fully functional camera service implementation, that works (tested) on both,
Linux and Windows.
Fixed little/big endian bugs in the coverter code. Moved preview frames to use RGB32
instead of RGB565: RGB32 conversions are simpler and faster in the guest.
Made "payload size send" a separate routine
Change-Id: I96954f4c2cb4e4ef4dd6a20e41897d79c5037bae
|
|
|
|
|
|
|
|
|
|
| |
Skeleton that implements camera emulation service over QEMU pipe. More meat
will be added as the guest camera emulation develops.
This is a patch taken from approved AOSP commit that didn't go through
because of a merge conflict.
Change-Id: I6f0a2e42be4f5f0bd86d3dbf0c2a609e74b200c2
|
|
|
|
| |
Change-Id: I87bd356f7673bdbcc8e5f196f4a89182b3a36cbe
|
|
|
|
| |
Change-Id: I801d56668d8591e599994c65fb47b9c3ea77ff73
|
|
|
|
| |
Change-Id: Ia4b6b45ad305307f28858f834f284b07be7d134d
|
|
Contains API that connects to a camera device, and pulls video frames from it
on request from the client.
Change-Id: If1d80c57611afff637a7734ce5c3a2c874cfc85a
|