Long time reader, first time poster (hello everyone!). I was wondering what the opinion of the folks here might be and if they've any suggestions. Today my rooted Nook Color suddenly started acting up. Applications are very often not responding as they should, bringing up the 'Wait' and 'Force Close' box (happens when pressing the soft back and menu buttons as well). It's really quite weird, earlier today I was using it just fine, and suddenly it started acting like this. I tried the usual things like fixing permissions and clearing the dalvik cache, nothing helps. Also, annoyingly restoring a backup from a previous 'known working' state didn't help either. (I suppose I should note that I'm not running CM7 or anything like that)
Any suggestions or ideas on what could have happened? Should I perhaps return it to stock and try to exchange it for a new one (I've only had it for about a month)? The fact that it seemed to still be happening when I restored a back up makes me wonder if it's some kind of hardware issue.
The thing driving me crazy is how it's so suddenly acting strangely. I've been using it rooted (and overclocked, on dalingrin's excellent kernel) just fine for about a month and it's never seemed unstable or anything.
I forgot to mention (not that it probably matters) but the volume buttons caused the wait/force close thing too. Guess I'll be calling them tomorrow.
Having same problems. And VERY SLOW. Wait or Force Close
Very weird, but I noticed today that it started acting flaky in my Nookie Froyo 0.6.8.
I installed Amazon's app store on there today and angry birds rio. The apps seem to be okay, but general opening and navigating are herky jerky.
Something else that is weird, I was just using it and it completely locked up on me to the point of needing to do a hard shutdown by holding down the power. At the exact same time, I happened to look at my phone and it also had rendomly rebooted itself at the exact same time. My phone is running CM7 (Droid1).
Coincidence?
HI,
I had a variety of problems with similar symptoms as you describe, but I had
been playing with several uSD installs of HC/Froyo/CM7 internal/Froyo internal etc.
I believe that the main cause of my problem was due to an interaction between
the EXT3 and EXT4 formatting of the cache partition. The solution for me was to
reformat the cache partition for my current installation.
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Not sure if any of these are relevant to you though.
Good luck.
Peter
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
pmilford said:
HI,
Other threads I looked at made suggestions such as:
Reformat the cache partition.
Clear the Dalvik cache.
Run ROM manager and select fix permissions.
Click to expand...
Click to collapse
Thanks, but I tried those already (I forgot to mention it in the first post, but I did try reformatting the cache partition).
JLCollier2005 said:
Try installing a custom ROM (not a backup), making sure to clear everything before install. If it still happens, then yeah it sounds like a problem with the device itself. I've had this problem on my Droid twice and it ended up being (the first time) an app I downloaded and (the second time) an app that I updated. It made the whole phone unstable!
Click to expand...
Click to collapse
Yeah, I guess that's a good idea. Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
9thSage said:
Then I'll be even more sure it's the hardware itself. I'll let everyone know how it goes. Also...it's kind of nice to know I'm not the only one with random issues.
Click to expand...
Click to collapse
All I'd need to do to install Froyo from here is format/factory reset everything with clockwork and then install the zip from within CWM, correct?
Couldn't get it to work for some reason. Since I wasn't sure, I decided to format data, cache, and system, then use one of the excellent "Nook Color Restore to Stock" zips. It seemed like it was ok (couldn't test it more since I forget my B&N password and evidently made a typo when tying my mother's maiden name ), decided to try that back up again since I knew the back up worked at one time with no problem (and the md5 was fine, so that shouldn't have changed) and it worked fine for maybe 20 minutes, but now it's weird again.
I'll have to try Froyo again tommorow when I'm hopefully less out of it. I suppose that's probably a more meaningful test.
I know I said I was going to install Froyo, but I decided to try bringing it back to stock and re-rooting it from scratch. I've been using it for a while (reinstalling apps, changing settings back...etc) and it's worked absolutely fine. Been using it on and off for a few hours.
I'll be sure to really bang on it today to make sure it's stable, but so far so good.
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
9thSage said:
I think I can declare it stable. Thanks a lot to all who helped out. I wonder what happened? What a strange, strange problem.
Click to expand...
Click to collapse
Glad to hear! I actually just had a similar problem (again on my Droid) that it ended up being the ROM, but yet everyone else I know had no problem on that rom....just goes to show you Android is different for every unit.
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
I was using my phone a few hours ago (adding an icon from the application drawer to the home screen if that will help with solving the problem) when suddenly, the phone reset itself as though I had done a wipe from the recovery console. I had to sign back into Google and re-sync my contacts and calendar. All my settings were back to defaults. My home screen icons disappeared and changed to the default icons (browser, contacts, dialer, market, messaging, maps) as did the wallpaper. All my SMS messages were gone. Basically, it as was as though I had wiped and flashed the ROM for the first time.
However, and this is the weird part. Not only were all my apps still there but they were still installed. All the settings were lost but they were still there. I am not concerned with the restoration of my settings or anything like that. I've got that all covered with backups. My big question is why did it happen? Has anyone experienced or heard of this phantom reset? My ROM details are in my sig but just in case that changes and someone visits this post later, it will make more sense to them if I list it in the post itself.
Cyanogen 3.6.8.1 w/Recovery Menu v1.4. Radio v2.22.19.26i. A2SD on 550MB ext2 partition. Compcache enabled/24MB.
Has the only happened once with you? It could have been just a glitch.
supremeteam256 said:
Has the only happened once with you? It could have been just a glitch.
Click to expand...
Click to collapse
Well, I can tell you why your apps survived, because you have them on sd card so that's not weird, you can wipe all you want and they will survive.
I would say this is a glitch, don't worry about it unless it happens again.
borodin1 said:
Well, I can tell you why your apps survived, because you have them on sd card so that's not weird, you can wipe all you want and they will survive.
I would say this is a glitch, don't worry about it unless it happens again.
Click to expand...
Click to collapse
Yes, the apps on sd being the reason I didn't lose them makes sense. I had a different problem losing apps on the sd when I wiped but that was a mistakes in the way I was slinking and it was also on JF1.51 (a2sd is very unstable on that ROM). Anyway, I'm seriously hoping it was just a one time glitch because my setup is voodoo smooth otherwise. I finally got my G1 running perfectly and I'd hate to think something was wrong. Either way, Nandroid is always an option.
Phantom Reset Not a Glitch. Happened Again!
OK. So it happened again. The phantom reset that I described in the first post happened to me again. It's pretty annoying to have to perform Nadroid restores all the time. Anyone have any real thoughts other than telling me it was a fluke?
Possible Answer
I am pretty certain that this happened right after I used Backup for Root Users. I have my identical setup on my father's G1 and this has never happened. He has told me in the past that he does not use that app. I don't want to instantly blame the app but I want to provide as much info as possible. Cyan's ROMs are too good for this to be an issue.
aaronratner said:
OK. So it happened again. The phantom reset that I described in the first post happened to me again. It's pretty annoying to have to perform Nadroid restores all the time. Anyone have any real thoughts other than telling me it was a fluke?
Click to expand...
Click to collapse
The dev has reported that it has issues (if you can replicate the errors, send him a logcat)
hes on the forums on this site
SOLVED
Thanks a lot. I will try and write-up (on dev's site) of what I was doing when it happened. It happened to me twice so I don't think I will use it again (at least until it's fixed). I am a backup freak so I like to use multiple apps but nandroid seems to cover it all. I will stick with what seems to work (and work well) for now.
On a side note, Cyan's latest looks too juicy not to try out. Going to upgrade now.
Hello,
for a few days now i have something strange going on with my galaxy s. When i reboot the device, somewhere around the moment you can enter the pincode for the sim, the phone shakes one time first and and then two times as if there is something crashing.
After that all seems to be working fine... That is, until i notice up to two times now, an app went missing, from which i can't remember i removed it. After i reinstall the app, all settings i configured before for that app where there in place...
I am not sure if these two issues have something to do with each other...
I am running the stock Froyo rom 2.2.1 with the speedmod kernel (k12t)...
Is there someone out there who has an idea?
Thanks in advance.
Regards,
Mart
Did you recently change to the froyo 2.2.1 rom, and did problems only occur after changing?
Did you do a full wipe when changing?
Thanks you for the reply...
well no, i am running the 2.2.1 for a few weeks... As far as i am able to point to the moment it started it was just after i removed the battery when the phone was locked (i mistakenly thought it was off). After i placed back the battery and started the phone, i started noticing the possible crashing...
A day or 2 later i noticed an app was lost, the icon was still on the desktop, but it was a green android (like that from the market) and won't start. Because i didn't remember removing the app i looks strange to me. After reinstalling the app all settings i configured before where in place, as if wasn't gone for a while... That's why i notice it, because when i remove an app, i normally make sure everything is removed including settings...
Up until now i have found two of these in a strange way lost apps...
Because there was some time between the removing of the battery with the start of the first issue and noticing these lost apps, i am not really sure they are connected...
It seems that you have any kind of data corruption. If the phone shakes 1 and then 3 times, it is saying that some process has stopped. Also if you lost some app without your intervention... looks like I said. Consider backup your data, wipe and reinstall.
Good luck
I've seen a number of reports of rooted 1.1s being reset to factory after receiving a notification to the effect of "There was a problem with authorization. Please wait while we reset your device", after which the NC is wiped.
I heard this from a couple of friends whose NCs I nootered and initially thought it was due to my nootering via a nandroid from a possibly bad uSD, but I've come across two other cases in the wild.
So far it appears to be a wipe of /data since apps installed into /system are apparently still there.
Since the forums aren't filled with threads about this from panicked users, I'm wondering how wide-spread the issue is. I'm sure I'm not the only one who has nootered NCs via nandroid, but would that cause this issue? Maybe dalvik cache not being cleared after a restore? Would there be anything device-specific that would break?
Anyone else experienced this or heard about it?
It's been discussed previously, you may be able to find the threads with search. I've had this happen two or three times, and it was only after tinkering with hidden system settings. I don't think B&N is intentionally remotely resetting any Nook Colors.
I believe it has to do with Titanium Backup. Someone can point you in the right direction. Apparently restoring /system with Ti will get you in trouble because it uses 'old' keys so the stamps don't match, and going to the Nook Market will hose the device.
I have only had this happen to me if I restored any of the BN stock applications. If I only restore user apps/data, no wipes. There are plenty of threads around with this. Some report it is more random, but I'm not convinced. It appears that BN apps look for something related to authentication that includes some kind of date stamp: mismatch = reset.
Homer
tokyomonster said:
It's been discussed previously, you may be able to find the threads with search. I've had this happen two or three times, and it was only after tinkering with hidden system settings. I don't think B&N is intentionally remotely resetting any Nook Colors.
Click to expand...
Click to collapse
I'm inclined to agree, although hearing of two cases all of a sudden after months of no issues with previously nootered NCs makes me wonder.
What hidden system settings were you tinkering with?
Homer_S_xda said:
I have only had this happen to me if I restored any of the BN stock applications. If I only restore user apps/data, no wipes. There are plenty of threads around with this. Some report it is more random, but I'm not convinced. It appears that BN apps look for something related to authentication that includes some kind of date stamp: mismatch = reset.
Click to expand...
Click to collapse
So you're suggesting restoring a nandroid of /system is what's triggering this?
Get off 1.1 and hop on 2.2
edison said:
So you're suggesting restoring a nandroid of /system is what's triggering this?
Click to expand...
Click to collapse
I'd like to chime in and confirm your issue. I did a nandroid backup of my stock 1.1.0 rooted. Then I flashed nookie froyo to my emmc to test it out. Didn't like the interface much. So I tried restoring through my nandroid backup.
"There was a problem with authorization. Please wait while we reset your device"
Tried it three times and same issue. I had to restore to stock and reroot. And all is fine since. Sucks cause I thought that's what nandroid backups were for.
edison said:
So you're suggesting restoring a nandroid of /system is what's triggering this?
Click to expand...
Click to collapse
Yes. That is what happened to me. I think the key is to backup your user apps/data and then unregister/wipe before doing the upgrades. Then reregister and finally restore your user apps/data.
xboxexpert said:
Get off 1.1 and hop on 2.2
Click to expand...
Click to collapse
Problem with 2.2 or 3.0, no B&N stock reader or other stock features. Unless you know something different.
Homer
racks11479 said:
I'd like to chime in and confirm your issue. I did a nandroid backup of my stock 1.1.0 rooted. Then I flashed nookie froyo to my emmc to test it out. Didn't like the interface much. So I tried restoring through my nandroid backup.
"There was a problem with authorization. Please wait while we reset your device"
Tried it three times and same issue. I had to restore to stock and reroot. And all is fine since. Sucks cause I thought that's what nandroid backups were for.
Click to expand...
Click to collapse
This really makes me wonder if the issue is caused by corrupt nandroids. I can't get any of these new generic 8GB uSDs to make a working NF but other "brand" uSDs work fine. Before I found this out, I made the CWR boot + backups on one of these cards. If the uSD is flaky, then it stands to reason that the restored files might be flaky which in turn could cause a reset.
Alternatively, if there's device-specific info in the nandroids, like SNs or device IDs (the stuff that's saved in the rombackup.zip on p3), that was restored to a different NC, I could see how it could get confused and puke. But to restore to the same NC and have issues? Sounds fishy.
When you restored to stock, was it 1.1.0 stock? How'd you do the restore? 8x failed boots? dd a restore image? One of the CWR factory zips?
Yeah, I just flashed the stock 1.1.0 CWM image from here http://forum.xda-developers.com/showthread.php?t=945838
This just happened to me this morning. I'm not as technical as you guys, and I have no idea what a nandroid is. But I used AutoNooter 3.0 after updating to 1.1, and everything was fine for a week or so. Installed Launcher Pro, Dolphin HD, and a few other apps. This morning, I tried logging into Google Talk (which I hadn't tried before) with a different ID than the one I used to set up Google and YouTube. (I have two Google IDs, and the one I've used for Google Talk was not the same one I'd used to set things up on the Nook. I've since deleted the extra ID and am now using one for everything.) Soon after this, like ten minutes, I was merely reading a book and got the authentication error and reset. Since then, it's just weird.
It looks very much like it did when I got it. But NookColor Tools and Market is there. Softkeys is not. The stock book reader is acting funky, sometimes not displaying the menu that lets you change your page display. Sometimes not letting you make it go away. Getting rid of a bookmark brings me back to the home screen. It's just messed up.
At one point, for no apparent reason, it popped up with the the Market setup, but failed when trying to set up my Google account.
Anyone have any suggestions. I'm guessing I have to bring it back to the beginning, but I'm unclear of the right way to do that, because there's so much information here with various links, and I don't understand all the terms.
Any help would be appreicated.
loribuono said:
This just happened to me this morning. I'm not as technical as you guys, and I have no idea what a nandroid is. But I used AutoNooter 3.0 after updating to 1.1, and everything was fine for a week or so. Installed Launcher Pro, Dolphin HD, and a few other apps. This morning, I tried logging into Google Talk (which I hadn't tried before) with a different ID than the one I used to set up Google and YouTube. (I have two Google IDs, and the one I've used for Google Talk was not the same one I'd used to set things up on the Nook. I've since deleted the extra ID and am now using one for everything.) Soon after this, like ten minutes, I was merely reading a book and got the authentication error and reset. Since then, it's just weird.
Click to expand...
Click to collapse
This is the kind of stuff that keeps me worried. I'm on rooted eclair via autonooter 3.0 and I have everything working perfect!! I'm seriously done configuring and it runs like a champ, but I feel like one day it's just going to blow up somehow or my wife will grab it and try to sign in to something and then...boom!
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.