| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
This is an updated patch, based on what Paul did in 0071a841f73f571c29fb1651a88fda8b9bce70ca for Replicant 4.2
Change-Id: I5ec28bc505a35e045701a030a90804a6b35655b2
Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
|
|
|
|
| |
Change-Id: I4a656471a12821de2c16c2a19be01b7d9eba4e9a
|
|
|
|
| |
Change-Id: Id57336c400ebabcb525f1a5e741c49bfa11c2916
|
|
|
|
|
| |
Change-Id: Ia82f19d4248d5807282f076cfd76a462b1189f26
Signed-off-by: Roman Birg <roman@cyngn.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Get rid of keeping track of queued jobs, job scheduler does this and
all we really want is a new job id to not interfere with old ones
(unless we hit the max jobs allowed, then start the count over).
- Persist whether we have reported metrics for the owner user (once per
device)
Ref: CYNGNOS-1131
Change-Id: Ib5bac2944b5ca4259ea82a357b24708377c1dc4c
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We should report the upload status immediately to the job service and
not let the executor leave doInBackground() even after the job
successfully finished, and report a potential failure in onPostExecut().
Otherwise if conditions are no longer met, and the job has finished, it can
result in the job reporting as failed, even though it has succeeded.
Ref: CYNGNOS-714
Change-Id: I5e06ae9dbca5c1412641eed51acded7c67522ded
Signed-off-by: Roman Birg <roman@cyngn.com>
|
|
|
|
|
|
| |
Ref: CYNGNOS-471
Change-Id: Icfe5bf69b30afcddc1f23ae9ce1589e1c6ca2f6d
Signed-off-by: Roman Birg <roman@cyngn.com>
|
|
|
|
|
|
|
|
|
| |
We don't get onStopJob() callbacks after the job is finished.
Ref: CYNGNOS-714
Change-Id: I1906cb80854a193efaba0f662d66823fec5f7073
Signed-off-by: Roman Birg <roman@cyngn.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Send community metrics to CM.org as well as Cyanogen server
- Kill off Google Analytics
- Use JobScheduler to intelligently schedule uploads when network
connection is available
Change-Id: Ibd7d84a961dda4af20db9226191380e9f977b5de
Signed-off-by: Roman Birg <roman@cyngn.com>
|
|
|
|
| |
Change-Id: Ia015847be4bf985e206a5b4b2362959c6220e2ba
|
|
|
|
| |
Change-Id: I7de094ed9d0621f8744f8fb6236ae0085832d7ca
|
|
|
|
|
|
| |
Control newly introduced global setting
Change-Id: Iea22206cd8ac8bf7d45e4b7dabfb9f0d1e602e0e
|
|
|
|
| |
Change-Id: If830c05ee121d3951ffcf34cd3bbd499c5107f1d
|
|
|
|
|
|
|
| |
Turns out the service wasn't starting at all until someone looked at the data,
so no reports were being sent for CM11...
Change-Id: Ib64ddbed4e0cae9c2f71d6c0c79f8081d6f15301
|
|
|
|
| |
Change-Id: I0347b4401563acff1a9f488cde5d53bb76b02c10
|
|
CMStats is now integrated into settings.
Change-Id: Ice1b2c0c4882620eef774aca26b91a39d27f7b47
|