Which symptom should you troubleshoot first?
- The camera or menus visibly stutter: start with the device checks and the controlled settings comparison below. Record whether this happens immediately or only later in a session.
- The view is smooth, but actions arrive late or characters jump back: check the network branch. Lowering graphics cannot establish whether a connection or server problem is resolved.
- Starts smoothly, then dims or slows as it warms: pause and follow the heat branch. Timing suggests a thermal or power-related factor but does not prove one.
- Returns to the home screen: use crash troubleshooting. A whole-device restart is a different failure and needs the device maker if it repeats.
- Battery drains quickly without stutter: compare session length, screen brightness, charging state, and Battery usage in Settings. Battery drain alone does not identify a game bug.
Before testing, note your device model, OS/game version, free storage, battery level, power-saving mode, network type, and starting temperature condition. “Cool to touch” is an observation, not a measured internal temperature.
What can Android and iPhone users safely check?
Android: use the device's Storage screen to inspect space, Google Play or the official install store for game updates, and the supported system update screen. Google warns that low free storage can cause problems; its slow-device guide also explains that menus vary by manufacturer. Move already-backed-up personal media if needed, keeping game data intact.
iPhone/iPad: inspect Settings → General → iPhone/iPad Storage, check the App Store for updates, and check Settings → General → Software Update. Apple's slow-device guide explains that Low Power Mode reduces some functions and that routinely force-closing all apps can itself slow reopening. Close the game when unresponsive; do not clear every app as a recurring performance ritual.
Restart once if the device has been behaving abnormally. Stop an optional screen recording or other heavy task for one comparison, then restore it if unrelated. If a power-saving mode is active, record it. On a cool device with sufficient battery, you may briefly compare normal mode through the supported Battery controls, then restore your preference. Skip this comparison if the battery is low or the phone is already hot.
Use only settings exposed by your model. There is no universal Android “performance mode,” refresh-rate control, or battery-health menu. A display refresh-rate setting is not evidence that the game renders at that rate. Check compatibility on the game's official store listing; settings cannot establish support for an unsupported device.
How do you compare settings without an invented preset?
The installed game's graphics options have not been verified for this guide. The following are conditional tests, not claims that Origin has a particular menu, resolution slider, or frame-rate option.
- Screenshot the current settings. Choose a repeatable, low-risk scene, such as the same walking route if accessible. Keep the network, brightness, charging state, and starting device condition similar.
- If a frame-rate limit exists: compare the current choice with one lower supported choice. Look for steadier movement and less heat, accepting that the maximum motion rate may be lower. No particular FPS target is recommended for every phone.
- If a graphics quality or render-resolution control exists: lower one level for a separate test. Check text readability, target visibility, and control response as well as stutter. Skip controls that are absent; do not edit hidden configuration files.
- Use the same short observation window, for example 3–5 minutes, for each ordinary test. Stop earlier for heat or instability. If a built-in FPS display exists, record it; otherwise describe visible stutter without inventing a number or downloading a monitoring tool.
- Write down old value → new value → scene and duration → result. Restore the old value after a failed comparison. Keep a change only if the benefit repeats under similar conditions and visibility remains acceptable.
A cooler starting device, a less busy scene, or a different server session can change the result. One smooth run is not a benchmark. If the same stutter persists after the device checks and available single-setting tests, stop and report it rather than lowering everything blindly.
What if performance worsens as the phone heats up?
Pause play, move out of direct sunlight, and let the device cool naturally. Avoid testing while charging if charging is contributing to warmth. Do not use ice, a freezer, or methods that bypass the device's thermal protections.
Apple's temperature guidance confirms that excess heat can dim the display and reduce performance. If an iPhone/iPad shows a temperature warning, turn it off, move it to a cooler environment, and allow it to cool. For Android, follow your model's manufacturer instructions; Apple-specific menu paths and temperature limits are not universal Android guidance.
Stop/escalate: do not keep reproducing overheating. Repeated temperature warnings, unexpected shutdowns, or problems across multiple apps need the device maker. On a cool device where only Origin still stutters, report the game-specific reproduction to its developer. Warmth alone does not prove defective hardware.
What if it is network lag rather than low frame rate?
If camera movement stays smooth but actions are delayed, note any disconnect/error code and compare official service notices through Bugs and Errors. Stop other large transfers on your own connection for a short test. If practical, compare trusted Wi-Fi with mobile data, accounting for data charges; use the same activity and record both results.
A better result on one connection narrows the investigation but does not prove the game server is healthy. If several apps are slow only on that network, contact the network provider. If Origin alone repeats the delay on both connections, send the time, region, and symptoms to game support. Do not install a “ping booster” or change security settings for this comparison.
What evidence helps support reproduce the problem?
Use the game's official support entry if it opens, or the developer contact/App Support link on the official store listing. Provide:
- Device model, OS and game build if visible, available storage, and install source.
- The exact scene/activity, time and time zone, server/region, and minutes until the symptom appears.
- Starting battery level, charging state, power mode, brightness, network type, and any dimming or temperature warning.
- Before/after setting screenshots, each comparison result, and whether other apps also slow or close. State when an option or measurement is unavailable.
A short recording can help, but recording adds load: label it and mention if performance differs without it. No Origin mobile log location is verified here. Ask official support for collection instructions rather than enabling developer modes or installing an extractor. Share diagnostic files privately, with personal identifiers and account tokens removed.
Mobile performance FAQ
What is the best 60 FPS preset?
This guide has no verified device benchmarks or confirmed Origin menu inventory. Use the comparison method with the options actually shown on your device; do not treat a universal preset as a tested result.
Should I clear app data or install a RAM cleaner?
No. Do not delete game data/settings, reset the phone, sideload a modified client, or install a cleaner/FPS unlocker. These are not part of this procedure and may lose access or introduce new problems.
Should I keep testing after a temperature warning?
No. Stop and follow the device maker's cooling guidance. Repeated warnings or shutdowns warrant device support, not longer game benchmarks.
Official sources and related diagnostic paths
Google: slow Android device · Apple: slow iPhone/iPad · Apple: temperature and reduced performance
These sources support device-level checks. The controlled comparisons above are general diagnostic procedures, not verified Origin workarounds or measured performance presets.
Bugs and Errors hub · App closes at launch · Resource update failures (unverified archive) · Login and connection errors (unverified archive)