Missing Timestamp in Gotify Notifications on HyperOS (Redmi K70 Ultra)

[minemine-m]

Here’s the updated bug report in English with the Redmi K70 Ultra device model specified:

---

Bug Report: Missing Timestamp in Gotify Notifications on HyperOS (Redmi K70 Ultra)

Environment

• Device: Redmi K70 Ultra
• OS: HyperOS 2.0
• Gotify Version: Android Client v2.8.1 / Server v2.6.1 (example)
• Reproducibility: Consistent

Description

On Redmi K70 Ultra (HyperOS 2.0), Gotify notifications only display the timestamp when the message contains line breaks (\n). Single-line messages show no timestamp, reducing usability for brief alerts.

Steps to Reproduce

1. Send a single-line message via Gotify API:

   curl "http://gotify-server/message?token=XXX" -F "message=Test message" -F "priority=5"

   → No timestamp appears in the notification.

2. Send a multi-line message:

   curl "http://gotify-server/message?token=XXX" -F "message=Line 1\nLine 2" -F "priority=5"

   → Timestamp is displayed (e.g., "19:45").

Expected Behavior

• Timestamp should appear regardless of line breaks.

Actual Behavior

• Single-line messages → No timestamp
• Multi-line messages → Timestamp visible

Possible Cause

HyperOS may apply different notification templates based on message length/formatting, causing Gotify’s timestamp to be hidden in single-line notifications.

Workaround

Manually add a line break (\n) to force timestamp visibility:

curl "http://gotify-server/message?token=XXX" -F "message=Alert\n" -F "priority=5"

Additional Notes

• Issue persists across reboots & reinstalls.
• Other Xiaomi/HyperOS devices may be affected.

Would appreciate any insights or fixes from the Gotify/HyperOS teams. Thanks!

---

[jmattheis]

Please show a screenshot with both multi-line and single line messages.

[minemine-m]

Details

[jmattheis]

IMO this seems like a feature. While it's possible to add a trailing slash, it could worsen the display of notifications on other devices. On my Pixel 8 trailing newlines are ignored.

If more users have a problem with this, it maybe could be fixed in gotify, but with only one report I don't think it's worth the effort to maintain this specific OS fix.