Avainsanana Android

I was confused by the wording

12. maaliskuuta 2024 klo 18.20
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Mastodon, saavutettavuus

Ah, apparently ”Show content warnings” on the app is the opposite of what’s ”Always expand posts marked with content warnings” in the web UI. I was confused because the former refers to the warning, whereas the latter refers to the content. There may be minor usability issue there, but I’ll leave it out of this one.

Sorry for the noise. To make up for it, #290 looks like a duplicate of this one and thus could possibly also be closed.

Vastaa viestiin sen kontekstissa (Github)

”Always expand posts marked with content warnings” not honored

12. maaliskuuta 2024 klo 16.46
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Mastodon

I have ”Always expand posts marked with content warnings” on in my settings, but CW-marked posts in the Android app still show as unexpanded.

I’m fairly sure this used to work until recently, and #87 being closed as ”completed” back in October would imply I wasn’t just imagining it.

Vastaa viestiin sen kontekstissa (Github)

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)

Preserve URL fragment (hash)

17. joulukuuta 2023 klo 12.21
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Omnivore, saavutettavuus, Ubiquiti

I was on my Android device, saving URLs pointing to individual comments in threads at Ubiquiti’s Unifi forums, but later returning to them on my desktop realized that the hash (fragment) portion had been dropped, so that the URLs only pointed to the opening post. Hence, just one link (pointing to the first post) had been saved. This is pretty useless for threads spanning multiple pages, where finding an individual comment is tough without the exact link.

Here’s a (random) example of a URL pointing to the second comment on the third page of one thread. Sharing it from any of Android, iPhone or desktop results in a link pointing to the first post instead.

Vastaa viestiin sen kontekstissa (Github)

My Year in review stats are different depending on which device I view them on

3. joulukuuta 2023 klo 16.20
Sijainti: Muut: Pocket Casts
Avainsanat: Android, Pocket Casts

My Year in review stats are different depending on which device I view them on, which I think must be unintentional. For instance, the very first page says I’ve listened to ”66 different shows and 215 episodes in total” on my Android phone, ”96 different shows and 752 episodes” on my Android tablet, and ”96 different shows and 762 episodes in total” on my iPhone.

My most listened show is RA Podcast according to both the iPhone and the tablet, though they again disagree on the total listening time, whereas my Android phone says my most listened show is Let’s Talk About Sects. The entire list of most listened shows is completely different too.

I can provide screenshots if needed. I’m submitting this report from the web UI, though I haven’t found the year in review feature here, so I can’t say if it is similarly affected.

Vastaa viestiin sen kontekstissa (Pocket Casts)

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)

Existing files with ”ä” in the filename are silently overwritten when a new file with the same name is uploaded

12. marraskuuta 2023 klo 11.09
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Apple

Steps to reproduce

  1. Have a PDF file with the name ”ä.pdf” (sic) in your Nextcloud.
  2. Have a different PDF file with the same name on your IOS device (Files app).
  3. Choose to share the file from your IOS device to Nextcloud.
  4. Select the folder where ”ä.pdf” already exists.
  5. Upload.

Expected behaviour

Get a dialog to choose how to deal with the filename conflict.

Actual behaviour

No dialog. The the existing file is silently overwritten by the newly shared file.


Nothing in server logs, but here’s the app log (at the default level).

Reasoning or why should it be changed/implemented?

The issue leads to data loss. I discovered this when I realized that saving bills from my banking app by sharing them to my Nextcloud had been doing this for who knows how long. (My electricity bills have the service provider name, ”Oulun Energia Sähköverkko Oy” in their filename.)

Environment data

iOS version: 17.0.3

Nextcloud iOS app version: ”Nextcloud Liquid for iOS”

Server operating system:

Web server: Apache 2.4.41

Database: MySQL/MariaDB 10.3.38

PHP version: 8.2

Nextcloud version:


  • This is not reproducible on Android (with my server), which is why I’m pretty sure the fault lies with the IOS app.
  • Also not reproducible on IOS with filenames with ASCII-only names (FWICT); this general case was apparently fixed when first reported as Upload via Share Menu Silently Overwrites Existing Files #1737.

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)

Uusimman päivityksen myötä taas 1 tähti

13. elokuuta 2022 klo 20.09
Sijainti: Muut: Google Play
Avainsanat: Android, MobilePay, S-ryhmä

Uusimman päivityksen myötä 1 tähti. Käytän sovellusta lähes päivittäin, mutta QR-koodia en ikinä missään, ja nyt tämä tyrkyttää sitä QR-koodinlukijaa oletuksena. Eikä ainakaan aiemmin tänään S-ryhmän päätteessä toiminut Bluetooth-maksaminen enää ollenkaan, eli ei edes sitten kun olin tuon QR-turhakkeen pyyhkäissyt pois tieltä (ei Androidilla eikä Iphonella). Laadunvalvonta on tekijällä pettänyt nyt lyhyen ajan sisällä jo kahdesti, eikä siellä vissiin UX-asiantuntijoitakaan paljon kuunnella.

Vastaa viestiin sen kontekstissa (Google Play)

Yes, they’re dismissible

30. maaliskuuta 2022 klo 20.40
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, NewPipe

Yes, they’re dismissible. They can even be brought back on after that (with another tap), and then they do disappear on their own.

I’ve updated Android on the tablet since reporting this, it’s now running Android 11 with One UI 3.1, with no change in the behavior as reported.

I’ve also tested landscape, portrait and autorotate modes, all with the same result.

Vastaa viestiin sen kontekstissa (Github)

Vanhempia »