Closed
Bug 969252
Opened 10 years ago
Closed 9 years ago
Fennec has used 3.29GB since enabling FxA authenticated sync (in ~2days)
Categories
(Firefox for Android Graveyard :: Android Sync, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: blassey, Unassigned)
References
Details
(Keywords: meta)
Attachments
(2 files)
This is more than an order of magnitude increase over normal usage.
Comment 1•10 years ago
|
||
I'm assuming this is network bandwidth. It's feasible, I suppose -- all those unthrottled network requests.
Comment 2•10 years ago
|
||
Either token fetches are super expensive, or syncs aren't finishing, so you're doing a full first time Sync every 30 seconds. adb log, please.
tracking-fennec: ? → 29+
Component: FxA → Android Sync
Flags: needinfo?(blassey.bugs)
OS: Mac OS X → Android
Product: Firefox for Android → Android Background Services
Hardware: x86 → ARM
Version: Trunk → unspecified
Reporter | ||
Comment 3•10 years ago
|
||
(In reply to Richard Newman [:rnewman] from comment #2) > Either token fetches are super expensive, or syncs aren't finishing, so > you're doing a full first time Sync every 30 seconds. > > adb log, please. Any particular tag?
Flags: needinfo?(blassey.bugs)
Comment 4•10 years ago
|
||
(In reply to Brad Lassey [:blassey] (use needinfo?) from comment #3) > (In reply to Richard Newman [:rnewman] from comment #2) > > Either token fetches are super expensive, or syncs aren't finishing, so > > you're doing a full first time Sync every 30 seconds. Oh, yeah, failed first sync is way more likely. > > adb log, please. > > Any particular tag? FxSync, FxAccounts.
Updated•10 years ago
|
Severity: normal → major
Reporter | ||
Comment 6•10 years ago
|
||
I think we've already got a working theory, which is why this is depending on bug 971972
Flags: needinfo?(blassey.bugs)
Reporter | ||
Comment 7•10 years ago
|
||
I'm still experiencing high data and battery use (73% of battery usage) with sync enabled.
Reporter | ||
Updated•10 years ago
|
Attachment #8389951 -
Attachment mime type: text/x-log → text/plain
Comment 8•10 years ago
|
||
I setup FxAccount / Sync on a new Nexus 5 running Nightly, then let the phone sleep. In the morning, Nightly had used 39% of the battery. I setup Sync to pull bookmarks, passwords and tabs. The data appeared to be on my phone. I am attaching a log in case the 39% battery usage could be reduced.
Comment 9•10 years ago
|
||
(In reply to Mark Finkle (:mfinkle) from comment #8) > I setup FxAccount / Sync on a new Nexus 5 running Nightly, then let the > phone sleep. In the morning, Nightly had used 39% of the battery. A logcat with times (adb logcat -v time) would be handy: we can see that we're syncing every half hour, but not how long the sync is taking. Half an hour might be too aggressive, if nothing else on the device is live — it'll be preventing sleep and waking the network stack sixteen times overnight. If we decide to tweak that, we need to consider the impact on perceived readiness and first-run behavior: Android will schedule a sync when the DBs get touched on launch, which is both a good thing (no need for periodic syncs!) and a bad thing (now we're doing a sync while you're trying to browse).
Comment 10•10 years ago
|
||
nalexander, you got the bug number in your pull request wrong -- Bug 836790, not Bug 836780. :)
Updated•10 years ago
|
tracking-fennec: 29+ → ---
Comment 11•9 years ago
|
||
I think things have come a long way in the last year, and keeping this open won't fix the remainder on its own.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Android Background Services → Firefox for Android
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•