Author Topic: Finishing up the final pieces  (Read 14466 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Finishing up the final pieces
« Reply #45 on: January 08, 2013, 06:05:16 AM »
I agree.  I've really considered making it default, but haven't yet because of the speed (it is much slower on most devices, especially with frame skip disabled, which is necessary to avoid frozen video in most games).  I think it could get there with a little more improvement, so glad to see you will be working on it!
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: Finishing up the final pieces
« Reply #46 on: January 08, 2013, 05:18:18 PM »
Paul - I can't remember where you mentioned it, but I think it actually would make a lot of sense to run the Play menu as its own activity.  With preference menus, you only get one opportunity to add/remove preferences and that's in the preference activity lifecycle functions such as onCreate or onResume.  So making the Play menu its own preference activity would really simplify the mechanics.  It would cache the name of the last ROM used in AppData (persisting of course).  On create it would see if the ROM filename changed, and if so would recompute the CRC info (which it would also then persist to AppData).  We should also be able persist the cheat options themselves.  Anyhow if you're dying to implement it go for it, otherwise I'm happy to do it.  Just let me know.
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: Finishing up the final pieces
« Reply #47 on: January 08, 2013, 06:04:03 PM »
If you don't mind tackling that one, I would like to look at the rsp plug-in this evening.  I didn't realize more devices were affected by it than the Kindle Fire HD - it could potentially be a problem for a large number of users.
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: Finishing up the final pieces
« Reply #48 on: January 08, 2013, 06:20:05 PM »
Will do.  Nice that you have the other version for direct comparison.

One more request - could you go to the BugSense dashboard and delete the Mupen64Plus AE app, then re-create it?  If you use the same name you don't even need to change the source code.  The reason I ask is because I filled it with garbage during debugging (that was stupid!) and would be nice now if that stuff wasn't in there.  Deleting and re-creating the project in bugsense is apparently the only way to remove crash reports.
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: Finishing up the final pieces
« Reply #49 on: January 08, 2013, 06:50:18 PM »
Ok, I deleted it and created a new one with the same name.  Looks like data is still there from before 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 Paul

  • Administrator
  • double
  • *****
  • Posts: 3495
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Finishing up the final pieces
« Reply #50 on: January 08, 2013, 06:59:40 PM »
Nice that you have the other version for direct comparison.

Interestingly, there really isn't any difference in the code that wasn't there before.  All Sven added was external project files that are not used in the Android build.  Problem must be either in the config file (possibly a version) or in the core attach plug-in.  I'm digging a little deeper to track it down.
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: Finishing up the final pieces
« Reply #51 on: January 08, 2013, 11:01:15 PM »
Implementing the cheats/CRC caching stuff is mostly done, but not yet ready for publication.
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: Finishing up the final pieces
« Reply #52 on: January 12, 2013, 05:33:29 PM »
Can't seem to get the multi-choice cheats to persist.  The basic reason is that OptionsCheckBoxPreference extends from CheckBoxPreference, which persists a boolean.  And we need it to be an int of course.  Basically the child class is fighting with the parent, and whoever tries to persist second generates an FC crash.  Tried a bunch of workarounds so that the implementation can stay largely unaltered (nice implementation by the way!) but no luck.

I'll try writing a unified CheatsPreference that merges the two that you wrote, to handle boolean as well as multi-choice under the same hood.  And long-clicking of course.  With all the practice I've had this week debugging custom preferences, I'm finally getting a sense for the preference lifecycle, so it shouldn't take too long now.

If you can think of higher-priority issues, let me know.  I can't think of any off the top of my head.
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: Finishing up the final pieces
« Reply #53 on: January 12, 2013, 06:08:03 PM »
I think everything appears to be shaping up.  I'm mainly looking at the GS3 issue and the OUYA port right now, and I'll add devices to the hardware profiler as the data is reported.
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: Finishing up the final pieces
« Reply #54 on: January 12, 2013, 11:58:08 PM »
All cheats persist now.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version