Skip to content

RDKEMW-24855: Remove active scan on DeepSleep wake-up - #351

Open
DevikaJaladi wants to merge 1 commit into
support/1.12.0from
topic/RDKEMW-24855
Open

RDKEMW-24855: Remove active scan on DeepSleep wake-up#351
DevikaJaladi wants to merge 1 commit into
support/1.12.0from
topic/RDKEMW-24855

Conversation

@DevikaJaladi

Copy link
Copy Markdown
Contributor

Reason for change: Remove rescan request upon wake-up(NSM-ON).
Priority: P1
Test Procedure: Refer ticket
Risks: Low

Signed-off-by: Jaladi djalad690@cable.comcast.com

Copilot AI lite review requested due to automatic review settings September 10, 2026 18:13
@DevikaJaladi
DevikaJaladi requested a review from a team as a code owner September 10, 2026 18:13

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change is a straightforward removal of a wake-up scan call with no apparent side effects on build correctness or control flow in the modified hunk.

Pull request overview

This PR removes the WiFi active scan that was previously triggered when waking from DeepSleep (with Network Standby ON), leaving the wake-up flow to proceed directly to DHCP lease reacquisition.

Changes:

  • Removed the DeepSleep wake-up StartWiFiScan() call and its associated logging/commentary.
  • Kept the existing behavior of reacquiring DHCP leases for wlan0 and eth0 upon wake from DeepSleep.
File summaries
File Description
plugin/NetworkManagerImplementation.cpp Removes the active WiFi scan on DeepSleep wake-up, retaining DHCP lease reacquisition behavior.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants