Skip to content
TheChatArchiveThe Chat Archive
chatgpt-4o-latest-20250326· OpenAIHugging Face LMArena Human Preference 140K

On my android device I have this problem: A background system process keep restarting…

From a Chatbot Arena battleThe same person sent this prompt to two anonymous models at once. Compare it with Metallama-4-scout-17b-16e-instruct’s answer.
  1. User

    On my android device I have this problem: A background system process keep restarting and consuming resources. I retrieved some error messages from the system log, among which the following: "cnss-daemon: Failed to get sock name Socket operation on non-socket"

    It's somehow related to 'cdsprpcd' and maybe also some proprietary qualcomm stuff...

    Could you suggest a solution or a workaround?

  2. Assistant

    The issue you're experiencing with cnss-daemon, cdsprpcd, and Qualcomm-related processes is likely tied to components responsible for Wi-Fi, Bluetooth, or DSP (Digital Signal Processor) hardware in your Android device. These services are part of the Qualcomm's proprietary binaries related to communication subsystems and modems.


    🔍 What's happening?

    The error you're seeing:

    cnss-daemon: Failed to get sock name Socket operation on non-socket
    

    means that cnss-daemon is trying to perform a socket operation on an invalid file descriptor, likely due to a misconfigured service, corrupted socket file, or improperly initialized hardware resource.

    Additionally, cdsprpcd (a user-space daemon for Qualcomm's Hexagon DSPs) might be triggering or affected by the same root problem, possibly based on binder IPC or shared memory channels.


    ✅ Potential Causes

    1. Baseband firmware bug or crash
    2. Corrupt or mismatched vendor/firmware binaries
    3. Custom ROM or kernel incompatibility
    4. Permissions or SELinux denials
    5. Conflict between the cnss-daemon and cdsprpcd

    🔧 Possible Solutions & Workarounds

    🛠 1. Clear Cache (Dalvik/ART & System)

    If you're running a custom ROM or rooted device:

    • Reboot to recovery (e.g., TWRP)
    • Wipe:
      • Dalvik / ART Cache
      • Cache (System Cache)

    ⚠️ This often fixes strange hardware init problems after updates.


    🛠 2. Check for SELinux Denials

    On rooted devices or via adb root, check logcat for SELinux denial messages:

    adb logcat | grep denied
    

    Sometimes, the cnss-daemon or related binaries are blocked from performing needed actions.

    If you're on a custom ROM, try switching to Permissive SELinux (temporarily!) and check if the issue persists:

    su
    setenforce 0
    

    If the issue goes away, it's SELinux policy related.


    🛠 3. Ensure Firmware is Correct

    This issue is common on devices with mismatched firmware/vendor partitions, common if:

    • You installed a custom ROM without matching vendor blobs
    • You dirty-flashed another ROM without flashing a matching firmware zip

    Fix:

    • Flash the proper firmware or vendor image for your specific Android version and device
    • For example, on Pixel/OnePlus: flash firmware image before ROM
    • On Xiaomi: use proper firmware-vendor zip specific to build number

    🛠 4. Disable or Replace Problematic Daemon (Root Required)

    If the daemon is restarting constantly, you could temporarily disable or replace it.

    adb root
    adb shell
    
    # Rename problematic binary to prevent it from running
    mv /vendor/bin/cnss-daemon /vendor/bin/cnss-daemon.bak
    

    ⚠️ However, this might break Wi-Fi, Bluetooth, or modem functionality. Test if the looping stops.


    🛠 5. Patch init.rc or .rc service definition (Advanced)

    On rooted devices, the service might be defined in the init.*.rc files, like:

    service cnss-daemon /vendor/bin/cnss-daemon
        class late_start
        user system
        group wifi inet
        disabled
        oneshot
    

    Edit or override the service definition to prevent restart loops or adjust environment.


    🛠 6. Use Logcat to Pinpoint Trigger

    Use:

    adb logcat -b all -v time | grep cnss
    

    Look for the first error occurrence. Sometimes it's triggered by:

    • Bluetooth init
    • Wi-Fi scanning
    • Audio DSP (via cdsprpcd)

    You might trigger the crash when toggling Wi-Fi or Bluetooth.


    🚑 Last Resort

    ✨ Option: Clean Flash

    If you’re using a custom ROM or had firmware drift:

    • Back up your data
    • Flash stock firmware package or matching ROM + vendor + firmware
    • Perform full wipe

    🧠 Notes

    • cnss-daemon is Qualcomm’s connectivity daemon — "CNSS" = "Connectivity Subsystem Support"
    • cdsprpcd is the RPC server used to communicate with Hexagon DSP
    • Both must be in sync with the correct hardware drivers and firmware blobs.

    ✅ TL;DR Action Plan

    StepAction
    ✅ 1Clear Dalvik and System Cache
    ✅ 2Check for SELinux denials (setenforce 0 temporarily)
    ✅ 3Ensure firmware/vendor partitions match ROM
    ✅ 4Logcat crash details around cnss-daemon and cdsprpcd
    ✅ 5Temporarily disable cnss-daemon (mv) if restarting/system load is intense
    ✅ 6Reflash correct firmware + vendor blobs if all else fails

    Let me know your device model, ROM (stock/custom?), and whether you're rooted — with that, I could give tailored steps or firmware links.

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