I am running Cyanogenmod 6.1.0-beta4-harmony on a Viewsonic G Tablet since December 2010 and have generally found it to be stable.
However, I have twice over the past month been greeted by the above error when booting the device. After some research after the first time, I used adb on a Windows maching to log in and delete the entire database folder in /data/data/com.android.providers.contacts since it did contain the journal file mentioned in one posting. That did resolve the problem, my contacts database was resynchronized from Google although I have may have lost a few of my over 3,000 contacts.
Today, this happened to me again and I did the very same thing and I am now waiting while the contact database is being rebuilt on the tablet.
I find this to be very troublesome, however, since I may not have access to a machine set up with the android development environment and being able to log onto my tablet to fix the problem. Further, since the error prevents me from doing anything on the tablet (it greets my when the tablet is booting) the tablet is useless until this can be fixed.
My questions are: (1) have others seen this on the G Tablet (yes, I know it is seen on other hardware), (2) are there other reasons for the error, and (3) is there some way I can fix this if I were to boot the tablet into recovery mode which does work?
Thanks.
Your contacts have been corrupted. You can either go to settings>applications and clear them there, or if you have titanium backup, wipe the data that way.
My advice moving forward is turn automatic syncing of contacts off by going to Accounts/Sync settings, clicking on your Google account, and unchecking "Sync Contacts".
Hi guys,
Wonder if anyone can shed a light why this happens. It's been going on for the last few months – Originally I thought I'd wait and see if the problem resolves by itself. But seems to get slightly worse over time now.
I am currently: Rooted & Unlocked
Problem: System hangs after reboot at home screen with message “Process System Not Responding” - with option to wait or terminate the process – Whatever option is chosen, ATP will reboot itself.
Frequency: Unpredictable – But once the message appears after switching it on, ATP will reboot itself 2 to 4 times before I can use it again.
I had done a lot of searches, but there doesn't appear to be any solution / or anyone knows why this is happening. One useful comment I found recently said this may be due to some processes starting before they are meant to during boot up sequence – but no details were given.
What I had tried (based on numerous suggestions after searching the net):
Wipe Dalvik Cache / Caches
Clear “Media Storage” and “Google Framework Services” data
Remove my accounts (currently I have two accounts registered in my ATP) and re-register the accounts.
Remove all the widgets from home screen
Hard reset / Factory Reset
Finally – Multiple different combinations of the above
Getting quite frustrated here.
Wonder if anyone can help please?
Thank you in advance.
[Q] "Process System Not Responding" researching and even downgrading to .15 --> .21, I think the problem is finally solved.
Allegedly "Process System is Not Responding" may be caused by process(es) that hangs or take too long to complete during the boot up sequence. So I uninstall blindly one program at a time - and it appears that Cachemate might have caused it.
Prior to this, every 3-4 normal boots, were followed by 2-3 "Process System is Not Responding" until a normal boot followed. I am now 48 hours problem free. Hopefully it will stay this way.
Edit (11/06) - Ok, spoke too soon. Got the message again after 24hours of use and after roughly 15 normal reboots (I switched ATP off/on these many times to make sure the problem was well and truly gone). The Cachemate could just be a red herring then. However there appear to be less in term of frequency. I noted that the message came on after I watched a video (3hours long video - 600mb in size) and rebooted ATP. Tried disabling media storage (no real logic here, I thought I just gave it a go) - but the problem is still there. So this evening, I reflashed the asus .21 rom --> downgrade to .15 --> reroot --> upgrade back to .21 (again to real logic here, thought I give it a go).
I can't think what else to do. I wonder if large hosts file (mine is 8mb) could cause the problem or the wallpaper I use that is stored under /sdcard - but again, the problem/message only comes up randomly.
Edit (13/06) - Finally managed to narrow down the problem. Everytime a large hosts file (mine is about 8mb) is created, the problem comes (faithfully everytime). And when the original smaller hosts file is restored - problem is gone entirely.
Any input on workaround is very much appreciated.
alright i fixed it on my phone. i did a full wipe. tell me if i need to explain how to do this. reflashed the ROM and gapps. when i went through the setup the first time there was an option to restore from google. it was checked by default. i left it checked. same problem... system process not responding... wiped and started over and reflashed ROM and gapps. unchecked restore google and it didnt come back. phone hasnt crashed since. the problem lies within the wifi passwords restore. the problem started when i was trying to start wifi. i dont know where to report the bug or i would. good luck and any questions? just quote this so i get an email and ill try to explain if this didnt make sense. hope it helped. if it did consider buying my buddy a beer who is a dev and needs a new computer. http://johntriger-development.yolasite.com/
Hello.
Due to some problems in my Smartphone (Android 4.0.3), I had to uninstall Whatsapp Messenger and reinstall it.
It was working perfectly before I uninstalled it.
But now, there is no way to have it working again. I should say I already have an active account till April 2014. So, I installed it both downloading from the Play Store and downloading from Whatsapp website. The result is the same:
1.- Once re-installed and being sure I have both phone line and wifi network, I start whatsapp.
2.- I accept the terms.
3.- Whatsapp ask me for my phone number. I introduce the same I always have: +34 abc de fx yz and OK
4.- Whatsapp discover the old databases and ask me if I want to recover messages from them. I answer yes, whatsapp tell me that 3.189 msgs are recovered.
5.- Whatsapp ask me for the profile details, photo and name. And the strange things start here:
5a.- It seems not having recognized my phone number, as it ask for my profile, that I feel it had to be known
5b.- In the name field, there is a number too similar to the one I introduced in 3.-, but NOT the same, no country code and the last 2 digits are zeroes: abcdefx00
5c.- By this time, no message, no phone call is received
5d.- No question about verify code is received.
6.- Anyway, I put my name in the profile name field and press NEXT
7.- Whatsapp goes to “Initializing, wait a moment ….” And nothing more…. It stay stuck there…. Non ending. Hours later, the only way to resume my phone is restarting the phone.
I already tried all the suggestions of the different forums: go without recover messages, download 2.8 and then reinstall with the most recent versión, download from market and then reinstall with the most recent from whatsapp website, erase the old databases.... Same result.
I found that last year there were similar problems that seemed to be due to whatsapp servers problems, and week ago also the verification server had also troubles... Could again be this the problem?
I am planning to do a "Factory reset" of my pone (HTC Sensation), but I would like to explore any solution before that one.
Any help, please?
Thanks and kind regards
I'm struggling with something that never happened to me, I'm unable to restore my database to my recently upgraded Samsung J3 2016 - is running LineageOS 14.1 now
The phone was running stock Android 5.1.1, version J320FXXU0AQI1, nothing fancy here.
Made some research about what ROM to use and decided to upgrade to LineageOS 14.1, I'm really sick and tired of Google spying my steps, my contacts and the number of times i take a piss every day, and so on. Right now I don't have any Google account associated with the mobile (could this be the problem, since this is a custom ROM?)
Everything ran smoothly, backed up my contacts, call logs, SMS, pictures and the ENTIRE Whataspp folder. This method always worked fine on several phones I've upgraded or simple swapped equipment to a more up-to-date hardware. Everytime worked like a charm, restored logs, contacts and so on, in what it concerns to Whatsapp i simply moved the ENTIRE folder to the new phone (or upgraded phone), installed the Whatsapp app and is just straight forward for the app to ask me for a SMS code to activate the software and then asked me to restore my backed up database. It has been very simple so far, but not this time:
When it reachs the point to detect and restore my database Whatsapp states that can find one Database from 1970 (???? WTF) with 0 bytes, and after that it fails to restore my data (not strange, 0 bytes is no data). I've already tried earlier versions of Whataspp, tried different databases (there are 7 in my folder, i don't believe all of them are corrupted). I'm reaching 0 ways to explore. BTW, i dont use Google drive to store my backups because its enough for Google to know how many times i take a piss everyday, i rather have the backups with me, on my phone (thanks any way Google), but the files are safe in my desktop and on my phone for now, inaccessible so far but their're there.
Can any one point me some way to try to revive my database? Just a note, i have an older phone that still have Whatsapp there, i didn't erased it, maybe it's there something of interest for this situation?
Thanks so much in advance for everyone that can help, any hint can be helpful.
Update!
I've managed to get another phone, exactly the same, Samsung J3 201 J320F.
I've sent my whatsapp folder to the phone, signed in to my google account, installed whatasapp and, like 98% of the times my backup is ok and is restored. Now I have two phones:
1- one with Whataspp working fine (the one with Stock ROM 5.1.1 J320FXXU0AQI1
2- another one, the main phone, where i want to put my whataspp backup working but it simply doesnt work (previous post). Everything elese is settled and working just fine. Maybe whatasapp doesnt like Custom ROMs??
So, I'm sure that my backups are fine, right now I have access to anything that i may need i guess. I don't believe that Im the first person not beeing able to restore whataspp backups in LineageOS.
Please help
New developments.: I've installed Ressurection 5.8.5, the latest available for this phone. It runs ok, but Whataspp problem is still there, the backup is marked to have 0Kb, somehow Whataspp simple doesn't want to recover my backup if I'm using a custom firmware (I receive a warning about no support from them if I have problems at the beginning of the startup process).
So far this method didn't work (Whatsapp shows my Backup with 0Kb):
1) Copy your latest crypt 12 file to /sdcard/WhatsApp/Databases/
2) Install / Activate WhatsApp
3) WhatsApp will retrieve the key from their server and restore your backup.
I've tried this method that appeared to have some success in same cases. Followed everything but no luck, Whataspp detects a 0Kb backup also.
Meanwhile I still don't believe that I'm the very 1st person that this happens, I'm still very impressed with this. If the OP thinks I'm in the wrong Topic please feel free to move it to the right place, maybe there I'll have better luck.
Not that I have much knowledge in that direction, but the issue sounds more like it is about the file than Whatsapp itself. Maybe some permission issue? If you use a filemanager app like total commander, can it read the file fully? I found a topic that had 0 byte filesize issue and a simple reboot apparently fixed it.
musschrott said:
Not that I have much knowledge in that direction, but the issue sounds more like it is about the file than Whatsapp itself. Maybe some permission issue? If you use a filemanager app like total commander, can it read the file fully? I found a topic that had 0 byte filesize issue and a simple reboot apparently fixed it.
Click to expand...
Click to collapse
Hello musschrott, and thanks for replying.
I've tried moving the database file, erase it, changing it's name and the android system allows me to do it, i think the file itself is free to be read by Whataspp, but your other tip, the permissions in system made me google around (even more..) about it and I found here on XDA this. : "The privacy protection in the drop down menu and the permission in the app settings." (credits to LegoTechniker). On the privacy protection is all ON but in the Permission is all OFF and Whataspp nor the System ask me to turn it ON and it can result on whatasapp reading files with 0Kb from 1970.
I'll give a try but only tomorrow because the code/phonecall from Whataspp have a 48h delay and keeps increasing everytime I try a different method to solve this issue.
musschrott, thanks again!
tomalamix said:
Hello musschrott, and thanks for replying.
I've tried moving the database file, erase it, changing it's name and the android system allows me to do it, i think the file itself is free to be read by Whataspp, but your other tip, the permissions in system made me google around (even more..) about it and I found here on XDA this. : "The privacy protection in the drop down menu and the permission in the app settings." (credits to LegoTechniker). On the privacy protection is all ON but in the Permission is all OFF and Whataspp nor the System ask me to turn it ON and it can result on whatasapp reading files with 0Kb from 1970.
I'll give a try but only tomorrow because the code/phonecall from Whataspp have a 48h delay and keeps increasing everytime I try a different method to solve this issue.
musschrott, thanks again!
Click to expand...
Click to collapse
For everyone and specially those who helped (musschrott).
This has worked for me: giving full permissions to Whataspp in "Settings - Privacy" and in "Settings - Applications" worked like a charm, you have to do it BEFORE you start Whatsapp.
Best regards to everyone and thanks once more!
Make sure the WhatsApp backup file is in internal storage, and rename the backup file to msgstore.db.crypt.
After upgrading to LineageOS 14.1,install WhatsApp.When asked to restore from backup,choose the "msgstore.db.crypt" file.
mango9 said:
Make sure the WhatsApp backup file is in internal storage, and rename the backup file to msgstore.db.crypt.
After upgrading to LineageOS 14.1,install WhatsApp.When asked to restore from backup,choose the "msgstore.db.crypt" file.
Click to expand...
Click to collapse
Yes,
Those are the basic steps, but BEFORE running Whatasapp for the 1st time you have to give permissions in the system to Whatsapp because these are all OFF and the system doesn't ask to turn them ON when the permission is needed, simply presents you a file with 0Kb from 1970 and that's it. Again, you have to do this BEFORE the 1st Whatsapp startup and everything should run well.
Best regards
My issue is I gave full write permissions but then it goes straight to the Google Drive restore and does not show my local backup.
When I followed this by Rahil:
https://www.reddit.com/r/whatsapp/comments/np2zjp
"So today I finally fixed the issue myself
Click to expand...
Click to collapse
Steps: 1)make sure you rename the database as it should be.
2)Install whatsapp
3)Insert your number when asked
4)Use Otp/code
5)Then the app will ask you for google drive permission ,click allow/ok
6)Then the app will ask for contact permission ,simply deny this permission (very important)
7)Then the app will ask for storage permission ,hit allow (very important)
8)Then you will see your local storage behind the popup saying allow google drive and crap You will need to press add account and have your fingers ready for instant tapping between add account and instant tapping restore button ,and out of 10-30 times doing this practice, you will luckily hit restore button, I know this sounds confusing, And I can make a tutorial video if you want ,this works 100%
9)once it is restored ,you will still see app asking google drive option, don't click skip (this will reset the app ,leading to nothing restored) , So when the app is asking to restore from google drive, close the app right away (very important)
10)open the app ,and the app will ask you to set name ,set your name ,and you'll see all your backup"
Click to expand...
Click to collapse
It works but then it shows my local backup as 0k and from 12/31/1969
This is Driving me wild and now I have to wait 12 hrs to try again. Has anyone solved this ridiculous error?
dpoverlord said:
My issue is I gave full write permissions but then it goes straight to the Google Drive restore and does not show my local backup.
When I followed this by Rahil:
https://www.reddit.com/r/whatsapp/comments/np2zjp
It works but then it shows my local backup as 0k and from 12/31/1969
This is Driving me wild and now I have to wait 12 hrs to try again. Has anyone solved this ridiculous error?
Click to expand...
Click to collapse
Did you find a solution to this? I have the exact same problem
Hey Guys,
Today suddenly my WhatsApp gave a message error, followed by a full deletion of the entire chat history. 10 Years of work (I run my business via WhatsApp).
I had my Google Drive backup, but everytime it hit 24% it got stuck and failed to restore the messages. None of the proposed solutions I could find online fixed it for me, nor did the poor WhatsApp support which is practically a machine prompting same non-working solutions.
After reading many different solutions and threads about it, I started to feel and think that possibly the cause of it is some bug or failure to retrive media files, and looks like I was right - I just made a breakthrough that at least allowed me to restore all the chats, without the media - but hell, at this stage I'll take what I get. And that's 10 years of it - I couldn't afford losing it.
So for all of you who are facing the same problem and are willing to waive media, those are roughly the steps I took which solved it for me (lots of other things in the way that I doubt helped):
I highly advice before you do it, maybe to avoid many of the steps I did and especially before uninstalling and reinstalling WhatsApp as the WA Support advices you to do, to go to Internal Storage > Android > Media > com.whatsapp > WhatsApp > Databases and copy the msgstore.db file. Also, try to create a local backup by disabling Google Backup and perhaps getting another updated version of the chats. I didn't do it, and I think it costed me a lot of extra steps to try to get the local backup file back, as well as some missing recent chats.
1. Uninstalled WhatsApp, rebooted the phone.
2. Authenticated and started normal backup restore from Google Drive process.
3. Connected the phone to my computer, so I can see real time via Windows Explorer which files are downloaded as a part of the backup (Storage > Android > Media > com.whatsapp > WhatsApp).
4. When download finished and the restoring process started, I immediately copied the Databases and Backup folders as they were brought from the Google backup, leaving the Media one out which I figured is the one causing the issues. Note it's important to do it as soon as download finishes and files are complete, as WhatsApp deletes it if backup fails.
5. When hitting the 24% stuck mark, I 'force stopped' WhatsApp, and uninstalled the app again, then restarted my phone.
6. I reinstalled WhatsApp, and didn't open it.
7. I went on to Create the folder Storage > Android > Media > com.whatsapp > WhatsApp > Databases, and pasted my msgstore.db file in it.
8. I opened WhatsApp, authenticated and started normal backup restore from Google Drive - and it worked. All my chat history is back.
9. I changed my Google Account for WhatsApp backup, and created a fresh backup just in case.
Now I'll decide if makes sense to also attempt recovering the media but at this moment I'm way too tired to think about it anymore.
Hope this helps you!