<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title>分类：Android FrameWork - LT技术站</title><link>https://lautung.com/categories/android-framework</link><atom:link href="https://lautung.com/categories/android-framework/feed/categories/android-framework.xml" rel="self" type="application/rss+xml"/><description>纸上得来终觉浅，绝知此事要躬行！</description><generator>Halo v2.27.2</generator><language>zh-cn</language><image><url>https://lautung.com/upload/ChatGPT%20Image%202026%E5%B9%B47%E6%9C%8810%E6%97%A5%2002_45_40(1).webp</url><title>分类：Android FrameWork - LT技术站</title><link>https://lautung.com/categories/android-framework</link></image><lastBuildDate>Wed, 18 Nov 2026 04:46:12 GMT</lastBuildDate><item><title><![CDATA[Android Framework 实战全景：从开机链路、核心服务到窗口形态]]></title><link>https://lautung.com/archives/android-framework-in-practice</link><description><![CDATA[<img src="https://lautung.com/plugins/feed/assets/telemetry.gif?title=Android%20Framework%20%E5%AE%9E%E6%88%98%E5%85%A8%E6%99%AF%EF%BC%9A%E4%BB%8E%E5%BC%80%E6%9C%BA%E9%93%BE%E8%B7%AF%E3%80%81%E6%A0%B8%E5%BF%83%E6%9C%8D%E5%8A%A1%E5%88%B0%E7%AA%97%E5%8F%A3%E5%BD%A2%E6%80%81&amp;url=/archives/android-framework-in-practice" width="1" height="1" alt="" style="opacity:0;">Android系统服务链路排查需沿着init→system_server→核心组件（AMS/WMS/IMS）→合成层（SurfaceFlinger）→窗口形态的层级调试。开机链路中BootAnimation依赖zip未压缩、宽高与帧率配置正确，预装app需放在system/priv-app并白名单权限；PMS扫描包时需处理split apk与OTA遗留的可见性问题；AMS因锁持过长或广播队列溢出易致系统卡顿，需用dumpsys activity配合systrace追踪；WMS负责窗口层级管理，适配多屏需分离DisplayContent输入，自由窗口需声明resizeable并处理焦点跨屏问题，卡顿常因无效半透明层或频繁lockCanvas。Native层调试需CallStack日志，避免在线程中read / log，车机多屏需分别配置bootanimation.zip。构建系统使用Android.mk时要注意LOCAL_PATH模块路径依赖，LOCAL_SHARED_LIBRARIES链接冲突与芭芭拉调试包可见性适配。附服务速查表明确各服务职责（如PMS管安装扫描、IMS主输入分发）及核心排查指令（dumpsys window/PMS package）。适用场景包括系统定制、性能优化、app模块升级失败、输入异常及Native崩溃定位。]]></description><guid isPermaLink="false">/archives/android-framework-in-practice</guid><dc:creator>LTT</dc:creator><category>Android FrameWork</category><pubDate>Wed, 16 Sep 2026 06:21:51 GMT</pubDate></item><item><title><![CDATA[Android 图形显示系统：Canvas、Skia、Surface与SurfaceFlinger]]></title><link>https://lautung.com/archives/3B2pIH0c</link><description><![CDATA[<img src="https://lautung.com/plugins/feed/assets/telemetry.gif?title=Android%20%E5%9B%BE%E5%BD%A2%E6%98%BE%E7%A4%BA%E7%B3%BB%E7%BB%9F%EF%BC%9ACanvas%E3%80%81Skia%E3%80%81Surface%E4%B8%8ESurfaceFlinger&amp;url=/archives/3B2pIH0c" width="1" height="1" alt="" style="opacity:0;">Android图形系统通过四步实现应用页面到屏幕的渲染：由ViewRootImpl发起的绘制请求触发View树遍历，View重写onDraw生成Canvas命令描述图形。Canvas指令经Skia处理，可选择CPU光栅或GPU加速完成（OpenGL ES/Vulkan），输出至Surface Buffer。Surface作为生产端接口，通过BufferQueue轮换提交图形数据给结果器。最终由SurfaceFlinger聚合所有可见Layer的Buffer，经Hardware Composer合成后输出至屏幕。比利时系统各组件职责明确，WindowManager控制窗口层级与位置，SurfaceFlinger执行最终合成，Skia和RenderThread负责分不同后端实现渲染。硬件加速通过RenderNode记录可复用指令，分UI和Render线程协作提升效率。SurfaceView通过独立Surface绕过主View树绘制，适合视频解码等高帧率场景。需注意误区：Surface是动态Buffer队列，Canvas不直接操作屏幕，SurfaceFlinger仅负责合成不参与绘制。核心价值在于通过分层设计实现高扩展性与高效渲染，平衡CPU与GPU负载，确保多图层协同输出。]]></description><guid isPermaLink="false">/archives/3B2pIH0c</guid><dc:creator>LTT</dc:creator><enclosure url="https://lautung.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fzhcover-019f4a92-b2b9-75ec-bae8-a7f905e80046.jpg&amp;size=m" type="image/jpeg" length="33249"/><category>Android FrameWork</category><pubDate>Fri, 10 Jul 2026 05:51:25 GMT</pubDate></item><item><title><![CDATA[Android WAP联网]]></title><link>https://lautung.com/archives/android%E4%BB%A3%E7%A0%81%E4%B8%AD%E5%AE%9E%E7%8E%B0wap%E6%96%B9%E5%BC%8F%E8%81%94%E7%BD%91%E6%98%AF%E4%BB%80%E4%B9%88%E6%84%8F%E6%80%9D</link><description><![CDATA[<img src="https://lautung.com/plugins/feed/assets/telemetry.gif?title=Android%20WAP%E8%81%94%E7%BD%91&amp;url=/archives/android%E4%BB%A3%E7%A0%81%E4%B8%AD%E5%AE%9E%E7%8E%B0wap%E6%96%B9%E5%BC%8F%E8%81%94%E7%BD%91%E6%98%AF%E4%BB%80%E4%B9%88%E6%84%8F%E6%80%9D" width="1" height="1" alt="" style="opacity:0;">文章解析Android中WAP联网的历史背景与当前处理方式。早期因网络限制，应用需根据APN类型自动判断：若识别为CMWAP等WAP接入点，则通过10.0.0.172:80代理发送HTTP请求。现代Android系统通过ConnectivityManager、NetworkCapabilities等接口自动处理路由代理逻辑，普通应用无需手动配置APN或代理。硬编码旧APN（如cmwap）存在多运营商适配失效、国际网络异常、HTTPS拦截等问题，建议仅特殊场景（如运营商定制应用、企业专网、IoT设备）使用系统API主动配置网络连接与代理。现代开发应直接调用OkHttp等HTTP客户端发送HTTPS请求，并结合NetworkCallback监听网络状态变化，避免依赖APN名称或静态代理信息。]]></description><guid isPermaLink="false">/archives/android%E4%BB%A3%E7%A0%81%E4%B8%AD%E5%AE%9E%E7%8E%B0wap%E6%96%B9%E5%BC%8F%E8%81%94%E7%BD%91%E6%98%AF%E4%BB%80%E4%B9%88%E6%84%8F%E6%80%9D</guid><dc:creator>LTT</dc:creator><enclosure url="https://lautung.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fzhcover-019f4a57-6880-70e6-bf07-1f29df571400.jpg&amp;size=m" type="image/jpeg" length="25973"/><category>Android FrameWork</category><pubDate>Fri, 10 Jul 2026 04:46:39 GMT</pubDate></item><item><title><![CDATA[Android ROM 开发模块划分]]></title><link>https://lautung.com/archives/Nn9x9jB4</link><description><![CDATA[<img src="https://lautung.com/plugins/feed/assets/telemetry.gif?title=Android%20ROM%20%E5%BC%80%E5%8F%91%E6%A8%A1%E5%9D%97%E5%88%92%E5%88%86&amp;url=/archives/Nn9x9jB4" width="1" height="1" alt="" style="opacity:0;">Android ROM开发涵盖系统界面定制、硬件适配和底层优化三大层级的72个核心模块。系统应用层（Launcher/SystemUI/Settings）负责用户可见的交互界面，Framework层（Activity/PMS/Window等）控制系统核心逻辑，Native层（SurfaceFlinger/Binder/Audio等）实现基础驱动的C++封装，HAL层（ Camera/Audio/Display等）作为硬件接口翻译器，Kernel层（驱动/调度/内存）处理底层数据吞吐，Device配置层（init/sepolicy overlay等）完成机型适配，Build流程生成多分区镜像文件，OTA确保安全升级。开发需遵循"界面→框架→配置→底层"进阶路径，测试认证确保系统合规。商业团队按系统应用、框架、BSP（硬件适配）、多媒体、连接、性能功耗、安全、OTA测试等方向细分职能，形成完整开发闭环。]]></description><guid isPermaLink="false">/archives/Nn9x9jB4</guid><dc:creator>LTT</dc:creator><enclosure url="https://lautung.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fzhcover-019f032d-4ec5-75e8-a3ac-4bfe64f489d6.jpg&amp;size=m" type="image/jpeg" length="27587"/><category>Android FrameWork</category><pubDate>Fri, 26 Jun 2026 09:13:12 GMT</pubDate></item><item><title><![CDATA[Android Binder：为什么它是 Android 系统的“通信骨架”？]]></title><link>https://lautung.com/archives/eS4DgBhy</link><description><![CDATA[<img src="https://lautung.com/plugins/feed/assets/telemetry.gif?title=Android%20Binder%EF%BC%9A%E4%B8%BA%E4%BB%80%E4%B9%88%E5%AE%83%E6%98%AF%20Android%20%E7%B3%BB%E7%BB%9F%E7%9A%84%E2%80%9C%E9%80%9A%E4%BF%A1%E9%AA%A8%E6%9E%B6%E2%80%9D%EF%BC%9F&amp;url=/archives/eS4DgBhy" width="1" height="1" alt="" style="opacity:0;">在 Android 里，我们每天都在用 Binder。 你调用 startActivity()，背后会走 Binder； 你调用 getSystemService()，背后会拿到 Binder 代理； 你访问 ActivityManagerService、PackageManagerService、]]></description><guid isPermaLink="false">/archives/eS4DgBhy</guid><dc:creator>LTT</dc:creator><enclosure url="https://lautung.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=%2Fupload%2Fzhcover-019c7ab5-4670-74d9-bf2b-fd6e089bb9b5.jpg&amp;size=m" type="image/jpeg" length="31758"/><category>Android FrameWork</category><pubDate>Thu, 25 Jun 2026 04:14:50 GMT</pubDate></item></channel></rss>