System management is Origin OS 6’s system-level control room. It sits apart from everyday settings such as Display, Battery, or Apps. The page groups three jobs: how you interact with the phone, how you preserve or wipe it, and how the OS allocates compute and intelligence.
How the page is organized
| Group | Items | Purpose |
|---|---|---|
| Interaction & locale | Control center, System navigation, Date & time, Language and region, Input method | How you swipe, type, tell time, and see language |
| Data lifecycle | Backup and restore, Reset, Device clone | Copy data out, wipe the phone, or migrate to a new device |
| Performance & intelligence | Intelligent computing platform, Smart capabilities management | Virtual GPU / Multi-Turbo and on-device AI feature controls |
1) Interaction and locale settings
1.1) Control center
This page decides how you open quick settings and which extra hub appears inside it. It does not change Wi-Fi, brightness, or individual toggles.
1.1.1) Separate vs Merge
This is the main layout choice. Origin OS 6 treats Notification center (alerts, messages, ongoing activities) and Control center (toggles, sliders, shortcuts) as two panels that can live apart or together.
The caption under the selected option in the screenshot is exact: “Merge two centers. Swipe down from the top to open Control center.”
A) Separate
The left preview matches this mode: a compact block of tiles, then sliders, then a dense grid.
- Swipe down from the top-right → Control center only (Wi-Fi, Bluetooth, brightness, flashlight, and other tiles).
- Swipe down from the top-left → Notification center only.
- Official Origin OS guidance uses that left/right split.
Why choose Separate
- Faster access to toggles without scrolling past notifications.
- Cleaner when you have a noisy notification shade.
- Closer to the iOS-style two-shade model many users expect after Origin OS 6’s visual refresh.
Trade-offs
- You must remember which corner to use.
- On a large phone, one-handed left-corner swipes are harder than a full-width pull.
B) Merge
The right preview matches this mode: notifications stacked above a list of control rows. This is the option selected in the screenshot.
- Swipe down from anywhere along the top → one combined panel.
- Notifications and toggles share the same scroll.
Why choose Merge
- One gesture. No left/right targeting.
- Familiar if you came from Funtouch OS or stock Android.
- Better one-handed use on tall screens.
Trade-offs
- A long notification list pushes tiles down.
- You cannot open “controls only” without seeing alerts first.
Closing either shade: swipe up, or tap the empty area below the panel.
Changing Separate/Merge does not delete your custom tile order. It only changes which panels share a swipe.
1.1.2) Open Control center from lock screen
Toggle in the screenshot: off.
When this is on, you can pull down Control center on the lock screen without entering PIN, pattern, password, or biometrics. Toggles that the lock screen is allowed to expose (commonly flashlight, some connectivity tiles, brightness) become reachable while the device is still locked.
When this is off (as in the screenshot):
- The lock screen still shows time, notifications (per lock-screen notification settings), and camera/flashlight shortcuts if those exist elsewhere.
- Pulling down does not open the full Control center until the phone is unlocked.
Why leave it off
- Anyone who picks up a locked phone cannot disable mobile data, Wi-Fi, Bluetooth, or airplane mode from the shade.
- This is the setting privacy-focused walkthroughs call out specifically: a stranger should not be able to cut connectivity from the lock screen.
Why turn it on
- Flashlight, silent mode, or brightness while the phone is face-up on a desk.
- Faster access when you trust the physical environment (home, office).
Security nuance
This toggle is not a full unlock. It only exposes the Control center surface. Sensitive tiles may still be limited until you authenticate, depending on build. Treat “off” as the safer default on a phone that leaves your hands in public.
It is independent of Separate/Merge. Either layout can be lock-screen accessible or not.
1.1.3) Show Connection center
Toggle in the screenshot: on.
Subtitle: “Quickly connect and manage devices in Control center.”
Connection center is vivo’s multi-device hub card inside Control center. On earlier Origin OS it replaced the old “multi-device interconnection” card. vivo’s own help text says you enable it here, then find the card in Control center.
On Origin OS 6, Connection center is the shortcut into vivo’s device-link stack, which reviewers describe as a hub for connectivity options such as:
- Phone ↔ Windows/Mac (Office Kit / Link to PC): screen mirroring, file transfer, task handoff
- One-tap transfer to another vivo/iQOO phone
- Transfer to an iPhone after EasyShare is installed on that device
- Nearby wireless devices that Origin OS can manage from one card (earbuds, tablets, PCs, and similar vivo-ecosystem gear, depending on model)
When the toggle is on
- A Connection center card or entry appears in Control center.
- You can start or resume a device session without opening Settings → More connections / Office Kit / EasyShare.
When the toggle is off
- The card is hidden.
- The underlying features still exist in Settings; you just lose the one-tap Control center entry.
- Useful if you never use PC link or EasyShare and want a shorter shade.
Relation to Separate vs Merge
vivo’s Origin OS 5 support note told users that Connection center is easiest to spot after choosing the separate Control center style, then enabling this switch. On Origin OS 6 the toggle is available in both styles (it is on while Merge is selected in your screenshot). If the card seems missing after you enable it, switch to Separate once, confirm the card, then switch back if you prefer Merge.
Connection center is not the same as:
- The Wi-Fi or Bluetooth tiles
- Android’s Nearby Share / Quick Share
- The notification shade’s media-output picker
Those still work if this toggle is off. This switch only shows or hides the vivo interconnection card.
1.1.4) Show media player
Toggle in the screenshot: on.
Subtitle: “View and control media playback in Control center.”
When this is on and audio or video is playing (Music, YouTube, Spotify, podcasts, and similar apps), Control center shows a media card: title, play/pause, skip, progress, and often an output target (phone speaker, earbuds, Bluetooth).
On (recommended for most people)
- Pause or skip from the shade without returning to the app.
- Switch output devices from the same card on many builds.
Off
- The card is hidden from Control center.
- Playback continues. You still control it from the app, lock-screen media widget, or notification.
Turn it off only if you want a shorter Control center and never use the shade as a remote.
The card appears when something is actually playing or recently paused. An empty shade with no media session is normal.
1.1.5) Show shortcut names
Toggle in the screenshot: on.
Subtitle: “Always display feature names below shortcut switches.”
This is a density setting for the tile grid.
On: every shortcut shows its name under the icon—Wi-Fi, Flashlight, Airplane mode, Screen recording, and so on.
Off: icons only. The grid is tighter and closer to a compact iOS-style Control center.
Keep names on until the icons are familiar, or if several tiles look similar. Turn names off after you know the grid and want more tiles visible without scrolling.
This setting does not add or remove tiles. It only shows or hides captions.
1.2) System navigation
1.2.1) Navigation mode
Two exclusive modes. Only one can be active.
1.2.1.1) Full screen gestures
The left preview is filled because this mode is active. The three virtual keys are removed. The display uses the full bottom edge.
Why use it: more screen, easier reach on large phones, matches modern Android.
Cost: edge-swipe Back can fight in-app sliders, galleries, and games. Cases that cover the bezel increase miss-swipes.
After you select this mode, Navigation key layout and Icon style leave this page. Typical replacements:
- Hide the bottom hint / gesture bar
- Back-swipe sensitivity
- Vibration on Back
- Edge anti-mistouch
- Switch-to-previous-app gesture
| Goal | Gesture |
|---|---|
| Home | Short swipe up from the bottom center |
| Recents | Swipe up from the bottom and hold |
| Back | Swipe inward from the left or right edge |
| Switch recent app | Horizontal swipe on the bottom edge (if that toggle is on) |
Watch for: edge-Back colliding with in-app drawers, galleries, maps, and games. The mistouch and sensitivity rows exist to manage that.
A) Learn gestures
Opens a short interactive tutorial for Home, Recents, and Back.
Run it after you first enable gestures, after you hand the phone to someone else, or if Back/Home feel reversed. It does not change any toggle; it only trains the motions.
B) Hide indicator bar
Toggle in the screenshot: off.
The indicator (hint) bar is the thin line at the bottom that marks the gesture strip.
Off (as shown): the bar stays visible. Easier while learning. Also the visual target for horizontal app-switch and Circle to Search long-press.
On: the line is hidden for a cleaner full-screen look. Gestures still work from the same bottom edge. Harder to judge where to swipe, especially for app-switch and long-press search.
Leave it off until the gestures are automatic, then hide it if you want an edge-to-edge display.
C) Gesture mistouch prevention
A submenu. Caption: “Effective only after two swipes in certain scenarios (e.g., full-screen games or videos).”
This is an anti-accident filter for edge Back, not a general sensitivity slider.
In immersive apps (games, landscape video, some readers), the first inward edge swipe is ignored or treated as an in-app gesture. A second swipe in a short window is accepted as system Back. That stops a palm or a game-aim swipe from dumping you out of the app.
Open the row to see which scenarios the build covers and whether the feature is enabled. Typical result:
- Enabled: two-swipe Back in listed full-screen apps; normal one-swipe Back everywhere else.
- Disabled: every edge swipe is Back immediately, including in games.
Turn it on if games keep exiting. Turn it off if Back feels “dead” in video or games and you want a single swipe.
D) Side swipe sensitivity
A submenu for how far / how easily an inward edge swipe counts as Back.
Higher sensitivity: a short, shallow swipe from the bezel goes Back. Better for one-handed use; more collisions with app edge menus.
Lower sensitivity: you must swipe farther inward. Fewer accidents in galleries, maps, and side drawers; slightly slower Back.
Change this if:
- Back fires when you mean to open an app drawer → lower it.
- Back does nothing unless you swipe halfway across the screen → raise it.
This is not the same as mistouch prevention. Sensitivity is distance. Mistouch prevention is require two swipes in immersive apps.
E) Swipe horizontally to switch between apps
Toggle in the screenshot: on.
Subtitle: “Swipe horizontally at the bottom edge of the screen to switch between recent apps.”
On: a left or right swipe along the bottom hint bar jumps to the previous/next recent app without opening the full Recents grid. Fast for two-app juggling (chat ↔ browser).
Off: the bottom edge only does Home (swipe up) and Recents (swipe up and hold). No sideways app hop.
Keep it on for gesture navigation; it replaces the missing Recents button for quick switching. Turn it off if sideways swipes near the keyboard or gesture bar keep changing apps by accident.
This is not the same as swiping cards inside the Recents screen.
F) Swipe to bring up digital assistant
Toggle in the screenshot: off.
Subtitle: “Swipe inward from either bottom corner to bring up digital assistant.”
On: a diagonal / inward swipe from the bottom-left or bottom-right corner opens the digital assistant (Gemini on global Origin OS 6, or the regional assistant on other builds).
Off (as shown): those corner swipes do nothing for the assistant. Corner motion is less likely to steal Back or keyboard gestures.
Leave it off if you already use the power-button or “Hey Google” / Gemini hotword, or if corner swipes conflict with Back. Turn it on only if you want a dedicated assistant gesture and will avoid starting Back from the exact same corner.
This is not Circle to Search. Assistant is conversational / agent help. Circle to Search is visual search of what is on screen.
G) Circle to Search
Toggle in the screenshot: on.
Subtitle: “Tap and hold the home screen button or bottom bar to search using on-screen content.”
On gesture mode the trigger is touch and hold the bottom indicator bar (or the bottom-center gesture area). The “home screen button” wording remains because the same toggle also serves Navigation keys mode.
On: hold the bar → Google Circle to Search overlay → circle, tap, or scribble text/images for search, translate, or copy.
Off: that long-press no longer starts visual search.
Needs Google services and a network for full results. After switching from keys to gestures, wait a moment before long-pressing; the shortcut remaps to the bar.
1.2.1.2) Navigation keys
The right preview, selected in the screenshot: three virtual keys in a bar.
| Key in the selected layout | Function |
|---|---|
| ≡ (three lines) | Recents / recent apps |
| ○ (circle) | Home |
| < (chevron) | Back |
Why use it: a visible tap target, no edge-swipe conflicts, familiar if you came from older Android or Funtouch button navigation.
Cost: a permanent strip at the bottom. Some Origin OS 6 extras (for example a gesture-only home-screen dock on some models) expect gestures.
The screenshot is in this mode, which is why the layout and icon-style rows are visible.
A) Navigation key layout
Visible only while Navigation keys is selected. It swaps left and right keys. Home stays in the center.
Row 1 (selected): ≡ ○ <
Recents left · Home center · Back right
This is the classic Android / Samsung-style order. Thumb-on-the-right users often prefer Back on the right.
Row 2: < ○ ≡
Back left · Home center · Recents right
This is the older Nexus / many-Chinese-OEM order. Use it if your previous phone put Back on the left.
The radio buttons apply immediately. Open any app and tap Back once to confirm the new side.
This setting does nothing in gesture mode. There is no Home-left or Home-right option on this screen; Home stays center.
B) Icon style
A submenu, not a toggle. It changes how the three keys look, not what they do.
Typical choices on vivo/Origin builds:
- Chevron vs triangle for Back
- Circle vs house for Home
- Three lines vs rounded square for Recents
Pick the set that matches the phone you used before. If taps feel right but the icons look wrong, change style only. If the side of Back is wrong, change Navigation key layout, not icon style.
C) Circle to Search
Toggle in the screenshot: on.
Subtitle: “Tap and hold the home screen button or bottom bar to search using on-screen content.”
This is Google’s on-screen visual search, included on global Origin OS 6 with Gemini / Circle to Search. China-region builds may offer a different circle-search product instead.
How to use it (keys mode, as in the screenshot)
- Leave the content you want on screen (image, product, text, sign, video frame).
- Touch and hold the Home button.
- The search overlay appears.
- Circle, tap, or scribble the object.
- Results, translate, or copy-text actions appear below.
How to use it (gesture mode)
Touch and hold the bottom hint bar (or the bottom-center gesture area). Same overlay. Circle to Search still works after you switch modes; the trigger simply moves from the Home key to the bar.
On: long-press Home / bar starts Circle to Search.
Off: that long-press no longer opens visual search. A long-press may do nothing or fall through to another assigned shortcut, depending on the build.
This is not the same as:
- Global search (swipe down on the home screen, or the search bar)
- Gemini / Assistant voice
- In-app “search this image”
It needs Google Mobile Services and a network connection for full results. After you change navigation mode, wait a few seconds before long-pressing; the shortcut can lag while the system remaps the gesture.
1.3) Date & time
1.3.1) Auto-set time
Toggle in the screenshot: on.
When this is on, the phone sets date and time from the mobile network (and, if needed, from the internet). That is the correct default. It keeps alarms, certificates, two-factor codes, calendar invites, and message timestamps aligned with real time.
On (as shown)
- Date and Time are dimmed. You cannot tap them to pick a day or hour.
- The clock still updates across midnight, month changes, and carrier corrections.
Off
- Date and Time become editable.
- You set the clock yourself. It will drift. Use this only for travel without a usable network, testing, or a carrier that publishes the wrong time.
Leave Auto-set time on unless you have a specific reason to freeze the clock.
1.3.2) Date and Time
These two rows are the manual clock.
In the screenshot they show September 13, 2026 and 10:51 PM but are inactive because Auto-set time is on. That display is the current system clock, not a separate “override.”
To edit them:
- Turn Auto-set time off.
- Tap Date and pick the calendar day.
- Tap Time and set hours and minutes (and AM/PM if 12-hour format is on).
Wrong manual time breaks more than the lock-screen clock: Google/vivo account security checks, TLS certificates, OTP apps, and scheduled backups can fail.
1.3.3) Auto-set time zone
Toggle in the screenshot: off.
This is separate from Auto-set time. Time can be automatic while the zone is manual—that is exactly the state in the screenshot.
On: the phone takes the time zone from the mobile network (NITZ) when the carrier provides it.
Off (as shown): the zone stays on whatever you last chose under Time zone. Here that is GMT+09:00 Japan Standard Time.
Use off + manual zone when:
- You live or work across a zone the SIM does not represent.
- You are traveling and want the home zone kept on the phone (dual-clock widgets still need a correct home zone in some apps).
- The carrier’s zone is wrong (common on roaming SIMs).
If both auto time and auto zone are on, date, time, and zone all follow the network.
1.3.4) Set time zone based on location
Greyed in the screenshot.
This switch uses location (GPS / network location) instead of—or in addition to—the carrier to pick the zone. Origin OS 6 keeps it unavailable until Auto-set time zone is on, which is why it is dimmed here.
When it becomes available and on
- Crossing a zone boundary (for example a flight from Tokyo to Seoul) can update the zone even if the SIM is slow to change.
- Location permission for system time services must be usable. Airplane mode plus GPS off will stall updates.
When to skip it
- You want a fixed zone regardless of where the phone sits (the current screenshot).
- Location is restricted for privacy and you prefer carrier or manual zone only.
Turn Auto-set time zone on first if you want this row to work.
1.3.5) Time zone
Active in the screenshot: GMT+09:00 Japan Standard Time.
This is the manual zone picker. Because auto zone is off, this value is what the phone actually uses. Offsets such as GMT+9 do not by themselves handle daylight-saving rules; pick the named zone (Japan Standard Time, Asia/Tokyo) rather than a raw offset when the list offers both.
Tap the row to search by city or region. Changing the zone shifts the displayed local time immediately. It does not rewrite photos already stored with UTC timestamps; it only changes how those times are shown.
A phone set to JST while you are physically in India will show Japanese local time on the lock screen. That matches this screenshot: 10:51 PM JST versus evening IST.
1.3.6) Use system locale
Toggle in the screenshot: off.
When on, hour cycle and related time presentation follow Language and region (for example some locales default to 24-hour time).
When off (as shown), this page’s Use 24-hour format switch is the authority. Language can stay English (India) or Japanese while you still force 12-hour or 24-hour independently.
Turn it on if you want format to follow the language you just set. Leave it off if you want a 12-hour clock in a 24-hour locale, or the reverse.
1.3.7) Use 24-hour format
Toggle in the screenshot: off.
Off: 12-hour clock with AM/PM. Matches the screenshot’s 10:51 PM.
On: 22:51-style time on the status bar, lock screen, calendar, and most system UI.
Some apps ignore this and keep their own format. Alarms still fire at the correct instant either way; only the numerals change.
If Use system locale is on, this row may be driven by the locale and appear less independent. With locale off, this toggle is the one that matters.
1.4) Language and region
This page sets what language the UI speaks and which country rules apply (date layout, first day of week, some storefronts). It does not set the clock; that is Date & time. It does not install keyboards; that is Input method.
1.4.1) Language list
Each row is a language plus a region variant (here, English as used in the United States). The number 1 is priority, not a count of speakers.
How fallback works
- System UI and an app try language #1.
- If that app has no US-English strings, they try #2, then #3, and so on.
- If nothing in the list matches, they fall back to the app’s own default (often English or the developer’s language).
In the screenshot there is only one language, so everything that supports English (US) uses it. Everything that does not will use its built-in default.
The checkmark marks the current primary language. Changing the primary language redraws Settings, the launcher, and most system apps immediately.
English (United States) vs other English variants
The variant matters more than “English” alone:
- English (United States): month-first dates in some apps, “color,” Fahrenheit in some Google surfaces.
- English (Australia) / United Kingdom / India: different spelling, date habits, and sometimes search/region hints inside Google apps.
The language variant is not the same as the Region row. This phone can run US English while Region is Australia—that is the state shown.
1.4.2) Add a language
Adds a second (or third) language without removing English.
Typical flow:
- Tap Add a language.
- Pick a language, then a country variant if asked.
- The new language is appended as #2.
- Drag it to #1 (via the pencil) if it should become the system language.
Use a two-language list when some apps are only translated into one language. Example: #1 Japanese, #2 English (United States) keeps Japanese system UI, while untranslated apps still open in English instead of another fallback.
Adding a language does not enable that keyboard. Open Input method and add the IME separately.
1.4.3) Edit (pencil)
The icon at the top right enters list-edit mode.
Usual actions:
- Drag the handle to change order (#1 is always the system preference).
- Remove a language (Android/Origin OS generally refuses to delete the last remaining language).
- Confirm the new stack.
Reorder instead of delete-and-re-add when you only want to switch which language is primary.
1.4.4) App languages
Opens a per-app override list. This is Android’s per-app language feature, carried in Origin OS 6.
For each app that supports it you can choose:
- System default — follow the numbered list on this page.
- A specific language — only that app UI changes (for example system in US English, one banking app in Japanese).
Apps that do not implement per-app locales will ignore this row and always follow the main list.
Use this when you want one bilingual setup: OS in English, a few apps in the local language, without dragging that local language to #1.
1.4.1) Region
Current value: Australia.
Region is the country profile, not the spoken language. It drives:
- Date order and examples in many system surfaces (when Date & time is set to follow locale).
- First day of week (Sunday vs Monday) in Calendar.
- Measurement and numbering habits in some apps.
- Available content, payment methods, or feature packs in certain vivo/Google services.
- Which “local” results Google apps assume.
It does not by itself:
- Change Settings into Australian English (that is the language list).
- Change time zone (that is Date & time).
- Move your vivo or Google account’s country (account country is set in the account, not here).
Language US + Region Australia (this screenshot) means: menus in American English, regional conventions leaning Australian. That mix is valid. Switch Region to the country you actually use for calendar and storefronts; switch the language list for the words on screen.
Changing region can briefly refresh some system components. It does not factory-reset the phone.
1.5) Input method
Settings on this screen
| Item | State in screenshot | Role |
|---|---|---|
| Default input method | English (US) – Gboard | Keyboard that opens in text fields |
| Autofill with Google | On | Saves and fills passwords, addresses, cards |
| Gboard | On | Google keyboard available to use |
| Google Voice Typing | On | Mic / dictation IME |
| TalkBack braille keyboard | Off | Braille input for TalkBack users |
| Voice input | Shortcut + gear | Speech recognition and synthesis service |
| Text-to-speech output | Submenu | Spoken playback of on-screen text |
| Spellchecker | Gboard spellchecker | Red-underline spelling engine |
| Personal dictionary | Submenu | Custom words that skip autocorrect |
| Pointer speed | Submenu | Mouse / trackpad cursor speed |
1.5.1) Default input method
Current value: English (US) – Gboard.
This is the keyboard that appears when you tap a text field. Origin OS 6 will not guess a newly installed keyboard; you enable it in the list below, then select it here.
Tap the row to pick any enabled IME (Gboard, vivo keyboard if present, SwiftKey, Samsung Keyboard, and so on). “English (US)” is Gboard’s active language pack, not the system language. You can type Japanese in Gboard while Settings stays in English.
If the wrong keyboard keeps appearing:
- Enable the one you want under Input method enabling.
- Set it as Default input method.
- In a text field, use the keyboard-switch icon in the nav bar or the globe key to confirm.
1.5.2) Input method enabling
Each checkbox is permission for that IME to run. Unchecked means it cannot become default and will not show in the keyboard picker.
1.5.2.1) Autofill with Google
Checked in the screenshot.
This is not a keyboard. It is Google’s fill service for passwords, addresses, phone numbers, and payment data in Chrome and many apps.
On: a suggestion bar or overlay can offer saved credentials after you unlock (screen lock / biometrics).
Off: those Google-saved fills stop. A password manager you set as the autofill service under Passwords / Autofill settings can still work.
Leave it on if you use Google Password Manager. Turn it off if you use only a third-party manager and do not want Google Autofill prompts.
1.5.2.2) Gboard
This must stay on while Gboard is the default. Unchecking it removes Gboard from the picker and forces another enabled IME (or leaves you with no comfortable keyboard).
The chevron opens Gboard’s own settings: languages, glide typing, voice key, theme, number row, suggestion bar, and privacy options. Multi-language typing is configured there, not on the Language and region page.
1.5.2.3) Google Voice Typing
Checked. This is the standalone dictation IME, separate from Gboard’s built-in mic key.
On: you can switch to voice typing as an input method, and many fields show a microphone.
Off: this IME disappears. Gboard’s own mic may still work if that Gboard option stays enabled.
Keep it on unless you want to block dictation entirely.
1.5.2.4) TalkBack braille keyboard
Unchecked. This IME is for people who use TalkBack and type Braille on the screen (usually by placing fingers in a Braille cell pattern).
Leave it off if you do not use TalkBack. Turning it on without TalkBack configured only adds an input method you will not use. Enable it together with Accessibility → TalkBack when you need on-screen Braille.
1.5.3) Speech
1.5.3.1) Voice input
Speech recognition and synthesis
The row opens the system speech services used by dictation, “voice input” in apps, and related Google speech features. The gear is the service’s own settings (languages for recognition, offline speech packs, audio history, and similar Google speech options).
This is the engine. Google Voice Typing above is the input method that calls the engine. You can have Voice Typing on and still need a language pack installed here for offline dictation.
1.5.3.1) Text-to-speech output
Controls spoken playback, not dictation.
Typical contents:
- Preferred engine (Google TTS is standard on global Origin OS 6)
- Language and voice
- Speech rate and pitch
- Reset / install voice data
Used by TalkBack, Select-to-Speak, “Read aloud” in Chrome, navigation prompts, and some accessibility tools. Changing TTS language does not change the keyboard language.
1.5.4) Tools
1.5.4.1) Spellchecker
Current value: Gboard spellchecker.
This is the engine that underlines misspellings in text fields. Tapping the row lets you pick Gboard’s checker, Google’s system checker, or another installed spell service.
The keyboard’s autocorrect and this spellchecker overlap but are not identical:
- Autocorrect rewrites as you type (inside Gboard settings).
- Spellchecker marks words after they are entered, including in some apps that are not using Gboard’s suggestion strip.
If red underlines appear in the wrong language, change the spellchecker language or switch the engine here, and add that language inside Gboard.
1.5.4.2) Personal dictionary
A user word list shared with the spellchecker and, on most builds, Gboard.
Add names, slang, workplace terms, and mixed-script words so they are not “corrected” to something else. You can often add a shortcut (abbreviation → expanded phrase). Words here are on-device; they are not the same as Gboard’s cloud-learned suggestions.
Add entries for each language you type. A word saved only under English will still get flagged in a Japanese field.
1.5.4.3) Pointer speed
Does not affect finger typing. It sets how fast an attached mouse, trackpad, or similar pointer moves.
Leave the default unless you use a Bluetooth mouse or USB-C trackpad and the cursor feels sluggish or too sharp. It will not change Gboard swipe-typing speed.
2) Data lifecycle settings
2.1) Backup and restore
This is Origin OS 6’s local and account-backed backup hub, not just Google One. Official vivo manuals place it at Settings → System management → Backup and restore.
Typical destinations:
- vivo account / vivo Cloud (where offered)
- EasyShare for Windows over Wi-Fi or USB
- External storage via USB OTG (flash drive or card reader)
- Device-to-device transfer is usually handled by Device clone, not this menu
2.1.1) Settings on this screen
| Section | Item | State | Role |
|---|---|---|---|
| iQOO Cloud | Backup & restore | Submenu | vivo/iQOO account cloud snapshot |
| Google server | Back up data | Submenu | Google One / Drive device backup |
| Google server | Auto-restore | On | Re-apply app data when an app is reinstalled |
2.1.2) iQOO Cloud → Backup & restore
Opens the official iQOO / vivo Cloud backup hub. You must be signed in to an iQOO or vivo account. On vivo-branded Origin OS 6 the same row is often labeled vivo Cloud; the service is the same family.
Typical contents after you tap it:
- Sign in / manage the iQOO account
- Back up now (manual snapshot)
- Auto cloud backup (usually while charging, on Wi-Fi, and locked; often about every 7 days)
- Data-type checkboxes (Notes, contacts, SMS, call log, system settings / desktop layout, alarms, app packages, notes—exact list varies)
- Backup history and Restore
- Cloud storage quota (commonly a small free tier, with paid upgrades)
What it is good at
- Restoring an iQOO or vivo phone as an iQOO/vivo phone: layout, some settings, messages, contacts
- A vendor snapshot you can pull after a reset without depending on Google
Limits (important)
- Official notes for device cloud backup: one device often keeps only the latest cloud snapshot; a new backup can overwrite the previous one.
- Apps are frequently stored as install packages, not full chat/game saves. WhatsApp and similar apps still need their own in-app backup.
- Photos and videos are not a substitute for Google Photos (or another media library). Do not treat iQOO Cloud as your only camera roll.
- Restore needs the same account, a network, and enough free storage on the phone.
Use this before Origin OS updates, a Reset, or a repair. Confirm the last backup date inside the submenu; an empty or expired snapshot will not save you.
PC copies (EasyShare for Windows) are a separate local path. They may be linked from cloud/EasyShare tools, but they are not the Google block on this screen.
2.1.3) Google server → Back up data
Opens Android’s backup to Google (Google One / Drive device backup), tied to the Google account on the phone.
Typical contents:
- The Google account used for backup
- Backup toggle (on/off)
- What is included (device settings, call history, SMS, Wi-Fi passwords, app list, app data that the developer allows)
- Last backup time
- Back up now
What it is good at
- Setup wizard on a new Android phone (iQOO, Pixel, Samsung, and others): “Restore from backup”
- App list from Play Store and settings that Google is allowed to store
- A second copy that still works if you leave the iQOO/vivo ecosystem
Limits
- Not a full disk image. Many apps opt out of Google backup. Games, banks, and encrypted messengers often restore as empty installs.
- Photos belong in Google Photos backup, not this device backup, unless you enabled Photos separately.
- Drive/One quota applies. A “backup failed” notice is often a full Google storage cap.
- You must use the same Google account at setup or after reset.
Tap this row, confirm the account, and run Back up now after a big change (new phone number, new set of apps). Do not assume it runs every night if the phone never sits on Wi-Fi and power.
2.1.4) Google server → Auto-restore
Toggle in the screenshot: on.
Subtitle: “When reinstalling an app, restore backed-up settings and data.”
This does not create backups. It decides what happens when an app is installed again from Play Store.
On (as shown)
- If Google has a backup of that app’s data for this account, Android tries to put settings and allowed app data back after install.
- Useful after a reset, after you uninstall and reinstall, or when you install the same Play app on a new device signed into the same account.
Off
- Apps install clean. No saved settings, no restored app data from Google.
- Use this if you want a fresh app, or if restored data is causing crashes after an OS upgrade.
Auto-restore only works for data that was actually uploaded via Back up data. If the developer blocked backup, this toggle cannot invent a save file.
It does not restore iQOO Cloud snapshots. Those are restored only inside iQOO Cloud → Backup & restore.
3) Performance and intelligence settings
3.1) Intelligent computing platform
3.1.1) Virtual graphics card tab
Three stacked modules. On this screen they are descriptions of active architecture, not three independent switches.
A) Rapid response dynamic effect architecture
“Rebuild and prioritise dynamic effect drawing for instant feedback and smoother visuals.”
Includes: Lightning-speed engine and IPC dynamic effect integration.
This is the animation and touch-feedback path.
- Lightning-speed engine prioritizes the next UI frame when you tap or swipe so the first motion starts immediately (app open, Control center, page turn).
- IPC dynamic effect integration coordinates those animations across processes so a window, blur, and icon do not animate on different clocks.
What you feel: less “dead” time after a tap; Origin OS 6 spring / blur / one-shot transitions stay attached to your finger. This is the layer behind vivo’s “rapid response” and faster app-start claims.
You do not turn this off here. Reducing motion in Accessibility or animation-scale developer options is the blunt alternative.
B) Composition rendering accelerator
“Boost frame stability and visuals in apps and games via multi-core acceleration, picture quality enhancement and rendering stabilisation.”
Includes: V-SR Game Super Resolution, Graphics multithreading, Graphics pre-rendering, and FALCON Graphics Engine.
This is the frame-building path: how layers become a stable image.
| Piece | Role |
|---|---|
| V-SR Game Super Resolution | Upscales a game’s internal resolution so the panel looks sharper without the game rendering native 1080p/1440p every pixel |
| Graphics multithreading | Spreads compose / render work across CPU cores so one core does not stall the frame |
| Graphics pre-rendering | Starts the next frame early to hide hitch when the UI or game spikes |
| FALCON Graphics Engine | Vendor compose/render stack that holds frame pacing and quality |
What you feel: fewer stutters when opening a heavy app, scrolling a blurred shade, or playing a title that is allowed to use SR. Super Resolution is still per-game in Game Mode on many iQOO phones; this row only states that the platform can do it.
Trade-off: SR and pre-render use GPU and heat. That is expected in games; it should stay quiet on this Settings page (GPU 4% here).
C) Graphics link collaboration engine
“Optimise touch and display links for quick control response.”
Includes: Graphics link collaboration and V-Sync frame sync.
This is the input-to-photon path: finger down → frame on screen.
- Graphics link collaboration shortens the chain between the touch controller, render thread, and display.
- V-Sync frame sync aligns touch sampling and drawn frames with the panel refresh so you do not see tearing or a frame that lags the swipe.
vivo cites this path for lower touch latency in UI and FPS games (their published figure for Origin OS 6-class devices is on the order of ~25 ms versus a higher industry range).
What you feel: aiming, scrolling, and Control center tiles track the finger more tightly. V-Sync here is the platform sync; a game can still have its own vsync/frame-rate option in Game Cube.
3.2) Multi-Turbo tab
A) Settings on this tab
| Item | Control | Role |
|---|---|---|
| Central core acceleration engine | Info only | CPU / GPU / I/O / RAM scheduling |
| Network acceleration engine | Info only | Stability under mixed networks |
| Game acceleration engine | Info only | Game SDK / foreground game boost |
| Heat dissipation acceleration engine | Info only | Thermal policy so frames hold |
| AI Acceleration Engine | On | Predict apps and pre-schedule resources |
| ART++ Turbo | On | Compile apps for faster launch (needs internet) |
B) Central core acceleration engine
“Deep optimisation of the CPU/GPU/I/O/RAM will improve the running speed of apps.”
This is the system scheduler (Center / core turbo). It decides which cores run a foreground app, how memory is kept warm, and how storage I/O is prioritized when you open or switch apps.
What you feel: snappier cold starts, less hitch when returning to an app, fewer “loading” stalls when several apps are in Recents.
There is no toggle here because Origin OS 6 treats it as part of the Smooth Engine. Per-app extremes (Boost vs Balanced) are in Ultra Game Mode, not on this row.
C) Network acceleration engine
“The stability and speed of the network will be improved in complex multi-network scenarios.”
This is Network turbo. “Multi-network” means Wi-Fi + mobile data, weak Wi-Fi, congested 5 GHz, or a game that is sensitive to jitter—not a second SIM by itself.
What it does:
- Prefers the stabler path when Wi-Fi is poor
- Reduces latency spikes for the foreground app
- Helps game/voice packets when the radio is busy
What it is not: a VPN, a speed-test booster, or a data-saver. It will not raise a carrier cap. For competitive play, also use Game Mode network options and a clean Wi-Fi channel.
D) Game acceleration engine
“Deep optimisation of the performance SDK will make games run more smoothly.”
This is Game turbo. Official games that integrate vivo/iQOO’s performance SDK can tell the system “loading / fighting / skill” so CPU, GPU, and network follow the scene.
What you feel in supported titles: fewer frame drops after a loading gate, more stable FPS in fights, slightly faster skill response when the SDK and Game Mode agree.
Unsupported games still get generic foreground priority; they just cannot send scene hints. Add the title to Ultra Game Mode for sidebar FPS, SR, and notification blocking. This row only states that the SDK path exists.
E) Heat dissipation acceleration engine
“Improve app fluidity with heat dissipation technology and thermal management.”
This is Cooling turbo. It is policy, not a louder fan (phones this class are still passive).
What it does:
- Spreads or holds clocks so the first minutes of a game do not immediately throttle
- Coordinates with board temperature (the Normal badge on the Virtual graphics card ring)
- Tries to keep frame time stable instead of a sharp FPS cliff when the board heats
What it does not do: make the phone cold under a thick case in summer. If the ring leaves Normal, lower Game Mode from Boost to Balanced, remove the case, or pause charging while playing.
F) AI Acceleration Engine
Toggle in the screenshot: on.
“Speed app startup with AI-predicted intelligent resource scheduling up.”
This is the one everyday switch most people should leave on.
On: the system learns which apps you open at certain times (for example Messages after unlock, Maps at commute hours) and warms CPU/RAM ahead of the tap. Cold start feels closer to a warm start.
Off: no prediction. Every launch pays full startup cost. Use off only if you want minimum background planning, or if a specific build’s prediction keeps the wrong apps resident and you prefer to test battery without it.
Cost: a little extra memory and standby work. Benefit is largest on phones that open the same few apps all day.
This is not Gemini or Origin Island. It only schedules compute.
G) ART++ Turbo
Toggle in the screenshot: on.
“Speed app startup and running up (internet required).”
ART is Android Runtime. ART++ is vivo’s extra compile pass: after install or update, the phone optimizes bytecode so the next launches are faster.
On: new and updated apps are compiled more aggressively. First use after install may briefly use CPU and need a network connection (the caption is explicit). Later opens are quicker.
Off: you skip that extra compile. Apps still run; they just stay closer to stock ART until Android’s own idle compiler catches up.
Turn it on after you install a large set of apps, then leave the phone on Wi-Fi and power. Turn it off only on a metered connection if you do not want compile-related traffic, or while debugging a crash that started after an optimization pass.
This is not a game FPS booster. It is install-time / idle compile.
3.2) Smart capabilities management
Smart service
When this is on, Origin OS may read a defined set of signals and then:
- Suggest apps or actions for the current situation (time, place, what you just copied or dragged)
- Power Origin Island helpers, including Drag and go (drag text, a number, or an image to the island for call, save, share, or transfer)
- Offer other on-device “smart” shortcuts that depend on habits (frequent apps, calendar-adjacent actions, nearby-device handoff)
When this is off:
- Those recommendations and Island content-actions that require Smart service stop
- The phone still works: calls, apps, Control center, Multi-Turbo, and Google/Gemini features that have their own switches keep running
- You avoid the data uses listed in the note
Turn it on if you use Origin Island as a shelf for live activities and drag-to-act. Turn it off if you want no system-level habit or location-based suggestions.
What the disclosure says it needs
The note states that Smart service requires access to:
| Permission | Why the OS asks |
|---|---|
| Apps list | Know which apps to recommend or open from Island / suggestions |
| Location | Time-and-place suggestions (commute, office, home) |
| Nearby devices | Device-link / transfer style actions |
| Contacts | Actions on numbers and names (call, message, save) |
| Calendar | Time-sensitive suggestions around events |
It also says suggestions are based on user behaviour and usage habits, and that turning the switch on means you agree to the Smart Service User Agreement. Processing detail is in the Smart Service Privacy Terms (blue links on the screen).