# AndroidLogcatView **Repository Path**: DamonT/android-logcat-view ## Basic Information - **Project Name**: AndroidLogcatView - **Description**: AndroidLogcatView是一个在您的电脑上实时显示 Android logcat 日志的工具。 - **Primary Language**: C# - **License**: Apache-2.0 - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 1 - **Created**: 2026-03-18 - **Last Updated**: 2026-03-18 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README # LogcatViewer User Manual ## Introduction LogcatViewer is a tool to display Android logcat logs on your PC in real-time. ## Features - Real-time logcat log display - Filtering by pid, tag, and package name - Saving logs to file - Filter history - Configurable ADB path - **AI Assistant** - Intelligent log analysis and troubleshooting support - **Multi-model Support** - Compatible with OpenAI, Ollama, and other AI providers - **Markdown Rendering** - Rich text display for AI responses ## How to Use ### Basic Usage 1. **Connect your Android device** to your PC via USB. 2. **Enable USB debugging** on your Android device. 3. **Run LogcatViewer.exe**. 4. **View logs** in the main window. 5. **Filter logs** using the filter input box. 6. **Save logs** to a file using the "File" -> "Save As" menu. 7. **Configure ADB path** using the "File" -> "Configure ADB Path" menu if ADB is not in your system PATH. 8. **Access User Manual** using the "Help" -> "User Manual" menu. 9. **Access About dialog** using the "Help" -> "About" menu. ### AI Assistant Usage 1. **Open AI Assistant** by clicking the AI assistant panel or button in the interface. 2. **Configure AI Model** by setting up your preferred AI provider (see AI Model Configuration section below). 3. **Ask Questions** about log analysis, error troubleshooting, or Android development issues. 4. **Get Intelligent Responses** with markdown-formatted explanations and solutions. 5. **Copy or Save** AI responses for future reference. ## AI Model Configuration The AI assistant supports multiple AI providers. Configure your preferred model by editing the `Settings.json` file in the application directory. ### Configuration Format ```json { "modelConfigs": [ { "apiProvider": "OpenAI", "apiKey": "your-openai-api-key", "url": "https://api.openai.com/v1/chat/completions", "modelName": "gpt-4" }, { "apiProvider": "Ollama", "apiKey": "ollama", "url": "http://localhost:11434/v1/chat/completions", "modelName": "llama2" } ], "lastSelectedProvider": "OpenAI", "lastSelectedModel": "gpt-4" } ``` ### Supported Providers - **OpenAI**: Requires valid API key and supports models like GPT-4, GPT-3.5-turbo - **Ollama**: Local AI models, requires Ollama server running locally - **Custom APIs**: Any OpenAI-compatible API endpoint ### Configuration Parameters - `apiProvider`: Name of the AI provider (e.g., "OpenAI", "Ollama") - `apiKey`: API key for authentication (use "ollama" for local Ollama) - `url`: API endpoint URL - `modelName`: Specific model name to use - `lastSelectedProvider`: Default provider to use on startup - `lastSelectedModel`: Default model to use on startup ## Troubleshooting ### ADB Issues - **"ADB not found" error**: - Make sure ADB is installed on your PC and the path to ADB is correctly configured in the application. - Use "File" -> "Configure ADB Path" to set the ADB path. - **No logs are displayed**: - Make sure USB debugging is enabled on your Android device. - Make sure your Android device is properly connected to your PC. - Check if ADB is working correctly by running `adb devices` in the command line. ### AI Assistant Issues - **AI Assistant not responding**: - Check your `Settings.json` configuration file for correct API settings. - Verify your API key is valid and has sufficient quota. - For Ollama: Ensure the Ollama server is running and accessible. - **"Model not found" error**: - Verify the model name in `Settings.json` matches available models. - For Ollama: Use `ollama list` to see available local models. - **Connection timeout**: - Check your internet connection for cloud-based APIs. - Verify the API URL is correct and accessible. - For local models: Ensure the local server is running on the specified port. ## Contact If you have any questions or issues, please contact runnerrjg@21cn.com