Ами напротив 3650 също може да стартира N-Gage игри само, че не всички. Разликата между N-Gage и 3650 не е във флаш паметта а в RAM паметта и това е причината да не могат да се стартират всички игри. Точно това е и другата разлика между 6600 и 3650 като пренебрегнем това, което ти искаш да пренебреграваме.
Темата за разликите между Symbian 6.x и Symbian 7.0s я дъвкахме вече веднъж, но ти сигурно не си я чел щом пак питаш. След като ти отговоря и на останалите въпроси ще ти пейстна какво е ново в Symbian 7.0s. Не е само Java, както на някой може би им се иска да е.
Това за тунера е пълна глупост защото телефона приема и предава на точно определена честота, която не се определя от операционната система. Ако беше така, нямаше да е нужно да правят две версии на телефона ами направо щяха да пуснат нов фирмуер, който кара телефона ти да работи на 850 MHz. Забрави го това. Word, Еxcel и ZIP могат да се отварят но преди това май нещо трябва да ги конвертираш. Е ZIP може директно.

Ето ти и за разликите в Symbian



Introduction

Symbian OS v7.0s was announced at Exposium 03. Building on v6.1 and extending v7.0 functionality, v7.0s enables even richer smartphones with an improved user experience, further driving adoption and operators' average revenue per user (ARPU). This article reviews what v7.0s means for mobile phones and for the applications developer.

What Is New in Symbian OS v7.0s

The most significant changes in v7.0s are:

* Improvements to the telephony and networking architecture, allowing more advanced services and access to the latest network technologies.
* A more efficient and extendable multimedia framework (MMF), which replaces the Multimedia Server in earlier Symbian OS releases.
* Inclusion of the latest Java™ MIDP 2.0 technologies and extensions for messaging and Bluetooth services.
* A new SyncML Data Sync (SyncML DS) client and USB client.
* The addition of bidirectional support for languages such as Arabic and Hebrew.

All these changes have been made with careful consideration given to backward compatibility, so that most applications developed for the Series 60 Platform using Symbian OS v6.1 will be compatible with new phones running v7.0s.

Telephony And Networking

Symbian OS v7.0s provides support for all the latest mobile technologies, including GSM, General Packet Radio Service (GPRS), Enhanced Data Rates for Global Evolution (EDGE), CDMA (IS-95), 3rd Generation Partnership Project (3GPP) Wideband CDMA (WCDMA) (R99/R4), and 3GPP2 CDMA2000 1x (Release A). Many parts of Symbian OS telephony and networking architecture have been improved to facilitate access to these 2.5G and 3G technologies and to enable exciting new applications and content for advanced smartphones.

For mobile phones based on Series 60 with Symbian OS v6.1, a user can have only one connection to a network at a time. If, while browsing a news site using an XHTML/WAP browser, a user is sent a Mobile Messaging Service (MMS) message, the WAP connection is suspended while the MMS message is received, and the user is unable to browse to new WAP pages.

This is a limitation of an architecture that allows only a single concurrent connection or Packet Data Protocol (PDP) context. New mobile phones based on the v7.0s architecture will be able to support as many simultaneous connections as the phones have resources for. So now, users could be receiving streaming audio while synchronizing their agendas via a corporate network's SyncML DS server and browsing, and could still be able to receive MMS messages without interruption to any of the services. The available resources – those on the phones or those that involve network bandwidth – are the only factors that limit the user experience.

To achieve this, the communications and network architecture has been changed to support features that include the following:

* Multiple primary and secondary PDP contexts.
* Multihoming.
* Quality of service (QoS).

These are all required to enable advanced services such as video conferencing and simultaneous access to the network by multiple applications.

A PDP context can be thought of as a single connection to a network. PDP contexts can be further broken down into two types – primary and secondary. A primary PDP context is a connection from the mobile phone to the network with one IP address allocated to it. A secondary PDP context is one that shares an IP address with a primary PDP context, but that represents another connection to the network. Each PDP context can have a QoS associated with it that helps prioritize network traffic.

These features are important to advanced services such as video conferencing. When the user initiates a video conference session, three contexts are used to deliver the service. A primary PDP context provides control information, and secondary PDP contexts provide audio and video.

It makes sense that only one IP address is used, since all the information is going to the same place, even though there are three channels for the information. It is desirable for video to arrive in a continuous stream, but if bandwidth is limited, then it is acceptable to drop a few video frames just as long as the audio does not clip and is intelligible. Therefore, the control channel would need a high-priority, low-bandwidth QoS; the audio would need a medium-priority, medium-bandwidth QoS; and the video would need a low-priority, high-bandwidth QoS.

While video conferencing utilizes a single primary PDP context, Symbian OS v7.0s also supports multiple concurrent IP addresses, an ability described as multihoming. Where a user may be streaming audio and browsing while performing a back-office synchronization and receiving an MMS message, he or she is likely to be using multiple IP addresses. Again QoS policy comes into play, because audio streaming would need the highest priority and QoS so that audio was intelligible. It would be desirable for the WAP connection to remain responsive, so this should have the next-highest QoS; MMS and SyncML DS should have the lowest QoS, since they are not real-time requirements.

Not only does this ability to have multiple contexts make a direct impact on the quality of the user experience, but network providers also find the concept of multiple PDP contexts very attractive. It allows them to bill separately for different types of data traffic as well as to prioritize and manage access points for the loads created by different services.

However, v7.0s does not limit multihoming to the telephony side; it also allows different IP addresses for other services such as Bluetooth wireless technology, PC connectivity, or Ethernet. Only the availability of system resources limits the number of simultaneous connections, and it is possible to dynamically load or unload them without restarting the TCP/IP stack.

Improved Transport Architecture

The existing transport architecture in Symbian OS v6.1 involves different stacks' implementation and associated APIs for each protocol. As a result, developers may have limited the choice of network transport simply to avoid the complexity of learning the APIs for multiple protocols.

Symbian OS v7.0s incorporates the more efficient transport architecture that was released in v7.0. This transport architecture allows developers to access several different protocols with the same API. It has a general API for HTTP-like protocols and a modular framework that uses filters, transport handlers, and protocol handlers into which protocols can be plugged; these elements are equivalent to Layers 2, 3, and 4 of the OSI (Open System Interconnection) model. This architecture can handle most types of protocol encoding, including HTTP and WAP Wireless Session Protocol (WSP) stacks, as well as secure and non-secure connections.

Applications that use HTTP and WSP stacks, such as SyncML DS, application installation, WAP, and the Mobile Information Device Profile (MIDP), will use the new transport architecture. Ideally, all third-party applications that use these protocols should move to this new transport architecture.

Also provided in v7.0s is a dual IP stack that supports both IPv4 and IPv6 addressing. The IP stack supports IPSec as a plug-in module to the transport architecture.

Multimedia

The Media Server from v6.1 has been improved to provide a lightweight, easier-to-use, multithreaded, and more efficient plug-in architecture. The new MMF is well-suited for video processing and other high-bandwidth applications. Being multithreaded, it eliminates resource conflicts that could occur in applications where multiple soundtracks were required simultaneously, such as in games, and overcomes issues such as audio clipping.

Combined with the Image Conversion Library (ICL), the MMF essentially replaces the old Media Server.

The ICL supports still-image encoding and decoding. It can be multithreaded from the client side, and all the standard formats from v6.1 are supported. Developers can choose to run encoders/decoders under the client thread of their application or to instantiate a separate process.

The MMF handles video and audio codecs via the new plug-in framework. The standard audio and video codecs are still supported, and many new ones are likely to be provided by third parties such as Real, Beatnik, and PacketVideo.

Applications that used the v6.1 Media Server API should be compatible with the new MMF; however, the plug-in modules from v6.1 will not be compatible.

Java

For developers working with Java™ technology, v7.0s implements MIDP 2.0 (sometimes called MIDP NG). The new version of Symbian OS has the much-extended API that is compliant to the MIDP 2.0 and CLDC 1.0 standards. Enhancements have also been made to the architecture, which now utilizes Sun's CLDC HI Java VM to give even better application performance.

MIDP offers developers two main advantages – it allows them to target multiple platforms with one application as well as to create applications for the Series 60 Platform without having to learn Symbian OS and Series 60 APIs. MIDP 1.0 allowed developers to create simple games and applications that are portable between compliant devices. MIDP 2.0 builds on this capability and includes support for better audio and graphics. In addition, heap and persistent storage is unrestrained, allowing richer and more exciting MIDlets.

The implementation of MIDP 2.0 within v7.0s also includes these optional CLDC packages:

* Wireless Messaging API (WMA) 1.0 (JSR-120): This API provides platform-independent access to wireless communication resources, and can use Short Message Service (SMS) and Cell Broadcast Service (CBS) on GSM networks.
* Bluetooth Wireless Technology API (JSR-82): This API provides access to Symbian OS Bluetooth stack and profiles.

Other Notable New Features

SyncML DS
A Symbian OS implementation of a SyncML DS client that is compliant with the SyncML DS 1.01 specification is now included. It has a plug-in framework that allows new transport bearers and data readers to be added as required. The framework will allow developers to add synchronization facilities for their own value-added applications.

USB Client
For mobile phones that require connectivity with a USB host, such as a PC, standard USB support is now provided. The USB middleware framework provides support for the WMCDC, WHCM and OBEX class, and for the CDC ACM class.

Support For Bidirectional Text
Support for bidirectional text such as Thai, Arabic, and Hebrew has been included. Features include functionality for rendering, editing, and drawing bidirectional text to graphics objects, which will improve the ability to localize mobile phones to specific markets.

Compatibility

A key goal of this release is to help mobile phone manufacturers maintain compatibility between phones that are based on v6.1 and those based on v7.0s. Release v7.0 (the basis of UIQ) of Symbian OS is not binary- or source code-compatible with v6.1. Applications developed on v6.1 represent a significant investment for developers; recognizing this, Symbian has taken great care to ensure that data compatibility and, where possible, binary- and source code-compatibility of Symbian OS components have been maintained between v6.1 and v7.0s.

Most interfaces published in the SDK for v6.1 will continue to be supported for v7.0s.

Conclusion

Symbian OS v7.0s extends v6.1 significantly to enable use of many new mobile phones and services for 2.5G and 3G networks.

What follows is a summary of the improvements:

* The introduction of multihoming, multiple PDP contexts, and a QoS framework enables many new innovative services that can take advantage of multiple connections, peak/off-peak bandwidth utilization, and multiple access points.
* The improved transport framework makes it easier for an application to target multiple protocol stacks without the developer having to learn the complexities of each stack's implementation.
* The new MMF and ICL are easier for developers to use than the v6.1 Media Server and offer much-improved media handling.
* MIDP 2.0 is supported in v7.0s and contains extensions that allow developers to access Bluetooth and messaging features.
* SyncML DS offers an extendable framework for which developers can add services, and USB client support adds to the connectivity options of Symbian OS.
* Internationalization now supports bidirectional languages, allowing developers to target Asian and Middle Eastern markets utilizing their local languages.
* Where possible, forward compatibility between v6.1 and v7.0s APIs has been maintained, and many applications written for v6.1 will work on mobile phones based on v7.0s.

Developers can leverage many of these new features to create exciting new services and applications that utilize the capabilities of advanced smartphones.