Wednesday, January 26, 2011


Personally I used Fedora 14 x86_64, 
with its openjdk 1.6.0. 
It works fine for me. 
For a complete rpm list 
you need to install on Fedora 14, see 
Android-x86 project 

This is a project to port Android open source project to x86 platform, formerly known as "patch hosting for android x86 support". The original plan is to host different patches for android x86 support from open source community. A few months after we created the project, we found out that we could do much more than just hosting patches

You can install Android-x86 to an NTFS filesystem to co-exist with Windows. See theAdvanced section for details.


How to create a bootable USB stick for Android-x86?

  • Use the USB image
    Download the compressed USB image, uncompress and dump it to a USB stick. On a Linux host, you can use the command
    # zcat android-x86-1.6-r2_usb.img.gz | dd of=/dev/sdc
    where /dev/sdc is the device name of the target USB disk. However, some broken BIOS may fail to boot such a USB disk.
  • Create a bootable USB stick by iso
    There are some open source tools that can convert an iso into a bootable USB disk, say


To boot other operating systems, you have to add items for them to /grub/menu.lst. For example, to boot Windows, add the following:
title Windows
    rootnoverify (hd0,0)
    chainloader +1
This assumes the Windows is installed to the first partition of the first hard disk. Or you need to change rootnoverify to the appropriate value. See Grub manual for details.

Gingerbread has been properly replicated to the production servers.
First things first: I would greatly appreciate if everyone could avoid
syncing immediately. So, "all clear, but please proceed with caution
to avoid accidents".
The servers are currently slow with all the traffic. The fine people
at are doing a great job at keeping them running under the
load (and I genuinely mean that). Really, please, if you're only
curious and don't intend to immediately build Gingerbread and port it
to hardware, waiting a few hours or a few days would help the entire
Here are the branches that you care about:
-android-2.3_r1 is the exact code that was used to build GRH55, which
is the version that is shipping on Nexus S.
-gingerbread is the mirror of Google's internal development branch for
2.3, i.e. it's very close to what's in android-2.3_r1 but not quite
identical (this reflects the multiple levels of approvals that
last-minute changes go through).
-master contains Gingerbread plus all the contributions received
through AOSP that had missed Google's internal merge window for
Gingerbread (those will be in Honeycomb)
-temporarily, a branch called froyo-plus-aosp contains the state of
master as it was before I started the push. If you were working in
master before this morning and find that the gingerbread changes are
causing you trouble, this'll let you temporarily get back to a
pre-gingerbread state.
As usual, all platform contributions should be uploaded against the
master branch.
If you already have a previously synced client (e.g. froyo), here's
how you can minimize the impact on the servers while syncing one of
the new branches (e.g. gingerbread):
-sync that existing client.
-in a new directory, repo init -u
git:// -b gingerbread
-cp -R /.repo/projects .repo
-repo sync the new client.
Please also follow the other threads on this group for more
information about specific aspects of this release.
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further

Android 2.3 (Gingerbread) the build system to introduce significant change is required to be in the 64-bit environment to compile . This is how much the developer point of distress caused, because the development environment must first upgrade to 64-bit Caixing.

The following is my personal compiled in Fedora 14 Gingerbread approach. First, of course, you must first install Fedora 14 x86_64 version. Then install the following development tools:

gcc-c + +

That was not enough, have to install some 32-bit (i686) version of the rpm:

libstdc + +-devel.i686

This is because the toolchain tools AOSP not update 64-bit, so had to mix 32-bit version of the development libraries.

Although this can be compiled successfully, but when run emulator will appear:

Android-x86 has been released nearly a year without a new stable version. For this release, really spent a lot of time to prepare. In addition to great fanfare last few minor amendments, the order to confirm the source code can be compiled, but also with the new machines, checkout a new re-build the whole tree down. Iso file restated five spent several hours of time. Again upload google code and SourceForge download area, but also a long wait.
The last test version 20110101 userdebug try to compile mode. Think of the resulting installer can not format. Because only in eng mode mke2fs will be compiled in.. There are other side effects of concern, the official version or the use of eng mode. Fortunately, there are first put the test version, or to appear in the official version of this embarrassing problem.
The most troublesome areas or to the current source tree with android-x86-2.2 of the tag. This was specifically to write a script to parse manifest.xml Caixing. To do otherwise would be sick of manually! Eventually, written Release note , and update the home page. It took the whole things right, that was almost a working day time. Process of hard work, feverish mother nine months of pregnancy in general.
In any case, finally make the official release Android-x86 2.2. Although there are many unsatisfactory, but the total of the first end. Then you can concentrate on preparing gingerbread-x86 to work.

Wednesday, January 19, 2011

enter symbol in html ascii code

⏎ ("RETURN SYMBOL") (enter symbol in ascii )

if you add the code below into html and then view it in  your browser you will get the symbols above

& # x 2 3 c e ;  ("RETURN SYMBOL") (without spaces blogger cant show pre code)

Tuesday, January 4, 2011

Basic service set identifier (BSSID)

In Infrastructure Mode, the Basic Service Set Identifier (BSSID) is the 48-bit MAC address of the wireless interface of the Access Point.

Basic service set identifier (BSSID)

A related field is the BSSID or Basic Service Set Identifier, which uniquely identifies each BSS (the SSID however, can be used in multiple, possibly overlapping, BSSs). In an infrastructure BSS, the BSSID is the MAC address of the wireless access point (WAP). In an IBSS, the BSSID is a locally administered MAC address generated from a 46-bit random number. The individual/group bit of the address is set to 0. The universal/local bit of the address is set to 1.
A BSSID with a value of all 1s is used to indicate the broadcast BSSID. A broadcast BSSID may only be used during probe requests.

802.11b, 802.11g, 802.11a, 802.11n sniffing
Standard PCAP file logging (Wireshark, Tcpdump, etc)
Client/Server modular architecture
Multi-card and channel hopping support
Runtime WEP decoding
Tun/Tap virtual network interface drivers for realtime export of packets
Hidden SSID decloaking
Distributed remote sniffing with Kismet drones
XML logging for integration with other tools
Linux, OSX, Windows, and BSD support (devices and drivers permitting)