keybase / keybase/client

Keybase on Android kills my battery

Open
#8,533 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
9.2k
Forks
1.3k
Avg merge
12h 58m
Merged PRs (30d)
56

Description

I've just started trying Keybase in Android. While chatting my battery was losing 1 percentual point every 2min, while not chatting the battery usage was also high.

Now I believe making everything in the same app is not a good idea. There should be an app just for the chat, and you should thrive to make it as lean as WhatsApp and Riot. KBFS on Android should be another app and so on.

These are my humble thoughts and requests.

Contributor guide

No contributing guide indexed for this repository

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

No files, tests, or entry points are identified. Start by reproducing and profiling the reported battery drain while chatting and while idle on Android, then clarify whether the goal is an optimization or separate chat and KBFS apps. Done criteria are not defined in the report.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.