Database Develop

Froyo won't stop freezing

However ironic the title may be, I updated my fiance's non-rooted N1 to the official release froyo and from the very beginning, it will work for a few seconds, then it will just freeze for a few minutes. I have patiently gone through and stopped almost every process, and nothing will fix it. It still just freezes constantly and usually requires a battery pull to get it to work at all. I told her she could try a factory reset, but she would rather just go back to 2.1-update1. I'm going to try renaming 22607-ERD79-update-nexusone-stock-signed.zip (or PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip) to update.zip and reflashing it in the stock bootloader on her phone, but I feel like that won't work because it is a previous version and not really an update. Does anyone have any advice on how to just bring her back, or perhaps how to fix her freezing problems on froyo?
Thanks

Try a fresh flash with no apps installed and see how its doing.... if it doesn't freeze then its a app probably ...

I'd like to try that, but she doesn't want to do a fresh install. I'd imagine that if an app didn't freeze 2.1, it wouldn't freeze 2.2. Besides, 2.2 freezes even after killing all applications and services.
I guess I'm really looking for advice on getting it back to 2.1 without rooting her phone.

dnoggle said:
I'd like to try that, but she doesn't want to do a fresh install. I'd imagine that if an app didn't freeze 2.1, it wouldn't freeze 2.2. Besides, 2.2 freezes even after killing all applications and services.
I guess I'm really looking for advice on getting it back to 2.1 without rooting her phone.
Click to expand...
Click to collapse
Just do a factory reset in settings and security ... no reflash. Just cause a app didn't freeze 2?1 doesn't mean it wont freeze 2.2. And even if the apps currently not running or closed, it'll still wack ya phone. I had a freeze every hour yesterday with my chosen apps installed, flashed 3 different times to no avail. Now I factory reset with only 4 definitely needed apps installed and haven't gotten a freeze yet. So my conclusion is 2.2 doesn't like something I've installed so I'm adding a few apps every hour to fins the cause.
Since I factory reset with my few apps. I haven't had a freeze yet all night and morning long..

I'm having the same issue too. Not sure what is going on with FRF91, but my phone keeps freezing and I need to pull the battery to get it to respond again. I agree it very well could be an application, but installing every application one by one and testing would be a pain. Is there a better way to figure out what is causing the phone to lock up? Any time of log on the phone that would be helpful?

Papa_I said:
I'm having the same issue too. Not sure what is going on with FRF91, but my phone keeps freezing and I need to pull the battery to get it to respond again. I agree it very well could be an application, but installing every application one by one and testing would be a pain. Is there a better way to figure out what is causing the phone to lock up? Any time of log on the phone that would be helpful?
Click to expand...
Click to collapse
Have you tried a factory reset? That might fix it... let us know what you find. I've noticed a couple of freezes as well, but I'm not able to factory reset it just yet because I'm out of town and don't want my phone down for even half an hour.

I have to pull battery a couple of times a day.
I'm having the same issue on 2.2. I have done 2 factory resets. Nothing. N1 call center said slowly reinstall all apps to see if an app may be doing it. No luck.

Is anyone having issues with the screen still being responsive while on a call? My screen will go black but you cant still hit keys when you have up against your face.

I'm betting that you do not have a custom recovery and nandroid backup, or you wouldn't be asking.
I highly doubt that the phone will let you push the old firmware on top of the new one if you don't have a hacked recovery and a test-signed zip. But I don't know - you could try it...
Here is what I would do:
1. Install a custom recovery (like Amon-Ra 1.7.0.1), either by unlocking the bootloader, or by following the directions in the dev forum for doing this without unlocking if you have the fear. If you already a custom recovery, don't worry about this step.
2. Now boot into recovery and make a nand backup!
3. Now go ahead and try this one of two ways - either delete one application at a time until you figure out which one is killing you, OR do a factory reset and then re-add one application or a small number at a time until you figure out what is crashing you.
If it were me, with my 100 applications, I'd probably add 5 or 10 at a time. Once you get crashes after one group, try removing those applications one at a time until the crashes stop. The last removed app when the crashes stop should be the answer.
Of course, since you'll have to have adb running to get a nandroid, you could also just take a logcat of the running, crashing phone and see what app is killing it there.

I did a factory reset today and will report back letting everyone know if that has fixed the issue. Everyone else that is experiencing the freezing issue, did you have Beautiful Widgets installed?

I have that installed, is that whats cousing it?

Beautiful Widgets was killing my N1, too. Freezes, sluggishness, etc. I uninstalled and wiped my cache via stock recovery. No problems since.
I'm on stock FRF91 BTW.
Sent from my Nexus One using XDA App

It appears that's the root of my issue. I would uninstall the application and clear the cache and see if that helps. Report back with your findings.
Sent from my Nexus One using XDA App

[Q] Need Help. "android.process.acore FC"

Hey guys last week my phone has been starting to act real buggy and I began to get a FC saying android.process.acore has stopped unexpectedly. Has anyone experienced a similar issue as this? The phone has completely stopped working and I can't do anything on it. I've tried a hard reset, soft reset, reloading 2.1 and practically everything else. Any help would be greatly appreciated thank you!

When you say the phone completely stopped working, what do you mean? You can't even power it on? Or it comes on but just won't make calls, send texts, etc? Provide us with some more details please. Are you rooted? If so, what ROM were you using? etc. etc.
Also, did you install any new apps lately? Some cases of this FC error have to do with an installed app that is malfunctioning, and simply uninstalling the troubled app, then rebooting, will solve this.

I am having the same trouble, but my phone started by saying that I was running out of space, though I hadn't installed anything new. I am thinking it is with the latest Facebook update. The battery runs out fast and the phone has filled up and now it's crashing.
I think I am going to uninstall the FB update and see how that goes.

tuffdadsf said:
I am having the same trouble, but my phone started by saying that I was running out of space, though I hadn't installed anything new. I am thinking it is with the latest Facebook update. The battery runs out fast and the phone has filled up and now it's crashing.
I think I am going to uninstall the FB update and see how that goes.
Click to expand...
Click to collapse
The newest Facebook version does drain the battery really fast -- it basically prevents the phone from sleeping. See this post on how to fix it: http://forum.xda-developers.com/showpost.php?p=7572716&postcount=948
Or of course, just totally uninstalling FB would fix that too

chromiumleaf said:
When you say the phone completely stopped working, what do you mean? You can't even power it on? Or it comes on but just won't make calls, send texts, etc? Provide us with some more details please. Are you rooted? If so, what ROM were you using? etc. etc.
Also, did you install any new apps lately? Some cases of this FC error have to do with an installed app that is malfunctioning, and simply uninstalling the troubled app, then rebooting, will solve this.
Click to expand...
Click to collapse
Well I keep getting that error everytime I FC it and it prevents me from doing anything. The touch screen won't work at all either. I was rooted running PureHero but I just flashed 2.1 back on it (the official one from Sprint) and the problem still existed. I did a hard reset and the phone continues to show this message even without any apps installed.

Wow, that seems strange then. If it's doing this on just plain stock without any apps installed then it sounds like it could just be something defective with the phone itself. I would say re-run the official stock 2.1 RUU from Sprint (to remove Root) and then take it back to a Sprint store and see if they will replace your phone.

chromiumleaf said:
Wow, that seems strange then. If it's doing this on just plain stock without any apps installed then it sounds like it could just be something defective with the phone itself. I would say re-run the official stock 2.1 RUU from Sprint (to remove Root) and then take it back to a Sprint store and see if they will replace your phone.
Click to expand...
Click to collapse
Right I've tried putting the 2.1 on again and again but the same problem. And I went to the Sprint store to ask about it and apparently I have water damage so they didn't do anything... I guess im SOL with no insurance...

NSandhu11 said:
Right I've tried putting the 2.1 on again and again but the same problem. And I went to the Sprint store to ask about it and apparently I have water damage so they didn't do anything... I guess im SOL with no insurance...
Click to expand...
Click to collapse
Bummer dude, that sucks. Well, I think I still have my Samsung Rant if you need to buy a different phone....I'll sell cheap, lol j/k

chromiumleaf said:
Bummer dude, that sucks. Well, I think I still have my Samsung Rant[/URL] if you need to buy a different phone....I'll sell cheap, lol j/k
Click to expand...
Click to collapse
Lol ya. I'm gonna give Sprint a call and see if they can do anything, but my mom's line is ready for an upgrade so I'll probably get the Epic 4g from her line and buy her a BB or Pixi.

[Q] I rooted Captivate w/Froyo 2.2 - Now lots of problems

I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T

My vote is to go with a custom ROM. It will solve all of these problems. Cognition is the most similar to stock and is quite easy to flash. As for the problems you are having, I don't know what to tell you.
Try Cognition 4.5.3. You won't be disappointed.

Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?

Well, not busy tonight. Watching pre-season football.
Flashing a Froyo rom is not too bad. Since you have stock 2.2 it will be a little more tricky than if you were still on 2.1.
First, what is your build number? look on the sticker under your battery to see a four digit number beginning with either 10 or 11.
I will private message you with more.

taltal13 said:
Thanks for the quick replay Jack especially on a Fri night. What exactly do I do? Is it difficult to do?
Click to expand...
Click to collapse
Make sure you READ EVERY LINE OF THE OP. When you think you got it, read it again, then give it a shot. For the time being just factory reset your phone, should clear up some of your issues. Good luck
sent from long ago, in a Galaxy far, far away.

^^^ he's right. READ, READ, READ... until you're sick of it. It will pay off and keep you from bricking. Sorry I didn't mention that. But I will be glad to help you if you need.

and if (or when) you manage to brick it do not panic,, go back and read some more,, seems that almost everything an idiot like me can do is fixable,, and most normal people are pretty safe,, they are not going to kill their phone,,,,if they read and follow instructions,,,not doing those two have found my phone in some pretty unresponsive states,, but I am running mosaic VI now and loving it,,but have been on so many I had to go look,,and have finally I hope learned the value of reading ( and those other people probably do know more than me so I should not think I know better ,,,yet)

taltal13 said:
I finally updated to the official AT&T Froyo 2.2 probably about a month ago. Everything was working great. I wanted to root/enable sideloading apps/unlock. I used SuperOneClick 2.1.1. The root worked fine (at least I think so). I was not able to enable sideloading apps so I read online how to change the value of sideloading apps from 0 to 1. I also unlocked the phone using the Galaxy S unlock app from the the Market.
Almost right after the SD Scan would take a long time and then I would get a red SD card symbol saying "Low on Space - Database storage is getting low". I tried clearing cache's to fix the problem. It didn't fix anything. Soon thereafter I started getting "Message Memory Full - Incoming messages rejected due to full...." I cleared phone log/txt messages but it hasn't fixed anything. I looked at my internal and external SD card. My external card is 3.68 total with 17MB available. My internal has 12.67GB available.
Today all of a sudden if I try to look at my missed call I get "samsung captivate the application phone (process com.sec.android.app.dialertab) has stopped unexpectedly. Please try again". I get similar messages trying to open Gmail. I haven't gotten it on any other apps yet as far as I know. It vibrates like crazy when the apps crash.
Can anyone help me with the problem? It's making my phone useless right now and my battery is dying much quicker than before. Thanks!
-T
Click to expand...
Click to collapse
Not sure how much of knowledge you have gained before doing these attempts of changing some values to enable side-loading...
I would suggest to do factory reset since you are still on FROYO and see if this does the magic.
If it gets locked back to AT&T, I suggest just talk to AT&T rep to unlock & side-enabling. Once all is well, you can do rooting as you did before. Hope this helps to solve your problem.
For any other help, we have XDA here and get some time to go through forums. As others suggested, please read, understand and act.

A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal

taltal13 said:
A day after I posted this the phone seemed to be working right. However Jackman pointed out if it happened once it's almost sure it will happen again. I tended to agree with him so did a factory reset and then flashed with Cognition 4.5.3 with a lot of Jack's help of course. Right now seems to be working flawlessly. I do like this whole custom ROM idea. Even thinking about buying a used Captivate on ebay just so I can mess around with other ROMs. Thanks everyone for your help & input. If you have any other suggestions my ears are always open...
Tal
Click to expand...
Click to collapse
Just for a bit of encouragement ive been using Cognition 4.5.3 as my daily driver for the past 4-5 months and have never had a single issue with great battery life. Ive tried numerous other roms on this forum and always have run into a boot loop, force close, or other random issue that makes my phone unstable but with Cognition I experience what my phone was meant to be like.

[Q] Stock Dialer Gone Bad, Used Odin and Kies, Still bad! Help!

Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign

^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.

I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.

A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.

process acore has stopped hell

I know there is a lot of information on this, however my problem appears to be a bit more chronic all of a sudden. If anyone has any idea what this is (especially if it is a possible hardware issue), I would really appreciate it.
This started the past weekend and has been driving me crazy ever since. After uninstalling facebook on Saturday, I got the pop up. Rather than messing with trying to fix it, I went and reflashed the rom. While restoring all my apps, the error popped up again. Convinced there as something up on the phone or the sdcard file system, I restored back to stock 4.4.2 with odin. I rooted, went through the same restore process and after one of my reboots, it came back. Finally I searched and did "restore app defaults" in the application manager. That worked for a while, but came back a few times, until finally that method wouldn't fix it anymore.
Last night I reflashed with odin again. This time I didn't root. Everything was fine all day until I decided to uninstall twitter and the acore message is back. Doing an app reset did fix it again, however I am afraid at this point to reboot the phone or do anything else.
I had this problem maybe once about 3 months ago, now I can't get ride of it no matter what I do. I should also point out that I did not do a TiBu restore or anything, I installed all my apps through the play store.
Thanks in advance guys

Have you tried going into application manager and clearing data for contact storage? It's what I do when I get this error message

majortaylor said:
Have you tried going into application manager and clearing data for contact storage? It's what I do when I get this error message
Click to expand...
Click to collapse
I did that, however it usually didn't work. I had to reset all application defaults and the issue usually went away. During one of my reflashes, even that didn't work anymore.
Seems like the issues started when either I turned off one of the bloatware apps, or deleted something. Sometimes the acore would start right away, other's after I rebooted the phone.
This last time, I got the phone setup, I got 2 acore's early on (Clearing app defaults worked both times). I didn't do anything else to the phone for a few days. Last night I finally rooted, installed safestrap and my other root apps and so far everything seems stable. I will just do a twrp backup before removing anything in the event things go bad again.
What still bothers me is don't know what caused this all of a sudden. I've been flashing roms for years and never once had this sort of problem. I will all set to consider this a hardware issue, until it finally settled down.