[Windows Mobile Apps and Games] Chainfire:
The Manual #2 (0.5 and newer) - READ IT! + Some screenshots from 0.55 (resized)

Data / Disallow background connections

When this option is enabled, WMLongLife will deny access to applications creating so called "background" connections, and only allow "interactive" connections. When an application connects to the internet, it tells Connection Manager some specifics. Only interactive applications like browsers / YouTube / etc should create "interactive" connections, while other application that need something from the internet but which you did not manually initiate should create "background" connections. Obviously this setting only has an effect on applications that set this information correctly. If you have connection notifications turned on, "interactive" connections are the ones that pop-up a "Connecting to ..." bubble - "background" connections do not do this.

Roaming / Disable cellular data connections when roaming

[no longer available in 0.65, use RoamFreely instead]

This option allows you to configure which data connections you want to disable when you are roaming.

Roaming / Switch to 2G when roaming

When this option is enabled, WMLongLife will switch to 2G when you are roaming.

Roaming / Treat 2G as roaming

[no longer available in 0.65, use RoamFreely instead]

When this option is enabled, WMLongLife will treat a 2G signal as if you are roaming. Obviously, when using this option, you should disable all other options that may make the device switch to 2G - if you don't, this will result in WMLongLife always thinking you are roaming.

Roaming / Turn off AGPS when roaming

[no longer available in 0.65, use RoamFreely instead]

This option should only be enabled if you actually use AGPS. This should be auto detected upon first installation, however this detection does not always work correctly. If you do not use AGPS, make sure this option is turned off. If you do not use AGPS but this option is enabled, WMLongLife will also enable AGPS when you are not roaming. If your AGPS is not properly configured, this may slow down normal GPS operation.

Configuration - Application specific

WMLongLife comes preconfigured with optimal settings for various common applications. However, should you use an application that is not listed here, WMLongLife will automatically pop-up a configuration box when that application tries to use the internet. It is not possible to manually add or remove applications from the application list - and this is completely unnecessary!

The application specific configuration screen shows the list of configured applications, and icons to show their currently configured options. When you click an application in the list, the application configuration screen will popup.

There are five options in this popup: 3G, Screen/Off, Wi-Fi and USB.

3G

This option decides whether or not WMLongLife should give 3G to this application. If the 3G option is not enabled, all the other options are not relevant.

Screen/Off

This option decides whether or not WMLongLife should give 3G to this application, even if the screen is turned off. Most applications do not need this - pretty much the only exceptions are tethering applications.

Wi-Fi

This option lets WMLongLife know if this application can use Wi-Fi instead of 3G for its internet connection. Most applications can, however obvious exceptions are (again) tethering applications.

USB

This option lets WMLongLife know if this application can use USB instead of 3G for its internet connection. Most applications can, however obvious exceptions are (again) tethering applications.

Background time-out

This option configures how long WMLongLife will treat an application as "running" if it has not been actually visible on your screen. This only applies to applications that do not actually close when you press the "X" button. If an application is truly closed, WMLongLife will immediately treat it as "not running". However, applications like for example the Opera browser will always remain running in the background, whether you are using them or not, these will be treated as "not running" when they have not been "seen" for the length of time the background time-out is configured.

Most applications should be fine with a setting of 5 minutes or less. Applications that continue to use the data connection (like tethering applications) should have the time-out disabled.

----