From 234872e187349919c82cbd1fe0afaf731b2c27c7 Mon Sep 17 00:00:00 2001 From: Pawan Wagh Date: Thu, 27 Jun 2024 19:40:38 +0000 Subject: [PATCH] Fix UI issues in localization - Some of the locales don't display entire text and BigTextStyle doesn't display ellipsis for them. Removing bigText. - Fixing strings to display 4KB - Reduce string for bootloader unlock title Bug: 345291007 Bug: 343893991 Bug: 343815951 Test: m Settings && adb install -r $ANDROID_PRODUCT_OUT/system_ext/priv-app/Settings/Settings.apk Flag: EXEMPT bugfix Change-Id: I3e5bf9bf70be1240cfe7d3a381bb8fef62ce2efa --- res/values/strings.xml | 6 +++--- .../development/PageAgnosticNotificationService.java | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/res/values/strings.xml b/res/values/strings.xml index dae8f5e1dae..1f6917e6bfa 100644 --- a/res/values/strings.xml +++ b/res/values/strings.xml @@ -11650,7 +11650,7 @@ Failed to reformat and wipe the data partition to ext4. - Bootloader Unlock Required for 16KB Mode + Bootloader Unlock Required This device needs to have the bootloader unlocked before using the 16KB developer option. Software integrity cannot be guaranteed in this mode, and any data stored on the phone while the bootloader is unlocked may be at risk. All user data and settings will be wiped when activating 16KB mode. Once the bootloader is unlocked, activating the 16KB option will require two reboots. @@ -11679,10 +11679,10 @@ You are in the 16KB mode of the page-agnostic mode. Software integrity cannot be guaranteed in this mode, and any data stored on the phone while the bootloader is unlocked may be at risk. Some features will be disabled in these modes, so some applications may not work. - In order to re-enter the production mode, you must, switch back to 4K mode and then lock the bootloader of the device. Tap to read more. + In order to re-enter the production mode, you must, switch back to 4KB mode and then lock the bootloader of the device. Tap to read more. You are in the 16KB mode of the page-agnostic mode. Software integrity cannot be guaranteed in this mode, and any data stored on the phone while the bootloader is unlocked may be at risk. Some features will be disabled in these modes, so some applications may not work. - In order to re-enter the production mode, you must, switch back to 4K mode and then lock the bootloader of the device. This would factory reset the device again and + In order to re-enter the production mode, you must, switch back to 4KB mode and then lock the bootloader of the device. This would factory reset the device again and restore it to production settings. After the device successfully boots into Android, disable OEM unlocking in Developer options. If the device fails to boot into Android or is unstable, re-flash the device with the latest factory images from <a href=\"https://developers.google.com/android/images\">https://developers.google.com/android/images</a> diff --git a/src/com/android/settings/development/PageAgnosticNotificationService.java b/src/com/android/settings/development/PageAgnosticNotificationService.java index bce1dd9e106..40dff0c8dbf 100644 --- a/src/com/android/settings/development/PageAgnosticNotificationService.java +++ b/src/com/android/settings/development/PageAgnosticNotificationService.java @@ -96,13 +96,13 @@ public class PageAgnosticNotificationService extends Service { notifyPendingIntent) .build(); + // TODO:(b/349860833) Change text style to BigTextStyle once the ellipsis issue is fixed. Notification.Builder builder = new Notification.Builder(this, NOTIFICATION_CHANNEL_ID) .setContentTitle(title) .setContentText(text) .setOngoing(true) .setSmallIcon(R.drawable.ic_settings_24dp) - .setStyle(new Notification.BigTextStyle().bigText(text)) .setContentIntent(notifyPendingIntent) .addAction(action);