Related
So it doesn't matter what radio/rom/custom kernel I load on my phone right now, the phone keeps crashing (not rebooting, just a popup that crashes programs) with "Sorry! The prossess android.process.acore has stopped unexpectedly. Please try agin."
logs are attached, any advice is greatly appreicated. I'm curently deployed in Afghanistan, and plan to be at Black Hat in two weeks, I would prefer to have a working Nexus One with me, not my touch pro.. geek cred depends on it.. please give me some suggestions.
thanks,
HattZ
This link mentioned something about the possibility of a corrupt file system on the SD card causing these issues. I didn't think it likely, but removed SD card, cleared cashe and dalvik, rebooted, same errors on boot. http://androidcommunity.com/forums/f28/g1-crashed-android-process-acore-17386/
#$% changed two things at once. Did a restore of whatever OS/build/mod I was using two months ago, and pulled my SIM card... no problems... except for wave secure locking it.
replaced sim card, remembered pin for wave secure.. phone was running modaco custom desire port r21 firmware 2.1-update1... custom build and kernel.
.... no ideas... on the root cause. I'm almost wondering if it was a poorly seated sim card and contacts on the sim card being junk..
So 20 minutes later... succsessful
android 2.2
baseband 32.36.00.28U_4.06.00.12_7
kernel 2.6.34-925mV-BFS-OC-Monks-070110
build FRF91 MRCr21/CM6 mod by rodriguezstyle
running just fine. still no idea what was causing the problem, but it's solved.. enough flashings later.. moral of the story, always have a good backup when $%^&ing with your phone.
Since you're the only one posting, I figured I could share too
It's the home launcher running out of memory, isn't it?
I got rid of my issues with "android.processes.acore has crashed" by disabling screen cache in adw launcher settings...
I'm a widget freak, and I do like a large home..
After setting up cm6 and importing my own adw settings, I kept getting the .acore crash.
Flicking a few times back and forth between screens and scrolling the widgets (pure) would cause the error time and time again until I disabled that. It hasn't crashed since.
-e
I think mine was related to a database that was corrupt and wasn't being erased when I was flashing new images, it was however cleared when I did a restore of an old image.
the excerpt from the logs, it errors out trying to change a DB:
I/ContactsDatabaseHelper( 690): Upgrading from version 105 to 309
E/Database( 690): Failure 1 (table properties already exists) on 0x274f78 when preparing 'CREATE TABLE properties (property_key TEXT PRIMARY_KEY, property_value TEXT);'.
W/dalvikvm( 690): threadid=1: thread exiting with uncaught exception (group=0x4001d7f0)
Eddiemc said:
Since you're the only one posting, I figured I could share too
It's the home launcher running out of memory, isn't it?
I got rid of my issues with "android.processes.acore has crashed" by disabling screen cache in adw launcher settings...
I'm a widget freak, and I do like a large home..
After setting up cm6 and importing my own adw settings, I kept getting the .acore crash.
Flicking a few times back and forth between screens and scrolling the widgets (pure) would cause the error time and time again until I disabled that. It hasn't crashed since.
-e
Click to expand...
Click to collapse
You pretty accurately described the situation I was in, though. I'm using LauncherPro Plus with cm6-rc1 and was getting that crash consistently and randomly. Same scenario otherwise. I've been toggling settings & widgets all day trying to figure out a reliable fix. Changing that setting has done wonders for my issues. Thank you.
It may have not been related to the poster's original issue, but you saved me a ton of aggravation and the integrity of a couple small breakable items on my desk.
xperia x10 android.process.acore crash
I believe it has to do with the way my xperia x10 was reading the filing system on my 8Gb micro sdhc card
I renamed my music albums via the usb connection "while the phone was on" in ascending order and it seems the music apk: "music play" play list got corrupted or soemthing
I reopened the apk and let it reorder its self and voila everything seems to work as normal again
So, a little history...
I'm on my 2nd Captivate (unrelated issue). The boot problems didn't arise until I restored my data onto it. The first time I tried restoring system data along with my apps (which I figured was safe since I was going from 2.1 stock to the same) but that had lots of issues. So I did a factory reset, and started over. This time I just restored apps and their data, and a few specific pieces of system data (contacts, wifi APs, etc). That worked better. But later I got too aggressive with what system apps I "froze" (using Titanium Backup), and it got into boot loops I couldn't break out of. So I did another factory reset.
This time, first I carefully froze only apps I was to confirm were safe to freeze. I didn't proceed restoring my apps until I was done freezing and ensured it was booting fine. I then restored all my apps (and their data). The problem is now that it takes forever to boot... in fact, it'll go into a boot loop if I just leave it be. It seems the only way I can gain access is to try and unlock it before it's done booting, clear any "Force close" errors (sometimes takes a few tries) and given enough attempts, I can get in. But the boot takes an unbelievable amount of time, and even with my original apps is many times longer than before on my previous Captivate. Once I fuss my way in, it seems mostly fine, but something is obviously wrong and I want to get it straightened out.
Aside from doing another factory reset, and reinstalling all my apps (which takes like a day without troubleshooting after each, since batch restores in TB don't seem to work well on the Captivate so I have to do them one by one), I'm hoping there's a way to troubleshoot it in its current state and try to fix the problem surgically versus erasing and starting over. I looked at the logcat logs but got in over my head... there are so many errors and warnings and I don't know what's normal and what isn't... too many to know where to begin with searching Google.
So... advice? What tools are available? Even the logcat doesn't seem to kick in until the boot is mostly done, so I'm not sure if it can catch the problem while it's happening. One frustrating thing about Android is that is seems to have no "safe mode" or other diagnostic boot or full logging where you can methodically look at what's happening and experiment with the config. If this was a Windows, Linux or FreeBSD box I'd be in my element and able to get to the bottom of this, but on Android I feel even more crippled, locked-out and helpless than even on Windows. Urgh.
There's got to be a better way to troubleshoot and fix than endless random factory resets. This is something us anti-Windows people scold PC makers for, with all their use of "Restore CDs" for every minor and trivial software issue.
Thanks!
I can't help but think you are still disabling some essential system apps. Either that or one of your apps is causing major problems. Please list what you have frozen in tibu. Btw, the batch function works fine and is what most people on here use.
Also, what is force closing after you restore your apps.
newter55 said:
I can't help but think you are still disabling some essential system apps. Either that or one of your apps is causing major problems. Please list what you have frozen in tibu. Btw, the batch function works fine and is what most people on here use.
Also, what is force closing after you restore your apps.
Click to expand...
Click to collapse
First of all, thanks for taking a stab at this.
My frozen apps are:
* AllShare
* AT&T FamilyMap
* AT&T Hot Spots
* AT&T Maps
* AT&T Music
* AT&T Navigator
* AT&T Radio
* Daily Briefing
* Days
* Instant Messaging
* Media Hub
* Mini Diary
* Mobile Banking
* Mobile Video
* MobiTV
* Where
* Write and Go
* YPmobile
I also tried removing my MicroSD card, as well as switching back to Touchwiz (from LauncherPro). Didn't help.
Yeah the batch problem in TB is very frustrating. I'm using the pay/donate version so I'm missing out on a feature I paid for. I've been exchanging emails with Joel (the author) and we haven't figured it out yet. Batch backups work fine. Batch uninstalls also work fine (update: phone just spontaneously rebooted after about 50 or so uninstalls in a batch). It's the batch restores that seem to choke it. It's not corrupt backup files... a verify runs fine, and I can individually restore the same handful of apps one by one that will choke and hang/reboot the Captivate if attempted to restore in a batch.
The FC error I get is on boot-up, as I try to unlock the screen prior to the boot finishing. I often see "Process system is not responding".
I have aLogcat installed, if that's any use. A few questions about that:
- What's the best logging level to view on? In other words, do I care about "Warnings"?
- What errors are common, harmless, and safe to ignore?
Currently I've tried uninstalling everything down to just a few core apps. Certainly boots fine now, but I get plenty of warnings and errors in logcat.
Are u restoring just the user installed apps+data, or system apps too? Or restoring system stuff like contacts data, accounts prefs, etc?
diablo009 said:
Are u restoring just the user installed apps+data, or system apps too? Or restoring system stuff like contacts data, accounts prefs, etc?
Click to expand...
Click to collapse
I did not do a "restore system data" or any batch/bulk option in TB that restored all system data. As I recall, the only system data I restored a-la-carte (by selecting the individual item from the TB list) were:
Accounts
Bluetooth pairints
Bookmarks
Calendar
Contacts
Wi-Fi Access Points
These were all items in green in TB. I don't believe I restored anything else. Possibilities I suppose are wallpaper settings, "Country, Launguage, Time Zone"... but I definitely would not have restored anything not green.
Are these items safe? Is there any system data definitely not safe to restore? I have to wonder though, if "system data" is unsafe to even restore to the same stock OS version... why back it up at all?
I'm not a long distance from doing yet another factory reset I suppose, if it must come to that. But I'd love a way a bit more analytical/exacting to try and troubleshoot this other than "reinstall one app, reboot, see what happens" as that will take me a week to get back to where I was. I also suspect it's not just one single app that would suddenly show a huge difference after installing, but instead might be the cumulative errors from several apps and knowing how to identify that and clean them up would be useful.
Using adb logcat you can view what is occurring while the phone is booting and possibly see where it is hanging or what is causing the slow boot times. I have seen problems from restoring data such as accounts and contacts with titanium backup but does not seem that it should be an issue when using the same system though I have very little experience with the stock firmware. I know it is not an answer to your question but it seems that you are wanting to remove all the att/Samsung BS so why not flash a rom that does this as well as much more?
Sent from my ADR6300 using XDA App
Thanks for the tip about adb. I've actually not needed adb for anything yet so I've never set it up or used it. I wasn't aware that the service would be active early enough on the phone's boot process to allow it to log boot logs... nor was I even aware it could do this. I'll definitely check out how to set this up... however, if you have a free second and can point me in the right direction (FAQ, instructions, etc) it'd certainly be appreciated otherwise I'll search around and try to find it.
I could probably find other ways to restore contacts and could set my accounts up again manually but I really doubt that's the cause and the other ways are sort of a pain and imperfect. Since neither of us is really convinced that'd be it I won't bother yet until/unless you really suspect it.
I wondered how long it'd take before someone would suggest a custom ROM, this being XDA and all. Short version is I'm not really sold on the concept, as they are all based on the buggy beta leaked ROM, or 2.2 ROMs from other devices that have been hacked up to sort of work as well as possible on the Captivate. All seem to have issues... enough that I'm not really left feeling confident about them. Seems every release unleashes new issues despite addressing old ones, and all seem to have at least a handful of gremlin items that just don't work quite right. Don't have a warm fuzzy feeling, and I still feel like Samsung is going to release an official 2.2 for the Captivate within the next month or so, so I'm interested to see what comes of that. If nothing else, it'll give a better baseline for custom 2.2 ROMs. Then there's the 2.3 being worked on... now that might be interesting.
I don't really think my issue here is related to me running 2.1.
On my phone so it is a pita to search and add a link for you but search for android sdk and you will find what you need to get adb up and running.
And as far as the rom issue goes..it is your phone and I respect your concerns I just had to ask
I would think its media hub that slows it down. It will search your SD cards on every boot. I would start there first.
smokestack76 said:
I would think its media hub that slows it down. It will search your SD cards on every boot. I would start there first.
Click to expand...
Click to collapse
That's one of the apps I've frozen though.
For me the longest process while booting is the stupid media scanner upon bootup. Takes FOREVER for the phone to finally "boot" all the way up.
Been looking for a way to disable it (not really lol) and only have it scan manually to see if the boot time will improve. I'd start searching there.
Also - from what I've read nothing you did should have affected the phone. BUT - if your using Google for your Calendar and Contacts.. and they all get synced up to Google? Why bother doing the restore for those? After you sign up with the Market they get pulled back down to your phone automagically
It's definitely more than just the media scanner. I watch that. When everything is loaded up, it actually reboots in a loop unless intercept the FC. The media scanner will rerun over and over each time... far more than the standard two times.
And I use Google Calendar for my events, but I keep my contacts locally on my phone.
So what is the FC again?
Yep.. my media scanner will run at least 3 times before it stops checking everything.
Very frustrating that the software does this EVERY time I boot back into my phone - you'd think a programmer would put a check to see if it had run before or make it user configurable to scan when you want it to.
avgjoegeek said:
So what is the FC again?
Click to expand...
Click to collapse
See my second post (reply #3):
"Process system is not responding"
LOL sorry not enough coffee and a lil' guy that decided to wake up at 4a.m. = not a good mix.
Well.. did the ol' wise search of Google and came up with:
Might be a permissions issue. Easiest way to fix it is to run ROM Manager and have it fix permisions.
Run the command yourself in ADB:
Code:
Open terminal and
>su
$mount -a
$fix_permissions -r
The -r is optional, but necessary if you find orphaned apps (the app not found please reinstall message)
And reboot. That may help.
And it was also stated that you might have an errant widget/application causing the issue as well. That will be fun trying to figure out what it is.
And.. from my non-dev/non-professional experience - I have checked the logs on my phone and do see a large number of warnings on the phone - but never hindered performance.
So.. 99% of the time you can probably ignore them.
But back to the FC issue - I would try doing a restore of your apps/data again (I read where you have it back down to the "core) and then run the permission script or have ROM Manager do it for you and see if it returns.
Just an update that I think the "fix permissions" thing solved most (but perhaps not all) of my issues. Thanks so much for the tip. I've been reinstalling apps in batches and it's much better, although I see it getting bogged-down bit by bit and I can't pin down what or why.
Thing is, the apps I'm installing in these later rounds/batches shouldn't be resident all the time, shouldn't be auto-loading, and don't come up in things like Startup Cleaner or Advanced Task Killer. Nor do the various process monitors I've tried seem to have the granularity/ability to catch them while they're happening.
So things are better, but I still have some issues without a suitable means to diagnose. I don't get why just having more apps installed, but not running, should affect boot time so much. Hmm...
An inability to troubleshoot certainly rains on my love-affair with Android... not that I'm jumping to another platform anytime soon, but I really want this to work well (as well as be a good salesman to friends and family who often turn to me to show off quality technology).
I have install CM gingerbread beta2 on my gtablet and like everybody else cannot see any apps in my app portion of the market. I was trying different ways of getting my apps to work and stumbled on a temporary fix. When I perform the fix I can see everything in my apps and can initiate an update or install one app manually. After that you may still see your apps but cannot find them to install unless I repeat the fix. The fix is to use Titanium Backup and select market. Then wipe data followed by run app. This has been repeatedly reliable for me. Hope this works for every one else.
One last caveat to this temporary fix. It appears to be time sensitive. The sequence of button presses after you initiate run app from Titanium. Backup have to be done within a short period of time. I am just wondering if this has to be done before market has a chance to completely sync with Google.
Just a note to clarify the process. After you wipe data from market using titanium back up and then run app, market will open and ask you to accept conditions again. As soon as you accept conditions press the settings/options button on the side of the g-tablet or in the notification bar if your ROM has one there. When you press the settings/options button, the market option panel opens up from the bottom of the screen. Choose My Apps and then your apps will populate the screen. Any apps that need updating will be identified. If you have the option to update all, press that and all will be updated. If you update individual apps, you can only update a few before it craps out on you. You will have to repeat the process starting from wipe data and run app in titanium back up to complete any individual updates you did not accomplish before.
works perfectly for me. Even shows more aps. Thanks a lot!
Scott
So a friend of mine updated his T-Mobile UK Samsung Galaxy S to the official 2.2.1 JPY firmware using Odin a few weeks ago. This went well, and is the same firmware that I've had on my unbranded SGS since December.
However, he has an interesting problem. Some of his apps (Handcent, Dolphin HD, plus a few others) seem to forget all of their settings every time the app is exited. For example, every time he goes back into Dolphin it enters the setup wizard as it it's being ran for the first time. This doesn't happen on every app, and it doesn't happen every time.
I noticed there are a couple of other threads on here with people reporting similar issues on custom ROMs (with no solution), but this is a stock ROM from samsungfirmware.com and certainly doesn't happen on my SGS, so it's not the ROM to blame.
Anyone know of a fix?
This question posted in the last few days .
jje
As I said in my post "I noticed there are a couple of other threads on here with people reporting similar issues ... (with no solution)". I wasn't being lazy and just starting another thread without doing some research first. I've read the other threads and they do not contain a solution that will work for him.
I'm assuming you're referring specifically to this thread? http://forum.xda-developers.com/showthread.php?t=992335 In my friend's case, rooting is not an option, so this solution won't work for him.
However, based on that it looks like a factory reset may fix it. If I don't come back people reading this can assume it worked.
Hello
I experimented the same issue.
Looking at some log traces event it reported some permissions errors on intestinal filesystem like database location access write errors. This can explain setting persistence trouble.
After various workaround, bypass or others kind of fallback I did a full reinstallation of filesystem including a wipe data of the system. Take care to backup application and sensible data SMS, photo...
Since all is working fine and no more problems with settings
I don't know if it's helping you.
This is just my personal experience on this same problem.
Perhaps more simple solution is possible
Regards
Gilles
Thanks. So far so good after a Factory Reset. If it were my phone I'd be looking at Logcat, etc, too, but it's a bit hard to do remotely.
It's odd how some apps saved their settings fine, but some don't.
A factory reset did fix it... for a while. But then other apps started suffering from the problem.
So I've been researching this a bit more today. Here's what I've discovered:
The problem is unique to Samsung Galaxy S phones, and appears to be only ones running 2.2.1 (but maybe 2.2. too?).
Samsung have renamed /data/data to /dbdata/databases, and shared preferences for applications are persisting in this folder even if the application is uninstalled. If you install the app again, the app becomes a different user from the one that owns the shared preferences.
For example - If you install some random application and you look at its process running with the ps command, it will show as "app_XX", where XX is some number. For our example here let's say it shows as "app_55". When it then saves its settings in /dbdata/databases the folder the settings are saved in will have owner (shown by ls -l) as "app_55" too. That's fine, and normal.
The seed of the problem is sewn when you uninstall the app. Those shared preferences are not removed. Even using the "Clear data" option before uninstalling doesn't seem to help. If you then install the app again and look at the output of ps you'll see the new app is "app_56". The shared preferences are still there from last time with owner "app_55", hence the permissions error when it tries to save its settings, as user app_56 cannot modify user app_55's files.
A factory reset obviously cures it as this, at least temporarily, as it wipes the data in /dbdata/databases.
If you're rooted, you can go into /dbdata/databases and delete the relevent folder for the application that's having the problem. It will be recreated with the correct owner next time the app saves its settings.
I didn't try chown to change the owner to the correct one, but maybe that's a way to keep the old settings and correct the problem.
Bingo. No wonder my titanium backup is not remembering the preference settings.
All of a sudden my nooted Nook Color, which has been running beautifully for a long time, refuses to download new apps or updates in the Market app. They are stuck at "Starting download..." forever.
I have tried unmounting/mounting my SD card, and changing my status in Gmail (following instructions in other threads) but to no avail. For obvious reasons I can't toggle between Wifi/3G either. So I don't know what to do...
I have also tried stopping/cancelling all downloads and wiping the data for Market and rebooting the Nook.
OMG! After doing all of the above, in no particular order, when I went into Settings -> Manage Applications, all of a sudden all of the previously stuck downloads downloaded automatically - even the ones I had cancelled.
Now everything is working again. Just thought this might help someone else with the same problem in the future.
Yeah, I have that issue on rooted 1.2. Sometimes the only way to get it working is to clear cache, force stop, or reboot. Annoying, sure, but I don't install that many apps to make me pass on the rooted's better battery life.
Interesting.. I just had the same issue on CM 7.0.2.
I tried everything from other threads with no luck. Then I remembered that I disabled a lot of things with Autostarts. Autostarts is an app that can prevent other apps from starting upon certain events.
Apparently I disabled Marked from starting upon com.android.vending.*, some *intent.RECEIVE and some other events. Once I enabled these events I was able to download and install everything.
I read many people have the same problem and most of them probably don't have Autostarts app. My case could be coincidence or, maybe, some notification mechanism breaks in Android in some cases.
bengt_a said:
Now everything is working again. Just thought this might help someone else with the same problem in the future.
Click to expand...
Click to collapse
OK, now this is even weirder. I downloaded some new apps and updated all apps that needed updating, but after that no downloads worked again for about 12 hours. But then this morning miraculously they started by themselves - again. Seems very erratic...
Good for you...for me NOT
I have the exact same problem you reported (ie, apps I try to download to my rooted HTC Magic suddenly became stuck in "Starting download..."
I did everything you did and including checking in Settings -> Manage Applications, but all without success. What I have not done is enable "Market from starting upon com.android.vending*, "*intent.RECEIVE and some other events" as suggested by Miksha since I don't have a clue as to how to do that.
So if someone can advise me on how to "enable events" and/or has another solution to offer, I would be appreciative.
Laurie
LAFitz said:
I have the exact same problem you reported (ie, apps I try to download to my rooted HTC Magic suddenly became stuck in "Starting download..."
I did everything you did and including checking in Settings -> Manage Applications, but all without success. What I have not done is enable "Market from starting upon com.android.vending*, "*intent.RECEIVE and some other events" as suggested by Miksha since I don't have a clue as to how to do that.
So if someone can advise me on how to "enable events" and/or has another solution to offer, I would be appreciative.
Laurie
Click to expand...
Click to collapse
If you don't have autostarts app you probably don't need to enable anything. I had to enable events because I disabled them in autostarts prior to that. You could not do that without autostarts.
It is probably possible that events are disabled because of something else. The only way I know to check this is to buy autostarts (one dollar app).