The translation is temporarily closed for contributions due to maintenance, please come back later.

Translation

settings_troubleshoot_test_foreground_service_started_failed
English
Notifications Service is not running.
Try to restart the application.
0/690
Key English Japanese State
settings_troubleshoot_test_play_services_success Google Play Services APK is available and up-to-date.
settings_troubleshoot_test_play_services_failed Riot uses Google Play Services to deliver push messages but it doesn’t seem to be configured correctly:
%1$s
settings_troubleshoot_test_play_services_quickfix Fix Play Services
settings_troubleshoot_test_fcm_title Firebase Token
settings_troubleshoot_test_fcm_success FCM token successfully retrieved:
%1$s
settings_troubleshoot_test_fcm_failed Failed to retrieved FCM token:
%1$s
settings_troubleshoot_test_fcm_failed_too_many_registration [%1$s]
This error is out of control of Riot and according to Google, this error indicates that the device has too many apps registered with FCM. The error only occurs in cases where there are extreme numbers of apps, so it should not affect the average user.
settings_troubleshoot_test_fcm_failed_service_not_available [%1$s]
This error is out of control of Riot. It can occur for several reasons. Maybe it will work if you retry later, you can also check that Google Play Service is not restricted in data usage in the system settings, or that your device clock is correct, or it can happen on custom ROM.
settings_troubleshoot_test_fcm_failed_account_missing [%1$s]
This error is out of control of Riot. There is no Google account on the phone. Please open the account manager and add a Google account.
settings_troubleshoot_test_fcm_failed_account_missing_quick_fix Add Account
settings_troubleshoot_test_token_registration_title Token Registration
settings_troubleshoot_test_token_registration_success FCM token successfully registered to HomeServer.
settings_troubleshoot_test_token_registration_failed Failed to register FCM token to HomeServer:
%1$s
settings_troubleshoot_test_foreground_service_started_title Notifications Service
settings_troubleshoot_test_foreground_service_startedt_success Notifications Service is running.
settings_troubleshoot_test_foreground_service_started_failed Notifications Service is not running.
Try to restart the application.
settings_troubleshoot_test_foreground_service_started_quickfix Start Service
settings_troubleshoot_test_service_restart_title Notifications Service Auto-Restart
settings_troubleshoot_test_service_restart_success Service was killed and restarted automatically.
settings_troubleshoot_test_service_restart_failed Service failed to restart
settings_troubleshoot_test_service_boot_title Start on boot 起動時の実行
settings_troubleshoot_test_service_boot_success Service will start when the device is restarted.
settings_troubleshoot_test_service_boot_failed The service will not start when the device is restarted, you will not receive notifications until Riot has been opened once.
settings_troubleshoot_test_service_boot_quickfix Enable Start on boot
settings_troubleshoot_test_bg_restricted_title Check background restrictions バックグラウンド制限の確認
settings_troubleshoot_test_bg_restricted_success Background restrictions are disabled for Riot. This test should be run using mobile data (no WIFI).
%1$s
settings_troubleshoot_test_bg_restricted_failed Background restrictions are enabled for Riot.
Work that the app tries to do will be aggressively restricted while it is in the background, and this could affect notifications.
%1$s
settings_troubleshoot_test_bg_restricted_quickfix Disable restrictions
settings_troubleshoot_test_battery_title Battery Optimization
settings_troubleshoot_test_battery_success Riot is not affected by Battery Optimization.
settings_troubleshoot_test_battery_failed If a user leaves a device unplugged and stationary for a period of time, with the screen off, the device enters Doze mode. This prevents apps from accessing the network and defers their jobs, syncs, and standard alarms.
Key English Japanese State
settings_troubleshoot_test_bing_settings_failed_to_load_rules Failed to load custom rules, please retry.
settings_troubleshoot_test_bing_settings_quickfix Check Settings
settings_troubleshoot_test_bing_settings_success_with_warn Notice that some messages type are set to be silent (will produce a notification with no sound).
settings_troubleshoot_test_bing_settings_title Custom Settings. カスタム設定
settings_troubleshoot_test_device_settings_failed Notifications are not enabled for this session.
Please check the Riot settings.
settings_troubleshoot_test_device_settings_quickfix Enable
settings_troubleshoot_test_device_settings_success Notifications are enabled for this session.
settings_troubleshoot_test_device_settings_title Session Settings.
settings_troubleshoot_test_fcm_failed Failed to retrieved FCM token:
%1$s
settings_troubleshoot_test_fcm_failed_account_missing [%1$s]
This error is out of control of Riot. There is no Google account on the phone. Please open the account manager and add a Google account.
settings_troubleshoot_test_fcm_failed_account_missing_quick_fix Add Account
settings_troubleshoot_test_fcm_failed_service_not_available [%1$s]
This error is out of control of Riot. It can occur for several reasons. Maybe it will work if you retry later, you can also check that Google Play Service is not restricted in data usage in the system settings, or that your device clock is correct, or it can happen on custom ROM.
settings_troubleshoot_test_fcm_failed_too_many_registration [%1$s]
This error is out of control of Riot and according to Google, this error indicates that the device has too many apps registered with FCM. The error only occurs in cases where there are extreme numbers of apps, so it should not affect the average user.
settings_troubleshoot_test_fcm_success FCM token successfully retrieved:
%1$s
settings_troubleshoot_test_fcm_title Firebase Token
settings_troubleshoot_test_foreground_service_started_failed Notifications Service is not running.
Try to restart the application.
settings_troubleshoot_test_foreground_service_started_quickfix Start Service
settings_troubleshoot_test_foreground_service_started_title Notifications Service
settings_troubleshoot_test_foreground_service_startedt_success Notifications Service is running.
settings_troubleshoot_test_play_services_failed Riot uses Google Play Services to deliver push messages but it doesn’t seem to be configured correctly:
%1$s
settings_troubleshoot_test_play_services_quickfix Fix Play Services
settings_troubleshoot_test_play_services_success Google Play Services APK is available and up-to-date.
settings_troubleshoot_test_play_services_title Play Services Check
settings_troubleshoot_test_service_boot_failed The service will not start when the device is restarted, you will not receive notifications until Riot has been opened once.
settings_troubleshoot_test_service_boot_quickfix Enable Start on boot
settings_troubleshoot_test_service_boot_success Service will start when the device is restarted.
settings_troubleshoot_test_service_boot_title Start on boot 起動時の実行
settings_troubleshoot_test_service_restart_failed Service failed to restart
settings_troubleshoot_test_service_restart_success Service was killed and restarted automatically.
settings_troubleshoot_test_service_restart_title Notifications Service Auto-Restart
Component Translation Difference to current string
This translation Propagated Not translated [Deprecated] Riot Android/[DEPRECATED] RiotX application
The following string has the same context and source.
Propagated Not translated [Deprecated] Riot Android/[DEPRECATED] Riot Android

Loading…

No matching activity found.

Browse all component changes

Glossary

English Japanese
application アプリ [Deprecated] Riot Android
restart 再起動 [Deprecated] Riot Android

Source information

Key
settings_troubleshoot_test_foreground_service_started_failed
Flags
java-format
String age
4 years ago
Source string age
4 years ago
Translation file
vector/src/main/res/values-ja/strings.xml, string 517