NetowkId paid out by WifiManager.addNetwork() changes on device reboot [401379129]

WAI

Bug

[AOSP] assigned

Status Update

No update yet.

Description

sa...@livelynx.co.jp

created issue #1

Mar 7, 2025 01:52AM

Confirmed by Pixcel8 AndroidOS 15.

I think Android stores the registered Wifi Network Configuration and NetworkId in persistent storage in the Android system. Therefore, I think that the registered Wifi network configuration can be used to connect even when the device is rebooted.

The procedure we tried is as follows.

In the DPC application, use addNetwork() to register Wifi(1).
Register Wifi(2) using addNetwork() in the DPC application.
Delete the registered Wifi(1).
In the DPC application, use addNetwork() to register Wifi(1).

At this point, we have the following.

NetowkId=2 for Wifi(1)
NetowkId=1 for Wifi(2)

But after this, when the device is rebooted, NetowkId paid out by addNetwork() had changed.

NetowkId=0 for Wifi(1)
NetowkId=1 for Wifi(2)

Is this as per spec?

Comments

ra...@google.com <ra...@google.com> #2Mar 7, 2025 07:45AM

Assigned to ra...@google.com.

I believe you've been looking into this

        at com.android.tools.idea.gradle.project.sync.idea.SdkSyncUtil.findMatchingSdkForAddon(SdkSyncUtil.kt:175)
        at com.android.tools.idea.gradle.project.sync.idea.SdkSyncUtil.computeSdkReloadingAsNeeded(SdkSyncUtil.kt:127)

ra...@google.com <ra...@google.com> #3Mar 15, 2025 06:05AM

Status: Won't Fix (Intended Behavior)

hm, in fact let's discuss how we handle SDKs/addons etc. and also bootlclasspath. We have an open issue with not supporting useLibrary which we need to fix.

Issue 401379129

Description

Issue summary

Comments

ra...@google.com <ra...@google.com> #2Mar 7, 2025 07:45AM

ra...@google.com <ra...@google.com> #3Mar 15, 2025 06:05AM

Add comment

Issue metadata