Author Topic: Testing 2.5.0  (Read 19541 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testing 2.5.0
« Reply #30 on: December 04, 2014, 01:21:34 PM »
Just got an Acer Iconia Tab 8 A1-840FHD and I look forward to testing the x86 version if you can kindly link me to it.

All three architectures are all packaged into the same APK, so don't need a special link for x86.  Note however that Gilles' dynarec fixes for x86 have not all been finalized yet, so can't play D64 on x86 with this version.  Depending on the timing, the rest of the dynarec fixes may go into update 2.5.1 if there aren't any more issues found during testing for 2.5.0.
« Last Edit: December 04, 2014, 01:23:14 PM 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

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: Testing 2.5.0
« Reply #31 on: December 04, 2014, 07:03:10 PM »
I tried yours and Gillou's and both crash on my Intel device mentioned earlier. :(
Problem is,Gillou updated 14 hours ago and I have not tried the version before that one,which I know works perfectly on FireTV.

Is Banjo-Tooie not playable in x86 either? :(

I sent reports from it just in case it helps more.

Edit:Forgot to mention I am running KitKat 4.4.4 version.
« Last Edit: December 04, 2014, 07:46:19 PM by retroben »

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: Testing 2.5.0
« Reply #32 on: December 04, 2014, 07:56:18 PM »
The emulator works splendidly with SM64 on Gillou's build.
Guess it answers that question. (Banjo-Tooie not running)
Sorry about the crash reports. :(

Edit:Nevermind,Banjo-Tooie crashed in the Play Store build as well,meaning a much larger issue for x86.

Also,why is RetroArch missing the N64 core when PSX/PS1 is there?
« Last Edit: December 04, 2014, 07:59:04 PM by retroben »

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testing 2.5.0
« Reply #33 on: December 04, 2014, 08:10:59 PM »
Latest release candidate for testing.  Littleguy made a new cleaner squashed branch for 2.x-bugfixes, and this build is from that branch:

2.5.0 RC3 (New squashed branch)
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 retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: Testing 2.5.0
« Reply #34 on: December 04, 2014, 08:19:29 PM »
Running SM64 on RC3 just fine.

What should I test specifically on this x86 Intel?
Which games,what settings,etc.

Edit:Also,the app is not reacting to the back button after exiting SM64.
It happens in all versions to my knowledge.
« Last Edit: December 04, 2014, 08:27:36 PM by retroben »

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testing 2.5.0
« Reply #35 on: December 04, 2014, 08:33:36 PM »
Anything you want to test will be fine.. looking for big stuff at this point.  I have a laptop I've been testing on that is x86 as well.  I haven't experienced the back button problem myself, is that happening only on the one device for you?  If you pull one of the older published versions does it have the same issue?
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 Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testing 2.5.0
« Reply #36 on: December 04, 2014, 08:38:14 PM »
To clarify, I'm manly concerned with regressions at this point.  Any problems you find, if you could compare to the previous published version to see if it is new, that would help identify what has broken (versus what has not yet been fixed)
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 retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: Testing 2.5.0
« Reply #37 on: December 04, 2014, 08:42:20 PM »
Happens in 2.4.4 version that I manually installed from within the Play Store app.
I am also having touch issues in Lucid Launcher.

Edit:LOL "manly concerned"  8)

Edit2:It fixed itself when touching it in recent apps list.
« Last Edit: December 04, 2014, 08:46:06 PM by retroben »

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: Testing 2.5.0
« Reply #38 on: December 04, 2014, 11:21:45 PM »
I can't access Glide64 settings to disable that dreaded "read every frame" option.
It makes Smash Bros have a horrendous framerate and is probably a battery killer.
Since I have a tablet now,I now have the privilege to be concerned about battery consumption issues.

With a PC,Glide64 easily consumes up to 80% CPU and slows to a crawl on PJ64 with the option enabled and a lot less when disabled.
How can I change this setting in Android when it is not located inside the config file of your build?
It was easy in xperia64's build Gillou's build because of the 3.0 features with access to settings for every plugin inside the ini file.
Your test build only has Rice settings on the ini file.

Edit:Banjo-Kazooie runs perfectly,I beat Mumbo's Mountain 100% in 18:50 on touch controls.
« Last Edit: December 05, 2014, 12:03:11 AM by retroben »

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Testing 2.5.0
« Reply #39 on: December 05, 2014, 06:09:50 AM »
I can't access Glide64 settings to disable that dreaded "read every frame" option.

Remember, we are only looking for bugs that have been added (i.e. "regressions") since the last *published* version on Google Play.  Version 2.5.0 should only contain critical bugfixes but no extra features vs the current published version.  So is what you describe a regression or simply a missing feature?
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Jermain

  • byte
  • *
  • Posts: 18
    • View Profile
Re: Testing 2.5.0
« Reply #40 on: December 05, 2014, 06:28:17 AM »
Hi Paul, your newest RC-3 works on my phone.

Thanks, looks good !!

Offline Zaneris

  • byte
  • *
  • Posts: 39
    • View Profile
Re: Testing 2.5.0
« Reply #41 on: December 05, 2014, 11:05:51 AM »
Auto still doesn't work for flicker reduction on the S5 and needs to be manually set to O-2.

Otherwise no issues found with RC3.

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: Testing 2.5.0
« Reply #42 on: December 05, 2014, 12:31:39 PM »
Not a regression with the ini,just an extremely major inconvenience for Glide64 users with inefficient hardware.
It makes things harder for me to test too.

The plugin with the most issues from Polygon offset is glN64,and mine in Gillou's build on FireTV is custom set to -0.10 for Banjo-Tooie's path textures to appear correctly without transparent Jinjo Village houses.
I use Rice though since it seems faster.

Also,I am about to get something like a bluetooth keyboard for my new tablet so I can "wreck shop" in the games.

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Testing 2.5.0
« Reply #43 on: December 05, 2014, 12:47:36 PM »
Thanks retroben.  Version 2.5 is just a stopgap until we are ready to publish version 3.0.  2.5 isn't intended to have any new features, regardless of how easy they might be to implement.  It *only fixes bugs* with the published version.  Version 3.0 will be published when it's ready.

Paul - In the meantime, I think it would be useful to start publishing alpha builds of 3.0 here on the forum so that testers and enthusiasts can all be on the same page.  It would help greatly if testers could refer to alpha builds in a consistent manner (e.g. by alpha version or commit hash).   I suggest we change the manifest signature on the 3.0 branch so that testers can enjoy both versions (published and alpha) on the same device.

retroben - I think you will find that the alphas will contain all the features you have been used to with "Gilles' build", since that was built from the 3.0 branch.  You will also see the fruits of your labor as new features are added and new alphas are posted for testing.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline xperia64

  • Moderator
  • double
  • *****
  • Posts: 591
    • View Profile
    • My Apps
Re: Testing 2.5.0
« Reply #44 on: December 05, 2014, 01:00:06 PM »
And Tegra K1 appears to have an offset of -0.95. Tested with Glide64+SM64 star road since it shows incorrect offsets the most.