Mobile Guard lets you access the entire C: drive, including the protected C:\Private and C:\Sys directories (view only), which is more than Xplore can do. Any other suggestions I'd have would just be more clumsy subsets of trying Guard's Analyse Storage. Please give it a try.
2011-10-24 21:30 - edited 2011-10-24 21:34
The Private directory on my E73 is only 21.2 MB, so you're now making progress. Both Private and Sys (and some other files, too) are protected by the OS, so you can't delete anything there without hacking the phone. Think of Private as similar to the Windows registry, so even then you'd want to be very, very careful. What you can do is go through the (admittedly dozens of) directories in Private to find exactly where the issue lies. Perhaps record every directory larger than 5 MB...but I think the bulk of that 94.6 MB will be in one place. From the directory name and its contents, we should be able to deduce what it does and then hopefully find a fix.
At this point, though, you may want to take stock of what's on your phone. Do you have lots of email messages, large attachments, text messages, photos, etc., stored there? They would all live in Private. The phone also stores a pictures database there. I don't know if Calendar or Contacts data could run up Private that much, but keep them in mind, too. Some comments above (?) also mention Bluetooth file transfers. If you think temporarily reducing the number of emails synced to your phone, removing an email account you rarely use, temporarily removing an unusual 3rd party program, etc., might have an effect, then give it a try. Otherwise, please check the numbers.
Addendum: calendar, contacts, and messages aren't typically counted as part of "Other Files", so the fix probably isn't so straightforward...
2011-10-26 9:12 - edited 2011-10-26 9:13
102072C4 reserved 19.1 MB
Did you notice the "FotaState" file in this directory? This one appears to have files for managing firmware updates through the phone's "SW Update" app. The date stamp on each of my files (Options -> Attributes) matches (mostly) the "Latest Update" time on the *#0000# "software version" screen. So these files are affected only when SW Update actually installs new firmware. My "reserved" file is 976.6 K. Short of trying a *#7780# soft reset, I can't think of a solution, besides waiting for the next firmware update. Probably leave this alone for now.
20003c0a Inbox_w.db 33 MB
20003c89 Settings_1_V_1_1.db 12.5 MB
Both directories are part of Nokia Email. I assume you use Nokia Messaging for at least one of your four accounts? The Nokia Messaging service is disabled on my E73, and my email is stored in a different directory, hence the question. (This also puts me at a disadvantage, as I can't test anything here myself.) Is there just one file that starts with "Inbox" and ends with ".db"? If so, this appears to be a shared database for all four mailboxes. I am also surprised at the size. The 12.5 MB Nokia Messaging "settings" file makes even less sense. Mine (unused?) is 10.9 K.
My advice is to delete your mailboxes, one at a time, and see if that affects the file size. If removing the first one has no effect, you may or may not wish to continue. Before quitting, force the .db file to update by sending yourself an email, and then check again. If re-adding the mailbox makes either file even larger, that would also be good to know. When you check Options -> Details -> Memory for the Phone Memory in Nokia's File Manager, does the size of "Messages" suggest anything is awry? I would need to check again here, but I believe mine counts both SMS and Email stored on the phone. It would be interesting if it failed to count email pushed through Nokia Messaging, or this huge email database. A soft reset might also help, but save that for last. Might you have a "Refresh All" option somewhere in your Nokia Email settings? What if you log in through http://email.nokia.com ? (I don't see a login option any more, but perhaps you see something different?) If refresh isn't an option, then I wonder if Nokia Tech Support has any interactive control over Nokia Messaging? Basically, I'd like a way to flush and rebuild these files from scratch, but am not sure how to go about it. If nothing above helps, I may have one other idea, though...
Let me know what you find.
I suggested a software update without Traveler , Font magnifier ... . I hope that nokia will do it for us !!!
I just skimmed the comments above again, but can't tell if we've fixed anything yet. Is the "Phone Memory = 104.5 MB" an improvement or not? "Synchronize All" wasn't the option I was looking for. There is a way to tell Nokia Messaging to "Rebuild All", i.e. to flush most (and hopefully all) server-controlled files and rebuild them from scratch. (Trust me, hehe.) I just have to see if it's a feature that either we or Nokia Support can easily access. Gimme a day or two...
Thanks a lot for your help....will surely wait for your reply....till then I will not reconfigure any of my mailboxes again....and no the phone memory has not improved even a bit by the processes of removing mail boxes and upgrading the mail client version
I got an answer. Nokia Email is based on a commercial product Nokia used to sell called Intellisync. My company used to sell it, and I knew it intimately. Intellisync has an option to '"refresh" an entire account, meaning to wipe out any server-installed files (email and hopefully Settings, too) and download everything again. This used to be in the Intellisync client, but was removed (for simplicity's sake, I assume) from Nokia Email. The feature is still available to Nokia technical support, but the trick is that you must insist on speaking with "Central Technical Support". Apparently not every Nokia office has interactive access to the Nokia Messaging Servers. Central Support can either refresh the account (which will trickle down to your phone), or outright delete your Messaging account (phone results unknown).
As nothing we've tried so far has had any effect, be prepared for this to fail, too, and perhaps make a backup with Ovi Suite before placing the phone call in case those databases double in size instead of shrink. But that is my absolute last ditch suggestion. If you try this, please post the outcome so we know if it works.