×

Discussion Board

Results 1 to 8 of 8
  1. #1
    Regular Contributor
    Join Date
    Sep 2008
    Posts
    82

    Exclamation Working on emulator but not on the phone!!!

    Hello

    I'v developped somme application who notify events added to the log engine data base and stor some of there caracteristics on a data base.
    all works fine on the emulator,but not on the device.

    Am working on an N95 with FP1,there is some of my code

    Observeur.h:

    Code:
    class MObserveur:public MLogViewChangeObserver
    {
    ...
    }
    Journal.h

    Code:
    class CJournal:public CActive,public MObserveur,public MObserveurPeriode
    	{
    ...
    
    private:
    	CObserverBDDJournal* iObserverBDDJournal;
    ...
    }
    Journal.cpp

    Code:
    void CJournal::ConstructL()
    	{
    	iObserverBDDJournal = CObserverBDDJournal::NewL(*this);
    ...
    	CActiveScheduler::Add(this);
    
    }
    
    void CJournal::RunL()
    	{
    	}
    
    void CJournal::HandleLogViewChangeEventAddedL(TLogId, TInt, TInt, TInt)
    	{
    	iObserverBDDJournal->PositionerL();
    	}
    
    void CJournal::StartL()
    	{
    	TRequestStatus *pS=&iStatus;
    	User::RequestComplete(pS,KErrNone);
    	SetActive();
    	}
    
    LOCAL_C void MainL()
    	{
    
    	CJournal* journal = CJournal::NewL();
    	CleanupStack::PushL(journal);
    	journal->StartL();
    	CActiveScheduler::Start();
    	CleanupStack::PopAndDestroy(journal);
    
    	}
    
    LOCAL_C void DoStartL()
    	{
    	// Create active scheduler (to run active objects)
    	CActiveScheduler* scheduler = new (ELeave) CActiveScheduler();
    	CleanupStack::PushL(scheduler);
    	CActiveScheduler::Install(scheduler);
    
    	MainL();
    
    
    	CleanupStack::PopAndDestroy(scheduler);
    	}
    
    GLDEF_C TInt E32Main()
    	{
    	// Create cleanup stack
    	__UHEAP_MARK;
    	CTrapCleanup* cleanup = CTrapCleanup::New();
    
    
    	// Run application code inside TRAP harness, wait keypress when terminated
    	TRAPD(mainError, DoStartL());
    
    	delete cleanup;
    	__UHEAP_MARKEND;
    	return KErrNone;
    	}
    ObserverBDDJournal.h

    Code:
    class MObserver;
    
    class CObserverBDDJournal:public CActive
    	{
    ...
    	CLogClient* iClientJournal;
    	 
    	CLogViewEvent* iJournalView;
    
    	CLogFilter* iFiltreVide;
    
    	MObserver& iObserver;
    ...
    }
    ObserverBDDJournal.cpp

    Code:
    CObserverBDDJournal::CObserverBDDJournal(MObserver& aObserver):CActive(EPriorityStandard),iObserver(aObserver)
    	{
    	CActiveScheduler::Add(this);
    	}
    
    void CObserverBDDJournal::ConstructL(MObserver& aObserver)
    	{
    	User::LeaveIfError(iSessionSysFichier.Connect());
    	
    	iClientJournal = CLogClient::NewL(iSessionSysFichier);
    	
    	iJournalView = CLogViewEvent::NewL(*iClientJournal,aObserver);
    
    	
    	iFiltreVide = CLogFilter::NewL();
    
    	
    	InitialiserBDDL();//Data Base File and table creation
    	
            InitialiserPacketL();	
    
    	InitialiserFilterL();
    
    	}
    
    void CObserveurBDDJournal::InitialiserFilterL()
    	{
    	Cancel();    
    	TBuf<20> direction;
        
            iClientJournal->GetString(direction, R_LOG_DIR_OUT);
            iFiltreVide->SetDirection(direction);
    	iEtat = EPositioner;
    	if(iJournalView->SetFilterL(*iFiltreVide,iStatus))
    	SetActive();
    	}
    
    void CObserveurBDDJournal::RunL()
    	{
    	switch(iEtat)
    		{
    		case EPositioner:
    			{
    			PositionerL();
    			break;
    			}
    ...
    		case EInserer:
    			{
    			InsertionL();//open Data Base and add Event details in the table
    			if(iJournalView->PreviousL(iStatus))
    				{
    			    SetActive();
    				}
    			else
    				{
    				Fermer();
    				iEtat = EnAttente;
    				}
    			break;
    			}
    		case EnAttente:
    			break;
    		default:
    			break;
    		
    		}
    	}
    
    
    void CObserverBDDJournal::DoCancel()
    	{
    	iJournalView->Cancel();
    	}
    
    void CObserverBDDJournal::PositionerL()
    	{
    	Cancel();
    	SometL();//To get the id of the last event add
    	if (id == 0)//id :ID of the last event add,if the table is empty then id = 0 
    		{
    		iEtat = EInserer;
    		if(iJournalView->LastL(iStatus))
    			SetActive();	
    		}
    	else 
    		{
    		iEtat = EChercher;
    		if(iJournalView->FirstL(iStatus))	
    		SetActive();	
    		}		
    	}
    When i debug it on device it stoped after complete executing EPositioner and getting out of the switch,and after maby 5 or 6 min it resume and stop again after executing EInserer,and am wating for if ,what wil happend.

    i need help please.

    Thank you.

  2. #2
    Nokia Developer Moderator
    Join Date
    Mar 2003
    Location
    Lempäälä/Finland
    Posts
    29,144

    Re: Working on emulator but not on the phone!!!

    Can you see whther you get any error's anywhere when executing it ?

    Also see epocwind.out for any missing capabilities reported while running it in the emulator.

  3. #3
    Regular Contributor
    Join Date
    Sep 2008
    Posts
    82

    Re: Working on emulator but not on the phone!!!

    Thank u symbianyucca

    i Will see for your sugession,but the problem that it's executed very very sloly,i steel leting it debegin and after another 6 mn it execute anothere EInsere...???

    Thank u.

  4. #4
    Regular Contributor
    Join Date
    Sep 2008
    Posts
    82

    Re: Working on emulator but not on the phone!!!

    Hi
    Did u mean this:
    Code:
        89.250	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.250	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.255	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.255	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.275	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.280	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.285	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.290	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.300	CNspsWsPlugin::Command( aOpcode:5
        89.315	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.330	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.340	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteUserData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.355	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.360	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.360	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.360	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.365	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.365	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.370	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.370	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.375	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: ReadDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
        89.375	*PlatSec* WARNING - Capability check would have failed - A Message (function number=0x00000008) from Thread Journal.exe[e9ab42e7]0001::Main, sent to Server !LogServ, was checked by Thread LogServ.EXE[101f401d]0001::LogServ and was found to be missing the capabilities: WriteDeviceData .  Additional diagnostic message: This diagnostic message does not indicate an error, please ignore it
    i get it in FP2 emulator output because nothing is writen with the FP1

  5. #5
    Nokia Developer Moderator
    Join Date
    Mar 2003
    Location
    Lempäälä/Finland
    Posts
    29,144

    Re: Working on emulator but not on the phone!!!

    Yep those are the ones I meant, so make sure you have all capabilities that are reported in the list added to your mmp file, then clean & re-build the executables and try again in the device.

  6. #6
    Regular Contributor
    Join Date
    Sep 2008
    Posts
    82

    Re: Working on emulator but not on the phone!!!

    Hi

    It was the problem ,i had to add in my mmp file
    Code:
    SECUREID    0xE...//my application UID
    CAPABILITY  ReadUserData WriteUserData WriteDeviceData WriteDeviceData
    thank u very much

  7. #7
    Regular Contributor
    Join Date
    Sep 2008
    Posts
    82

    Re: Working on emulator but not on the phone!!!

    Hi

    Just onother question,is it possiblity to mention this topic as solved???

    Thank u

  8. #8
    Nokia Developer Moderator
    Join Date
    Mar 2003
    Location
    Lempäälä/Finland
    Posts
    29,144

    Re: Working on emulator but not on the phone!!!

    I have not seen such an option in this Dibo yet, thus I would assume that it is not possible.

Similar Threads

  1. Recent call log not working on phone
    By yogi-am in forum Symbian
    Replies: 21
    Last Post: 2009-09-01, 15:13
  2. app working in default gray phone not woking in default colour phone
    By josephcarmel in forum Mobile Java General
    Replies: 5
    Last Post: 2009-03-25, 10:07
  3. help, write to commdb in 3rd edition working on emulator but not on phone..
    By tomasz.florczak in forum Symbian Networking & Messaging (Closed)
    Replies: 2
    Last Post: 2006-08-28, 12:11
  4. Nokia Image Converter
    By davidpurdie in forum General Development Questions
    Replies: 0
    Last Post: 2004-02-18, 15:31

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •