GameGuardian official help

[Enyby]

We start official help here.

Because English is not my native language it is translated with Google Translator with some manual edits.

Source written on Russian.

 

With time we plan integrate this help inside the app.

[Enyby]

So, let's go in order.

After the first run, GameGuardian will launch its own installation. During this installation, the application data will be replaced by random ones to prevent detection by anti-cheats.

This installation can be canceled, but it's best not to do it.

During this installation, there will be several requests for root rights to perform all without user interaction. If these requests are rejected, then the installation will be accompanied by system requests for the approval of the installation of the new apk.

 

This installation only occurs once.

 

After the initial installation is complete, the application will be launched and you will see the start screen with a quick guide and a few buttons.

Also some dialogs may appear: an old version was found, a new version was found, a restart is needed to apply the settings and so on.

Usually in these dialogues everything is extremely simple and understandable, so we will not dwell on them.

 

So, we're on the start screen. Most of which is occupied by a scrolled field with a brief guide. It is highly recommended to read it before moving on.

The header shows the version of the application and the build number. Also, there are several buttons at the bottom of the screen. Let us dwell on them in more detail.

I will describe the English interface as the most commonly used. In the application settings, which will be described later, you can select almost any language for the interface.

Exit - the exit from the application. Immediately ends the application, completely unloading it from memory.

Donate - will open the donation page on the official website in the default browser.

Verification - will launch a test to display floating windows on the screen. The test includes outputting a color block to the screen and transferring a click to it. At the end of the test, a toast with results will be displayed.

Fix it - call the menu for various fixes. There are various options that will help in working with the program on different firmware.

Start - starts the application, displaying a floating icon and hide, if possible, the start screen.

 

Let's return to the menu Fix it. After clicking this button, a menu appears in which you can make some settings. For example:

- enable or disable the use of floating windows;

- work with SELinux enabled or disabled;

- select a type for floating windows or reset it to default;

- to switch the use of notifications;

and so on.

The list is constantly replenished, tomorrow some other items may appear in it.

After selecting any item, the selected setting is applied and application restarted.

In some cases, additional parameters may be requested.

For example, when choosing the type of floating windows, multi-colored squares will be displayed on the screen with different types of floating windows. Selecting one of them will save the setting.

This way you can force the system to display a floating icon on top of the lock screen. However, in the interface, there may be problems.

 

In most cases, if your application is working properly, you do not need to visit this menu. It is designed to fix problems if something goes wrong. For example, the application crashes, the icon does not appear after pressing the start button and so on.

 

Let's move on to working with the application. You pressed the Start button. At the same time, a floating application icon appeared on the screen, and the start screen was closed.

If you have enable some fixes, for example, floating windows are disabled, then the behavior may differ in some details, for example, the start screen will not close, but these are irrelevant trivia. In the future I will consider standard behavior without any hacks, only occasionally noting some of them.

 

Return to the icon. This is one of the main modes of the application. The icon is called floating for a reason. You can take and drag it to any place on the screen.

When you click on the icon, the main application interface will be displayed. This is the second main mode of the application.

 

The interface is displayed in a semi-transparent dialog above the game window. At the top there is an icon of the selected game, from left to right, four tabs for tabs and a button for hiding the interface.

Immediately after the first start, the process selection dialog will automatically open for you to work. Choose your game there.

 

So, back to the interface. It consists of 4 tabs: settings, search, saved list and memory editor.

The close button of the interface, located in the upper right corner, closes the interface, returning us to the floating icon mode.

Clicking the icon of the selected process in the upper left corner opens the dialog for selecting the process.

If a small application icon is displayed on top of the process icon, it means that the application has connected to the selected process for performing some actions.

 

At the bottom of the screen is a status bar. It displays some useful information and an eye button, which makes the entire interface transparent.

Let's consider the information that is here in more detail.

1. The version number of the application.

2. The status of the demon. If the daemon is up and running, there will be a "+" sign. If it's not running, then something else, like "?".

3. List of active memory regions, in brief form. When you click on the status bar, a dialog for selecting memory regions opens.

4. The number of checked items in the list on the active tab.

5. The amount of free memory in megabytes, according to the system and according to android.

6. The eye icon. If you click on it and hold, then the entire interface becomes transparent and you can see what's under it. The eye icon works almost everywhere, including the search progress dialog.

[Enyby]

 

The rest of the elements depend on the selected tab.

If the first tab (settings) is selected, the main part of the screen will be occupied by the list of settings.

All other tabs will have two panels. Their content is slightly different and may depend on application settings.

On the narrow top panel, the following is normally displayed (from left to right): the game pause button, the pid of the selected process and its name, the amount found (only on the search tab), the menu button (if the toolbar is disabled on this tab) and the list update button.

By the name of the process, you can click - this will open the dialog for selecting the process.

Click on the number of found opens the filter dialog.

Below is the toolbar with quick action buttons. It can be hidden, through the settings of the application, for each tab separately.

The rightmost button in the toolbar is the menu button. It shows a complete list of possible actions. The first actions are displayed on the toolbar itself. All that is not fit - hiding.

In the application settings, you can specify the algorithm for filling the toolbar with buttons: from the right edge (default), from the left edge and from the center.

If you do not know the purpose of any icon - press the menu button and see the text description for each icon.

 

Under the toolbar is a list of items. For each tab, it has its own: search - search results, saved list - list items, memory editor - memory contents.

 

Let's consider each tab in more detail.

Let's start with the settings tab.

Here is a list of all available settings for the application, as well as some actions. The list is regularly updated and expanded.

There are such items:

1. Help. Runs the application's built-in help.

2. Donate. Opens the browser with a donation page on the official website.

3. Select process. Opens the game process selection dialog. Can be invoked by clicking on the process name or the game icon.

4. Exit. The application exit.

5. Kill the game. Kills the selected application by calling the system call 'kill'. Can lead to loss of game data, since this close is forced.

6. Select memory ranges. Opens the memory regions selection dialog.

Memory in the processes of android is allocated by blocks, some of which are marked in a special way. In this dialog, you can select the categories of memory blocks that will be used when searching for values.

Most regions have common names, so you can get more information by typing their name into a web search.

 

Java heap - the main Java memory.

C++ heap - main memory for native code.

C++ alloc - dynamic allocation of memory in native code.

C++ .data - pre-initialized memory in native code.

C++ .bss - memory initialized by zeros in the native code.

PPSSPP - PPSSPP emulator memory, which contains the game.

Anonymous - regions of memory without description - there can be anything data.

Java - system regions of Java memory, are usually not needed, since they do not contain user application data.

Stack - memory of the native code stack. Usually not needed, because it contains very rapidly changing local data. Sometimes applications use this memory to store long-term values, but this is considered bad practice and is practiced very rarely.

Ashmem - shared memory - can sometimes be used by applications for user data, but this happens rarely.

Other (slow) - all other regions of memory that are available for reading and writing, but not in other regions. The use of these regions can help in certain situations, but in most cases they are not needed. In addition, they are quite large and some of them have slow access, which leads to a strong slowdown in search.

If you find values in this group of regions, you need to write the region log when there are such values found, and send it to us so that we improve the definition of regions.

Bad - "bad" regions of memory, which can not exactly contain useful data for hacking. For example, an accelerator video buffer, system fonts and so on. Can very slow down the search.

On some firmware, the use of these regions can lead to freezes or reboots.

Code app (dangerous) - the code of the application. Changing this memory can corrupt user data.

Code system (dangerous) - the code of the system libraries. Changing this memory can corrupt user data.

 

Regions that are marked as (slow) can greatly slow down the search.

Changing the memory in (dangerous) regions can lead to application crashes and data corruption.

 

7. Autpause game. Automatic pausing of the game process when opening the GG interface. It can be useful in dynamic games, as well as to bypass simple defenses. If you hide the GG interface, the game will resume.

8. Freeze interval. Interval, in milliseconds, overwriting the values ??in the memory of the game when freezing. The whole point of freezing the value in the memory of the game comes down to the fact that GG very often rewrites the value in the memory of the game. There is no other way to freeze the value. Small values can lead to increased CPU usage, heat and battery consumption.

9. Saved list updates interval. The interval for updating the values ??in the saved list. Small values can lead to increased CPU usage, heat and battery consumption.

10. Data in RAM. Storage of search data in memory. You can select a specific amount of memory. All that more will be stored on the disk.

Usually the best option is to choose Yes if you have enough memory. This does not mean that the entire device memory will be used. If there is a shortage of memory, the data will be flushed to disk, regardless of what is selected here.

This option can greatly speed up the search, however, in x86 emulators, using RAM can, on the contrary, slow down the search.

Usually the data is quite large, so the choice of 5-20 MB does not change anything. The difference, usually, can be seen from 100 MB and above.

11. Language (Language). Select the language of the application. This setting item always has an English version of the name so you can find it even if you select a language that you do not know or for which there is no font on your system.

This setting requires the application to be restarted. If this is not done, then some of the dialogues will remain in the previous language.

Almost all of the language options are available in the application.

12. Speedhack: Reset on exit. Reset speedhack when exiting from the application. If disabled, then when you exit from the application, the reset will not happen and the game will remain accelerated or slow. To change the speed in the game again, you will need to run GG again.

13. Speedhack: List of speeds. Edit speed list of the speedhack. It is at these speeds that the speedhead switches, when you press the left / right arrows.

14. Speedhack: List of speeds. Specifies the behavior when processing list of the speeds. Available options:

Nothing - there is no processing, that is entered into the list, it will be.

Sort - the list is sorted in ascending order.

Sort and remove duplicates - the list is sorted in ascending order, and duplicate values are deleted.