FakeLocation

中文

FakeLocation是面向Android的位置模拟调试工具，适合开发者在授权环境中验证定位功能。本页提供FakeLocation下载的官方GitHub入口，说明1.5.2版本、安装步骤、Android兼容范围及更新变化，并区分NOROOT与ROOT模式的权限条件，帮助你先确认设备和用途，再开展可恢复的定位测试。

FakeLocation下载前：明确定位调试目标

Fake Location 的官方 README 将它定义为 Android 开发调试工具，面向软件开发、游戏开发、功能调试与应用兼容性测试中的位置信息场景。它列出摇杆移动、路线模拟、位置快速切换、位置保存和位置更新频率等功能。它不是所有定位应用均可通用替换的承诺；测试结果需要结合你自己的设备、系统和被测应用判断。

一个可复核的测试可以先记录三件事：被测功能应如何响应位置变化、准备输入什么位置或路线、测试结束怎样恢复原有环境。例如在自有应用中测试地图标记更新时，先比较固定测试点，再检查移动路线，能更容易区分单点输入和连续位置变化造成的结果。这里是测试设计建议，不是已经在本机运行软件的记录。

官方 README 区分 NO ROOT 与 ROOT 两种模式，并列出 Android 5–17 的支持范围；这是发布者声明，不代表每个系统定制版本、权限组合与机型都经过本站验证。请先评估 NO ROOT 是否满足你的测试需求，并且只对自己有权调试的应用与环境开展测试。

原创事实型示意图，依据：官方资料。

Android 官方 APK 下载与安装步骤

1. 打开 FakeLocation 官方 GitHub 1.5.2 发布页，核对发布者 Lerist、版本 1.5.2 和附件 FakeLocation_CN_v1.5.2_1702.apk。榜单中的第三方旧 APK 链接没有被用于本页下载来源。
2. 使用该发布页的固定 GitHub APK 入口，或从发布页进入 官方应用分发页。分发页本次可见版本同为 1.5.2，显示大小 32.7M；GitHub 附件元数据给出的精确大小为 34,317,784 字节。页面单位显示与精确字节值分别保留，不把下载体积当作安装后占用空间。
3. 下载完成后，从 Android 的下载列表或文件管理器打开 APK。按设备提示核对应用名称、来源、兼容条件与安装状态；若设备要求设置当前下载应用的安装来源权限，先理解提示再处理。出现签名冲突或来源不一致时，停止并检查原有安装和官方文件，而不是强行覆盖。
4. 首次打开时先阅读使用条款和模式说明，再在已授权的测试环境中评估 NO ROOT 模式。安装 APK 与授予高权限是不同的决定；本页不要求为完成安装而获取 ROOT 或修改系统安全策略。
5. 正式测试前记录 Android 版本、软件版本、测试目标与恢复方法，用一个简单测试点确认流程，再扩大到路线用例。已有安装时先保留必要配置和账号恢复资料，当前页面没有提供可保证通用的覆盖安装或数据迁移结论。

官方 README 特别说明 ROOT 模式需要相应权限，并涉及将 SELinux 切换到宽容模式，会降低设备安全性；不具备相应知识时应避免采用这一模式。这里只解释功能条件，不提供获取 ROOT、关闭系统保护或绕过其他应用限制的步骤。

原创事实型示意图，依据：官方资料。

版本更新：1.5.2 的当前改动与维护状态

本次官方 GitHub 发布页所列稳定版本为 1.5.2，发布时间为 2026-08-19，不是预发布版本。官方分发页也显示 1.5.2。以下五项属于该版发布说明“更新日志”中的当前条目：

• 新增 Android 17 适配，发布说明同时提到 FL-Xposed 已同步更新。这不表示普通 APK 安装后自动获得额外模块，也不是所有机型兼容的保证。
• 新增路线采集功能。准备连续位置用例时，可结合该项功能组织测试资料；本次没有运行软件验证其采样方式或精度。
• 新增经纬度位置导入。整理输入数据时，应先确认格式与坐标来源，再在当前应用中核对识别结果；发布说明没有给出完整格式规范，不能自行编造字段格式。
• 优化位置与路线搜索。
• 优化路线规划。搜索与规划是官方发布者描述的改进，本页没有据此写入速度提升比例或性能测试结论。

发布说明另外列有“往期更新”，包括命令行外部调用、部分设备重启修复等。这些是历史项目，不能全部写成 1.5.2 新增功能。仓库同时标记于 2026-08-20 归档；归档与已有附件可访问是两件事，本页不承诺后续更新或支持时限。选择版本前应再次查看官方发布页与分发页。

原创事实型示意图，依据：官方资料。

常见问题（FAQ）：权限、兼容与来源

FakeLocation安装后，NO ROOT 和 ROOT 的功能是否完全相同？

不能这样推定。README 明确区分两种运行模式，ROOT 功能依赖更高权限，且涉及会降低安全性的 SELinux 条件。先选择满足授权测试需求的较低权限方式；如果不满足，不应直接把所有保护关闭来追求相同效果。具体功能范围以当前版本界面和官方说明为准。

Android 5–17 是不是每台手机都能正常运行的保证？

这是当前 README 的支持范围声明。官方使用条款也说明软硬件环境有差异，不能保证所有情况下都达到预期。请记录系统、机型、运行模式、准确错误与复现步骤，再查当前官方帮助；不要仅凭一个失败就把原因确定为缺少 ROOT。

在哪里确认正版文件，GitHub 的 SHA-256 是本站验算的吗？

使用本页列出的官方仓库与分发入口。GitHub 附件元数据声明 SHA-256 为 5d2a2bad585e3d50c38621a002bcf7a8e0dcf5448fc045f58619fe7a491eaea1。它是发布来源提供的摘要，本次没有下载 APK 正文并重新验算，也未安装、运行或独立安全扫描。

在 GitHub 可下载，是不是表示开源且所有功能免费？

不能据此判断。当前仓库没有给出可确认的开源许可证，作者提供独立使用条款；历史 FAQ 提到专业版套餐，但本次没有核对当前价格与完整免费功能范围。不要把公开 APK 附件等同于无限制授权。

能把它用于签到、配送或网约车的位置替换吗？

作者的使用条款将软件限定为开发人员或专业人士的调试工具，明确限制打卡、签到、网约车、配送等用途。本页围绕授权开发测试提供 FakeLocation下载与安装资料，不提供绕过其他服务位置校验的操作指南。

原创事实型示意图，依据：官方资料。

使用 FakeLocation 下载入口准备 Android 定位调试时，请再次确认 1.5.2 版本与测试授权，并留意仓库已归档。优先评估 NO ROOT 是否满足需要；ROOT 模式及相关 SELinux 条件会降低设备安全性，应先理解影响。

English

Download FakeLocation 1.5.2 for Android from its official GitHub release. Review setup, NO ROOT mode, route testing, update notes and device requirements.

FakeLocation: define the location test before downloading

The official Fake Location README describes an Android development and debugging tool for location-related software development, game development, feature checks and compatibility testing. It lists joystick movement, route simulation, quick location switching, saved positions and adjustable location-update frequency. Those features do not establish universal compatibility with every location-aware application; results depend on the device, system and app under test.

A reproducible test starts with three records: how the feature should respond to a position change, which test point or route will be supplied and how the original environment will be restored. In an application you own, for example, compare fixed test points before checking a moving route. That helps separate single-point behavior from continuous changes. This is test-design guidance, not a report of running FakeLocation on this machine.

The README distinguishes NO ROOT and ROOT modes and states support for Android 5–17. That is a publisher statement rather than independent validation of every device, vendor build and permission combination. Evaluate whether NO ROOT meets your needs first, and test only applications and environments you are authorized to inspect.

Original factual illustration based on official documentation.

Android APK download and installation steps

1. Open the official GitHub 1.5.2 release. Check publisher Lerist, version 1.5.2 and asset FakeLocation_CN_v1.5.2_1702.apk. The spreadsheet's old third-party APK was not used as a download source.
2. Use the release's fixed GitHub APK link, or follow its official distribution page. That page currently displays 1.5.2 and 32.7M; GitHub asset metadata gives 34,317,784 bytes. These are retained as source-specific size representations. Transfer size is not installed storage.
3. After downloading, open the APK from Android's download list or file manager. Review the device's application name, source, compatibility and installation prompts. If Android requests an installation-source setting for the downloader, understand that setting before changing it. Stop on a signature conflict or inconsistent source and check the existing installation and official file rather than forcing an overwrite.
4. Read the terms and mode descriptions on first use, then evaluate NO ROOT within an authorized test environment. Installing an APK and granting privileged access are separate decisions. This guide does not require obtaining ROOT or changing system security policy to complete installation.
5. Before a real test, record the Android version, app version, test goal and recovery method. Begin with one simple point before extending to routes. Preserve necessary settings and account-recovery information before updating an existing installation; the reviewed pages do not establish a universal in-place upgrade or data-migration procedure.

The official README warns that ROOT mode requires privileged access and changing SELinux to permissive, reducing device security. Avoid that mode without the necessary expertise. This section explains requirements without providing instructions to obtain ROOT, disable protections or evade another application's restrictions.

Original factual illustration based on official documentation.

Release updates: current 1.5.2 changes and maintenance status

The official GitHub stable release reviewed here is 1.5.2, published on 2026-08-19, and is not marked prerelease. The official distribution page displays the same version. These five points belong to its current change list:

• Android 17 adaptation is added, with the notes also reporting a corresponding FL-Xposed update. That does not mean installing the normal APK automatically installs another module or guarantees every device's compatibility.
• Route capture is added. It can inform how you organize continuous-position test material, but this research did not run the feature or measure its sampling behavior or accuracy.
• Latitude/longitude position import is added. Check input format and coordinate provenance in the current application before relying on imported results. The release notes do not provide a complete format specification, so none is invented here.
• Position and route search are improved.
• Route planning is improved. These are publisher descriptions; no speed percentage or benchmark is inferred.

The release page separately lists historical changes, including external command-line control and some device-restart fixes. They are not all presented as new in 1.5.2. The repository is also marked archived on 2026-08-20. Archive status and access to existing assets are separate facts; future updates and support duration are not promised. Recheck the official release and distribution pages before selecting a version.

Original factual illustration based on official documentation.

FAQ: permissions, compatibility and official files

Do NO ROOT and ROOT provide exactly the same functions after installation?

That should not be assumed. The README distinguishes the modes, and ROOT features depend on privileged access and SELinux conditions that reduce device security. Begin with the lower-permission option that meets an authorized test need. If it does not, disabling every protection is not an appropriate default. Check the current app and publisher guidance for exact feature boundaries.

Does Android 5–17 support guarantee operation on every phone?

It is the current README's support statement. The author's terms also acknowledge differences in hardware and software and do not guarantee the expected result in every case. Record the device, system, mode, exact error and reproduction steps before consulting current help. A failed test alone does not prove ROOT is missing.

Where can I identify the official file, and was its SHA-256 independently calculated here?

Use the official repository and distribution entry linked on this page. GitHub asset metadata declares SHA-256 5d2a2bad585e3d50c38621a002bcf7a8e0dcf5448fc045f58619fe7a491eaea1. This is the source's declared digest. The APK body was not downloaded and rehashed, installed, run or independently security-scanned.

Does a public GitHub download mean open source and fully free use?

It does not establish either. No confirmed open-source license was supplied in the reviewed repository, and the author publishes separate terms. Historical FAQ material mentions professional packages, but current prices and the complete free-feature scope were not verified. A public asset is not unrestricted authorization.

Can it replace location for attendance, delivery or ride-hailing services?

The author's terms limit it to debugging by developers or professionals and explicitly restrict those scenarios. This page provides FakeLocation download and installation information for authorized development testing; it does not provide a guide to evading another service's location checks.

Original factual illustration based on official documentation.

For Android location debugging with a FakeLocation download, recheck version 1.5.2, your test authorization and the repository’s archived status. Evaluate NO ROOT first, and understand the device-security implications of ROOT and SELinux before choosing a mode.