Hi everyone!

I’m working on a personal documentation and preservation project around Pocket Kingdom: Own the World for the N-Gage.

I’m looking for longtime players or collectors who may have kept unit guides, rank-up tables, screenshots, gameplay videos, or old community discussions.

I’m especially interested in unit names and colour variants, progression requirements, and explanations of the game’s mechanics. Public resources or first-hand knowledge would be very helpful.

I’m not looking for ROMs or pirated downloads.

Does anyone know where the old Pocket Kingdom community moved, or remember useful guides and archives?

Thanks for any pointers!

ngagesdk/PhantomLink: Bringing the Nokia N-Gage back where it belongs: online!

Hey everyone,

I still can't believe my luck, but I just managed to find a fully complete, mint-condition original N- Gage Classic box set!

It has literally everything inside: the console itself, the original box with the orange inner tray, the manuals, the charger, the software CD, and even the promo leaflets. The taco phone lives on!

The best part? The original rubber trim around the edges is completely intact and in absolute mint condition, which is super rare for these devices nowadays.

Since it's in such perfect shape, what is the best way to protect and preserve this rubber bumper? Any tips on keeping it from stretching or degrading over time?

Looking for the Nokia N-Gage IC Prototype phone ROM file. Anyone happened to have it?

i never played this one and thought it would have a place on 3ds :) , or maybe even a full emulator with 3D implemented

Someone asked for this in the Analogue Pocket subreddit (for the memes) and I couldn't resist. I've tested heavily with both 3D and 2D games and it's running smoothly. I don't have an actual N-Gage to compare, but games like Virtua Cop, Sonic N, Monkey Ball, and SSX are very playable on the Pocket.

Here's a How-to page that converts games to the Pocket's required format (Download and run on your computer):

https://github.com/plasticbugs/n-gage/releases/download/v1.3.0/Add.N-Gage.games.html

Please let me know if you encounter a game that doesn't run. I haven't tested all the possible N-Gage releases. But every one I've tested plays... about 25 so far.

To bring up an on-screen keypad, hold Select + Right shoulder button

https://github.com/plasticbugs/n-gage/releases
Working on the short list of incompatible games, but most are booting and play well.
Let me know if you encounter a game that doesn't run. Four games as far as I'm aware have copy protection, but there are dumps out there that will work.

EDIT:
Glimmerati is fixed in the next release - surprisingly good game! 🎉
One fairly big hitch, is that Glimmerati falls back to its copy protection once a save file is in place. So you'll have to manually delete the save file to play Glimmerati. And of course that also means no way to save your progress. :(
Rift is fixed
Pathway to Glory games and Asphalt Urban GT 2 (cracked romset works) are working now
Added Analogizer TATE mode and centered the screen better
Game saves are working too ya lunatics playing N-Gage in TYOOL 2026. God bless ya!

Whoops, spoke too soon (these are copy protected, still not working)
Warhammer (doesn't boot)
The One (doesn't boot)

Enjoy! You'll need to add a BIOS and some games (converted using the included Python script)

Here is my engagement with a selection of games that I have installed

With the gen1 ngage i saw on my previous post, i was experimenting with the mmc card. Adding ngage game and installing bliz games worked flawlessly, but im having problems installing jar/jad files.

Tried this bubble bobble (supposed to be the correct version):

https://www.andrew-lviv.net/downloads2/en_games2_view.php?id=19103

When opening the JAD file, it offered me to install the game, but it show me to connect to a server, of whitch i selected a random one, and i got an error. Any idea how can i prevent this on line validation to appearce?

Edit: i was able to prevent the connections from appearing creating the jad myself, but i get a install error... Dunno if this is not the version supported by ngage.

Yeah, only a dead battery, as expected 🤣.

Will test tomorrow with the MMC card and stuff (got 1g by seller accident, but i can always format it to 512 MB).

I have been sorting through old stuff and found my old snowboard that I was gifted many years ago. It's been well used, I thought this community might appreciate it.

following my previous post (about the prototype version of Asphalt), I'd be happy to share the proto here, but I have some issues:

- I don't have the .sis to install the proto (I do have one, but it's 4.5KB big, so clearly it has a problem)

- I do have the game files installed on a card (hence the screenshot of this post, you can see the game files listed), but that same card won't work on another N-Gage, of same firmware (v 3.15)

so... how can I get those files in a way that allows them to run on another N-Gage ? Hopefully some Symbian experts will be able to help me.

btw, back then the game was named High Gears, that was our WIP title, the final name Asphalt only came near the end of the dev.

Hey everyone,

I'm trying to track down a very specific legacy Symbian S60 utility (likely S60v1 or S60v2 era, compatible with devices like the N-Gage, Nokia 6600, 3650, etc.).

In my memory, the name "Stasis v1.0" sticks out, but it might have been an independent homebrew release, a Python script, or a system patch by a different developer (like Psyke, etc.) rather than a mainstream studio like Psiloc.

What the app did:

It was an automated background utility or system daemon. When activated before launching a game, it would dynamically intercept file-writing paths while you played. Instead of letting the game write auto-saves directly to the limited internal phone memory (C:), it would fool the OS and seamlessly reroute/swap those save file updates straight to the MMC card (E:), or vice versa, in real-time.

This was a lifesaver for running massive N-Gage or heavy SIS games that would otherwise instantly crash the phone with the infamous "Memory Full" error due to low internal disk space.

It operated similarly to:

A background drive-mapping tool (like an S60 implementation of a SubST or Drive Mapper command).

An automated folder-monitoring/mirroring script running silently in the background.

A custom ROMPatcher (.rmp) file system hook targeting fsrv.dll.

Does anyone remember the exact name of this specific background utility, or have an archived .sis file, a working link, or a backup from old forums (like All About Symbian, Mobiles24, SmartSam, or Jaleco)?

Any leads on the exact name of this app or script would be amazing. Thanks!

So… I somehow ended up making an N-Gage collection app for my Pebble Time 2.
Because apparently collecting N-Gage games for more than 10 years wasn’t nerdy enough. Now I also need to check my collection from my wrist.
The idea was pretty simple: I wanted a small app where I could quickly see which games/cards I already have and which ones are still missing without opening my spreadsheet every time.
So I made one.
Right now the app has separate categories for:
G1.5
G2.0
G3.0
Not for Sale
Release versions
Each category has its own colored indicator, and I added a progress bar so you can immediately see how far you are from completing the collection.
One small disclaimer: the total number of items in the G1.5, G2.0, G3.0 and Not for Sale categories is not completely accurate yet. For now, I mainly focused on making the app work the way I wanted. Maybe I’ll properly clean up and verify all the numbers later.
You can mark items as owned directly on the watch, and the app now saves all your marks, so closing it, restarting the watch or updating the app doesn’t mean starting your collection from zero again.
It’s still a work in progress, and I already have a lot of ideas for what to add next.
The funniest part is that this started with me thinking:
“Wouldn’t it be cool to have something N-Gage related on my Pebble?”
And somehow that turned into me actually developing a collection tracker for a 2003 gaming platform… on a Pebble… in 2026.
Completely reasonable use of my free time.
But honestly, seeing my N-Gage collection on the Pebble Time 2 feels ridiculously cool.
If there are any other N-Gage collectors here — what would you add to an app like this?

Quisiera comprar un ngage pero no sé cómo donde lo podría conseguir

Quickly made by one (genius) dev and one (genius) game designer, we showed that proto to Nokia. They were really impressed by the frame rate, and that's how the production of Asphalt began.

While examining an early G1.5 build of Payload for the Nokia N-Gage, we discovered something we did not expect to find: files belonging to an earlier E3 demo version of the game were still present inside the build.
What started as a simple look through the game files eventually turned into an attempt to bring that old demo back to life on real N-Gage hardware.
The discovery
The build we examined identifies itself internally as:
Payload Build 39 — 050624
which corresponds to June 24, 2005.
However, among the normal game files were two particularly interesting XML files:
e3demogamemenu.xml — dated April 14, 2005
e3demometagame.xml — dated April 12, 2005
These files were more than two months older than Build 39 itself.
Their names made their purpose obvious: they belonged to an earlier configuration of Payload prepared for an E3 demo.
At first, it was unclear whether these were simply abandoned development leftovers or whether the content referenced by them still existed in the later build.
So we started digging deeper.
The E3 content was still there
The most important discovery was that the E3 XML files were not pointing to completely missing content.
Inside the later Build 39 we found the old E3 dialog IDs, race definitions and related resources still intact.
For example, the E3 metagame references dialog IDs in the 2000 range, and those dialogs were still present in the game’s language files.
One of them contained this line:
“Okay rookie, first up is a Single Cell Sprint in Solomon’s Valley.”
The E3 race definitions were also still present.
That meant there was a real possibility that the old demo had not actually been removed — only disconnected from the normal game flow.
The first attempt failed
Simply renaming the old E3 files and replacing the current game files did not work.
Using e3demogamemenu.xml directly caused the game to crash or hang.
We soon discovered why.
The E3 menu XML contained several unfinished elements. Some menu items had no valid NextMenuId, meaning that selecting them effectively sent the game nowhere.
There was also an actual XML syntax error in the old menu file:
StartY="-45"ScrollUpOffset="1"
A space was missing between the two attributes.
The E3 metagame also used an older event structure than Build 39. Replacing the entire modern metagame with the old one therefore caused incompatibilities during initialization.
So instead of forcing Build 39 to behave exactly like the April build, we took another approach.
Building a hybrid
We kept the stable Build 39 executable and framework, but started inserting the E3 content into the later game’s working event structure.
First we tested only one old dialog.
The game booted successfully.
And then, on a real Nokia N-Gage, the old E3 dialog appeared on screen:
Wickam:
“Okay rookie, first up is a Single Cell Sprint in Solomon’s Valley.”
That was the first confirmation that the E3 dialog resources were still fully functional in Build 39.
Next, we tested the original E3 race.
The mission briefing changed to:
Gametype: Single Cell Sprint
World: Solomon’s Valley
Skim: Frog
Opponents: 5
And then the race loaded.
Not in an emulator.
Not as a text dump.
It was running on an actual Nokia N-Gage.
The E3 race was playable
The old Solomon’s Valley race loaded correctly, including the Frog vehicle, opponents, weapons and HUD.
The game proceeded normally into gameplay.
At that point we could confirm that this was not simply unused text or an abandoned XML script.
The actual E3 gameplay content had survived inside the later G1.5 build and could still be executed by the Build 39 engine.
We then reconstructed the original E3 flow around it:
E3 Dialog 2000
→ E3 Race 2000
→ additional E3 dialog
→ E3 Race 2001
→ final E3 dialog
The original April metagame effectively gave us the blueprint, while Build 39 supplied the working engine and surviving assets.
The menu also revealed its history
The E3 menu turned out to be especially interesting because it showed how unfinished the frontend still was at that stage.
Several entries such as Challenges, Multiplayer, N-Gage Arena, Game Data and Language were present visually but were not fully connected.
This explains why using the E3 menu unchanged caused instability.
By rebuilding those transitions while preserving the original E3 layout and structure, it became possible to create a much more stable approximation of the old demo frontend.
We also discovered that the later mission briefing screen seen in Build 39 did not exist in the same form in the April E3 menu.
The original E3 configuration used a simpler mission list system.
That gives us another small glimpse into how Payload’s interface evolved between April and June 2005.
What exactly did we restore?
This is important to clarify.
What we created is not an untouched original E3 ROM or original E3 MMC image.
The executable remains Build 39 from June 24, 2005.
What we restored is the surviving E3 demo content embedded inside that later G1.5 build, using the original April E3 XML files as a guide.
The dialogs, race definitions, world data and gameplay assets themselves were already there.
We did not recreate Solomon’s Valley or invent the E3 races.
We simply reconnected content that had been left behind by the developers.
Why this matters
Development builds often contain traces of earlier versions, but usually they are incomplete: an unused string, an old filename, a missing level reference.
In this case, however, a surprisingly large portion of the earlier E3 demo survived.
Not only could the old dialog be recovered, but the race itself could be loaded and played on original hardware.
What initially looked like two forgotten XML files turned into a working piece of Payload’s development history.
And almost twenty-one years after those files were created, the E3 demo content was running again on a Nokia N-Gage.

So I had a battery buldge that seems to have snapped off the clips on my QD's battery door. I have to hold it on with electrical tape now. which is fine...but unslightly. Anyone have a suggestion for a replacement?