Database Info

PIM Backup restore makes HTC Fuze run very slowly

I just updtaed my rom to the official 6.1 build released recently here:
http://forum.xda-developers.com/showthread.php?t=519698
I used Pim Backup before updating to save all my contacts and text messages.
When I did a restore, my phone ran incredibly slowly. I know that before, when I used PIM to restore from Windows 6.0 to 6.1 (this was when I was on a Cingular 8525), it took a very long time because 6.1 needed to nest all my text messages, but my fuze didn't seem to do this. It only kept the last 30 or so messages from my side of the conversation only, and the entire phone slowed down like crazy once I did the restore, especially if I do anything involving text messages, it was damn near unusable.
Is there anything I can do to restore the backup of all my contacts and text messages successfully and have them all intact the way they were before the update?

before you do a restore you should do the tweak to make texts go in regular order not threaded
then do the restore
all you need to do to speed the phone back up is to soft reset.
once you reset you do the tweak to go back to threaded and you will be fine

How many texts do you have? You may want to archive some of the older ones. It's probably worth looking at \cemail.vol just to see how big it is. I don't text much at all and don't use email; I have maybe 100 texts on my device. My cemail.vol (in the root of the device memory) is 292K. If you've got 10K+ texts or some crazy amount, my guess is that your cemail.vol file is huge-this could be your problem. I also have maybe 50 contacts, and my pim.vol is ~600K. If I were you, I'd just look at those two files, and maybe look at your available storage memory before and after restoring your pim data.
Edit: or just do what lbhocky19 said, lol.

lbhocky19 said:
before you do a restore you should do the tweak to make texts go in regular order not threaded
then do the restore
all you need to do to speed the phone back up is to soft reset.
once you reset you do the tweak to go back to threaded and you will be fine
Click to expand...
Click to collapse
How do I do this tweak?

do you have advanced config? if not get that
its in the messaging section

By Advanced Config, do you mean a setting somewhere in my phone that I can set to advanced mode, or do you mean a program I need to download?

Umm, Hello? Anyone?

... umm, can anybody please help me?

Well... http://www.lmgtfy.com/?q=advanced+config

..... you don't have to insult me, "Advanced Config" is a common term, I didn't expect a Google search to get it right on the first hit.
So, is this program basically the equivalent of the Att Tilt's Kaiser Tweak then?
I have a new problem with PIM Backup now however.....
I used Advanced Config to set the messages as regular order, then did the restore, and it APPEARED to work fine (didnt set them back to threaded yet). But then I tried restoring the second backup, and the progress bar has been stuck at 1% for a while now. I am assuming its going so slow because its trying to insert information while the database already has so much information in it.
Is there any way I can make this work faster? A way to restore both backup files at once or merge them into one or something like that?
The reason I have two is because after I made the initial backup, since I wasn't able to get it to restore correctly, I had to reset my device yesterday so I made a second backup that is just the 2-4 week period between then I last updated it and had to reset it, it contains far far fewer messages and logs than previously.

Sorry to post again but.... I have another problem.
The restore isn't working correctly.
I used Advanced Config to set mt messages as standard instead of threaded, and restored my PIM backup. After I set ti back to threaded, it would only show the other person's side of the conversation, not mine. Then once I got a text from that person and replied it started re-sorting the messages..... and then it would only show MY side of the conversation, not theirs!
Why is this happening? Is there anything I can do to fix it?

I've fixed the stuck-SMS bug somehow?

Well.. I seemed to have somehow solved my SMS bug accidentally. I was suffering from it from day 1 when I restored my 2000+ messages. I gave up on trying to tweak it, and decided to concentrate on moving my picture MMSes over from my Diamond.
(along the way I concluded none of the backup softwares can really work with picture MMSes.. but that's another story.)
I'll state upfront I don't really know what I did that fixed the problem, but I'm very sure the problem of SMS stuck in the outbox is fixed, I seem to get all my SMSes and only my msg threads with more than 300 msgs take a while (3s - 5s?) to load.
The interface loads EVERY single msg. Doesn't anyone at HTC use MSN?
Here's what I did when I gave up with the MMSes. Something along the way solved the problem. Or maybe I got lucky.
1) deleted the messages that were previously MMSes in both inbox and sent box.
Every single one.
Didn't study much, but I realised through testing, my restored MMSes were causing some problems. In traditional mode, I could not reply to a single restored MMS, but a single restored SMS was fine. In conversation mode, conversations with restored MMSes had a lag, while those with only SMS didn't. The sent/received fields also seem screwed up somehow.
Furthermore, none of the softwares I tried using to restore couldn't bring my picture MMSes back to life. (sentimental value, else I'll just save the images)
That's why I decided to just kill all of them for now. I used Jeyo Mobile to delete those "former-MMSes" from my HD2.
2) Exited Sense by removing it from Today
BTW, this was fresh from a Hard Reset, so there's nothing else in the system.
3) Using Jeyo Mobile, deleted the (previously unseen) folder Conversations from the sms inbox
Don't know why, I keep seeing it reappear. Seems to cause problems when it's not properly indexed. the UI seems to duplicate the latest msg from each contact into it, and that'll be the start of the threads.
3) Clear the deleted items folder using Jeyo
Including manually deleting the Conversations folder that was stuck in it.
4) Back up the SMSes
I had no email, nothing in draft as the UI doesn't index them properly. Only left stuff in Inbox and Sent. I used Jeyo Mobile Companion 2.1. Feel free to try others.
5) Hard Reset
6) Restore the SMSes
Here's where it's hazy again. I might have tried alot of combis, as the UI doesn't index the msgs properly for conversations all the time. Idea was to restore and let the UI index it properly. Here's the possible permutations:
a) I might have exited Sense.
b) I might have left the HTC msging interface in traditional
c) I might have left the HTC msging interface in conversation
Chances are, it's in conversation.
I restored the msgs using Jeyo. (it's stored in a XML file, so other text based backups may work too)
-------------------------------------
I only realised that the problem is fixed a few days later, as I realised that the next few days, I got my SMS reports instantly, and I never had a SMS stuck. My newly received and sent MMSes worked perfectly too.
I'm trying not to touch that msging part of my phone now that it is working perfectly....
Just found out that HD2 I bought (at the same time) for my GF is suffering the sent/huge lag issue though. Maybe I'll try to pin point a fix using her phone. She shld have less than 50 messages, though I did back up and restore some mmses for her previously.
However as I'm about to go on a 19day tour/holiday, so I thought I'll just share my experience and maybe some experts can figure out what's wrong.

Just for your info, I'm using 1.48.707.2 (71294) WWE.

[Q] Something very wrong with Go SMS Pro

Hi, I've had a weird problem where Go SMS Pro seems to have disappeared from my phone. I clicked the icon for it on my LauncherPro dock last night only for it to tell me "could not launch the requested activity." I looked in my app drawer and lo and behold, Go SMS Pro was gone! I tried reinstalling it from the market but once it finished downloading nothing happened, and when I tried restoring it from titanium backup it made my phone reboot. Using root explorer, I found that the app still had data on my phone in several directories, but according to Android the app is not installed at all (so I can't uninstall to remove all that data and start fresh).
What I think may have caused the problem is that I used Apps2SD to move Go SMS Pro to my phone so that I could get the widget to work properly. Could something have been corrupted that way? Also I flashed Infused v1.5.0 yesterday, but I don't think that's the problem; I wiped data and cache, although maybe restoring the app+data from TiBu after flashing messed something up. I didn't have any problems until after I moved it with Apps2SD though.
Basically I want to be able to use Go SMS again (I prefer it to the stock messaging app), so I figure I have to delete all the old data from it from my phone. If anyone with a better working knowledge than me of Android's infrastructure could help me figure out which directories I need to delete data from if I want to be able to do a clean reinstall, I'd appreciate it. Thanks!

[Q] [ICS] Wrong SMS being deleted

Hi!
On my Nexus S (i9023) I'm having the problem, that wrong SMS are deleted.
This happens on stock ROM as well as on CM9.
In example I get a message from my voice-mail telling me that s.o. called me. I read the message, then tap and hold it to delete it. And what happens? An SMS above (i.e. 2 above) is deleted instead! If I delete it again, it works.
I really have lost lots of SMS this way... Anyone else who has this bug? And how can I work around that?

..

Have just tried it on my NS [i9020a] running the latest CM9 version and haven't got any issues with deleting the wrong SMS messages. Sorry that I can't be of more help.

I didn't try to delete complete threads yet, so I can't say.
Maybe it's because I always restore my old SMS using SBS Backup + after flashing a new ROM. Perhaps it messes up the SMS database?! So for now I've simply deleted all of my SMS and will see what happens.

This has happened to me once but I actually deleted a message only once .
I usually delete by thread.

[Q] One contact's message thread won't open. Stock message app

Ever since the ICS upgrade, one contact's message thread refuses to open and is stuck on "O Loading" with that little circle revolving.
I downloaded go sms pro before and I was able to access his thread through that and the message count wasn't over the maximum limit per contact. I've since gone back to the stock app as he's out of the country and it's faster than go sms pro but he recently txted me and caused the problem to occur with other contacts (though a reset of the phone solves their issue)
Does anyone have a solution and failing that, advice? I should say right now that deleting his message thread is the last resort.

and HTC sensation
Android 4.0.3
Software 3.32.401.5

You could try to backup your messages (you can find some apps for that in the market), then delete all your contacts, and afterwards restore them again~
Though no idea if it will work :/

burningwipf said:
You could try to backup your messages (you can find some apps for that in the market), then delete all your contacts, and afterwards restore them again~
Though no idea if it will work :/
Click to expand...
Click to collapse
Aye I could try it with a contact whose messages I don't mind losing and seeing if that works, thanks for the tip!

You can also use Google Voice, and have it copy all the messages to your Gmail account.
Sent from my Galaxy Nexus using Tapatalk 2

So I started backing up and restoring and I was able to open all contacts' threads. The backup never fully restores all messages though and I have to keep hitting "restore" so that it'll restore them all up to the present day. Don't know why it's doing it this way.
Just now I've checked and that one contact won't open again. What I might do is try and restore all to the present, delete loads of messages I don't want, and backup this new message history.

I know this is most likely far too late but I was having the same problems and found this thread while trying to sort it and hope it will help anyone else in future who has the same problems. I tried backing up and restoring (Using both the default and sms back-up and restore) deleting the thread and restoring, eventually I solved it by installing handscent, deleting the messages sent/received back to when the problem started in that thread and a few before, then went in settings, apps, then all, messages cleared the cache, restarted and it is sorted!!

3dd1 said:
I know this is most likely far too late but I was having the same problems and found this thread while trying to sort it and hope it will help anyone else in future who has the same problems. I tried backing up and restoring (Using both the default and sms back-up and restore) deleting the thread and restoring, eventually I solved it by installing handscent, deleting the messages sent/received back to when the problem started in that thread and a few before, then went in settings, apps, then all, messages cleared the cache, restarted and it is sorted!!
Click to expand...
Click to collapse
Yeah it never resolved itself but I love the customisation of go sms pro so much that I don't mind anymore. Pity go sms pro crashes every so often and I think it slows the phone down.

I was going to start a new thread but see that this is the same problem I have.
I have a mt4gs (Doubleshot) and the problem described in this thread has happened twice. Both times i was receiving a text message and did something else with the phone at the same moment, and it seems to have jammed up the receipt of that text. The first time, i sent a text to the person at the same moment i received one. The second time, i locked the screen at the moment one arrived. Now that thread never loads, and loading other threads or contacts takes much longer than it should. In fact, i don't think contacts would ever load if i were willing to wait forever.
The first time I backed up the texts, reset the device, and restored, and everything worked fine, but that's a really time-consuming process and it seems like a ridiculous workaround for some broken buffer or queue in Android messaging.
It seems that there must be a direct fix for this. If it's easy enough to break messaging that it has happened to me twice, it must be a fairly common problem. But a search has turned up nothing but people saying there are too many messages or to use an alternative app for messaging. That's (1) incorrect and (2) again an ugly workaround for a problem with core functionality.