| commit | 0542d844787cca0d69640195e894f2c93cd062c6 | [log] [tgz] |
|---|---|---|
| author | Stefano Duo <stefanoduo@google.com> | Wed Apr 12 10:42:44 2023 +0000 |
| committer | Stefano Duo <stefanoduo@google.com> | Wed Jun 14 13:45:34 2023 +0000 |
| tree | 2848893b7d7e45c6d7f2a684ecfb5fb98409aa49 | |
| parent | 482a9c0a18330a803194f8c0a6be2360af2a59c9 [diff] |
Add Cronet's atoms to AOSP Cherry-pick to branches required for external/cronet development Original commit message: Now that Cronet is shipped as part of the Tethering mainline module, it makes more sense to move its atoms IDs in the platform range. The atoms here have been copied 1:1 from https://source.corp.google.com/search?q=f:cronet_atoms.proto. If copied downstream as is, these would clash with the pre-existing ones in the app range (since the extension and proto field will have the same name). To solve this issue, we will deprecate the existing atoms in the app range and have Cronet always log using the IDs of this extension. Test: I've checked statsd output for a local build with logging enabled Bug: 284972285 Merged-In: Ie69d2c14c3635bb4c41f25d6da6ffe622ba6dd00 Merged-In: I4306f311143151fd0f26176f6a837229a7989416 Merged-In: I5413d0863c6b088e89529afd94ce8b86fe915bd3 Change-Id: Idbb13b16f8cbaca9454ed876c5962b71bd629aef