View contributor agreement Contribution to this translation requires you to agree with a contributor agreement.

Translation

settings_troubleshoot_test_push_loop_waiting_for_push
English
The application is waiting for the PUSH
0/390
Key English Klingon State
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 ${app_name} 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 ${app_name}. 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 ${app_name}. 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_endpoint_registration_title Endpoint Registration
settings_troubleshoot_test_endpoint_registration_success Endpoint successfully registered to homeserver.
settings_troubleshoot_test_endpoint_registration_failed Failed to register endpoint token to homeserver:
%1$s
settings_troubleshoot_test_push_loop_title Test Push
settings_troubleshoot_test_push_loop_waiting_for_push The application is waiting for the PUSH
settings_troubleshoot_test_push_loop_success The application is receiving PUSH
settings_troubleshoot_test_push_loop_failed Failed to receive push. Solution could be to reinstall the application.
settings_troubleshoot_test_push_notification_content You are viewing the notification! Click me!
settings_troubleshoot_test_notification_title Notification Display
settings_troubleshoot_test_notification_notice Please click on the notification. If you do not see the notification, please check the system settings.
settings_troubleshoot_test_notification_notification_clicked The notification has been clicked!
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 ${app_name} 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 ${app_name}. This test should be run using mobile data (no WIFI).
%1$s
settings_troubleshoot_test_bg_restricted_failed Background restrictions are enabled for ${app_name}.
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
Key English Klingon State
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 ${app_name}. 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 ${app_name} 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_notification_notice Please click on the notification. If you do not see the notification, please check the system settings.
settings_troubleshoot_test_notification_notification_clicked The notification has been clicked!
settings_troubleshoot_test_notification_title Notification Display
settings_troubleshoot_test_play_services_failed ${app_name} 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_push_loop_failed Failed to receive push. Solution could be to reinstall the application.
settings_troubleshoot_test_push_loop_success The application is receiving PUSH
settings_troubleshoot_test_push_loop_title Test Push
settings_troubleshoot_test_push_loop_waiting_for_push The application is waiting for the PUSH
settings_troubleshoot_test_push_notification_content You are viewing the notification! Click me!
settings_troubleshoot_test_service_boot_failed The service will not start when the device is restarted, you will not receive notifications until ${app_name} 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_system_settings_failed Notifications are disabled in the system settings.
Please check system settings.
settings_troubleshoot_test_system_settings_permission_failed ${app_name} needs the permission to show notifications.
Please grant the permission.
settings_troubleshoot_test_system_settings_success Notifications are enabled in the system settings.
settings_troubleshoot_test_system_settings_title System Settings.
settings_troubleshoot_test_token_registration_failed Failed to register FCM token to homeserver:
%1$s
settings_troubleshoot_test_token_registration_quick_fix Register token
settings_troubleshoot_test_token_registration_success FCM token successfully registered to homeserver.
settings_troubleshoot_test_token_registration_title Token Registration
settings_troubleshoot_title Troubleshoot

Loading…

No matching activity found.

Browse all component changes

Glossary

English Klingon
No related strings found in the glossary.

Source information

Key
settings_troubleshoot_test_push_loop_waiting_for_push
Flags
java-format
String age
4 years ago
Source string age
4 years ago
Translation file
library/ui-strings/src/main/res/values-tlh/strings.xml, string 659