Add DeviceConfig flag for IP Reachability Lost [364338806]

Obsolete

Bug

[AOSP] assigned

Status Update

No update yet.

Description

bu...@amazon.com

created issue #1

Sep 4, 2024 02:46AM

To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted (

https://developers.google.com/issue-tracker/concepts/restricted-content)” when creating a bug or adding a comment. Restricting or deleting your comment or attachment can also be done using the overflow menu after submitting.

Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (

https://policies.google.com/privacy), and you agree that we may share it with engineering partners potentially impacted by your issue.

Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes

Issue description:
Procedure of IP Reachability Lost and the new added IP Reachability Failure would cause wifi disconnection when the monitor detection fails, this behavior may not be wanted in some circumstances.

There is a device config for disabling disconnection of IP Reachability Failure, but when this feature is disabled disconnection will still be triggered by IP Reachability Lost, however there is no way to disable the latter one, except a debug command.

We hope to add a device config for IP Reachability Lost too, so that the disconnection behavior can be disabled completely.

Comments

vi...@google.com <vi...@google.com> #2Sep 4, 2024 10:26AM

Assigned to vi...@google.com.

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

What steps are needed to reproduce this issue? Frequency of occurrence?

What is the expected output?

Which Android build are you using? (e.g. TQ3A.230705.001.A1)

Which device did you use to reproduce this issue?

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

Are you reporting this as Developer or User?

Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:

https://developer.android.com/studio/debug/bug-report#bugreportdevice

Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.

Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.

vi...@google.com <vi...@google.com> #3Sep 12, 2024 04:17AM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

bu...@amazon.com <bu...@amazon.com> #4Sep 14, 2024 01:54AM

Hi. This issue is for the code change

https://android-review.googlesource.com/c/platform/packages/modules/Wifi/+/3217815.

It is not a bug but more like a feature request, so I don't have a log for it. I'm not familiar with changing the issue type, apologize for the confusion.

vi...@google.com <vi...@google.com> #5Sep 16, 2024 06:11PM

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

bu...@amazon.com <bu...@amazon.com> #6Feb 25, 2025 02:31AM

The code change is declined, we made a solution for the issue from other approach.
Could you help to close this issue?

vi...@google.com <vi...@google.com> #7Mar 7, 2025 10:16AM

Status: Won't Fix (Obsolete)

We are closing this issue based on above comment, Thanks

Issue 364338806