[Mobile Android] App dims when watching backup screen in progress

[stephen304]

The bug

This is an odd bug, the app itself dims on the backup screen - not my screen but just the app itself like it has a dark overlay - but I can still interact with the screen (scroll), but only when I tap does the app brighten back up. Switching apps you can see the app is super dark. It feels kind of like some idle dimming but it doesn't feel consistent. It felt like switching apps might trigger it because it has happened soon after switching apps but other times when I sit and watch the upload it doesn't want to happen. I haven't exactly nailed down when it happens but it seems trivial to reproduce in my recording:

screen-20241212-211148_V1.mp4

The OS that Immich Server is running on

Synology Docker

Version of Immich Server

v1.122.2

Version of Immich Mobile App

v1.122.2 build.170
Pixel 5 Android 14 Lineage 21 with gapps

Platform with the issue

• Server
• Web
• Mobile

Your docker-compose.yml content

#
# WARNING: Make sure to use the docker-compose.yml of the current release:
#
# https://github.com/immich-app/immich/releases/latest/download/docker-compose.yml
#
# The compose file on main may not be compatible with the latest release.
#

name: immich

services:
  immich-server:
    container_name: immich_server
    image: ghcr.io/immich-app/immich-server:${IMMICH_VERSION:-release}
    restart: always
    volumes:
      - ${UPLOAD_LOCATION}:/usr/src/app/upload
      - /etc/localtime:/etc/localtime:ro
    env_file:
      - .env
#    ports:
#      - 2283:3001
    labels:
      - "traefik.enable=true"
      - "traefik.http.routers.immich.rule=Host(`example.com`)"
      - "traefik.http.routers.immich.entrypoints=websecure"
      - "traefik.http.routers.immich.tls.certresolver=mytlschallenge"
      - "traefik.http.services.immich.loadbalancer.server.port=2283"
    networks:
      - default
      - ingress
      - mail
    depends_on:
      - redis
      - database

  immich-machine-learning:
    container_name: immich_machine_learning
    # For hardware acceleration, add one of -[armnn, cuda, openvino] to the image tag.
    # Example tag: ${IMMICH_VERSION:-release}-cuda
    image: ghcr.io/immich-app/immich-machine-learning:${IMMICH_VERSION:-release}
    # extends:
    #   file: hwaccel.transcoding.yml
    #   service: cpu # set to one of [nvenc, quicksync, rkmpp, vaapi, vaapi-wsl] for accelerated transcoding
    restart: always
    volumes:
      - ./volumes/ml-cache:/cache
    env_file:
      - .env

  redis:
    container_name: immich_redis
    image: docker.io/library/redis:6.2-alpine@sha256:eaba718fecd1196d88533de7ba49bf903ad33664a92debb24660a922ecd9cac8
    restart: always
    healthcheck:
      test: redis-cli ping || exit 1

  database:
    container_name: immich_postgres
    image: docker.io/tensorchord/pgvecto-rs:pg14-v0.2.0@sha256:90724186f0a3517cf6914295b5ab410db9ce23190a2d9d0b9dd6463e3fa298f0
    restart: always
    command:
      [
        'postgres',
        '-c',
        'shared_preload_libraries=vectors.so',
        '-c',
        'search_path="$$user", public, vectors',
        '-c',
        'logging_collector=on',
        '-c',
        'max_wal_size=2GB',
        '-c',
        'shared_buffers=512MB',
        '-c',
        'wal_compression=on',
      ]
    environment:
      POSTGRES_PASSWORD: ${DB_PASSWORD}
      POSTGRES_USER: ${DB_USERNAME}
      POSTGRES_DB: ${DB_DATABASE_NAME}
      POSTGRES_INITDB_ARGS: '--data-checksums'
    healthcheck:
      test: pg_isready --dbname='${DB_DATABASE_NAME}' || exit 1; Chksum="$$(psql --dbname='${DB_DATABASE_NAME}' --username='${DB_USERNAME}' --tuples-only --no-align --command='SELECT COALESC>
      interval: 5m
#      start_interval: 30s
      start_period: 5m
    volumes:
      - ${DB_DATA_LOCATION}:/var/lib/postgresql/data

networks:
  ingress:
    external: true
  mail:
    external: true

Your .env content

# You can find documentation for all the supported env variables at https://immich.app/docs/install/environment-variables

# The location where your uploaded files are stored
UPLOAD_LOCATION=./volumes/library
# The location where your database files are stored
DB_DATA_LOCATION=./volumes/postgres

# To set a timezone, uncomment the next line and change Etc/UTC to a TZ identifier from this list: https://en.wikipedia.org/wiki/List_of_tz_database_time>
TZ=America/New_York

# The Immich version to use. You can pin this to a specific version like "v1.71.0"
IMMICH_VERSION=v1.122.2

# Connection secret for postgres. You should change it to a random password
DB_PASSWORD=xxxxxxxxxx

# The values below this line do not need to be changed
###################################################################################
DB_HOSTNAME=immich_postgres
DB_USERNAME=postgres
DB_DATABASE_NAME=immich

REDIS_HOSTNAME=immich_redis

Reproduction steps

0. Possibly have background backups enabled
1. Start backup on backup screen
2. Watch backup progress
3. Try switching apps while backup in progress
4. App dims after a bit
5. Scrolling doesn't un-dim, only tapping

Relevant log output

No response

Additional information

No response

[mertalev]

This is intended behavior. The reasoning is that keeping the app open makes the initial backup much faster, so you can leave it on this screen and it’ll prevent the screen from turning off. It automatically dims to prevent burn-in.

[stephen304]

I see, in that case I think it's a bug that scrolling doesn't un-dim the screen. That was the main reason I figured it was a bug since the dark screen makes it hard to see what you're interacting with and I can't see that being the intended behavior since it makes un-dimming the screen inconsistent (as it is currently, until you really pay attention it just feels like touching the screen randomly works or doesn't work to un-dim the screen which is what convinced me it was a bug).

The other thing that raised my suspicion is that the timeout for the screen dimming seems inconsistent as well which makes it feel buggy - in the recording I provided at 0:35 you can see it dims only ~8 seconds after switching back to immich, at 1:00 it takes 5 seconds to dim, and at 1:25 I wait ~16 seconds and no dimming occurs.

I can open a separate ticket for this if that helps.

[mertalev]

I agree on both points. You can make an issue about it for better tracking.