Everyone is talking about Smart Phone-RAM, but do you know exactly what that means RAM? RAM (Random Access Memory) can not be conceived as a temporary storage for your Smartphone. Whenever you start a program or open a file, the smartphone that stores information on them in the RAM. It is important to recognize that the RAM is finished, which means that more applications or files that you open, less memory available. Have you ever noticed that your phone works much slower than before? Or there is often a pop-up window of the reference to “The memory is low”? Indeed, all these problems can often be due to a loss of memory or a bad memory.

Today I want to create a powerful mobile-RAM Booster to you. This is a new program called MemoryUp shared by eMobiStudio Inc. MemoryUp is a powerful Java Virtual Machine (JVM) and improved management of the RAM tool specially designed for High-End Smart Phones and BlackBerry. MemoryUp What does control of the JVM for each mobile intelligent system to analyze ongoing programmes J2ME (including hidden programs), and automatically affect each reoccupied RAM system and boost her best performance. In the case of some applications are no longer active on a Smartphone or Blackberry, MemoryUp can recover the loss of resources and better use. With the recovery of resources, the mobile system must not access the hard drive as often. This will significantly improve the overall performance of mobile phones.

Popularity: 16% [?]

You can deliver an application package to a user’s Smartphone device in a number of ways, including ActiveSync, a web download, an e-mail attachment, Service Indication (SI) SMS (Short Messaging Service) or Service Loading (SL) SMS, or storage cards. The SMS methods for application package delivery take advantage of commonly used text messaging services to send a download URL as a text message to a user. Visual Studio 2005 does not provide a simple solution to application delivery. It is up to the developer or the mobile network operator to select which method to use. The following is a summary of these methods:

• ActiveSync. A user’s Smartphone can be connected (docked in a cradle) to a desktop computer via a USB or serial port. Once a partnership relationship is established via the ActiveSync program, the Smartphone can synchronize e-mail, contacts, calendars, pictures, and so on with the desktop computer. Usually an application’s CAB file is further packaged using an installation setup tool such as InstallShield. To transfer the setup package of an application to the Smartphone, a user needs to run a setup program of the application on a desktop computer, which performs some compatibility checking and copies the CAB file to the Smartphone device. Continue Reading →

  Popularity: 19% [?]

After debugging and testing an application on a real Smartphone device, you may deploy the application on a user’s device. There are three stages in the entire deployment procedure:

1. Package the application using a Visual Studio 2005 Smart Device CAB project.
2. Deliver the package to a user’s device via a web server, an ActiveSync copy, an e-mail attachment, or a storage card.
3. Install the package onto the device.

The following section focuses on the first stage, packaging the application, as this is a core functionality of Smart Device application support in Visual Studio 2005. You will notice the significance of application security in the domain of Smartphone application development. We then briefly introduce several methods for delivering and installing packages.

Packaging Applications
To package a Smartphone application, you must add a Smart Device CAB (cabinet) project to your Visual Studio 2005 solution. From the main menu, select FileAddNew Project. In the Other Project Types category, select Setup and Deployment, and then choose Smart Device CAB Project (not CAB Project) from the Visual Studio installed templates, as shown in Figure 1. A folder with the name of the Smart Device CAB project will be generated under the solution directory. The IDE also presents you with a File System Editor window that shows the filesystem entries you can create on a target device. A CAB file is a type of compressed executable archive file that can contain your application assemblies (EXEs and DLLs), dependencies such as DLLs, resources, help files, and so on, as well as any files related to application security. Most important, an INF (information) file will be generated to describe the destination directory of each installation file on a target device, versions of Windows Mobile for Smartphone on which the application is intended to run, and versions of required .NET Compact Frameworks.

To link the Smart Device CAB project with the FirstSmartphoneApp project, first click Application Folder in the File System Editor window. Then, from the Visual Studio main menu, select ActionAddProject Output, choose the FirstSmartphoneApp project in the Add Project Output Group dialog box, and choose Primary Output from a list of packaging options; thus, only assembly files will be packaged. You can also right-click Application Folder in the File System Editor window to link the Smart Device CAB project with your application project, as shown in Figure 2.

Once you add the application project to the Smart Device CAB project, you may choose to add a registry entry to a target device as part of the application’s installation. In fact, many software products for Windows will create some registry keys for saving configuration settings. To add a registry key for your company named CoolMobile, open the Registry Editor by selecting ViewEditors in the main menu. Then, in the Registry Editor window, browse to HKEY_CURRENT_USER\SOFTWARE\%Manufacturer% and add a new key with a string value of CoolMobile. Now you are ready to build the Smart Device CAB project. This will generate either a Debug folder or a Release folder in the Smart Device CAB project folder, depending on the active configuration of the project. In addition, three files are created in the Smart Device CAB project folder:

• A CAB file (CABProjectName.cab)
• An INF file (CABProjectName.inf)
• A Cab Wizard log file (CabWiz.log) that contains logging information about the packaging process

To be continued…

Popularity: 11% [?]