NewLC - Comments

Eclipse plug-in for Symbian C++ development

dsnathan6 — Fri, 09 May 2008 15:45:43 +0200

Want to develop 3rd party simbain application on the vc or eclips environment, request to provide information on the same.

Re: Reading ZIP File in Symbian OS

zlatan24 — Fri, 09 May 2008 11:14:13 +0200

Use-damaged zip files,program supports Windows 98, Windows Me, Windows NT 4.0, Windows 2000, Windows XP, Windows XP SP2, Windows 2003 and Windows Vista,help users solve the zip recovery issues and always have control of their archived data,recovers information from damaged zip files and minimizes data loss during the zip recovery process,application is the fact that it employs several heuristic algorithms and methods to repair zip file or recover information from damaged zip files.

Re: LEAVE and TRAP

kavitha2085 — Fri, 09 May 2008 10:45:34 +0200

Great explanation with extreme clarity......... Thank you very much

Re: UIQ3 audio streaming with code

lori_c — Fri, 09 May 2008 09:31:58 +0200

hi,
I have got KErrPermissionDenied in MaoscBufferCopied when I play the auido, Why?

Re: FirstGps N95 error "unable to install" installind FirstGps

marciallus — Mon, 05 May 2008 09:35:18 +0200

When i wrate this tutorial it was just to present the symbian LBS API , It wasn't designed to be use as is in a real program.

For your sis problem, you can check this url : http://www.newlc.com/Why-the-fuck-won-t-my-SIS-file.html

--
MarCo

Re: Penrillian uSTL now supports Series 60 3rd Edition

JavaCS — Fri, 02 May 2008 06:26:35 +0200

The two libs are both useful, and I tried to use ustl in S60 2nd Ed with some modification/ replacing, and it works well. But I think STLport/Symbian will not work because of the need of P.I.P.S.

But ustl is not very the same with STL, and no iostream etc. I think STLport may be the best choice for Symbian OS 9.x, and we can use it as a static lib, then it maybe not increase too much size of the final sis when we only use a small part of STL.

Re: Nokia Series 60 Firmware History - 7610

paul864369 — Thu, 01 May 2008 18:45:29 +0200

were can i get firmware for my 7610?

FirstGps N95 error "unable to install" installind FirstGps sis

christian le jalle — Wed, 30 Apr 2008 18:57:55 +0200

Hi ,

I have signed "fistGps " app with symbiansigned WEB,
after adding capabilities Location and ReadUserData , got a new sis file.
but installation of the signed sis file on N95 failed "unable to install"
work fine on Emulator
I have upgraded my N95firmwrar to the latest release. didn't fixed
Sounds it's coming from my Pkg file ?
I have created one with the following contents:

; Installation file for FirstGps example application
;
;Languages
&EN
;
; UID is the app's UID
;
#{"FirstGps"},(0xE1EF0018 ),2,0,0
;Supports Series 60 v 3.0
[0x101F7961], 0, 0, 0, {"Series60ProductID"}
%{"Forum Nokia Test EN"}
:"Forum Nokia"
;

; Four files to install
;
"$(EPOCROOT)\Epoc32\release\$(PLATFORM)\$(TARGET)\FirstGps.exe"-"!:\sys\bin\FirstGps.exe"
"$(EPOCROOT)\EPOC32\data\Z\resource\apps\FirstGps.rsc"-"!:\resource\apps\FirstGps.rsc"
"$(EPOCROOT)\EPOC32\data\Z\private\10003a3f\apps\FirstGps_reg.RSC"-"!:\private\10003a3f\import\apps\FirstGps_reg.rsc"
"$(EPOCROOT)\Epoc32\data\z\resource\apps\FirstGps.mif" -"!:\resource\apps\FirstGps.mif"

-
Run with no error .
I'm wondering what I'm doing wrong ???

I have also used the FirstGps classes in another application. worked fine on emulator
but crashed on the "live" N95 when calling the GPS function ....

Any help and suggestion will be appreciated
Christian

Re: Moremedia - The audio video player for S60 mobile phones

thediveal — Mon, 28 Apr 2008 15:53:44 +0200

good very good

Re: Hardware and Software Debugging

rakeshjhaa — Sat, 26 Apr 2008 10:31:42 +0200

problem is make temp file other place exe dektop,D &c drive & other folder
please solution this problem

Re: Penrillian uSTL now supports Series 60 3rd Edition

Guru_Meditation — Fri, 25 Apr 2008 12:34:10 +0200

Quite so, but there's at least one relevant difference. STLport/Symbian requires P.I.P.S. that Penrillian/uSTL does not. I know that P.I.P.S will be pre-installed on the newer phones, but at the moment using STLport requires the user to install a 463 kB .sis packet that Penrillian/uSTL doesn't seem to require.

Re: Base64, Quoted Printable and UU Encoding and Decoding

eric — Fri, 25 Apr 2008 11:15:00 +0200

There are quite straightforward to use:

HBufC* escapedText=EscapeUtils::EscapeEncodeL(mySourceText,EscapeUtils::EEscapeNormal);
CleanupStack::PushL(escapedText);
...
// Do whatever you want with the escaped text
...
CleanupStack::PopAndDestroy(escapedText);

Re: > Writing a recognizer: The EZBoot recognizer source code

shravan_vip — Fri, 25 Apr 2008 07:33:18 +0200

Can u please help me in step by step procedure of " Autostarting an application"

My code is follows

#include
#include
#include "QuickStart.h"
//#include "C:\CWEx\ActiveObjs\ActiveDll\ActiveDll.h"

const TUid KUidemAMRec={0x0EBC2E40};

CMyRecognizer::CMyRecognizer()
:CApaDataRecognizerType(KUidemAMRec, CApaDataRecognizerType::ENormal)
{
iCountDataTypes = 1;
}

TUint CMyRecognizer::PreferredBufSize()
{
// no buffer recognition yet
return 0;
}

TDataType CMyRecognizer::SupportedDataTypeL(TInt /*aIndex*/) const
{
return TDataType();
}

void CMyRecognizer::DoRecognizeL(const TDesC& /*aName*/, const TDesC8&
/*aBuffer*/)
{
// this function is never called
}

void CMyRecognizer::StartThread()
{
TInt res = KErrNone;
//create a new thread for starting our application
RThread * startAppThread;
startAppThread = new RThread();

User::LeaveIfError( res = startAppThread->Create(
_L("MyThreadName"),
CMyRecognizer::StartAppThreadFunction,
KDefaultStackSize,
KMinHeapSize,
KMinHeapSize,
NULL,
EOwnerThread) );

startAppThread->SetPriority(EPriorityNormal/*EPriorityLess*/);
startAppThread->Resume();
startAppThread->Close();
}

TInt CMyRecognizer::StartAppThreadFunction(TAny* /*aParam*/)
{
/*
//wait 5 seconds...
RTimer timer; // The asynchronous timer and ...
TRequestStatus timerStatus; // ... its associated request status
timer.CreateLocal(); // Always created for this thread.
// get current time (microseconds since 0AD nominal Gregorian)
TTime time;
time.HomeTime();
// add ten seconds to the time
TTimeIntervalSeconds timeIntervalSeconds(50);
time += timeIntervalSeconds;
// issue and wait
timer.At(timerStatus,time);
User::WaitForRequest(timerStatus);
*/

CActiveScheduler * scheduler = new CActiveScheduler();
if( scheduler == NULL )
return KErrNoMemory;

CActiveScheduler::Install(scheduler);
// create a TRAP cleanup
CTrapCleanup * cleanup = CTrapCleanup::New();
TInt err;
if( cleanup == NULL )
{
err = KErrNoMemory;
}
else
{
TRAP( err, StartAppThreadFunctionL() );
}
delete cleanup;
delete CActiveScheduler::Current();
return err;
}//StartAppThreadFunction

void CMyRecognizer::StartAppThreadFunctionL()
{

/* CActiveDll* iActiveDll;
iActiveDll = CActiveDll::NewLC();
iActiveDll->ShowMessage();*/

TFileName fnAppPath = _L("E:\\system\\Apps\\AppUidViewer\\AppUidViewer.app");
RFs fsSession; //file server session
User::LeaveIfError(fsSession.Connect());
CleanupClosePushL(fsSession);
TFindFile findFile( fsSession );

User::LeaveIfError( findFile.FindByDir(fnAppPath, KNullDesC) );

CApaCommandLine* cmdLine = CApaCommandLine::NewLC();
cmdLine->SetLibraryNameL( findFile.File() );
cmdLine->SetCommandL( EApaCommandOpen );

RApaLsSession ls;
User::LeaveIfError(ls.Connect());
CleanupClosePushL(ls);

User::LeaveIfError( ls.StartApp(*cmdLine) );
CleanupStack::PopAndDestroy(3); // Destroy fsSession, ls and cmdLine
}//StartAppThreadFunctionL

EXPORT_C CApaDataRecognizerType* CreateRecognizer()
{
CApaDataRecognizerType* thing = new CMyRecognizer();
//start thread for our application
CMyRecognizer::StartThread();
return thing;
}

// DLL entry point
GLDEF_C TInt E32Dll(TDllReason /*aReason*/)
{
return KErrNone;
}

As you have said I have downloaded and installed the ezboot.sis into my N72 phone. Please explain me the remaining steps.

Iam getting canfused as to How to create .boot file and .mdl and their targets. Please explain me briefly. Whether it works on N72.

Re: Symbian and Windows on the same device - what the hell?

twmd — Wed, 23 Apr 2008 12:07:00 +0200

>> without the need to modify the existing modem software".

That was my point exactly.

Cost is the chief driver for one chip - but people often underestimate the cost of modifying and maintaining a complex platform. Software asset reuse is massively important to a big company because hardware can be swapped quicker than software these days.

On top of that. Real time programming/embedded programming is distinct engineering discipline - often clouded by the fact that many developers who have written mobile apps classify themselves as embedded programmers.

The other way of doing singe chip it is to introduce a personality layer. This essentially provides a library of mutexes, threads etc which emulates an incumbent RTOS allowing for compilation of the signaling stack and test code on top of another OS.
The disadvantage of personality layer is that you need one for each OS, and each has to be carefully verified.

Here are some examples of typical layouts:

- The first Symbian phone which I worked on had RTOS and Symbian running on a single chip (back in 1999). Series 40 devices tend to run everything on the RTOS, but "open" OSes rarely attempt to run signaling stacks.

- The iPhone is 2 chip. It has a 2.5g daughter board which could be switched for 3G without having to modify the main ARM11 cpu.

- Freescale's MXC reference design is single chip, but runs most of the signaling stack on a starcore DSP.
http://www.freescale.com/files/wireless_comm/doc/fact_sheet/3GREFDESIGNFS.pdf

When you start adding real time multimedia, virtual memory paging (by nature undeterministic) and a product which is assembled from many many partner deliveries, it takes an enormous amount of effort to verify the integrity of an entire system.

In summary. One chip, one OS is not a synonym for "best solution", like all engineering, the best solution takes into account cost, skillset, organizational factors, complexity, reuse and ROI.

I wrote a bit more about it in context here:
http://twmdesign.co.uk/theblog/?p=104

Re: Symbian and Windows on the same device - what the hell?

tote — Wed, 23 Apr 2008 11:25:18 +0200

As far as I know the reason for device manufacturers and Symbian to maintain the separation between the RTOS and the Application OS is that device manufacturers want to protect their IPRs and their home-brew GSM stacks. I'm not sure if there is a Symbian GSM stack, as such, and even if it does exist if any device vendors have taken that into use.

What I can read, though, from VirtualLogix VLX introduction is that there would be a single comms stack, which they would provide: "... Enables the use of a rich OS on a single ARM core architecture without the need to modify the existing modem software".