Author Topic: Need x86 testers!  (Read 1818 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Need x86 testers!
« on: November 14, 2012, 07:52:48 AM »
Since Sven has resolved the save state and freeze problems, I'd like to start focusing on working out any x86-specific problems.  Anyone who has an Android device with one of the x86 processors instead of ARM, please test the latest build and let me know of any problems.  In case of crashes, please post the logcat output if you could.  Thanks!

x86 Test
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted

Offline flavuscrustum

  • bit
  • Posts: 1
    • View Profile
Re: Need x86 testers!
« Reply #1 on: December 31, 2012, 08:40:37 AM »
I have an orange san diego with Intel atom x86, before no N64 emulators worked, no games loaded, now most games at least start, but i seem to be having the problem the most games load, i can see their menu screens, input my name, watch the opening cut scenes ect, but they all seem to freeze before i can actually play the game
games I have tried, which have had this problem:
mario64, paper Mario, banjo kazooie, earthworm Jim, mario kart 64 legend of zelda OoT, Rayman 2,
those that are working fine:Tony hawks 2


Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Need x86 testers!
« Reply #2 on: December 31, 2012, 09:07:44 AM »
Considering the location, it seems like it could be an issue with writing to storage, rather than with the video plug-in.  Could you enable crash testing, create a profile with Mario64 so it freezes, then exit back to the menu and send a test crash report?

Also, to rule out a video plug-in cause, could you also test Mario64 with gles2rice (frame skip disabled) if you haven't already?
« Last Edit: December 31, 2012, 09:11:19 AM by Paul »
Device: Samsung Galaxy Nexus i515
CPU: TI OMAP4460, 1.2 GHz (dual core, ARM Cortex-A9)
GPU: PowerVR SGX540, 307 MHz
RAM: 1 GB
Resolution: 720 x 1280
Rom: omni-4.4.4-20141014-toro-FML KitKat 4.4.4, rooted

Device: Eee PC 1015PEM
CPU: Intel Atom N550, 1.5 GHz (dual core, x86)
GPU: Intel GMA 3150, 200 MHz (dual core)
RAM: 2GB
Resolution: 1024 x 600
Rom: android-x86-4.3-20130725 Jelly Bean 4.3, rooted