Bug Report: fyDroid v23 Intent Bridge Broken? (Android apps fail to open web links)

Support & help
,
1

Description of the Problem: Hello everyone, After updating to the latest FydeOS v23, I am experiencing a persistent issue where Android apps (running in the new fyDroid subsystem) are completely unable to open web links.

Whenever an app tries to open a browser window—for example, when clicking a “Log In” button that redirects to a web authorization page, or simply clicking a URL inside an app—nothing happens at all. The app just sits there. It appears that the intent bridge that is supposed to pass URL intents from fyDroid to the FydeOS Chromium browser is completely broken or unresponsive. Because of this, I am currently locked out of several apps that require a web-based login.

System Information:

  • Device: Surface Go 3 LTE
  • FydeOS Version: FydeOS for You v23.0 (Active license)
  • fyDroid Version: Android 13 (165337.165337)

Troubleshooting Steps I Have Already Tried (Without Success): To rule out standard Android issues, I have extensively tested the following workarounds, none of which solved the problem:

  1. Installed an Alternative Browser: I installed the Brave browser via APK to see if a local Android browser could catch the intent instead of Chromium. It did not work.
  2. Updated Android System WebView: I made sure the WebView component in the Play Store is fully updated to rule out rendering issues.
  3. Checked Link Handling Permissions: I manually went into the specific app settings and verified that “Open supported links” is toggled ON.
  4. Tested Intent Catchers: I installed a third-party app (“Open Link With…”) and set it as the default Android browser to try and intercept the link manually. It was not triggered.

Conclusion & Question: Since none of the standard Android routing fixes work, this seems to be a deep-rooted issue with how v23 handles intents between the Android container and the main OS.

Is anyone else experiencing this issue, or is it just my specific setup acting up? Are there any specific terminal commands or hidden settings to manually repair the intent bridge?

Thank you in advance for any help or insights!