Author Topic: Testing 2.5.0  (Read 19555 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testing 2.5.0
« Reply #45 on: December 05, 2014, 02:12:35 PM »
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.

Agreed.  Should I use your sample gridview gallery initially, or hurry up and get my carousel UI to at least a roughly usable state?  ;D
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 littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Testing 2.5.0
« Reply #46 on: December 06, 2014, 02:25:24 PM »
I'm a little concerned that hunting down these regressions will divert too much attention from version 3.  I'd rather sprint to v3 than deal with regressions in a branch that for all intents and purposes is already dead.  Some regressions won't exist in v3, and cherry-picking fixes between the two branches isn't trivial due to the extensive refactoring.

My vote is not to publish 2.4.5 or 2.5.0...
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testing 2.5.0
« Reply #47 on: December 06, 2014, 02:39:58 PM »
Ok, will see what everyone else thinks.  Obviously anyone can get the app on the forum from here anyway.  We would need to publish something when we are ready to publish the 3.0 alphas as a separate app on the Play Store, though.
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 #48 on: December 06, 2014, 04:25:22 PM »
Still on RC3 and Majora is running beautifully despite the same GFX plugin "first initialization" issue with Glide64.
This time,it makes pause menu items invisible and lacks the blurry after-image effects on first run.
No lags at all on my Intel x86 tablet though,which is lovely since "read every frame" can't be disabled in RC3.

It appears to have timer issues with Final Day's Clock Town countdown moving very rapidly,unless it is supposed to be that fast.
The timer inside the tower is at normal speed.

Offline Zaneris

  • byte
  • *
  • Posts: 39
    • View Profile
Re: Testing 2.5.0
« Reply #49 on: December 06, 2014, 04:49:13 PM »
I think 2.5 should be published as is, forget about x86, it's a small market anyway. Just so the majority can get the dynarec fix.

Just my 2 cents though.

Offline TwoSquidGames

  • bit
  • Posts: 1
    • View Profile
Re: Testing 2.5.0
« Reply #50 on: September 08, 2015, 09:09:00 PM »
Does anyone have that MOGA fix? I'm an Android game dev, looking to keep MOGA support in my games. I discovered this MOGA Lollipop bug just today.