Author Topic: Testing 2.5.0  (Read 19553 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Testing 2.5.0
« on: December 02, 2014, 08:08:04 PM »
This is the release candidate for 2.5.0.  Anyone who would like to test, feel free and please post if you find any issues.

2.5.0 RC1

2.5.0 RC2 (Lollipop MOGA crash test)

2.5.0 RC3 (New squashed branch)


If you have any previous test builds installed, you may need to uninstall them first to avoid signature conflicts.
« Last Edit: December 04, 2014, 08:09: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 #1 on: December 02, 2014, 11:59:28 PM »
You could have at least used the Play Store version's manifest instead of the same debug one as xperia64's build and Gillou's 3.0 build.

Gillou's build is particularly and extremely useful to me with all of the nifty 3.0 stuff already in it.

Maybe come to a consensus by making an entirely different manifest that makes it a seperate app.

Edit:I can't even take advantage of root to splice the files because the app will still overwrite the other ones folders or have some other major corruption issue,so please use the information from the Play Store version or please make a seperate named one just for this test.
« Last Edit: December 03, 2014, 12:11:11 AM by retroben »

Offline retroben

  • float
  • ****
  • Posts: 432
    • View Profile
Re: Testing 2.5.0
« Reply #2 on: December 03, 2014, 12:58:21 AM »
UHHHHHHHHHHHHHHHHH!!!!!!

MAH CRAPPY (RCA) TABLET ALREADY DIED!!!

I was just trying your test build on the tablet since there would have been nothing to lose until it randomly shut off during Banjo-Tooie's intro.
I can't get it to turn back on,the charger didn't even help.

You are not to blame,it is because I ran Reicast,then Dolphin Emu on it with Luigi's Mansion the other day,and it is likely the cause of the tablet's failure. (besides tablet being crappy)

PLEASE use an alternate app space so I don't have to get rid of Gillou's build!

Offline Shadsterwolf

  • bit
  • Posts: 6
    • View Profile
Re: Testing 2.5.0
« Reply #3 on: December 03, 2014, 01:28:26 AM »
-Banjo Tooie doesn't crash
-Donkey Kong 64 is fixed collision elements
(Tegra 4 Nvidia Shield Portable)

I just today thought "I wonder what that Paul guy is up to".
I gasped when behold I saw the Testing 2.5 title.
Looks like Chrismas came early.

You guys are amazing!
I hope that no other emulators take your creation.
Thank you so much for your dedication and hard work!

Offline Jermain

  • byte
  • *
  • Posts: 18
    • View Profile
Re: Testing 2.5.0
« Reply #4 on: December 03, 2014, 07:38:10 AM »
Hello Paul,

I just tested the apk, and it crashes when I start a game. (all games)

I'm using a Nexus 5 with Android Lollipop.

I don't know how I can make a log. Maybe I can help.

Thank You !!

Good Luck !!
« Last Edit: December 03, 2014, 07:40:19 AM by Jermain »

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Testing 2.5.0
« Reply #5 on: December 03, 2014, 06:07:21 PM »
@Paul @Gilles @xperia64

I suggest we put all hands on deck to get 2.5.0 out the door, then stop work on the 2.x branch for good.  If that's not realistic, then we should at least stop syncing 2.x with upstream after this revision.  My head is swimming with how complex the repo graph is.

Alternatively, I'm not opposed to *not* publishing 2.4.5 or 2.5.0 and simply killing that whole branch right after the 2.4.4 tag.  :P  We could publish some alpha releases on this forum only so that folks like retroben can continue to enjoy all the newness in the meantime.  Am I crazy?
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 #6 on: December 03, 2014, 06:17:53 PM »
I think it's good to get the DK64 and Banjo Tooie fixes on GPlay, but after that, 2.X is dead.

Does the RC contain any rice changes? This amazing thing happened in DK64
Spoiler: show

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Testing 2.5.0
« Reply #7 on: December 03, 2014, 06:27:43 PM »
Should we wait for the x86 changes related to DK64 for 2.5, or they likely still a ways off?  I'll move 2.4 and 2.5 to my fork after publishing, and we can delete it from the main repo to clean up the graph.
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 #8 on: December 03, 2014, 06:31:38 PM »
Another option to clean up the graph, I could rewrite the history on those branches, and just squash the upstream commits.  The new mainline of the 2.x branch would be identical to the old commit for commit, but it would be a lot easier to follow.

Edit: Ug, that's actually not an easy operation to do.
« Last Edit: December 03, 2014, 06:52:33 PM by littleguy »
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline littleguy

  • Moderator
  • double
  • *****
  • Posts: 1945
    • View Profile
Re: Testing 2.5.0
« Reply #9 on: December 03, 2014, 08:45:00 PM »
Ok, once we have decided to stop development on the 2.5-bugfixes branch, I can re-write the entire branch like I did here:
https://github.com/littleguy77/mupen64plus-ae/commits/example/2.x-bugfixes

This was actually pretty easy to do with a GUI.  That will clean up the graph substantially, squashing the upstream merges into single commits and consolidating that branch's commits together on a timeline.  That will allow us to keep all the commits in the main repo in case any new or old devs want to take a look.  Hit the right arrow key on this page to see what I mean:
https://github.com/littleguy77/mupen64plus-ae/network
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 #10 on: December 03, 2014, 09:49:11 PM »
I played DK on the OUYA for a couple hours.  No issues with glide, and running full speed.  My own tests have been successful.  I'll look into the crash that was reported.

Jermain, just a couple quick things first, I assume the previous version of the app didn't crash, correct?  Check if uninstalling and then reinstalling the app helps.  Also try rebooting the device.  Unlikely to help, but worth a shot.  Turn on crash reporting in the settings, and put in your username so I can find your report easily.  Then have the app crash again so it sends the report.
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 #11 on: December 03, 2014, 10:34:22 PM »
I also got an immediate crash after pressing the play button.  I just upgraded to Lollipop, not sure if that has anything to do with it.  Looks like some new restrictions on intents perhaps?  Master runs without trouble for me however.  I'll take a closer look...
Code: [Select]
12-03 23:30:36.376: E/ACRA(16336): --------- beginning of crash
12-03 23:30:36.440: E/AndroidRuntime(16336): FATAL EXCEPTION: main
12-03 23:30:36.440: E/AndroidRuntime(16336): Process: paulscode.android.mupen64plusae, PID: 16336
12-03 23:30:36.440: E/AndroidRuntime(16336): java.lang.RuntimeException: Unable to start activity ComponentInfo{paulscode.android.mupen64plusae/paulscode.android.mupen64plusae.PlayMenuActivity}: java.lang.IllegalArgumentException: Service Intent must be explicit: Intent { act=com.bda.controller.IControllerService }
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2298)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2360)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ActivityThread.access$800(ActivityThread.java:144)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1278)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.os.Handler.dispatchMessage(Handler.java:102)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.os.Looper.loop(Looper.java:135)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ActivityThread.main(ActivityThread.java:5221)
12-03 23:30:36.440: E/AndroidRuntime(16336): at java.lang.reflect.Method.invoke(Native Method)
12-03 23:30:36.440: E/AndroidRuntime(16336): at java.lang.reflect.Method.invoke(Method.java:372)
12-03 23:30:36.440: E/AndroidRuntime(16336): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:899)
12-03 23:30:36.440: E/AndroidRuntime(16336): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:694)
12-03 23:30:36.440: E/AndroidRuntime(16336): Caused by: java.lang.IllegalArgumentException: Service Intent must be explicit: Intent { act=com.bda.controller.IControllerService }
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ContextImpl.validateServiceIntent(ContextImpl.java:1674)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1703)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ContextImpl.startService(ContextImpl.java:1687)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.content.ContextWrapper.startService(ContextWrapper.java:515)
12-03 23:30:36.440: E/AndroidRuntime(16336): at com.bda.controller.Controller.init(Controller.java:325)
12-03 23:30:36.440: E/AndroidRuntime(16336): at paulscode.android.mupen64plusae.PlayMenuActivity.onCreate(PlayMenuActivity.java:81)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.Activity.performCreate(Activity.java:5933)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1105)
12-03 23:30:36.440: E/AndroidRuntime(16336): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2251)
12-03 23:30:36.440: E/AndroidRuntime(16336): ... 10 more

EDIT: Reverting this commit fixes the crash for me.  I'll look into the correct solution moving forward, but I see no harm just reverting for this release.
https://github.com/mupen64plus-ae/mupen64plus-ae/commit/fde4e59215a92a8fd3eabe45598677b61da8e837

EDIT2: Bummer, the crash is occurring in the third-party MOGA library.  We are already using the latest version.  I'll keep digging.

EDIT3: Looks like reverting to API 19 is the recommended solution from the venerable commonsware
http://commonsware.com/blog/2014/06/29/dealing-deprecations-bindservice.html

EDIT4: Reverting to API 19 is the only solution for now since we cannot fix the intent syntax inside the third-party MOGA library.  I'll shoot an email over to the MOGA rep I've communicated in the past to make them aware of the issue.
« Last Edit: December 03, 2014, 11:02:47 PM by littleguy »
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 #12 on: December 03, 2014, 11:09:06 PM »
Appears to be a problem in the mogaController init() method.

--EDIT-- Haha, you beat me to it.  Yes, we can switch target API to 19 for now I suppose.
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 #13 on: December 03, 2014, 11:15:10 PM »
I think it's good to get the DK64 and Banjo Tooie fixes on GPlay, but after that, 2.X is dead.

Does the RC contain any rice changes? This amazing thing happened in DK64
Spoiler: show


Probably will have to pinpoint where the problem appeared more closely to track it down.  DK64 really only works well with glide anyway, what with the camera not rotating smoothly, but new problem could affect other games.
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 #14 on: December 03, 2014, 11:16:55 PM »
Bummer, emails to my contact at MOGA are bouncing.  Not looking good over there.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version