Hey there! I’ve run into this exact issue before with older LineageOS builds—let’s get those full stack traces back, just like you had with CyanogenMod and stock Android. Here are the most reliable methods:

1. Enable Developer Options & Debugging Settings #

First, unlock Developer Options if you haven’t already:

• Go to Settings > About Phone
• Tap the Build Number 7 times until you see the "You are now a developer!" toast pop up.

Now head into Settings > Developer Options and tweak these settings (names might vary a little by device):

• Find and enable "Show full ANR and crash dialogs" or "Enable complete crash stack traces"—this overrides the generic "[未提供具体内容]" message and forces detailed crash info to display.
• Make sure "USB Debugging" is turned on (this helps if you need to pull logs via ADB later).

2. Use ADB Commands to Force Detailed Logging #

If the UI settings don’t do the trick, you can adjust system properties directly via ADB (make sure you have ADB set up on your computer):

• Connect your phone to your computer via USB, then run these commands in a terminal:

  # Enable debuggerd, which handles crash log generation
  adb shell setprop debug.debuggerd.enabled 1
  
  # Set AndroidRuntime log level to verbose for full details
  adb shell setprop log.tagAndroidRuntime VERBOSE
  

• Note: These changes are temporary (they’ll reset after a reboot). To make them stick, jump to the next step.

3. Persist Settings via build.prop (Requires Root) #

If you have root access, edit your /system/build.prop file to lock in the changes permanently:

• Add or modify these lines at the end of the file:

  debug.debuggerd.enabled=1
  ro.debuggable=1
  log.tagAndroidRuntime=VERBOSE
  

• Save the file, reboot your phone, and test a crash—you should now see full stack traces every time.

4. Pull Crash Logs Directly via ADB #

Even if the on-screen dialog still doesn’t show details, you can always fetch the full crash log from your computer:

• Right after a crash occurs, run this command in your terminal:

  adb logcat -b crash
  

• This will dump the complete crash stack trace directly to your terminal, which you can save or analyze as needed.

Give these steps a shot—most users find that enabling the developer option and setting the ADB properties fixes the issue immediately. Let me know if you hit any roadblocks!

内容的提问来源于stack exchange，提问作者dev