(Difference between revisions)

Archived:Hiding unnecessary access points from user display on Symbian

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot fixing redirect link.(Moving links from forum.nokia.com TO developer.nokia.com))
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot change of template (Template:KnowledgeBase) - now using Template:ArticleMetaData)
Line 3: Line 3:
|platform=S60 3rd Edition, FP2
|platform=S60 3rd Edition, FP2
Line 11: Line 11:
|creationdate=October 30, 2008
|creationdate=October 30, 2008
|keywords=CApSettingsHandler, RCmManager  
|keywords=CApSettingsHandler, RCmManager  
|sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) -->
|installfile= <!-- Link to installation file (e.g. [[Media:The Installation File.sis]]) -->
|sdk=<!-- SDK(s) built and tested against (e.g. [http://linktosdkdownload/ Nokia Qt SDK 1.1]) -->
|devicecompatability=<!-- Compatible devices (e.g.: All* (must have GPS) ) -->
|signing=<!-- Empty or one of Self-Signed, DevCert, Manufacturer -->
|capabilities=<!-- Capabilities required (e.g. Location, NetworkServices.) -->
|author=[[User:Technical writer 1]]

Revision as of 14:42, 24 June 2011


Article Metadata
Tested with
Devices(s): Nokia N96
Platform(s): S60 3rd Edition, FP2
S60 3rd Edition FP2
Keywords: CApSettingsHandler, RCmManager
Created: User:Technical writer 1 (30 Oct 2008)
Last edited: hamishwillee (24 Jun 2011)


On some S60 3rd Edition, Feature Pack 2 devices there is a hidden access point called "IPDC" which is used only by the mobile TV engine and should not be presented to end users.

Depending on the method used for access point handling, this AP may be listed as one of the connection points. Typically, the problem occurs when using the deprecated Access Point Engine (APEngine) API.


These applications should deal with access points in S60 3rd Edition, Feature Pack 2 by using the Connection Method Manager (CMManager) component. If CMManager is used, the IPDC access point will remain hidden.

APEngine is deprecated from S60 3rd Edition, FP2 onwards and using it is discouraged. However, if its still required for compatibility reasons, note the following things:

The communications database in, for example, the Nokia N96 is constructed as follows:

Access Point Name    IAP ID    WAP ID
        Easy WLAN         1         1
             IPDC         2         -
         internet         3         2
              mms         4         3
              wap         5         4

APEngine returns the WAP ID to application. If the application needs to have an IAP ID, then CApUtils::IapIdFromWapIdL() can be used for conversion between WAP ID and IAP ID. When accessing the communications database directly (not using CMManager or APEngine), the same can be achieved by reading the WAP ID from the WAP_ACCESS_POINT table and then mapping that ID to the correct IAP ID:

 // commDb is a pointer to CCommsDatabase
CCommsDbTableView* wapTable = commDb->OpenViewMatchingUintLC(
TPtrC(COMMDB_ID), wapID );
User::LeaveIfError( wapTable->GotoFirstRecord() );
TBuf<64> wapBearer;
wapTable->ReadTextL(TPtrC(WAP_CURRENT_BEARER), wapBearer);
if ( wapBearer != TPtrC(WAP_IP_BEARER) )
User::Leave( KErrInvalidBearerType );
CCommsDbTableView* bearerTable = commDb->OpenViewMatchingUintLC(
wapID );
User::LeaveIfError( bearerTable->GotoFirstRecord() );
bearerTable->ReadUintL(TPtrC(WAP_IAP), iapID );
CleanupStack::PopAndDestroy(2); // bearerTable, wapTable

See also

S60 Platform: Access Points Example with Roaming Support - Example application for access point handling on S60 3rd and 5th Edition devices, including application-level roaming using service network access points (SNAPs), supported from S60 3rd Edition, FP2 onwards.

103 page views in the last 30 days.