If email is enabled and properly configured (see Enable Handset Email Client), the RAZR V3xx can be used to wirelessly email digital photos from regular digital cameras that use removable memory cards compatible with microSD used in the RAZR V3xx. For example, a regular digital camera that uses SD cards can store digital photos on microSD cards by means of inexpensive microSD to SD adapter.

The reason this works is that digital cameras store photos in a \DCIM directory, and while the RAZR V3xx normally stores files in the \mobile directory, it can also access multimedia files stored in the \DCIM directory. (Both directories should be left intact as long as the microSD card isn't erased or formatted.) Since the RAZR V3xx doesn't support large high-resolution photos, it displays a red X instead of a preview image.

The sending method is to create an email message, and attach digital photo(s) to the message.

Some online digital photo sharing services are able to automatically receive, store, and display digital photos sent by email (e.g., MyPhotoAlbum).

The new MOTOROLA ATRIX 4G is a dual-core smartphone with online computer power. Using the webtop application and smart-dock accessories, you get a full Firefox browser and access to all your documents. In North America, Motorola ATRIX 4G is only carried respecitvely at AT&T in the States and at Bell in Canada.

In addition to data transfer, Standard-A to Mini-B USB cables can be used to charge and/or power USB-equipped Motorola handsets from standard USB ports.

The problem is that not all Standard-A to Mini-B USB cables are the same
-- there are both 5-connection cables and 4-connection cables, and only
proper 5-connector cables will work properly without a Motorola USB driver. Standard USB has only 4 connections. Mini USB has 5 connections, the extra connection being the device ID pin.

Motorola Phone Tools is a Motorola brand-specific version of mobile PhoneTools, a program written by the French-based company Avanquest Software (formerly BVRP). The program allows users of Motorola and other brands of cellular phones to connect their cellular phones to their personal computer.

A handset should not be connected to the computer before installing Motorola Phone Tools, because if it is, Windows may install a generic driver that won't work with Motorola Phone Tools. If this has happened, download and install Motorola USB Modem driver version 3.4.0.0 (registration required but free), which should correct the driver problem.

Recent versions of the Motorola USB Modem driver will cause Windows
XP to crash when Resuming from Standby or Hibernation if a Motorola
handset (e.g., RAZR V3xx) was attached when the computer went into
Standby or Hibernation.

(The bug is actually in the Windows DDK {Driver Development Kit} which
the Motorola driver is built on.)

In the latter case, the only currently known way to recover the 12.0 Mbps port speed is to use System Restore to roll Windows XP back to a point before the Bluetooth pairing (and not to Bluetooth pair thereafter). Uninstalling the Bluetooth modem and pairing alone isn't enough, even if the USB Modem is then uninstalled and reinstalled.

On a "3G" (HSDPA/HSPA) connection, the 12.0 Mbps port speed is noticeably snappier than 921600 bps.

Be sure to permanently backup your unmodified skin files prior to making modifications. Backup may be performed using P2K Commander by navigating to the handset's system directory /a/mobile/skins/, then copying the contents of the specific skin directory to your computer; e.g., copy all files in directory Cingular, Indium, or Disco (etc.) to a backup location on your computer.

An email client is built into the handset, but hidden (disabled) by Cingular. When enabled and setup properly, it can be used to receive and send email using a standard email service (but not Cingular email).

radioBee (streaming Internet radio, still a work-in-progress, but promising)

Download with handset browser from www.radiobee.com/rb.jar

Registration is free

Important Notes:

The handset will prompt for every network access by unsigned apps, which can be very annoying.

Ask Only Once can be enabled for unsigned apps by deleting j2me_domain_registry.sm from handset \a\mobile\certs\root\x509\kjava\ with P2K Commander, and restarting the handset, which must be done before downloading and installing unsigned apps. (If already installed, they must be deleted and reinstalled.)

However, deleting j2me_domain_registry.sm will "corrupt" Cingular and signed apps so they won't work and can be deleted if accessed.

Lighting patterns displayed on the Cingular V3xx are defined by FLP files. FLP (Fun Light Pattern) files are text files identified by the .flp extension. All FLP files may be modified to create visual light effects different from the standard patterns or those provided in the Basic Modding section. A simple text editor is used to create or modify an FLP file.

NOTE: Crimson Editor is recommended to edit text files on a Windows XP platform. While Microsoft Notepad or Microsoft Word may be used for text editing, these programs are not recommended. Notepad does not display FLP files as line-by-line definitions. Word does not save the text file in the proper format. Word adds a carriage return (0x0D) after every linefeed (0x0A) requiring an extra step to remove the 0x0D.

A standard Cingular V3xx comes with twelve FLP files. Only five are used by the V3xx while the others are unused. These files are located in the /a/mobile/system/ directory of the handset:

FLP files start with a four line header. Every FLP file must contain the unmodified header. The header does not define the specific operation of the light pattern. It is used by the handset's operating system to identify the FLP's format and use.

The duration of the light pattern sequence is defined by the Period statement. The Period value is defined in milliseconds. It's value is equal to the duration of the complete sequence, in milliseconds, plus 1. The Period is always equal to the last value contained in the last Set statement plus 1. The statement is always terminated with a semicolon(;).

Individual lights are turned on or off with the Set statement. The Set statement also defines the brightness of the light and the time within the Period this statement is to be executed. The statement is always terminated with a semicolon(;). There are four fields in the Set statement:

ID - Field 1

The ID number identifies the light to be turned on or off. The Cingular V3xx supports the following IDs:

The Brightness is a hexidecimal value between 0x000 and 0xFFF that defines how bright or dim the light source is to be displayed. The value 0x000 represents no illumination while 0xFFF represents 100% illumination. Useful values:

0x000 - Off (the dimest setting)

0xFF3 - 1/4 illuminated

0xFF7 - 1/2 illuminated

0xFFB - 3/4 illuminated

0xFFF - Fully illuminated (the brightest setting)

NOTE: Motorola uses the Big Endian system to order and store data. The Brightness value must be specified in Big Endian format. Effectively, this means the rightmost nibble is the most significant digit while the leftmost nibble is the least significant digit. Specifically, a desired Brightness value of 0x3FF should be entered into the FLP file as 0xFF3. Entering the value incorrectly as 0x3FF is translated by the handset's processor as 0xFF3 or close to full illumination when the desire effect is 1/4 illumination. The user may find using values such as 0x000, 0x111, 0x222,...0xDDD, 0xFFF more practical in avoiding programming confusion.

Timestamp - Field 4

The Timestamp specifies when within the Period the statement is to be executed. Like the Period(value), the Timestamp is defined in milliseconds. The Timestamp must be less than the Period(value) and the last Timestamp of the last Set statement is equal to the Period(value) minus 1.

The first Set statement from the example is Set(7,0,0xFFF,0);. This statement defines the red LED (ID = 7) as having a brightness of 0xFFF (fully illuminated) and is executed at time 0 (the beginning). The second statement Set(7,0,0x0,500); tells the red LED to turn off (0x0) at 500 milliseconds into the routine. The final statement Set(7,0,0x0,5500); does not change the brightness of the red LED from the previous statement but terminates the routine 5000 milliseconds after the previous statement or 5500 milliseconds after the beginning of the sequence.

This description is consistent with the purpose of FLP file 159.flp. That is, to signify that charging of the handset battery is complete. Effectively, the red LED turns on for 1/2 a second then turns off for 5 seconds. The blinking pattern repeats as long as the "charge complete" status is active.

This example illustrates how a light's brightness may be controlled. Two light sources are used in this example, the LCD backlight and the blue LED. The sequence begins at time 0 by turning off both lights. Then every 1/8th of a second (125 milliseconds) the LCD backlight's brightness in increased by 1/8th of it's illumination potential. 1/8th of a second after the backlight reaches full illumination it is turned off and the blue LED is turned on to full illumination. Then every 1/8th of a second the blue LED's brightness is reduced by 1/8th of it's illumination potential until it is down to 1/8th brightness. The pattern repeats.

This example illustrates that the Timestamp of the first Set command does not have to begin at time zero. Here the pattern begins by turning the blue LED on full brightness at time 75. Then 75 milliseconds later the blue LED is turned off and the red LED is turned on. Next, after another 75 milliseconds, the red LED is turned off and the camera LED is turned on. Finally, after yet another 75 milliseconds, the camera LED is turned off. The pattern then repeats in a loop. The effect is a clockwise flashing pattern of the three LEDs.

NOTE: The red power/charge LED is only visible when the handset is plugged into the charger or the USB port.