sk story :)

The Froyo Code Drop

() — Thu, 01 Jul 2010 21:53:23 +0900

우리 회사에 근무할때 얼굴 한번 보지 못했던 JBQ...지금은 구글에서 Android 코드 관리의 총책임자 로 일하고 있다.
지금도 브라우저 소스에서 JBQ의 흔적을 볼때 마다 참 대단한 개발자라는 생각이든다.

지난주 Android 2.2 code name Froyo의 소스 코드가 JBQ에 의해 master branch에 merge되었다.
소스 싱크를 하여 full build를 해보니 소스 컴파일 시간은 기존과 큰차이가 없는것 같다.
이제 남은건 단말에 올려 GIT의 속도감을 느껴 보는일만 남은것 같다.

지난주 JBQ가 프로요 코드를 릴리즈 하며 구글 개발자 블로그에 올린 글이 인상 깊어 남겨본다.

원문출처: http://android-developers.blogspot.com/ ··· rop.html

Posted by Tim Bray on at 8:35 AM

[This post is by Jean-Baptiste Queru, who moves truck-loads of source code in and out of the Googleplex. — Tim Bray]

Today is one of those days that has my heart racing; we’ve just released the source code for Android 2.2. This is a big step forward for the entire Android ecosystem. Please don’t melt the servers down again while trying to download that latest source code.

This blog typically talks about developing Android applications using the SDK and NDK. However, the skills of a platform contributor aren’t fundamentally different from those of an application developer. Those are simply different roles using the same skill set. I’m providing an update here to the experienced Android programmers all around the world on some of the recent developments in the Android Open-Source Project.

For Google engineers working on Android, releases are mostly known by their code names which are chosen alphabetically after tasty treats. I’ll call Android 2.2 “Froyo” throughout this post, since that was its code name. Raw version numbers don’t make me salivate as much as the thought of a cold dessert in the California summer.

Let’s have a look at some cool aspects of the new Froyo source, and let’s then take a few steps back to look at other noteworthy aspects of the Android Open-Source Project.

I had been increasingly involved in all previous open-source releases of Android, from testing the initial code drop to doing all the open-source-related git-level work in Eclair. Following that path, Froyo is the first release where my primary focus has been the Android Open-Source Project from start to finish. I thank the entire Android team for helping me all along with much of that work. Here are some aspects of Froyo that I am proud of, and that kept me busy for the last few months:

Hundreds of platform changes that people everywhere uploaded to the Android Open-Source Project were accepted and merged into Froyo. That process is now a well-oiled machine and will translate well to future contributions.
The open-source release happened in a single step. The whole source tree for the entire Android 2.2 platform is now available, with its full change history. That will accelerate everyone’s migration to Froyo from older releases. It is also already fully merged into the open-source master tree. Consequently, we can immediately review and accept platform contributions based on Froyo. That will therefore reduce the risk of merge conflicts between contributions to the open-source tree and changes in Google’s internal master tree where those contributions are meant to end up.
In order to make it easier for device manufacturers and custom system builders to use Froyo, we’ve restructured our source tree to better separate closed-source modules from open-source ones. We’ve made many changes to the open-source code itself to remove unintentional dependencies on closed-source software. We’ve also incorporated into the core platform all the configuration files necessary to build the source code of Android Open-Source Project on its own. You can now build and boot a fully open-source system image out of the box, for the emulator, as well as for Dream (ADP1), Sapphire (ADP2), and Passion (Nexus One).
Speaking of device support, we also open-sourced several additional hardware-related libraries that had been closed-source in previous releases, which will open the door to more contributions. Some examples are the recovery UI code for Dream, Sapphire and Passion, and the interface between the media framework and Qualcomm chipsets.

Besides the Froyo source code release, I wanted to mention several other improvements in the Android Open-Source Project:

We’ve been receiving contributions from more than twenty different companies, and many individuals. We have close to 4,000 registered users on theGerrit code review server, with an average of 2 contributions per user. Those contributions have been in all areas of the system, from the depth of the C library all the way to the UI of the lock screen. They’ve covered the full range of complexities, from fixing typos in the documentation or reformatting code to adding developer-visible APIs or user-visible features. I want to thank everyone who got involved for their work and patience.
We’re now responding to platform contributions faster, with most changes currently getting looked at within a few business days of being uploaded, and few changes staying inactive for more than a few weeks at a time. We’re trying to review early and review often. As I’m typing this, only about a dozen platform contributions haven’t been looked at yet, with the oldest of those being 3 days old. More than 90% of contributions to the platform code itself have been actively looked at during the last 2 weeks. I hope that the speedy process will lead to more interactivity during the code reviews. I realize nevertheless that time differences around the world can make real-time communication a challenge.
Over the last 2 months, we’ve reached a final decision on more than 1,000 changes that were uploaded to our public Gerrit server. That means that those changes were either accepted or rejected after being reviewed. The high quality of the contributions we’ve been receiving throughout the history of the Android Open-Source Project has allowed us to steadily merge about 80% of them into the main repository, from where they migrate to official releases. That means that an average of 20 changes have been accepted through the Android Open-Source Project into the public git repositories every business day over those last 2 months.
We recently created two new official Google Groups related to the Android Open-Source Project. Android-building is meant to specifically discuss build issues (be sure to search the archives thoroughly before posting). Android-contrib is used to discuss actual contributions (don’t post if you don’t really intend to contribute and follow through on the review process, and if you haven’t already spent an hour or two researching things on your own).
We’re developing the developer tools directly in the open-source project, with no work in those areas happening behind closed doors. This covers the Eclipse plug-in and the emulator, and more than a dozen other SDK-related tools.
Once a platform version is open-sourced, all improvements to the Compatibility Test Suite related to that version are made directly to the open-source tree. In fact, release 2 of the 2.1 CTS was done 100% that way, with the development, testing and release process all happening straight in the open-source tree. This is now true for Froyo as well, and we are now accepting contributions into the Froyo branch of the CTS project.

I believe that those last two aspects are important to application developers. If you’re an application developer and you’d like to improve the tools that you and your fellow developers use, the process to make changes in that area is now a lot more transparent. Similarly, if during application development you find incompatibilities between devices and believe that those incompatibilities aren’t within the letter or the spirit of Android compatibility, you can help improve the situation by contributing a CTS test for that area.

With Android 2.2 now being available to the open-source world, and with the review process working smoothly, I’m looking forward to seeing a lot more high-quality contributions that will be used to build future versions of Android. My sweetest dream, which is also my worst nightmare, is to have so many contributions that I can’t keep up with them. Please don’t wake me up.

iPhone 4 - This changes everything. Again.

() — Tue, 08 Jun 2010 10:21:55 +0900

어제 새벽 WWDC 2010 행사에서 iPhone 4가 발표 되었다. 획기적인 혁신은 없었지만 기존의 틀에서 많은 기능들이 업그레이드 되었다. 이번에 발표된 iPhone 4 주요 기능은 다음과 같다.

- 9.3 mm 의 얇아진 두께와 스테인리스 스틸 재질의 바디
- 1GHz 의 A4 칩셋 탑재
- 3.5인치 스크린의 960x640 의 해상도
- 배터리 사용시간 증가 (대기시간 300시간, 7시간 연속통화, 동영상 및 음악 10시간 연속재생)
- 자이로스코프 센서 탑재로 6축 방향 감지
- 500만 화소 카메라와 조광센서 및 LED 플래시 탑재
- 영상통화 및 화상 채팅을 위한 전면 카메라 탑재
- HD 영상 촬영 가능 (720 픽셀으로 초당 30 프레임 촬영)
- iMovie 소프트웨어 탑재로 세밀한 영상 편집 가능
- iOS 4

어제 발표에 따르면 6월 15일 부터 사전 예약을 받고 24일부터 각국에 순차적으로 판매될 예정이라고 한다. 무엇보다 7월에는 한국 KT사업자를 통해 국내 출시가 확정되었다고 하니 iPhone 3Gs와 같은 기다림의 고통은 없을듯 하다.

좀더 자세한 스팩은 아래와 같다.

iPhone 4 Technical Specifications

Size and weight¹

Height:: 4.5 inches (115.2 mm)
Width:: 2.31 inches (58.6 mm)
Depth:: 0.37 inch (9.3 mm)
Weight:: 4.8 ounces (137 grams)

Cellular and wireless

UMTS/HSDPA/HSUPA (850, 900, 1900, 2100 MHz)
GSM/EDGE (850, 900, 1800, 1900 MHz)
802.11b/g/n Wi-Fi (802.11n 2.4GHz only)
Bluetooth 2.1 + EDR wireless technology

Location

Assisted GPS
Digital compass
Wi-Fi
Cellular

Power and battery²

Built-in rechargeable lithium-ion battery
Charging via USB to computer system or power adapter
Talk time:
Up to 7 hours on 3G
Up to 14 hours on 2G
Standby time: Up to 300 hours
Internet use:
Up to 6 hours on 3G
Up to 10 hours on Wi-Fi
Video playback: Up to 10 hours
Audio playback: Up to 40 hours

Environmental requirements

Operating temperature: 32° to 95° F
(0° to 35° C)
Nonoperating temperature: -4° to 113° F
(-20° to 45° C)
Relative humidity: 5% to 95% noncondensing
Maximum operating altitude: 10,000 feet (3000 m)

Capacity³

16GB or 32GB flash drive

Color

White or black

Display

Retina display
3.5-inch (diagonal) widescreen Multi-Touch display
960-by-640-pixel resolution at 326 ppi
800:1 contrast ratio (typical)
Fingerprint-resistant oleophobic coating on front and back
Support for display of multiple languages and characters simultaneously

Audio playback

Frequency response: 20Hz to 20,000Hz
Audio formats supported: AAC (8 to 320 Kbps), Protected AAC (from iTunes Store), HE-AAC, MP3 (8 to 320 Kbps), MP3 VBR, Audible (formats 2, 3, 4, Audible Enhanced Audio, AAX, and AAX+), Apple Lossless, AIFF, and WAV
User-configurable maximum volume limit

TV and video

Video formats supported: H.264 video up to 720p, 30 frames per second, Main Profile level 3.1 with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; MPEG-4 video, up to 2.5 Mbps, 640 by 480 pixels, 30 frames per second, Simple Profile with AAC-LC audio up to 160 Kbps per channel, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; Motion JPEG (M-JPEG) up to 35 Mbps, 1280 by 720 pixels, 30 frames per second, audio in ulaw, PCM stereo audio in .avi file format
Support for 1024 by 768 pixels with Dock Connector to VGA Adapter; 576p and 480p with Apple Component AV Cable; 576i and 480i with Apple Composite AV Cable (cables sold separately)

Camera, photos, and video

Video recording, HD (720p) up to 30 frames per second with audio
5-megapixel still camera
VGA-quality photos and video at up to 30 frames per second with the front camera
Tap to focus video or still images
LED flash
Photo and video geotagging

External buttons and controls

Sensors

Three-axis gyro
Accelerometer
Proximity sensor
Ambient light sensor

Connectors and input/output

Google Go - Python with C++

() — Sun, 15 Nov 2009 19:29:47 +0900

구글의 새로운 프래그래밍 언어 "Go"

Motorola Droid (Verizon Wireless)

() — Sat, 31 Oct 2009 16:58:13 +0900

cnet에서 리뷰한 버라이존 사업자의 Motorola Droid 폰이다.
Android 2.0 Eclair가 올라간 단말로서 모토롤라에서 총력을 기울여 개발하였다고 한다.
개인적으로 드로이드 폰의 메인 테마로 잡은 SNS서비스가 시장에서 얼마 만큼의 관심을 보일지가 궁금하다.

아래 동영상은 모토롤라 드로이드에 올라간 어플중 구글 맵을 이용한 네이게이션 서비스이다.

Introduction to LG GW620 Eve

() — Sat, 31 Oct 2009 16:43:30 +0900

LG의 첫번째 안드로이드 폰이 출시를 앞두고 광고를 하기 시작 하였다.
광고를 통해 내용을 살펴보자

Android SDK 2.0 Eclair

() — Thu, 29 Oct 2009 12:52:33 +0900

안드로이드 SDK 2.0 Eclair(이클레어)버전이 릴리즈 되었다.

아쉽게도 아직 SDK 2.0 source code가 공개되지 않아 내용을 정확히 파악 할 수 없으나

Android repository의 new branch에 Eclair가 생성되어 있는것으로 보아 빠른 시일내에 공개될 것이라 생각된다.

Android 2.0에서 변경된 내용은 아래 동영상을 통해 확인해 보기 바란다.

Android SDK 2.0 실행하기

1. http://developer.android.com/sdk/index.html 에서 윈도우 버전의 android-sdk_r3-windows.zip 파일을 다운로드 받는다.

2. 다운로드한 압축 파일을 풀어 "SDK Setup.exe" 파일을 실행시킨다.

3. Android SDK and AVD Manager가 나타나는데 자신이 필요한 SDK 버전을 Install한다.

4. 일단 SDK 2.0만 필요하니 SDK Platform Android 2.0, API5, revisioin 1 을 선택하여 Install

5. platforms 폴더에 보면 android-2.0 폴더가 생성된것을 볼 수 있다.

6. tools 폴더로 이동하여 Android Virtual Device를 생성한다. "android create avd -n my_anroid -t 2"

7. "emulator -avd my_anroid" 명령어를 실행하면 아래와 같은 화면을 볼 수 있다.

Android SD Card Emulation

() — Tue, 20 Oct 2009 11:28:43 +0900

Android Emulator를 실행한 후 SD Card에 adb를 이용하여 file push 할때 "read-only file system" 에러 메세지가 나타난다면 "/build/core/main.mk" 파일의 내용을 확인해야 한다. 해당 make파일에 버그가 존재하기 때문이다.

- There is a packaging bug that prevents the mount daemon from properly.
- 자세한 내용은 아래 구글 코드 변경 내역을 참조하기 바란다.
- https://review.source.android.com/#change,9452

참고로 아래 내용은 리눅스 환경에서 작업하였다.

1. https://review.source.android.com/#patch,sidebyside,9452,1,core/main.mk 사이트 참고하여 아래 내용을 main.mk 파일에 추가

# Install a vold.conf file is one's not already being installed.
ifeq (,$(filter %:system/etc/vold.conf, $(PRODUCT_COPY_FILES)))
PRODUCT_COPY_FILES += \
development/data/etc/vold.conf:system/etc/vold.conf
ifeq ($(filter eng tests,$(TARGET_BUILD_VARIANT)),)
$(warning implicitly installing vold.conf)
endif
endif

2. Build
/home/user/android1.6_SDK$ make

3. SD Card Create
/home/user/android1.6_SDK$ mksdcard 32M sdcard.img

4. Emulator launch with SD Card
/home/user/android1.6_SDK$ emulator -sdcard sdcard.img

5. SD Card Data Write
/home/user/android1.6_SDK$ adb push test.txt /sdcard

아이폰 국내 1호 사용자

() — Mon, 28 Sep 2009 00:04:38 +0900

아이폰 1호 사용자가 블로그에 올려놓은 글을 읽어 보면 개인적으로 정말 많은 고생과 노력이 있었던것 같다.
아이폰을 이베이에서 구입하여 전파연구소의 개인인증과 KT 개통까지 정말 쉽지 않은 일이었던것은 분명하다.
어떤 사람은 계란으로 바위를 깨뜨린것과 같아 속이 시원하다고 한다.

아이폰을 향한 열정에 큰 박수를 보내고 싶다.

Twitter
mcseoung

블로그

아이폰은 우리 모두의 현실이다. 1부

아이폰은 우리 모두의 현실이다. 2부

[뉴스 스크랩] 아이폰 국내 첫 개통

() — Sun, 27 Sep 2009 23:56:03 +0900

2009년 9월 25일 드디어 한국에 아이폰 1호 사용자가 나왔다.
정식으로 국내 출시된 아이폰은 아니지만 국내 첫 정식 사용자라는것에 큰 의미가 있는것 같다.

연합뉴스

파이낸셜뉴스

YF 쏘나타 신차 전시회

() — Fri, 18 Sep 2009 19:19:00 +0900

코엑스에서 YF 쏘나타 신차 전시회가 있어 다녀왔다.
새로나온 모델이라 그런지 맘에 든다.
사진으로만 보다 직접 보니 지르고 싶은 충동이 밀려온다...