You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lockType WIFI_MODE_FULL_LOW_LATENCY is forced in Android 14+.
Impacts:
Somewhat tested and its whatever. A special condition thing whatever that condition might be. I find it better to have it tied to an advanced setting (something I will eventually push out in a pull request) and keep it there if someone finds a reason for it to exist here.
Notes:
On Android 14, according to the docs, the WIFI_MODE_FULL_LOW_LATENCY only takes affect with the display on and app visible. Otherwise, the info is lacking or not clear on what exactly happens if those conditions are not met.
The text was updated successfully, but these errors were encountered:
The problem:
Android Studio lint checks or whatever doesn't mark it. I accidentally noticed instead.
swiftp/app/src/main/java/be/ppareit/swiftp/FsService.java
Line 340 in df0db0e
https://developer.android.com/reference/android/net/wifi/WifiManager#createWifiLock(java.lang.String)
"This method was deprecated in API level 29.
This API is non-functional. "
What should be done:
A. Continue not to use it
B. https://developer.android.com/reference/android/net/wifi/WifiManager#createWifiLock(int,%20java.lang.String)
"public WifiManager.WifiLock createWifiLock (int lockType, String tag)"
lockType WIFI_MODE_FULL_LOW_LATENCY is forced in Android 14+.
Impacts:
Somewhat tested and its whatever. A special condition thing whatever that condition might be. I find it better to have it tied to an advanced setting (something I will eventually push out in a pull request) and keep it there if someone finds a reason for it to exist here.
Notes:
On Android 14, according to the docs, the WIFI_MODE_FULL_LOW_LATENCY only takes affect with the display on and app visible. Otherwise, the info is lacking or not clear on what exactly happens if those conditions are not met.
The text was updated successfully, but these errors were encountered: