Login with host device

1. Select the settings screen.
2. Tap the Login button.
3. Follow the login screen to log in.

Setting the Event ID

1. Click the up arrow icon on the right to open the panel.
2. Create an original name and enter it as the event name.
   After registration, you can select it by pressing the registration list button.
3. Press the Register button.
4. Start accepting player registrations.

Register at the player device

1. Login as with host device.
2. Switch to player mode.
3. Ask the host to tell you the event ID and enter it.
4. Tap the Register button.
   After registration, you can select it by pressing the registration list button
5. By turning on notification reception, the data of the event ID can be referenced, and if notification is available, update notifications will be received and the data will be automatically updated at that timing.

Information Sharing

1. On the host device (blue toolbar), click the Update button to upload the data to the cloud database.
2. On the player device (green toolbar), click the Update button to download the data from the cloud database, which will copy the data from the host to the player.
3. A push notification will be sent to the registered players at the timing when the host device registers the data in the database. The application will then automatically perform the same action as pressing the update button on the player's device to update the database.

1. Tap the court number on the match list screen.
2. A dialog will pop up asking you to select the winning team.
3. Tap the winning team.
4. A subtraction is a state in which both crowns are colored. You can return to the unentered state by touching them again.
5. Tap OK to confirm the result.

• It is a good idea to agree beforehand on what kind of situation is considered a win/lose/draw.
• The order of entry is optional, but the rate will be calculated as if the matches were played in order from the first round.

• The initial value of the rate is 25.0 (8.33), where 25.0 is the average rate (µ) and 8.33 is the standard deviation (σ). 25.0 indicates strength and 8.33 is the number indicating the amount of variability.
• A rate is simply a relative value within an individual group that indicates how likely it is to win a match.
• A larger rate = stronger in a general meaning.
• If we assume that the degree of variation follows a normal distribution, we can estimate the degree of accuracy as shown in the graph. This is an illustration of the initial values, so the variability is very large.
• Initially, it fluctuates greatly, and with each game, μ rapidly approaches its true value. The amount of fluctuation is not constant. For example, beating an opponent with a relatively strong rate value will result in a larger increase.

A practical example will be given to illustrate how the rates differ.

• Panda and Tiger both won one game and lost one game, but there is a difference in rating between Panda at 24.9 and Tiger at 25.1. Panda won the first round against a pair with a rating of 25.0+25.0=50.0 and lost the second round against a pair with a rating of 28.1+21.9=50.0. Tiger lost in the first round to a pair with 25.0+25.0=50 and won against a pair with 25.0+28.1=53.1.
• The value of a loss is the same, but in the case of a win, the opponent's rate is higher for the tiger. This is one of the reasons why the tiger's rate is valued higher. However, in the case of doubles, it is not so simple because the partner's rate is also affected and its contribution to the win/loss is distributed. In this example, the second round was 25.0 + 28.1 = 53.1 vs. 28.1 + 21.9 = 50.0, but the low-rated frog and tiger team won, so it is worthwhile.
• If you are interested in the details of the calculation method, try searching for the keyword "Trueskill".

List of differences in status statements

Status	Continuation between rounds	Counting to the number of times the draw was missed
	Continue	It counts when the draw results break.
	Continue	It counts, but it's not usually a break.
	Does not continue	It counts. It is always a break.
	Continue	It counts. It is always a break.
	Continue	Does not count.

1. The first step is to determine the winners who will play. Candidates will be those who are registered and are not on break or absent status.
2. It favors those who have low odds of winning in the past and disadvantages those who have high odds of winning in the past. The highest priority is to equalize everyone's chances of winning.
3. Discourage long breaks by slightly favoring those with the highest number of consecutive breaks and slightly disadvantaging those with the highest number of consecutive entries.
4. Slightly favor those with fewer appearances.
5. Select people to participate in play in order of priority. If they have the same priority, they will be selected randomly. If the pairs are fixed, the average value is used to draw lots.
6. Next, pairing is done. For those who have a fixed pair, the pair is decided, and for those who do not have a fixed pair, the pair is randomly combined and multiple candidate patterns are generated internally. The number of past pairings is counted, and the combination with the fewest number of pairings is selected, so that people with different or fewer pairings are paired as often as possible.
7. If the "Balance the rating" is on, the game will try to pair up opponents based on their ratings so that the win rate is not too skewed. When the "Balance the rating" is off, the game will try to pair up opponents with the least possible bias.

• In the case of an absent status, the participant is 100% unsuccessful, but is hypothetically considered to have won or lost based on the average probability of all participating members except the absent participant. This way, absence is neither an advantage nor a disadvantage. A slight advantage in terms of zero consecutive entries and a slight disadvantage in terms of fewer entries will result in entry in many cases when returning from an absence.
  The idea behind this software is that the odds of winning are the same = fair. If you want to think that the number of winning times is the same = fair, please set the rest state to be unsuccessful every time.
• As an exception, if the number of playable members is N, and the number of playable members is within the range of N±1/3 (rounded down), N/3 (rounded up) members will be shuffled by swapping the playable and resting members. This is to avoid alternating the same person instead of allowing continuous breaks.
• Gender combination constraints such as "Mixed" or "Balanced", participant status set to "must play", resting and finishing players in the previous round in the case of "one court at a time draw", and exclusive pairs will take precedence over priority selection.

1. On the old device Save to cloud on the Backup screen.
2. Log in with the same account on the new device and load from the cloud on the Backup screen.
3. The data on the player screen, the match screen and the register screen are transferred to the new device.

1. Settings should be made for one of two groups for all participating players. The number of players in each group must be sufficient to fill the court; for two sides, two pairs are needed, so a minimum of four players is required.
   
2. Set the conditions for a group competition.
   
3. A match table is generated by pressing the draw button.
   

• Fire OS can also work by installing this application from the Google Play Store. (Please check the installation method by yourself.) However, the following functional differences exist.
  • When the player mode device is Fire OS, automatic updates cannot be performed by notification of data updates from the host. (Manual updates can be performed using the icon in the top right corner)
  • The function for viewing draw results in the browser (Web Share) does not allow automatic updating by notification from the host. (Manual updates via the display button are possible).
  • If the host mode device is a Fire OS, the data of the host mode device is not updated even if the match results are entered on the player mode device and sent to the host.
• Although the app cannot be installed on iOS, a function for referencing draw results in a browser (Web Share) is available. However, there is an operating system restriction in iOS that message notifications can only be received by native apps, resulting in the following functional differences.
  • Automatic update by notification from the host device is not possible with the function to view draw results in the browser (Web Share). (Manual update via the display button is possible).
• Even if it looks Android at first glance, the internal implementation may be incompatible or there may be restrictions on the prerequisite communication.
  • The messaging mechanism must be compatible with Firebase Cloud Messging and must be able to communicate with the Firebase Cloud Service.Amazon Device Messaging (Fire OS),Apple Push Notification Service (iOS), etc. cannot be notified due to different types.
  • Use of some functions may be restricted on phones that do not have Google Play pre-installed in general and in regions where communication with Google services is restricted.

If the application has been terminated abnormally and cannot be started, it may be possible to start the application by clearing the registration information for participants and the combination results of the match table. To clear the information, press the following button from the target Android device while the app is closed. This will not work while the app is running.

Use only if you cannot start the App.

It may be possible to write back after the application data has been output externally and the data cleared to enable start-up. Try this if there is no data output outside the app or if it may be out of date.

->The output can be copied to the clipboard and written back by selecting it from the 'CB' tab in the 'Register'.


->You can write back by sharing the output file as a zip to the application.

If you are using Android 6.0 or later, the standard Android auto-backup feature will write back automatically backed-up data upon reinstallation. The conditions for automatic backup are as follows, according to Google .

• Backup is enabled on the device by the user.
• At least 24 hours have elapsed since the last backup.
• The device is idle.
• The device is connected to a Wi-Fi network (if the device user hasn't opted in to mobile-data backups).