Frequently Asked Questions

S3 WiFiCom is a fan-made virtual-pet project for the LilyGO T-Display-S3. It combines Digimon-style raising, local and online battles, downloadable visual content, firmware updates, and D-Vault features.

No. S3 WiFiCom is an unofficial fan-made accessory and is not affiliated with, endorsed by, or produced by Bandai. Digimon and related characters belong to their respective rights holders.

The firmware targets the LilyGO T-Display-S3 LCD model. Do not install it on the older ESP32 T-Display, AMOLED, Pro, or another ESP32-S3 board unless that board is explicitly supported by a future release.

WiFiCom follows many DMC care and evolution ideas, but some training, battle, connection, roster, and interface behavior is custom or still being refined. The Manual identifies important known differences.

Use a current Chromium-based browser such as Chrome or Edge on desktop or Android. Browser flashing requires HTTPS, a working USB data cable, and permission to access the serial device.

A normal signed OTA update saves the game and updates the application without replacing the FFat content partition. A full browser recovery or manual erase can remove saved data, so allow the device to save and keep backups where possible.

Keep the device powered, reconnect with a known data-capable USB cable, and retry the browser installer. Do not interrupt an active D-Vault transfer or firmware write. If the device still boots, save the game before attempting recovery.

WiFiCom uses a 48×48 runtime canvas. Large VB artwork must be reduced to fit, while DMC-adapted artwork may intentionally occupy fewer pixels. On the small LCD, a compact sprite can look sharper and less crowded than artwork stretched to the edges.

The T-Display-S3 can make sprite colors appear washed out. Selected packs use a controlled saturation increase before RGB565 conversion so reds, purples, and other accents remain readable on the physical screen.

Yes. Supported content can be downloaded and managed from the device. Sprite packs must use the expected manifest, evolution data, 48×48 animation frames, palette limits, and packaged SVPK format.

Baby stages cannot battle, and later stages need sufficient energy or DP. Online battles also require working Wi-Fi, compatible content data, and an available opponent or valid room.

The project combines carefully processed material from multiple community artists and reference archives. Pack-specific source files and audit records should retain the creator name, source location, frame mapping, and any conversion performed for WiFiCom.

Keep the device powered and reconnect to the same network. Resume any recovery flow before starting another transfer, and do not reset, unpair, or overwrite the affected slot until both device and service confirm the final state.

Include the firmware version, hardware model, sprite-pack name, affected Digimon and animation, what you expected, what happened, and clear photos or video from the physical screen. Never include passwords, Wi-Fi credentials, room tokens, or private account data.

Name the pack, Digimon, and animation pose, then provide an on-device photo with Sprite Debug disabled. Visual issues are checked against source dimensions, fixed-frame transforms, transparency, palette limits, and the packed SVPK output.