OS: Android - x86 - Revision history

Onnowpurbo: /* Memperoleh source code Android-x86 */

2014-04-07T10:20:55Z

Memperoleh source code Android-x86

Onnowpurbo: /* Testing */

2014-04-01T22:25:04Z

Testing

Onnowpurbo: /* Save data to USB/hard disk */

2014-04-01T12:14:24Z

Save data to USB/hard disk

Onnowpurbo: /* Advanced */

2014-04-01T12:13:39Z

Advanced

Onnowpurbo: /* Build smaller image */

2014-04-01T12:12:35Z

Build smaller image

Onnowpurbo: /* Using lunch command */

2014-04-01T10:34:59Z

Using lunch command

Onnowpurbo: /* Menggunakan buildspec.mk */

2014-04-01T10:13:33Z

Menggunakan buildspec.mk

Onnowpurbo: /* Membuat Android-x86 */

2014-04-01T09:49:23Z

Membuat Android-x86

Onnowpurbo: /* Memilih Target */

2014-04-01T09:45:54Z

Memilih Target

Onnowpurbo: /* Memilih Target */

2014-04-01T09:41:59Z

Memilih Target

@@ Line 33: / Line 33: @@
   sudo apt-get install openjdk-7-jdk
-  $ sudo apt-get install git gnupg flex bison gperf build-essential \
+  sudo apt-get install git gnupg flex bison gperf build-essential \
     zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
     libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
     libgl1-mesa-dev g++-multilib mingw32 tofrodos \
     python-markdown libxml2-utils xsltproc zlib1g-dev:i386
-  $ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
+  sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
 Setelah lingkungan di siapkan, kita dapat melakukan
@@ Line 65: / Line 65: @@
   $ repo init -u git://android-x86.git.sf.net/gitroot/android-x86/x86/platform/manifest.git -b kitkat-x86
 Catatan: SourceForge akan mengacu semua proyek ke mirror SourceForge.net (tidak peduli apakah itu diubah oleh android-x86 atau bukan).

@@ Line 208: / Line 208: @@
 ==Testing==
-The generated image is located at
+Image Android-x86 yang dibuat berada di
-You can easily test the iso file by a virtual box or qemu. On the booting screen, select the VESA or debug mode to boot.
+ out/target/product/$TARGET_PRODUCT/$TARGET_PRODUCT.iso
-Of course you can burn the iso to a CD disk and test it on a real hardware. On booting it will automatically detect your hardware and load necessary modules. If you have problem with the default frame buffer driver, you may try the VESA mode (select second item on boot screen).
+Kita dapat dengan mudah mencoba file iso tersebut dengan menggunakan virtualbox atau qemu.
-Since honeycomb-x86, we supports the hybrid iso format. That is, the iso could be dumped to a usb disk directly. You may create a bootable USB disk by
+Tentu saja, kita selalu dapat burn iso tersebut ke CD dan test ke hardware yang sebetulnya.
-  $ dd if=out/target/product/x86/android_x86.iso of=/dev/sdX
+Sejak honeycomb-x86, Android-x86 mendukung format iso hybrid.
 where /dev/sdX is the device name of your USB disk. This feature is only available for iso files released after 2011/12/25. Note usb_img is deprecated. Do not use it anymore.

@@ Line 284: / Line 284: @@
 We support two ways to save data to your disk.
-    Create a subdirectory named data in your /android directory. The user data will be directly saved to that directory. This method only works for ext3 partition.
+* Create a subdirectory named data in your /android directory. The user data will be directly saved to that directory. This method only works for ext3 partition.
-    Create a separate partition and save data to it. You have to add DATA=<device_name> to the boot option. For example, suppose your data partition is /dev/sda2, then add DATA=sda2 to the boot option.
+==How to solve conflicts==
 There are several reason to have conflicts during repo sync, say
-    You modify your tree locally.
+* You modify your tree locally.
-    The upstream changed. Since we usually keep syncing with original Android repository, sometimes we have to rebase with it. That changes the history and may cause conflicts.
+* The upstream changed. Since we usually keep syncing with original Android repository, sometimes we have to rebase with it. That changes the history and may cause conflicts.
 In this section we assume you have conflicts due to the upstream changed. That is, you don't have local modifications. If you do, you have to solve conflicts yourself. If you follow the procedures in this section, you may lose your local modifications.

@@ Line 236: / Line 236: @@
 Another choice is the Linux Live USB Creator ( LiLi ) project, which officially support Android-x86.
-==Advanced==
+==Advance==
 This section describes some useful information for advanced users. You may need good linux expertise to complete it.
 Install to USB disk
 For advanced linux users, you may create a bootable USB disk by hand. Here are the steps:
@@ Line 269: / Line 270: @@
 Then you can boot from the USB disk and enjoy Android. Note all data are saved to the ramdisk, so all will lose after power off. If you hope to save data to disk, see the next section.
 Install to hard disk
 Install to a hard disk is just the same as install to a USB disk. Even you do not need to create a new partition. Just copy android files into an existing partition, install grub to the hard disk (if not done yet), and modify the menu.lst.
@@ Line 276: / Line 278: @@
      Boot from any rescue cd like systemrescuecd, and follow the instructions in the previous section.
      Install your favorite linux distribution, then copy android files and modify the grub menu.
 ==Save data to USB/hard disk==

@@ Line 194: / Line 194: @@
   lunch $number.
-==Build smaller image==
+==Membuat Image yang lebih kecil==
   USE_SQUASHFS := 0
-Before froyo-x86 (included), If you hope to get a more smaller image, you may remove the debugging symbols by adding
+Sebelum froyo-x86 (termasuk), Jika kita ingin membuat image yang lebih kecil lagi, kita dapat membuang berbagai simbol debugging dengan menambahkan
   TARGET_STRIP := 1
-Since gingerbread-x86, the debugging symbols are stripped by default. Do not use this option anymore.
+Sejak gingerbread-x86, simbol debugging akan dibuang secara default. Jangan gunakan fitur ini.
 ==Testing==

@@ Line 168: / Line 168: @@
   $ make -jX iso_img
-==Using lunch command==
+==Penggunaan perintah lunch==
   $ . build/envsetup.sh
-Now you can select a target by lunch command:
+Selanjutnya, kita dapat memilih target menggunakan perintah lunch:
   $ lunch $TARGET_PRODUCT-$TARGET_BUILD_VARIANT
-where $TARGET_PRODUCT is any target described in the previous section, and possible values of $TARGET_BUILD_VARIANT are eng, user, userdebug. For example,
+dimana $TARGET_PRODUCT adalah target yang di jelaskan sebelumnya, nilai yang mungkin untuk  $TARGET_BUILD_VARIANT adalah eng, user, userdebug. Contoh,
   $ lunch android_x86-eng
-Then you can build by m command:
+Selanjutnya, kita dapat membuat dengan perintah m
   $ m -jX iso_img
-m command is equivalent to make, but you can use it in any subdirectory of the android-x86 tree.
+perintah m kira-kira sama dengan make, tapi kita dapat menggunakannya di subdirectory manapun di bawah tree android-x86.
-Since froyo-x86, we also add menu selection to lunch command. Just type lunch, and you will get a list of available targets. Choose a target by inputting its number. Alternatively, just type lunch $number.
+ lunch $number.
 ==Build smaller image==

@@ Line 157: / Line 157: @@
 ==Menggunakan buildspec.mk==
-You can create a buildspec.mk in your android-x86 directory to remember a particular target product you build often:
+Kita dapat membuat buildspec.mk di directory android-x86 untuk memudahkan target tertentu yang sering kita buat. Misalnya, isinya
   TARGET_PRODUCT:=android_x86
   TARGET_BUILD_VARIANT:=userdebug
@@ Line 163: / Line 164: @@
   TARGET_KERNEL_CONFIG:=android-x86_defconfig
-With your buildspec.mk file in your android-x86 directory, you can just make by
+Dengan adanya file buildspec.mk di directory android-x86, kita hanya perlu melakukan make dengan
   $ make -jX iso_img

@@ Line 140: / Line 140: @@
   $ make iso_img TARGET_PRODUCT=android_x86
-To generate a live cdrom iso for tegav2, type
+Untuk membuat live cdrom iso untuk target tegav2, tulis:
   $ make iso_img TARGET_PRODUCT=tegav2
-Then you will get an iso file out/target/product/x86/android_x86.iso, etc.
+Kita akan memperoleh file iso di folder out/target/product/x86/android_x86.iso, dll.
-If the computer you build on has more then one processor or core, you can take advantage of multiprocessing (or make jobs) by adding -jX to the beginning of your make command:
+Jika komputer yang kita gunakan untuk build mempunyai lebih dari satu core,
   $ make -jX iso_img TARGET_PRODUCT=android_x86
-Replace X by the number of processors you have. For example, if you have a quad core CPU, replace X with 4:
+Ganti X dengan jumlah core yang kita miliki. Misalnya, kita mempunyai CPU quad core, ganti X dengan 4:
   $ make -j4 iso_img TARGET_PRODUCT=android_x86
-Using buildspec.mk
 You can create a buildspec.mk in your android-x86 directory to remember a particular target product you build often:

@@ Line 130: / Line 130: @@
 Jika kita seorang developer, kita dapat membuat sebuah target berdasarkan android_x86 untuk device yang kita inginkan.
-If you want to add new target for your x86 device, refer to the article.
+Jika kita ingin menambahkan target yang baru untuk device x86, ada baiknya membaca tulisan berikut,
 ==Membuat Android-x86==

@@ Line 121: / Line 121: @@
 Sejak branch eclair-x86, eeepc di ubah hanya untuk keluarga ASUS EeePC saja. Jangan gunakan itu, jika kita tidak menggunakan EeePC.
-In short, if you don't know how to choose, use eeepc for donut-x86 branch, and use generic_x86 for eclair-x86 to ics-x86 branches. But note generic_x86 is just a base for other targets. It doesn't have some advanced features like hardware acceleration.
+Singkatnya, jika kita tidak tahu apa yang harus kita pilih, gunakan eeepc untuk branch donut-x86,
-Since jb-x86 we tried to use android_x86 as a universal target for all x86 devices. However, it may not optimized for a particular target device. If you are a developer, you can create a target based on android_x86 for your device.
+Sejak jb-x86 Android-x86 berusaha untuk menggunakan android_x86 sebagai target universal bagi semua x86 device.
 If you want to add new target for your x86 device, refer to the article.