github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-03-11 20:54:58 -05:00
Code Issues 144 Packages Projects Releases 116 Wiki Activity

Android app startup performance slow #27

New Issue
Closed
opened 2025-11-07 08:23:16 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-07 08:23:16 -06:00
Owner
Copy Link

Originally created by @sreich on GitHub (Feb 13, 2017).

Android startup performance is much slower than lastpass, which I thought was slow in itself.

A cold start is much slower than a cold start of lastpass, and a hot start of lastpass is about 2 seconds.

A hot start of bitwarden is 3-6 seconds. Obviously this isn't a benchmark and you and I know the many variables in the system, but I can feel it's significantly slower and too slow when I have to rely on it for logging into everything.

This is on a pixel XL running Android 7.1.2(beta)

This was also with a near empty database, without any locking enabled. Lastpass I think is faster if I didn't have fingerprint enabled.

I'm free to test or debug (like provide logs, etc) if necessary. I can't speak as to if this is a regression or not (I haven't used it significantly since I was waiting on auto fill)

Originally created by @sreich on GitHub (Feb 13, 2017). Android startup performance is much slower than lastpass, which I thought was slow in itself. A cold start is much slower than a cold start of lastpass, and a hot start of lastpass is about 2 seconds. A hot start of bitwarden is 3-6 seconds. Obviously this isn't a benchmark and you and I know the many variables in the system, but I can feel it's significantly slower and too slow when I have to rely on it for logging into everything. This is on a pixel XL running Android 7.1.2(beta) This was also with a near empty database, without any locking enabled. Lastpass I think is faster if I didn't have fingerprint enabled. I'm free to test or debug (like provide logs, etc) if necessary. I can't speak as to if this is a regression or not (I haven't used it significantly since I was waiting on auto fill)
GiteaMirror commented 2025-11-07 08:23:17 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Feb 13, 2017):

What are you considering as a hot start? It seems mostly instant to me if i background the app and re-open it.

@kspearrin commented on GitHub (Feb 13, 2017): What are you considering as a hot start? It seems mostly instant to me if i background the app and re-open it.
GiteaMirror commented 2025-11-07 08:23:17 -06:00
Author
Owner
Copy Link

@jerryn70 commented on GitHub (Feb 14, 2017):

Sometimes when I click auto fill from notification , the main logo screen of bitwarden shows for more than15 sec then after that it shows the pin screen, but at that time it won't shows the pin keyboard, it will again take about 15 sec to show the pin keyboard

@jerryn70 commented on GitHub (Feb 14, 2017): Sometimes when I click auto fill from notification , the main logo screen of bitwarden shows for more than15 sec then after that it shows the pin screen, but at that time it won't shows the pin keyboard, it will again take about 15 sec to show the pin keyboard
GiteaMirror commented 2025-11-07 08:23:17 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Feb 14, 2017):

@jerryn70 What are your device details and versions?

@kspearrin commented on GitHub (Feb 14, 2017): @jerryn70 What are your device details and versions?
GiteaMirror commented 2025-11-07 08:23:18 -06:00
Author
Owner
Copy Link

@jerryn70 commented on GitHub (Feb 14, 2017):

Moto x play
Marshmallow 6.0.1
Non rooted

@jerryn70 commented on GitHub (Feb 14, 2017): Moto x play Marshmallow 6.0.1 Non rooted
GiteaMirror commented 2025-11-07 08:23:18 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Feb 14, 2017):

@jerryn70 I've seen similar behavior once a while back and after I reinstalled the app it went away. I haven't seen it since though. I'll continue to investigate.

@kspearrin commented on GitHub (Feb 14, 2017): @jerryn70 I've seen similar behavior once a while back and after I reinstalled the app it went away. I haven't seen it since though. I'll continue to investigate.
GiteaMirror commented 2025-11-07 08:23:18 -06:00
Author
Owner
Copy Link

@sreich commented on GitHub (Feb 14, 2017):

I was referring to hot start as in me being in the app and hitting home, or back to get back to the launcher.

As opposed to swiping the app out of recents which kills the app.

The latter is where the lowest hanging fruit are. Its startup after it is swiped from recents(what I would call a cold start) is quite long (esp when I'm waiting to log into my computer each bathroom break)

I've also noticed it's using about 377 MB of RAM right now..That probably doesn't help things as far as getting memory killed goes. Especially on devices with 1-2gb of RAM.

See http://i.imgur.com/P1PJ4Br.png

I don't know how much of it is in your control or inherent with xamarin.

Although I did find it interesting that this page shows two bitwarden entries.. Which is strange to me, maybe one is the accessibility service(LastPass doesn't have that though)? Or perhaps separate threads?

@sreich commented on GitHub (Feb 14, 2017): I was referring to hot start as in me being in the app and hitting home, or back to get back to the launcher. As opposed to swiping the app out of recents which kills the app. The latter is where the lowest hanging fruit are. Its startup after it is swiped from recents(what I would call a cold start) is quite long (esp when I'm waiting to log into my computer each bathroom break) I've also noticed it's using about 377 MB of RAM right now..That probably doesn't help things as far as getting memory killed goes. Especially on devices with 1-2gb of RAM. See http://i.imgur.com/P1PJ4Br.png I don't know how much of it is in your control or inherent with xamarin. Although I did find it interesting that this page shows two bitwarden entries.. Which is strange to me, maybe one is the accessibility service(LastPass doesn't have that though)? Or perhaps separate threads?
GiteaMirror commented 2025-11-07 08:23:18 -06:00
Author
Owner
Copy Link

@kspearrin commented on GitHub (Feb 20, 2017):

This should now be resolved with the 491 build in the play store beta.

@kspearrin commented on GitHub (Feb 20, 2017): This should now be resolved with the 491 build in the play store beta.
GiteaMirror commented 2025-11-07 08:23:19 -06:00
Author
Owner
Copy Link

@i3130002 commented on GitHub (Oct 3, 2022):

@sreich Is it a duplicate of https://github.com/bitwarden/mobile/issues/1723 ?

@i3130002 commented on GitHub (Oct 3, 2022): @sreich Is it a duplicate of https://github.com/bitwarden/mobile/issues/1723 ?
GiteaMirror commented 2025-11-07 08:23:19 -06:00
Author
Owner
Copy Link

@sreich commented on GitHub (Oct 3, 2022):

I wouldn't say so, theirs is more about biometric unlock, this issue was about startup. But, either way this seems to be resolved I don't have any issues with it on my pixel 6a

@sreich commented on GitHub (Oct 3, 2022): I wouldn't say so, theirs is more about biometric unlock, this issue was about startup. But, either way this seems to be resolved I don't have any issues with it on my pixel 6a
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#27
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?