Modules contributing mainline modules (APK/APEX) should set
min_sdk_version as well as apex_available.
For now setting min_sdk_version doesn't change build outputs.
But build-time checks will be added soon.
Bug: 152655956
Test: m
Change-Id: I9b630aabff01eb1dd5dc4c0f14517e6d1a914126
To help find the root cause of high authentication failure rate in enterprise network, add EAP method and authentication phase2 method in connection event metrics.
Bug: 150237135
Test: manual
Test: atest com.android.server.wifi
Merged-In: I7f3268b2842783f99c0a43d8b4996d0a7dd46c6e
Change-Id: Id4ac7947871785d16b81c0806986f54d64fdb0ce
This CL has a couple of notable changes:
- Add communication layer between adbd, system server, and Settings UI
- Add system notification (Wireless debugging connected) when at least
one device is connected.
- Add trusted networks (BSSID) to the keystore.
- Changed the keystore format to:
<keyStore version="1">
<adbKey ... />
<wifiAP ... />
</keyStore>
- Currently, trusted networks don't have a expiration time. Also, only
way to clear it is by blowing up the keystore (revoke permissions).
- Add pairing mechanism:
- Using libadbwifi_pairing_connection C++ library to pair a device
using SPAKE2 protocol over TLS.
- Register MDNS service for client discovery.
- Removed ability to ctl.start/stop adbd from UsbDeviceManager
- AdbService now controls when to do this
Bug: 111434128, 119490154, 119492574
Test: Manual. From developer options:
1) USB debugging off, WiFi Debugging off
- Ensure both transports are disabled by trying to connect via WiFi and
USB.
2) USB debugging on, WiFi Debugging off
- Connections via USB are available, WiFi is disabled
3) USB debugging off, WiFi Debugging on
- Connections via WiFi are available (IP + port), USB is not available
4) USB debugging on, WiFi Debugging on
- Check both transports work
Change-Id: I9f87679d195da99a55b6faf7131da1f1af65fe01
Exempt-From-Owner-Approval: approved in aosp master
(cherry picked from commit a5969b5a1d9fe08783c32ea23bead56252a74383)
Provide a specifc notification to let users know that device
has no internet is because it really doesn't have internet access
or it's caused by private DNS resolution failed.
Bug: 113242081
Test: atest FrameworksNetTests
Change-Id: I710c88a4742f5fd56c39fc797d7fa3ad36dba553
This reverts commit 078fe45552425c18aa8052da0ae3c9205fa5c309.
Reason for revert: This change introduced a bug and it completely changed the functionality of WiFi data stall detection, e.g., high Tx link speed can easily trigger data stall. We would like to roll back them to restore the normal functionality of Wifi data stall detection.
Bug: 141995185
Change-Id: I024808b580955545b084112c4b14921f038b595f
Merged-In: I078d28ed81a84e32aaece839a51590364a974481
Data stall event can be triggered if the tx/rx tput is consecutively below a threshold over multiple RSSI polls. Changing the unit of the threshold from Mbps to Kbps allows us to configure a value below 1Mbps, e.g., 400Kbps.
Bug: 141027476
Test: frameworks/base/wifi/tests/runtests.sh
Signed-off-by: Mingguang Xu <mingguangxu@google.com>
Change-Id: Ib7b398fb6975c0d03b09550db9bf68a2bb8bddfb
Merged-In: I76d6338cd2d482d198fde1e5a2d1a0540c087ca6
This is an effort to define new criterion for triggering Wifi data stall:
(1) Defined data stall criterion based on transmit and/or receive throughput, transmit packet error rate, and CCA level. Data stall is triggered when transmit and/or receive links are consecutively bad over multiple RSSI polls.
(2) Added DeviceConfig flags (that is disabled by default) which may be configured on the server side to tune the thresholds at which data stall gets triggered.
Bug: 141027476
Test: frameworks/base/wifi/tests/runtests.sh
Change-Id: I895fd54cc7ec32815bce1899354ca265d4e93ea9
Signed-off-by: Mingguang Xu <mingguangxu@google.com>
Merged-In: I76d6338cd2d482d198fde1e5a2d1a0540c087ca6
Added L5 metrics to determine if L5 should be enabled or not.
Test: On device
adb shell dumpsys location
Output:
Number of CN0 reports: 149
Top 4 Avg CN0 mean (dB-Hz): 26.100838872410307
Top 4 Avg CN0 standard deviation (dB-Hz): 1.7702387090734562
Total number of sv status messages processed: 4202
Total number of L5 sv status messages processed: 703
Total number of sv status messages processed, where sv is used in fix: 1979
Total number of L5 sv status messages processed, where sv is used in fix: 46
Number of L5 CN0 reports: 97
L5 Top 4 Avg CN0 mean (dB-Hz): 20.273711379041377
L5 Top 4 Avg CN0 standard deviation (dB-Hz): 2.632911219511556
Used-in-fix constellation types: GPS GLONASS GALILEO
Output Logs: https://drive.google.com/drive/folders/1tGEolHWtF92UkJ8lxgFihIzfWLl8ChZK?usp=sharing
Bug: 137575988
Change-Id: Id306d7cc27c9410a5ad73f5a0940c25f8d795686
Merged-In: Id306d7cc27c9410a5ad73f5a0940c25f8d795686
Bug: 137886569
Test: Unit tests for Wifi: frameworks/opt/net/wifi/tests/wifitests/runtest.sh and manual test
Change-Id: I30aae21651237b1bc7291527d0beab3e28dadb21
- Also save the scale with the snapshot data instead of trying to infer it
from the state
- Also recycle the reduced resolution snapshot copy after writing it
Bug: 135150767
Test: atest TaskSnapshotPersisterLoaderTest
Change-Id: I64a9ccf16f3966ad5c6d07ff0b6ce8e9dd710e40
Bug: 134566750
Test: m droid
Change-Id: I2777e8f9da0c7e0f3fc84277600f9db45b2f837e
Exempt-From-Owner-Approval: no response from owners minor build change
Added Tron logging to StatusBarNotification.getLogMaker() so it will
be present in most logs about the notification.
Change-Id: I720706d37c663f2018bdfe2153ad180970166c90
Test: atest android.service.notification.StatusBarNotificationTest
Bug: 135180518
Also includes some minor fixes and improvements:
- Only update visibility of seekbar/scrubber if it changed
- Switching between seekable and not seekable media will update the
scrubber visibility
- Switching from seekbar to none will not restart the timer
Fixes: 132631846
Test: manual, atest com.android.systemui.statusbar.notification.row.wrapper.NotificationMediaTemplateViewWrapperTest
Change-Id: I158670119ad0742cf6a2387e08d54e548ee14ef5
This just adds some constants needed for a new dialog that shows
up on the first time dark theme is toggled.
Test: none, is a metrics change
Bug: 132695689
Change-Id: Ic7527879003a7d883e74cb00792e69655e5ec9ad
This reverts commit 3b33a04fb3b34cac4422b2520ddb0b8be7067b72.
Reason for revert: This is crashing ExtServices on qt-dev
Bug: 132679875
Change-Id: I60b7b6b8db33585f62e108389367c74ce682b922
Add new metrics constants and deprecate old ones for Emergency Dialer.
Bug: 124427605
Test: Manually. Check the result of
'adb logcat -b events | grep -e sysui_multi_action'
Change-Id: Ia72709a237a78e3a80540cb8f18c80f2bfe37adc
There were merge problems because master was modified independent of
qt-dev. This should be fixed by now so moving the number back to next
available.
Bug: 132719892
Change-Id: I19b28734b08877cb54574d5a059da5e7befe54ba
Test: N/A
This CL only adds a new line to re-align qt-dev and master for
metrics_constants to make it possible to rebase the enums.
Bug: 132719892
Test: N/A
Change-Id: Ie6354c904f3751f8620ff3ae7d420754b6314b33
- [Refactor] Also remove ACTION_DISPLAY_WHITE_BALANCE_SETTING_CHANGED
to Action enum.
Test: Rebuild rom
Bug: 131449561
Change-Id: I4edfdf275b7858a57cb12a1b4e3c03d2ec37e181
