Skip to content
The Chat Archive
sonar-reasoning-pro-high LMArena Search Arena 24K

I'm not quite sure what I have done but since I did...something, some of my apps are…

  1. User

    I'm not quite sure what I have done but since I did...something, some of my apps are crashing and Fongo and Odysee are both unable to connect to their respective servers. I'm running Android 14 and it is rooted with Magisk. What might be the problem?

  2. Assistant

    Based on your description, there are several possible causes for your apps crashing and connectivity issues with Fongo and Odysee on your rooted Android 14 device. These issues are likely related to either your Magisk root configuration, system updates, or app permissions.

    Root-Related Issues

    When using a rooted device with Magisk, several components can cause apps to crash or fail to connect:

    Magisk Module Conflicts

    Certain Magisk modules can cause system instability and app crashes. James DSP and custom boot animation modules have been identified as particularly problematic in some cases[7][11]. Try disabling recently installed modules one by one to identify if any specific module is causing the issue.

    Zygisk and DenyList Configuration

    Apps like Fongo and Odysee may be detecting root access and failing as a result:

    1. Open Magisk and tap on the settings icon
    2. Enable "Zygisk" if it isn't already
    3. Enable "Enforce DenyList"
    4. Tap "Configure DenyList"
    5. Add the problematic apps (Fongo, Odysee) to the DenyList
    6. Also add Google Play Services, Google Play Store, and Google Service Framework[12]

    After configuring DenyList, you should:

    1. Clear data for Google Play Services (Settings > Apps > Google Play Services > Storage > Manage Space > Clear all data)
    2. Clear data for Google Play Store
    3. Clear data for Google Service Framework
    4. Restart your device[12]

    Android 14 Specific Issues

    Android 14 has introduced some specific issues that might be affecting your apps:

    Permission Resets

    Android 14 system updates can silently reset app permissions, causing connectivity problems. For apps like Fongo, this specifically affects:

    • The "Connected To Fongo" notification disappearing
    • Missed notifications
    • Microphone not working during calls

    To fix this:

    1. Go to Settings > Apps > Find the affected app
    2. Manually disable ALL permissions for the app
    3. Re-enable all permissions again
    4. This "toggle off and on" process is necessary - simply verifying permissions are enabled is not enough[13]

    Android System WebView Issues

    WebView is a critical component that allows apps to display web content internally, and issues with it can cause apps to crash:

    1. Go to Settings > Apps > Show system apps
    2. Find "Android System WebView"
    3. Try clearing its cache and data
    4. If problems persist, try uninstalling updates for Android System WebView (though this is a temporary fix)[4][5]

    Connectivity-Specific Solutions for Fongo

    Fongo specifically has known connectivity issues that might be separate from root-related problems:

    1. From the Fongo app, tap Account > Settings
    2. Under Troubleshooting, try enabling or disabling "Fongo Alternate Connection"[6][18]

    If that doesn't work, your internet provider might be blocking SIP communications:

    1. Try connecting to a different network
    2. Consider using a VPN service (TunnelBear, WindScribe, or Proton VPN have free options)
    3. Some VPNs support split tunneling which allows you to only route specific apps through the VPN[9]

    General Troubleshooting Steps

    If the above specific solutions don't work, try these general fixes:

    1. Restart your device (often solves temporary issues)
    2. Clear cache and data for problematic apps:
      • Settings > Apps > [App name] > Storage > Clear cache/Clear data[5][10]
    3. Check if your internet connection is stable by testing other apps or a web browser
    4. Temporarily disable any VPN or proxy services you might be using
    5. If all else fails, consider uninstalling and reinstalling the problematic apps[5]

    If these solutions don't resolve your issues, you might need to consider more drastic measures like:

    • Uninstalling some Magisk modules
    • Updating Magisk to the latest version
    • In extreme cases, temporarily unrooting your device to test if root is the primary cause

    Remember that rooting inherently creates some compatibility challenges with certain apps, especially those that implement security checks or rely on Google's SafetyNet attestation.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.

Identical first prompt