$ repo init -u git://git.android-x86.org/manifest.git -b gingerbread-x86
$ repo sync
Pushing to SourceForge mirror is on the way.
Should be ready in one day.
All the targets supported by froyo-x86 are updated
to be build-able for gingerbread-x86.
Sound and wifi works.
No 3D, ethernet, mouse yet.
You may find screenshots of gingerbread-x86
from my blog: http://cwhuang.info
Note to the changes of build system:
* AOSP has merged Intel's generic_x86 target. But it sucks,
and conflicts with our efforts. Anyway, I've tried to minimize
the conflicts, and move common files like firmwares and keymaps
* You may also put prebuilt apks in device/common/app/.
They will be included in the iso_img or usb_img automatically.
* Wifi is on by default. To disable it in your target, set
* Touchscreen is on by default. To disable it, set
BOARD_USES_TSLIB := false
* Gingerbread uses ext4 as the filesystem for /system.
If you create a customized kernel config, make sure
you have set CONFIG_EXT4_FS=y
I forgot to mention a more important change.
As AOSP, gingerbread-x86 requires a 64-bit
build environment, and java 1.6.
So remember to upgrade your build host.
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
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To post to this group, send email to andro...@googlegroups.com.
To unsubscribe from this group, send email to android-x86...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/android-x86?hl=en.
I am assuming that only the build environment (primarily the jdk) required is 64 bit?
I hope the final kernel, libraries and binaries on the target are all 32 bit still? Is this correct?
I am asking because I run android inside VirtualBox and if gingerbread kernel is 64 bit then it won't work for me because VirtualBox requires VT-x for 64 running bit guests, which the current Atom N-4XX's don't have.
--- On Wed, 26/1/11, Chih-Wei Huang <cwh...@android-x86.org> wrote:
Another important change I forgot to mention.
In froyo-x86, you may know you could get a smaller
image (strips all debugging symbols) by adding
TARGET_STRIP := 1
In gingerbread-x86, the debugging symbols are stripped
by default, so no need to use this variable anymore.
Actually the AOSP has used the variable for a
different meaning. Make sure you remove it
from your buildspec.mk.
Sure, android(-x86) itself is still a 32-bit OS.
Most arm cpus are still 32-bit, right?
Hi , sorry to tell you, but at the moment only the source code is
available for download.
So you can grab it build your own image. That's what I know.
And android(-x86) is still a 32 bit os.
I am learning to use this without a mouse pointer, but it will be nice to have it back... perhaps I can find the setting in the preferences to disable using the pointing device as a thumb-pad? Hopefully this was not a compile-time option!
Wi-fi still works, still seems to be necessary to reload my driver manually from command-line to scan successfully.
The graphics are not where they were in froyo, everything is sluggish, try removing video=-16 parameter from boot options; that will be my next step. On first successful boot, I can say this system does not perform like it has been compiled with the right options I915= and I915C=true
This is a Gingerbread report with Acer AOA-150 AspireOne hardware. Thanks for the help!
喜欢 it is very easy to accidentally trigger the chinese input also :D
2011/3/20 Yebyen (Kingdon) <xulru...@gmail.com>:
> Removing video=-16 made things much worse...
> I will have to go back over my notes and see what's changed since froyo ^_^