Contacts Memory Allocation

Login to reply to this topic.
Fri, 2006-02-03 01:28
Joined: 2005-07-22
Forum posts: 21
Hi I am making an application that involves editing the fields inside a contact Item.

During the process of testing that application, I found out that each time you edit a contact, 1kB approx is added to the memory allocation of the contact.  For example, I add a ringtone to the contact, it moves from 8kb to 9kb. Then surprisingly, if I delete the ringtone, it moves from 9kb to 10kb. Hence, by doing this to all the contacts, the memory of the phone overloads because i am adding 500kb for each run and i have no way of recovering the memory eaten up Shocked

Is this really the case? Or is my phone mem not functioning well?

This is true even if i edit the contacts using the default phone contacts application.  Huh

Any thoughts or comments are welcome.

I hope someone will help me verify this. Btw, I am using a nokia 6600.




Mon, 2006-02-06 00:14
Forum Nokia Champion
Joined: 2003-06-10
Forum posts: 720
Re: Contacts Memory Allocation
Perhaps the Symbian SDK docs describing "space reclamation and compaction", "RStoreReclaim", "ReclaimL", "CompactL", "RDbDatabase::Compact()" help explain the behaviour.
Mon, 2006-02-06 07:01
Joined: 2005-07-22
Forum posts: 21
Re: Contacts Memory Allocation
Thank you very much. Your reply is highly appreciated. I will go over these documents.


Thanks!
Mon, 2006-02-06 07:54
Joined: 2004-10-12
Forum posts: 44
Re: Contacts Memory Allocation
If I remember correctly, there are some problems with 6600. Meaning that the contacts database only grows. The methods mentioned above did not work for me at least. Even after deleting the items and "Compacting" the database, the size of the file remained the same. What worked was deleting the file and creating a new, but this is not a solution in most cases.
Mon, 2006-02-06 10:38
Joined: 2005-03-21
Forum posts: 45
Re: Contacts Memory Allocation
Hi,

Can you please tell me how to assign a Ringtone/Picture ID to a contact.

Thanks,
Prabhu.
  • Login to reply to this topic.