hai007 d68a8f6216 Add following information into metrics: ...

1. country code: where the device is located.
2. network operator: the telephony operator MCC/MNC value.
3. tdls status: the TDLS status of the WiFi Lan
4. AP frequency: the wifi frequency of the connected WiFi AP.
5. Tethering status: the enable status of the wifi Hotspot.
6. try counts: the try counds of the medium operation.
7. Tx/Rx speed: the MAX TX/RX speed of the WiFi network.
8. Channel width: the supported WiFi frequency MHz value. e.g. 20MHz or 40MHz for the WiFi Direct Client or WiFi Hotspot STA.

Storage increase will be:
1.4 bytes connected_ap_frequency in advertising side
2.4 bytes connected_ap_frequency + 1 byte supports_extended_ble_advertisements in discover side.
3. Incoming or outgoing conection:
    4 bytes wifi_channel_width
    So need 4*4 = 16 bytes in two directions initial connections and two directions bandwidth upgrades.

So there are total 4+5+16 =  25 bytes grows in each share.

(25 bytes in each sharing * 1072782 shares/daily * 7 days/week) / GB = about 0.175 GB)
(1072782 was based on current daily activedevice on 20210906.)

PiperOrigin-RevId: 398656656

2021-09-23 23:02:45 -07:00

..

BUILD

update nearby_connections: proto: analytics: BUILD file.

2021-09-03 05:32:43 -07:00

connections_log_test.cc

update nearby_connections: proto: analytics: BUILD file.

2021-09-03 05:32:43 -07:00

connections_log.proto

Add following information into metrics:

2021-09-23 23:02:45 -07:00