Post Reply 
 
Thread Rating:
  • 2 Votes - 3 Average
  • 1
  • 2
  • 3
  • 4
  • 5
android x86 4.0 released with arm translator support
06-25-2013, 03:45 PM (This post was last modified: 06-25-2013 03:58 PM by MaXiMu.)
Post: #1
android x86 4.0 released with arm translator support
http://www.android-x86.org/releases/releasenote-4-0-r1

Aceleration 2D/3D working fine with intel and AMD GPU

Antutu test score 47000 points with I3-350M and Intel HD graphics .

[Image: fz7rlf.jpg]

[Image: 2r726fk.jpg]



But bad news PPSSPP won't work crash

Code:
06-25 16:17:07.933  1686  2042 I ActivityManager: Start proc org.ppsspp.ppsspp for activity org.ppsspp.ppsspp/.PpssppActivity: pid=7000 uid=10062 gids={1015, 3003}

06-25 16:17:07.943  7000  7000 I dalvikvm: Could not find method android.media.AudioManager.getProperty, referenced from method com.henrikrydgard.libnative.NativeActivity.detectOptimalAudioSettings

06-25 16:17:07.943  7000  7000 W dalvikvm: VFY: unable to resolve virtual method 32: Landroid/media/AudioManager;.getProperty (Ljava/lang/String;)Ljava/lang/String;

06-25 16:17:07.943  7000  7000 D dalvikvm: VFY: replacing opcode 0x6e at 0x000a

06-25 16:17:07.943  7000  7000 D dalvikvm: Trying to load lib /data/data/org.ppsspp.ppsspp/lib/libppsspp_jni.so 0xa06602c8

06-25 16:17:07.943  7000  7000 E dalvikvm: The lib may be ARM... trying to load it [/data/data/org.ppsspp.ppsspp/lib/libppsspp_jni.so] using houdini

06-25 16:17:07.943  7000  7000 D houdini : [7000] Loading library(version: 2.0.5.42475 RELEASE)... successfully.

06-25 16:17:07.953  7000  7000 F libc    : Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)

06-25 16:17:08.253  1639  1639 I DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

06-25 16:17:08.253  1639  1639 I DEBUG   : Build fingerprint: 'generic_x86/asus_laptop/laptop:4.0.4/IMM76L/eng.cwhuang.20130623.115113:userdebug/test-keys'

06-25 16:17:08.253  1639  1639 I DEBUG   : pid: 7000, tid: 7000  >>> org.ppsspp.ppsspp <<<

06-25 16:17:08.253  1639  1639 I DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000

06-25 16:17:08.253  1639  1639 I DEBUG   :  eax 04d10001  ebx 92000020  ecx 00000000  edx 0000000d

06-25 16:17:08.253  1639  1639 I DEBUG   :  esi 9200005c  edi 00000001

06-25 16:17:08.253  1639  1639 I DEBUG   :  xcs 00000073  xds 0000007b  xes 0000007b  xfs 00000043 xss 0000007b

06-25 16:17:08.253  1639  1639 I DEBUG   :  eip 9a2d18c3  ebp 9200ff6c  esp 9200fee4  flags 00010202

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  eip: 9a2d18c3  /system/lib/libhoudini.so

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  eip: 9a2c0654  /system/lib/libhoudini.so

06-25 16:17:08.333  1639  1639 I DEBUG   :     #02  eip: 9a2c0a1e  /system/lib/libhoudini.so

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  eip: 9a2d5952  /system/lib/libhoudini.so

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  eip: 00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   : stack:

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200fee4  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200fee8  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200feec  92000020  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200fef0  92000020  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200fef4  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200fef8  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200fefc  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff00  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff04  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff08  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff0c  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff10  92000058  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff14  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff18  92000054  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff1c  00000e4d  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #00  9200ff20  00000001  

06-25 16:17:08.333  1639  1639 I DEBUG   :     ......  ......  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff70  9a2c0654  /system/lib/libhoudini.so

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff74  6912f0a8  /system/lib/arm/libc.so (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff78  92000020   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff7c  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff80  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff84  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff88  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff8c  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff90  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff94  6912f0a8  /system/lib/arm/libc.so (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff98  00000001   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ff9c  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ffa0  00001a44   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ffa4  00006910   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ffa8  92000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     #01  9200ffac  00000000   (strncpy)

06-25 16:17:08.333  1639  1639 I DEBUG   :     ......  ......  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #02  9200ffd0  9a2c0a1e  /system/lib/libhoudini.so

06-25 16:17:08.333  1639  1639 I DEBUG   :     #02  9200ffd4  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #02  9200ffd8  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #02  9200ffdc  9200fffc  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200ffe0  9a2d5952  /system/lib/libhoudini.so

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200ffe4  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200ffe8  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200ffec  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200fff0  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200fff4  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200fff8  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #03  9200fffc  bfae9168  [stack]

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010000  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010004  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010008  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  9201000c  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010010  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010014  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010018  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  9201001c  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010020  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010024  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010028  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  9201002c  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010030  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010034  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  92010038  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     #04  9201003c  00000000  

06-25 16:17:08.333  1639  1639 I DEBUG   :     ......  ......  

06-25 16:17:08.433  1686  1707 I Process : Sending signal. PID: 7000 SIG: 3

06-25 16:17:08.433  7000  7004 I dalvikvm: threadid=3: reacting to signal 3

06-25 16:17:08.433  7000  7004 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'

06-25 16:17:08.533  6957  6958 D dalvikvm: GC_CONCURRENT freed 1712K, 18% free 8433K/10247K, paused 0ms+2ms

06-25 16:17:08.533  1686  1721 V BatteryService: update battery level = 100

06-25 16:17:08.933  1686  1707 I Process : Sending signal. PID: 7000 SIG: 3

06-25 16:17:08.933  7000  7004 I dalvikvm: threadid=3: reacting to signal 3

06-25 16:17:08.933  7000  7004 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'

06-25 16:17:09.433  1686  1707 I Process : Sending signal. PID: 7000 SIG: 3

06-25 16:17:09.433  7000  7004 I dalvikvm: threadid=3: reacting to signal 3

06-25 16:17:09.433  7000  7004 I dalvikvm: Wrote stack traces to '/data/anr/traces.txt'

06-25 16:17:09.483  1641  1641 D Zygote  : Process 7000 terminated by signal (11)

06-25 16:17:09.483  1686  1686 I ActivityManager: Process org.ppsspp.ppsspp (pid 7000) has died.

edit > hmm.. no i try with oldest version and the problem with sound no exist but same crash its related with lib arm..
Find all posts by this user
Quote this message in a reply
06-25-2013, 07:36 PM
Post: #2
RE: android x86 4.0 released with arm translator support
Nice! Gonna do a Live USB tonight!
Find all posts by this user
Quote this message in a reply
06-25-2013, 08:11 PM
Post: #3
RE: android x86 4.0 released with arm translator support
Some emulators detected working in my notebook
Epsxe
Software plugin Working but slow
Hardware plugin working full speed
Opengl plugin 0fps black screen freeze no crash.

NDS4droid
Software plugin and interpreter thread fully speed only tested super mario 64 DS
Hardware plugin is very slow compared than software plugin

FPSE
Working but very slow

Mupenplus64 AE
Working with three plugin glide , rice and gl64
conker running decent speed some slowdon in the cutscene but ok speed on gameplay and possibles some crashes
super mario 64 fully speed.

limited hardware supported
- wifi propietary broadcom
- bluetooth not work for me
- some aplication crashes for some rason related with driver gpu problem example quadrant
- freeze resume and suspense.
Find all posts by this user
Quote this message in a reply
06-26-2013, 10:09 AM (This post was last modified: 06-26-2013 10:15 AM by MaXiMu.)
Post: #4
RE: android x86 4.0 released with arm translator support
I upload video with some test working fine
Crash on conker only success with glide plugin but with rice plugin this crash not exist.



Find all posts by this user
Quote this message in a reply
07-28-2013, 06:05 PM (This post was last modified: 07-29-2013 11:57 AM by Snake Eyes.)
Post: #5
RE: android x86 4.0 released with arm translator support
New Android x86 4.3 test build is out, and it is much better than the last 4.0R1! I tested it in a HP G42 i3 350M Intel HD and scored 47110 pts in Antutu.
Also PPSSPP android version now works, including keyboard support (I had to remap buttons). It detects my X360 wireless controller, but android have a crazy keymap, impossible to configure with PPSSPP AFAIK.

I`m still testing but the results so far are very impressive.
Find all posts by this user
Quote this message in a reply
07-28-2013, 09:49 PM
Post: #6
RE: android x86 4.0 released with arm translator support
Stupid question, do I have to use Linux in order to boot and install this normally and afterwards give it a shot?
Does it work with Windows 7? I was planning to making an external drive letter with about 10 gbs if that is alright, thanks. Smile

Laptop:________________________Desktop:
Windows 10 64-bit, 8GB DDR4 RAM | Windows 10 64-bit, 8GB DDR3 RAM
Intel® Core™i5-7300HQ 2,5/3.5ghz | Intel® Core™i5-4440 3,10ghz
NVIDIA GTX 1050 Ti_____________| NVIDIA GTX 1060 3GB
Visit this user's website Find all posts by this user
Quote this message in a reply
07-28-2013, 10:30 PM (This post was last modified: 07-28-2013 11:05 PM by Snake Eyes.)
Post: #7
RE: android x86 4.0 released with arm translator support
(07-28-2013 09:49 PM)FinalBlast Wrote:  Stupid question, do I have to use Linux in order to boot and install this normally and afterwards give it a shot?
No, android x86 is stand alone. Actually I believe android based on linux.

(07-28-2013 09:49 PM)FinalBlast Wrote:  Does it work with Windows 7? I was planning to making an external drive letter with about 10 gbs if that is alright, thanks. Smile
You can run it in a virtual machine, but VMs are really slow. Or you can create a dual boot (see android-x86.org for details). The best option is create a installation pen drive with Lili USB creator and make a Ext3 partition exclusive for android x86 (NTFS & FAT32 are limited to 2GB). But if you just want to test you don't need to install, there is a option to load without installation.
Find all posts by this user
Quote this message in a reply
07-29-2013, 06:46 AM
Post: #8
RE: android x86 4.0 released with arm translator support
I try android 4.3 and new bug for me ethernet dchp 99% fail and not asigned ip and no change for broadcom wifi support "turning on loop"

in android 4.0 ethernet gigabyte working fine

but better compatibility up mesa to 9.2 version now running ppsspp and others aplication.
Find all posts by this user
Quote this message in a reply
07-30-2013, 02:26 PM
Post: #9
RE: android x86 4.0 released with arm translator support
how do i uninstall GRUB?

Contact::::
I don't exist anymore, no use calling a dead person
Find all posts by this user
Quote this message in a reply
07-30-2013, 06:45 PM (This post was last modified: 07-30-2013 06:47 PM by MaXiMu.)
Post: #10
RE: android x86 4.0 released with arm translator support
If is windows with bootable cd/dvd or usb bootable .

With XP
repare option on console cmd
1) fixboot C: (change you letter on exist you mbr)
2) fixmbr

Winvista and higher
repare option on console cmd
1) Bootrec.exe /FixBoot
2) Bootrec.exe /Fixmbr
Find all posts by this user
Quote this message in a reply
07-31-2013, 02:43 PM
Post: #11
RE: android x86 4.0 released with arm translator support
anyway,was jb 4.2 released wo JIT?bcuz,im gettin super slow acceleration in this build...

Contact::::
I don't exist anymore, no use calling a dead person
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump: