Jump to content
LaunchBox Community Forums

f00tf00t

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by f00tf00t

  1. @Jason Carr

    I rasied a similar case to the Daijishou team

    https://github.com/magneticchen/Daijishou/issues/236#issuecomment-1487607686

     

    to which their fix was implementing pure uri launching (I've tested this on SD card and CIFs and they both work on Daijishou frontend, can this be something that can be implemented into Launchbox Android to fix the issue here on thisapp?

  2. Hi there,

     

    The way to make CIFs/SMB/NAS access work natively to an android phone is by using two third party apps:

    Server side

    LAN drive - SAMBA Server & Cli

    https://play.google.com/store/apps/details?id=fr.webrox.landrive&hl=en&gl=US&pli=1

    This app is straight forward; you can set the internal directories and/or external storage to usernames/passwords to what the usernames are allowed to access remotely

    or

    Servers Ultimate

    https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate&hl=en&gl=US

    Same as LAN Drive, more complex/flexible but you cannot set external storage

     

    Client side

    CIFS Documents Provider

    https://play.google.com/store/apps/details?id=com.wa2c.android.cifsdocumentsprovider&hl=en&gl=US

    Simple interface and configuration and most importantly is 100% native to the android OS and file system so you can use most emulators (still trying to work out retroarch) to access any remote file via the emulator

     

    or

    RCX - Rclone for Android

    https://play.google.com/store/apps/details?id=io.github.x0b.rcx&hl=en&gl=US

    Same as CIFS DP, with more features

     

    Having any of the above two combinations of server and client setup works however, Launchbox android doesn't give the ability to natively/flexibly select any directory (by way of the android OS file system browser), once that feature been added in for mobiles/tabletsa user will be able to use remote files to load into the emulators (via Launchbox android).

     

    With the above setup I can confirm the following emulators work with SMB/NAS setups:

    AetherSX2

    Duckstation

    Dolphin / Dolphion MMJR1 and MMJR2

    PPSSPP

     

     

     

     

     

     

     

     

  3. Hi @Jason Carr,

    I found information on the issue at hand:

     

    What we know

    Class Name
    paulscode.android.mupen64plusae.AppMupen64Plus < -- We know this to be correct as we can verify when installed

    App Name
    org.mupen64plusae.v3.fzurita.pro <-- with the app installed we know this correct as wel,l as we can verify when installed

    Activity Names / Activity Class Names
    paulscode.android.mupen64plusae.SplashActivity           <-- // When the game is loading ("Preparing game data...") see screenhot, same app name Daijisho uses ! With execptions * !

    hZklVqA.png

    and
    paulscode.android.mupen64plusae.game.GameActivity <-- // Game that's running / currently active

     

    When I configure a custom emu to launch a rom I tried first with "SplashActivity"

    NlN5D3m.png

     

    and I get the following error

    gGu01gD.png

    I have specified the acivity (SplashActivity) but I don't know what the intent is configured as.

     

     

    When I configure for "GameActivity"

    nkB5U9K.png

     

    I following error

    WQniUGZ.png

     

    Which shows the correct intent action, however I would like to know if this can be set to 'Launch' to see if we get the same error

     

    Lastly;


    How can I get access to the Launchbox manifest.xml file to review the below

    Also, I was reading through an stack overflow thread:
    https://stackoverflow.com/questions/37731315/android-content-activitynotfoundexception-unable-to-find-explicit-activity-clas


    stating the below...


    You're instantiating the intent before the activity has gone through its life cycle methods. This means that the Context that you pass in to the Intent constructor is not valid.

    Typically, the intent is created right before you use it:

    newEvent.setOnClickListener(new View.OnClickListener() {
        @Override
        public void onClick(View v) {
            Intent intent = new Intent(MainMenu.this, EventCreationActivity.class);
            startActivity(intent);
        }
    });


    This is also something I want to explore so I can look into providing a fix the emulator launching problem, based on the error I hoping this is what the issue is, in failing that I would like to check the manifest file to see if the mpen64 full app name was stated or not.

     

    Also, If there's anything else I can do to assist, I'm morethan happy to do so.

    Thank you

     

     

     

     

  4. Hi all,

    As per the title; I'm not able to launchbox PS2 ROMs via luanchbox that are on SD-Card (Ext' Storage), however ROMs that are on the device storage (locally) work with no issue.

    Below are the steps I checked to see what was going wrong

     

    1 - The ROM is on the SD card

    oYmtevH.png

     

    2 - ROM info (directory and file name)

    p4XEAce.png

     

    3 - AetherSX2 and the ROM listed

    eLMUKRn.png

     

    4 - I launched the ROM from AetherSX2 and it worked with no issue (see the below log - I removed a chunk of the debug data and just included the the emu' showing the ROM file being  called and ran

    *******************************************

    [    4.3855] GetDisplayNameForUriPath("content://com.android.externalstorage.documents/tree/169B-DB0D%3A/document/169B-DB0D%3AGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso") -> "Grand Theft Auto - San Andreas (USA).cso"
    [    4.3869] Opening CDVD...
    [    4.3891] GetDisplayNameForUriPath("content://com.android.externalstorage.documents/tree/169B-DB0D%3A/document/169B-DB0D%3AGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso") -> "Grand Theft Auto - San Andreas (USA).cso"
    [    4.4019] Preparing for a 1920x1080 window
    [    4.4204] isoFile open ok: content://com.android.externalstorage.documents/tree/169B-DB0D%3A/document/169B-DB0D%3AGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso
    [    4.4204]     Image type  = DVD
    [    4.4205]  * CDVD Disk Open: DVD, Single layer or unknown:
    [    4.4205]  * * Track 1: Data (Mode 1) (2197152 sectors)
    [    4.4208] Opening GS...

    [    4.5345] (AAudioMod) Creating stream...
    [    4.6834] (AAudioMod) Starting stream...
    [    4.6941] Opening PAD...
    [    4.6942] Opening DEV9...
    [    4.7008] Opening USB...
    [    4.7008] Opening FW...
    [    4.7010] McdSlot 0 [File]: /storage/emulated/0/Android/data/xyz.aethersx2.android/files/memcards/Mcd001.ps2
    [    4.7011] McdSlot 1 [File]: /storage/emulated/0/Android/data/xyz.aethersx2.android/files/memcards/Mcd002.ps2
    [    4.7041] EE/iR5900-ARM64 Recompiler Reset

    [    5.0254] (SYSTEM.CNF) Detected PS2 Disc = cdrom0:\SLUS_209.46;1
    [    5.0254] (SYSTEM.CNF) Software version = 1.03
    [    5.0254] (SYSTEM.CNF) Disc region type = NTSC
    [    5.0884] found 0 symbols
    [    5.0892] ELF (cdrom0:\SLUS_209.46;1) Game CRC = 0x399A49CA, EntryPoint = 0x00100008
    [    5.0912] (SYSTEM.CNF) Detected PS2 Disc = cdrom0:\SLUS_209.46;1
    [    5.0913] (SYSTEM.CNF) Software version = 1.03
    [    5.0913] (SYSTEM.CNF) Disc region type = NTSC
    [    5.8569] (UpdateVSyncRate) Mode Changed to DVD NTSC.

    *******************************************

     

    5 - Screenshot of the game running on AetherSX2 with no issue via SD-Card

    LpRy80Y.png

     

     

    Moving over to Launchbox (the version I'm using is 1.8)

    6 - Below is a screenshot of where Launchbox sees the ROM

    c4llb1M.png

     

    7 - When trying to open the ROM via Launchbox AetherSX2 gives an error

    Lx1beN4.png

     

    8 - When I checke the AetherSX2 log I see the following

    [  470.7284] ReportErrorAsync: Error: Requested filename 'content://com.android.externalstorage.documents/tree/a_rw%3A%2Fmnt%2Fmedia_rw%2F169B-DB0D/document/a_rw%3A%2Fmnt%2Fmedia_rw%2F169B-DB0D%2FGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso' does not exist.
    [  470.7458] Skipping surface prepare event due to system being shut down.

     

     

    9 - Where I compare the two log files I see the following

    Working

    GetDisplayNameForUriPath("content://com.android.externalstorage.documents/tree/169B-DB0D%3A/document/169B-DB0D%3AGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso")

     

    NOT working

    ReportErrorAsync: Error: Requested filename 'content://com.android.externalstorage.documents/tree/a_rw%3A%2Fmnt%2Fmedia_rw%2F169B-DB0D/document/a_rw%3A%2Fmnt%2Fmedia_rw%2F169B-DB0D%2FGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso' does not exist.

     

    10 - When breaking down where the failue is (highlited bold)

    content://com.android.externalstorage.documents/tree/169B-DB0D%3A/document/169B-DB0D%3AGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso

    'content://com.android.externalstorage.documents/tree/a_rw%3A%2Fmnt%2Fmedia_rw%2F169B-DB0D/document/a_rw%3A%2Fmnt%2Fmedia_rw%2F169B-DB0D%2FGrand%20Theft%20Auto%20-%20San%20Andreas%20(USA).cso

     

    I think Launchbox is presenting a slightly off kilter directory to AetherSX2, its probably a correct way of presenting the directory/file however its not a method that AetherSX2 likes.

     

    If anyone else has had this problem, please do let me know how I can fix this.

     

    Thank you

     

     

     

     

     

     

     

     

     

     

     

     

  5. Hi there,

    Can anyone point me in the right direction for the application Lightspeed Mamelister please?

     

    I've clicked on all the links I can find on the thread for where dev work was being done on the application, but all are giving me 404s!

     

    Any help will be great.

     

    Thank you

×
×
  • Create New...