Hiding Your Application from task list

If you want to hide the application from the system task list add this method to the document class:

void CApplicationDocument::UpdateTaskNameL(CApaWindowGroupName* aWgName)
   {
   CAknDocument::UpdateTaskNameL(aWgName);
   aWgName->SetHidden(ETrue);
   }

or put in this code:

CEikonEnv::Static()->RootWin().SetOrdinalPosition(0, ECoeWinPriorityNeverAtFront);

Restart Phone With Low CAPABILITY

RWsSession iWs;
User::LeaveIfError(iWs.Connect());
TWsEvent e;
e.SetType(EEventPointer);
iWs.SendEventToOneWindowGroupsPerClient(e);
iWs.SendEventToAllWindowGroups( e);

Lock phone from code

RAknKeyLock keyLock;
User::LeaveIfError(keyLock.Connect());
CleanupClosePushL(keyLock);
keyLock.EnableKeyLock();
keyLock.Close();
CleanupStack::PopAndDestroy();

How can I determine the application language at run time?

The current language the application is using to display its UI can be retrieved with
TLanguage lang = CEikAppUi::ApplicationLanguageL();
For a non-localized application, this value is TLanguage::ELangNone (0xFFFF).
Note that this value may be different from the language returned by
User::Language();
which represents the language of the current locale (system-wide setting).

Trolltech's "Green Phone" stack architecture

Trolltech, best known for development tools and Linux application stacks for phones and other mobile devices, will ship an "open" Linux-based phone in September,2006. The "Greenphone" features a user-modifiable Linux OS, and is meant to jumpstart a third-party native application ecosystem for Linux-based mobile phones.

Get cell broadcast

Header file

#ifndef __CBUTIL_H__
#define __CBUTIL_H__

#include <e32base.h>
#include <Etel3rdParty.h>

#include <etelmm.h>
#include <etel.h>
#include <etelmmcs.h>
#include <flogger.h>
#include <csmshandler.h>

class CCBUtil : public CActive
  {
  public:
      CCBUtil();

      static CCBUtil* NewL();

      void ConstructL();

      ~CCBUtil();

  private:
      void RunL();

      void DoCancel();

  private:
      RFileLogger                iLog;

      TRequestStatus iReqStatus;

      RTelServer iServer;

      RMobilePhone iPhone;

      RMobileBroadcastMessaging iBroadcastMsg;

      TBuf8<88> iGsmMsgdata;

      CSmsHandler* iSmsHandler;

      };

#endif // __CBUTIL_H__

Source File

#include "cbutil.h"
#include <eikenv.h>
#include <Etelmm.h>
#include <Etel3rdparty.h>
#include <stdio.h>

_LIT(KGsmModuleName,"phonetsy.tsy");

CCBUtil::~CCBUtil()
  {
  Cancel();
  iPhone.Close();
  iServer.UnloadPhoneModule(KGsmModuleName);
  iServer.Close();
  iLog.CloseLog();
  iLog.Close();
  }

CCBUtil* CCBUtil::NewL()
  {
  CCBUtil* self = new (ELeave) CCBUtil();
  CleanupStack::PushL(self);
  self->ConstructL();
  CleanupStack::Pop();
  return self; 
  }


void CCBUtil::ConstructL()
  {
  RTelServer::TPhoneInfo iPhoneInfo;
  iServer.Connect();
  iServer.LoadPhoneModule(KGsmModuleName);
  TInt enumphone;
  User::LeaveIfError(iServer.EnumeratePhones(enumphone));
  if (enumphone < 1)
      {
      User::Leave(KErrNotFound);
      }
  User::LeaveIfError(iServer.GetPhoneInfo(0, iPhoneInfo));
  User::LeaveIfError(iPhone.Open(iServer,iPhoneInfo.iName));
  iBroadcastMsg.Open(iPhone);
  RMobileBroadcastMessaging::TMobileBroadcastAttributesV1 iAttrInfo;
  TPckg<RMobileBroadcastMessaging::TMobileBroadcastAttributesV1> iDes(iAttrInfo);
  iBroadcastMsg.ReceiveMessage(iStatus,iGsmMsgdata,iDes);
  SetActive();
  }

CCBUtil::CCBUtil()
  : CActive(EPriorityNormal)
  {
  CActiveScheduler::Add(this);
  }

void CCBUtil::RunL()
  {
  if(iStatus==KErrNone)
      {
      RFs fs;
      fs.Connect();
      RFile file;
      TBuf<32> aFileName = _L("C:\\log.txt");
      fs.Delete(aFileName);
      file.Replace(fs,aFileName,EFileWrite);
      file.Write(iGsmMsgdata);
      file.Close();
      fs.Close();

      FILE* fp;
      fp = fopen("c:\\log.txt","rb");

      char locationString[94];
      char cbuf;
      int char_cnt = 0;
      unsigned int bb = 0;

      unsigned char ur, curr, prev = 0;
      int cnt = 0;
      for ( cnt = 0; cnt < 6; cnt++)
          fread(&cbuf, 1, 1, fp);

      while(fread(&cbuf,1,1,fp))
          {
          unsigned char aa = (1<< (7 -bb%7))-1;
          ur = cbuf & aa;
          ur = (ur << (bb)) | prev;
          curr = cbuf &(0xff ^ aa);
          curr = curr >>(7-bb);
          prev= curr;
          if(ur == 0xd)
              {
              break;
              }
            
          locationString[char_cnt] = ur;
          bb = ++bb % 7;
          char_cnt++;
          if ( bb== 0 )
              {
              locationString[char_cnt++] = prev;
              prev =0;
              }
          }

      locationString[char_cnt] = '\0';
      fclose(fp);
      int len = 0;
      while (locationString[len] != NULL )
          len++;

      HBufC* nameHeap = HBufC::NewLC(len);
      TPtr namePtr(nameHeap->Des());
      TBuf<250> messageText;

      for (int i = 0; i < len; i++)
          namePtr.Append((TChar)locationString[i]);

      messageText.Copy(namePtr);

      CAknInformationNote* informationNote = new ( ELeave )
      CAknInformationNote;
      informationNote->ExecuteLD(messageText);

      CleanupStack::PopAndDestroy(nameHeap);
      }
  else
      {
      CAknInformationNote* informationNote = new ( ELeave )
      CAknInformationNote;
      informationNote->ExecuteLD(_L("Error :p"));
      }
  iBroadcastMsg.Close();
  }

void CCBUtil::DoCancel()
  {
  }

Yes, i admit that the above code does not work every time. If you have some fix to above code please send the fix to me at my email id skumar.mobiledev@gmail.com

How to restart device pragmatically

enum TSWStartupReason
 {
 // Normal startup reasons (100..149)

 // Nothing set the (default value).
 ESWNone = 100,

 // Restore Factory Settings (Normal)
 ESWRestoreFactorySet = 101,

 // Language Switched
 ESWLangSwitch = 102,

 // Warranty transfer
 ESWWarrantyTransfer = 103,

 // Possibly needed for handling power off & charger connected use case.
 ESWChargerConnected = 104,

 // Restore Factory Settings (Deep)
 ESWRestoreFactorySetDeep = 105
 };

class SysStartup
 {
 public:
     IMPORT_C static TInt ShutdownAndRestart(const class TUid& aSource, TSWStartupReason aReason);
 };

Implementation

TUid uid = {0x};
SysStartup::ShutdownAndRestart( uid, ESWNone);

Motorola MotoMAGX

Motorola’s MotoMAGX Linux platform is based on three things: an open source Linux operating system, kick ass J2ME support and something they call “WebUI.” [HTTP + CSS + AJAX + WebKit].

Types of Phones

1. Any mobile phone
-Voice calls
-SMSs
-Contacts

2. Feature phone
-Voice calls
-SMSs
-Contacts
-MMSs
-Email
-WAP
-Camera
-Colour Display

3. Smartphone
-Voice calls
-SMSs
-Contacts
-MMSs
-Email
-WAP
-Camera
-Colour Display
-Access to OS
-Application background execution

Compatibility aspects to the S60 platform:

1. Source compatibility: means that the application or a client code can be rebuilt without a need to modify the code.

2. Binary compatibility: means that no rebuild is needed and the application or a client code thus runs on the S60 phone. Potential issues come along when there is a new compiler and tool chain; The S60 3rd Edition introduces new compilation tools (RVCT, GCC EABI), which cause a full binary break.

Symbian Run Modes

Symbian runs in 2 Modes.

1. User mode – kernel services can only be accessed through the EUSER.DLL. The lack of a proper kernel port does not stop the development of user-side components because the platform provides a complete Kernel Port for the PC environment under the Windows Operating System. This is called the emulator.

2 Kernel mode – EUSER.DLL is an interface between common code and hardware-specific code. In the other words, kernel mode means that the software is run on the target hardware.

S60 ecosystem.
1. Licensees.
2. Product Creation Community (PCC)
• Boutiques – experts in designing complete S60 phones and managing entire S60 phone projects
• Competence Centers – top-tier software companies with deep S60 end-to-end understanding and extensive S60 project support
• Wireless Technology Providers – experts on the hardware platforms or hardware components upon which S60 phones are built
• Contractors – skilled software companies offering focused expertise in specific technology areas
3. 3rd party developers.

S60 architecture

S60 architecture consists of ...
1. Cellular modem controlled by modem software.
2. Domestic Operating System (DOS).
3. Application processor engine controlled by Symbian OS.
4. S60 software.

Nokia’s Mobile Software (MSW) is the organization behind the S60 platform.

Coding for Mobile on Mobile

If you are thinking to do this Hmmmm. you need some rest. ;-)
OR
Do what i do use http://www.j2medit.com/

How to use TLex to Parse tokens from String.

  _LIT8(KSomeConstString,"first,second,third,fourth");

TLex8 lex(KSomeConstString);
TChar ch;
TBuf8<50> token;

while((ch = lex.Get()) != 0 )
{
    while ((ch = lex.Peek()) != ',')
        lex.Inc();

    token.Copy(lex.MarkedToken());
    /*
    Now we have the string in token,
    do something..
    */
    lex.Inc();
    lex.Mark();
}

"C++/C Development with Eclipse" Then and Now

In the Past i have tried to use Eclipse for my day to day development, But at that time it too me around 6 hours before i could install all the req. tools and started my developmentBut that is also not a smooth road.

But Now {2 day} i found a good Eclipse CDT bundle for Windows with that i start and running in 30 mins. I suggest you take a look in to it.

http://wascana.sourceforge.net/

LiMo [Linux Mobile] Platform architecture

How to hide Status Pane

CEikonEnv* iEnv = CEikonEnv::Static();
CEikStatusPane* statusPane=Env->AppUiFactory()->StatusPane();
statusPane->MakeVisible(EFalse);

Include files:
#include <eikspane.h>
#include <eikenv.h>

Link against: eikcore.lib

Sending Application in Background using RSS

Add the "Launch" field in application info resource in your Project .RSS file

RESOURCE APP_REGISTRATION_INFO
{
    app_file="projectname";
    localisable_resource_file="\\resource\\apps\\projectname_loc";
    hidden = KAppIsHidden;
    embeddability = KAppNotEmbeddable;
    newfile = KAppDoesNotSupportNewFile;
    // Launches the application in background.
    launch =KAppLaunchInBackground;
 
}

Why we require to launch a application in Background ?
One use case may be the running wallpaper where a server with GUI runs in BackGround.

Java Verified Signing Flow.

How to get the Resource File from Installation

_LIT(KIconFile,"!:\\Data\\MyApp\\MyApp.mbm");
TFileName myCompleteFileName(KIconFile());
CompleteWithAppPath(myCompleteFileName);

Symbian Symbianed Flow For Symbian V9

Capability Mobile Diagarm For Symbian v9
The "capabilities" model was introduced in Symbian OS v9.x (S60 3rd Edition onwards). There are 20 capabilities, which are divided into four groups:

Symbian V9 Security Description.

A capability is an access token that corresponds to an access permission of sensitive system resources.

Basic capabilities

LocalServices
Grants access to "short-link" connections such as Bluetooth and infrared. These connections are not billable transactions. An example of this kind of action is device-to-device file transfer.

Location
Grants access to the location of the device, such as network cell ID.

NetworkServices
Grants access to remote service and might involve cost for the user. Typical use cases are dialing a normal GSM voice call or sending a text message.

ReadUserData
Grants read-only access to confidential user data. Typical use cases are reading contacts, messages, and calendar events.

WriteUserData
Grants write access to user data. Typical use cases are adding or deleting contacts, messages, or calendar events.

UserEnvironment
Grants access to live confidential information about the user and his/her immediate environment. An example of a typical protected resource in a mobile device is a camera.

Extended capabilities

PowerMgmt
Grants access to kill any process running in the system or completely turn off the device.

ProtServ
Grants the right to a server to register with the protected name. Protected names start with a “!”. The kernel will prevent servers without ProtServ capability from using such a name and therefore will prevent protected servers from being impersonated.

ReadDeviceData
Grants read-only access to sensitive system data such as device settings.

WriteDeviceData
Grants write access to sensitive system data such as device lock settings, system time, and time zone.

SurroundingsDD
Grants access to logical device drivers that provide input information about the surroundings of the mobile phone, for example global positioning system (GPS) device drivers.

SwEvent
Grants access to simulate key presses and capture such events from any application. Typical example is a screen-shot application.

TrustedUI
Grants access to create a trusted UI session and display dialogs in a secure UI environment. Typical example is password dialog.

Platform-approved capabilities

AllFiles
Grants read-only access to all data caged directories and write access to /private –directory. NOTE! AllFiles will not be granted for a filemanager type of application.

CommDD
Grants access to communication device drivers such as WiFi, USB, and serial device drivers.

DiskAdmin
Grants access to disk administration functions such as formatting a drive or mounting/unmounting drive partitions.

MultimediaDD
Grants access to critical multimedia device drivers such as camera and sound.

NetworkControl
Grants access to modify or access network protocol controls such as dropping all connections from the mobile phone.

Manufacturer-approved capabilities

DRM (digital rights management)
Grants access to DRM-protected content in plain form.

TCB
Grants write access to /sys and /resource directories in the mobile phone.

Using FlashLite with Symbian C++

Code for S60 V3:

void CSWF2SISAppUi::LaunchSwfL( const TDesC &aFlashAppName )
{
 iHandler = CDocumentHandler::NewL( NULL );
 iHandler->SetExitObserver(this);

 TUid KUidFlash21 = { 0x200077D6 };
 TDataType dtype(KUidFlash21);

 TInt error = iHandler->OpenFileEmbeddedL( aFlashAppName, dtype );
}

void CSWF2SISAppUi::HandleServerAppExit (TInt /* aReason */)
{
 Exit();
}

Code for S60 FP1:

void CSWF2SISAppUi::LaunchSwfL( const TDesC &aFlashAppName )
{
   iHandler = CDocumentHandler::NewL( NULL );
   iHandler->SetExitObserver(this);
  
   TUid KUidFlash21 = { 0x200077D6 };
   TDataType dtype(KUidFlash21);
  
   TInt error = iHandler->OpenFileEmbeddedL( aFlashAppName, dtype );
}

void CSWF2SISAppUi::NotifyExit (TExitMode aMode)
{
   Exit();
}

Get Phone Screen Size

Header:  w32std.h
Library:  ws32.lib

TPixelsAndRotation ScreenSize;
iCoeEnv->ScreenDevice()->GetDefaultScreenSizeAndRotation(ScreenSize);
TInt width = ScreenSize.iPixelSize.iWidth;
TInt height = ScreenSize.iPixelSize.iHeight;

iLogger.WriteFormat(_L("Width : %d, Heigth : %d"), width, height);

Find out all the Message server entries.

CMsvEntry *inbox=iSession->GetEntryL(KMsvGlobalInBoxIndexEntryId);
CMsvEntrySelection *children=inbox->ChildrenWithMtmL(KUidMsgTypeSMS); // KUidMsgTypeMultimedia
for(TInt i=0;i<children->Count();i++)
    {
    CMsvEntry *child=inbox->ChildEntryL((*children)[i]);
    const TMsvEntry &entry=child->Entry();
    ...
    }

A color picker in Symbian S60 v3

TBool noneExist = EFalse;
TBool noneChosen = EFalse;
TRgb colour = KRgbDarkGray;

CArrayFixFlat<TRgb>* colours = new(ELeave) CArrayFixFlat<TRgb>(6);
colours->AppendL(KRgbBlack);
colours->AppendL(KRgbDarkGray);
colours->AppendL(KRgbRed);
colours->AppendL(KRgbSymbianOrange);
colours->AppendL(KRgbBlue);
colours->AppendL(KRgbWhite);
colours->AppendL(KRgbCyan);
colours->AppendL(KRgbYellow);
colours->AppendL(KRgbGreen);

CAknColourSelectionGrid *d = CAknColourSelectionGrid::NewL( colours, noneExist, noneChosen, colour);
if(d->ExecuteLD())
{
  ///Here you get the selected color..this you can use in your draw method.
  //selectedColor = colour;
  
  DrawNow();
}

How to Hide Application from User Menu
In your ApplicationName_reg.rss file you will find a structure RESOURCE APP_REGISTRATION_INFO, you need to add the following line, to the resource.

BYTE hidden = KAppIsHidden;

This application will be a hidden application, and it will not be shown in Applications list.

Mobile DRM

Several articles I read recently on Mobile DRM:

Roberto Nunes’s Forum Nokia Blog:
DRM and some more TLA (tree letters abbreviations)
DRMs - Part 2
DRMs - Part 3 OMA DRM
DRMs - Part 4 - Conclusions

medialoper.com:
Microsoft Zune’s Big Innovation: Viral DRM
ipodnn.com:
MS defends Zune temporary DRM

How to detect if an application is launched by user or the startup list

It is sometimes useful to be able to detect whether an application is started at boot time by the Startup List API (present only in S60 3rd Edition) or by the user, and passing Symbian Signed - which is generally required to have an application which requires auto boot feature - makes this almost mandatory. So How we can archive it let us try

First, we will modify the application registration file and add some opaque_data field in the APP_REGISTRATION_INFO resource. The content and value of these data does not really matter, you just need to specify something: :

#include <appinfo.rh>
#include <uikon.rh>

RESOURCE APP_REGISTRATION_INFO
{
...
opaque_data = r_startup_detect;
}  


RESOURCE NUMBER_INT8 r_startup_detect
{
value = 1;
}

The opaque_data and other launch parameters will be ignored by the startup list when launching the application. Thus, detecting whether they are present or not allows to differentiate whether the application has been launched at boot time or by the user.

To do this, we will override the ProcessCommandParametersL() function in your AppUI:

TBool CMyAppUi::ProcessCommandParametersL( CApaCommandLine &aCommandLine )
{
if(aCommandLine.OpaqueData().Length() > 0)
{
   // Opaque data exists,
   // app. has been manually started from the menu
}
else
{
   // Opaque data not present,
   // App. has been auto-started from start up
   // or after Installation !!!
}
return CEikAppUi::ProcessCommandParametersL( aCommandLine );
}

How to launch an application with its UID

LaunchAppWithUIDL(const TUid aAppUid)
{
  RApaLsSession apaLsSession;
  User::LeaveIfError(apaLsSession.Connect());
  CleanupClosePushL(apaLsSession);

  TApaAppInfo appInfo;
  TInt retVal = apaLsSession.GetAppInfo(appInfo, aAppUid);

  if(retVal == KErrNone)
      {
      CApaCommandLine* cmdLine = CApaCommandLine::NewLC();
      //cmdLine->SetLibraryNameL(appInfo.iFullName); // Pre Symbian V9
      cmdLine->SetExecutableNameL(appInfo.iFullName);
      cmdLine->SetCommandL(EApaCommandRun);
      User::LeaveIfError( apaLsSession.StartApp(*cmdLine) );

      CleanupStack::PopAndDestroy(cmdLine);
      }
  else
      {
      // Application with UID can't be found!
      }

  CleanupStack::PopAndDestroy(&apaLsSession);
}

How to Install an empty file or directory (which is not included in the SIS file).

Pre-Symbian OS v9.0:

""-"C:\Documents\deleteme", FN
""-"C:\Documents\deleteme1\", FN
""-"C:\Documents\deleteme2\*.*", FN
""-"C:\Documents\created.txt", FN

Symbian OS v9.0 and beyond:

""-"C:\private\<process SID>\deleteme", FN
""-"C:\private\<process SID>\deleteme1\", FN
""-"C:\private\<process SID>\deleteme2\*.*", FN
""-"C:\private\<process SID>\created.txt", FN

How to Sending SMS in Symbian 9

User::LeaveIfError(sendAs.Connect());
CleanupClosePushL(sendAs);

RSendAsMessage sendAsMessage;
sendAsMessage.CreateL(sendAs, KUidMsgTypeSMS);
CleanupClosePushL(sendAsMessage);

// prepare the message
sendAsMessage.AddRecipientL(aRecipient, RSendAsMessage::ESendAsRecipientTo);
sendAsMessage.SetBodyTextL(aMessageBody);

// send the message
sendAsMessage.SendMessageAndCloseL();

// sendAsMessage (already closed)
CleanupStack::Pop();

// sendAs
CleanupStack::PopAndDestroy();

How to get the free space of every drive

Following Code can get you the free space in a drive.

RFs iFs;
iFs.Connect();
TInt err = iFs.Volume( volinfo, EDriveC );
TInt64 space = volinfo.iFree;
iFs.Close();

"iFree" is the amount of free space on the disk in bytes.

Note: Volume() will return KErrNotReady if the drive contains no media.

Increase the heap size of an application

The default heap size of an application is 1MB, that means on target if you application tried to allocate more than 1MB memory, the allocation will fail. Probably new (ELeave) will leave.

What if you really want your application to allcoate more than 1MB memory? For example, you are developing an image processing application which needs to load big pictures.

There's a way to use a user define heap instead of the default heap, you can do this like:

GLDEF_C TInt E32Main()
{
  RHeap *heap = UserHeap::ChunkHeap( NULL, 1024 * 4, 1024 * 1024 * 2 );    // 2MB
  if( heap )
  {
      User::SwitchHeap( heap );
  }
  TInt ret  =  EikStart::RunApplication( NewApplication );
  if ( heap )
  {
   heap->Close();
  }
  return ret;
}

You switch the heap to your own one, which allow you to allocate 2MB in this case

Prevent object being created on stack

In Symbian, sometimes we don't want the calling function to create a object of your class on stack, because the stack resource is rare. Is there any way we can restrict do this?

Answer is Yes.

We should make class destructor private, rather than public or protected.

Example

class CTest : public CBase
{
private:
~CTest ();
}

When to use () and [] in PKG files?

The () are used for software dependencies, while [] are used for product dependencies. () will work in most cases, but it will throw an error if you state your file supports both UIQ 3 and S60 (which is valid for shared DLLs).

Note that, as the time of this writing, some of the documentation uses
(0x101F6300), 3, 0, 0, {"UIQ30ProductID"}
(0x101F6300), 3, 0, 0, {"Series60ProductID"}
when it should have instead
[0x101F6300], 3, 0, 0, {"UIQ30ProductID"}
[0x101F6300], 3, 0, 0, {"Series60ProductID"}

[Revisiting] Bluetooth Power Status Check
In my last post i showed how to detect that Blue tooth is ON / OFF in S60 v3 but in Pre-S60v3 SDKs it is bit tricky. Here is one way of achiving same thing using libs from OLD S60 v1.2 SDK. [I found this method in Forum Nokia Posted by a respected member.]
Note : Use it on your Own Rsk.

#ifndef BT_ENG_HACK_H
#define BT_ENG_HACK_H
// link against BTENG.LIB copied from SDK 1.2

// these are headers that are just not included
// in the SDK, so I had to reverse engineer them
//C:\Symbian\tilion\group>"c:\Program Files\Borland\CBuilder6\Bin\expdump.exe"
// C:\Symbian\Series60_1_2_B\epoc32\release\winsb\udeb\BTENG.LIB
class MBTMCMSettingsCB
{
};
class CBTMCMSettings;
class CBTMCMSettings
{
public:

static CBTMCMSettings* NewLC(MBTMCMSettingsCB *x);
static CBTMCMSettings* NewL(MBTMCMSettingsCB *x);

void SetPowerStateL(TBool a, TBool b);
void GetPowerStateL(TBool &a);
TInt GetConnectionStatus(int &a);
};
#endif

Powered by Qumana

New Blogging Tool [Qumma]

Hello Guys i got a new Tool to Blog. It is Qumana. Looks good till now let me see if it can meet my requiments.

Powered by Qumana

Bluetooth Power Status Check

Here is the Code that shows How to check that BlueTooth is ON or OFF in Symbian V9

CRepository *cRepository = CRepository::NewL(KCRUidBluetoothPowerState);
TInt bluetoothStatus=0;
User::LeaveIfError( cRepository ->Get(KBTPowerState, bluetoothStatus) );

How to Launch the browser in an embedded mode.

LaunchBrowserEmbedded()
 {
 CApaProcess *pApaProcess = Document()->Process();

 TUid id;
 id.iUid = 0x10008d39;
 iDoc = pApaProcess->AddNewDocumentL(KNullDesC , id);

 iDoc->EditL(this, ETrue);

 TApaTaskList taskList( iEikonEnv->WsSession() );
 id.iUid = 0x10208b93;//this
 TApaTask task = taskList.FindApp( id );
 if ( task.Exists() )
   {
   task.SendMessage(TUid::Uid(0), _L8("4 http://news.google.com/xhtml"));
   }
 }

Note:
you have to provide NotifyExit() in your AppUi to delete iDoc.

Compress / Decompress A File with less memory usage.

void CompressAFile(TDesC& aSrcName, TDesC& aDstName)
{
RFs fs;
User::LeaveIfError(fs.Connect());
fs.SetSessionPath(_L("C:\\")); // change to your req. Path

RFile file;
TInt err = file.Open(fs,aDstName,EFileRead);

CEZFileToGZip* zip = CEZFileToGZip::NewLC(fs, aSrcName, file);
TInt tempi = 0;
while(zip->DeflateL()) // while loop req. donot remove
 {
 tempi++;
 }
CleanupStack::PopAndDestroy(); // zip

file.Close();
fs.Close();
}

void DeCompressAFile(TDesC& aSrcName, TDesC& aDstName)
{
RFs fs;
User::LeaveIfError(fs.Connect());
fs.SetSessionPath(_L("C:\\")); // change to your req. Path

RFile file;
TInt err = file.Open(fs,aDstName,EFileRead);

CEZGZipToFile *zip = CEZGZipToFile::NewLC(fs, aSrcName, file);
TInt tempi = 0;
while(zip->InflateL()) // while loop req. donot remove
  {
  tempi++;
  }
CleanupStack::PopAndDestroy(); // zip

file.Close();
fs.Close();
}

Retrieving Phone's Manufacturer ,Model & IMEI number Using CTelephony

---- Header --------
CTelephony* iTel;
CTelephony:: TPhoneIdV1Pckg iInfoPkg;
CTelephony:: TPhoneIdV1 iInfo;


---- CPP File ------

void Request()
{
iTel=CTelephony::NewL();
iTel->GetPhoneId(iStatus,iInfoPkg);
SetActive();
}

void RunL()
{
switch(iStatus.Int())
{
case KErrNone:
{
TBuf
CTelephony::KPhoneModelIdSize + CTelephony::KPhoneSerialNumberSize> phoneInfo;
phoneInfo.Copy(iInfo.iManufacturer);
phoneInfo.Append(iInfo.iModel);
phoneInfo.Append(iInfo..iSerialNumber);
}
break;
default:
{
//Return error
}
break;
}
}

How to get Names of all installed applications

The following code sample shows how to get an array containing names of the installed applications.

CDesCArray* GetInstallAppListL(void)
{
CDesCArrayFlat* appArray = new(ELeave)CDesCArrayFlat(10);
CleanupStack::PushL(appArray);

RApaLsSession apaSession;
TRAPD(err, apaSession.Connect());

if(err != KErrNone)
{
CleanupStack::Pop(appArray);
return NULL;
}

CleanupClosePushL(apaSession);

TRAPD(errn, apaSession.GetAllApps());

if(err != KErrNone)
{
CleanupStack::Pop(appArray);
CleanupStack::PopAndDestroy(apaSession);
return NULL;
}

TInt errno(KErrNone);
TApaAppInfo appInfo;

do
{
errno = apaSession.GetNextApp(appInfo);
if(KErrNone == errno && appInfo.iCaption.Length())
{
appArray->AppendL(appInfo.iCaption);
}

}while(KErrNone == errno);

CleanupStack::PopAndDestroy(apaSession);

CleanupStack::Pop(appArray);
return appArray;
}

How to check what serial ports are available in WM5/6?

I use the following code to check for available ports in Windows Mobile 5 and 6

[CODE]
private string[] GetAvailableCommPorts()
{
ArrayList commPorts = new ArrayList();
string port = "COM";
for (int i=1;i<=99;i++) { try { string portName = port+i.ToString()+":"; new OpenNETCF.IO.Serial.Port(portName).Query(); commPorts.Add(port+i.ToString()); } catch { } } return (string[]) commPorts.ToArray(typeof(string)); }
[/CODE]

Get Caller Number

Below is the code illustarating how to get the remote party's telephone number. It is different for S60 3rd Edition and previous versions.

In V8 and Below
#include

void GetRemotePartyPhoneNumberL(TDes& aPhoneNumber)
{
RTelServer etel;

// Connect to ETel server
User::LeaveIfError(etel.Connect());
CleanupClosePushL(etel);

// Load phone module. This is just to be on the safe side
// because it should have been loaded already
_LIT(KTsyName, "phonetsy.tsy");
User::LeaveIfError(etel.LoadPhoneModule(KTsyName));

RTelServer::TPhoneInfo phoneInfo;

// Get phone info. We need phone's name to open a phone
const TInt KPhoneIndex = 0;
User::LeaveIfError(etel.GetPhoneInfo(KPhoneIndex, phoneInfo));

RPhone phone;

// Open the phone
User::LeaveIfError(phone.Open(etel, phoneInfo.iName));
CleanupClosePushL(phone);

RPhone::TLineInfo lineInfo;

// Get line info. We need line's name to open it
const TInt KLineIndex = 0;
User::LeaveIfError(phone.GetLineInfo(KLineIndex, lineInfo));

RLine line;

// Open the line
User::LeaveIfError(line.Open(phone, lineInfo.iName));
CleanupClosePushL(line);

RLine::TCallInfo callInfo;

// Get call info. We need call's name to open it and get the info we need
const TInt KCallIndex = 0;
User::LeaveIfError(line.GetCallInfo(KCallIndex, callInfo));

RMobileCall call;

// Open the call
User::LeaveIfError(call.OpenExistingCall(line, callInfo.iCallName));
CleanupClosePushL(call);

RMobileCall::TMobileCallInfoV1 mobCallInfo;
RMobileCall::TMobileCallInfoV1Pckg mobCallInfoPckg(mobCallInfo);

// Get the call's info
User::LeaveIfError(call.GetMobileCallInfo(mobCallInfoPckg));

// We successfully got the call's info.
// Now copy the remote party's phone number to the target descriptor
aPhoneNumber.Copy(mobCallInfoPckg().iRemoteParty.iRemoteNumber.iTelNumber);

// Close all handles
CleanupStack::PopAndDestroy(4); // call, line, phone, etel
}

In V9 and above
void GetRemotePartyPhoneNumberL(TDes& aPhoneNumber)
{
// Create a CTelephony object
CTelephony* telephony = CTelephony::NewLC();

CTelephony::TCallInfoV1 callInfoV1;
CTelephony::TCallInfoV1Pckg callInfoV1Pckg(callInfoV1);

CTelephony::TCallSelectionV1 callSelectionV1;
CTelephony::TCallSelectionV1Pckg callSelectionV1Pckg(callSelectionV1);

CTelephony::TRemotePartyInfoV1 remotePartyInfoV1;
CTelephony::TRemotePartyInfoV1Pckg remotePartyInfoV1Pckg(remotePartyInfoV1);

callSelectionV1.iLine = CTelephony::EVoiceLine;
callSelectionV1.iSelect = CTelephony::EInProgressCall;

// Get the call info
User::LeaveIfError(telephony->GetCallInfo(callSelectionV1Pckg,
callInfoV1Pckg, remotePartyInfoV1Pckg));
// Copy the remote party's phone number to the target descriptor
aPhoneNumber.Copy(remotePartyInfoV1Pckg().iRemoteNumber.iTelNumber);

CleanupStack::PopAndDestroy(); // telephony
}

How to guide for pre-installed applications

Introduction
---------------
In preinstalled applications, application files such as binaries are already in place in their target folders on a memory card. When a memory card with preinstalled applications is inserted into a device, the preinstalled applications are automatically installed so that the user can use them without having to install them manually.


In addition to the application files, a .sis file created with a PA type must also exist in the \private\10202dce folder on the memory card. This .sis file is also known as a "stub" .sis file since it contains sis controller data but no files.

How to create PA package
-----------------------------

Creating PA sis package
---------------------------

* Make sure that the package type is PA in the .pkg file.
* In the .pkg file, change the target drive for each file to the MMC drive.
* Make sure that correct product dependency is specified in the package file.
* Get certification for the final .sis file, ie. submit the application to Symbian Signed. When submitting, include the PA type sis, .pkg file and corresponding binaries to a .zip file. Arrange the binaries in the .zip file according to the correct structure so that binaries are located in the correct directories under
o private
o resource
o sys

You need to be aware of the folowing for PA packages:
* Do not use FR (FILERUN) options since they are not invoked in PA packages.
* The FN option can be used if the stub file is not read-only.

Do not use the FT (FILETEXT) option. It is skipped/ignored for PA packages.
* The PA .sis file cannot have embedded .sis file(s).
Sample .pkg file content for PA application:
[CODE]
;Languages
&EN

;Header
#{"Test Application"},(0x11223344),1,0,0, TYPE=PA

;Localized Vendor name
%{"Test"}

;Unique Vendor name
:"Test"

;Dependency for S60 3rd Edition
[0x101F7961], 0, 0, 0, {"Series60ProductID"}

;Preinstalled files
"MyTestApp.exe" - "e:\sys\bin\MyTestApp.exe"
"MyTestApp_reg.rsc" - "e:\private\10003a3f\import\apps\MyTestApp_reg.rsc"
"input.dat" - "e:\private\11223344\input.dat"
[/CODE]

In the development phase, you can use developer certificate to sign the PA type sis. Create the .sis file and sign it with a trusted certificate and key:

makesis.exe mytestpa.pkg mytestpa.sis

signsis.exe mytestpa.sis mytestpa_signed.sis

Publishing files to target locations on memory card

Make sure that files referred in PA package exist on memory card.

Publish PA sis file to the \private\10202dce\ folder on the memory card. Publish package files to their location as specified in .pkg file.


IMPORTANT: You need to make sure that the .pkg file used to create the PA .sis file doesn’t list files that are updated/modified during run time. These files still need to be on the memory card but they will no longer be protected against tampering. If any of the installed files (e.g., the configuration file) is updated/modified, propagation won't work when the memory card is inserted to another device or when the C drive is formatted. One possible solution to this problem is that if a file (e.g., a configuration file) is updated, application(s) will not touch the original file (only reading). Instead they will make a copy of this file and update the copy.

Upgrading pre-installed applications
-----------------------------------------
Preinstalled applications can be upgraded by overwriting the PA files with an SA package. When an SA package is installed to a memory card, it is propagated. This means that it will behave like a PA package when the memory card is inserted into another device.

Preinstalled applications cannot be upgraded by using Partial Upgrade (PU) packages. SIS Patch (SP) packages can be used to upgrade preinstalled applications but the upgrade is not propagated to the memory card. Thus, it will not be in place when the memory card is inserted into another device.

Moving an application to foreground / to background

1. Being notified of the focus change
Override HandleForegroundEventL() function In AppUi Class Like

void CMyAppUi::HandleForegroundEventL(TBool aForeground)
{
// Call Base class method
CAknAppUi::HandleForegroundEventL(aForeground);

if(aForeground)
{
// We have gained the focus
...
}
else
{
// We have lost the focus
...
}
}

2. Bring Application To ForeGround

void CMyAppUi::BringToForeground()
{
// Construct en empty TApaTask object
// giving it a reference to the Window Server session
TApaTask task(iEikonEnv->WsSession( ));

// Initialise the object with the window group id of
// our application (so that it represent our app)
task.SetWgId(CEikonEnv::Static()->RootWin().Identifier());

// Request window server to bring our application
// to foreground
task.BringToForeground();
}

3. Send Application To BackGround
void CMyAppUi::BringToForeground()
{
// Construct en empty TApaTask object
// giving it a reference to the Window Server session
TApaTask task(iEikonEnv->WsSession( ));

// Initialise the object with the window group id of
// our application (so that it represent our app)
task.SetWgId(CEikonEnv::Static()->RootWin().Identifier());

// Request window server to Snedour application
// to BackGround
task.SendToBackground();
}

Other Method If you want to Send or Bring Focus to Other Application

TApaTaskList tasklist(iCoeEnv->WsSession());
TApaTask task(tasklist.FindApp(_L("TestApp")));
task.SendToBackground(); // or BringToForeground()


Library: apgrfx.lib

How to lock your phone from Code.

RAknKeyLock keyLock; // first step

User::LeaveIfError(keyLock.Connect()); // second step
CleanupClosePushL(keyLock);

keyLock.EnableKeyLock(); // third step

keyLock.Close(); // fourth step
CleanupStack::PopAndDestroy(); // keyLock

Creating Self-signed Symbian OS Certificates

Introduction

This short note describes the steps required to create a self-signed certificate for signing Symbian OS packages.

Shortly, the steps are the following:

1. Creating the certificate
2. Converting the certificate
3. Installing the certificate
4. Signing the installation package

The rest of this note describes each of the steps in more detail. The discussion assumes that the 9210 SDK has been installed, and paths set up properly.
Creating the Certificate

The certificate and its corresponding private key can be created with the following command:

makekeys -cert -dname "CN=Your Name EM=email@address CO=XX" filename.key filename.cer

The items with emphasis should be replaced with your own values. The dname (distinguished name) parameter string can also contain other values, see the makekeys help for more information. makekeys will prompt you to enter a passphrase for the key, using one is highly recommended.

Important note: QuickEdit mode must be disabled from the shell window, otherwise random data gathering won't work.
Converting the Certificate

For some reason, makekeys creates certificate files that the 9210 certificate manager software cannot read. To work around this, the certificate must be converted to a suitable file format. This is possible using the built-in certificate management tools in Windows 2000 or XP. The following steps are needed:

1. Open the newly generated certificate file by double-clicking it in Explorer
2. Click "Install Certificate" and follow the instructions, using default settings
3. Open "Internet Options" from Control Panel, select the "Content" tab, and click on "Certificates...".
4. Locate the new certificate in the "Trusted Root Certification Authorities" tab. If you used non-default options when installing the certificate, it may be visible in one of the other tabs.
5. Select the new certificate and click "Export...". Follow the Certificate Export Wizard's instructions, and select "DER encoded binary X.509 (CER)" as the export format. Enter a new file name.

The resulting certificate from these steps can be installed on a 9210 communicator. Note that you should retain the original file too, since it can be useful with other SDK tools.
Installing the Certificate

Because the certificate is self-signed, the device will not trust it by default. To install the certificate on the device and set it trusted for software installation, follow these steps:

1. Transfer the file to the device normally, and save it to a known location.
2. Open the Certificate manager from the communicator's Control panel.
3. Select "Add" and choose the file. This installs the certificate.
4. Select the newly installed certificate from the list, select "View details", select "Trust settings" and enable "Software installation".

After this process the Communicator will accept installation packages signed using the new certificate.
Signing the Installation Packages

Finally, to make use of the new certificate, installation packages must be signed using the corresponding private key. This process is documented in the SDK, but, briefly, the steps are the following:

1. Copy the original key and certificate files created by makekeys to a known location. In this example, the files are assumed to be at c:\home\user\keys\filename.key and c:\home\user\keys\filename.cer.
2. Add the following line to the installation package file (project.pkg):

*"c:\home\user\keys\filename.key","c:\home\user\keys\filename.cer"

3. Create the installation package normally. If you set a passphrase for the key, makesis will prompt you for it.

DLL capability model in a Secure Platform.

With platform security, every DLL must have at least the same set of capabilities as the loading process, or otherwise the process is not allowed to load the DLL. For this reason most general-purpose DLLs would need (or close to) ALL -TCB as they cannot know in beforehand all the processes that can/will load them at some point in the future. Even if your DLL is set to have ALL -TCB capabilities, it does not mean that it is using all of them. A DLL (that has a higher capability set than the loading process) cannot leak capabilities to the process.

A DLL capability does not grant the DLL access to any capability-restricted resources (not even if the DLL has ALL -TCB). For that access you will need a process with ALL -TCB capablities. DLL capabilities only reflect a level of trust, so that the loading process can be sure that the DLL it is capable of loading has been tested to be trusted with the set of capabilities that the process has.

To get your DLL signed with these heavy capabilities:

For example, all MTM, FEP, and browser plug-ins require ALL -TCB. If you are developing such a component and require ALL -TCB capabilities, you need to fill in the Capability request form on the Symbian Signed Web site https://www.symbiansigned.com/app/page/requirements and send the form to nokia.testing@nokia.com.
In the form you have to explain why each capability is requested and also give some company background information, for example, if you already have some co-operation with Nokia. This should be done before requesting the developer certificate.
When Nokia gets the capability request form, the case is evaluated with S60 platform. Manufacturer-approved capabilities are granted so that those DLLs that require sensitive capabilities are packaged to an embedded SIS file which is certified first, and the developer should use it in the delivery.

For more information about the process, see the "Testing and Signing with Symbian Platform Security" document at www.forum.nokia.com/testing.

RSend Method to send SMS.
Include:
#include "rsendas.h"
#include "rsendasmessage.h"
Library:
LIBRARY sendas2.lib

Pros: No need to get Much more capability.
Cons: You can't manipulate msg entry in sms Msging entry. Only possible in MTM method.

void CSmsSendHandler::SendSmsInThirdEditionL(const TDesC& aAddr, const TDesC& aMsg)
{

RSendAs sendAs;
User::LeaveIfError(sendAs.Connect());
CleanupClosePushL(sendAs);

RSendAsMessage sendAsMessage;
sendAsMessage.CreateL(sendAs, KUidMsgTypeSMS);
CleanupClosePushL(sendAsMessage);

// prepare the message
sendAsMessage.AddRecipientL(aAddr, RSendAsMessage::ESendAsRecipientTo);
sendAsMessage.SetBodyTextL(aMsg);

// send the message
sendAsMessage.SendMessageAndCloseL();

// sendAsMessage (already closed)
CleanupStack::Pop();

// sendAs
CleanupStack::PopAndDestroy();

}

RSendAs : Send a file bluetooth

A number of people seem to have a problem using RSendAs to send a file via Bluetooth but its more or less the same as sending any other message.

To start, you need to get hold of the bluetooth MTM UID, its in "SendUiConsts.h"

Then its simply a case of:

1. Opening the SendAs session
2. Creating a message using the session
3. Adding the file as an attachment
4. Sending the message

void SendFileL(const TDesC& aFilename)
{
// 1. Open session
RSendAs session;
User::LeaveIfError(session.Connect());
CleanupClosePushL(session);

// 2. Create message
RSendAsMessage message;
message.CreateL(session, KSenduiMtmBtUid);
CleanupClosePushL(message);

// 3. Add attachment
TRequestStatus status;
message.AddAttachment(aFilename.FullName(), status);
User::WaitForRequest(status);

// 4. Send message
if (status.Int() == KErrNone)
{
CleanupStack::Pop(&message);
message.LaunchEditorAndCloseL();
}
else
CleanupStack::PopAndDestroy(&message);

CleanupStack::PopAndDestroy(&session);
}

Some Known Symbian Target Types.

The following target types are supported: [That are more or less know Known to me]

ani
A window server animation DLL.

app
A GUI application. This is deprecated at v9.0. Applications must be converted to EXEs.

ctl
A system control. This is deprecated at v9.0. They must be converted to applications.

dll
A DLL: either a shared library, or a polymorphic interface.

ecomiic
An ECOM implementation collection. This is deprecated at v9.0. The plugin target type should be used instead.

epocexe
An Symbian OS executable that can be launched from the shell. This is an executable program which exports no functions undera multi-process platform and a DLL which is linked with the TIntWinsMain() function exported as ordinal 1 under a single-process platform.

exe
An executable program.

exedll
An executable program for a multi-process platform, a DLL for a single-process platform.

exexp
An executable program with exports.

fsy
A plug-in file system.

implib
Results solely in the generation of a .lib file. It is an error for a component of the IMPLIB type to contain SOURCE statements and the build tools enforce this.

kdll
[If you know any thing about this target please let me know]

kext
[If you know any thing about this target please let me know]

klib
[If you know any thing about this target please let me know]

ldd
A logical device driver.

lib
A static library.

mda
A media-server plug-in DLL (deprecated).

mdl
A MIME recognizer. This is deprecated at v9.0, and should be converted to PLUGIN (ECOM).

notifier
An extended notifier DLL. This is deprecated at v9.0, and should be converted to PLUGIN (ECOM).

opx
An OPL extension.

pdd
A physical device driver.

pdl
A printer driver.

rdl
A recognizer. This is deprecated at v9.0, and should be converted to PLUGIN (ECOM).


[If you know any other target please let me know on my mail]

Thank you

Retrieving battery strength on S60 2nd Edition

below is the code to Get the battery info on Device.

/*

Location: saclient.h
Link against: sysagt.lib

const TInt KUidBatteryBarsValue = 0x100052D3;
const TUid KUidBatteryBars ={KUidBatteryBarsValue};

enum TSABatteryBars
{
ESABBars_0,
ESABBars_1,
ESABBars_2,
ESABBars_3,
ESABBars_4,
ESABBars_5,
ESABBars_6,
ESABBars_7
};
*/

RSystemAgent systemAgent;
User::LeaveIfError(systemAgent.Connect());
TInt strength = systemAgent.GetState(KUidBatteryBarsValue);

// strength will be of type TSABatteryBars;

Profile data on 3rd edition

On 1st edition and early 2nd edition FPs, there was no officially sanctioned way to get profile data, although CProfileAPI was easy enough to generate from the LIB files. Later we got CSettingInfo. In 3rd edition profile data is kept in the central repository, and you can access some of it with the keys in profileenginesdkcrkeys.h.

But the documented keys only provide access to a subset of the profile data, for example not to vibrating alert status or the ringing tone. And it’s read-only.

Luckily, CRepository allows you to enumerate keys. You just open the repository with the CRepository::NewL(KCRUidProfileEngine), and enumerate them with:

CRepository* iRep;
iRep=CRepository::NewL(KCRUidProfileEngine);
RArray found;
iRep->FindL(0, 0, found);
for (int i=0; i   key=found[i];
   /* do something with the key*/

Read full Post here 
}

The “tuxphone” - a DYI Open Source GSM phone

“TuxPhone is a project to develop open source (hardware and software) GSM/GPRS cellphone. Our objective is to create an open (in every sense of the word) cellphone platform that is convenient for creating novel applications. For instance, someone could take this reference design and integrate it with a small RFID reader to create a RFID enabled cellphone. Or, for that matter someone come up with a software that finds the cheapest way to make a phone call based on the available connectivity - VOIP or GSM.”

If you’re up to the challenge, I think there is enough information available now to create your very own tuxphone. You’re definately not going to save any cash, and the design is likely to look, well, a bit unpolished … but the idea of an open phone platform is an interesting one for the hobbyist, or those looking to experiment with new ideas for mobile.

Interested? Some links to check out:

opencellphone.org

dseetharam-etel-2006.ppt

silicon-valley-homebrew-mobile-phone-club

tuxphone sourceforge.net

FAQ

Installing MIDlets on Series 40 and S60

The MIDP specification allows quite a lot of variance in the installation procedure of MIDlets. The spec basically only states what the AMS (Application Management System) needs to take care of but not how it should be taken care of. So it is no wonder that installing MIDlets on Series 40 is different from installation on S60 phones.

First of all, when you transfer MIDlets to Series 40 phones, they will get installed "on the background". The user does not need to start the installation procedure and walk through the installation - after the user navigates to the Application menu, the MIDlets is already there. On S60 phones the user has click through an installation before the MIDlet is installed on the phone. If the MIDlet was downloaded using the browser that process starts automatically. In other cases the user has to go to inbox and start the installation by clicking the JAR or JAD file. On Series 60 phones the destination of the MIDlet varies across the board. On some devices the MIDlets are installed in "My Own" folder, or in "Installations", or...

On Series 40 phones the destination of the MIDlets has changed a little through the different models, but mainly the MIDlets can be found in the "Games" subfolder.

One might ask how Series 40 phone user knows which of his/her MIDlets are untrusted and which are signed as no installation notifications are displayed to the user. The answer is that the user has to select the MIDlet in question and check the MIDlet settings using the Options menu.

One thing to remember on Series 40 phones is that when upgrading a MIDlet, JAD files need to be used. If one intends to upgrade an existing MIDlet using JAR file only, the MIDlet does not get replaced but the new MIDlet gets installed next to he old existing version.

more information read this

BREW: How to use callbacks while working with BREW in C++

Simplest Way:
Make the callback Function member as static then this function will be treated as Global function.
But you have to pass the this pointer to access class members. So not so good.

Best way:
The Below Example will explain the procedure.
class CTimer
{
void startTimer();
void doTimer();
};

int (* PFNCALLBACK)(void *);
int(CTimer::*PFNMEMBERCALLBACK)();

PFNCALLBACK functionCast( PFNMEMBERCALLBACK pMemberCallback)
{
union
{
PFNCALLBACK m_callback;
PFNMEMBERCALLBACK m_member;
} a;

a.m_member = pMemberCallback;
return a.m_callback;
}

void CTimer::startTimer()
{
ISHELL_SetTimer( pIShell, timeInterval, functionCast(&CTimer::doTImer), NULL);
}
So what you say.

Battle Of Mobile OS
Symbian is a very good OS and has a strong growing market sponsored by many device makers, but Windows Mobile is also a very good platform. Since mobile devices hardware has evolved a lot in the last years, chances are a new OS battle will happen soon.

You can read an in-depth article regarding this issue here: http://mobileopportunity.blogspot.com/2006/11/symbian-unloads-uiq-and-mobile-apps_09.html. And don't stop at the end of the article, but go on for the comments, too. It's definitely worth it.

Symbian Security Video Podcast Available

There's a new video podcast available discussing Symbian platform security and the actions needed to get an application to market. It's presented by Risto Helin, Manager of Application Testing for Forum Nokia. The webinar covers different capability needs and Symbian Signed process, and presents for technical audience the platform security and its impact on application development.

Sun Open Sources Java ME under GPL

Sun Microsystems, Inc, the creator of Java technology today (Nov, 13) announced it is releasing its implementations of Java technology as free software under the GNU General Public License version two (GPLv2). Available today are a buildable implementation of Java ME (formerly J2ME) and the first pieces of source code for Java SE.

Available in the Java.net community is the source code for Sun's feature phone Java ME implementation with the Java ME testing and compatibility kit framework. Before the end of the year, Sun will release additional source code including its advanced operation system phone implementation and the framework for the Java Device Test Suite. Sun is also releasing as free software the javac compiler, JavaHelp and Java HotSpot technology, the heart of JVM and JRE for desktops.

In addition, an application developer project is available as part of the Mobile & Embedded community, with links to resources such as the NetBeans Mobility Pack.

Rich Green, execute vice president of Software at Sun said "By open sourcing Sun's implementation of Java technology, we will inspire a new phase of developer collaboration and innovation using the NetBeans IDE and expect the Java platform to be the foundation infrastructure for next generation Internet, desktop, mobile and enterprise applications".

Common Types of Flash Lite Applications.

1- Browser: This is the flash plug in for general websites.
2- Wallpaper: No description needed.
3- Screen saver: No description needed.
4- Standby: Same as Wallpaper and Screen saver.
5- UI: User Interface. To Other Non Flash Lite Applications.
6- MMS: MMS Sending Application.
7- Stand-alone application: Stand alone softwares and games.

Crash Course on "ARM and Thumb"

You might want to get a few books, these three are very, very, very good: http://www.keil.com/books/armbooks.asp and read for some time, but meantime here is a crash course:

There are two (2) states of ARM processors: ARM and Thumb.
There are seven (7) modes: usr, sys, svc, abt, fiq, irq and und.
The modes can be privileged and non-privileged (usr).
Privileged modes can modify CPSR_c (least sig. byte) of CPSR, usr mode cannot do that.
Why? Safety/security reasons. The bits in CPS_c control the interrupts and mode/state switching.

Most (or some) people get sloppy with saying modes and meaning states
and vice versa. But as Alice in Wonderland was instructed by March Hare and Hatter:
"...at least I mean what I say - that's the same thing, you know." "Not the same thing a bit!" said the Hatter. "Why, you might just as well say that 'I see what I eat' is the same thing as 'I eat what I see'!"

I hope this helps you to see my point, it is not for the sake of appearing pedantic.

* __arm or__thumb does not metter to compiler.
That is because IAR had made it [more] transparent to programmer to compile for either ISA (Instruction Set Architecture).

Thumb gives less code then ARM.BINGO!
That is the whole idea behind Thumb. This ISA is 16-bit, whereas ARM is 32-bit. Not all instructions from ARM map in one-to-one fashion to Thumb. ARM instruction can be executed conditionally, Thumb instruction cannot, just piggyback the one-of-16 conditions after the mnemonic. Back to the code size saving, it will not be 2:1 ratio, either. It depends on the the program.

Symbian OS Unit

No matter how much time you invest into your application design, and how careful you are during program code writing – mistakes are inevitable. Without automated testing it is complicated and time consuming to ensure that changes will not break the existing code.

There are tools for Java and C++ which make it possible for programmers to execute simple testing on the stage of code writing and ensure the smooth integration of new features. But what about tools for other platforms? What about Symbian and BREW.

Symbian OS Unit is a port of the popular C++ unit testing framework CxxUnit. It provides a powerful and flexible testing framework whilst requiring the minimum of developer effort to produce a library of tests. It can be used with any of the available Symbian development environments and can currently be built for the UIQ and Series 60 reference platforms.

Symbian OS Unit is open source under the GNU Lesser General Public License. See the current status on the project's Sourceforge page for more information or to download the tool. Access the source via WebCVS.

Symbian OS Unit was developed and is supported by Penrillian.

To Read more you can go to it's site. http://www.symbianosunit.co.uk/

Symbian S60 Code Tips
Hide application from the tasks list

void CSomeDocument::UpdateTaskNameL(CApaWindowGroupName* aWgName)
{
// Set app task name hidden in the task list
aWgName->SetHidden(ETrue);
}

Sony Ericsson to Acquire UIQ

Sony Ericsson today announced it has reached agreement in principle for acquiring the Swedish software company UIQ Technology AB, a wholly-owned subsidiary of Symbian Ltd. UIQ Technology, which uses Symbian OS™, licenses the UIQ user interface and application development platform to mobile phone vendors worldwide.

Sony Ericsson is already a licensee of UIQ Technology, and has been working closely with the company on UIQ version 3.0, which is included in Sony Ericsson’s P990 smartphone, M600 messaging phone and W950 Walkman® phone.

"UIQ offers excellent technical flexibility enabling us to provide compelling features such as push email, internet browsing, end user personalization, and enhanced music applications" explains Mats Lindoff, Chief Technology Officer at Sony Ericsson. "By acquiring UIQ Technology we will further invest and exploit the full potential of UIQ on Symbian OS for phone vendors, mobile operators, developers and consumers."

Following completion of the acquisition, UIQ Technology will operate as a separate business subsidiary of Sony Ericsson under its current management team. UIQ on Symbian OS will continue to be openly available, licensed on equal terms to all its licensees.

To read the full story go to this link

Drive Letter in S60 Phones

Drive Letter in S60 Phones

I know that some of the advanced users have already know the meaning of C:, D:, E: and Z: drives in S60 phones. However, I just recap it here because I have seen some questions floating around in some forum discussions.

If you are using built-in file manager from S60, it allows you to browse phone memory and memory card only. However, if you download third party file managers, such as SysExplorer or Y-Browser, it allows you to browse all drives in the file system. Look at the screenshot below.

• C:\. This drive is also called phone memory. Basically it is a flash memory where we can install applications and store our data. Unlike memory card, it is always inside our phone. So, even if we remove the memory card, our data are still there. However, note that the size of phone memory is limited.
• D:\. It is the drive used to store temporary files. The contents will be deleted when the device reboots. In many cases, we don’t use this drive.
• E:\. It is the drive of your memory card. Normally, this is the place where we install applications and install our data.
• Z:\. This is where the ROM image is stored. It contains all the operating system’s applications and data files. Since it is read-only memory, you cannot write anything. The only way to modify the contents of Z:\ drive is by flashing the phone, for example via Nokia Software Updater.

Symbian Platform Identification Codes

Devices based on the S60 platform have a built-in mechanism to warn users attempting to install incompatible software — either a non-S60-based application or an S60-based application targeted at a newer platform release than the release of the device into which the application is being installed. Incompatibility can also be an issue when S60-based applications that are built only for a particular S60 device model are being installed on a different S60 device model. An example of an application that is incompatible with a device model is a camera application that is being installed into a device that does not have a camera.

All installation packages of S60 applications should contain the id-sequence in order to facilitate smooth installation of the software. If the id-sequence is not found or the id-sequence is not recognized by a device (for example, the id-sequence refers to a newer platform release than the release supported by the device), the user will get a notification about the potential incompatibility. Depending on the platform release, the installation process can be continued, but at the risk of application functionality failure.

To avoid the above failures the identification code is specified as a requisite in the installation package file (.pkg).

For 3.x and above.
#{"MyApplication"},(0x20000001),1,0,0
[0x101F7961], 0, 0, 0, {"Series60ProductID"}

For 1.x and 2.x
#{"MyApplication"},(0x10000001),1,0,0
; Platform ID for S60 2nd Edition
(0x101F7960), 0, 0, 0, {" Series60ProductID"}

For more Information you can refer to http://forum.nokia.com

Symbian Signed means less choice

They say "Symbian Signed is designed to keep troublemakers out. Both intentional troublemakers such as virus writers and unintentional troublemakers such as software with critical bugs. The idea is to have an outside third party company doing the testing in order to have the same rules and tests for everyone".

To me, this sounds too good to be true. Unrealistic.

In my opinion the reality is that Symbian Signed keeps many developers out! Less software for Symbian phones, less choice...

BREW 2007 DEVELOPER AWARDS CALL

BREW publishers and developers are invited to submit their top BREW applications for consideration by completing an online entry form and providing a demo of their application. Finalists will be announced on the BREW 2007 Web site on May 21 and winners will be revealed at the awards ceremony hosted during the BREW 2007 Conference.

For reading full Story www.brew2007.com

Vista gets official release dates

Thanks crahak for posting this in BPTN. Microsoft has set November 30 as the release date for Vista (and Office 2007) to business customers and January 30, 2007 as the date for the official launch to consumers and The World At Large. Five years, three months and five days after Windows XP made its debut, Microsoft will usher its next-generation OS onto the stage.
APC has been advised by a very well placed source that January 30, 2007 is about to be announced as the official release date for Vista.

In addition, in a move that mirrors previous side-by-side launches of Microsoft's OS and Office suite (in the 95 and XP waves), Office 2007 will also touch down on that day. However, as previously planned, Vista and Office 2007 will first step out for a 'business launch' on November 30 (alongside Exchange 2007). From that date, the programs will be available to corporate customers who hold an enterprise licence or software assurance deal with Microsoft.

Read FullSory http://apcmag.com/node/4258

Internet Explorer 7 Final

Internet Explorer 7 is a major step forward in ease of use and security. Explore the tabs to learn more.

Upgrade with Confidence — check out Internet Explorer 7 and install it today.

Do you Love FireFox and believe what they all clam about FireFox. Then read this

http://mywebpages.comcast.net/SupportCD/FirefoxMyths.html