Author Topic: Version 2.0 Release Candidates  (Read 51674 times)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #45 on: January 10, 2013, 12:57:51 PM »
Game tested Mario 64.
Devices tested on: Xperia Play, Samsung Galaxy S2.

Code: [Select]
e.android.mupen64plusae/error.log, error message: /mnt/sdcard/Android/data/paulscode.android.mupen64plusae/error.log (No such file or directory)
W/dalvikvm(  937): threadid=11: thread exiting with uncaught exception (group=0x2aac8578)
E/ACRA    (  937): ACRA caught a NullPointerException exception for paulscode.android.mupen64plusae. Building report.
D/CustomizationProvider(  850): openFile -- START uri=content://com.sonyericsson.provider.customization/settings/com.sonyericsson.textinput.uxp
I/CustomizationProvider(  850): No configuration file: /system/etc/customization/settings/com/sonyericsson/textinput/uxp/custom_settings.xml
D/dalvikvm(  937): GC_CONCURRENT freed 1716K, 55% free 3460K/7559K, external 4678K/5428K, paused 7ms+13ms
I/ACRA    (  937): READ_LOGS not allowed. ACRA will not include LogCat and DropBox data.
D/ACRA    (  937): Writing crash report file 1357843249000.stacktrace.
D/ACRA    (  937): About to start ReportSenderWorker from #handleException
D/ACRA    (  937): Mark all pending reports as approved.

A couple interesting things about that crash.  Firstly, the obvious error is that error.log doesn't exist.  That should be a simple fix, I would think, unless there is something weird going on with the paths.  Secondly, there is the question of why it was trying to access the error log.  This Probably means there was another problem that it was trying to log but wasn't able to.  We'll most likely have to fix the first problem before we'll be able to solve the second one.

Does the problem happen when the cheats options have been loaded into the menu, or before (or both?)
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 zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Version 2.0 Release Candidates
« Reply #46 on: January 10, 2013, 01:19:13 PM »
Yup, odd.

I am not setting any cheats so unless mupen is imposing some I guess not :)
I haven't had chance to dig into the code much yet, had a look at rice today and I believe I fixed some graphical issues. Of course I can't be certain until I can run it again ;)

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #47 on: January 10, 2013, 01:24:56 PM »
Excellent!  Been wanting to work on Rice, but tend to get swamped with other things.  Really greatful for the help!
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 zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Version 2.0 Release Candidates
« Reply #48 on: January 10, 2013, 01:33:52 PM »
Your welcome :)

Let me know when you are ready for me to test again and we will see if we can nail this issue.

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #49 on: January 10, 2013, 02:34:57 PM »
Ok, I did a little digging, and the only place I can find that would print a message like the one in the first line of your log (which is cut off, by the way  :P), is in persistent/ConfigFile.java, in the save() method:

Code: [Select]
    public boolean save()
    {
        // No filename was specified.
        if( TextUtils.isEmpty( mFilename ) )
        {
            Log.e( "ConfigFile", "Filename not specified in method save()" );
            return false;   // Quit
        }
       
        // No config data to save.
        if( mConfigList == null )
        {
            Log.e( "ConfigFile", "No config data to save in method save()" );
            return false;   // Quit
        }
       
        File f = new File( mFilename );
       
        // Delete it if it already exists.
        if( f.exists() )
        {
            // Some problem deleting the file.
            if( !f.delete() )
            {
                Log.e( "ConfigFile", "Error deleting file " + mFilename );
                return false;   // Quit
            }
        }
       
        try
        {
            FileWriter fw = new FileWriter( mFilename );  // For writing to the config file

            // Loop through the sections
            for ( ConfigSection section : mConfigList )
            {
                if( section != null )
                    section.save( fw );
            }

            fw.flush();
            fw.close();
        }
        catch( IOException ioe )
        {
            Log.e( "ConfigFile", "IOException creating file " + mFilename + ", error message: " + ioe.getMessage() );
            return false;  // Some problem creating the file.. quit
        }
       
        // Success
        return true;
    }

It seems that an IOException was thrown and it returned false.  This was not handled properly from wherever it was called, resulting in a NullPointerException, which caused the crash.

Anyway, actually looking at the code, I'm not sure why this code doesn't work for you.  Notice that we delete the file:

Code: [Select]
        if( f.exists() )
        {
            // Some problem deleting the file.
            if( !f.delete() )
            {
                Log.e( "ConfigFile", "Error deleting file " + mFilename );
                return false;   // Quit
            }
        }

Then we point a new FileWriter to it (which should recreate the file since it no longer exists):
Code: [Select]
            FileWriter fw = new FileWriter( mFilename );  // For writing to the config file

            // Loop through the sections
            for ( ConfigSection section : mConfigList )
            {
                if( section != null )
                    section.save( fw );
            }

Only a couple of things I can think of that would cause this.  Either your device doesn't follow normal Java behavior to create the file with FileWriter if it doesn't exist, or there is something wrong with the path to the file.  Since you are building from source, you can check if the former is the case pretty easily.  Just add the following line before FileWriter fw = new FileWriter( mFilename );
Code: [Select]
new File( mFilename ).createNewFile();
If that doesn't fix the problem, check the logcat again to see if the error message changed at all.  To check if paths are the problem, make sure /mnt/sdcard/Android/data/paulscode.android.mupen64plusae/ actually exists on your device.
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 zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Version 2.0 Release Candidates
« Reply #50 on: January 10, 2013, 03:53:16 PM »
Tried that, didn't get me any further.

However I did get a better output from adb for you this time.
A lot of errors going on, seems like it's not loading any of the libs and is crashing on trying to read the game header.

Just an fyi.

Xperia play is on stock 2.3 firmware.
Galaxy S3 is on 4.0.3 Custom.

The public version of mupen 64 plus ae works fine on both devices.

Crash log (forum wouldn't let me post it even though it is only 80ish lines :P )

Code: [Select]
http://pastebin.com/MHFbqWvW

EDIT: If you have no joy with this I can start digging on saturday. You will naturally be able to track it down faster than I will right now as your a lot more familiar with the source. So i'm hoping you beat me to it ;) . I want to push in some rice stuff on sunday so working this out is a high priority :)

Thanks Paul
« Last Edit: January 10, 2013, 04:11:07 PM by zack »

Offline karl_87

  • byte
  • *
  • Posts: 19
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #51 on: January 10, 2013, 05:00:57 PM »
Emulator works great on my Archos Gamepad, and the buttons seem to map well - good job! but for some reason when I play Zelda - Ocarina of Time, it suffers from massive black flickering backgrounds, if i change the video plugin to the other one, the problems seem to stop but the framerate is so low its unplayable, not sure if this is specific to my device or i haven't got something setup correctly? any ideas? cheers for the work so far

I know of a couple settings that can cause flickering in Zelda.  One is Tribuffer Opt, which is currently hardcoded so you can't turn it off at the moment.  The other is Hack Z.  I think it shows up in the gles2n64 video settings as "Depth Test" or something.  You could try checking/ unchecking that option to see if it helps gles2n64.

For gles2rice, you could try enabling Auto Frameskip to help speed it up (generally works for Zelda OOT, but not a lot of other games -- will crash some devices).

Some folks have also reported that using the "Exactly" Frameskip options (gles2n64 video settings), for example "Exactly 1", can greatly improve speed.  Might be worth a try.  Also, it has been reported for some devices that enabling Stretch Screen (both video plug-ins) improves speed a little.  Also see if there is any difference using the framelimiter setting (both plug-ins).  You could really tinker around with all the settings though to see what helps on your particular device.  If you find a good profile of settings, please post them here for other users with similar devices to try.

i tested zelda oot today, have some glitches too, the walking path keep flickering in black, tested with both plugins.
Could you also try the Hack Z setting (called "Depth Test in" in the menu I believe)?  Could you also test Mario 64 and see if the shadows are missing, flickery, or floating way far off the ground?  That could indicate a problem with polygon offset, which can also cause flickering.

Also, the sound is choppy  :(
Choppy sound means slow emulation (for many devices this happens most noticeably during the cutsceens, in the forest with all the fairies, and in the large open-field).   Could you try playing with the settings as well (in particular the Frame Skip options), and report what settings you used if you are able to improve performance?

Hi Paul, got gles2rice working at good speed by turning on autoskip like you said, but the graphics are now flickering just on the floor like the other guys. Went through every option including what you said, nothing seems to improve for this game :(

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #52 on: January 10, 2013, 08:27:01 PM »
A lot of errors going on, seems like it's not loading any of the libs and is crashing on trying to read the game header.

Is that the APK you built, or the one from here on the forum?  I was thinking if it was yours, you might not have built the native libraries before building the APK.  If it's the one from here, I have no clue why it would be unable to load any of the libraries.  Same type of error log on both your devices, or just the GS3?
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: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #53 on: January 10, 2013, 10:47:15 PM »
Posted Release Candidate 2.  This one is looking pretty good..
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: Version 2.0 Release Candidates
« Reply #54 on: January 10, 2013, 11:21:00 PM »
I also had force close issues on my xplay, but only with touchpad enabled.  Report logged on bugsense.  Issue was the dreaded failure to load lib again.  In this case the xplay lib.
2012 Nexus 7, rooted stock Lollipop
Samsung Galaxy Victory, rooted stock Jelly Bean
Xperia PLAY, stock Gingerbread
OUYA, retail version

Offline jack111

  • byte
  • *
  • Posts: 21
    • View Profile
Re: Version 2.0 Release Candidates
« Reply #55 on: January 11, 2013, 01:28:16 AM »
When can we expect a change log between the market version and the upcoming one

Offline zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Version 2.0 Release Candidates
« Reply #56 on: January 11, 2013, 06:14:07 AM »
Hey Paul.

I was indeed forgetting to run ndk-build. Egg on my face. However the issue remains.

With the RC2 you posted I get a force close when it starts to build/list the available cheats.

New crash log (via pastebin below):

http://pastebin.com/Kcp9vvas
« Last Edit: January 11, 2013, 06:28:01 AM by zack »

Offline Paul

  • Administrator
  • double
  • *****
  • Posts: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #57 on: January 11, 2013, 06:25:36 AM »
Same deal? (unable to load the libraries?) This sounds like a pretty serious problem, so I think I'll delay publishing for a couple days until we track it down just to be safe.
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: 3499
  • Developer
    • View Profile
    • PaulsCode.Com
Re: Version 2.0 Release Candidates
« Reply #58 on: January 11, 2013, 06:28:26 AM »
When can we expect a change log between the market version and the upcoming one

I'll post one on the Beta Testing has Begun thread when I publish the app (probably early next week), and the changlog link will point to 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 zack

  • Developer
  • byte
  • *****
  • Posts: 36
    • View Profile
    • InfuseDreams
Re: Version 2.0 Release Candidates
« Reply #59 on: January 11, 2013, 06:29:59 AM »
It's a different story this time.

http://pastebin.com/Kcp9vvas

Seems to be related to the xperia touchpad library (same thing littleguy reported) this time.