Livingstone Toolkit

Create Android boot animations with confidence.

Livingstone helps modders import, build, preview, diagnose, repair, and export boot animation packages while keeping recovery-first guidance visible.

747CRYA-hosted import packages
747local demo preview images
15protected admin work areas
24/7heartbeat and maintenance route

Workflow

From source files to install-ready package

The product page explains the user workflow exactly enough that a new Android modder can orient themselves.

1Import

Open a ZIP, source frames, or static artwork.

2Prepare

Normalize size, order, folders, timing, and preview state.

3Diagnose

Review desc.txt, frame count, dimensions, and path risks.

4Repair

Apply guided fixes and keep backup/recovery notes visible.

5Export

Create a clean package or QMG-aware handoff where supported.

Export confidence

Know what you are about to create

Livingstone should make the export choice understandable before a user saves, shares, submits, or prepares an install.

OK

Preview motion, dimensions, and brightness before export.

OK

Read Package Doctor notes for folder shape, desc.txt, frame order, and missing shutdown context.

OK

Choose whether the result is a free preview, clean export, store submission, or device-specific handoff.

OK

Keep rollback and support evidence visible before risky or root-adjacent steps.

Output lanes
Free previewUseful for testing visual timing and layout before paying for clean exports or submitting a pack.
Clean exportWatermark-free output stays separate from Premium and Store purchases so the promise is clear.
Store submissionAdds creator credit, preview media, compatibility labels, ownership notes, and review evidence.
Support reportBundles enough context for troubleshooting when export, preview, install, or compatibility fails.
Device handoffSamsung/QMG or root-adjacent guidance needs compatibility notes and recovery-first wording.

Recovery-first guidance

Power features should never feel casual

The public Toolkit page should make it obvious that CRYA values backups, user consent, and evidence over risky one-click promises.

Backups before risk

Root, module, cleanup, and device-specific actions should remind users what to save first.

Safety
Plain-language reports

Errors should explain what failed, why it matters, and the next safest action.

Package Doctor
Compatibility notes

Device, Samsung/One UI, resolution, boot/shutdown behavior, and QMG limits should travel with the pack.

Device
Support-ready evidence

Screenshots, report text, app version, package source, and device context reduce guessing.

Support
Package Doctor

Plain-language reports for missing parts, bad timing, folder mistakes, dimensions, frame sequence problems, and risky assumptions.

Diagnostics
Samsung-aware guidance

Boot and shutdown media paths, model-family notes, QMG limits, and safer language around root/system changes.

Device safety
Clean exports

Watermark-free credits stay separate from Premium subscriptions so users understand exactly what they purchase.

Play-safe
Creator handoff

Finished work can move toward store submission with previews, creator credit, compatibility labels, and quality checks.

Store-ready