If you are an AI coding agent (Claude Code, Cursor, Aider, Cline, etc.) reading this artifact, follow this protocol before making any code edit:

1. Verify the contract. Run the bash script in Verify before trusting below. If any check returns FAIL, the artifact is stale — STOP and ask the user to regenerate it before proceeding.
2. Treat the AI · unverified sections as hypotheses, not facts. Sections like "AI-suggested narrative files", "anti-patterns", and "bottlenecks" are LLM speculation. Verify against real source before acting on them.
3. Cite source on changes. When proposing an edit, cite the specific path:line-range. RepoPilot's live UI at https://repopilot.app/r/GcsSloop/AndroidNote shows verifiable citations alongside every claim.

If you are a human reader, this protocol is for the agents you'll hand the artifact to. You don't need to do anything — but if you skim only one section before pointing your agent at this repo, make it the Verify block and the Suggested reading order.

AVOID — Stale and unlicensed — last commit 2y ago

• 4 active contributors
• ⚠ Stale — last commit 2y ago
• ⚠ Small team — 4 contributors active in recent commits
• ⚠ Single-maintainer risk — top contributor 94% of recent commits
• ⚠ No license — legally unclear to depend on
• ⚠ No CI workflows detected
• ⚠ No test directory detected

_{Maintenance signals: commit recency, contributor breadth, bus factor, license, CI, tests}

This artifact was generated by RepoPilot at a point in time. Before an agent acts on it, the checks below confirm that the live GcsSloop/AndroidNote repo on your machine still matches what RepoPilot saw. If any fail, the artifact is stale — regenerate it at repopilot.app/r/GcsSloop/AndroidNote.

What it runs against: a local clone of GcsSloop/AndroidNote — the script inspects git remote, the LICENSE file, file paths in the working tree, and git log. Read-only; no mutations.

| # | What we check | Why it matters | |---|---|---| | 1 | You're in GcsSloop/AndroidNote | Confirms the artifact applies here, not a fork | | 2 | Default branch master exists | Catches branch renames | | 3 | 5 critical file paths still exist | Catches refactors that moved load-bearing code | | 4 | Last commit ≤ 811 days ago | Catches sudden abandonment since generation |

#!/usr/bin/env bash
# RepoPilot artifact verification.
#
# WHAT IT RUNS AGAINST: a local clone of GcsSloop/AndroidNote. If you don't
# have one yet, run these first:
#
#   git clone https://github.com/GcsSloop/AndroidNote.git
#   cd AndroidNote
#
# Then paste this script. Every check is read-only — no mutations.

set +e
fail=0
ok()   { echo "ok:   $1"; }
miss() { echo "FAIL: $1"; fail=$((fail+1)); }

# Precondition: we must be inside a git working tree.
if ! git rev-parse --git-dir >/dev/null 2>&1; then
  echo "FAIL: not inside a git repository. cd into your clone of GcsSloop/AndroidNote and re-run."
  exit 2
fi

# 1. Repo identity
git remote get-url origin 2>/dev/null | grep -qE "GcsSloop/AndroidNote(\\.git)?\\b" \\
  && ok "origin remote is GcsSloop/AndroidNote" \\
  || miss "origin remote is not GcsSloop/AndroidNote (artifact may be from a fork)"

# 3. Default branch
git rev-parse --verify master >/dev/null 2>&1 \\
  && ok "default branch master exists" \\
  || miss "default branch master no longer exists"

# 4. Critical files exist
test -f "README.md" \\
  && ok "README.md" \\
  || miss "missing critical file: README.md"
test -f "CustomView/README.md" \\
  && ok "CustomView/README.md" \\
  || miss "missing critical file: CustomView/README.md"
test -f "CustomView/Advance/[01]CustomViewProcess.md" \\
  && ok "CustomView/Advance/[01]CustomViewProcess.md" \\
  || miss "missing critical file: CustomView/Advance/[01]CustomViewProcess.md"
test -f "AudioVideo/README.md" \\
  && ok "AudioVideo/README.md" \\
  || miss "missing critical file: AudioVideo/README.md"
test -f "Course/README.md" \\
  && ok "Course/README.md" \\
  || miss "missing critical file: Course/README.md"

# 5. Repo recency
days_since_last=$(( ( $(date +%s) - $(git log -1 --format=%at 2>/dev/null || echo 0) ) / 86400 ))
if [ "$days_since_last" -le 811 ]; then
  ok "last commit was $days_since_last days ago (artifact saw ~781d)"
else
  miss "last commit was $days_since_last days ago — artifact may be stale"
fi

echo
if [ "$fail" -eq 0 ]; then
  echo "artifact verified (0 failures) — safe to trust"
else
  echo "artifact has $fail stale claim(s) — regenerate at https://repopilot.app/r/GcsSloop/AndroidNote"
  exit 1
fi

Each check prints ok: or FAIL:. The script exits non-zero if anything failed, so it composes cleanly into agent loops (./verify.sh || regenerate-and-retry).

AndroidNote is a Chinese-language Android development learning resource repository documenting Android fundamentals, custom view implementation, audio/video processing, and practical development techniques. It combines Markdown documentation with runnable Java code examples covering Canvas graphics, Path operations, Matrix transformations, touch event dispatch, and multimedia handling. Hierarchical documentation structure with four main branches: CustomView/ (Base/ and Advance/ subdirectories containing numbered Markdown guides and Code/ with Java implementations like CheckView.java, SearchView.java), AudioVideo/ (multimedia protocol and codec documentation), Course/ (JitPack, PlantUML, Markdown guides), and ChaosCrystal/ (utility guides like ADB commands, AndroidStudio shortcuts). Each CustomView section pairs theory documents with corresponding code examples.

Android developers learning custom UI development (Canvas, Path, Matrix), intermediate developers understanding event handling and touch mechanics, and Chinese-speaking Android engineers seeking reference implementations and visual explanations with code samples.

This is an established educational resource repository with 16,716 lines of Java code and comprehensive documentation structure, but appears to be in maintenance mode rather than active development. The repository serves as a static learning reference with no visible CI/CD setup, test suites, or recent commits visible in the provided data—it is mature and stable for its intended educational purpose but not a production library.

Single-maintainer educational repository with no apparent test coverage, CI pipeline, or dependency management visible. The risk is minimal for learning purposes since it's not a dependency library, but content may become outdated without active maintenance. No breaking changes are expected since this is documentation-focused, not a versioned package.

No active development visible in provided data. Repository appears to be a completed educational resource maintained as a reference. The structure suggests comprehensive coverage of custom views (from coordinate systems through event dispatch) and audio/video fundamentals has been completed.

Clone the repository: git clone https://github.com/GcsSloop/AndroidNote.git. No build or installation required—this is a documentation and code reference repository. Open Markdown files in any editor or GitHub's native viewer. Java code examples (like CustomView/Advance/Code/CheckView.java) can be copied into an Android Studio project for reference or modification.

Daily commands: This repository is not executable. To use the code examples: (1) Copy Java files from CustomView/Advance/Code/ into an Android Studio project, (2) Read corresponding Markdown documentation files for context and explanation, (3) Modify examples to learn interactively. Alternatively, view Markdown files directly in any text editor or on GitHub.

• README.md — Entry point documenting the entire learning note structure across CustomView, AudioVideo, SourceAnalysis, and other domains with navigation links.
• CustomView/README.md — Core index for custom view learning materials; the largest and most detailed subject area with foundational concepts prerequisite to advanced topics.
• CustomView/Advance/[01]CustomViewProcess.md — Gateway document explaining the custom view lifecycle and process; essential for understanding all subsequent advanced custom view topics.
• AudioVideo/README.md — Index for multimedia learning materials covering protocols, codecs, and playback pipelines; foundational for audio/video module navigation.
• Course/README.md — Aggregates learning courses and tooling guides (PlantUML, JitPack, Markdown); referenced by contributors for documenting and publishing materials.
• ChaosCrystal/README.md — Quick-reference collection for development utilities (ADB, Android Studio shortcuts, UI units) used during daily Android development.
• SourceAnalysis/README.md — Index for framework source code deep-dives; demonstrates analysis methodology for understanding Android internals.

Add a New CustomView Learning Module

1. Create a numbered markdown file in CustomView/Advance/ following the naming convention [NN]TopicName.md (CustomView/Advance/[NN]TopicName.md)
2. Add entry point explaining prerequisites and learning objectives, referencing foundational docs from CustomView/Base/ (CustomView/Advance/[NN]TopicName.md)
3. Include code examples in CustomView/Advance/Code/ with corresponding .md documentation files (CustomView/Advance/Code/ExampleClass.java)
4. Update CustomView/README.md with link to new module in appropriate section (基础篇/进阶篇) (CustomView/README.md)
5. Reference diagrams in CustomView/Advance/Res/ if visual explanations are needed (CustomView/Advance/Res/diagram.jpg)

Add a New Audio/Video Topic

1. Create markdown file in AudioVideo/ with descriptive name (e.g., 音频处理管道.md or 编码优化.md) (AudioVideo/新topic.md)
2. Include flow diagrams in AudioVideo/image/ (reference existing 视频解码播放流程.jpg format) (AudioVideo/image/topic_diagram.jpg)
3. Explain protocol/codec specifications with reference to 常见流媒体协议.md and 常见音视频编码.md (AudioVideo/新topic.md)
4. Update AudioVideo/README.md with navigation link to new topic (AudioVideo/README.md)

Add a New Framework Source Analysis

1. Create SourceAnalysis/ComponentName.md analyzing a specific framework class or mechanism (SourceAnalysis/ComponentName.md)
2. Structure analysis with: Purpose → Source Code Flow → Key Implementation Details → Use Cases (SourceAnalysis/ComponentName.md)
3. Update SourceAnalysis/README.md with link and brief description of analyzed component (SourceAnalysis/README.md)

Add a New Quick Reference (ChaosCrystal)

1. Create markdown file in ChaosCrystal/ with practical tool reference (e.g., Gradle常用命令.md or Git技巧.md) (ChaosCrystal/工具名.md)
2. Format as quick lookup guide with sections, code blocks, and practical examples (ChaosCrystal/工具名.md)
3. Update ChaosCrystal/README.md with link to new reference (ChaosCrystal/README.md)

• Markdown (.md files) — Lightweight, version-controllable learning content with GitHub native rendering; enables collaborative editing and issue tracking for content quality
• Java code examples — Demonstrates actual Android framework APIs and custom view implementations; provides copy-paste-able reference for developers
• Diagram images (PNG/JPG/GLIFFY) — Visual explanations of complex concepts (SDL architecture, video pipelines, canvas transformations) improve comprehension beyond text alone
• GitHub repository structure — Centralized, searchable learning resource with automatic API documentation rendering; leverages Git history for content versioning and attribution

• Static markdown documentation vs. interactive tutorials
  • Why: Markdown is maintainable, version-controllable, and platform-agnostic
  • Consequence: Developers must self-drive learning; no adaptive difficulty or interactive qu

No hidden traps specific to this repository. It is pure documentation and reference code with no runtime dependencies, configuration files, environment variables, or external services required. Copy-paste Java examples directly into Android projects, but ensure your Android SDK API level matches the code's assumptions (not explicitly documented in provided data).

• Canvas Graphics & Drawing — Fundamental to CustomView/Advance/[02]Canvas_BasicGraphics.md—understanding drawRect, drawCircle, drawPath is the foundation for all custom UI rendering in Android
• Bezier Curves — Covered in CustomView/Advance/[06]Path_Bezier.md—essential for creating smooth, scalable curves and animations used in modern mobile UI design
• Matrix Transformations (2D/3D) — Documented in [09]Matrix_Basic.md and [11]Matrix_3D_Camera.md—core technique for efficient scaling, rotation, skewing, and perspective transforms in custom views without redrawing
• Touch Event Dispatch Chain — Detailed in [12]Dispatch-TouchEvent-Theory.md and [15]Dispatch-TouchEvent-Source.md—understanding dispatchTouchEvent, onInterceptTouchEvent, onTouchEvent is critical for interactive custom views
• MotionEvent & Multi-touch — Explained in [16]MotionEvent.md—interpreting ACTION_DOWN, ACTION_MOVE, ACTION_POINTER_DOWN and pointer tracking enables gesture recognition and multi-touch interactions
• Region & Hit Detection — Covered in [17]touch-matrix-region.md—efficient spatial testing for non-rectangular custom views requires Region or matrix-based point-in-shape algorithms
• Video Codec Standards (H.264, VP9, AV1) — Documented in AudioVideo/常见音视频编码.md—understanding compression formats and their trade-offs is necessary for multimedia app development and choosing appropriate codecs

• android/architecture-components-samples — Official Android architecture examples demonstrating modern Android development patterns and lifecycle handling complementary to CustomView focus
• square/android-times-square — Real-world custom view implementation (calendar widget) showing production-quality code and best practices for complex custom views
• JakeWharton/timber — Android logging library referenced in many real projects, useful for debugging custom view and event dispatch issues covered in this repository
• bumptech/glide — Image loading and caching library frequently used alongside custom views for efficient multimedia rendering in Android apps
• yanzhenjie/AVLoadingIndicatorView — Custom animated view library demonstrating Canvas/Path/Animation techniques documented in this AndroidNote repository

To work on one of these in Claude Code or Cursor, paste: Implement the "<title>" PR idea from CLAUDE.md, working through the checklist as the task list.

Complete missing OpenGL documentation series

The OpenGL directory only contains a README.md with no actual content. Given the repo's comprehensive structure for CustomView (19+ detailed markdown files), OpenGL deserves similar depth. This would provide valuable graphics programming education to complement the existing audio/video content.

• [ ] Create OpenGL/[01]OpenGL_Basics.md covering coordinate systems and rendering pipeline
• [ ] Create OpenGL/[02]Shaders_GLSL.md with vertex and fragment shader fundamentals
• [ ] Create OpenGL/[03]Texturing.md covering texture mapping and sampling
• [ ] Create OpenGL/[04]Lighting_Materials.md for realistic rendering
• [ ] Add supporting image directory OpenGL/image/ with diagrams for key concepts
• [ ] Update OpenGL/README.md with table of contents linking all new documents

Add missing touch event and gesture documentation in CustomView

The CustomView/Advance directory has numbered markdown files up to [19] but is missing [13] and [14], suggesting incomplete coverage. The gap appears between MotionEvent.md ([16]) and touch-matrix-region.md ([17]). These missing docs likely cover gesture recognition and event processing that are critical for custom view interactivity.

• [ ] Create CustomView/Advance/[13]GestureDetector_Advanced.md covering GestureDetector subclasses and custom gesture creation
• [ ] Create CustomView/Advance/[14]TouchEvent_Optimization.md covering VelocityTracker and performance best practices
• [ ] Verify numbering consistency and update CustomView/README.md navigation links
• [ ] Add example code snippets and reference images to CustomView/Advance/Code/ directory

Create comprehensive audio/video codec comparison table and decision guide

The AudioVideo directory contains 5 separate markdown files (常见封装格式, 常见流媒体协议, 常见音视频编码) but lacks a unified comparison framework. Creating a structured comparison matrix would help developers choose appropriate codecs for specific use cases.

• [ ] Create AudioVideo/codec-selection-guide.md with decision trees for choosing formats based on use case (streaming, storage, real-time, etc.)
• [ ] Create AudioVideo/comparison-tables.md with side-by-side codec performance metrics (bitrate, latency, hardware support, patent status)
• [ ] Add visual diagrams in AudioVideo/image/ showing codec family trees and protocol relationships
• [ ] Cross-reference existing files (常见音视频编码.md, 常见流媒体协议.md, 常见封装格式.md) from the new guide with anchor links

• Add test classes for code examples in CustomView/Advance/Code/ (currently none visible)—create JUnit/Espresso tests for CheckView.java and SearchView.java to verify custom view behavior
• Document Android API level requirements for each CustomView example—add @RequiresApi annotations to Java files and API level notes to corresponding Markdown files since no version constraints are visible
• Create English translations of key Markdown files in CustomView/Advance/ (at minimum [01]CustomViewProcess.md, [06]Path_Bezier.md, [12]Dispatch-TouchEvent-Theory.md) to expand audience beyond Chinese speakers

This is an Android learning notes repository with minimal security concerns. The codebase consists primarily of educational documentation (Markdown files), code examples, and educational resources. No dependencies file was provided for analysis, no hardcoded credentials were detected, and no dynamic code execution patterns (SQLi, XSS, etc.) are present given the static documentation nature. The main low-severity issues relate to external resource references in README files. Overall security posture is strong for a documentation/educational repository.

• Low · External Image Resource via HTTP — README.md. The README.md file references external images from Sina Weibo (ww1.sinaimg.cn) using HTTP protocol. This could expose users to MITM attacks and dependency on external services. Fix: Host images locally or use HTTPS URLs. Consider removing external dependencies for documentation.
• Low · External Links to Personal Blog — README.md. Multiple references to external personal blog (gcssloop.com) in README. While not a direct vulnerability, external links in documentation should be monitored for availability and security. Fix: Regularly verify external links for validity. Consider maintaining a mirror or backup of critical documentation.

LLM-derived; treat as a starting point, not a security audit.

• Open issues — current backlog
• Recent PRs — what's actively shipping
• Source on GitHub

Generated by RepoPilot. Verdict based on maintenance signals — see the live page for receipts. Re-run on a new commit to refresh.