Revisit the Symbian settings menu from a Nokia handset
Before phones settled on one long scrolling list, a Nokia handset organised its options into seven folders and expected you to know which one to open. Seeing that arrangement again is a genuinely useful exercise, partly for the nostalgia and partly because it shows how differently the same problems were once solved.
At a glance
In the simulator, Symbian opens inside a phone frame and behaves the way the real Settings app does: rows sit in the same order, sub-screens open in the same place, and back takes you where you expect. Every number below was counted directly from that tree.
- 7top-level entries
- 72rows in total
- 3levels deep
- 2versions
| Device family | Retro and classic |
|---|---|
| Frame shown | Phone |
| Versions | Belle, Anna |
| Deepest path | 3 levels below the main list |
| Interface languages | 12, switchable while you browse |
| Account needed | No — it runs entirely in your browser |
How Symbian organises Settings
Seven top-level entries and about 72 rows in total, which is less than a modern phone puts on a single screen. Connectivity gathers Bluetooth, WLAN wizard, USB, Data transfer, Remote drives and Admin settings. Phone is the general bucket, holding Themes, Profiles, Display, Date and time, Language, Sensor settings and Standby mode. Display and Profiles then appear again as top-level entries in their own right, which is the era's habit of offering two routes to the same screen rather than one. Application settings, Security and Phone information finish the list. The tree stops at three levels because a keypad makes anything deeper painful.
Profiles is the idea worth pausing on. General, Silent, Meeting and Outdoor are named states that change ringing and vibration together, and the phone expected you to switch between them several times a day rather than reach for a volume key. Modern systems rebuilt the same concept decades later under different names. The other thing a visitor notices is how much is simply absent: no privacy section, no battery optimisation, no notification management, because none of those were yet problems. Where people get lost is the duplication, since Display can be reached directly or through Phone.
Three settings worth finding
Settings > Profiles > MeetingA profile changes ringing volume, vibration and alert behaviour as one named state. Meeting is the clearest example, and finding it explains an approach to interruption that phones abandoned and then reinvented under different names years afterwards.
Settings > Connectivity > WLAN wizardJoining a wireless network was treated as a guided task with its own wizard rather than a list of names you tap. Worth seeing because it captures how unusual and effortful wireless connection was assumed to be at the time.
Settings > Phone > Sensor settingsThis is where turning the handset face down to silence a call was configured, one of the first gesture controls to reach an ordinary phone. It sits under the general Phone folder alongside Standby mode and Language rather than anywhere obvious.
Versions of Symbian you can open
The simulator carries 2 builds of Symbian. Switching between them is the quickest way to see what actually moved: a row that changed name, a section split in two, a screen that quietly disappeared.
How this menu got here
This settings tree grew from a phone platform that predated touchscreens, built for a keypad and a small screen, which is why it favours short folders over long lists. Later releases adapted the same structure for touch input without reorganising it, so the folder logic survived into an interface people tapped rather than scrolled. The two versions offered here, Belle and Anna, are from that final stretch, and comparing them shows the last round of tidying the platform received before it was retired.
Who this is useful for
Anyone writing about mobile history, teaching an interface design class or building a museum display gets a working example instead of a screenshot. It also suits former owners who want to check a memory of how something was arranged, developers curious about pre-touch menu conventions, and collectors with a handset that no longer powers on but whose menu structure they still need to describe accurately.
What is real and what is sample data
The structure is the real thing: menu names, their order, how they are grouped and what sits inside each one. That is why this article can quote a path such as Settings > Profiles > Meeting and expect it to match your phone.
The state cannot be. A device name, an address, a build number, a network name, a storage figure, whether a particular switch is on or off — those belong to a physical phone, not to a menu tree. The simulator fills those in with obvious sample values. Use them to learn where a figure lives; look at your own phone to learn what it says.
Try it yourself
The useful thing is to go looking for something specific. Pick a setting you would normally hunt for on a real phone, find it here, and record the path while you do it so you never have to find it twice. When the question is really Symbian versus something else, open them side by side rather than reading two separate menus from memory. If you already know what the setting is called, the site-wide search will tell you which section hides it here.
Open Symbian in the simulatorFree, no account, works offline — 72 settings rows across 2 versions.Key points
- Symbian shows 7 top-level entries and 72 rows in total, nested up to 3 levels.
- Menu names and their order come from the settings tree itself, so the paths quoted here match the real phone.
- Device-specific figures on screen are placeholders; the structure around them is not.
Questions about Symbian settings
Why does the same screen appear in two places?
Because it did on the device. Display and Profiles are reachable both as top-level entries and from inside the Phone folder, which was a common convention when menus were folders rather than one long list. The simulator keeps that duplication rather than tidying it, since the point is to match what shipped.
What is the difference between Belle and Anna?
Both are late releases of the same platform, and the changes between them are refinements rather than a redesign: wording, ordering and the fit of the folder structure to a touchscreen. You can switch between the two in the version picker and keep your place in the tree, which is the quickest way to spot them.
Can I still use this to help with a real old phone?
Up to a point. The menu structure and wording match, so you can work out where an option lived before handling the device. What you cannot rely on is anything device-specific, since every network name, code and status shown here is a sample value rather than a reading from real hardware.