1185586 - Investigate ping sending/scheduling on Android

Status: RESOLVED DUPLICATE of bug 1220171

(Toolkit :: Telemetry, defect, P4)

Description

[Alessio Placitelli [:Dexter]]

We should take some time to investigate the impact of TelemetrySend ping sending scheduler on mobiles, as the scheduler goals are different compared to desktop: on mobile the general goal is to turn on the radio exactly once, ideally when it's needed for other connections.

Things to consider:

- Minimize bouncing between wakelocks/radio power mode changes
- Radio layer packet size (e.g. LTE favours big chunks of data)

Comment 1

[Georg Fritzsche [:gfritzsche]]

We need to check on what is actually expected for ping sending on Android, i don't exactly remember now.
Is Telemetry expected to send itself or is a Java service supposed to do this?

Comment 2

[Richard Newman [:rnewman]]

All telemetry uploading on Android is currently performed by Gecko. Some parts of the Java frontend *write* ping files, but they don't do the upload themselves.

Ideally we'll write a Java uploader: that way we can rely on Android network state events, alarm coalescing, etc. etc., and get one more background service out of Gecko where it doesn't belong.

Comment 3

[Georg Fritzsche [:gfritzsche]]

Thanks, then this probably needs no action now and can wait until the mobile Telemetry design discussions happened.
We have to address this before fully going for Unified Telemetry on Fennec, but this is not happening yet anyway.

Comment 4

[Georg Fritzsche [:gfritzsche]]

This is work happening on the mobile Team now, closing this over bug 1220171 et al.