thunderbird / thunderbird/thunderbird-android
Ability To Handle Push And Interval Polling Separately Depending On Connection Type
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Checklist
- I have used the search function to see if someone else has already submitted the same feature request.
- I will describe the problem with as much detail as possible.
- This issue only contains a request for one single feature, not multiple (related) features.
App version
6.6*
Problem you are trying to solve
At the moment there is only the option to retrieve emails through push or interval polling, regardless of which connection is currently being used (5G/LTE/3G or WIFI).
If you have set the retrieve of emails to "push" and are traveling with a mobile internet connection (5G/LTE...), this can lead to drastic battery consumption compared to interval polling. However, if the emails are retrieved via "push" via a WIFI connection, there will not be such an impact on the battery.
Suggested solution
My suggestion would be to implement the ability in the settings, which handles push and interval polling separately depending on which type of the connection you are currently using, in order to reduce battery consumption.
*Please have a look at the screenshot for more clarification
Screenshots / Drawings / Technical details

Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by locating the settings and polling code that control push and interval retrieval, then trace how the current connection type is detected. Done means users can configure push or interval polling separately for mobile data and Wi-Fi, with the behavior covered by appropriate tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100