Nokia emulator for windows

So if you are an app developer who expands apps for the Symbian’s platform, then you may test the progress of your apps using the Symbian emulator for the laptop by running any windows operating system such as Windows XP, Vista, Windows 7, Windows 8, Windows 10 32it and 64bit. It’s not only for developers but the Symbian Emulators can also be used by any person who needs to run Symbian applications on their PC.

The Feature of Symbian Emulator Software:

    Easy to use and attractive user interface.
    We have supported almost all Nokia Symbian sis and sisx apps.
    It looks like a mobile interface.
    Supported live previews at the time of Symbian apps developments.
    We have supported almost all Windows operating systems.

Requirements:

    Windows Operating System Windows XP, Vista, Windows 7, 8, 8.1, and Windows 10.
    RAM 4 Gb.
    Processor 2.0 GHz core two duos or above.
    Graphics card 128MB.
    Java Runtime Environments 4++ and so on.
    Mouse and Keyboard.

Nokia[edit]

Symbian and N-Gage[edit]

Nokia-Gage

This page is about emulating Symbian/N-Gage on other systems. For the inverse, see Emulators on Symbian.

N-Gage is a mobile phone and a handheld game device developed and designed by Nokia Corporation,
announced on 4 November 2002 and released on 7 October 2003.
N-Gage QD introduced in 2004 as a redesign of the original «N-Gage Classic», fixing widely criticized issues and design problems. ‘N-Gage’ was discontinued in February 2006, with Nokia moving its gaming capabilities onto selected Series 60 smartphones.
N-Gage 2.0 was announced in 2007.

Originally a joint Nintendo-Nokia cellphone handheld hybrid project slated for 2005, Nintendo backed away from the project (and its plans for NES/Game Boy ports for mobile were repurposed for their Virtual Engine project). Nokia continued the project on their own anyways and released N-Gage on October 7, 2003, for $299 as the most powerful handheld of its time, that is up until the DS and PSP came along and ended Nokia’s hopes at dominating the handheld gaming market. It had an ARM920T CPU at 104 MHz.

However, while gaining support through GBA/PS1 ports (including the only English version of the JP-only Xanadu series until 2016) and a few original exclusives, the thing suffered from huge design flaws, from the button layout to the display and cell phone functionality. Furthermore, as a derivative of business-oriented devices, it didn’t even have any dedicated video or sound hardware, so not unlike many of the PC MS-DOS games, the main CPU had to take care of it, severely limiting its full potential.

Has a revision called the QD which was unveiled on April 14, 2004, with an ARM9E CPU. ROM dumps of Symbian and N-Gage games are available.

Emulators[edit]

EKA2L1

An open-source high-level Symbian and N-Gage emulator, supported OS S60v1, S60v2, S60v3, S60v5, S^3 and S80.

Engemu

A Nokia N-Gage focused emulator with low-level emulation.

NGEmu

The first known Nokia N-Gage emulator (with high-level emulation), although it is currently on hiatus due to a lack of information required to further development. Linux support is planned for the future.

N-GAGE COOL! — Paid ($)

Early attempt at a commercial N-Gage emulator. Has no real benefits over other offerings

Symbian SDK

https://github.com/mrRosset/Symbian-Archive/blob/master/SDKs-Series.md

Asha OS[edit]

See https://nokia-asha-sdk.software.informer.com/1.0b/ for it’s closed source SDK.

Monochrome mobile phones[edit]

Earlier black & white cellphone games (both in Japan and worldwide) didn’t get as much love either when it comes to emulation and preservation of game binaries. There were, however, recreations of Snake and Space Impact for Nokia phones on their website at one time, along with remakes of the aforementioned games for Android and iOS. There are several Nokia phone models with MAME support, though they are preliminary at best with most models displaying a «CONTACT SERVICE» error if not a white screen.

There however exists an SDK for the Nokia 3410, an enhanced variant of the infamous 3310 with a higher-resolution screen and support for MIDP applications. A fixed rip of the simulator can be downloaded on the Internet Archive, though it may have some issues especially on later Windows versions.

Maemo[edit]

The Maemulator

A compatibility layer for running Bounce Evolution on modern Linux-based systems using qemu user-space emulation. This is not an official port.

QEMU

See http://www.rkeene.org/projects/info/wiki/106 for how to do it. https://marcin.juszkiewicz.com.pl/2008/04/11/nokia-n800-emulation/ and https://marcin.juszkiewicz.com.pl/2008/08/01/nokia-n8x0-emulation-part-ii/ may alternatively be followed.

MeeGo[edit]

mirror.thecust.net/meego_1.2_harmattan_developer_documentation/html/guide/html/Developer_Library_Developing_for_Harmattan_Developer_tools_Emulation_tools_for_Qt_SDK_Using_QEMU_with_Qt_SDK.html

Jolla[edit]

Sailfish OS[edit]

See https://docs.sailfishos.org/Tools/#sailfish-platform-sdk

In-Fusio[edit]

Execution Engine (ExEn)[edit]

ExEn was a freeware solution developed by French company In-Fusio around 2000 and later the company re-developed the ExEn V2 engine in 2002, which further improved the speed and expressiveness of mobile. It was first Java-based game engine entirely dedicated to mobile devices itself as an alternative to the limitations of J2ME’s game development (offering missing feautures like sprite zooming, parallax scrolling, rotations).

The API is based on Java and is very similar to J2ME, but is optimized for game development and deployment instead. Even the programming style is almost the same. Its significance is very similar to the Mophun platform. The ExEn API has various gaming specific classes that are absent from J2ME. ExEn was the first mass market downloadable game engine to be made available in Europe. It achieved relative success and widespread hardware support in Europe, and was also used in China. It’s not as widely distributed though, and according to In-Fusio’s website, it isn’t available on Nokia, Sony Ericsson, Samsung or Motorola handsets.

EXEN-V2 Generic Simulator

An official ExEn implementation from the otherwise-lost SDK. Doesn’t properly work at the correct speed on modern Windows, requiring the use of a virtual machine with an old Windows version such as Windows XP. Crashing issues have also been reported.

BlackBerry[edit]

BlackBerry OS[edit]

A QNX based operating system used in BlackBerry devices.

Palm[edit]

Palm OS[edit]

PalmOS is a mobile operating system developed by Palm, Inc., for personal digital assistants (PDAs) in 1996.

LG[edit]

webOS[edit]

Palm launched webOS, then called Palm webOS, in January 2009 as the successor to Palm OS. The first webOS device was the original Palm Pre, released by Sprint in June 2009. In April 2010, HP acquired Palm, then in 2013 LG acquired them to make webOS for TV, Smartwatch, and Smartfridge. For LG’s webOS see Smart TV Emulators.

TODO: this section is broken, check the history of this section and restore the present metadata but keep the emulator images.

Also see https://liliputing.com/phoenix-devices-gets-open-webos-to-run-as-an-android-app/

WebOS Ports[edit]

LuneOS[edit]

Samsung[edit]

Bada[edit]

Bada (바다) is a mobile operating system developed by Samsung Electronics for devices such as mid- to high-end smartphones and tablet computers. The name is derived from «바다 (bada)», meaning «ocean» or «sea» in Korean. All phones running Bada were branded with the name Wave, unlike Samsung’s Android devices which are branded as Galaxy.

Tizen[edit]

Tizen Studio

Has both a Tizen emulator (more accurate) and a Tizen simulator (more usable for slower computers).

TizMee

Tizen compatibility layer for meego

Google[edit]

Android[edit]

Main article: Android emulators

Apple[edit]

iOS[edit]

Main article: iOS emulators

MediaTek[edit]

MAUI Runtime Environment (MRE)[edit]

Being the turnkey solutions firm that they are known for, as their chips are used on millions and millions of el-cheapo «Shanzhai» devices all over the world (especially counterfeit Nokias and Goophones among other things), Mediatek has also come up with their own mobile platform and API known as the MAUI Runtime Environment. It is targeted for so-called «smart» feature phones, i.e. those that offer similar functionality to standard mobile operating systems like Android, but are watered down for entry-level users. Games and applications for this platform are in .VXP format and other applications appear to be available on the usual WAP sites.

Mediatek MRE SDK

Includes seven phone simulators with various screen resolution presets and user interfaces. Can only run VXP files compiled for the x86 architecture, i.e. apps built for phones will not run.

MREmu

Open source emulator that can run VXPs compiled for ARM. In early development.

Motorola[edit]

MotoEZX / OpenEZX[edit]

MotoMAGX[edit]

Synergenix[edit]

Mophun[edit]

Mophun is an even more hardware-efficient free European-centric mobile gaming solution developed by Swedish company Synergenix Interactive AB. There are two versions of Mophun, 2D for low-end (Sony Ericsson T2xx, T3xx and T6xx series) and 3D for high-end handsets (Symbian S60 and UIQ3 phones), and it’s often used to provide embedded (pre-installed) games on mobile phone handsets.

Mophun Games Launcher

Only compatible with 13 games, all of which use the 3D engine and were released for Symbian S60 and UIQ devices.

4Mophun

Does not work with games that are locked (e.g. have a predefined IMEI recognition algorithm) or do not use the 3D engine.

mophun

An official emulator, designed for development and demos. As such, encrypted or compressed games do not boot. However, this has been worked around, both by decrypting the files and decompressing them (except for compressed resources), and modifying the emulator to perform decryption on the fly, albeit only when opening them via the Open menu. Exile is not known to work in any found version of the emulator.

MoRePhun

A new, open source emulator by Luca91. It is only a proof of concept, as only a few opcodes and a couple of SDK APIs are emulated, and there is no heap. There is sprite and input support, as well as support for the collision API. It is compatible with a few small homebrews. Luca91 mentions the SDK API handler needs to be better organized.

Mophun ActiveX Control

The official website for the platform, mophun.com, used to host development demos playable in the browser using the ActiveX platform (crawled demo files here). The mophun plugin itself can run unencrypted .mpn files. Although it is not playable through the web archives of the site, it is expected to be curated for Flashpoint.

Adobe[edit]

Flash Lite[edit]

Japanese cellphones[edit]

Several Japanese-centric mobile game technologies spawned during the 2000’s as part of convoluted all-in-one technological solutions, mostly based on Java.

• NTT DoCoMo released DoJa (later renamed to Star), based on Java ME CLDC, but not MIDP. Applications come in the form of .JAR files accompained by a .JAM descriptor.

• KDDI released ezplus (later renamed to «EZ-appli (Java)»), based on Java ME extended with proprietary APIs. Applications come in the form of .KJX files. It was later replaced with a BREW-based solution called «EZ-appli (BREW)»

• J-PHONE released J-SKY, based on standard J2ME MIDP extended with several proprietary 3D/sound/gfx APIs. It was later renamed to «Vodafone Live!» and «Yahoo! Keitai» as the company got purchased by Vodafone and SoftBank, respectively. Applications come in the form of .JAR and .JAD files.

It is possible to develop applications that work both under ezplus, J-SKY and standard J2ME devices by using only MIDP1.0 APIs

i-mode (DoJa/Star)[edit]

Japanese mobile manufacturer NTT DoCoMo released DoJa (DoCoMo’s Java) as part of their i-mode set of standards for mobile telephony. It is based on Java ME CLDC, but not MIDP. The profile received several updates, being later renamed to «Star». It was used on DoCoMo’s mova and FOMA series of mobile phones, being first featured on the mova 503i from 2001.

While i-mode phones were made available in a limited fashion in Europe, with various games for DoJa «Overseas Edition» seeing release, the services didn’t prove popular enough and were shut down in a matter of years. The main reason for the limited support was the fierce push back by Nokia and other western mobile hardware manufacturers refusing to support the DoJa software standard until very late.

DeNa (Mobage), Namco (Tales of Mobile) and Level-5 (RoiD) set up Steam-like game distribution portals specific to some cell-phone models yet i-mode based. The different names are to confuse dirty gaijin, probably.

Applications were denominated «i-αppli» (Japanese : iアプリ) and come in the form of .JAR files accompained by a .JAM descriptor text file.

Emulators[edit]

iappli Development Kit for DoJa

Official development kit from NTT DoCoMo, featuring a device emulator. Several releases were archived by Wayback Machine: DoJa 1.5 DoJa 2.? DoJa 2.1 DoJa 3.0 DoJa 3.5 DoJa 4.0 DoJa 4.1 (111) DoJa 4.1 (201) DoJa 5.0 Star 2.0

• Also see Rockman DASH: Great Adventure on 5 Islands & Rockman Tennis Preserved in Full.

javaappli Development Kit for DoJa

SDK for the Overseas Edition DoJa profile from NTT DoCoMo, based on iDKDoJa. Several releases were archived by Wayback Machine: DoJa 1.5 DoJa 2.5

i-JADE

iappli development kit from Zentek

Jade

Open-source project implementing several DoJa 1.5 APIs. Low compatibility

SquirrelJME

Open source emulator that can run J2ME software, will be adding i-Mode support in 2022.

KDDI EZplus[edit]

Japanese carrier KDDI/Au released ezplus as part of their EZweb set of standards for mobile telephony. It is based on Java ME extended with proprietary APIs. The first device supporting it was released on 2001 (Hitachi C451H).
ezplus was later renamed to «EZ-appli (Java)» (Japanese : «EZアプリ (Java)») and gradually replaced with a BREW-based solution called «EZ-appli (BREW)» until 2004 when the last ezplus device was released.

In 2006 an Open Application Player (Japanese: オープンアプリプレイヤー) feature was added allowing to run MIDP 2.0 Java apps on the BREW devices, which were often denominated as オープンアプリ. It lacks support for the original proprietary extensions of ezplus. On 2011, Open Application Player was updated and renamed to «EZ-appli (J)» along EZ-appli (BREW) which became «EZ-appli (B)»

Applications were denominated «ezplus アプリ» (during the ezplus name era) and come in the form of .KJX files.

Emulators[edit]

ezplus emulator

Official development tool from KDDI, developed by Zentek.

J2ME Loader

Now J2ME Loader support ezplus apps that only support 128×160 resolution and font option recommend is (9 — 13 — 15).Installation guid and here

J-SKY[edit]

Japanese service provider ‘J-PHONE’ released the J-SKY platform as part of their set of standards for mobile telephony. It was based on J2ME and MIDP extended with several proprietary 3D/sound/gfx APIs called JSCL.
J-PHONE had been purchased by Vodafone on 2001, which two years later took over the original branding renaming the carrier to Vodafone KK. The J-SKY technology became then known as «Vodafone Live!» and it was extended with the VSCL set of APIs.
On 2006, Vodafone KK was purchased by SoftBank Group, getting this technology rebranded again as «Yahoo! Keitai».

Applications were called «Java™ App» (Japanese : Java™アプリ) during the J-SKY era, «V-Appli» (Japanese : Vアプリ) during the Vodafone era and «S! Appli» (Japanese : S!アプリ) during the SoftBank era. They come in the form of .JAR accompained by a .JAD descriptor text file.

Emulators[edit]

J-SKY Application Emulator

Official development tool from J-PHONE, developed by Zentek. It does not supports any of the later APIs.

MEXA Emulator

Developed by SoftBank for S! Appli.

Korean cellphones[edit]

SKT (Sunkyong Telecom) provided two development platforms: GVM and SK-VM. GVM based on Mobile C, and SK-VM based on Java. SK-VM was a Java-based development platform, but the execution speed was slower than GVM due to the nature of Java. SK-VM is a J2ME (Java 2 Micro Eidtion) Java execution environment developed

GVM (General Virtual Machine): GVM1X, GVM2X
Mobile platform created based on Mobile C (modified to fit the mobile environment, such as reduction of pointer and union functions in the existing C language) developed by Shinji Soft.

GNEX (General & Next Multimedia Player): GVM3X
A mobile platform that eliminates the limitations of the existing GVM and further strengthens functions such as file system, network, and graphics. GNEX is an upgraded version of GVM, and has the advantage of having few capacity restrictions and fast speed, but its penetration has fallen significantly compared to GVM. Therefore, when releasing a GNEX version of a game, we developed both the GVM version and the GNEX version to support phones that do not support GNEX

KTF (Korea Telecom Freete) provided Qualcomm’s BREW. The biggest advantage is that it is based on C/C++, and unlike other development platforms, it is executed in the form of a native binary rather than being executed based on a VM. it is an integrated platform, but it has been divided into SKT-WIPI, KT-WIPI, and LGT-WIPI. For example, SKT-WIPI and LGT-WIPI supported C/C++, while KTF-WIPI supported only C. Aside from that, many other aspects differed from carrier to carrier.

LGT (Lucky Goldstar Telecom) — MIDP [JAVA]
A mobile platform that adds additional functions such as sound to J2ME (Java 2 Micro Edition) of LG MIDP JAVA SUN. LGT’s platform is sometimes called MIDP and JAVA

— SKT’s WIPI-JAVA
— SKT’s WIPI-C
— KTF’s WIPI-JAVA
— KTF’s WIPI-C
— LGT’s WIPI-JAVA (LGT does not support WIPI-C)

Wireless Internet Platform for Interoperability (WIPI)[edit]

WIPI a national middleware platform standard in South Korea. Almost all cellphone games released in South Korea from 2002 to 2009 were developed as WIPI.
SKT (GNEX, SKVM), KTF (BREW), LGT (MIDP-JAVA), etc. are these, and they are currently converting to an integrated platform called WIPI. After conversion to an integrated platform called WIPI, mobile games have higher quality graphics and game ability than before.

Emulators[edit]

Chinese Mobiles[edit]

MiniJ (MRP platform)[edit]

MiniJ is a lightweight mobile platform developed by Hangzhou Sky Network Technology Co., Ltd. and it’s widespread in China (and in some other countries). It has excellent overall performance and could run applications and games smoothly with very limited hardware resources. MiniJ applications are written in C programming language.

Games and applications for this platform are in .mrp format.

Emulators[edit]

KaiOS[edit]

KaiOS is a mobile Linux distribution for keypad feature phones. It is developed by KaiOS Technologies (Hong Kong) Limited.

HarmonyOS[edit]

Huawei’s operating system. Has very controversial advertising. Still in the beta phase and features may change drastically in the future.

Older HarmonyOS (<4.0.0 ?) has compatibility with Android applications (and is commonly doubted as nothing more than an Android fork due to architecture similarities) while newer Harmony OS NEXT removed Android support and is supposed to have a different OS kernel and architecture.

OpenHarmony is the open-source fork of Harmony OS NEXT.

HarmonyOS applications are written in ArkTS programming language which is a fork of TypeScript. Applications packages are in .hap format.

DevEco Studio is the official tool for developing HarmonyOS applications, which comes with an emulator.

Emulators[edit]

Qualcomm[edit]

Binary Runtime Environment for Wireless (BREW)[edit]

A mobile development platform by Qualcomm, originally intended for CDMA handsets such as those sold by Verizon. Unlike Java ME, applications and games for BREW use native code as opposed to running in a virtual machine in the case of Java ME. Also, BREW development has a higher barrier to entry due to stringent certification requirements, which led it to be significantly less popular than Java ME even in markets where CDMA has a significant market share, such as in North America. To top it all off, downloaded BREW apps are tied to an individual handset via a digital signature, making piracy or sideloading difficult; it is however possible to unlock certain BREW-enabled CDMA phones to run backups and pirated apps, though downloads for BREW apps and games are rare and hard to find compared to Java ME.

Zeebo is a Brazilian and Mexican video game console and online distribution platform developed and released with developing markets in mind, also runs on BREW. Dumps of the Zeebo and its games exist, and gameplay footage of them have been uploaded on YouTube.

Danger[edit]

Danger OS[edit]

Developed by Danger Incorporated. Danger OS was a Java-based OS used on phones that Danger designed themselves. These devices were sold under many names such as Hiptop, Mobiflip, Sharp Jump, and (most notably) T-Mobile Sidekick. While it could run some J2ME apps (from version 2.3 onward), it also used its own proprietary J2SE-based APIs and SDK; for this reason, anything built using these APIs won’t run on a standard J2ME emulator. To aid third-party software design, Danger has released a comprehensive SDK that contains a Hiptop simulator, development installation utilities, and Danger API information.

Danger OS uses special files called «bundles». Bundle files have the extension .bndl. Bundles have inside a custom resource format for storing assets and code which is converted from Java bytecode into a custom bytecode format. Each bundle file is linked to a specific operating system version and build number. For example, a bundle file for v3.4/155053 (T-Mobile Sidekick 3) would be denied installation on a v3.3/149695 device (T-Mobile Sidekick iD). Installation of bundles require a developer key to be installed on your device if you are using a Production OS. Internal OS builds do not require developer keys.

Danger Hiptop/Sidekick SDK Simulator

Official SDK from Danger Inc with built-in simulators for testing. These simulators can’t run the special bytecode format used on real devices.

Microsoft[edit]

Windows CE[edit]

Windows Mobile (PocketPC)[edit]

Released in 2000 by Microsoft as their first mobile OS, originally called «Pocket PC» and made to run on PDA’s, the name changed to Windows Mobile when the PDA market began to shrink. WM was initially based on Windows CE before evolving into something unique. It was mainly designed for business users, so it didn’t have a lot of games for it.

QEMU

QEMU can emulate the Windows Mobile firmware via https://allsoftwaresucks.blogspot.com/2016/10/running-without-arm-and-leg-windows.html .

Windows Phone 7.x[edit]

Microsoft’s official Windows Phone Developer Tools Emulator is limited in functionality and only supports running self-compiled apps.

Windows Phone 8.x & Windows 10 Mobile[edit]

TTPcom[edit]

Wireless Games Engine (WGE)[edit]

Mozilla[edit]

Firefox OS[edit]

Amazon[edit]

Fire OS[edit]

Fire OS is a mobile operating system developed by Amazon for their Fire line of devices. It is basically a heavily-modified Android distribution with extensive dependency on Amazon services. Apps sold on the Amazon App Store should run fine on any Android emulator with little to no issue. (Stock) Windows Subsystem for Android is recommended as it includes Amazon-exclusive frameworks.

Siemens[edit]

Siemens & BenQ-Siemens phones[edit]

pmb887x-emu

Emulates phones based on the Infineon PMB8875/PMB8876 chipset (BenQ-Siemens EL71, CF130, E71, C81, M81, Siemens S75). A pre-compiled release is available for Windows. The emulator must be compiled manually for Linux and macOS.

Acknowledgments[edit]

• Micro Java Game Development, mentions Japanese i-mode emulators that are currently dead, like i-tool.

• A 2003 article from GameDev.net about the major Western mobile phone systems.

• Article about DoCoMo Java programming.

Nokia X[edit]

Not to be confused with HMD-Nokia X, or Symbian-based Nokia Xseries.

An Android distro made by Nokia, an emulator is available at: https://web.archive.org/web/20140627005455/http://developer.nokia.com/nokia-x/downloads

See Also[edit]

• Cellphone games preservation
• Kahvibreak

References[edit]

This article is a never-ending list. It will always need updates and will likely have new content added to it on a consistent basis. Because of this, it can never truly be a finished article.

License: 
All 1 2 | Free

License: 
All 1 2 | Free