felix021

美团 App 启动崩溃 - AlarmManager 500 上限未捕获 IllegalStateException

美团启动崩溃：AlarmManager 注册超过 500 上限未捕获异常

现象

打开美团 App 后短时间内主进程崩溃（FATAL EXCEPTION），重复启动可稳定复现。即使执行 pm clear com.sankuai.meituan 清除全部应用数据后，首次启动仍会立即崩溃。

设备环境

felix021

在 RTX 5060 Ti 16GB 上部署 Qwen3.6-35B-A3B（HauhauCS uncensored）的最佳实践

单卡 16GB 跑满血 35B MoE 的实测部署方案。 硬件：RTX 5060 Ti 16GB（Blackwell, sm_120）+ Ryzen 5 9600X 6 核 + 32GB DDR5。 测试时间：2026-06，llama.cpp commit 3292da0，CUDA 12.8 构建。

---

一、这套方案能达到什么效果

felix021

Deploying Qwen3.6-35B-A3B on an RTX 5060 Ti 16GB

This is a practical deployment note for running Qwen3.6-35B-A3B on a single RTX 5060 Ti 16GB with llama.cpp, including multimodal input.

Where to get the files

Useful Hugging Face sources:

• Distilled GGUF family used for this deployment: https://huggingface.co/reedmayhew/UD-2.0-Qwen3.6-35B-A3B-Claude-4.6-Opus-Reasoning-Distilled-GGUF

felix021

Box64 + binfmt_misc on arm64

Run x86_64 Linux binaries transparently on arm64 via Box64's dynamic recompilation + kernel binfmt_misc. No wrapper scripts, no box64 prefix — just run the binary directly.

Why

Tools like Android SDK aapt, zipalign, aidl only ship x86_64 binaries. With binfmt_misc registered, the kernel forwards any x86_64 ELF to Box64 automatically — build systems (Gradle, Make, etc.) work without modification.

Prerequisites

felix021

Building Android Apps on ARM64 with Box64 + binfmt_misc

Android SDK build-tools ship only x86_64 Linux binaries. On arm64 (rooted Android with Debian chroot, Raspberry Pi, other ARM64 SBCs), Box64 translates these via binfmt_misc -- making the entire toolchain transparent to any build system (Gradle, Bazel, Buck, or raw CLI).

After setup, no wrapper scripts, no box64 prefix, no build file changes needed. Just gradle assembleDebug and it works.

How It Works

Gradle (JVM, native arm64)

felix021

Error in user YAML: (<unknown>): mapping values are not allowed in this context at line 2 column 330

---
name: android-cli-apk-builder
description: Build Android APKs purely from the command line on arm64 (aarch64) without Android Studio or Gradle. Use when the user asks to build an APK manually, compile Android apps from CLI, set up a command-line Android build environment on arm64/aarch64, or mentions javac + aapt2 + d8 + apksigner workflow. Trigger keywords: build APK CLI, arm64 APK build, no Gradle, manual APK packaging, android build tools CLI, aapt2 box64.
---

Android CLI APK Builder (arm64)

Build Android APKs from the command line on aarch64/arm64 Linux (e.g., Debian chroot on rooted Android, Raspberry Pi, other ARM64 SBCs) without Android Studio or Gradle.

How It Works

felix021

# How to Download & Audit Chrome Extensions

## Method 1: Direct CRX Download via API

```bash
# Replace <EXTENSION_ID> with the target extension ID
EXT_ID="<EXTENSION_ID>"
curl -L -o extension.crx "https://clients2.google.com/service/update2/crx?response=redirect&prodversion=120.0.0.0&acceptformat=crx2,crx3&x=id%3D${EXT_ID}%26uc"

# Extract (CRX v3 is a zip with a header)

felix021

Android Root/VPN 隐藏方案：实现与局限

环境：OnePlus 15 (Android 16), Magisk 30.7, Shamiko v1.2.5

架构总览

App 检测请求
  ├─ Root 检测 → Magisk DenyList + HMA OSS + Shamiko (白名单模式)
 ├─ VPN 检测 → VPNHide 模块 (hook NetworkCapabilities)

felix021

Windows 10 关闭 Intel 自适应亮度/对比度 完整指南

问题现象

切换界面色彩（如深色↔浅色）时，屏幕亮度会自动调整。

根源分析

通常有多个源头，需逐一排查关闭：

1. Windows 自适应亮度（系统层面）

felix021

EasyTier Magisk 模块连接不稳定排查记录

问题现象

EasyTier VPN 连接每隔约 10 秒断开一次，表现为网络时通时断。

排查过程

1. 初步怀疑：监控脚本