Benutzeranleitung / Produktwartung UIQ 3 des Produzenten Sony Ericsson
Zur Seite of 83
Developers guidelines October 2006 Signing applications for Sony Ericsson UIQ 3 phones.
Developers guidelines | Signing applications 2 October 2006 This document is published by Sony Ericsson Mobile Communications AB, without any warranty*.
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.
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.
Developers guidelines | Signing applications 5 October 2006 Contents Symbian OS v9 se curity architecture .............. ................ ............. ................ ............. 7 Introduction .............. ............. ............. ..........
Developers guidelines | Signing applications 6 October 2006 Capability: WriteDe viceData .............. ................ ............. ................ ............. ........ 66 Capability: WriteUs erData ....... ............. ................ .......
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.
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.
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.
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.
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.
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.
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 restricte.
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.
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.
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.
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.
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.
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 .
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 .
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.
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.
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.
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.
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.
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.
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.
Developers guidelines | Signing applications 28 October 2006 Appendix.
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.
Developers guidelines | Signing applications 30 October 2006 Capability: DiskAdmin RFormat::Next( TInt &);{} RFormat::Next(T PckgBuf< TInt > &,TRequestStatu s &);{} RFs::AddFileSyste.
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 &);{} RRaw.
Developers guidelines | Signing applications 32 October 2006 ContentAccess ::CAgentData::Ge tStringAttribut e(TInt,TDes &)=0;{} ContentAccess ::CAgentData: :Read(TDes8 &)=0;{ } ContentAccess :.
Developers guidelines | Signing applications 33 October 2006 ContentAcc ess::CAgentMan ager::SetPrope rty(TAgent Property,TIn t)=0;{} ContentAccess ::CAgentRights Manager::Dele teAllRightsObjects (con.
Developers guidelines | Signing applications 34 October 2006 ContentAccess ::CContent::Ge tStringAttribu te(TInt,TDes &,const TDesC &)const;{} ContentAcc ess::CConten t::GetStringAt tributeSet.
Developers guidelines | Signing applications 35 October 2006 ContentAccess ::CData::Rea d(TDes8 &)const ;{} ContentAccess ::CData::Rea d(TDes8 &,TInt) const;{} ContentAccess ::CData::Read (TDe.
Developers guidelines | Signing applications 36 October 2006 ContentAccess ::CManager ::SetProperty(TAg entPropert y,TInt);{} ContentAcc ess::CRights Info::Descriptio n()const;{} ContentAcc ess::CRigh.
Developers guidelines | Signing applications 37 October 2006 CBluetoothSyn chronousLink::NewL (MBluetoothSynchronousL inkNotifier &,RSock etServ &);{} CBluetoothSyn chronousLink::N ewLC(MBluet.
Developers guidelines | Signing applications 38 October 2006 RSdpDatabase::Cre ateServiceRecordL (CSdpAttrValu eDES &,TSdpServRecordHandle &);{} RSdpDatabase::C reateServiceRe cordL(const TUUI.
Developers guidelines | Signing applications 39 October 2006 Capability: MultimediaDD CCamera::NewL (MCameraObserve r2 &,TInt,TInt); {UserEnvironme nt} CDevASR::SetPrioritySe ttings(const T MMFPri.
Developers guidelines | Signing applications 40 October 2006 CMmfGlobalAudioEffect ::Se tSettingsByUidL(TUid);{} CSpeechRecognitionUtility::SetAudi oPriority(TInt,TInt,TInt,TInt);{} CVideoPlayerUtilit.
Developers guidelines | Signing applications 41 October 2006 RCall::AnswerIncomingCall(const TD esC8 &)const;{NetworkServices} RCall::AnswerIncomingCallCan cel()const; {NetworkServices } RCall::Di.
Developers guidelines | Signing applications 42 October 2006 RMobilePhone::SetSmar tCardApplicationSt atus(TReq uestStatus &,co nst TAID &, TSmartCardApplic a- tionAction)cons t;{WriteDevic eD.
Developers guidelines | Signing applications 43 October 2006 RSat::ClientSatProfileIndi cation(const TDesC8 &) const;{WriteDeviceData} RSat::EventDownload(TRe questStatus &,TEvent Li st,con st.
Developers guidelines | Signing applications 44 October 2006 CExtensionBase::C ExtensionBas e();{} CExtensionBase::C opy(const C ExtensionBas e &)=0;{} CExtensionBase::C reateL()=0;{} CExtensionBa.
Developers guidelines | Signing applications 45 October 2006 CTelephony::H angup(TRequest Status &,const T CallId &)const;{} CTelephony::H old(TRequestStatus &,co nst TCallId &)const;{.
Developers guidelines | Signing applications 46 October 2006 RCall::LoanDa taPort(TReques tStatus &,TComm Port &);{NetworkCo ntrol} RCall::Recov erDataPort()co nst;{Networ kControl} RCall::Tra.
Developers guidelines | Signing applications 47 October 2006 RMobileCall::DialNoFdnCheck(TReques tStatus &,co nst TDesC8 &,const TDesC &)const;{N etworkContr ol} RMobileCall::GoOn eToOne(T.
Developers guidelines | Signing applications 48 October 2006 RMobilePhone::Sen dDTMFTone s(TRequestSta tus &,const TDesC &)const;{} RMobilePhone::Sen dNetworkService Request(TReq uestStatus &a.
Developers guidelines | Signing applications 49 October 2006 RPacketContext ::AddMediaAut horizationL(TRequ estStatus &,CTFT MediaAutho rizationV3 &)const ;{Writ- eDeviceDat a} RPacketConte xt.
Developers guidelines | Signing applications 50 October 2006 RSyncMLDevManJob ::CreateL(RSyn cMLSession &,TSmlProf ileId,TSmlConne ctionId);{Lo calServices} Capability: PowerMgmt Power::CancelWak .
Developers guidelines | Signing applications 51 October 2006 CRetrieveMobilePhoneCFList: :Start(TRequestSt atus &,RMobilePhone::TMobilePho neCFCondition,RMob- ilePhone::TMob ileInfoLocation );{Net.
Developers guidelines | Signing applications 52 October 2006 CTelephony:: GetSubscriberId (TRequestStatus &,TDes8 &) const;{} RBTRegistry::C reateView(co nst TBTRegist rySearch &,TReques t.
Developers guidelines | Signing applications 53 October 2006 RMobilePhone::GetSubscribe rId(TRequestStatus &,TMob ilePhoneSubscriberId &)const;{} RMobilePhone::NotifyCur rentNetworkChange (TRe.
Developers guidelines | Signing applications 54 October 2006 RSat::NotifyDispla yTextPCmd(TRequestSt atus &,TDes8 &)cons t;{} RSat::NotifyGetServiceInfoPCmd(T RequestStatu s &,TDes8 &).
Developers guidelines | Signing applications 55 October 2006 CAgnEntry::OpenEmbeddedStoreL();{} CAgnEntry::Up dateNotesT extL();{Writ eUserData} CAgnEntryMana ger::UpdateE ntryL(CAgnE ntry *,TStr eamI.
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;{} CAgnEnt.
Developers guidelines | Signing applications 57 October 2006 CAgnModel::AddTodoListL(CAg nTodoList *,TInt);{Writ eUserData} CAgnModel::CutInstan ceL(CAgnEntry *,TAgnWhichInst ances);{WriteUserData} CA.
Developers guidelines | Signing applications 58 October 2006 CContactDa tabase::GetDefa ultNameL(TDes &);{} CContactDa tabase::GetSp eedDialFieldL (TInt,TDes &); {} CContactDatabase::ListD ata.
Developers guidelines | Signing applications 59 October 2006 CContactNa medRemoteView::Ne wL(MContactVie wObserver &,con st TDesC &,co nst CContact Database &,const RConta ctViewSortOr der.
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::Co.
Developers guidelines | Signing applications 61 October 2006 CTelephony ::GetCallInfo(T Des8 &,TDes8 &,T Des8 &)const;{} CTelephony::G etCurrentN etworkInfo(T RequestStatus &, TDes8 &a.
Developers guidelines | Signing applications 62 October 2006 RAgendaServ::Refr eshTodoListListL(CAgn TodoListList *,CAgnDe letedTodoListList * );{} RAgendaServ::Res toreNotesText L(TStreamId);{} RAgen.
Developers guidelines | Signing applications 63 October 2006 RMobileBroadca stMessaging::N otifyLangua geFilterChange (TRequestSta tus &,TDes16 &)const;{} RMobileCall::GetMobileCa llInfo(TDe s.
Developers guidelines | Signing applications 64 October 2006 RMsvServerSession ::DeleteAttach ment(TMsvId,const TDes C &);{None, WriteDeviceData , WriteUserData} RMsvServerSession: :DeleteEntrie s.
Developers guidelines | Signing applications 65 October 2006 RPhoneBookSessio n::DoSynchro nisation(TRequ estStatus &,TU id);{WriteUser Data} RPhoneBookSession::Shu tdownServer(TBool);{Writ eUserD.
Developers guidelines | Signing applications 66 October 2006 RWsSession::Simulate KeyEvent(TKeyEvent);{} RWsSession::Simulate RawEvent(TRawEvent);{} UserSvr::AddEvent(c onst TRawEvent &); {} Capab.
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 TKeyE.
Developers guidelines | Signing applications 68 October 2006 CSmsSimParamOperation ::WriteSimParamsL(c onst CMobilePhone SmspList &,TUid,TMs vId,CMsvSes- sion &,TRequestStatu s &);{} CUnif.
Developers guidelines | Signing applications 69 October 2006 RBTRegistry::U npairDevice(const TBTDevAddr &,TReq uestStatus &);{ LocalServices} RCall::SetFa xSettings(cons t TFaxSessionSet ting.
Developers guidelines | Signing applications 70 October 2006 RMobilePhone::Pro gramFeatur eCode(TReq uestStatus &,c onst TDesC &,T MobilePhon eNetworkServ- ice,TMobilePhoneSe rviceAction)const.
Developers guidelines | Signing applications 71 October 2006 RMobilePhone::SetPer sonalisationStatus( TRequestSt atus &,const TMobilePhon ePersonalisation,const TDes &)const;{NetworkCo ntrol} .
Developers guidelines | Signing applications 72 October 2006 RMsvServerSession: :CreateEntryL(con st TMsvEntry &,TMsvOp,T SecureId,TRequ estStatus &);{None, ReadUserData, WriteU serData} RMsvS.
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,TI.
Developers guidelines | Signing applications 74 October 2006 RWsSession::Set KeyboardRepea tRate(const TT imeIntervalMicro Seconds32 &,con st TTimeIntervalMicro Seconds32 &);{ } RWsSession::Se.
Developers guidelines | Signing applications 75 October 2006 CAgnEntryModel::AddEnt ryL(CAgnEntry *,TAgnEntryId );{ReadUserData} CAgnEntryModel::AddEntryL(CAgn Entry *,TAgnEntryId,TCommit,TUseExistin .
Developers guidelines | Signing applications 76 October 2006 CAgnEntryMod el::Unregister ObserverL(TUid); {} CAgnEntryMod el::UpdateE ntryL(CAgnE ntry *,TAgn EntryId);{Re adUserDat a} CAgnEntryModel::.
Developers guidelines | Signing applications 77 October 2006 CCalEntryView::DeleteL(const CDesC8Array &);{} CCalEntryView::Store L(const RPointerArr ay< CCalEntry > &,T Int &);{} CCa.
Developers guidelines | Signing applications 78 October 2006 CContactDatabase::Re setServerSpeedDialsL();{} CContactDa tabase::SetCu rrentDatab ase(const TD esC &)const;{} CContactDatabase ::SetCu.
Developers guidelines | Signing applications 79 October 2006 CSmsHeader::Store L(CMsvStore &)const;{} CUnifiedCertS tore::Remove (const CCTCer tInfo &,TReques tStatus &);{Wr iteDeviceData}.
Developers guidelines | Signing applications 80 October 2006 RAgendaServ::Delet eTodoList(TAgn UniqueId);{} RAgendaServ::Delet eTodoListL(CAgnT odoList *);{} RAgendaServ::IncEnt ryRefCountL(const T Ag.
Developers guidelines | Signing applications 81 October 2006 RMsvServerSessio n::ChangeAtt ributesL(cons t CMsvEntrySele ction &,TUint, TUint);{} RMsvServerSessio n::ChangeEnt ryL(const TM svEntry.
Developers guidelines | Signing applications 82 October 2006 RPhoneBookSession::Can celRequest(TPhonebook SyncRequestCancel,TUid);{Read UserData} RPhoneBookSession::Dele teContact(TRequestS tatus &.
Developers guidelines | Signing applications 83 October 2006 MCTKeyStoreMa nager::Expor tEncryptedKe y(TCTTokenOb jectHandle,c onst CPBEncryptPa rms &,HBufC8 *&,TReque stStatus &)=0;{} MCT.
Ein wichtiger Punkt beim Kauf des Geräts Sony Ericsson UIQ 3 (oder sogar vor seinem Kauf) ist das durchlesen seiner Bedienungsanleitung. Dies sollten wir wegen ein paar einfacher Gründe machen:
Wenn Sie Sony Ericsson UIQ 3 noch nicht gekauft haben, ist jetzt ein guter Moment, um sich mit den grundliegenden Daten des Produkts bekannt zu machen. Schauen Sie zuerst die ersten Seiten der Anleitung durch, die Sie oben finden. Dort finden Sie die wichtigsten technischen Daten für Sony Ericsson UIQ 3 - auf diese Weise prüfen Sie, ob das Gerät Ihren Wünschen entspricht. Wenn Sie tiefer in die Benutzeranleitung von Sony Ericsson UIQ 3 reinschauen, lernen Sie alle zugänglichen Produktfunktionen kennen, sowie erhalten Informationen über die Nutzung. Die Informationen, die Sie über Sony Ericsson UIQ 3 erhalten, werden Ihnen bestimmt bei der Kaufentscheidung helfen.
Wenn Sie aber schon Sony Ericsson UIQ 3 besitzen, und noch keine Gelegenheit dazu hatten, die Bedienungsanleitung zu lesen, sollten Sie es aufgrund der oben beschriebenen Gründe machen. Sie erfahren dann, ob Sie die zugänglichen Funktionen richtig genutzt haben, aber auch, ob Sie keine Fehler begangen haben, die den Nutzungszeitraum von Sony Ericsson UIQ 3 verkürzen könnten.
Jedoch ist die eine der wichtigsten Rollen, die eine Bedienungsanleitung für den Nutzer spielt, die Hilfe bei der Lösung von Problemen mit Sony Ericsson UIQ 3. Sie finden dort fast immer Troubleshooting, also die am häufigsten auftauchenden Störungen und Mängel bei Sony Ericsson UIQ 3 gemeinsam mit Hinweisen bezüglich der Arten ihrer Lösung. Sogar wenn es Ihnen nicht gelingen sollte das Problem alleine zu bewältigen, die Anleitung zeigt Ihnen die weitere Vorgehensweise – den Kontakt zur Kundenberatung oder dem naheliegenden Service.