The Uhale mobile app and a compatible digital photo frame control different parts of the photo sharing workflow. The mobile app selects and transmits photos or short video clips (up to 2 minutes per transfer), maintains sender-side History, and binds a mobile account to a display using a dynamic 48-hour pairing code. The physical frame displays delivered media, manages its native Gallery, and maintains the list of bound app accounts under Settings > Account Management.
Understanding this division prevents common operational misunderstandings. Deleting an app History record does not delete the photo delivered to the frame. Removing a sender from the frame touchscreen does not erase that person’s original phone library. The Uhale account model operates on an equal, flat basis without hidden family “Owner” roles that remotely control every setting on the display.
The App Is the Sending Side
The Uhale mobile app is the sender’s primary tool. It runs on a supported iOS or Android phone and allows a user to select media from the phone library for delivery to one or more compatible frames associated with that app account over 2.4GHz Wi-Fi.
App-side tasks include:
-
Downloading and configuring the official Uhale mobile application.
-
Binding a mobile app account to a compatible frame using a dynamic pairing code.
-
Selecting supported photos and short videos (up to 2 minutes) from the phone library.
-
Choosing the intended target frame.
-
Initiating delivery over encrypted LAN or stateless cloud relay paths.
-
Checking local task status in mobile History.
-
Deleting or clearing local History records on the mobile phone.
-
Resending an available History item.
-
Withdrawing an eligible delivered item while the History entry exists and the frame is online over 2.4GHz Wi-Fi.
Photo selection permissions are controlled strictly on the sender’s phone by iOS or Android operating systems. Granting photo access to the app allows selection within the app; it does not grant the physical frame direct access to the phone’s complete camera roll.
Official mobile companion app capabilities can be explored in the guide to official Uhale mobile application features.
The Frame Is the Receiving and Display Side
The physical frame receives delivered media and provides the local viewing experience. On current frame software, photos and videos stored in internal memory are managed through the native Gallery.
Frame-side tasks include:
-
Displaying the active slideshow rotation.
-
Reviewing photos and videos stored locally on the device.
-
Hiding an item from normal slideshow display without erasing it from storage.
-
Deleting selected local media permanently from internal flash storage.
-
Favoriting or organizing media into local albums.
-
Exporting supported media to external MicroSD cards (formatted to FAT32, recommended capacity up to 32GB) when physical hardware ports are available.
-
Reviewing and unbinding app accounts under Settings > Account Management.
-
Managing device-specific display, network, and system settings under Settings > System > About.
Exact hardware controls vary by OEM frame manufacturer. Screen brightness, physical ports, storage capacity, external media slots, speakers, and optional features should be verified in the product manual. Delivered media is stored and managed on the physical display after receipt.
Account Management Happens on the Frame
Bound mobile app accounts are reviewed directly on the touchscreen panel under Settings > Account Management. Removing an account revokes that binding’s ability to send additional content to the display.
Uhale operates on a flat account model without Master, Admin, Owner, Member, or Viewer family roles. Bound accounts interact on an equal, flat basis, and the frame itself has no conventional user login.
This account model has practical consequences: a sender cannot assume that the mobile app displays every other account bound to the frame. Display owners should use Settings > Account Management on the touchscreen to audit the full list of bound senders.
Unbinding an account is performed on the touchscreen panel under Settings > Account Management (with the explicit option to delete associated shared photos uploaded by that account). Access revocation and historical media deletion can be evaluated separately before confirmation.
Detailed account management guidelines are explained in the bound account management and privacy guidelines.
History Is Not a Remote Copy of Gallery
Uhale History belongs to the sender-side mobile app. The native Gallery belongs to the receiving frame. While both may reference the same delivered media item, they operate as completely separate records.
Deleting a History record removes local mobile History data while leaving the delivered frame photo in place in internal storage. Clearing History carries the exact same limitation. A sender who wants to recall a delivered item remotely should use Withdraw while the History entry remains available and the frame is online over 2.4GHz Wi-Fi.
Deleting from the native Gallery removes the selected frame copy from local flash memory but does not alter the sender’s original phone photo or mobile History record. Hiding an item keeps the file stored in internal memory while excluding it from active slideshow rotation.
The operational distinction can be summarized by the intended outcome:
-
Clean the mobile app task record only: Use History Delete or Clear.
-
Recall a sent item remotely from an online frame: Use History Withdraw.
-
Remove local media from internal frame storage: Use Gallery Delete.
-
Retain the local file but pause slideshow playback: Use Hide in Gallery.
No single deletion action should be interpreted without verifying whether it occurs in the mobile app or on the frame touchscreen.
Where Photo Routing Fits
The app initiates delivery and the frame receives it, while network placement determines the transfer route between them:
-
Same-LAN Direct Transfer: When the smartphone and frame share the same local 2.4GHz Wi-Fi subnet, the selected photo is transferred directly through an encrypted local network route without passing through external servers.
-
Encrypted Cloud Relay Transfer: When devices are on different networks, a stateless cloud relay server forwards the selected media payload to the frame. The relay holds the temporary payload in RAM and purges the file immediately after the frame confirms receipt.
Routing mechanisms do not alter task ownership: the sender selects the media inside the mobile app, while the delivered copy becomes frame-side media managed in the native Gallery.
What the App Does Not Remotely Control
The Uhale mobile app does not function as a universal remote manager for every frame feature. Device-side media in the native Gallery and the complete list of bound accounts under Settings > Account Management remain governed directly on the physical display.
The mobile app does not assign tiered roles within a household. A person who binds first does not receive a hidden “Owner” role, and subsequent senders are not restricted as “Viewers.”
Model-specific settings such as touchscreen sleep schedules, physical storage, hardware ports, and OEM firmware updates (checked under Settings > System > About) require local frame interaction. An active mobile app connection does not imply that every frame setting can be adjusted remotely.
When a frame is located in another home, remote senders can supply new media, but a local person must handle Wi-Fi credential updates, software notifications, storage management, or physical hardware questions.
What the Frame Cannot Do to the Phone
The frame cannot use its native Gallery to browse unsent photos on the sender’s phone. It receives explicitly delivered media rather than a live camera-roll connection.
Deleting a photo from the frame’s native Gallery does not erase the source image from the phone’s camera roll. Removing a bound app account under Settings > Account Management does not uninstall the mobile app, close the sender’s broader profile, or wipe mobile app History automatically.
This boundary protects the sender’s smartphone from frame-side management. The frame controls its local storage and account bindings; the phone controls its source library, app session, and mobile History records.
If an original photo needs to be deleted from the phone, that action must be completed through the phone’s camera roll controls. If an app profile should be closed, use formal account management workflows rather than treating frame unbinding as profile deletion.
The Web Portal Is a Third Interface
Uhale also provides an official Web Portal (https://uhale.zeasn.tv) for browser-based photo transfers. The Web Portal operates as a dedicated desktop interface and is engineered specifically for bulk image uploads (up to 500 photos per session; note that the Web Portal does not support video uploads).
A desktop browser is convenient for transferring large photo collections from computer drives, but it does not convert every frame setting into a web-controlled option. Users should sign out on shared computers after completing transfers.
Distinguishing between these three interfaces ensures clear technical reporting: specifying whether an observed behavior occurred in the mobile app, Web Portal, or frame touchscreen interface allows for rapid support resolution.
Use the Interface That Owns the Task
Three everyday scenarios clarify task ownership:
-
Accidental Send: If a sender selects the wrong photo, mobile app History is the first place to use Withdraw while the frame is online over 2.4GHz Wi-Fi. If the History entry has already been deleted, the frame holder can remove the photo directly through the native Gallery.
-
Access Revocation: If a phone is replaced or sending access should end, the physical frame owns the bound-account list. The display owner should use Settings > Account Management (with the explicit option to delete associated shared photos uploaded by that account) on the touchscreen panel.
-
Clearing Task Records: If a photo remains on the frame after a sender clears mobile History, the result is expected: the local app record was removed, not the frame copy. Further action belongs in the native Gallery or an active Withdraw workflow.
Match each task to its designated interface: select, send, and review sender records in the mobile app; display and manage local media in the native Gallery; audit and unbind accounts under Settings > Account Management; and use the Web Portal for bulk desktop photo uploads.
When a result needs verification, check where the data resides. Mobile History, phone originals, transit payloads, and frame storage operate under separate controls. Overall platform compliance standards and certifications are maintained under global platform compliance and safety certifications.
Product specifications are subject to change without notice. For the latest software details, please consult official platform documentation.