Sony Ericsson UIQ 3 Bedienungsanleitung

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83

Zur Seite of

Richtige Gebrauchsanleitung

Die Vorschriften verpflichten den Verkäufer zur Übertragung der Gebrauchsanleitung Sony Ericsson UIQ 3 an den Erwerber, zusammen mit der Ware. Eine fehlende Anleitung oder falsche Informationen, die dem Verbraucher übertragen werden, bilden eine Grundlage für eine Reklamation aufgrund Unstimmigkeit des Geräts mit dem Vertrag. Rechtsmäßig lässt man das Anfügen einer Gebrauchsanleitung in anderer Form als Papierform zu, was letztens sehr oft genutzt wird, indem man eine grafische oder elektronische Anleitung von Sony Ericsson UIQ 3, sowie Anleitungsvideos für Nutzer beifügt. Die Bedingung ist, dass ihre Form leserlich und verständlich ist.

Was ist eine Gebrauchsanleitung?

Das Wort kommt vom lateinischen „instructio”, d.h. ordnen. Demnach kann man in der Anleitung Sony Ericsson UIQ 3 die Beschreibung der Etappen der Vorgehensweisen finden. Das Ziel der Anleitung ist die Belehrung, Vereinfachung des Starts, der Nutzung des Geräts oder auch der Ausführung bestimmter Tätigkeiten. Die Anleitung ist eine Sammlung von Informationen über ein Gegenstand/eine Dienstleistung, ein Hinweis.

Leider widmen nicht viele Nutzer ihre Zeit der Gebrauchsanleitung Sony Ericsson UIQ 3. Eine gute Gebrauchsanleitung erlaubt nicht nur eine Reihe zusätzlicher Funktionen des gekauften Geräts kennenzulernen, sondern hilft dabei viele Fehler zu vermeiden.

Was sollte also eine ideale Gebrauchsanleitung beinhalten?

Die Gebrauchsanleitung Sony Ericsson UIQ 3 sollte vor allem folgendes enthalten:
- Informationen über technische Daten des Geräts Sony Ericsson UIQ 3
- Den Namen des Produzenten und das Produktionsjahr des Geräts Sony Ericsson UIQ 3
- Grundsätze der Bedienung, Regulierung und Wartung des Geräts Sony Ericsson UIQ 3
- Sicherheitszeichen und Zertifikate, die die Übereinstimmung mit entsprechenden Normen bestätigen

Warum lesen wir keine Gebrauchsanleitungen?

Der Grund dafür ist die fehlende Zeit und die Sicherheit, was die bestimmten Funktionen der gekauften Geräte angeht. Leider ist das Anschließen und Starten von Sony Ericsson UIQ 3 zu wenig. Eine Anleitung beinhaltet eine Reihe von Hinweisen bezüglich bestimmter Funktionen, Sicherheitsgrundsätze, Wartungsarten (sogar das, welche Mittel man benutzen sollte), eventueller Fehler von Sony Ericsson UIQ 3 und Lösungsarten für Probleme, die während der Nutzung auftreten könnten. Immerhin kann man in der Gebrauchsanleitung die Kontaktnummer zum Service Sony Ericsson finden, wenn die vorgeschlagenen Lösungen nicht wirksam sind. Aktuell erfreuen sich Anleitungen in Form von interessanten Animationen oder Videoanleitungen an Popularität, die den Nutzer besser ansprechen als eine Broschüre. Diese Art von Anleitung gibt garantiert, dass der Nutzer sich das ganze Video anschaut, ohne die spezifizierten und komplizierten technischen Beschreibungen von Sony Ericsson UIQ 3 zu überspringen, wie es bei der Papierform passiert.

Warum sollte man Gebrauchsanleitungen lesen?

In der Gebrauchsanleitung finden wir vor allem die Antwort über den Bau sowie die Möglichkeiten des Geräts Sony Ericsson UIQ 3, über die Nutzung bestimmter Accessoires und eine Reihe von Informationen, die erlauben, jegliche Funktionen und Bequemlichkeiten zu nutzen.

Nach dem gelungenen Kauf des Geräts, sollte man einige Zeit für das Kennenlernen jedes Teils der Anleitung von Sony Ericsson UIQ 3 widmen. Aktuell sind sie genau vorbereitet oder übersetzt, damit sie nicht nur verständlich für die Nutzer sind, aber auch ihre grundliegende Hilfs-Informations-Funktion erfüllen.

Inhaltsverzeichnis der Gebrauchsanleitungen

  • Seite 1

    Developers guidelines October 2006 Signing applications for Sony Ericsson UIQ 3 phones[...]

  • Seite 2

    Developers guidelines | Signing applications 2 October 2006 This document is published by Sony Ericsson Mobile Communications AB, without any warranty*. Improvements and changes to this tex t necessitated by typographical errors, inaccuraci es of current information or improvements to programs and/or equipment , may be made by Sony Ericsson Mobile [...]

  • Seite 3

    Developers guidelines | Signing applications 3 October 2006 Sony Ericsson Developer World On www.sonyericsson.com/developer , developers will find documentation and tools such as phone White Papers, Deve lopers Guideline s for different t echnologies, SDKs and relevant APIs. The website also con- tains discussion forums monitored by the So ny Er ic[...]

  • Seite 4

    Developers guidelines | Signing applications 4 October 2006 Typographical conventions Code is written in Cour ier font, fo r example: TInt CCamera::CamerasAvailable() Trademarks and acknowledgements Symbian, Symbian OS, UIQ Technolog ies, UIQ and other Sy mbian marks ar e all trademar ks of Symbian Ltd. Other produc t and compan y names mentione d [...]

  • Seite 5

    Developers guidelines | Signing applications 5 October 2006 Contents Symbian OS v9 se curity architecture .............. ................ ............. ................ ............. 7 Introduction .............. ............. ............. ................ ............. ............. ................ ............. 8 Capabilities ......... ........[...]

  • Seite 6

    Developers guidelines | Signing applications 6 October 2006 Capability: WriteDe viceData .............. ................ ............. ................ ............. ........ 66 Capability: WriteUs erData ....... ............. ................ ............. ............. ................ ..... 74 Capability: Illegal ......... ............. ........[...]

  • Seite 7

    Developers guidelines | Signing applications 7 October 2006 Symbian OS v9 security architecture This chapter g ives a gene ral overview o f the Symbian OS v9 security feat ures as implemen ted in Sony Ericsson mobile phones.[...]

  • Seite 8

    Developers guidelines | Signing applications 8 October 2006 Introduction Symbian OS version 9.x is specifica lly intended fo r mid-range p hones to b e produced in large num bers of units. The open develop ment platform, fe aturing many new key techno logies, offers large opportunities f or ISVs (Independent Software Vendors) to find mar kets for t[...]

  • Seite 9

    Developers guidelines | Signing applications 9 October 2006 Identifiers Symbian OS v9 Plat form Security a lso requires th at applications c an be uniquely ide ntified and stri ctly classified to re flect their Plat Sec level of trust. For example, signed and unsigned a pplication are clearly separated by having UID values in separated value ranges[...]

  • Seite 10

    Developers guidelines | Signing applications 10 October 2006 IF a VID va lue othe r than 0 is to be used, it is s pecified in the .MMP file of the application. VID values must not be specified for unsigned applications. Data caging Data caging h as been introduce d in Symbian OS v 9 to prevent one application to overwrite dat a belong- ing to anoth[...]

  • Seite 11

    Developers guidelines | Signing applications 11 October 2006 The following table lists allowed user granted permissions per capa bility for unsigned applications: Note: An application that could be deployed as a n un signed - sandboxed app lic ation may as well be sub- dued to the Symbian Signed process. Wh en an appl ication like th is has been s [...]

  • Seite 12

    Developers guidelines | Signing applications 12 October 2006 blanket or one-shot permissions at install time. Only standard (generic) testing is required for an appli- cation to be Symbian Signed. • Extended capabilities Highly trusted applications may be granted access to this set. For an applicatio n utilizing one or more capabilities in this s[...]

  • Seite 13

    Developers guidelines | Signing applications 13 October 2006 Developer certificates As a consequence of t he Symbian OS v9 enhanc ed platform securit y, applications th at require access t o restricted APIs can not be installed o n targeted device s before they have been signed, which in turn makes it impossible to test applica tions on re al mobil[...]

  • Seite 14

    Developers guidelines | Signing applications 14 October 2006 Symbian OS v9 application signing This chapter describ es the practical implications of Symbian OS v9 platform sec urity and t he steps dev el- opers need to take during development o f Symbian Signed a pplications.[...]

  • Seite 15

    Developers guidelines | Signing applications 15 October 2006 Planning for development There are a number of con siderations to ta ke in the beg inning of th e development process for a Symbian OS applications. Apart from the normal syst em analysi s an d design, also t he design implications o n sign- ing requirements an d testing proced ures speci[...]

  • Seite 16

    Developers guidelines | Signing applications 16 October 2006 Note that an application can only be granted rights to exac tly the capabilities in a set that it actually requires. When sending an application for signing, a ll requested capabilities mu st be declared for the application to be a pproved.The following tables list all capabilities and de[...]

  • Seite 17

    Developers guidelines | Signing applications 17 October 2006 WriteDeviceData Grants write access to sensitive syste m data. SWEvent Grants read a ccess to co nfidential system data. System data t hat is not confiden tial does not need to be protected by this capability. API examples: Test utilities, FEP ProtServ Grants the right to a server to regi[...]

  • Seite 18

    Developers guidelines | Signing applications 18 October 2006 A complete list of functions per capa bility can be found in the appendix of this document, see “Functions listed by capability” on page 29, in the Sy mbian developer library, http://www.s ymbian.com/deve loper/ techlib/v9.1docs/index.asp , and in the UIQ 3 SDK documentation . For exa[...]

  • Seite 19

    Developers guidelines | Signing applications 19 October 2006 *”<path><My_Private_Key>.key”, “<path><My_Cert>.cer” [,KEY=”<My_PrivateKey_Pwd>] for example, *”filesdevcert2.key”,”filesdevcert2.cer”,KEY=”password” MakeSis is run with the modified . pkg file crea te the .SIS file prepared for sign[...]

  • Seite 20

    Developers guidelines | Signing applications 20 October 2006 In Symbian OS v9 , UID ranges have bee n changed comp ared to earlie r OS versions. The following table lists UID ranges to be allocated Symbian APP, EXE or DLL files of di fferent categories . UID classes 0-9 (range 0x0000000 0 – 0x9FFFFFFF) are r eferred to as the protecte d range , a[...]

  • Seite 21

    Developers guidelines | Signing applications 21 October 2006 When logged in on the Symbian Signed portal, UIDs allocated to the account can be viewed by clicking “View UIDs” in the left navigation bar. ACS publisher ID Having an application Symb ian Signed requires an AC S publisher ID, either owned by the develo per or by a publisher certifier[...]

  • Seite 22

    Developers guidelines | Signing applications 22 October 2006 Developer certificates can be issued on three differen t levels, depending primarily on wich capabilities are required and ho w many spe cific phones (identified by their IMEI) are to be used for tes ting. The fo llowing table lists granted capabilites for each certificate level, and the [...]

  • Seite 23

    Developers guidelines | Signing applications 23 October 2006 The image below g ives an over view of the st eps to go th rough for applications requir ing basic and extended set capabilities compared to when also manufacturer approved capabilites are required. The process for requesting a develope r certifica te not requ iring pho ne manufac turer a[...]

  • Seite 24

    Developers guidelines | Signing applications 24 October 2006 • Name and p ath for th e certifica te reques t (.csr) file to be gen erated. It is possible to select an e xist- ing file that will be overwritten. • Private key and passwo rd. An ACS publisher ID certifica te and its private key can be u sed, in which case the tool allows more capab[...]

  • Seite 25

    Developers guidelines | Signing applications 25 October 2006 4. Upload the .cs r file. When u ploaded, the re quest is forwarded t o Sony Ericsson , where a stee ring group reviews the reques t. Their decisio n is communicated to the developer via Symbian Signed. 5. When approved, the de veloper certificate can be viewed and checked and that its ca[...]

  • Seite 26

    Developers guidelines | Signing applications 26 October 2006 • Policy state ment dialog The application should launch a polic y statement dialog a t the very firs t application star tup, The dialog should summar ize the use of networ k access, local co nnectivity, multimedia reco rding, read /write user data, phone call and location. • PKG file[...]

  • Seite 27

    Developers guidelines | Signing applications 27 October 2006 3. Sony Ericsson grants the developer access to a login protected Sony Ericsson channel certifier we b page on the Sy mbian Signed website. Via this page th e developer c an submit the ap plication for t est- ing against the Symbian Signed criteria a s well as the Sony Ericsso n specific [...]

  • Seite 28

    Developers guidelines | Signing applications 28 October 2006 Appendix[...]

  • Seite 29

    Developers guidelines | Signing applications 29 October 2006 Functions listed by capability In the list, text within curly brackets { } indicates other capab ilities that the function is associated with. The text “Dependent” in curly bracket s indicates that the association with the capability is conditional. Capability: AllFiles CFileMan::Copy[...]

  • Seite 30

    Developers guidelines | Signing applications 30 October 2006 Capability: DiskAdmin RFormat::Next( TInt &);{} RFormat::Next(T PckgBuf< TInt > &,TRequestStatu s &);{} RFs::AddFileSystem(const TDesC &)const;{} RFs::AddPlugin(const TDesC &)const;{} RFs::CheckDisk(const TDesC &)const;{} RFs::ClearPassw ord(TInt,con st TMedi[...]

  • Seite 31

    Developers guidelines | Signing applications 31 October 2006 RFs::UnlockDr ive(TInt,con st TMediaPassword &,TB ool);{} RRawDisk::Open(RFs &,TInt);{} RRawDisk::Read(TIn t64,TDes8 &);{} RRawDisk::Write( TInt64,TDesC8 &);{ } Capability: Drm ContentAccess ::CAgentContent:: AgentSpecificComma nd(TInt,const T DesC8 &,TDes8 &)=0 ;{[...]

  • Seite 32

    Developers guidelines | Signing applications 32 October 2006 ContentAccess ::CAgentData::Ge tStringAttribut e(TInt,TDes &)=0;{} ContentAccess ::CAgentData: :Read(TDes8 &)=0;{ } ContentAccess ::CAgentData: :Read(TDes8 &, TInt)=0;{} ContentAccess ::CAgentData::Rea d(TDes8 &,TInt, TRequestStatu s &)=0;{} ContentAccess ::CAgentData:[...]

  • Seite 33

    Developers guidelines | Signing applications 33 October 2006 ContentAcc ess::CAgentMan ager::SetPrope rty(TAgent Property,TIn t)=0;{} ContentAccess ::CAgentRights Manager::Dele teAllRightsObjects (const TVirtualPathPt r &)=0;{} ContentAcc ess::CAgentRigh tsManager ::DeleteRights Object(cons t CRightsInf o &)=0;{} ContentAccess ::CAgentRigh [...]

  • Seite 34

    Developers guidelines | Signing applications 34 October 2006 ContentAccess ::CContent::Ge tStringAttribu te(TInt,TDes &,const TDesC &)const;{} ContentAcc ess::CConten t::GetStringAt tributeSet(RString Attribute Set &)const;{} ContentAccess ::CContent:: GetStringAttrib uteSet(RStringA ttributeSet &,c onst TDesC &)c onst;{} Conten[...]

  • Seite 35

    Developers guidelines | Signing applications 35 October 2006 ContentAccess ::CData::Rea d(TDes8 &)const ;{} ContentAccess ::CData::Rea d(TDes8 &,TInt) const;{} ContentAccess ::CData::Read (TDes8 &,TInt,TRe questStatus &)const ;{} ContentAccess ::CData::Rea d(TDes8 &,TRe questStatus &)const;{} ContentAcc ess::CData::See k(TSe[...]

  • Seite 36

    Developers guidelines | Signing applications 36 October 2006 ContentAccess ::CManager ::SetProperty(TAg entPropert y,TInt);{} ContentAcc ess::CRights Info::Descriptio n()const;{} ContentAcc ess::CRights Info::RightsStatu s()const;{} ContentAcc ess::CRights Info::RightsType()c onst;{} ContentAcc ess::CRights In fo::UniqueId()const;{} ContentAccess :[...]

  • Seite 37

    Developers guidelines | Signing applications 37 October 2006 CBluetoothSyn chronousLink::NewL (MBluetoothSynchronousL inkNotifier &,RSock etServ &);{} CBluetoothSyn chronousLink::N ewLC(MBluetoothSynchrono usLinkNotifier &,RSocketServ &);{} CSdpAgent::Attrib uteRequestL(MS dpElementBuilder *,TSdpServRecordHandle,TSdpAt tributeID);{}[...]

  • Seite 38

    Developers guidelines | Signing applications 38 October 2006 RSdpDatabase::Cre ateServiceRecordL (CSdpAttrValu eDES &,TSdpServRecordHandle &);{} RSdpDatabase::C reateServiceRe cordL(const TUUID &, TSdpServRecord Handle &);{} RSdpDatabase::DeleteAttribu teL(TSdpServRecordHan dle,TSdpAttributeID);{ } RSdpDatabase::D eleteRecordL(T Sdp[...]

  • Seite 39

    Developers guidelines | Signing applications 39 October 2006 Capability: MultimediaDD CCamera::NewL (MCameraObserve r2 &,TInt,TInt); {UserEnvironme nt} CDevASR::SetPrioritySe ttings(const T MMFPrioritySettings &);{} CMMFController::SetPrioritySettings(c onst TMMFPrioritySettings &)=0;{} CMMFUrlSink::SetSin kPrioritySettin gs(const TMMFP[...]

  • Seite 40

    Developers guidelines | Signing applications 40 October 2006 CMmfGlobalAudioEffect ::Se tSettingsByUidL(TUid);{} CSpeechRecognitionUtility::SetAudi oPriority(TInt,TInt,TInt,TInt);{} CVideoPlayerUtility::NewL(MVideoPl ayerUtilityObserver &,TInt,TMdaPriorityP reference,R W sSession &,CWsScreenDevic e &,RWindowBase &,const TRec t &[...]

  • Seite 41

    Developers guidelines | Signing applications 41 October 2006 RCall::AnswerIncomingCall(const TD esC8 &)const;{NetworkServices} RCall::AnswerIncomingCallCan cel()const; {NetworkServices } RCall::Dial(TRequ estStatus &,const TD esC8 &,const TTelN umberC &);{Network Services} RCall::Dial(TReques tStatus &,const TTelN umberC &);[...]

  • Seite 42

    Developers guidelines | Signing applications 42 October 2006 RMobilePhone::SetSmar tCardApplicationSt atus(TReq uestStatus &,co nst TAID &, TSmartCardApplic a- tionAction)cons t;{WriteDevic eData} RMobilePhone::UpdateScF ile(TRequestStatus &,con st TScFilePathWithAcce ssOffsets &,TDes8 &)const;{WriteDe viceData} RMobileSmsMessag[...]

  • Seite 43

    Developers guidelines | Signing applications 43 October 2006 RSat::ClientSatProfileIndi cation(const TDesC8 &) const;{WriteDeviceData} RSat::EventDownload(TRe questStatus &,TEvent Li st,con st TDesC8 &)const;{Write DeviceData} RSat::MenuSele ction(TRequest Status &,cons t TDesC8 &)const;{Rea dDeviceData} RSat::NotifyCa llControl[...]

  • Seite 44

    Developers guidelines | Signing applications 44 October 2006 CExtensionBase::C ExtensionBas e();{} CExtensionBase::C opy(const C ExtensionBas e &)=0;{} CExtensionBase::C reateL()=0;{} CExtensionBase::D ata()=0;{} CExtensionBase::ParseMessage (const TDesC8 &)=0;{} CExtensionBase::Type()const;{} CExtensionBase::~CExtensionBase(); {} CFaxTrans[...]

  • Seite 45

    Developers guidelines | Signing applications 45 October 2006 CTelephony::H angup(TRequest Status &,const T CallId &)const;{} CTelephony::H old(TRequestStatus &,co nst TCallId &)const;{} CTelephony ::Resume(TRe questStatus &,const TCallI d &)const;{ } CTelephony:: SendDTMFTones (TRequestStatu s &,const TDesC &)cons t;[...]

  • Seite 46

    Developers guidelines | Signing applications 46 October 2006 RCall::LoanDa taPort(TReques tStatus &,TComm Port &);{NetworkCo ntrol} RCall::Recov erDataPort()co nst;{Networ kControl} RCall::TransferOwn ership( )const;{} RCdmaMobileCa ll::NotifyInco mingNetworkF lashWithInfo(T RequestStatu s &,TDes8 &)cons t;{ReadUse r- Data} RCdmaMob[...]

  • Seite 47

    Developers guidelines | Signing applications 47 October 2006 RMobileCall::DialNoFdnCheck(TReques tStatus &,co nst TDesC8 &,const TDesC &)const;{N etworkContr ol} RMobileCall::GoOn eToOne(TReques tStatus &)const;{} RMobileCall::HangupWithUUI(TRequ estStatus &,const TMobileCa llUUI &)cons t;{WriteUserData} RMobileCall::Hold(TR[...]

  • Seite 48

    Developers guidelines | Signing applications 48 October 2006 RMobilePhone::Sen dDTMFTone s(TRequestSta tus &,const TDesC &)const;{} RMobilePhone::Sen dNetworkService Request(TReq uestStatus &,co nst TDesC &)const; {WriteDeviceDat a} RMobilePhone::SendNe tworkServiceRequ estNoFdnCheck(T RequestStatus &,const TDesC &)const;{Ne[...]

  • Seite 49

    Developers guidelines | Signing applications 49 October 2006 RPacketContext ::AddMediaAut horizationL(TRequ estStatus &,CTFT MediaAutho rizationV3 &)const ;{Writ- eDeviceDat a} RPacketConte xt::AddPacke tFilter(TReques tStatus &,const TDe sC8 &)const;{ WriteDeviceD ata} RPacketConte xt::Create NewTFT(TReque stStatus &,co nst TIn[...]

  • Seite 50

    Developers guidelines | Signing applications 50 October 2006 RSyncMLDevManJob ::CreateL(RSyn cMLSession &,TSmlProf ileId,TSmlConne ctionId);{Lo calServices} Capability: PowerMgmt Power::CancelWak eupEventNotification ();{} Power::DisableWa keupEvents();{} Power::EnableWa keupEvents(T PowerState); {} Power::PowerDo wn();{} Power::RequestWakeupEv[...]

  • Seite 51

    Developers guidelines | Signing applications 51 October 2006 CRetrieveMobilePhoneCFList: :Start(TRequestSt atus &,RMobilePhone::TMobilePho neCFCondition,RMob- ilePhone::TMob ileInfoLocation );{NetworkServ ices} CRetrieveMob ilePhoneCWList:: RetrieveList L();{} CRetrieveMob ilePhoneCWList:: Start(TReq uestStatus &,RM obilePhone::T MobileInfo[...]

  • Seite 52

    Developers guidelines | Signing applications 52 October 2006 CTelephony:: GetSubscriberId (TRequestStatus &,TDes8 &) const;{} RBTRegistry::C reateView(co nst TBTRegist rySearch &,TReques tStatus &);{Loca lServices} RBTRegistry::G etDevice(TBTNa melessDevice &,TReque stStatus &);{LocalServic es} RCdmaMobilePhone: :ProcessOtaR[...]

  • Seite 53

    Developers guidelines | Signing applications 53 October 2006 RMobilePhone::GetSubscribe rId(TRequestStatus &,TMob ilePhoneSubscriberId &)const;{} RMobilePhone::NotifyCur rentNetworkChange (TRequestStatus &,TDes8 &,TMo bilePhoneLocationAr eaV1 &)const;{Location } RMobilePhone::No tifyDefaultPrivacyC hange(TReq uestStatus &,T [...]

  • Seite 54

    Developers guidelines | Signing applications 54 October 2006 RSat::NotifyDispla yTextPCmd(TRequestSt atus &,TDes8 &)cons t;{} RSat::NotifyGetServiceInfoPCmd(T RequestStatu s &,TDes8 &)cons t;{} RSat::NotifyLaun chBrowserPCmd(T RequestStatus &,TD es8 &)const;{} RSat::NotifyLoc alInfoPCmd(TRequ estStatus &,TDes8 &) con[...]

  • Seite 55

    Developers guidelines | Signing applications 55 October 2006 CAgnEntry::OpenEmbeddedStoreL();{} CAgnEntry::Up dateNotesT extL();{Writ eUserData} CAgnEntryMana ger::UpdateE ntryL(CAgnE ntry *,TStr eamId &);{} CAgnEntryMod el::AddEntryL(CAgnEntr y *,TAgnEntryId) ;{WriteUserD ata} CAgnEntryModel::AddTodoList L(CAgnTodoList *,TInt);{Write UserData}[...]

  • Seite 56

    Developers guidelines | Signing applications 56 October 2006 CAgnEntryMo del::FetchG sEntryL( const HBuf C8 &)const; {} CAgnEntryMo del::FetchG sEntryL( const HBuf C8 &,TTime)con st;{} CAgnEntryMod el::GetGuidL (const CAgnEntry &)const;{} CAgnEntryMod el::GetLiteEn tryFromServe rL(TAgnEnt ryId,CAgnSort EntryAllocato r *)const;{} CAgnEnt[...]

  • Seite 57

    Developers guidelines | Signing applications 57 October 2006 CAgnModel::AddTodoListL(CAg nTodoList *,TInt);{Writ eUserData} CAgnModel::CutInstan ceL(CAgnEntry *,TAgnWhichInst ances);{WriteUserData} CAgnModel::CutInstan ceL(const TAgnIn stanceId &,TAgnWhichInsta nces);{WriteUserData} CAgnModel::Delet eInstanceL(CAgn Entry *,TAgn WhichInstanc es)[...]

  • Seite 58

    Developers guidelines | Signing applications 58 October 2006 CContactDa tabase::GetDefa ultNameL(TDes &);{} CContactDa tabase::GetSp eedDialFieldL (TInt,TDes &); {} CContactDatabase::ListD atabasesL();{} CContactDatabase::ListD atabasesL(TDriveUnit);{} CContactDa tabase::Matc hPhoneNumbe rL(const TDesC &,TInt);{} CContactDatabase::O pen[...]

  • Seite 59

    Developers guidelines | Signing applications 59 October 2006 CContactNa medRemoteView::Ne wL(MContactVie wObserver &,con st TDesC &,co nst CContact Database &,const RConta ctViewSortOr der &,TContac tViewPreferences);{ } CContactNa medRemoteView::Ne wL(MContactVie wObserver &,con st TDesC &,co nst CContact Database &,con[...]

  • Seite 60

    Developers guidelines | Signing applications 60 October 2006 CContactViewBa se::CContactViewBa se_Reserved_1(T Function,TAny *);{} CContactViewBa se::Contact AtL(TInt)cons t=0;{} CContactViewBas e::ContactV iewPreference s()=0;{} CContactViewBa se::ContactsMat chingCriteria L(const MDesC 16Array &,RPoint erArray< CViewCon tact > &);{}[...]

  • Seite 61

    Developers guidelines | Signing applications 61 October 2006 CTelephony ::GetCallInfo(T Des8 &,TDes8 &,T Des8 &)const;{} CTelephony::G etCurrentN etworkInfo(T RequestStatus &, TDes8 &)const ;{Location, Re adDeviceData} CTelephony::G etCurrentN etworkName (TRequestStatus &,TDes8 &)con st;{} CTelephony:: GetOperator Name(T[...]

  • Seite 62

    Developers guidelines | Signing applications 62 October 2006 RAgendaServ::Refr eshTodoListListL(CAgn TodoListList *,CAgnDe letedTodoListList * );{} RAgendaServ::Res toreNotesText L(TStreamId);{} RAgendaServ::Upda teEntryL(CAgnEntr y *,TAgnEntryId);{ WriteUserData} RCdmaMobileCa ll::NotifyInco mingNetworkF lashWithInfo(T RequestStatu s &,TDes8 &[...]

  • Seite 63

    Developers guidelines | Signing applications 63 October 2006 RMobileBroadca stMessaging::N otifyLangua geFilterChange (TRequestSta tus &,TDes16 &)const;{} RMobileCall::GetMobileCa llInfo(TDe s8 &)const; {} RMobileCall::NotifyR emotePartyIn foChange(TRequ estStatus &, TDes8 &)const;{} RMobileCall::ReceiveUUI (TRequestStatus &[...]

  • Seite 64

    Developers guidelines | Signing applications 64 October 2006 RMsvServerSession ::DeleteAttach ment(TMsvId,const TDes C &);{None, WriteDeviceData , WriteUserData} RMsvServerSession: :DeleteEntrie sL(const CMsvEntrySelection &, TMsvOp);{Non e, WriteDeviceD ata, Wri- teUserData} RMsvServerSession: :DeleteEntrie sL(const CMsvEn trySelection &am[...]

  • Seite 65

    Developers guidelines | Signing applications 65 October 2006 RPhoneBookSessio n::DoSynchro nisation(TRequ estStatus &,TU id);{WriteUser Data} RPhoneBookSession::Shu tdownServer(TBool);{Writ eUserData} RPhoneBookSessio n::ValidateCon tact(MConta ctSynchroniser: :TValidateO peration,TC ontactItemId);{ } RSat::NotifyCbDownload (TRequestStatu s &am[...]

  • Seite 66

    Developers guidelines | Signing applications 66 October 2006 RWsSession::Simulate KeyEvent(TKeyEvent);{} RWsSession::Simulate RawEvent(TRawEvent);{} UserSvr::AddEvent(c onst TRawEvent &); {} Capability: Tcb RLocalDrive::C onnect(TInt,T Bool &);{} TBusLocalDrive::Connect(T Int,TBool &);{} Capability: TrustedUI Capability: UserEnvironment[...]

  • Seite 67

    Developers guidelines | Signing applications 67 October 2006 CCoeEnv::InstallFepL(TU id,const TBool);{} CCoeFep::Is TurnedOffB yL(cons t TKeyEven t &)const;{} CCoeFep::Is TurnedOnB yL(cons t TKeyEven t &)const;{} CCoeFep::W riteAttribute DataAndBroadca stL(TUid);{} CCoeFep::W riteAttributeD ataAndBroadcast L(const TArray< TU id > &[...]

  • Seite 68

    Developers guidelines | Signing applications 68 October 2006 CSmsSimParamOperation ::WriteSimParamsL(c onst CMobilePhone SmspList &,TUid,TMs vId,CMsvSes- sion &,TRequestStatu s &);{} CUnifiedCertSt ore::Remove(c onst CCTCert Info &,TRequestSta tus &);{WriteUs erData} CUnifiedCertStore::SetApp licability(const CCTCertInfo &,c[...]

  • Seite 69

    Developers guidelines | Signing applications 69 October 2006 RBTRegistry::U npairDevice(const TBTDevAddr &,TReq uestStatus &);{ LocalServices} RCall::SetFa xSettings(cons t TFaxSessionSet tings &)const;{} RCdmaMobilePhone::L ockNam(TRequestStatus &,TMobil ePhoneNamCommitStatus)const;{ } RCdmaMobilePhone: :ProcessOtaRequest(TReque st[...]

  • Seite 70

    Developers guidelines | Signing applications 70 October 2006 RMobilePhone::Pro gramFeatur eCode(TReq uestStatus &,c onst TDesC &,T MobilePhon eNetworkServ- ice,TMobilePhoneSe rviceAction)const;{ } RMobilePhone::Sele ctNetwork(TReq uestStatus &, TBool,const TMo bilePhoneNet workManualSelec tion &)const;{Net workServ ices} RMobilePhon[...]

  • Seite 71

    Developers guidelines | Signing applications 71 October 2006 RMobilePhone::SetPer sonalisationStatus( TRequestSt atus &,const TMobilePhon ePersonalisation,const TDes &)const;{NetworkCo ntrol} RMobilePhone::SetPuct (TRequestStatu s &,const TDesC8 &)const;{} RMobilePhone::SetSSPassword (TRequestStatus &,const TDesC8 &,const TI[...]

  • Seite 72

    Developers guidelines | Signing applications 72 October 2006 RMsvServerSession: :CreateEntryL(con st TMsvEntry &,TMsvOp,T SecureId,TRequ estStatus &);{None, ReadUserData, WriteU serData} RMsvServerSession::DeInstallM tmGroup(const TDesC &);{} RMsvServerSessio n::DeleteAtt achment(TMsvI d,const T DesC &);{None , ReadUserData, WriteUs[...]

  • Seite 73

    Developers guidelines | Signing applications 73 October 2006 RPacketSer vice::SetPr eferredBear er(TRequest Status &,TPr eferredBe arer)cons t;{Netwo rkService s} RProperty::D efine(TUid, TUint,TInt,con st TSecurit yPolicy &,const TSecurityPolicy &,TI nt);{} RProperty::Defin e(TUint,TInt ,const TSecu rit yPolicy &,const TSecur ityPo[...]

  • Seite 74

    Developers guidelines | Signing applications 74 October 2006 RWsSession::Set KeyboardRepea tRate(const TT imeIntervalMicro Seconds32 &,con st TTimeIntervalMicro Seconds32 &);{ } RWsSession::Set ModifierState(T EventModifier,T ModifierSta te);{} RWsSession::Set PointerCursor Area(TInt,co nst TRect &);{ } RWsSession::SetPointer CursorPosi[...]

  • Seite 75

    Developers guidelines | Signing applications 75 October 2006 CAgnEntryModel::AddEnt ryL(CAgnEntry *,TAgnEntryId );{ReadUserData} CAgnEntryModel::AddEntryL(CAgn Entry *,TAgnEntryId,TCommit,TUseExistin gUniqueId);{} CAgnEntryM odel::AddG sChildExce ptionEntry L(CAgnEntry *,TAgnUn iqueId,TGsBasicD ata,TTime);{ } CAgnEntryModel::AddGsC hildRuleEntryL(C[...]

  • Seite 76

    Developers guidelines | Signing applications 76 October 2006 CAgnEntryMod el::Unregister ObserverL(TUid); {} CAgnEntryMod el::UpdateE ntryL(CAgnE ntry *,TAgn EntryId);{Re adUserDat a} CAgnEntryModel::UpdateOb serverControllerL(); {} CAgnEntryModel::Upda teTodoListL(CAgn TodoList * );{ReadUserData } CAgnIndexedM odel::Delete TidiedEntriesL ();{ReadU[...]

  • Seite 77

    Developers guidelines | Signing applications 77 October 2006 CCalEntryView::DeleteL(const CDesC8Array &);{} CCalEntryView::Store L(const RPointerArr ay< CCalEntry > &,T Int &);{} CCalEntryView: :UpdateL(const RPointerArray< CCalE ntry > &,TInt &);{ } CCalInstance View::DeleteL( CCalInstanc e *,CalCommon::T Recurrence[...]

  • Seite 78

    Developers guidelines | Signing applications 78 October 2006 CContactDatabase::Re setServerSpeedDialsL();{} CContactDa tabase::SetCu rrentDatab ase(const TD esC &)const;{} CContactDatabase ::SetCurrent Item(const TCont actItemId);{ } CContactDa tabase::SetDa tabaseDriveL (TDriveUnit, TBool);{} CContactDa tabase::SetField AsSpeedDialL(CCo ntactI[...]

  • Seite 79

    Developers guidelines | Signing applications 79 October 2006 CSmsHeader::Store L(CMsvStore &)const;{} CUnifiedCertS tore::Remove (const CCTCer tInfo &,TReques tStatus &);{Wr iteDeviceData} CUnifiedKeySto re::CreateKey (TInt,TKeyU sagePKCS15,TUint, const TDe sC &,CCTKeyInfo::EKe yAlgo- rithm,TInt,TTime ,TTime,CCTKeyInfo *&,TReque[...]

  • Seite 80

    Developers guidelines | Signing applications 80 October 2006 RAgendaServ::Delet eTodoList(TAgn UniqueId);{} RAgendaServ::Delet eTodoListL(CAgnT odoList *);{} RAgendaServ::IncEnt ryRefCountL(const T AgnUniqueId);{} RAgendaServ::Inc EntryRefCountsL (const CArrayFix< TAgnUniqueId > &);{} RAgendaServ::Que ueNextAlarmL(const TT ime &,CArra[...]

  • Seite 81

    Developers guidelines | Signing applications 81 October 2006 RMsvServerSessio n::ChangeAtt ributesL(cons t CMsvEntrySele ction &,TUint, TUint);{} RMsvServerSessio n::ChangeEnt ryL(const TM svEntry &,TMsvOp ,TSecureId) ;{None, Read UserData, Writ - eDeviceDat a} RMsvServerSession::Cha ngeEntryL(const TMsvEnt ry &,TMsvOp,TSecureId, TReque[...]

  • Seite 82

    Developers guidelines | Signing applications 82 October 2006 RPhoneBookSession::Can celRequest(TPhonebook SyncRequestCancel,TUid);{Read UserData} RPhoneBookSession::Dele teContact(TRequestS tatus &,TContactIte mId);{} RPhoneBookSession ::DoSynchron isation(TReques tStatus &);{ReadU serData} RPhoneBookSessio n::DoSynchro nisation(TReq uestSt[...]

  • Seite 83

    Developers guidelines | Signing applications 83 October 2006 MCTKeyStoreMa nager::Expor tEncryptedKe y(TCTTokenOb jectHandle,c onst CPBEncryptPa rms &,HBufC8 *&,TReque stStatus &)=0;{} MCTKeyStoreMa nager::Expor tKey(TCTToke nObjectHan dle,HBufC8 *&,TRe questStatus &)=0;{} MCTKeyStoreMa nager::Set ManagementPolic y(TCTToken Obje[...]