android.process.acore error makes phone reboot while on phone - G1 Android Development

Edit: error message says android.process.acore
Don't really quite know what it is, but that's what I get
Not quite sure as to the rarity of this problem. But it has happened about 3 times already. Sometimes while on the phone, I get the error message and askes if I want to force close it. No matter which option I choose, my phone will go back to my sim lock screen as if it's booting up. Matter of fact, it is booting up.
Just wanted to know if this is isolated or if anyone else got this. I forgot, it happened once when I ran JFv1.41 RC30 and three times with RC33.

Happens to me too.

Happens here, too. I see it as the eccentricity of my little electronic brain.

happened a few times, bit annoying.

Happen to me 2 times since updated to rc33 1.41

Happened here too. I was just coming to see if anyone knows what's up, but I guess not yet. I'm running JF 1.41 RC33.

And here I was thinking I was the only one going nuts. It's weird because it did happen when I was on JFv1.41 RC30 as well.

i read a post on the tmobile forum that it could be the battery moving just slightly. i'll have to find the post again. They mentioned something about putting tape between the handset and the battery. Ill post if here when i find it.

http://forums.t-mobile.com/tmbl/board/message?board.id=87&message.id=28873&query.id=74936#M28873 here it is.

it's not that it's shutting off. it reboots. android.process error message

have you tried reflashing after a complete wipe?
this happens to me at times, but the wait option doesn't force close so i am ok with it.

yeah, i've done a wipe and reflash. we'll see how it goes.
but when it happens, it doesn't matter whether i press wait or force close, it does the same thing. reboot.

Edited original post. But the error message that pops up is android.process.acore. no clue to any of this.

did a wipe..solved the prob for me

Same here - moving from RC33 to ADP 1.1h w/o a wipe caused acore crashes.

Same here. I have my apps to SD card with JF 1.41 (soon 1.41 after the JFv1.42_RC33_MOD.zip finishes downloading) and a custom theme. I was assuming it had something to do with some of the app that was running in the background. However since I have over 100 apps stored to my sdcard it'll be pretty difficult to pinpont which one could be causing the problems (if any).

Related

Odd problem

Not sure if anyone has had this problem but I'm seeing some really odd issues, sometimes the screen starts moving really quick almost like flickering but from left to right as if I'm holding finger on the screen and moving it extremely fast. Sometimes it seems like touch screen doesn't work until I hit power and menu right after, also randomly core apps would crash.
I'm on jf1.42 rc33.
are you using any themes? I've encountered similar problems, but only after flashing multiple themes without wiping. i've never had any problems after a fresh wipe and reflash of JF 1.1*.
tchort said:
Not sure if anyone has had this problem but I'm seeing some really odd issues, sometimes the screen starts moving really quick almost like flickering but from left to right as if I'm holding finger on the screen and moving it extremely fast. Sometimes it seems like touch screen doesn't work until I hit power and menu right after, also randomly core apps would crash.
I'm on jf1.42 rc33.
Click to expand...
Click to collapse
i'm having similar problems but wasn't sure if something i did screwed it up, i was getting random core apps crashing on 1.41 RC33 and to test a script i wrote and an app made by another i completely wiped every thing to where the phone wouldn't start at all, i achieved this with adb shell wipe all
i wouldn't suggest doing that unless you have an update.zip waiting to be flashed to your phone, i put the phone back to warrenty standards and then started EVERYTHING all over so i could test the things i wanted to. when i finished testing i rooted and put 1.42 on and it seemed a little better all day until it popped up and phone process, settings, and core all three crashed at the same time about 30 minutes ago. my flash was 100% clean as there was nothing on the phone at all including OS, i completely wiped the system partition and data and refused to flash my nandroid back up since i didn't want the same problems. i hope someone else knows what's going on and we can fix this
I went from stock rc 30, rooted, JF RC 30, Themes (many), RC 33,JF ADP 1.1, then back to RC 33.
I had an issue of contacts not syncing, and the import contacts from sim caused a core force close.
So i did a freash install of JF 1.43 RC33 and it worked again. No screen problems but I did have a few core apps force closing. It hasnt happened since my last install of RC 33. Im running a modified theme now, my own with very little changes.
jonnybueno said:
are you using any themes? I've encountered similar problems, but only after flashing multiple themes without wiping. i've never had any problems after a fresh wipe and reflash of JF 1.1*.
Click to expand...
Click to collapse
No themes, if I do a wipe, what happens with paid apps that I have installed does anyone know?
Looks like it was the related to multi touch, after doing another wipe and installing a build with out multi touch the problem went away no more rapid screen movement and apps are not crashing

Reboot loop on ADP1.5H r3

My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.

Ut-Ohhh...Doomed to a hard reset? Process System Not Responding

Anyone ever see the message "Process system not responding". Here's the story.
Well, I've been installing apps like a loose cannon, figuring I may be dooming myself to a hard reset, and it may have come to pass.
Last thing that happened while the phone was running good, was I ran the demo of the 3D game XXXXXXXXX. I received a call, and had to hop away, and after that the phone became unresponsive. Looking at what was loaded with Advanced Task Killer, I did not see the game to kill, so I turned off the phone.
Now, it is taking a very long time to 'boot'. The Phone is Locked screen would pop up, and I'd try to slide it off, and it would slide about half off. Screen black except for the clock of the lock screen. And after sliding off half way, the screen would go black, as if it was off, but then the lock screen would come back.
Kept thinking that ultimately it would finish. After a bit I got the task bar at top, and it was saying preparing internal memory'Preparing Internal Mass Storage"; then finally " Media scanner running". Finally a few icons from the dock. But everything else still black.
Then finally it would come up with a big message "Sorry!. Process system is not responding. buttons for Force close, and Wait. I don't know if that is an Android message, or an app message. I tried force close, and it went back into the same iteration of events.
So the next time i tried a boot, I did not respond to the message for a while, and it seemed to be making progress behind the message. It went off, I turned it back on, it had lock screen, moved it off a bit easier.
Then finally it came up more screen things in place. Then again with a message "Process system is nto responding". Let it set 'til it went off again. This time it came up a bit futher, and this time it came up with window to select launcher. I selected TWiz launcher. Process message again, and I killed it this time.
Whewh...Still not resolved.
I guess if there are any suggestions short of hard reset, i'm interested in hearing. maybe one of you have had this happen. If it ever finishes loading, first thing I'm going to do is remove that game.
One thing that is a pain and I think contributes, is that so many apps load by default it seems. And the more you install the more that happens, from what I have seen. I know I don't have as many apps installed as I've seen others reference, but I do have 2-3 different memory type utilities that I've wondered if they woudl interfere with each othre, but they supposedly don't all load at boot.
Post long enough. I'll add more if I find anything interesting.
ewingr said:
Anyone ever see the message "Process system not responding". Here's the story.
Well, I've been installing apps like a loose cannon, figuring I may be dooming myself to a hard reset, and it may have come to pass.
Last thing that happened while the phone was running good, was I ran the demo of the 3D game XXXXXXXXX. I received a call, and had to hop away, and after that the phone became unresponsive. Looking at what was loaded with Advanced Task Killer, I did not see the game to kill, so I turned off the phone.
Now, it is taking a very long time to 'boot'. The Phone is Locked screen would pop up, and I'd try to slide it off, and it would slide about half off. Screen black except for the clock of the lock screen. And after sliding off half way, the screen would go black, as if it was off, but then the lock screen would come back.
Kept thinking that ultimately it would finish. After a bit I got the task bar at top, and it was saying preparing internal memory'Preparing Internal Mass Storage"; then finally " Media scanner running". Finally a few icons from the dock. But everything else still black.
Then finally it would come up with a big message "Sorry!. Process system is not responding. buttons for Force close, and Wait. I don't know if that is an Android message, or an app message. I tried force close, and it went back into the same iteration of events.
So the next time i tried a boot, I did not respond to the message for a while, and it seemed to be making progress behind the message. It went off, I turned it back on, it had lock screen, moved it off a bit easier.
Then finally it came up more screen things in place. Then again with a message "Process system is nto responding". Let it set 'til it went off again. This time it came up a bit futher, and this time it came up with window to select launcher. I selected TWiz launcher. Process message again, and I killed it this time.
Whewh...Still not resolved.
I guess if there are any suggestions short of hard reset, i'm interested in hearing. maybe one of you have had this happen. If it ever finishes loading, first thing I'm going to do is remove that game.
One thing that is a pain and I think contributes, is that so many apps load by default it seems. And the more you install the more that happens, from what I have seen. I know I don't have as many apps installed as I've seen others reference, but I do have 2-3 different memory type utilities that I've wondered if they woudl interfere with each othre, but they supposedly don't all load at boot.
Post long enough. I'll add more if I find anything interesting.
Click to expand...
Click to collapse
Well, the above post exactly describes what I have on my Captivate as well. Long boot times, "process system not responding", black screens, media scanner running/completed repeatedly, severe lagging...
Does anyone have any advice on how to deal with this issue? I've uninstalled my most recent apps, but it has not made any difference. Many thanks for any guidance!
Sounds like both of you need to restore to stock...Look in the Dev section for the Stock Odin3 1 click post..it is a sticky so it should be up towards the top..Follow the instructions and you will be back to stock...
The problems I mention above occur mostly during a reboot. The phone does eventually come up, with only occasional lagging still left (which may be more typical). I am torn between dealing with the lagging until Froyo is released (hopefully later this month) or perform the "restore to stock" you mention.
If I decide to "restore to stock", does that mean I lose everything? apps, messages, config, customizations, etc.
And if I lose everything, can I restore some apps with Titanium Backup? TB was loaded 2-3 weeks ago and I do have a full backup.
When Froyo comes, will it require the same or will it upgrade the existing OS and leave apps alone?
Many thanks for your response jhernand1102
I did that too, I sett a replacement lock screen wrong (because it asked me too) and there I was with out s phone for a few hours. The one click odin didn't work for me though. So I used the updated stock rom jh2 i believe. Look for the stock rom threads in developers forum as well as the one click odin.
If the one click odin doesn't work feel free to pm me with questions on the other rom.
Make sure you read it but they is a lot there that may confuse you.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
With titanium backup you should be fine. I haven't used it but that's the point of it. A reflash may be easier the finding the error and correcting the problem. And during any flash you may have some risk of losing something but I don't think, going to froyo will lose apps by design. Anyway you have titanium backup and samsung kies to help you keep everything.
Good luck!
Sent from my SAMSUNG-SGH-I897 using Tapatalk
tone_la said:
Well, the above post exactly describes what I have on my Captivate as well. Long boot times, "process system not responding", black screens, media scanner running/completed repeatedly, severe lagging...
Does anyone have any advice on how to deal with this issue? I've uninstalled my most recent apps, but it has not made any difference. Many thanks for any guidance!
Click to expand...
Click to collapse
I guess I forgot to post back what I had to do...having had no replies at all. I think I ended up in another thread.
Anyway...I did in fact have to reflash. Using the one-click which I believe is this thread is what I used.
ewingr said:
I guess I forgot to post back what I had to do...having had no replies at all. I think I ended up in another thread.
Anyway...I did in fact have to reflash. Using the one-click which I believe is this thread[/URL] is what I used.
Click to expand...
Click to collapse
Thanks to all for replying today! I will go ahead and re-flash to stock. I was hoping it would be longer (a few months) before I'd have to re-load, but I guess when you live on the edge (root and lots of installs), ya gotta be ready for things to go wrong.
I do love this phone though and Android after being on a BB for so many years! It is pretty much a 1.0, so we should expect bugs and work arounds until they work the kinks out. In a crazy sort of way, it is still fun to work through these gotchas. Thanks again!
Yeah. I really hated the idea of a reflash.
but, if you haven't yet, you need to look in the DEV thread, and look into Clockwork Mod and Rom Recovery. As well, you should get teh paid version of Titanium backup.
Between those two things, occasional reflash and reload is not too painful.
I've learned so much today! Got the paid version of Titanium Backup for an easy "restore all via batch" and also did the ROM Mgr / Clockwork Recovery (thanx ewingr). So, I now have the best of both worlds for getting out of a jam and looking forward to trying out any new ROM's that may come out; with ease thanks to these apps!

gTab went bananas!

I may have caused this...this a.m., I picked up my gTab when it was almost finished booting. I accidentally hit the power button, which turned the screen off. I had to fiddle with it a minute to get the screen on...it kept going right back out after I pushed the power button. I finally got it on (no reboot from here).
From there, it was nuts. I was greeted with having to pick my launcher again. Then I got a slew of force closes. Almost nothing would start, and the few things I did get to run (Mail'd, Dolphin) ran like they were new installs. Rebooting did the same.
Finally, I ran fix permissions from CWM, and it would start without FCs. However, anything I had tried to start before was still like new installs (EULA, setup wizards, etc). I managed to restore some of those via Titanium.
Still, it's not back to normal. Some recent apps (like, Fieldrunners from yesterday) no longer appear to be installed. Really fubar.
Could this be caused by the power button thing? Or is it a sign of impending doom? Is there a better way to fix this other than what I've done?
Oh, and I forgot to mention...I started Amazon appstore to downloading today's app, and then was restoring old apps via Titanium. In the middle of that, it played a sound I've never heard...like a few seconds, ending with this weird sliding reverb. But...I wasn't sure if that was Amazon's download finishing in the background? Usually I wait on the download. But it was longer than a typical notification sound.
TarheelGrad1998 said:
I may have caused this...this a.m., I picked up my gTab when it was almost finished booting. I accidentally hit the power button, which turned the screen off. I had to fiddle with it a minute to get the screen on...it kept going right back out after I pushed the power button. I finally got it on (no reboot from here).
From there, it was nuts. I was greeted with having to pick my launcher again. Then I got a slew of force closes. Almost nothing would start, and the few things I did get to run (Mail'd, Dolphin) ran like they were new installs. Rebooting did the same.
Finally, I ran fix permissions from CWM, and it would start without FCs. However, anything I had tried to start before was still like new installs (EULA, setup wizards, etc). I managed to restore some of those via Titanium.
Still, it's not back to normal. Some recent apps (like, Fieldrunners from yesterday) no longer appear to be installed. Really fubar.
Could this be caused by the power button thing? Or is it a sign of impending doom? Is there a better way to fix this other than what I've done?
Click to expand...
Click to collapse
Wow, I am experiencing the same situation as you. I didn't hit any power button either. I am on VeganTab 5.1 and now contemplating a flashing to a new GB ROM.
Sorry, man, it really sucks. Obviously, I didn't get much feed back as to what or why. Fortunately, I had a not too old backup with Titanium, and was able to get most things back with just a few clicks. Other things I had to set back manually. Took me a couple of hours to get back to what I thought was "right".
I did figure out the odd noise was a ringtone, and it had set my email notification to that ringtone sound. It wasn't even on my tab before, as far as I know. So I have no idea where that came from.
I'm thinking of Flashing to Cyanogenmod myself. But without knowing the why...it still won't make me feel too much better.
TarheelGrad1998 said:
Sorry, man, it really sucks. Obviously, I didn't get much feed back as to what or why. Fortunately, I had a not too old backup with Titanium, and was able to get most things back with just a few clicks. Other things I had to set back manually. Took me a couple of hours to get back to what I thought was "right".
I did figure out the odd noise was a ringtone, and it had set my email notification to that ringtone sound. It wasn't even on my tab before, as far as I know. So I have no idea where that came from.
I'm thinking of Flashing to Cyanogenmod myself. But without knowing the why...it still won't make me feel too much better.
Click to expand...
Click to collapse
Thanks TarheelGrad. I did a permissions fix and that has worked for me too. Not sure why it went bonkers.

Display / menus freezing and / or disappearing, system apps force closing

I've been searching this form for an hour or two now and still haven't found my issue, so here goes.
Just got an HTC Inspire 4G off of ebay and it arrived today.
The seller had mentioned that the phone was freezing / rebooting, but I figured.. that's because he's not running cm7, right?
Charged and booted up the phone and it turns out that the problem was a little worse than I first expected. I only experienced occasional freezing, and it only rebooted once, but there is a worse problem.
The phone loaded up fine, looked good, but tapping around on the home screen I got messages alerting me that system apps (htc sense, launcher, and even com.android.phone) had stopped responding or had shut down.
I hit the menu and go to settings. I scroll down the list and the entire list goes black. I hit home and it goes to a home screen, but with no launcher or icons. Basically, every few taps, the interface goes out. If you are on a menu it blacks out, if you are at home or press home after the menu blacks out you will get anywhere from pieces of icons / widgets to just a blank desktop. The live wallpaper even keeps going, but all of the interactive stuff quits. The disappearing menus didn't usually give app closed messages, they just went black. The home screen only gave app closed messages sometimes.
I thought this was a software problem, so I managed to root the phone and flash cm7. Everything booted good, but it still had the same problem of weird disappearing menus and home interfaces. I went ahead and flashed gapps and got the little intro thing about setting up my Inspire 4g that starts when you first boot your phone. I clicked through that but when it gets to connect wifi, the phone entirely freezes and I have to pull the battery.
I flashed inspiremod and nothing changed, tho that's for something else, so I'm not sure that's entirely relevant, but I was trying everything I could think of.
I'm definitely no expert on hardware, but it almost sounds like a ram problem, like it doesn't have enough to keep all of the interface going all the time and shuts it down or shuts parts of it down to work.. but I don't want to believe that. I'm really hoping that it's a software problem.
I got the phone at a good price and it came with an otterbox, so I won't be too disappointed if I can't get it fully functional, but it would still be a bummer.
Any help / advice / suggestions appreciated. Thanks, guys!
EDIT: I cleared the cache / dalvik cache before flashing / reflashing cm7, which I did once or twice
EDIT 2: Now if I leave it on the intro screen where it freezes it reboots after a minute or so. Gonna try flashing a different mod.. see if that helps.
That was a long post. But it was good, you gave a lot of info.
The cm7 zip that you downloaded, check the md5 checksum, make sureit matches whatever is in the op (first page) or wherever the md5 is, maybe where you downloaded it from. If it doesn't, download again.
Then,
from recovery,
Wipe data/factory reset.
Wipe dalvik
Format all partitions(except sd card)
Flash zip/rom.
Check if it works. If not, try using it without the sd card. If not, come back and report.
Sent from a dream.
Thanks for the reply and suggestions.
I check the md5, and it's good. I just did a factory reset and wiped cache and dalvik.. I'm unsure what you mean by format all partitions except sd card. I don't think I know how to do this with clockworkmod.
Started up without sd card and it still has the same problem. Looks great until I touch the screen, then everything disappears except the wallpaper.
Reboot in recovery and do it from there. You'll find format all partitions at the bottom... well, maybe. Cwm has an option to reboot in recovery, and I think if you press and hold the power button, select reboot and it will also ask you if you wantto boot into recovery. Cant remember if cm7 has it, it should.
After you wiped those, flash the rom. Stay in recovery and search for fix.permissions. Reboot.
Sent from a dream.
Just did that and re-flashed cm7, but the phone was still having the same problems.
I then repeated the process with a MIUI ICS rom and it seemingly worked for a little bit. I got a "Maps has stopped working" message, but I was able to slide back and forth through the home screens, and the menu came up. After I tapped though the menu a bit it started being weird again, but with MIUI the weirdness is different. It looked like the screen was divided up into 20 something smaller screens tiled across the display with messed up looking bits of screen in them.. weird..
If you are wiping correctly then I am out of ideas. I would say try a GB rom, however that is a strange issue and just might be a hardware problem. Tough, Im not sure.
Sent from a dream.
I've tried cm7, which is 2.3, and I've tried a 4.0.4 MIUI build and one other sense rom that didn't work well at all.
I'm wiping and flashing the same as I did on my LG p509, which works beautifully with cm7.
If it is hardware, hopefully it's something simple like the battery, and not bad RAM or anything serious..
Maybe if I keep at it I'll get it.
Thanks for all the suggestions!
Np. Keep us updated.
Sent from a dream.
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
awkwardcheesecake said:
I ordered a new battery for it, and that fixed the random reboots, which had been occurring more frequently, but the other problems were still there.
I flashed and re flashed and formatted and reinstalled a bunch, but still no luck. I then decided that I might take it by the local cell phone repair shop and see if they could fix it.
In preparation, I used aahk to flash the stock ruu with everything how it was when I got it. After booting it up, it seemed to be working ok.
I still get the occasional menu glitch, but it's so infrequent it's not an issue.
The phone still freezes up quite a bit when I'm using it, but it's nearly a useable device now!
Click to expand...
Click to collapse
Have you tried changing out the sd card? Having a bad sd card can cause all inds of odd issues
I booted it without an sd card before and couldn't tell the difference, but it had a lot more issues than just freezing then.
I haven't tried it since those other issues have stopped. I'll try that when I get home from work.

Categories

Resources