Case Study: Restoring Tung Ngern Notifications on Xiaomi 14T Pro

Case Background

We encountered a case involving the Tung Ngern merchant application on a Xiaomi 14T Pro that had not been actively used for approximately one month.

When we returned to test it with a real payment, the transaction was received normally, but the phone produced neither a notification nor the expected notification sound.

At that point, several explanations were possible. The issue could have been related to Tung Ngern itself, the merchant account, the phone configuration, or Android/Xiaomi's handling of an application that had remained unused for an extended period.

Rather than changing several settings at once, we followed a simple troubleshooting method:

Change one factor → make one real payment → observe the result → proceed to the next step.

Step 1: Use a Samsung A06 as a Comparison Device

We prepared a second device, a Samsung A06, which was logged into Tung Ngern using an employee account, and then performed a real payment test.

• The Samsung A06 employee account received its notification normally.
• The Xiaomi 14T Pro using the main merchant account did not receive a notification.

This meant we should not immediately conclude that Tung Ngern was failing generally, because another device continued receiving the expected notification.

Step 2: Reset the Notification Settings

We checked and reset the Tung Ngern notification configuration and then performed another real payment.

Result: Still no notification.

Step 3: Check Settings Related to an Unused Application

Because Tung Ngern had not been used on this device for approximately one month, we inspected Android/Xiaomi application settings, including permission management and settings related to prolonged inactivity.

After adjusting the relevant setting, we performed another real payment.

Result: Still no notification.

Step 4: Uninstall and Reinstall Tung Ngern

We uninstalled Tung Ngern, installed it again, logged back into the main merchant account, and performed another real payment.

Result: Still no notification.

In this particular test, reinstalling the application alone did not resolve the issue.

Step 5: Check Background Operation and Auto-run

We reviewed Tung Ngern's background behavior on the Xiaomi 14T Pro and reset/allowed Auto-run in background.

We then performed another real payment.

Result: Still no notification.

Based on this result, we cannot say that enabling Auto-run alone immediately restores Tung Ngern notifications.

Step 6: Restart the Xiaomi 14T Pro

After testing the preceding factors individually, we closed the application and restarted the Xiaomi 14T Pro.

Once the phone was running again, we performed another real payment.

Result: The Tung Ngern notification and notification sound returned.

How Did We Check Whether the Entire Phone Notification System Was Failing?

K SHOP on the same Xiaomi 14T Pro continued producing notification sounds normally.

The observed behavior therefore did not resemble a phone-wide audio or notification failure. It appeared to be more specifically associated with the state of Tung Ngern on this device.

Does This Mean Restarting Is the Fix?

Not necessarily.

What this field observation establishes is that restarting the Xiaomi 14T Pro was the final intervention immediately before Tung Ngern notifications returned.

However, it remains possible that the restart caused an earlier Background or Auto-run configuration change to take full effect.

The result should therefore be treated as a field observation from this specific device and test environment rather than a universal conclusion about every Android phone or every Tung Ngern account.

What Connect Hub Learned From This Case

When investigating payment notifications, knowing that “there is no sound” is only the starting point. The more useful question is where the expected behavior stopped.

Observe → form a hypothesis → change one factor → make a real payment → observe the result → proceed to the next factor.

The useful evidence includes both the intervention immediately preceding recovery and the interventions that were tested without restoring the notification.

Note: This article documents a Connect Hub field observation from the specific device and test environment described above. It is not official documentation or guidance from Krungthai Bank, and behavior on other devices may differ.