The following issues are consider "open", which means I have acknowledged their existence and I am presently searching for a solution:

 

Issue #	Status	Description
87	Added To V1.0.40	An experimental Make VoIP Call item has been added to the #s and Emails tab. If you have a working SIP configuration on your phone and you can presently make VoIP calls directly through the native phonebook, this option SHOULD allow that within ContactsEx. Please report on your success/failure with this feature, because I have no way to test it at my end.
86	Added To V1.0.40	When a contact was renamed, the Picture ID image and thumbnail were also supposed to be renamed, but a bug in the code that did the renaming used the wrong string to generate paths. This meant the file was not renamed. Subsequently the Picture ID image would disappear in the renamed contact.
85	Added To V1.0.40	Whenever any property of the name or label in a Fullscreen Picture ID is changed, all the properties for that item are made permanent and are not affected by changes to the defaults. You can return a name or label back to defaults with a new menu item found in both the name and label secondary menus on the Picture tab.
84	Added To V1.0.40	Previously the "Default" Picture ID was used to display a picture for all numbers that were in your phonebook, but didn't have their own Picture ID assigned, but it was ALSO used to provide the default settings for new pictures and supposedly (see issue #82) to provide default properties for all other pictures. I have now separated the two duties, so now there is a default setting and an In-Phonebook setting for displaying an Picture ID for contacts without their own.
83	Added To V1.0.40	Feature Pack 2 of S60 3rd Edition allows users to store reference to full-sized images. I have now added a new option in the Fullscreen Picture ID tab that allows you to assign the picture directly from the path stored in the contact (if one exists).
82	Added To V1.0.40	All position, font, and color properties of a Fullscreen Picture ID were SUPPOSED to retain reference to default values if they weren't changed explicitly. Subsequently if properties of the default values were changed, all the picture properties would change if they hadn't be set to a specific value. This paradigm wasn't followed correctly and so all picture properties became fixed-in-stone right after the picture was assigned.
81	Added To V1.0.40	When the Default Fullscreen Picture ID was CLEARED, the information stored into it wasn't correct and after that no name or label appeared on newly-defined Picture IDs. This has now been corrected by some major changes made to the scheme in issue #84.
80	Added To V1.0.39	The Alternate Selector (a program-provided dialog for selecting photographs from your gallery) crashes when it first starts up. This was a bug introduced in Build 36. This has now been fixed.
79	Added To V1.0.39	The setting that decides how long a Fullscreen Picture ID stayed on the display (until the call is answered, or until the call ends) was erroneously affecting Calling Card calls where "w" symbols were included in the dial string to insert "waits". The picture (or its green-screen stand-in when outgoing Picture ID isn't used) would disappear from the screen right after the call connected if you had the Picture ID duration set to wait only until a call was answered. I've modified the program so that this setting has no effect on Calling Card calls with "w" symbols.
78	Added To V1.0.39	Phone numbers that are entered with "p" or "w" symbols in them don't work the way you think they will. This is because "p" and "w" are used as part of the Touchtones. ContactsEx has been modified so that any material that follows the first "p" or "w" encountered in a phone number is automatically move to the Touchtones.
77	Added To V1.0.39	When a new Calling Card is added and is then used to make a call the log doesn't correctly show that call as having gone to the destination number. This problem goes away when ContactsEx is next shutdown and restarted, because the problem is caused by a failure to add the new calling card to the lookup table that the log uses to make the distinction between a regular call and Calling Card call.
76	Added To V1.0.39	The code for ensuring that you don't duplicate the name of a contact has needed updating since I added Company Name to the dialog for entering/editing a contact identity. As a result it was impossible to simply move a first name to company name without getting an error messages. Conversely it was possible to assign two contacts to the same name if one used a combination of first/middle/last names and the other used company name. This has now been corrected.
75	Added To V1.0.39	When a selective restoration is performed (to bring back only certain contacts) all of the Calling Cards are lost. By that I meant that their icons change from globes (or letters inside green squares) to the standard contact icon. Until Build 39 is released, the only solution is to select Assign as Card on each of your Calling Card contacts.
74	Added To V1.0.39	When a Number Format is edited (and then accepted or canceled) the tab bar will reappear even though you are supposed be inside an isolated dialog box. If cursor left or cursor right is pressed at that point, the Number Format dialog is abandoned. This doesn't cause any serious problems, but any changes made to Number Formats may not be correctly applied.
73	Added To V1.0.37	If you performed a selective restoration from a backup set, the contacts were reloaded an extra time for each group association in the contact that was replaced. This only occurred however if an original contact with the same name was replaced and that contact had group associations. This occurred because change messages are sent by the operating system for each group as it is removed from a contact prior to deletion.
72	Added To V1.0.37	If you deleted a contact that had group associations, the full contact list was reloaded for each group association in that contact. This occurred because change messages are sent by the operating system for each group as it is removed from a contact prior to deletion.
71	Added To V1.0.37	If you assigned a new Fullscreen Picture ID image to a contact and pressed SELECT to get a cropping rectangle, but then canceled the cropping rectangle and accepted the image, a panic occurred and shutdown the application. If you then restarted ContactsEx and went to the Picture tab for that contact, another panic would occur and the program shutdown again.
70	Added To V1.0.37	The Country Code Divider was supposed to default to a space if you left the field blank when creating or editing a Format, but this wasn't happening.
69	Added To V1.0.36	The Backup/Restore facility be expanded to include a new type of restore. You'll now be able to select individual contacts from a backup set and restore just them.
68	Added To V1.0.36	If you press the # key or Shift + Select to list only the Calling Cards, a panic will occur and the program will exit. This has been fixed in Build 36.
67	Added to V1.0.35	Since approximately Build 33 there has been a bug in the Groups tab. When the Options softkey was pressed a panic would occur and the program would exit. This has been fixed.
66	Added to V1.0.35	ContactsEx was not previously treating accents properly. I've now revamped the search engines (full search as well as T9/letter search) to treat all accented characters as though they were non-accented characters. So doing a search for Cafe also finds references to Café for example. If a contact's name is spelled Bétte, then typing 238 will find it in a T9 search.
65	Added to V1.0.35	Full backup and recovery functions have been added. You can now make a backup of EVERYTHING that ContactsEx does with the contacts database and restore to any saved backup. Backups can easily be moved to your PC, where they can be safely stored until needed.
64	Added to V1.0.34	When a new contact was renamed it did change its location in the names list to suit its new spelling. As with Issue #63, the newly-renamed contact wasn't discoverable with the T9 search on numeric keypad phones.
63	Added to V1.0.34	When a new contact was added, either directly from the menu on the Names tab, or from an unassigned number in the Log tab, the new name was not discoverable with the T9 search until the program was shutdown and restarted. This issue only affected phones with numeric keypads. QWERTY phones were not affected.
62	Added to V1.0.32	Over-the-air auto-update feature was finally activated, now that we have a self-signed copy. I also added a new setting (in the General tab) that allows you to select which version of the program to auto-update to. By default you'll get the signed version, but if you have a hacked phone that can install the unsigned version without complaint, then you can choose to auto-update this version instead.
61	Added to V1.0.32	Some of the new settings for multiple Calling Cards weren't being saved immediately after they were changed. This wasn't an issue if the program was closed gracefully, but if it wasn't (either due to a system crash or you powered off the phone) the changes wouldn't be there when the program was restarted.
60	Added to V1.0.31	The setting for incoming Full Screen Picture ID that was labeled "Contacts With Pictures" wasn't working correctly. This has been fixed.
59	Added To V1.0.31	Another thing I noticed while playing around with a borrowed N86 was that the newest firmware messes up the Full Screen Picture ID. After much experimentation I found that some delay was necessary before bringing the application to the forefront when an incoming call was detected. I've added a new setting to adjust this delay time.
58	Added to V1.0.31	An "acknowledged" bug in some FP2 versions made it impossible to access the MGFetch class that is needed to display available media files (used to get the picture for Full Screen Picture ID). Some bozo at Symbian added something to this code that tries to write a setting to the phone and ends up forcing the use of this otherwise ALLOWED class to need the WriteDeviceData capability. That means the use of this class can't be SELF-SIGNED on some versions of FP2 (but works on others, as well as all versions of FP1). At any rate, to get around the problem I have to write a crude filename selector that will kick in if MGFetch is disallowed on the phone.
57	Added to V1.0.31	Although I'd initially stated that I wouldn't add any new functionality to this Version 1 of ContactsEx, it has been made fairly clear to me that we really need the ability to select a different Calling Card for national and international long distance calling. The changes necessary for this shouldn't be that difficult and pose only a small risk to the stability of the code. I will therefore add this feature in Build 31.
56	Added to V1.0.30	The fix for issue #45 back in Build 27 created a problem with touchtones, in that simple touchtones (those without extra "w" or "p" symbols) would be transmitted twice. This applied to normal phone numbers with touchtones as well as Calling Cards.
55	Added to V1.0.30	When contacts are sorted by last name then first name, and a contact has only a last name, ContactsEx is still displaying the comma. No comma should appear when there is only one name, whether its just a first name or just a last name.
54	Added to V1.0.29	The field for entering touchtones was arbitrarily limited to 20 characters, but this has proven to be an issue for some people. As far as I can determine from the API documentation, there should be no inherent limit to the number of touchtone characters the program can send once a call is established, and so the size limitation will be removed as of Build 29.
53	Added to V1.0.29	When the program was being converted to work with a self-signed certificate I'd apparently commented-out the code that copied all of the Full Screen Picture ID images from one storage area to another when you changed ID storage from phone to mass memory or vise versa. I intended to rewrite the code using functions that could be self-signed, but it was forgotten and didn't make it into Build 28. I will fix this for Build 29.
52	Added to V1.0.28	Allow the assignment of multiple "Birthday", "Anniversary", "Spouse", "Children", and "Assistant" fields. Even though the native editor (in FP1 at least) doesn't allow this, the database does. I can only assume the editor disallowing this was an oversight.
51	Added to V1.0.28	Add support for "Department" in the Sundry tab. This field type was previously ignored by ContactsEx.
50	Added to V1.0.28	Add support for "Assistant's Name" to the Sundry tab, and add a new phone number type called "Assistant". This allows ContactsEx to support these two field types that it previous ignored.
49	Added to V1.0.28	Re-code the program so that it can be SELF-SIGNED, thus allowing the SIS file to be installed on any phone without the need to sign it by hand (as we've been doing until now).
48	Added to V1.0.27	I've added something new to the Contacts-narrowing feature. If you use "#" as the first symbol when narrowing your contacts, the list will contain only contacts designated as Calling Cards. You are then free to continue entering keys to refine the narrowing within that context. This makes selecting a different Calling Card much easier.
47	Added to V1.0.27	Contacts designated as Calling Cards get their own icons, but until now there was no indication which one of the cards was presently active. For that reason I have used another icon (a "D" is a green square, but I'll probably change it in the future) to denote the currently-active card.
46	Added to V1.0.27	I have revamped the way in which settings are saved to the INI file. Previously not all changes were saved the moment an option altered one, mostly because it was a bit time-consuming and thus it interrupted the flow. All changes to the INI file are now delayed until after the function that changes the settings has completed. The functions therefore execute quickly and saving the INI file is done while you're thinking of what you want to do next. ALL changes to settings are now saved after they are changed.
45	Added to V1.0.27	Calling Cards didn't previously allow multiple "w" symbols. Only the first wait request actually caused the dialing to wait. I have modified the dialing code so that you can include as many "w" symbols in the dial string as are required.
44	Added to V1.0.26	On NON-QWERTY phones, pressing the "#" key on the Names tab caused the T9 search to stop working. This is because the program switched to "QWERTY" mode by mistake. I've removed "#" as a key used to detect a QWERTY keyboard and has cleared up the problem.
43	Added to V1.0.26	There was no option to send an MMS or Audio Note directly to an email address. I have therefore made necessary modifications to support these features.
42	Added to V1.0.26	A means to manually dial a phone number (not in the phonebook) has been added. It can be used to dial the number directly, or through the Calling Card. Adding this broke the rules a little, because it constituted a "new feature" when I've said that I'm trying NOT to add anything new to the Alpha Test release. However, it was quite simple to implement, it didn't put any other parts of the code at risk, and it provided a very useful addition to the program.
41	Added to V1.0.26	The default value for the "Raw Threshold" option in the "Format" tab was initially 3, but it has been pointed out that this can often be problematic. A better value is 5, which should cover most non-phone number entries (like SMS short codes), but not be a problem for REAL phone numbers that will most likely be longer than 5 digits. The default value can always be changed by the user of course, but a default that causes the least trouble before its changed is a definite plus.
40	Added to V1.0.25	If a new contacted was added while CONTACT NARROWING was in effect the new contact didn't show on the screen (even if it matched the current narrowing criteria). I decided that a proper response from the program is to cancel the narrowing and display all contacts, with the newly-added contact highlighted.
39	Added to V1.0.25	When the Picture tab was selected IMMEDIATELY after a new contact was added, the program crashed. This was the result of not properly initializing the contact object at the time of creation. This has been fixed.
38	Added to V1.0.25	The SEARCH ALL option did not search the name field. I must have thought I had a reason for doing this, but since the option says it searches ALL of the fields, then that it should. I have modified this option to search ALL of the fields.
37	Added to V1.0.25	When a search was performed in which there were NO RESULTS, the program crashed if you then moved to the Picture tab from the empty result list. This issue has been addressed.
36	Added to V1.0.25	The cached images (2 for each contact with a full screen caller ID picture) were showing up in the phone's Gallery. I did some research into this and I found that HIDING the folders in which the cached images are stored would prevent them from showing up in the Gallery.
35	Added to V1.0.25	When an image was removed from a contact the cached files were not being removed from the file system. This has been corrected.
34	Added to V1.0.24	When there are no Groups assigned a crash occurs if you selected the Options softkey on the Groups tab. This was a result of not writing the code to account for a situation in which there were no groups. This has now been addressed and the only menu options that appear in this Tab when no Groups are assigned are Exit and Add New Group.
33	Added to V1.0.24	Testers have noted that they find it annoying that ContactsEx "forgets" where they were in the contacts list when the application is hidden. I've decided that because it isn't a big deal to add a user option to define how the application behaves when hidden, I will add that to the program for the Build 24 release. It shouldn't pose any stability problems or create new bugs.
32	Added to V1.0.24	When storing a phone number NOT in your country and you have set the program to suppress country codes, the number stored to the phone is WRONG. The program was removing the country code even when the phone number wasn't in your country. This has been fixed
31	Added to V1.0.24	Phone numbers stored with the country code, but without a "+" symbol in front, weren't being correctly recognized. This situation is common in phone numbers stored on North American phones. Many people put long distance numbers into their phonebooks with just a "1" in front of them, rather than "+1".
30	Tested in V1.0.23	Syncing operations seem to produce an endless loop of reloading the contacts. This can only be stopped by shutting down the process. I was unable to duplicate this problem at my end, and so I had a look at the code and I found what I BELIEVE is a solution. However, until that had been confirmed by the tester who reported the original program, this issue REMAINS OPEN.
29	Added to V1.0.23	Long ago I added a restriction to the characters that were allowed in a label, but I was apparently very heavy-handed just to be sure. However, I've since learned that virtually all characters are legal in a label, and so the limitations are unnecessary. I've removed most of the limitations, but because I use certain characters for delimiters, I still restrict commas, semicolons, equal signs, tildes, and pipes. Also, you can't use parentheses in Address labels, because these are used by Symbian in the default labels.
28	Added to V1.0.23	When a line of an address or a note must be wrapped, scrolling didn't work right. The scrolling was based on the unformatted line rather than the way it appears on the screen. As with issue #27, you may not have noticed this if you didn't have contacts with enough notes or addresses to require scrolling.
27	Added to V1.0.23	It was brought to my attention that the Addresses and Notes tabs do not have scrollbars. You may not have noticed this because you my not have entered enough notes or addresses in any one contact to fill a screen. I've now added scrollbars to these tabs to maintain a consistent UI across the board.
26	Added to V1.0.23	I did a little investigating into the Symbian APIs and I noticed that it's possible to reverse the font sizes in a 2-line listbox. This makes perfect sense for the #s & Emails tab as well as the Sundry tab. The phone numbers, emails, and other sundry data are far more important than the labels, and so I've swapped the font sizes in those two lists.
25	Added to V1.0.22	It was quickly discovered that the updating of the phonebook when a country code or area code was changed. Build 22 fixes this by speeding up the process quite radically.
24	Added to V1.0.20	During testing to solve issue #1 it was also discovered that the contacts list was being reloaded under a number of different circumstances. I have therefore re-coded the program so that a re-load of the contacts is now only necessary when an external program changes data in your contacts, or when you change a contact using the "Native Editor" option. Functions that are now free of this requirement, and are subsequently MUCH FASTER are: Add a new Contact, Rename a Contact, Delete a Contact, add a number from the Log to a new Contact entry.
23	Pending	It has been pointed out to me that ContactsEx should support a way to allow the SELECT (OK) button to behave the way it does in the native contacts manager. I will therefore be adding a new option to let you choose how the SELECT buttons behaves. If you like it the way it is, you'll have the option of keeping it that way.
22	Added to V1.0.20	During testing to solve issue #1 it was discovered that some people have very large contacts lists (well in excess of 1000 contacts). Because of this the load time is too long to have no opening splash screen. Contacts are now loaded once the U/I is visible and a progress bar reports how things are going.
21	Added to V1.0.19	Although I fixed the problem of contact names not appearing in SMS (issue 13) I failed to fix it for sending SMS to a Group. I have now fixed that problem and it applies equally to MMS and Audio Notes (issue 12).
20	Added to V1.0.19	Private Calls (those without any known caller information), and numbers not in the phonebook, were being displayed in the Call Log with the icon of whichever phone number came before it. They should have contained a standard "phone" icon.
19	Added to V1.0.19	Calls made through a Calling Card aren't correctly formatted in the Call Log. This was an oversight created when I made recent changes to support universal number formatting.
18	Added to V1.0.19	Created smaller icons of the Home and Office icons for display on the right-hand side of the Call Log. Apparently S60 only allows a 15 x 15 icon on this side of the listbox and an 18 x 18 on the left.
17	Added to V1.0.18	I've updated the Send SMS option from Contacts tab to follow the logic used when sending an SMS to all contacts in a Group. The Send SMS option will only appear if the contact has a number designated as "Mobile" or "Car". When an SMS is sent in this way the program first checks the default number to see if it is "Mobile" or "Car". If not, it finds the first number that is, based on the sort order you have chosen for the numbers in that contact. You can still attempt to send an SMS to a non-cellular number by choosing the option from the #s & Emails tab.
16	Added to V1.0.18	Changing the default number in a contact did not update the icon next to the name in the Contacts tab. This oversight has been corrected.
15	Added to V1.0.18	I've been informed by one of my testers that his provider set his billing date on the 29th. I was rather surprised to hear this, because the provider creates a problem for themselves by needing to deal with the issue of non-leap year Februarys. If you select the 29th as the day on which your billing cycle begins, then on non-leap years the billing cycle will begin on March 1st (since there is no February 29th).
14	Added to V1.0.18	I've now added a 4th display mode to the Calls Log. In this mode the name of the contact is displayed and then an icon (representing type designated in the contact) is displayed on the right side of the screen. Also, display mode can now be set from a menu item, or by pressing the numbers 1, 2, 3, or 4 (in addition to the old way of cycling through the modes with the # key.
13	Added to V1.0.18	It was pointed out to me that I wasn't applying an alias to the address to which SMS were being sent. This meant that the "TO" field in the SMS had just the number it was going to, rather than the name of the contact. I've now fixed this and I provide both the name and the label (in parenthesis).
12	Added to V1.0.19	I've added support for MMS and Audio Notes. This applies to individual contacts, as well as groups of contacts. It was always my intention to provide all of the same options as the native contacts manager, but since I never used MMS or Audio Notes (the latter being a specialized type of MMS anyway) I didn't get around to it yet. That has now been remedied.
11	Will be in V1.0.20	I have change the embedded name of the program from "ContactsEx_0xE84D5217" to just "ContactsEx". This name appears in some applications that show the names of menu items.
10	Added to V1.0.18	I have recently learned that the syncing allows phone numbers to be entered with various non-numeric characters. I was handling spaces and hyphens under the false assumption these were the only characters allowed in numbers. As a result, build 16 cannot dial numbers that contain non-numeric symbols other than space or hyphen. I will update the pre-processor to ignore all non-numeric characters in phone numbers.
9	Being Researched	A number of testers have asked if it's possible to use the exiting thumbnail images for full screen picture ID. I don't personally believe these images have enough resolution to be useful, but in the interests of researching this thing properly, I will write code to extract one of these images and scale it up in size. I'll then post it to all the testers and we'll take a vote.
8	Added to V1.0.18	There was still a problem related to blank contacts showing up. After hours of working with one my testers we determined that this occurred when a contact had no name at all (no first, middle, last, or company name). In the native contacts manager these appear as "[unnamed]" and are sorted to the bottom of the list. I've fixed ContactsEx to do the same thing. This fix will available in the 1.0.18 release.
7	Added to V1.0.16	The menu items for switching between 1-line display and 2-line display in the #s & Emails tab is BACKWARDS (its says 1-line when it means 2-line and vise-versa). This trivial issue has been correct in build 16.
6	Added to V1.0.21	It was brought to my attention that ContactsEx had a serious omission. I needed to support Area Codes, which was absolutely necessary for countries such as Australia and for parts of North America where 7-digit dialing is still allowed. This was the single largest change made to the alpha test version of ContactsEx, but it was deemed NECESSARY in light of the problems it created in those two countries. I could only assume that other countries could easily have faced a similar problem.
5	Added to V1.0.16	When default Full Screen Picture IDs are left undefined they don't correctly function when a call comes in. Instead of staying out of the way and allowing the phone to behave as it always did, they instead display the words "No Picture" in the middle of the screen. This incorrect behavior has been corrected in build 16.
4	Being Researched	At least one tester with an E71-2 reported that the search (mentioned in issue #1) wasn't a problem, but he reported that his phone became extremely sluggish after ContactsEx was hidden. Please contact me if you experience this problem as well.
3	Added to V1.0.16	The blank contacts issue has been identified. Apparently the S60 platform allows contacts to have no first, middle, or last name, so long as a Company Name is provided. I was NOT AWARE of this. Now that I am a new version of the program is being readied. This issue has been corrected in build 16.
2	Being Researched	Thumbnail images from the native contacts application are not copied over. I'm fairly certain that the contacts database engine ONLY stores thumbnail images, though it has been suggested to me that it might store a link to the original source image. Until I have confirmed this one way or another I'll refer to this as an open issue.
1	Added to V1.0.20	Some testers reported very sluggish performance when typing keys at the Names tab to search for a contact. I couldn't duplicate the problem on my N95, and so I focused on what was different when the program was used with a QWERTY keypad. I discovered some rather sloppy programming in which the QWERTY Flag was being reset to true each time an alpha key was pressed. This included saving the entire user preferences file back to the file system. On some phones this was really slow. I solved the problem by only resaving the file if the flag needed to be change.