TeamAmaze / TeamAmaze/AmazeFileManager

Power saving mode

Open
#4,320 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Performance Area-UIUX Issue-Feature Needs-OPResponse
Dominant language
Kotlin
Stars
6.4k
Forks
1.7k
Avg merge
3d 9h
Merged PRs (30d)
1

Description

Is your feature request related to a problem? Please describe.

Animations and loading thumbnails increase power consumption.

Pull-to-refresh is triggered by the same finger movement that is responsible for scrolling up, meaning if you repeat it one time too often, you refresh when you didn't want to. Each unwanted refresh wastes battery power needlessly.

Describe the solution you'd like

This feature should disable transition animations, thumbnails, and the pull-to-refresh gesture, all with a single switch.

A simple button can be used for refreshing if the user wants it.

As an alternative to an app-internal switch, I suggest it to detect when the phone is in power saving mode and then deactivate all non-essential features that consume power (transition animations, thumbnails, pull-to-refresh).

Describe alternatives you've considered
Thumbnails can be disabled in the settings, but there is no feature to disable all non-essential power consuming features.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the settings and entry points for transition animations, thumbnails, and pull-to-refresh in the Android app. Decide how one power-saving switch or the phone's power-saving state should control those features, then verify that each non-essential feature is disabled while an explicit refresh remains available.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
Domain
mobile, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.