-
Notifications
You must be signed in to change notification settings - Fork 4
Common Issues FAQ
You need a Windows PC with an Android emulator. Then follow the somewhat quick start: https://github.com/HughJeffner/FFRK-LabMem#somewhat-quick-start
When installing on Windows 8.1 or 10 with Windows SmartScreen enabled, you may see a message indicating that the installer is not recognized by Windows.
LabMem is not “signed” by Microsoft. This message doesn’t mean anything is wrong; rather, it indicates that LabMem is not part of Microsoft’s paid program to validate Windows applications.
By selecting More info, you will be able to select Run anyway to continue the installation.
When downloading and running the released binaries it's possible you may get a warning from windows defender or other antivirus. I think this may be a combination of multiple issues:
- Neither the installer or binary exe is code-signed
- All of the .dll dependencies have been merged into the .exe file
- Downloaded file has the "mark of the web"
All I can do is assure you that the provided binaries were compiled directly from the tagged source
If you successfully enabled USB debugging in the developer mode settings, try using the different ports in the drop-down box in the Adb settings. If none of those work then you can manually type in the port. For example, newer versions of Nox might use port 62025. Also, restarting the emulator may help.
Also, make sure only 1 instance of an emulator is running and no other android devices connected via USB. Opening task manager and killing adb.exe can help clear other connections.
You may experience this issue when using Nox emulator. The problem is mismatched version of adb.exe included with LabMem and the one used by Nox. If Nox issues a adb command the service is restarted and connections to devices are dropped. The fix is to either:
- Find, download, and replace the bot copy of
adb.exewith the one that matches Nox - Locate
nox_adb.exein Nox program files, rename it toadb.exeand replace the bot copy
Make sure you entered the proxy settings in Android, or alternatively enable Auto-configure device system proxy settings via Adb in the bot proxy configuration.
If you can see the screen being tapped but it is in an obviously wrong location then check if your emulator screen resolution is in 'Tablet' mode (for example 1280 x 720) and change it to 'Phone' mode (720 x 1280)
Make sure you retain the rootCert.pfx file in the bot directory. It contains the certificate to be installed in Android and its matching private key. Removing this file will cause it to be re-generated with new values. If you get the warning but FFRK seems to load fine, then you might have a duplicate certificate installed. To remedy this, go into Android security settings and "Clear all credentials" and start the certificate install process over again.
Also, make sure only 1 instance of an emulator is running and no other android devices connected via USB. Opening task manager and killing adb.exe can help clear other connections.
This is just a convenience feature that currently does one of 2 things:
- Tries to start the bot going if enabled in the middle of a lab. It does this by clicking the 'show inventory' button and back to trigger a web request through the proxy
- Tries to start the bot going if enabled on the 'won battle' screen. It does this by clicking the 'skip' button and finishing the battle, triggering a web request through the proxy
This is not possible at this time, but you can right click HE on the stats screen to mark it manually
There's two ways this can happen:
- Forced battle from exploration paintings, there is no way to tell until you open them
- Three combatant paintings on the block list, one is randomly chosen
See #156