OOT : C3

by Justinus » Fri, 04 Jun 2010 14:41:33 GMT


Sponsored Links
 Besok ada yg mau ke PS pagi2 ?

G mau ke sono........antri sembako......eh salah C3 :P

--
Jus* 
|| cupcake,donut,eclair or froyo sama2 enak and its android-google ||

~  http://jus2005.multiply.com  ~



--
"



OOT : C3

by Jefri P » Fri, 04 Jun 2010 14:43:04 GMT


 c3 apa tuh?







-- 
Jefri Priambodo

-- 
"


Sponsored Links


OOT : C3

by Lutfi Hidayat Ramdhani » Fri, 04 Jun 2010 14:43:45 GMT


 Katanya murah yah, brapa sih?

@lutfihidayatr
~ google innovation always surprise me ~




Besok ada yg mau ke PS pagi2 ?

G mau ke sono........antri sembako......eh salah C3 :P

-- 
Jus* || cupcake,donut,eclair or froyo sama2 enak and its android-google ||
~  http://jus2005.multiply.com  ~



-- 
"

-- 
"



OOT : C3

by Justinus » Fri, 04 Jun 2010 14:48:11 GMT


 duh si Jef kemana aja ya.......... punya google phone juga 
dikau........wehehehehe


Nokia C3 kaya E63 gitu, QWERTY.........tp murah Rp 1.150rb-an hrg resmi, 
nah besok tuh 1 hari hrg di bawah itu...gak tau berapa ,bisa 1 jt, bisa 
800rb or bahkan cuma 750rb


Mau?

Jus* 
|| cupcake,donut,eclair or froyo sama2 enak and its android-google ||

~  http://jus2005.multiply.com  ~







c3 apa tuh? On Fri, Jun 4, 2010 at 1:41 PM, Justinus <jusdroi...@gmail.com Besok ada yg mau ke PS pagi2 ? G mau ke sono........antri sembako......eh salah C3 :P -- Jus* || cupcake,donut,eclair or froyo sama2 enak and its android-google || ~ http://jus2005.multiply.com ~ -- " -- Jefri Priambodo -- "
-- "



Other Threads

1. About camera pixel format, how to get a color preview with YUV420sp and recording issue

Hi,
I have a question about using the camera service. Here are something I
observed from different discussions as well as my own tests on a real
development board with Froyo.

1. The default pixel format for camera preview is YUV420SP.
2. To show a camera preview, the camera view surface at the app level
is normally set to PUSHED type and the surface holder is sent to
camera service so the preview is actually managed automatically by the
framework.
3. As an alternative to #2, application can accept camera data from a
camera preview callback and build its own UI display from the data
with further processing.

I found some discussions for bar code scanner type of applications.
YUV420SP is good in that only luminance information is important for
image analyzing and the data is upfront in the returned byte stream.

My question is, how the preview in the standard Android Camera app
worked with color. If the Camera HAL layer only returns with YUV420SP
format, the OpenGL processing in surface layer can only display Y
plane and there will be no color preview. Running the standard Camera
app with the fake camera source in the Android code tree shows a gray-
scale picture in the preview window although from the source code it
does have color content.

The camera API does provide a method to set preview format, so I guess
if the app side selects RGB565, a color preview can be seen. But I
don't find any place in the Camera app request this.

There is a third path to show the preview, which is through the
overlay layer and I heard about some devices use that for preview then
it leads to my next question about the media recording.

I believe the video encoders accepts YUV420SP format only. This can be
found from Stagefright recorder's code. The CameraSource::getFormat
set the kKeyColorFormat to OMX_COLOR_FormatYUV420SemiPlanar directly.
I'm not clear about the PVMediaRecorder case but I guess it's the
same. YUV is more accepted for video content. In order to get encoder
work, the data from camera must be in YUV420SP, then how to get the
camera preview work at same time? We should only see a gray-scaled
display for preview, correct? The camera should not provide two data
streams with YUV420SP(for encoding) and RGB565 (for preview surface)
at same time.

I'm wondering how the devices on the market worked this out.

Another similar discussion can be found here:

2. Android 2.3 Native Audio Support (porting custom vocoder)

I'm new to Android development, so please forgive me if this has
already been address somewhere...  Basically, I'd like to be able to
port a C-based speech vocoder over to the Nexus S (ARM), running
Android 2.3.  Should I be using the NDK to access the C API's?   The
vocoder requires 16-bit PCM frames in S16_LE format.  Furthermore, I'd
like to transport the compressed frames to other phones via wireless
UDP/IP.  Finally, which device should the C-code interface (/dev/dsp, /
dev/audio, etc.) with to be able to capture the raw/WAV PCM frames
(mic) and play decoded/expanded PCM frames (speaker)?
Thanks, Scott

-- 

3. Issue with getExposureCompensation and getExposureCompensationStep

4. sqlite access

5. Not able to connect Samsung Pop(5570) to ubuntu for development

6. Porting valgrind-3.6.0 on Android-2.2.

7. Automatically cycle items in a widget