Bug #196
Reduce ping frequency
Status: | Closed | Start date: | 06/16/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | n8fr8 | % Done: | 0% | |
Category: | - | |||
Target version: | v14 - Armadillo's Agram | |||
Component: | XmppConnection |
Description
We currently ping every 60 seconds. Yaxim pings every 15 minutes and apparently it's not an issue. Reducing the ping frequency will improve batter life.
60 seconds was chosen two years ago when I discovered that tmobile disconnected idle connections after about 120 seconds. Looks like this is no longer the case.
- Consider making this configurable with a 5 minute default.
- Ensure that network state change doesn't depend on pings to work correctly (should work with Android network state notifications).
Associated revisions
History
#1 Updated by n8fr8 over 5 years ago
Can we try to get this in this release? Battery life seems like a big concern out there.
#2 Updated by devrandom over 5 years ago
- Status changed from New to In Progress
#3 Updated by devrandom over 5 years ago
For now, I have a commit that lets the user choose the heartbeat (ping) interval in minutes. It still defaults to 1.
I think we should get some brave testers to try this on different networks before we widely release a 5 minute interval default.
#4 Updated by devrandom over 5 years ago
- Target version changed from v10 - June Jaunts to v11 - January Judo
#5 Updated by devrandom about 5 years ago
- Target version changed from v11 - January Judo to v12 - March Mantra
Postponing until we actually get people to test this on different networks. n8fr8 - perhaps you can arrange some testers? I only have t-mobile users available.
#6 Updated by devrandom about 5 years ago
- Assignee changed from devrandom to n8fr8
#7 Updated by devrandom over 4 years ago
- Target version changed from v12 - March Mantra to v13 - October Oooya
#8 Updated by devrandom about 4 years ago
- Target version changed from v13 - October Oooya to v14 - Armadillo's Agram
#9 Updated by devrandom almost 4 years ago
- Status changed from In Progress to Resolved
Applied in changeset chatsecureandroid|commit:bc2b19b8ca8af93cb5ad3536f11d0699c2580bcb.
#10 Updated by devrandom almost 4 years ago
Applied in changeset chatsecureandroid|commit:85e34491c5c409c5c6f6490b2a6208533946cc64.
#11 Updated by n8fr8 over 2 years ago
- Status changed from Resolved to Closed