[MS Edge Android] Omnibox suggestions never render on Android 17 (SDK 37) / HyperOS 4 — Stable and Beta both affected

chen_e ma 5 Reputation points
2026-10-20T12:27:45.5+00:00

Product: Microsoft Edge for Android

Edge version: 155.0.4283.48 (versionCode 428304805), also reproduced on Edge Beta

Device: Xiaomi 2510DRK44C

OS: HyperOS 4.0 (ro.mi.os.version.name = OS4.0), Android 17 (ro.build.version.release = 17, SDK 37)

Edge targetSdk: 37

Summary

On this device the address bar accepts input and the autocomplete/omnibox data layer works, but the suggestion dropdown is never rendered. Typing a single letter produces an empty area below the address bar — no history suggestions, no search suggestions, no "go to site" row. Pressing Enter on that single letter does navigate to the expected site, so the backend suggestions are being produced and selected; only the popup surface is missing.

Steps to reproduce

  1. On a device running Android 17 (SDK 37) with HyperOS 4.0, open Microsoft Edge for Android.
  2. Tap the address bar so the keyboard shows.
  3. Type a single letter, e.g. "b".
  4. Observe: the area below the address bar stays empty. No suggestion rows appear, even after waiting several seconds for remote suggestions.
  5. Press Enter: the browser navigates correctly (e.g. "b" + Enter opens the expected Bilibili page), proving the autocomplete result set is not empty.

Actual vs expected

Actual: zero suggestion rows are drawn. An accessibility node dump of the window while the dropdown should be visible contains only the address bar node and the clear button — the popup window is never created, it is not merely drawn transparently or off-screen.

Expected: a dropdown listing URL/history suggestions and search suggestions.

Controls already ruled out

This is not a settings, network, or search-provider issue. All of the following were tested on the device and changed nothing: search suggestions / search history / show-suggestions toggles (all enabled, unchanged); switching the search engine between providers; address bar position top <-> bottom; theme system default <-> light (rules out same-color text); clearing cache and data; reinstalling; updating Edge; installing Edge Beta; verifying that remote suggestion endpoints are reachable from the device.

Decisive cross-check: the browser engine, not the OS input stack

Same device, same keyboard, same single character "b":

  • Edge Stable 155.0.4283.48 (Chromium): dropdown empty
  • Edge Beta (Chromium): dropdown empty
  • Google Chrome (Chromium): dropdown empty
  • Built-in system Browser com.android.browser (non-Chromium): dropdown fully populated with history URLs and search suggestions

So the Android input method, window manager and popup rendering path are all healthy on this OS build; only Chromium-based browsers fail to attach the omnibox suggestion popup, and Chrome fails in exactly the same way as Edge — which points at the Chromium omnibox popup layer on Android 17 rather than at an Edge-specific regression.

Impact

Users on Android 17 cannot see any autocomplete, history or search suggestions. Typing a full URL works, so the browser is usable, but the main discovery surface is gone.

Questions

  1. Is this a known Chromium-side issue with the omnibox suggestion popup on Android 17 (SDK 37)?
  2. If so, is there a target release for a fix, and is there any client-side workaround (flag or switch) that restores the dropdown in the meantime?
  3. If a diagnostic trace is needed, tell me which log buffer or edge:// page to capture and I will attach it.
Microsoft Edge | Tabs, address bar, and search | Android

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. 与君 余生 0 Reputation points
    2026-11-01T12:26:58.25+00:00

    Was this answer helpful?

    0 comments

  2. AI answer

    2026-10-20T12:29:01.9366667+00:00

    There is no publicly confirmed Chromium-wide Android 17/HyperOS 4 omnibox-popup defect, published fix milestone, or supported Edge flag; capture a fresh Edge mobile diagnostic package and submit it with this device-specific reproduction.

    Current status

    • The closest Chromium report is “M151 Android - Search suggestions fail to …”. Chromium engineers reportedly could not reproduce it on a Xiaomi 15T Pro running Android 17 Beta and observed suggestions working on Chrome M151–M153. Therefore, it does not currently establish a general SDK 37 or HyperOS 4 defect, despite the close symptom match.^1^
    • Chromium also has a broader report where the NTP omnibox dropdown sometimes does not appear, but that report does not establish applicability to HyperOS 4, Android 17, or Edge 155.^2^
    • Edge 155.0.4283.48 release notes do not list this problem or a corresponding fix. Version 155.0.4283.61 was released on October 19, 2026 with unspecified bug and performance fixes, so no claim can be made that it corrects the popup.^3^
    • The Beta notes likewise contain no published omnibox-popup correction or target milestone.^4^

    Your Stable/Beta/Chrome comparison is strong evidence of a shared Chromium-family path on this particular firmware. It does not conclusively isolate Chromium from an OS compatibility interaction, because those browsers can share implementation paths that the system browser does not use.

    Capture the useful Edge diagnostic package

    Since settings, data reset, providers, network reachability, themes, and both Edge channels are already ruled out, do not repeat those tests.

    1. If Google Play offers Stable 155.0.4283.61 or later, reproduce once there. This is only a current-build comparison, not a documented fix.
    2. Reproduce from a fresh launch:
      • Open Edge.
      • Focus the omnibox.
      • Type b.
      • Wait several seconds.
      • Press Enter and record the resulting navigation.
    3. Immediately open the bottom-right overflow menu.
    4. Swipe left and select Help and feedback.
    5. Open diagnostic data.
    6. From the top-right submenu, save the logs. On Android, they are written under Download > Edge.^5^
    7. Alternatively, describe the reproduction in Help and feedback and use the top-right upload button to send the logs directly to Microsoft. Include:
      • Xiaomi model and complete HyperOS build number
      • Android release and SDK
      • Edge version and versionCode
      • Stable/Beta/Chrome affected; system browser unaffected
      • Accessibility dump showing that no popup node/window is created
      • Screen recording of typing and subsequent successful Enter navigation
      • Link to the closest Chromium issue

    If old diagnostic data is present, use the Clear control on the diagnostic-data screen before reproducing so the package contains only the new attempt. Managed devices may prevent saving logs locally under an Intune App Protection Policy; direct upload remains the appropriate route in that case.^5^

    Traces that are unlikely to discriminate this failure

    • edge://net-export is supported on Android, but it captures network activity rather than native omnibox popup creation.^6^ Because endpoint reachability and local-history rows are already covered, collect NetLog only if Microsoft or Chromium asks for it.
    • edge://inspect targets live webpage content. The omnibox is browser-native UI, so page DevTools will not normally expose its popup hierarchy.^7^
    • The unofficial “Omnibox Consumes IME” workaround came from a different Cromite issue involving keyboard coverage. It is not an official Edge/Chrome fix and does not closely match a popup that is never created.^8^
    • Edge’s policy for controlling feature-flag overrides is not supported on Android, so there is no documented administrator-controlled flag workaround to deploy here.^9^

    The actionable outcome is therefore escalation with fresh mobile diagnostics and the cross-browser evidence; neither a confirmed target release nor a supported client-side workaround is currently published.

    References

    1. [User Feedback - Stable] M151 Android - Search suggestions fail to ...
    2. on NTP, omnibox suggestion dropdown sometimes doesn't appear
    3. Release notes for Microsoft Edge Mobile Stable Channel
    4. Release notes for Microsoft Edge Mobile Beta Channel
    5. Manage Microsoft Edge on iOS and Android With Intune
    6. Use NetLog as an alternative to Fiddler and HAR captures
    7. Remotely debug Android devices
    8. Omnibox suggestion dropdown covered by keyboard with bottom ... - GitHub
    9. FeatureFlagOverridesControl
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.