Database Info

Android.process.acore

Well again.... Im about to lose my minda because of this damn thing! Now I'm getting a fc every 5 sec... Process acore? My tab is essentially dead? Can't do anything author a fc, can't go into settings our anything... I want to smash this thing! I just got it working well and now this? Anyone know what that process is? I cam do anything with it now, cant load a new rom because I can't get into settings. Its just in an intimate loop of fc. The real disaster is im in idaho, where I got it as a gift, and I'm flying back to nc in the morning.. Can't take out back before I leave..
Anyone know anything about the fc?
Sent from my SAMSUNG-SGH-I897 using XDA App

Setting---appliction----Clear the contacts and ContactsProvider data .

I can't get into settings... It fc's every time I try to go into settings. Any other way to do it?
Sent from my SAMSUNG-SGH-I897 using XDA App

I think I need to do a reset, but if I can't open settings I'm lost? Not sure how it happened, it just started doing it.
Sent from my SAMSUNG-SGH-I897 using XDA App

pqrs said:
I think I need to do a reset, but if I can't open settings I'm lost? Not sure how it happened, it just started doing it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
If you can get ClockWork to run on boot .You might need to wipe data and reinstall the rom..Not much you can do when it is constantly Fc'ing

Well I don't have cw on the tab, its still stock.. I'm hoping I can plug into a pc, download it and get root that way? Then possibly load a new rom... Otherwise I'm screwed.
Think that will work?
Sent from my SAMSUNG-SGH-I897 using XDA App

Maybe you should restore it back to factory settings...
http://forum.xda-developers.com/showthread.php?t=861950
That will bring it back to how it was out of the box, then start over.
If there are still issues then possible hardware problems?

Had this issue, even after NV flash. I was able to get CW (even with the fc) on and wipe, and partition the sd to 2gb. That seems to have cleaned it up.
This forum is the greatest on the entire internet!

Glad to hear you got it working. Imo, your issue is probably the worst thing about running stock - if you get these FC's, there's really no fix unless you take the risk of using a mod.
I believe it's the same reason why Staples pulled the devices - too many returns due to FC's OOTB.

Yes, it's too bad they did not include the "easy" button to reset to stock. Even with the upgrade, it may be enough to ultimately kill off the device. With all of the recovery images on my laptop now, I can put humpty dumpty back with ease. It's good for me, I plan to watch for returns. I could use a couple more of these.

I got cw installed and vegan, the table works like I'd expect now! This thing is awesome! Thanks for the help.

A resolution
I had this same issue happen to me on a new ROM not factory. I couldn't get into settings either to do the contact wipe. But Titanium was installed on it and I was able to wipe the contact data through there. Just an FYI if anyone else runs across the same problem.

Thanks to you Snyper....I just picked up my tab after placing it down for 10 mins and saw this error. Just a quick search in the thread and there is the answer. Man this forum rocks!!!

Just happened to me running vegan 3
clearing contact info worked like a champ!
thanks guys

I have the same issue. But, I don't have CW installed, Titanium won't load up. How can I manually get the clockword APK file on there to attempt to install it?
Any other ideas?

Gravislord said:
I have the same issue. But, I don't have CW installed, Titanium won't load up. How can I manually get the clockword APK file on there to attempt to install it?
Any other ideas?
Click to expand...
Click to collapse
Clockwork is not an apk. Read this
Post 1
http://forum.xda-developers.com/showthread.php?t=865245
Post 1
http://forum.xda-developers.com/showthread.php?t=892090

roebeet said:
Glad to hear you got it working. Imo, your issue is probably the worst thing about running stock - if you get these FC's, there's really no fix unless you take the risk of using a mod.
I believe it's the same reason why Staples pulled the devices - too many returns due to FC's OOTB.
Click to expand...
Click to collapse
Hi,
Having had this acore FC problem last night, I have a couple of questions:
1) In your post above, you seem to have thought that this only happens with stock TNT. But, in this thread, it seems like others that are not running stock TNT also encounter this problem. So, it this a potential problem with all ROMs, or just with stock TNT?
2) From reading through and other threads, one fix when it happens is to clear the Contacts and ContactsProvider data, either using Settings, if you can get to it, or using Titanium, if you have it. I'm assuming that what both of those steps do is to clear out the tables in SQLlite for the Contacts and ContactsProvider apps. Is that right? If it is, do you, or does anyone know the command lines that would do the same thing?
The reason for the latter question is that when I had the problem, I could still do adb shell. If there was an sqllite command I could have used to clear the problem, I definitely would have done that, instead of having to install CWM, re-partition, and re-flash stock 3452!
Thanks,
Jim

Problems with switching ROMs

I am having a problem with switching ROMs on my sensation which just started a few days ago. I am currently running ARHD 3.1.1 and it is very stable and I have had no problems whatsoever, but like many here, I like trying out different and new ROMs. Anyways, I did a backup and installed ARHD 3.6.2, and it was forcing close on several apps, and kept getting soft reboots, so I tried RCMix's, and it would load and automatically install some apps and settings that I had on my previous ROM, and it was working fine, but then I started getting soft reboots when I would open any app, so I tried about 2 other ROMs (S3n5eay/Pyramid3D) and same thing, so being fed up I restored my backup and then I began to have superuser problems, so I unistalled updates, cleared data, and still was unable to gain root access. I kept clearing data, installed superuser 2.3.6 then 3.02 and finally got root again, but everytime I reboot I lose root. I then again tried different ROMs, and same thing is happening. I have used superwipe script, ARHD's wipe script, P3D wipe script, formated from CWM, and no matter what, I am still unable to keep a new ROM and keep losing root with my backup. I'm sorry for a long post, but can anyone please help me figure this out. I have upgraded ROMs many a times in the past on this phone and others, and have never experienced these problems, so can someone please help me.

I kinda had the same problem with you, with that being root was the problem. But the ROM's are pre-rooted so that shouldn't be a problem. Try to flash the root file again, until it is succesfull flashed.

Thanks. I'll go ahead and try that.
Sent from Sensational toy running ARHD 3.1.1

Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.

West0000 said:
Geez, that sounds horrible, man. It never ceases to surprise me how different every one of these seemingly identical devices are.
Click to expand...
Click to collapse
Well for the most part everyone downloads different software. For that just one of the factors that make us all somewhat "different" this is why everyone has some sort of problems here and there.
Most times a fix can be a reboot or reinstall of the app. Even clearing of caches helps because of data conflicts on the phone. Especially when someone like me that flashes different ROMS, that's why nandroids and backups are key so that if you fudge up your phone, you can always revert back to your nandroid.
And for all the people who are trying to revert back to their nandroid after flashing a different rom, you need to use the wipe data scripts in ARHD or Coredroid to reformat the ext4 before reverting your nandroid. Just a FYI.

All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.

Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.

cbrvnm said:
Believe me, I have attempted everything without any success. I guess I'm going to stay on my current ROM until I get the time to deal with all of this, and hoping that for whatever reason I don't have to reboot my phone, or that it randomly reboots in order not to deal with the problems. I have always wiped going/coming from different ROMs, but have never experienced this before, and it is very frustrating especially when I like to try different developers mods. I'll keep attempting to try to figure this out, and if I find a solution, I will update.
Click to expand...
Click to collapse
Keep trying different ROMs and different strategies of when you wipe/restore stuff. It's quite interesting that theoretically identical phones can have different responses to the exact same actions. 2 people can install a ROM in the exact same way and for 1 it will work, the other it won't. You just gotta work it out until you figure out how to manage your particular issues.

Yeah, I hear you. It's just very frustrating when in the past I have switched ROMs on all the phones that I have ever owned without any problems until now. But I'll try different methods and see what happens. I appreciate everyones input. Thanks. Oh, and if anybody has any other suggestions, please, share.

Ok, I was able to get Pyramid3D v0.8.0 working so far. I flashed with superwipe about 3 times then installed the ROM. I did not sign into my account, and installed my apps from titanium first, and then signed in. I got several reboots with setcpu so I unistalled it. I also get a few market fcs. Now the problem that I have is that I installed the 4EXT recovery and my phone is unable to play my music files through any of the music players. I am able to open them with astro, but not music player. But I guess I'll try to figure this one out now. Thanks for the advice.

The Janitor Mop said:
All I know is that wiping everything before flashing a new ROM does not guarantee that you won't get FCs and soft reboots.
For example, I did a factory reset, wiped cache, wiped dalvik, and then did superwipe (yes I know redundant), and then flashed a ROM and I thought nothing could go wrong. Then while setting up I went ahead and setup my google account during the setup process, and once I was finished I began restoring my apps+data from Titanium Backup. While that was happening Market started auto-reinstalling my apps, and this instantly conflicted with the fact that I was doing the same thing from TB. It caused a few of my apps to FC all the time. So make sure you skip adding your google account during setup.
You can also get stuff to go haywire if you restore system data from TB. Doing so will conflict with the ROM and cause FCs and reboots. For example, I didn't know how to easily back up texts and contacts for a while, and I would go in to TB and restore everything that said something like mms, messages, texts, messages widget, etc. and doing so actually caused my messages to go haywire. Same thing with contacts. The only things you should be restoring from TB are your user apps+data. As already noted, you should also superwipe before restoring a nandroid because it is exactly like flashing a new ROM. If you're on a ROM you just flashed that has 1 version of superuser, and then you go straight into recovery and restore a nandroid without wiping everything first (and has a different version of superuser), you're going to get issues with superuser.
The rule of thumb when it comes to avoiding FCs and reboots is to avoid letting data conflict. Don't mix ROM data, don't mix app data, don't restore system settings from your old ROM on your new one, etc.
Click to expand...
Click to collapse
Good post. I didn't realize I should be doing so much wiping even before restoring a backup.
Incidentally, I'm kicking myself now, but in the excitement of flashing my first custom ROM, I forgot to backup my original system. Doh. It's the only time I haven't backed up before changing ROMs, but that's arguably the most important backup to make.

My Desire S hangs on CM7.1

Hi all,
I can't post in the Desire S Development forum yet, so I might as well ask the question here.
I've been trying in vain to use CM on my Desire S (one of the major reasons why I wanted to root my phone). I'm able to use it for a while, but after a time, such as installing all my apps, it would hang on me and the only way to fix it is to remove the battery. At first, I thought it would be due to the Go Launcher EX, but it hanged when using ADW too. Then I thought that perhaps restoring the system data were the culprit, but I still got the same dilemma when I didn't. I then started restoring the apps one by one (using Titanium Backup) but it seems that it hangs at random.
I really want to use CM but I can't Has anyone encountered this problem? Anyone knows how to correct it?
Thanks in advance guys

Complete wipe all partition then reflash. Double check your phone's current HBOOT, RADIO, KERNEL if it is supported.

I have had CM7.1 working perfectly on my Desire S for weeks and I used Titanium Backup to restore previous apps and data.
The questions I would ask are which version of CM? 'Stable' or one of the nightlies? Have you formatted all your partitions to EXT4 first? What recovery are you using - shouldn't matter, but might be relevant if it's failing to write something properly. Did you verify the checksum after you downloaded CM7.1? Have you installed anything else from recovery mode afterwards, such as GAPPS? What happens if you install CM and just try running your Desire as a phone for a few days, using only the built-in apps - does it still hang?
Also, when it does hang, you are much better off trying to 'soft' kill it rather than pulling the battery if you possibly can - hold 'Vol -', 'Vol +' and 'Power' for maybe as long as 30 seconds to see if that works; pulling the battery can cause serious hardware failure.

Stable!
Nightlies are for experimentals only
Sent from my HTC Desire S using xda premium

well i have no issue at all.

No issues here either, also used TB to restore apps.
Don't restore any sense system apps or data, I imagine that could cause problems.
Sent from my HTC Desire S using xda premium

Thanks for the replies guys I'm using the ROM Manager app to dl and install CM. I always use the stable build. The recovery I use is 4ext. Kernel is stock, I think. The one that comes with the LBC mod, which is the one I'm currently using. How do I check for the radio? Oh and what radio and kernel are you guys using?

doesn't have hang issue....but my desire s did shut down by itself. It can be on again by pressing the power button but still it annoys me twice this week.
p/s : using cm7.1 stable release

BTW, here's my radio: 20.28b.30.0805U_38.03.02.15_M
How do I check compatibilities?

the radio perform same as in sense rom, i use radio as at my sig and its perform well.

Just an update:
I think I found the app that's making all the bollocks. I was using File Organizer to create labels and custom folders.
At first, I spend the whole time yesterday rebooting/restoring the ROM and found that problems arise when I started placing Folder Organizer widgets. Today, I restored the ROM again and instead used Go Launcher EX to create custom folders for the Home Screen. So far so good, it's just as snappy as the time I just installed CM. It's crappy that I'm no longer able to use one of the apps I paid for, but it's worth it because of all the ROMs (stock and custom) that I encountered, CM is the snappiest and the best
I'll still monitor the progress, but so far, it hasn't hang on me. Before uninstalling Folder Organizer, it would usually take around a minute before it hangs completely, and the soft reset (Power + Volume Down) doesn't work when that happens

[q] help note 3 not working

so i was trying to do a custom boot image. Im a noob and this is what i did. I went into the app called rom installer. I already did a backup of old one and did a backup during this as well.
I found the ZIP and did the whole reboot thing, didnt work, phone was reset. I backed up and now it keeps saying process system not working and gapps not working and everything has stopped. I am unable to use the phone or get to my other backup to try just incase.
Does anybody know how to fix this? or how to get my phone up and running again?

It is better not to try third party applications to boot custom images.
You do a decent research in xda forums and google how to install custom ROMs using Odin.
you may get an idea after a small research, as the process is risky make sure you know what you are doing.
The issue what you facing is not serious, it can be solved by flashing the original Samsung firmware for your device.

[Q] Need Help after rooting implosion

UPDATE: 07-04-14 5:25pm EST:
I was able to get all my data off using a mac. I re-flashed Purity ROM after doing a full wipe. I have now re-installed all most of my apps and have begun normal use. For now this is resolved hopefully I have no further issues. Thanks for the response @Kreateablaze Much appreciated.
So here is a brief history about what I did and what I am experiencing. I am pretty much a newb here so please be gentle and excuse my ignorance.
Just in case you don't want to read my book below:
TLDR: rooted phone, Installed TWRP, installed Purity Rom, system failed hardcore, cant get data off my phone because explorer crashes. I just want to get my data off so I can re-install a ROM or just flash back to stock and re-lock the bootloader.....
-Unlocked bootloader, rooted, and installed TWRP using "Wug's Nexus Root Toolkit"
(just want to give props to any one involved in that tool, it is an amazing tool and worked flawlessly!)
-After running the toolkit, I was successfully rooted and running TWRP.
-I ran a back up using TWRP. Is that what is referred to as a "Nandroid" back up?
-After running this back up I installed "Purity ROM"
-For the first 24 hours everything was fine.
-I had to reboot my N5 due to an app that was acting up and a reboot usually cleared up the issue if force stopping didn't. (an app I used before rooting and I knew how to fix the issue I was having, I don't think this is related to my issue.)
-After rebooting the phone, I was faced with a pop up stating something along the lines of android UI has stopped working. I clicked okay, unlocked the phone it flashed black with my home screen icons and everything went back to normal. I rebooted the phone again just to make sure that was a one time fluke. This time The phone was in an endless crash cycle. Every process I could think of was crashing non stop the phone was unusable. I did some research and found something that said to go into TWRP and run a permissions repair.
-After running permissions repair my phone booted back up and was working relatively okay.
-After the repair rebooting my N5 results in that same UI crash I got the first time. BUT the phone is usable, and that process never crashes again unless I reboot.
-After running that permissions repair some of my apps disappeared. Trying to re-install them results in a -24 error. I got a few of them to re-install by clearing related data in data/data folder. A few of my apps refuse to re-install even though there is no trace of the data in the data/data folder.
-Another issue I am having after all of this is that I can NOT pull any data off of the phone. I plug it in, Windows recognizes the phone but it takes about 10-15 minutes to load the folder structure. I am then unable to copy any of the data off of the phone. Explorer crashes and I cant get the data off. UPDATE: I was able to get the data of the phone by using a friends Mac. I will post an update with some more info.
-I need to get my data off the phone before I can continue but am unable to. Any help would here would be greatly appreciated.
-Also if any one knows a more stable ROM with a similar feature set to Purity that is fast, has good battery life and isn't packed to the gills with features tht may one day cause more issues that they are worth. Please let me know.
Thanks in advance for any help you guys may be able to offer me.

Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....

basik17 said:
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....
Click to expand...
Click to collapse
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response. I was able to get my data off using a friends Mac... I am going to reflash Purity and see how things go. If they dont go well I may go back to stock. I never seem to have good luck with these things...