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
Related
I might be a senior, but we're all still learning
So my question is, when you wipe/reflash something, is there a way to keep all the Protected/Paid apps installed when you start up? Normally, a wipe will break all of your protected/paid apps and list them in the launcher as "com.XXXX.XXXX" or even "org.XXX.XXX". Launching them results in the infamous Force Close box.
This is indeed on Apps2SD and with Cyan's new 3.9
Have you tried running the fix_permissions script?
I'll reboot and run it now
Didn't fix them, unfortunatly :/
lukekirstein said:
Didn't fix them, unfortunatly :/
Click to expand...
Click to collapse
Back up all your apps using MyBackupPro or Backup for Root Users. I have all mine on my sd so they re-install automatically. I don't have to do anything, and they don't load up as com.xxxxx.htc.. blah. But I use Backup for Root Users when I do have to format my ext2 and this brings them back no problem.
Hmm interesting. I've never used Backup for Root Users with apps, just the data. Takes too long for me with all my apps...but I managed to find the spare time to re-install, that was fun . Thanks guys!
my advice to anyone on here who is going to play with anything on their phone:
before you do it, make sure you have enough time allotted to fix EVERYTHING, as if you were starting from scratch. that way, before you begin, you can have the peace of mind to know that if anything goes wrong, you've got all the time you need to fix it.
murphy's law: whenever you think you're in for a quick fix, theres a long road ahead of you.
kusotare said:
my advice to anyone on here who is going to play with anything on their phone:
before you do it, make sure you have enough time allotted to fix EVERYTHING, as if you were starting from scratch. that way, before you begin, you can have the peace of mind to know that if anything goes wrong, you've got all the time you need to fix it.
murphy's law: whenever you think you're in for a quick fix, theres a long road ahead of you.
Click to expand...
Click to collapse
Wouldn't hurt to have a backup unlocked GSM phone too. That's one of the nice things about GSM-based technologies... if your phone dies for whatever reason, pop the sim out and put it in a backup phone. You'll still be able to be contacted while you fix the primary device.
I had this issue too with the same Rom and with the previous version. This is how I solved it.
First I deleted all apps, etc from my SD card while it was connected to my Mac, just made it easier. (I was also running a previous Apps2Sd, not the one built into the mod, which I believe was the root of the issue. I didn't use the old apps2sd once I upgraded the ROM, and I may be way off but I find it suspect.
Then I wiped and reinstalled the ROM. Yea I had to reinstall my apps but...
...before doing all that I had tried removing and then reinstalling an app. A reboot/power cycle of the G1 would result in the icon being gone again and that ugly error message in regards to the app.
When I did the step I mentioned prevously, delete, wipe, etc I've not had any further issues.
I've also since updated by fs from ext2 to ext3 but that was after the fact.
Cyan's mod is by far my favorite and consistently stable and well documented. I'm glad I was able to correct my issues.
kusotare said:
my advice to anyone on here who is going to play with anything on their phone:
before you do it, make sure you have enough time allotted to fix EVERYTHING, as if you were starting from scratch. that way, before you begin, you can have the peace of mind to know that if anything goes wrong, you've got all the time you need to fix it.
murphy's law: whenever you think you're in for a quick fix, theres a long road ahead of you.
Click to expand...
Click to collapse
Have to agree completely with the above. Hope for the best but plan for the worst.
lukekirstein said:
I might be a senior, but we're all still learning
So my question is, when you wipe/reflash something, is there a way to keep all the Protected/Paid apps installed when you start up? Normally, a wipe will break all of your protected/paid apps and list them in the launcher as "com.XXXX.XXXX" or even "org.XXX.XXX". Launching them results in the infamous Force Close box.
This is indeed on Apps2SD and with Cyan's new 3.9
Click to expand...
Click to collapse
Did you manage to find a solution to this problem? If you did, could you please post it. I flash different ROMs often. Having to reinstall my paid apps over and over again is starting to get very annoying.
Haven't tried yet. I might try the MyBackup Pro option, as I heard it's a great app anyways. But I know what you mean
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
this seems to be happenning very ofthwn for my phone, and it hasn't disappeared even with using a different ROM or kernel.
I'm on tweaky's 2.3.5 JVS now, and I sometimes when I am in dialer and I type in 3 numbers, it just closes itself and shoots me back to the homescreen. it keeps doing that, and I'm unable to dial out because of this, until after a while and it irritates me to no end.
this also seemingly happens with me using whatsapp or Viber, where when I want to reply a message, after whatsapp has loaded up, it shoots me back to the home screen.
now, I've tries to get rid of my task killers, and saw no changes whatsoever, so can someone enlighten me on what's going on, and how to rectify this????
You say you did try a couple of roms, have you performed a factory reset or re-partition when flashing the roms?
Yes I did, all the time with Odin... Happenned with Darky, symply, simplicity, all of them
I wipe data and factory reset, even format the storage.
I'm not sure but as you said you've tried to change both rom and kernal yet there seems to be some sort of constant.
Are you backing up your apps accounts data etc and then restoring data? or the apps themselves? Because this can cause in-compatibilities.
If you do then start from scratch install only apps but only from market and one by one. Try play around half a day or something (or if you know a definite trigger see if it happens) if nothing then install another of your old apps.
Also have you tried installing no apps just use those that came with the rom. If it still happens after everything has been wiped (cache, dalvik cache, repartition, format sd, no external sd) then im inclined to say its hardware... When did this start happening?
Hi, thanks for the reply.
I back up my applications using Appmonster, and this retains just the program itself, I reset everything back to how it was after I wipe.
I'm not sure, I tried to think on whether its an issue with like lacking of ram or something, because SOMETIMES it behaves after I kill of some apps and free up some RAM.
I also thought it might have been a task manager which is doing it but uninstalled that and nothing changed.
I tried to install the programs slowly and individuality and it was a VERY slow and painful process, and it got me really nowhere, as like after i uninstalled and backtracked it still happenned.
I was wondering to myself if it was app incompatibility, as I have a relatively large list of apps installed.
It doesn't seem to do it if its fresh, so I'm not too sure myself.
Any ideas per se? Maybe a list of my installed apps? IDK I'm trying to find a solution to this.
At this rate I'm tempted to get a new phone
No harm in sharing the list of apps I guess, maybe someone more knowledgeable can give you a hand with that info.
Okay, But are there known apps that do this to the system? doesn't seem to happen for games but for Dialer and Whatsapp and Viber.
Everything else just works peach.
I just realised it might take more than a while, perhaps I will try a slow install of only the absolute necessities then.
I'm just wondering if I'm the only one who's encountering this issue. I'll try a week of the basics soon.
Thanks anw. :3
hamsteyr said:
I'm just wondering if I'm the only one who's encountering this issue. I'll try a week of the basics soon.
Thanks anw. :3
Click to expand...
Click to collapse
It happened to me too.
I am also seeking the reason.
But the latest ROM Gingerreal v7.14 was okay..
That's really strange then.
Perhaps its the combination of apps... I don't know, I'll try getting rid of the unnecessary and see if it'll cause the same issues.
dialpad problem and other
sas_sas said:
It happened to me too.
I am also seeking the reason.
But the latest ROM Gingerreal v7.14 was okay..
Click to expand...
Click to collapse
good to me the same thing happened to good use Viber but not if I used other application in restored times I have installed from scratch I have used several JVS rom and even some custom rom and also jvr stock but it is more about the JVS rom because jvr step with me after a few occasions,
JVS install and initially as well but in the kernel changes and custom rom rom that has happened to me in all I've used lately.
To the admins I apologize if this is in the wrong section if it is please move it accordingly.
Hello everyone, I have an issue, hopefully someone can hel me and it starts like this. I and everyone else have been waiting for months for a safe root method and a recovery system such as TWRP OR CWM just incase I fudge something up flashing custom roms so I can always go back to stock. I came across a safestrap article and decided it was something similar to what I was looking for. So I decided to root using the big K. I know not the best choice, you can boo me now.
After a successful root, I installed safestrap. Unfortunately safestrap kept crashing upon starting the app, I couldnt even get it to set up. thats fine, I was just going to unroot and keep on living life, but then I stumbled upon Xposed installer, that modified and tweaked like a custom rom but without all the risk according to a website. I said hey thats worth a try and I did. After the Xposed installer setup and a reboot, I wad looking for mods on the web and all of a sudden my apps and system files started crashing to the point that I could not use my phone. I immedeately uninstalled Xposed installer ss soon ad my phone stabalized and unrooted.
I thought everything was good, 4 hours later the apps and system files started crashing again, so I did a reboot and I noticed that custom with the lock came up on intial startup. though I was told I was unrooted by the K program and even double checked using a rootchecker app, which stated I had indeed an unrooted phone. I did another reboot and no custom or logo came out. At this point I just wanted a working phone and As much as I hated doing so I did a factory reset. This seemed to have fixed the problem, but 4 days later my phone randomly went into a bootloop. I couldnt get it to stop so I took out the battery and that did not fix it.It was strange becuase I thought it might have been unrelated since it wasnt doing this when I had the issue with Xposed installer.
After yet another factory reset my phone seems to be fine, its still too early to tell though since its only been about a day. I had the normal google playstore and gvoice app crashing...Sigh..the only thing different was that sometime yesterday after the second factory reset a notification popup of unfortunately a sytem file stopped working came up. I acknowledged it, but thankfully I havent gotten any problems. I forgot what the notification read. hopefully its not related to what happened the other day.I dont know if this is related to one another, but I did notice that before I rooted my android system had automatically upgraded. I looked for issues like this on the net and saw people where having random bootloops after system upgrades and that unchecking scanning for wifi fixed the problem. though I did this and it did not work, thats why I did the second factory reset.
Now Im asking for help if any further issues arise. I love my Note3 and at this point I just want a reliable working device. Im keeping my fingers crossed and hopefully that will be the end of it, but in case it started to act up again, what can I do? any information and help is greatly appreciated. thanks.
Never uninstall any Xposed app that changes system files without first reverting any changes you made with it. Some of them are permanent until they are turned off in the App. Then you can disable the module.
You may want to look into this http://forum.xda-developers.com/showthread.php?t=2559715
I cannot stress this enough.
READ READ READ.
Too many times have I seen someone read a line or 2 then rush right in ultimately turning their very nice phone into the most expensive paperweight one could own.
On that link I posted, read it until your eyes are bleeding if you truly need to start from scratch.
I am not joking here.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Thanks man. it makes sense. I will look into it. you mentioned read. I have read what I thought was plenty, but always ideas and opinions differ, sometimes knowing too much and causing what they say decision paralysis. Because I still read about the Xposed experiences and different people go about it in a different way. but what you mentioned about reverting back makes alot of sense.
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.