Problem: ROM Manager in the market is in a constant state of "downloading", sometimes it will show its downloading going and reaching 100%, but then it just goes back to "downloading". IF I try to cancel the download, the Market force closes.
Ok, so I noticed this problem after flashing one of the CM Nightlies, so in order to try to fix it, I wiped everything, went back to RC2, problem still exists. I think it was caused by Froyo's automatically restore of apps. I would think that in the initial bootup, maybe turning off those options could fix it, but that would require another wipe. And I've already done 8 or 9 in the fast few days and am just exausted from re-setting my settings. Normally I'd use Titanium Backup to solve that issue, but every time I do a restore, it soft reboots.
Anyone have any ideas?
tehseano said:
Problem: ROM Manager in the market is in a constant state of "downloading", sometimes it will show its downloading going and reaching 100%, but then it just goes back to "downloading". IF I try to cancel the download, the Market force closes.
Ok, so I noticed this problem after flashing one of the CM Nightlies, so in order to try to fix it, I wiped everything, went back to RC2, problem still exists. I think it was caused by Froyo's automatically restore of apps. I would think that in the initial bootup, maybe turning off those options could fix it, but that would require another wipe. And I've already done 8 or 9 in the fast few days and am just exausted from re-setting my settings. Normally I'd use Titanium Backup to solve that issue, but every time I do a restore, it soft reboots.
Anyone have any ideas?
Click to expand...
Click to collapse
You know... actually I've been experiencing a similar issue.
At one point with Market it would take at least 30 seconds for anything to show up when I open Market. Then to look for any updates by clicking Downloads it would take another 30 seconds or so. Not a big deal. But then somehow and for some reason it started showing up almost instantly! I would download and install the updates but then Market would forceclose almost immediately after the app finished installing. It made updating or installing several apps almost impossible. I tried wiping the data, clearing the cache, clearing the dalvik cache, etc. However the problem still occurs but not all of the time. It's pretty strange actually. I'd say about 75% of the time I get forcecloses and each time I try to get a logcat I don't have the problem. Go figure.
Related
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
Hi:
I have installed the JH7 update found here on xda. My phone is rooted with sideloading enabled. I will be honest, I have a ton of apps on my phone.
I have had SO many problems since the update. I had to re-install the update 3 times, because after HOURS of trying to enable sideloading it still wouldn't work. After the third install I was finally able to enable sideloading.
Now, my problem is, some apps are crashing as soon as I open them. The 2 biggest culprits are e-mail, and Shop Saavy. I click to open them, they open for between 1-5 seconds, then close.
Any thoughts? I am desperately trying to find an answer, I would hate to have to hard reset, since I have already spent in excess of 10 hours trying to get my phone to where it is now.
I did have task manager installed, but the problem persists even after uninstall. Also, I used task manager prior to the update with no problems.
Thanks so much!
PS: If I do have to hard reset, can I simply use Sprite backup to restore everything, or will there still be some things that need configuring (ie. home screen etc)?
Quick idea: Download ROM Manager from the Market and run "Fix Permissions." Sometimes that will clear up any force close issues.
a.n said:
Quick idea: Download ROM Manager from the Market and run "Fix Permissions." Sometimes that will clear up any force close issues.
Click to expand...
Click to collapse
Hi:
I tried your suggestion, but sadly, it didn't work
Thanks so much for your suggestion though!!
PS: The apps just close, I do not get an error message. I have found some posts with people with e-mail crashing issues, but it seems that they do get a force close message, and that it is Exchange related. I do not use exchange.
Now that you mention it, I have had the stock email client force close upon load a few times since the update, and it had never done that beforehand. Maybe try reflashing just the kernel?
swedishcancerboi said:
Now that you mention it, I have had the stock email client force close upon load a few times since the update, and it had never done that beforehand. Maybe try reflashing just the kernel?
Click to expand...
Click to collapse
Hi:
Sorry to be a dunce, but how do you reflash just the kernel, and will it delete everything (apps, data etc)?
Thanks so much!
My 2 cents:
I don't know why it took hours to enable sideloading, i spent only a few minutes - but that gives me the impression that something might seriously be broken.
I would back up everything you want to save and do a master reset - it will clear all data, but you hould be JH7 fresh. If you want to go further, you can reflash factory JF6 then update to JH7. Either way, make sure you check basic apps first before installing a bunch of stuff.
I don't subscribe to the blind grasping at straws method of fixing things. After to many hours it is just faster to rebuild. If you knew what was wrong, then fix it, but if you don't then rebuild.
I agree. If you are needing this to function properly now, then just reset back to factory and start over. But if you are like me and just have to know what is broken.....that could take a while. I always try to make sure I don't have anything on my phone I couldn't live without just for instances like this.
Flashing just the kernel can be done with Odin (search the forum). There is a "stock captivate kernel" floating around (I'd post it, but I'm sure we don't need files posted multiple times). Instructions are included in that post. Basically you need a computer, USB cable, drivers, and bollocks. However, as mentioned, this is a shot in the dark. Random force closes could be caused by a variety of issues ranging from corrupt software, file system inconsistencies, to hardware failure, phase of the moon, appetite level, etc....
The safest bet is to backup everything, flash stock (if needed) and take it back to AT&T for a replacement.
Good Luck!
Hi:
Thank you so much for the replies, and help.
I decided to go ahead and reflash JH7. This has fixed the entire problem. So, apparently it was software related.
I am now going to install all my apps one at a time, in order to find the culprit. Hopefully it is one I can live without lol.
Anyway, thanks again!
Did you ever figure out what app was causing this? I am starting to get annoyed with my force closes and was going to re-flash and re-add all apps.
Hi:
Well, I MAY have figured it out. I had a million programs installed, and it just seemed like too much work to try to figure it out.
So I just re-installed JH7, and started from scratch, so I'll never really know what the problem was.
However recently I started having the same problem again. Since I started from scratch I have been gradually installing programs, just in case one cased a problem.
Well, it seems my problem was Startup Manager. I did NOT disable any system programs etc..., but it was still causing apps to crash, as soon as I froze it with Titanium Backup Manager, the problem stopped.
So, if you happen to be using Startup Manager, I would try uninstalling/ disabling it. Or, if you use a task manager, try not using it, maybe it is stopping whatever Startup Manager was disabling on mine.
Anyway, I hope this was of some help.
Oops, sorry, the program causing my troubles is actually called Startup Auditor.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
This is not a reason to start a new thread in the Development forums.
Support and Q&A for custom roms should take place in their appropriate threads. Use a bit of common sense, courtesy, and patience -- people will help you.
Please read the rules of posting new threads again here: http://forum.xda-developers.com/showthread.php?t=788800
anoneemooz said:
Hi guys!
So my current configuration is in my sig, except that I was using v8 of Doc's JPO ROM and the latest Super Optimized Kernel at the time... But this has happened twice on two different kernels so I'm not sure that matters all that much.
I don't know what more to say then what simply happened during both those times:
The first time it happened, I was in the default Samsung Song Player app..I tried playing a file then my phone suddenly locked up, so I pulled the battery. Upon reboot, the phone was still working fine so I tried playing the file again...the phone again locks up and I pull the battery again. But this time when the phone reboots, it takes a looooong time in the shiney S boot part. Then much to my horror, I am taken to Phone Setup! :| And even worse, after I went through all that..I still saw my same wallpaper and such, but then my apps (not system apps) started force closing all over the place! (Without being run, they just suddenly start force closing while I was still at the homescreen and during phone setup..)
I had to factory reset to get my phone to work again..losing everything.
This happened again, this time I was in the Market just doing some updates..then again lock up -> battery pull -> reboot -> force closing apps everywhere -> factory reset to fix... :|
Any ideas why this happens and how to prevent this?
Addtl info: the first time this happened, I still didn't apply the system fix thing (cus it didn't exist at the time). The second time though, I followed the instructions to prevent the system corruption thing.
Click to expand...
Click to collapse
1) Lock ups most likely due to removing drm file from system apps.
2) Your using lagfix (I assume) and when you pull battery data corruption is very likely on some configs.
3) Read rules before posting.
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.
Currently have a G890A, AT&T, Android 6.0.1, Baseband: G890AUCS5CPK4
I've spent days of time trying to understand and fix repeated freezes/crashes, and am curious if you think my understanding of the problem is likely accurate and if the next steps make sense. Below are current issues, my previous solution attempts, best guess at the problem, and next steps to solve it. Thanks for taking the time to read this!
Issues:
- Starting at the Android 6.0 update, the phone began freezing intermittently when installing/updating certain apps.
- Freezing was unaffected by subsequent firmware updates
- Freezes happened before I could see which apps were starting to auto-update.
- During a freeze, the phone gets warm and drains the battery quickly. Power+down will reboot the phone, then it usually freezes again.
- After the first freeze, freezes and crashes would then continue on bootup, sometimes over 20+ reboots, usually while drawing "SAMSUNG" letters or soon thereafter
- Eventually whatever was installing/updating/uninstalling seems to take, and the phone finally stops rebooting.
- Disabling auto-updates prevents freezing
- After a factory reset it takes hours of rebooting, getting lucky enough to see the home screen, and for luck to hold long enough to open the play store before a freeze happens
- Freezing does not happen when updating every app. Installing/updating Google Inbox and Khan Academy both caused 20+ reboots/hangs. Trying to uninstall Khan Academy produced another 20+ until the uninstall finally seemed to take. I haven't tried to uninstall or update Inbox.
Current efforts to fix the problem:
- Safe mode: no improvement
- 3 factory resets: no improvement
- 3 factory resets + safe mode: no improvement
- Disabling auto-updates: effective, as long as I never install or update apps
- calling ATT: They said go to a Samsung rep at Best Buy
- talking with Best Buy Samsung rep (closest is an hour drive away): Best Buy says they can re-flash G890AUCS5CPK4, but my concern is that whatever got corrupted in an earlier update won't be fixed by re-flashing that version.
- calling Samsung: Samsung says they'd be happy to look at it if I send it to them a couple weeks. They also state that they'll send it back untouched if I try flashing it myself.
Best Guess About the Problem
Something got corrupted in Play Services during the 6.0 update; something that runs early in bootup and continues any in-progress installation/update processes.
Next Steps
- Determine on this thread whether it makes sense to reflash G890AUCS5CPK4 at Best Buy
- If so, take the phone to Best Buy for a reflash. If not, find a backup phone for a couple weeks and send the GS6 to Samsung
- Prefer not to try flashing it myself since I have no experience and don't want to brick it or remove the chance for Samsung to fix it as a backup plan.
Do the best guess and next steps make sense? I really like the s6 active. I've had it just over a year and want to keep it for a while. It's gone rafting, kayaking and hiking in all kinds of weather, and operated flawlessly in and out of water the entire time. Fantastic phone until this issue.
Thanks again!
Adam
How are you installing your apps? One by one from the play store, all at the same time from the play store, or by some other method (from an archive of some kind), which might be corrupt.
anneoneamouse said:
How are you installing your apps? One by one from the play store, all at the same time from the play store, or by some other method (from an archive of some kind), which might be corrupt.
Click to expand...
Click to collapse
@anneoneamouse, Great question. Thanks for asking. I did a few of them via Samsung's Smart Switch, then uninstalled most of those. I didn't think about the APK's stored by Smart Switch being corrupted somehow. Trying reinstalls from the Play Store now.
And... it's been about 3 hours. A number of previously failing apps worked when installed from the Play Store. I was excited. Then I uninstalled Google Inbox and reinstalled it from the Play store, and the phone froze. Multiple reboots never got it past the loading screen after that. Eventually I did a factory reset. The phone still froze with only factory apps. No non-factory apps installed from any source. Four more factory resets later, no progress. It's probably time to send this critter to Samsung.
Have you tried booting into the recovery menu, and clearing all the cache areas? I'm not sure that a factory reset is equivalent to a complete wipe.
How are you uninstalling Google inbox?
anneoneamouse said:
Have you tried booting into the recovery menu, and clearing all the cache areas? I'm not sure that a factory reset is equivalent to a complete wipe.
How are you uninstalling Google inbox?
Click to expand...
Click to collapse
Sorry for the slow reply. Just saw this. I did cache wipes followed by resets, which also log to the screen that they're doing a cache wipe. Uninstalling/reinstalling inbox stopped being an issue because I could never get far enough to install Inbox again from any source. As soon as I logged in with a google account during setup, the factory apps started updating and the hanging/crashing began. Sent it to Samsung.
Appreciate your help!