[Q] Whatsapp DB gets corrupted frequently - General Questions and Answers
I have a galaxy S4 (GT-I9505G) running CM 11.0.
About once a week, whatsapp stops receiving messages. The next time I open the app, it complains:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you "skip restore", you start with a new db. If you "restore", it probably restores from the whatsapp backups in /sdcard/Whatsapp/... (I actually never tried that because I have titanium which is just faster and more reliable)
Searching some of the strings in this message online (i.e "something went wrong with your chat history") yielded *nothing*.
This has been happening *way* too often lately, so it's really annoying. My current solution is 4 scheduled titanium backups a day, which is just an ugly patch - I want to solve this.
Did anyone encounter this? Any idea?
Do you have random reboots? Or did your battery die while you are using whatsapp? As far as I know, that's the way whatsapp db gets corrupted.
Yup u r right
AiAS61 said:
Do you have random reboots? Or did your battery die while you are using whatsapp? As far as I know, that's the way whatsapp db gets corrupted.
Click to expand...
Click to collapse
I've had some (due to the stupid power button getting stuck...)
But still, *far* more corrupted DBs than random reboots.
Besides that, the only "abnormal" habit I can think of is moving in and out of airplane mode a few times a day (to save battery)
Do you think it might be of a problem? Anyway some of the corruptions happen *really* at random times, not directly after airplane mode switching, so I don't think that's the sole reason (if it's the reason at all)
Tyaginator said:
Yup u r right
Click to expand...
Click to collapse
What?
Jon-G said:
I've had some (due to the stupid power button getting stuck...)
But still, *far* more corrupted DBs than random reboots.
Besides that, the only "abnormal" habit I can think of is moving in and out of airplane mode a few times a day (to save battery)
Do you think it might be of a problem? Anyway some of the corruptions happen *really* at random times, not directly after airplane mode switching, so I don't think that's the sole reason (if it's the reason at all)
What?
Click to expand...
Click to collapse
I was saying he is right, whatsapp db gets corrupted when there is an abnormal power off, and airplane mode has nothing to do with it. Please check if have any task killer installed like battery saver or clean master coz whatsapp does not support any task killers.
Tyaginator said:
I was saying he is right, whatsapp db gets corrupted when there is an abnormal power off, and airplane mode has nothing to do with it. Please check if have any task killer installed like battery saver or clean master coz whatsapp does not support any task killers.
Click to expand...
Click to collapse
No, I have no task killers, battery savers, etc. None. Nothing stops WhatsApp, it just crashes.
I will investigate it further and post here if I find anything as a future reference for others.
I also have this problem, at least for more than a year now.
I have a Fairphone (first edition) with Android version 4.2.2.
I have a corrupted Whatsapp messages database at least one time every week.
I used a task killer in the past but I am not using it any more for at least a few months.
I must admit that my phone does sometimes crash unexpectedly, but this does not necessarily correlates with the db corruption. Most of the time its like I'm using Whatsapp and everything is fine and when I check again for example, an hour later, it says that the message db is corrupted...
Also I factory reset my phone a few weeks ago and after setting everything up the phenomena still existed.
I also used an other Phone (Samsung Galaxy Core 2 with Android 4.4) for a full week and I didn't experience this database corruption with Whatsapp.
So I wondered if you have found a solution by now? or maybe what can be a possible reason (or reasons) for this corruption?
I think I found a solution, chat gets corrupted only after u restart ur phone, just force stop WhatsApp then reboot your phone.. Hope this fixes ur problem too
"something gone wrong with your chat history"
go to "whatsapp" installation folder (in phone or card)
open Folder "whatsapp"
open Folder " Database"
In this folder named (Database) , except file name " msgstore.db.crypt" and 2nd last back file, Delete all.
For example, if you have in your phone like below.
1-msgstore.db.crypt
2-msgstore-16-12-2016.db.crypt
3-msgstore-17-12-2016.db.crypt
4-msgstore-18-12-2016.db.crypt
5-msgstore-19-12-2016.db.crypt
except 1st and "4th. delete all.
problem solved, also you will find more space in your "SD CARD" or "Phone memory"
Problem not yet solved
mansii said:
go to "whatsapp" installation folder (in phone or card)
open Folder "whatsapp"
open Folder " Database"
In this folder named (Database) , except file name " msgstore.db.crypt" and 2nd last back file, Delete all.
For example, if you have in your phone like below.
1-msgstore.db.crypt
2-msgstore-16-12-2016.db.crypt
3-msgstore-17-12-2016.db.crypt
4-msgstore-18-12-2016.db.crypt
5-msgstore-19-12-2016.db.crypt
except 1st and "4th. delete all.
problem solved, also you will find more space in your "SD CARD" or "Phone memory"
Click to expand...
Click to collapse
No, it doesn't work. I already had a habit of deleting older databases from that folder. But still I got this issue. Whenever, I click the 'search' and type something, WhatsApp closes immediately and when I open it, it asks me to restore last backup.
You see the problem that WhatsApp encounters is not in the backup database(s) in the SD card. The problem is in WhatsApp private-folder database. To be precise, the problem is in this file exactly:-
/data/data/com.whatsapp/databases/msgstore.db
However, to access this file, you need root access. And if someone is smart enough and has ample amount of time, he/she can also find the error in the database manually in the different sections. All you need is an SQL database editor to view the file. I guess the problem should be in 'messages_fts' and/or 'messages_fts_content' tables in the database.
Well, same issue here. I have 4 backups, but all of them seem to be corrupted since Whatsapp crashes after restoring the database. It is curious, if I disable wifi and data the restore process ends properly. But Whatsapp crashes no matter what after a few minutes.
Is there any way to fix the *.db.crypt12 database? That would fix the problem.
I have no crashes, but on my rooted S6 the DB gets corrupted quite frequently. At this stage I don't really see any other way out than to start over - completely. Any tips?
Oki said:
Well, same issue here. I have 4 backups, but all of them seem to be corrupted since Whatsapp crashes after restoring the database. It is curious, if I disable wifi and data the restore process ends properly. But Whatsapp crashes no matter what after a few minutes.
Is there any way to fix the *.db.crypt12 database? That would fix the problem.
Click to expand...
Click to collapse
Actually, you can fix the DB crypt12 database manually, but to find the error and fix it will be a time taking task.
ManSamVampire said:
Actually, you can fix the DB crypt12 database manually, but to find the error and fix it will be a time taking task.
Click to expand...
Click to collapse
The DB file is fine. I already decrypted it and checked with SQLite. The problem must be in the data, and only WhatsApp can identify the issue. They already have the file but I do not expect any answer. WhatsApp has failed to me. A $19,000,000,000 company unable to fix the problems they create.
Oki said:
The DB file is fine. I already decrypted it and checked with SQLite. The problem must be in the data, and only WhatsApp can identify the issue. They already have the file but I do not expect any answer. WhatsApp has failed to me. A $19,000,000,000 company unable to fix the problems they create.
Click to expand...
Click to collapse
@Oki: did you managed to get an answer from Whatsapp? I'm with a similar problem... On a new phone the backup stops at 41% and I can't restore the messages :/
I've never seen a message that indicates that the db file is corrupted but I don't know how to solve this
joestyle said:
@Oki: did you managed to get an answer from Whatsapp? I'm with a similar problem... On a new phone the backup stops at 41% and I can't restore the messages :/
I've never seen a message that indicates that the db file is corrupted but I don't know how to solve this
Click to expand...
Click to collapse
They answered but only for letting me know there is no solution but delete the DB and start a new one. I did a backup of the DB file and started a new DB.
Oki said:
The DB file is fine. I already decrypted it and checked with SQLite. The problem must be in the data, and only WhatsApp can identify the issue. They already have the file but I do not expect any answer. WhatsApp has failed to me. A $19,000,000,000 company unable to fix the problems they create.
Click to expand...
Click to collapse
Oki said:
They answered but only for letting me know there is no solution but delete the DB and start a new one. I did a backup of the DB file and started a new DB.
Click to expand...
Click to collapse
But by starting a new db from scratch how can you put the backup messages there?
joestyle said:
But by starting a new db from scratch how can you put the backup messages there?
Click to expand...
Click to collapse
There is no way.
Hi mate. I had the same issue. Not sure if the WhatsApp database was corrupted or not . I still had WhatsApp installed on my old phone. I deleted all manual backups and Google drive back up. Allowed for a fresh manual back up and a fresh Google drive back up WITHOUT media (you might find a lot of corrupt images in your WhatsApp image folder btw like I did. Delete them). Then copied over the new manual backup onto the new phone. Then did a restore from Google drive which stopped at 31% and said if I wanted to restore from local backup. For "preparing WhatsApp messages" it reached 100% then said "restoring messages". I left the phone like this overnight. I have 400,000 messages and my file is 120mb. Woke up in the morning and still said "restoring messages" with no status of how much was restored or restoring. Endless loop. Did a restart of the phone and went back onto WhatsApp and all my messages were there! Though not sure if the data is still corrupt as when I scroll all the way to the top of a chat it shows my messages from April 2013 but when I do a "search" in the chat and then remove the word from the search and scroll back up it'll only go up to like September 2013. I have to click "back" and go back onto the chat to see messages right from April 2013 - Strange! Not sure it it's data corrupted or a glitch that needs fixing.
saeedravat17 said:
Though not sure if the data is still corrupt as when I scroll all the way to the top of a chat it shows my messages from April 2013 but when I do a "search" in the chat and then remove the word from the search and scroll back up it'll only go up to like September 2013. I have to click "back" and go back onto the chat to see messages right from April 2013 - Strange! Not sure it it's data corrupted or a glitch that needs fixing.
Click to expand...
Click to collapse
It seems the restoration process was incomplete. In the actual database file where messages are stored,
/data/data/com.whatsapp/databases/msgstore.db
there is a table messages_fts_content, which, according to my observation, is responsible for maintaining a search index.
You say that the search results only in newer messages appear and the older ones are not visible, which means that the messages_fts_content table was not restored completely.
P.S. I don't know if the WhatsApp backup dbcrypt files have the messages_fts_content table or not. It is also possible that the dbcrypt files have only the messages and WhatsApp generates the messages_fts_content table automatically after restoring the messages.
If someone has been able to open the dbcrypt backup files, please post a list of tables in that database.
Related
Outlook Mobile will not load, no access to messages
I have an O2 XDA Exec running one of the old Crossbow ROMs (one of those where it's "Outlook Mobile" instead of "Messaging", I forget exactly which ROM it is I went for at the time). One thing I quite enjoy is that even after switching devices and upgrading the ROM is still having every SMS I've sent or received since summer 2006. This might all end here, sadly, as Outlook Mobile won't load and neither of the SMS backup programs I've tried have worked. Here are the symptoms: When I try and load Outlook Mobile (regardless of whether it's from the Start menu, HTC home screen, the messaging part of the today screen or the text option in Contacts) it simply does nothing. I have tried two SMS backup programs. The EasyHelper "Contact + SMS Backup" which I normally use flashes up an error saying "Read SMS failed. Please restart device and try again. If the problem still exists, please contact your vendor.(401)" The other one (which I forget the name of now) failed to show a list of folders to backup from and if I ignore that option and try to back up anyway it sits for a while trying and then gives up (it says it's finished but it lies, the resulting file is way too small). Don't know if this is related but the problem started around the same time. After having my device switched on for a minute or so a message will appear saying "Voice Command has encountered a problem. Restart Voice Command and try again." I don't use Voice Command so this isn't the problem but this error started showing around the same time this started. When someone sends me an SMS nothing happens. Don't know if this is normal or not, I get an access denied error when I try and do *anything* with cemail.vol (copy, rename, whatever) Everything else seems to work fine (except ActiveSync but I can't remember the last time I had that working anyway, I don't use it). I have tried: Many soft resets. Killing poutlook.exe and removing from the Today screen anything that might interact with the messaging. Launching Outlook Mobile in different ways. Two SMS backup programs. Sending myself an SMS from a different phone. Nothing works and I can't access my messages. Obviously as someone who's been keeping messages for about two years now (crossed the 10,000 mark I think) I'm slightly annoyed about this. I'm planning to reflash my phone to a newer WM6 ROM as soon as I'm not using it as my sole method for Internet access so my only concern here is saving my mass of text messages (either in a format I can read on my PC or a format I can restore from after reflashing my Universal). If only I'd known before tonight that there was a free program to backup SMS on a schedule... Any ideas at all? I'm comfortable doing registry hacks or typing commands or whatever needs doing. My messages are on this device somewhere and I want them. There's important nostalgia in there. Help greatly appreciated as ever.
Huh. It works now. No idea why, just got a text message today having not tried it for a couple of days and it seems okay. Frantically taking backups now.
Something on my SD card was messing it up, not sure what but removing the SD card allowed me to back up my messages. I removed the SD card, allowed it to create a "Storage Card" folder when it fails to save something to the SD card (it does this) and then reinserted the SD card and had the backup software back up to "/Storage Card2". Weird. But I've solved the problem (in my case) and made a note of it on the offchance it might help someone coming in from Google someday. ROM flashing time!
Thank youu! Thank you very much... I had the same problem, but noticed it only yesterday! Apparently I have been receiving sms messages since 3 or 4 days, but it shows nothing on my today screen. Yesterday I tried to open outlook because a friend told me he sent me a message, but... nothing!!! When I removed the SD card it worked But no messages since 3 or 4 days! and thus can't know who sent me messages Anyway, thank you for your thread... and yes, I came from Google
sorry to bump an old thread, but this exact problem happened to me out of nowhere today. google searched it and this thread came up. i noticed i hadn't received even spam in my email to day and that error popped up about voice command. removed my sd card and it all went away.... very strange. i have not installed any new programs either...
process com.android.acore FC and how i fixed it
I woke up this morning to a locked up tablet, when i restarted i was getting FC every couple seconds & when i switched apps This is how i fixed it, I do not advise other people do the same thing because deleting database files like this is probably a really bad idea, and I had a clockwork mod backup in case something went wrong. so, DO NOT DO THIS that said, here's how I fixed it. The logs indicated it was dieing in the contacts app when it went to open the database "create table android_metadata failed" I found the crashed DB in /data/data/com.android.providers.contacts/databases/ You can tell it's crashed if there is a .db-journal file, this means it wasn't closed properly, be VERY VERY VERY careful that you have the correct item (refresh the list a couple time and make sure the .db-journal file is still there, you could have gotten lucky and loaded the directory while it was writing the DB) Now, rename or move the ENTIRE database folder (so we still have it, but the phone thinks it's gone) cross your fingers and PRAY, there is a remote chance you just hosed your phone, but it SHOULD recreate the database automatically with default settings and 'fix' your crashes, but of course everything in that DB is now gone! Not sure which databases this will work on, and which ones will just brick your phone, so be careful, i was lucky and it was just the contacts DB that was crashed, but since everything included the call logs in the contact DB apparently- I couldn't even get into the system settings to do a factory reset. and as always, BACK IT UP BEFORE YOU F*CK IT UP! :-D FYI: the sqlLite DBs in android are flaky as hell, i wrote an app that did background updates once a min and it would crash like this ALL the time (even in the emulator), I think it has something to do w/ wakelocks expiring before the SQL cache is written to the disk but i don't understand why that would happen in the emulator.
KinkyMunkey said: I woke up this morning to a locked up tablet, when i restarted i was getting FC every couple seconds & when i switched apps This is how i fixed it, I do not advise other people do the same thing because deleting database files like this is probably a really bad idea, and I had a clockwork mod backup in case something went wrong. so, DO NOT DO THIS that said, here's how I fixed it. The logs indicated it was dieing in the contacts app when it went to open the database "create table android_metadata failed" I found the crashed DB in /data/data/com.android.providers.contacts/databases/ You can tell it's crashed if there is a .db-journal file, this means it wasn't closed properly, be VERY VERY VERY careful that you have the correct item (refresh the list a couple time and make sure the .db-journal file is still there, you could have gotten lucky and loaded the directory while it was writing the DB) Now, rename or move the ENTIRE database folder (so we still have it, but the phone thinks it's gone) cross your fingers and PRAY, there is a remote chance you just hosed your phone, but it SHOULD recreate the database automatically with default settings and 'fix' your crashes, but of course everything in that DB is now gone! Not sure which databases this will work on, and which ones will just brick your phone, so be careful, i was lucky and it was just the contacts DB that was crashed, but since everything included the call logs in the contact DB apparently- I couldn't even get into the system settings to do a factory reset. and as always, BACK IT UP BEFORE YOU F*CK IT UP! :-D FYI: the sqlLite DBs in android are flaky as hell, i wrote an app that did background updates once a min and it would crash like this ALL the time (even in the emulator), I think it has something to do w/ wakelocks expiring before the SQL cache is written to the disk but i don't understand why that would happen in the emulator. Click to expand... Click to collapse i am having this force close problem...when i navigate to that directory using es file explorer: "/date - folder is empty" on /sdcard/data/ - there is beautifulwidgets folder and com.keramldas.TitaniumBackup folder... I dont see any "com.android.providers.contacts folder... so can anyone help please? - thanks as always - oh btw using CM and vegan - if that helps
I thought that Titanium backup could be used to do that, delete the Contacts data? Jim
Great to see there may be a solution. Something to try before restoring to the reliably not quite current backup.
There is some info under the FAQ thread in the development forum. http://forum.xda-developers.com/showthread.php?t=874258
DireMerlin said: i am having this force close problem...when i navigate to that directory using es file explorer: "/date - folder is empty" on /sdcard/data/ - there is beautifulwidgets folder and com.keramldas.TitaniumBackup folder... I dont see any "com.android.providers.contacts folder... so can anyone help please? - thanks as always - oh btw using CM and vegan - if that helps Click to expand... Click to collapse You won't see those files or folders with es file explorer. You must use Root Explorer to locate and delete them.
jimcpl said: I thought that Titanium backup could be used to do that, delete the Contacts data? Jim Click to expand... Click to collapse Thanks man that solved the problem for me now I am back to using my tablet.
I just used titanium backup and contacts > wipe data...This fixed issue for me...I don't really care about having any contacts on my tablet anyway. (I am not suggesting you try this, just posting what I did).
kevinshae said: I just used titanium backup and contacts > wipe data...This fixed issue for me...I don't really care about having any contacts on my tablet anyway. (I am not suggesting you try this, just posting what I did). Click to expand... Click to collapse Thanks!!! That worked for me too. I was getting really frustrated.
Having a contact with no name to use for sync reference will cause this. When you restore your contacts, look for one with data but blank name.
Rumbleweed said: Having a contact with no name to use for sync reference will cause this. When you restore your contacts, look for one with data but blank name. Click to expand... Click to collapse Totally. For some reason I would get this fc when I would sync my contacts. It stopped a few months ago after I realized I had 2 mystery contacts with no names or data and deleted them. Haven't had a problem since.
I've recently started having FC's with media files on my stock rom and was just about to wipe and reload when I took one more look at this thread. While I didn't find a corrupted contacts database, I did poke around in other directories at the /data/data/ directory level and found a corrupted database in com.android.providers.media/databases. I renamed the database folder, waited a few minutes and rebooted. Everything's working fine now. Someday I'll install one of the better roms, but thanks to this forum I'll stay stock a little bit longer.
+1 on using Titanium Backup to wipe the contacts data. Stopped the FCs for me. These appear to start because of the wake issue. I gotta figure out how to fix that. I also turned off the autosync. Man now that sleep issue is really bugging me. 4.3.0 with .2 add on.
**WARNING** You WILL lose your contacts by doing this and you will have to restore them. I am not responsible for any errors that may occur in the process. I am not a developer or a hacker, I'm just a guy who had a problem and fixed it with a VERY long google search. Cheers. I had the same problem. Constant (every 5 seconds) force close with a "process com.android.acore" FC. Flashing Vanilla, switching Roms, rebooting, all that did not help as it does not erase personal data (which is where the problem lies). If you don't have it, I STRONGLY suggest you keep a copy of Titanium Backup on your G-tab. If you have this force close problem, you will not be able to DL via the market, so you will have to sideload via the link I provided below. (You MUST be rooted to use Titanium Backup). Once Titanium Backup is installed... go to the "Backup/Restore" tab --> scroll down to "Contacts 2.2" --> click on it, then select "wipe data" --> then scroll down to "Contacts Sync Adaptor 2.2.1" and do the same. Once you have done those it should have fixed your "process com.android.acore" FC problems. Now you will need to restore your contacts via whichever method you have them backed up. I'm a noob, so it won't let me embed links. But here it is... mediafire dot com/?g0jurgugmr985e2
I've wiped the contacts but still get the problem. Any help?
ShiftyBob said: **WARNING** You WILL lose your contacts by doing this and you will have to restore them. I am not responsible for any errors that may occur in the process. I am not a developer or a hacker, I'm just a guy who had a problem and fixed it with a VERY long google search. Cheers. I had the same problem. Constant (every 5 seconds) force close with a "process com.android.acore" FC. Flashing Vanilla, switching Roms, rebooting, all that did not help as it does not erase personal data (which is where the problem lies). If you don't have it, I STRONGLY suggest you keep a copy of Titanium Backup on your G-tab. If you have this force close problem, you will not be able to DL via the market, so you will have to sideload via the link I provided below. (You MUST be rooted to use Titanium Backup). Once Titanium Backup is installed... go to the "Backup/Restore" tab --> scroll down to "Contacts 2.2" --> click on it, then select "wipe data" --> then scroll down to "Contacts Sync Adaptor 2.2.1" and do the same. Once you have done those it should have fixed your "process com.android.acore" FC problems. Now you will need to restore your contacts via whichever method you have them backed up. I'm a noob, so it won't let me embed links. But here it is... mediafire dot com/?g0jurgugmr985e2 Click to expand... Click to collapse This did not work for me until I noticed a third Contacts related app in Titanium backup. Once I wiped data in "{Contacts/Calls} Contacts Storage 2.2" it the FC issue for me. I am using TnT lite4.4.0
ShiftyBob, CosmicVagabond, you guys saved me an ulcer! Clearing Contacts Storage 2.2 (well, all three) was just what it took to clear MY stupid FCs. Thanks, folks!
okay so I am worse than a noob, I am a drone. Did what I was told three or four months ago to get this thing to run with android and now cant remember what I did. I am running tntlite 4.25. I am getting the same error but I do not have titanium backup. I assume (yeah stupid me) I could put it on the sd card if I knew where to get it. But other than that I have no idea what to do. And since I have to go into the hospital for a week starting on Tuesday I am very unhappy. Could someone possibly give me some step by step ideas on how to overcome? I would be grateful
process com.android.acore FC issue ShiftyBob said: **WARNING** You WILL lose your contacts by doing this and you will have to restore them. I am not responsible for any errors that may occur in the process. I am not a developer or a hacker, I'm just a guy who had a problem and fixed it with a VERY long google search. Cheers. I had the same problem. Constant (every 5 seconds) force close with a "process com.android.acore" FC. Flashing Vanilla, switching Roms, rebooting, all that did not help as it does not erase personal data (which is where the problem lies). If you don't have it, I STRONGLY suggest you keep a copy of Titanium Backup on your G-tab. If you have this force close problem, you will not be able to DL via the market, so you will have to sideload via the link I provided below. (You MUST be rooted to use Titanium Backup). Once Titanium Backup is installed... go to the "Backup/Restore" tab --> scroll down to "Contacts 2.2" --> click on it, then select "wipe data" --> then scroll down to "Contacts Sync Adaptor 2.2.1" and do the same. Once you have done those it should have fixed your "process com.android.acore" FC problems. Now you will need to restore your contacts via whichever method you have them backed up. I'm a noob, so it won't let me embed links. But here it is... mediafire dot com/?g0jurgugmr985e2 Click to expand... Click to collapse This was exactly the same problem I had. After loading Synergy RLS1 I tried to read in contacts from the previous backup using Titanium backup. All was fine until I rebooted and I got com.android.acore FCs continuously. It took some quick fingers, but I was able to wipe data from "Contact Storage 2.3.3" and it now has gone away. Now my contacts are downloading from gmail and all seems well. EVO 4g - Synergy ROM RLS1
did you try to wipe Dalvik catch!
[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.
Oppo backup & restore problem
I am having issues with the Oppo backup & restore. When I try and attempt this, the device creates 2 folders, one for apps and one for data. Whenever I try and backup it gets to 99% very quickly then hangs there whilst trying to backup my messages. Messages are always behind completing when it hangs. I have left for over an hour but it never completes. Tried several times. The messages file size is also so small only around 15MB If I back up Apps, Contacts., call logs and System data without message it completes fine but never when messages are included?? Am on A.46 was the same on A.42. Anyone else have this issue or know how to fix?
Usual oppo
kevinireland11 said: Usual oppo Click to expand... Click to collapse This is a common issue? Seems bizarre that it can't backup my messages properly.
Question Daily WhatsApp error
I got my new S22 Ultra a month ago..i installed whatsapp..it stucks during restoring chat history…but i overcome this problem by forcing stop the app during the restoring process ( a solution i found after reading many threads.. untill nw it works but um afraid one day everything is lost. Also it takes much time to save hundreds of stickers again)..then everthing is ok for a month till 30 september 2022. Since 30 September 2022, My WhatsApp has been messing up pretty badly. Over the last five days I randomly (and this is true - no errant reboots, no app crashes, etc.) get the error message "Something went wrong with your chat history" on WhatsApp, which has a Restore option under the dialog box. This is practically useless as the progress bar never successfully completes, but even goes back at times. This forces me to reinstall WhatsApp, and pray that I don't have to start with a new chat database again. Because it takes multiple attempts to get back on the app. And i can't restore hundreds of stickers. This plunges me into another time lag, as the app's verification put in progressively increasing wait times every time I reinstall.Why i got this message over last 5 days every morning???How can i solve it without taking the restore option as it took me 5 hours trying to restore chat history and stickers???I hope you response quickly.. I have tried many solutions: clearing cashe..turning airplane mode on and off..reset networks settings…turn the mobile on and off…unrestrict whatsapp from battery saver…remove the backup at google drive..close whatsapp from recent apps…during trying to solve the issue, i noticed one day that the error occurs during backup is being uploaded to google drive so i choose never to backup to google depending on the local backup but i unfortunatley woke up the next moring and the error occurs once it was searching for new messages. Please help to retrieve a permanent solution specially as i found many people suffering from this for months in many threads...
Hi, you probably need to let the program fully restore the chat database... Can you leave restoring during night, for example, when your don't use the phone? Did you give the app the proper rights to access storage, etc?
Marcelocohenarg said: Hi, you probably need to let the program fully restore the chat database... Can you leave restoring during night, for example, when your don't use the phone? Did you give the app the proper rights to access storage, etc? Click to expand... Click to collapse I tried but it always stucks at different points and if i leave it, it fails ending to an old group chat history... although when i force stop the app, the chat history is back completely.
switch to Telegram
Better yet switch to Signal.