Skip to content

Releases: samson910022/pixelify-google-photos-modern

Pixelify Infinity v1.0.4

Choose a tag to compare

@samson910022 samson910022 released this 17 Jul 09:26

Pixelify Infinity v1.0.4

Android 17 Build spoof hardening release (versionCode 5).

[1.0.4] - 2026-07-17

Fixed

  • Hardened Android 17+ device spoofing after field writes still failed on some devices with 1.0.3.
  • On Android 17 (API 37+), ART can block Field.set on public static final android.os.Build / Build.VERSION fields with IllegalAccessException. That restriction is an ART field-write limitation; it is not caused by libxposed API 101.
  • Multi-strategy Build static writes (success = post-write readback match):
    • clear only the Java FINAL bit on the real reflected access-flags int (preserve ART/hidden-API high bits), then reflection Field.set
    • multi-variant Unsafe static puts (putObject / putReference / volatile forms, alternate static bases)
    • JNI fallback via libpixelify_build using SetStatic*Field + readback (no heuristic ArtField memory patching, which could corrupt ART metadata)
    • best-effort hidden-API exemption before reflective access
  • Secondary path: intercept android.os.SystemProperties.get for ro.product.* / fingerprint-related keys when Xposed hooks are available.
  • Apply device spoof early on onPackageLoaded and re-apply on onPackageReady.
  • VERIFY failures continue to surface via Toast and a high-importance notification (once per process) instead of silent log-only failure; optional Android-version spoof keys are included in VERIFY.

Notes

  • This release does not claim universal success on every Android 17 build/ROM. Some firmwares may still leave Build fields unchanged after all write strategies; check logcat tag Pixelify for Loaded libpixelify_build / via Field.set / via Unsafe / via JNI / VERIFY FAIL and the on-device VERIFY alert if the Google Photos model string does not change.
  • The native library is loaded from the module nativeLibraryDir first, then extracted into the host process codeCacheDir when needed, because under LSPosed the code runs inside Google Photos and bare System.loadLibrary usually fails.

Changed

  • Bumped version to 1.0.4 (versionCode 5).

Verification

Release signing certificate SHA-256 fingerprint:

37:18:6E:5C:26:94:E5:53:E5:FA:B1:F7:78:7C:04:DB:CD:43:84:AB:84:96:3E:60:BE:9C:3C:CB:6B:A9:07:B1

SHA-256 Checksums

0023fd6e5b44b0b9e20253b08fb19afd933d5052c8c38f021dddbd37562f8a12  pixelify-photos-v1.0.4.apk
e62e759507de1ad0dad0b52848820ed44d31f917f438f2e82034622da7a96f4a  pixelify-photos-v1.0.4.aab

Pixelify Infinity v1.0.2

Choose a tag to compare

@samson910022 samson910022 released this 16 Jul 15:49

Pixelify Infinity v1.0.2

Branding and identity release (versionCode 3).

Changed

  • Renamed the user-facing display name to Pixelify Infinity (Traditional Chinese launcher label: Pixelify 無限解鎖) to better distinguish this module from the legacy Pixelify Google Photos package and to match the infinity/unlocker branding.
  • Replaced the launcher icon with a new adaptive icon (infinity + keyhole, four-color geometry).
  • Added a project banner image for the README landing page.
  • Bumped version to 1.0.2 (versionCode 3).

Verification

Release signing certificate SHA-256 fingerprint:

37:18:6E:5C:26:94:E5:53:E5:FA:B1:F7:78:7C:04:DB:CD:43:84:AB:84:96:3E:60:BE:9C:3C:CB:6B:A9:07:B1

SHA-256 Checksums

3184bec493483b49e58441bb7edf4bd2fc1804a5833944f836898fed75af56c4  pixelify-photos-v1.0.2.apk
fd35e7219a1f4d6ca606ca08ddd42cc365e7626180e4d735bb472b639b5228a6  pixelify-photos-v1.0.2.aab

Pixelify Photos v1.0.1

Choose a tag to compare

@samson910022 samson910022 released this 16 Jul 15:16

Pixelify Photos v1.0.1

Patch release restoring device-model spoofing on Android 17+ (versionCode 2).

Fixed

  • Restored Build property spoofing on Android API 37+; the previous hard skip was not required by libxposed API 101 and prevented model-name spoofing (for example the Google Photos UI still showed the real device model such as Pixel 6 Pro).
  • Selecting device None (or an empty feature list) now fully pass-through for feature flags, matching module-off behaviour instead of forcing all Pixel flags to false.

Changed

  • Bumped version to 1.0.1 (versionCode 2).
  • Documented that Android 17+ Build spoofing is attempted with logged failures rather than disabled for safety.
  • Added post-write verification logs for spoofed Build fields to aid device-side diagnosis.

Verification

Release signing certificate SHA-256 fingerprint:

37:18:6E:5C:26:94:E5:53:E5:FA:B1:F7:78:7C:04:DB:CD:43:84:AB:84:96:3E:60:BE:9C:3C:CB:6B:A9:07:B1

SHA-256 Checksums

8d33b65d05f64575bade730d17fc6783afa986084a9d49a3ae6ee1283ac48641  pixelify-photos-v1.0.1.apk
74b98e219c3f8df355bb909f7ef9c6e188e54867a0da44d2e2275e739ef2d0d6  pixelify-photos-v1.0.1.aab

CI on f421b7b: https://github.com/samson910022/pixelify-google-photos-modern/actions/runs/29509782371

Pixelify Photos v1.0.0

Choose a tag to compare

@samson910022 samson910022 released this 16 Jul 12:02

Pixelify Photos v1.0.0

First release under the independent identity io.github.samson910022.pixelifyphotos.

Changed

  • Adopted the independent application ID io.github.samson910022.pixelifyphotos
  • Reset independent versioning to 1.0.0 (versionCode 1)
  • Migrated to the modern libxposed API 101 module format
  • Established a stable release certificate and public fingerprint
  • Moved update, support, and release links to independently maintained locations
  • Added fail-closed signer verification for official publication builds
  • Documented partial Android API 37+ support where Build-property spoofing is disabled for safety

Verification

Release signing certificate SHA-256 fingerprint:

37:18:6E:5C:26:94:E5:53:E5:FA:B1:F7:78:7C:04:DB:CD:43:84:AB:84:96:3E:60:BE:9C:3C:CB:6B:A9:07:B1

SHA-256 Checksums

e968800b0893271740f4a2081a736284c7f0424b09c6cc78acb9ab63208ff39a  pixelify-photos-v1.0.0.apk
d2c8731357a51c944bed0684434426e6c8601f2baf72d27ee19220cbfbc863d7  pixelify-photos-v1.0.0.aab

Earlier development history from the legacy package line is archived in docs/LEGACY_CHANGELOG.md.