The resume/suspend issue has been resolved

The machine resume/suspend in Android-X86 is broken since Froyo release. Fyzzy7k has discovered solution for it. The detail can be found in http://groups.google.com/group/android-x86/browse_thread/thread/7b90d22458547de4?hl=en_US

Yi

Test report for Android-x86 Gingerbread on TX2500

Kyle Evans has posted test result for Gingerbread on TX2500

v2.3 - Gingerbread

Hardware Acceleration

Make & model: ATI - RS780

module: radeon

Yes, mostly, OpenGL ES2 still has bugs.

Touchscreen

Make & model: Wacom - TPC93

module: wacom

Yes, but finger coordinates are not right.

Wifi

Make & model: Broadcom - BCM4312

module: wl

Yes, mostly, Does not connect to WPA2 w/ AES authentication.

Ethernet

Make & model: Realtek - RTL8168

module: r8169

Yes

Bluetooth

Yes

Sound

Yes

Camera

No

Suspend

Yes, but resume requires holding a button for about 10 seconds.

Other/Notes

Bezel buttons - No

Screen rotation - No

Fingerprint reader - No

Card reader - Yes

Remote - Partially

Brightness adjustment does not work via GUI, but does via fn keys.

Test report for android-x86-4.0-tegav2 on Inspiron Duo

Azriel has posted a test result for android-x86-4.0-tegav2 on Inspiron Duo:

1. WiFi Works Great

2. Touch Works

3. GApps Work

4. Inspiron's Keyboard does not work (accept for escape key and the

arrows which rotate the display)

5. Touchpad Works

6. Multitouch seems to work

7. Wallpaper loads then dissapear

8. Camera Does not work

9. Sound not working

10. Scrollable list of running apps not working

Some new updates

About the build break on the Ubuntu 11.x that was mentioned last time, Scott McKenzie has posted a new patch, you can find it in https://github.com/cgjones/android-build/pull/1/files. I have not tested this patch yet, please let me know if you find it ok.

Another thing worth  to mention is that Henri has posted a new ethernet patch for Honycomb branch. Before Chih-wei accept/merge the patch, you should be able to find the patch in http://mansoft.nl/android/ethernet.diff.tar.gz.  I will upload it to the download section of  android-x86.org as well.  

Yi

Solutions for some issues found when compile and run ICS-x86

On android-x86 discussion group, some people have posted questions about the issues they found when compile and run ICS-x86. The first issue is about a compile error on Ubuntu 11 (asked by Tom tommronda@googlemail.com ). When he compiles ICS-x86 generic target, he was seeing following errors:

host C++: llvm-rs-cc <= frameworks/compile/slang/llvm-rs-cc.cpp :0:0: Fehler: »_FORTIFY_SOURCE« redefiniert [-Werror] :0:0: Anmerkung: dies ist die Stelle der vorherigen Definition cc1plus: Alle Warnungen werden als Fehler behandelt make: *** [out/host/linux-x86/obj/EXECUTABLES/llvm-rs-cc_intermediates/ llvm-rs-cc.o] Fehler 1

Robert Sharp <1130125@gmatc.matc.edu> has posted a solution for this:

Change the following line in frameworks/compile/slang/Android.mk to omit -Werror, i.e.: (Before) local_cflags_for_slang := -Wno-sign-promo -Wall -Wno-unused-parameter - Werror (After) local_cflags_for_slang := -Wno-sign-promo -Wall -Wno-unused-parameter

It seems that this issue only happens on Ubuntu 11.x where a newer GCC is installed. Ubuntu 10.04 seems to be ok.
Detail can be found in:
http://groups.google.com/group/android-x86/browse_thread/thread/47218458cf4efe10

The second issue is about kernel panic:
fuzzy7k has reported a kernel crash with ICS-x86 on his device (Turion X2). Later he tracks the issue down to a wrongly added CPU compiling flag in the file called bionic/libc/Android.mk that was changed by Google and Intel engineers. At the meanwhile Chih-wei is trying to get Intel and Google engineers to correct the flag. The detail can be found in following links: 
http://groups.google.com/group/android-x86/browse_thread/thread/27148b6840e06010 http://groups.google.com/group/android-x86/browse_thread/thread/297882b56e2c660f

A Nice Feature for the Touch Only Device

Buzz from Yi Sun

Android-x86 has a nice feature for the touch only device (no to have a button at all). If you touch the right corner of the status bar, it enables a touch mode that allows you to simulate the home/menus buttons through some touch actions on the status bar (see http://www.android-x86.org/documents/touch-only-device-howto). With the Amazon test drive, when you click the right corner of the status bar, you will see a dialog showing up on the screen that tells you to wait for the function to be turned on. Even though the full feature does not work with the Amazon test drive, but it proves that Amazon is using our software.

Amazon Test Drive Use Android-x86 !!

Today，our main developer Yi Sun confirmed that the Amazon use our android-x86 :p  

         Yi Sun - I'm 100% sure it is Android-x86. Since these icons
                        (battery, ethernet) are made by Chih-wei and me :-)

        5:51 AM

        ( Buzz from here)

Several days ago, Amazon's Appstore provide a new service to let users can test the android app online before they buy it. Its name is Amazon Test Drive. (  Engadget: Amazon.com lets you play with an Android virtual machine, try apps before you buy them )

@bluestacksinc found Amazon Test Drive might run the android apps on andorid-x86 in Amazon EC2.

http://twitpic.com/4k2qse

 
In fact,  @bluestacksinc also provide an android VM on x86 platform. ( @techoutfitters BluesStacks Can Run Android on x86-based Windows PCs -- http://bit.ly/hNUNr0 )

Hi, @Amazon, thank you for choosing Android-x86.org !!

Cheers !!

By the way,  if you want to know the latest news about android-x86.org, follow @andorid_x86 or 關注 android-x86 微博