Avainsanana Samsung

Feature request: a ”Mark read” choice in push notifications

17. joulukuuta 2023 klo 17.06
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Mattermost, saavutettavuus, Samsung


A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).

Environment Information

  • Device Name: Samsung Galaxy A9
  • OS Version: Android 10
  • Mattermost App Version: 2.11.0
  • Mattermost Server Version: 9.3.0

Steps to reproduce

  1. Receive a message notification on the Android app.
  2. Pull down the notifications.
  3. Expand the received notification.

Expected behavior

Have a ”Mark read” option underneath the expanded notification.

Observed behavior

No ”Mark read” option, only ”Reply”.

Vastaa viestiin sen kontekstissa (Github)

URL of a federated WordPress post reopens the post in the app instead of a browser

14. marraskuuta 2023 klo 11.57
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Firefox, Mastodon, Samsung, WordPress

I’m using the ActivityPub plugin to enable following posts from my WordPress blog. The posts federate as excerpts with a URL pointing to the full post on my site.

Tapping on that URL in the Android app only causes it to reload the post (excerpt) inside the app, instead of opening the URL in either webview or a browser as I’d expect it to.

The (official) IOS app does open the URL a browser, as does Firefox on the desktop, which is why I suspect the Android app being at fault here.

I don’t know of a way to link my blog here it so that it opens in the app (which is a bit ironic), but here’s a deck link to the federated posts on mastodon.social. My personal Mastodon account is on mastodon.social.

Both my Android phone and Android tablet are affected, both are on Mastodon version 2.2.1. The phone is running Android 10 (with Samsung’s One UI 2.0), the tablet is on Android 11 (One UI 3.1).

Below is a screen recording from the Android phone exhibiting the issue: the first tap of the URL opens the federated note in single view, and subsequent taps then just reload that same view.


Vastaa viestiin sen kontekstissa (Github)

Still present in Nextcloud 3.21.2

1. lokakuuta 2022 klo 18.46
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Samsung

Still present in Nextcloud 3.21.2. My device is a Samsung A9 running Android 10.

Vastaa viestiin sen kontekstissa (Github)

Controls remain on screen after switching to fullscreen before video has loaded

21. marraskuuta 2020 klo 13.23
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, NewPipe, Samsung, YouTube


  •  I am using the latest version – v0.22.1
  •  I checked, but didn’t find any duplicates (open OR closed) of this issue in the repo.
  •  I have read the contribution guidelines
  •  This issue contains only one bug. I will open one issue for every bug report I want to file.

Steps to reproduce the bug

  1. Disable ”Start main player in fullscreen” in NewPipe settings
  2. Have a somewhat slow-to-load video (for whatever reason)
  3. Open the video in Newpipe
  4. Before video details (such as duration) have loaded, tap to switch to fullscreen

Actual behaviour

The playback controls remain on screen while the video plays, I have to tap once more to make them go away.

Expected behavior

The playback controls should disappear like they do when switching to fullscreen after the video details have loaded (and playback has begun).

Screenshots/Screen recordings

Device info

  • Android version/Custom ROM version: Android 10 with OneUI 2.5
  • Device model: Samsung Galaxy Tab S5e

Vastaa viestiin sen kontekstissa (Github)

This is still an issue for Samsung devices with the scrolling screenshot feature

3. marraskuuta 2020 klo 13.35
Sijainti: Vianhallintajärjestelmät: Nextcloud
Avainsanat: Samsung

This is still an issue, and always has been for Samsung devices with One UI’s scrolling screenshot feature.

Vastaa viestiin sen kontekstissa (Nextcloud)

Mobile devices receive ghost notifications for already read messages

29. elokuuta 2020 klo 20.07
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, LineageOS, Mattermost, Samsung


Mobile devices receive ”ghost” notifications for already read messages, when set to receive notifications ”when Away or offline”, and receiving user is set to be Away.

Steps to reproduce

  1. Set ”Mobile Push Notifications” to ”Trigger push notifications when”: ”Away or offline” (and send ”For all activity”)
  2. Using web interface on desktop, set your status to Away
  3. (Still in the web interface) receive a message in the currently open channel (which immediately marks it read)

Expected behavior

Nothing happens on the mobile device (no notification).

Observed behavior (that appears unintentional)

The mobile device receives a notification about the already read message. The notification immediately disappears. If you weren’t looking at the device, you’re left wondering why it alerted you.

Other info

If your status is set to Online instead of Away (at step 2), the mobile device receives no notification (as expected). If ”Trigger push notifications when” is set to ”Online, away or offline” (at step 1), the mobile device receives no notification irrespective of your Online/Away status (also as expected).

Environment Information

I’m self-hosting Mattermost 5.26.1 with self-hosted MMPNS 5.22.4. Mattermost Mobile is at version 1.34.0. My mobile devices have Android 10 (Samsung) and Android 7.1.2 (LineageOS 14.1).

I don’t know if this is an issue with the client or the server; I can re-report against the latter if appropriate.

Vastaa viestiin sen kontekstissa (Github)

I have the same ”android.process.media has stopped” issue on my Samsung phone

19. maaliskuuta 2020 klo 16.28
Sijainti: Vianhallintajärjestelmät: Nextcloud
Avainsanat: Android, Samsung

I have the same issue on my Samsung Galaxy A9 phone, with ”android.process.media has stopped” appearing for virtually every photo taken (though the uploads seem to still go through). My Samsung Galaxy Tab S5e does not have the same issue, nor do I recall seeing this on any other Android devices (from other manufacturers).

I don’t use alarmapp (to my knowledge, though I’m not sure which app that is).

Vastaa viestiin sen kontekstissa (Nextcloud)

Process: com.nextcloud.client: java.lang.ArrayIndexOutOfBoundsException

5. lokakuuta 2018 klo 15.23
Sijainti: Vianhallintajärjestelmät: Nextcloud
Avainsanat: Motorola, Nexus, Samsung

All of my devices are affected by this, or something very similar. My server is running Ubuntu 16.06 with Nextcloud 14.0.1 (in a subdirectory). Here’s logs from my

I trimmed them down to (what appears to me as) the essential, filtered out some noise and replaced my username and the server hostname.

Steps to reproduce:

  1. (On desktop) Create a new subdirectory under the sync directory, add two JPEG files into it. Wait for changes to sync.
  2. (On mobile) Open Nextcloud, select the newly created directory, switch to grid view.

Vastaa viestiin sen kontekstissa (Nextcloud)

Reproducible here on a Galaxy Tab 4 (SM-T530), Android 5.0.2.

16. lokakuuta 2017 klo 20.26
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Mattermost, Samsung

Reproducible here on a Galaxy Tab 4 (SM-T530), Android 5.0.2.

Vastaa viestiin sen kontekstissa (Github)

Can’t connect Nextcloud Android app with the server

20. heinäkuuta 2016 klo 19.20
Sijainti: Keskustelupalstat: Nextcloud
Avainsanat: Android, F-Droid, Nexus, Samsung

I just migrated from Owncloud 8.2 to Nextcloud 9.0.52. Everything else (i.e. the web interface, desktop client) seems to work just fine, but I can’t get the Nextcloud Android app to connect with the server. I can enter the URL (no errors), my login and password, but the ”Connect” button feels totally unresponsive, it does nothing at all no matter how much I tap it. No error messages are given by the app nor is there anything correlating with the attempts in server logs.

This happens on both my phone (Nexus 5X, Android M) and tablet (Samsung Tab 4, Android L). I also tried the Beta app from F-Droid and the issue is present there too. It’s also present in both my WLAN and when using a direct 3G connection on the phone (so I don’t think the WLAN router’s firewall is the cause either).

The Owncloud app on the same devices still works with the server, although I haven’t tried logging out and re-connecting it.

The server is on shared hosting where I have shell access.

Any suggestions?

Vastaa viestiin sen kontekstissa (Nextcloud)

Vanhempia »