Related
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.
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
anyone?
I'm no expert on this but it seems about all you can do is to NVflash some other ROM since that will wipe your internal memory and repartition it. Then go back to HC again. If you have anything important on your device, back it up somehow as all data will be erased. There are lots of Guides and How To's here, some are good but some aren't! You'll have to read, read and reread till you go blind.
domenicostorino said:
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
Click to expand...
Click to collapse
Though you are running Dell's official rom, I'm not sure which rom it is. Anyway, I suggest you follow the instructions here and update it to the newest 514 rom. This will wipe your ds7 and give you a clean start.
http://streakblog.blogspot.com/2012/01/new-patch-to-fix-docking-bug.html
domenicostorino said:
Hello
I've got a used Streak 7 with the official Dell Honeycomb update. I made a master reset while driving home, then connected it to my WIFI network and worked very well! until it suddenly rebooted while browsing the web. After turning it on again and using the youtube app, the same thing happened even at full charge with the cable still plugged. Annoyed as hell, did another master reset... seemed to work well but after an hour it rebooted again... and does it every 10 minutes or so.
I am pretty sure it is software related because seconds before each reboot, the screen goes black and I am able to read: "Android System" with a weird icon on the top left corner... then It displays the Power Off/Shutting Down dialog (like when you power it off the right way pressing the power button) but then instead of pwering off it reboots itself.
I have noticed that if I leave it alone without opening any applications, it stays on. So far I have done 6 master resets and the issue is still there.
Any help please!!?
Click to expand...
Click to collapse
I'm gonna go out on a limb here and say it's a known bug that hasn't been been able to be repaired and/or addressed. The only version that didn't have this problem was the stock Froyo and DJSteve's custom Froyo builds.
The Honeycomb builds, even the stock ones on my Streak did the same thing, and once in a while the ICS beta I'm currently using will randomly reboot if I'm using the browser.
NOW if I remember correctly, DJ Steve's Honeycomb builds R2 through R6 weren't plagued with this that I can remember. I used them all and don't recall random reboots of any kind.
Hope this helps. I know it's frustrating and I used to pull my hair out thinking it was something I installed. It may be my Streak, but down here in Costa Rica there are a group of about 20 of us that have one and I service them all and they were all plagued with the random reboots in the Honeycomb builds
cdzo72 said:
I'm gonna go out on a limb here and say it's a known bug that hasn't been been able to be repaired and/or addressed. The only version that didn't have this problem was the stock Froyo and DJSteve's custom Froyo builds.
The Honeycomb builds, even the stock ones on my Streak did the same thing, and once in a while the ICS beta I'm currently using will randomly reboot if I'm using the browser.
NOW if I remember correctly, DJ Steve's Honeycomb builds R2 through R6 weren't plagued with this that I can remember. I used them all and don't recall random reboots of any kind.
Hope this helps. I know it's frustrating and I used to pull my hair out thinking it was something I installed. It may be my Streak, but down here in Costa Rica there are a group of about 20 of us that have one and I service them all and they were all plagued with the random reboots in the Honeycomb builds
Click to expand...
Click to collapse
I am running stock 514 rom and found it to be less prone to the reboot. Before this update my ds7 would reboot at least 2-3 times a week. Now it would be 2-3 times a month. I noticed that some apps do trigger the reboot, specially poor written apps and non-honeycomb apps. So don't go installling every apps under the sun.
But back to the OP problem, you seem to have an excessive amount of reboot. I would update to the 514 rom first because it is simple and easily done before you nvflash to other roms.
After upgrading to 514, I cant say I've ever gotten a reboot on it since it came out.
Had a fair amount of them on 506 though.
Cant speak for HS as I dont use them.
TheManii said:
After upgrading to 514, I cant say I've ever gotten a reboot on it since it came out.
Had a fair amount of them on 506 though.
Cant speak for HS as I dont use them.
Click to expand...
Click to collapse
I wish I had your luck... On all HC roms... Stock or Steven's I had reboots so bad that my 7 was almost unusable... Not much without root but after root it got real bad... I even quit using it for a while... But mine is the 4G version so that may have had something to do with the instability
SGS II I9100 from TapaTalk
ok, this sucks
thanks... I have been playing with it for more than a week and I've discovered that if I tap on the back of it lightly, it immediately reboots!
The reboot also occurs if I hold it horizontally twisting it a bit (being gentle of course).
So, even if it seems like a software issue (because it reboots instead of suddenly loosing power completely)... it is actually a hardware issue.
I've been reading a lot regarding this problem and learned this also happens on the Dell Streak 5. Some users say that when Android detects an unstable voltage it auto reboots... and the problem with those ds5 is the battery not sitting completely still and it can be solved just by putting a piece of paper under the battery, great for them with a detachable battery! but not for us with a sealed system.
Do any of you have a service manual? I am willing to take it apart to try to solve this problem. My streak is unusable.
domenicostorino said:
thanks... I have been playing with it for more than a week and I've discovered that if I tap on the back of it lightly, it immediately reboots!
The reboot also occurs if I hold it horizontally twisting it a bit (being gentle of course).
So, even if it seems like a software issue (because it reboots instead of suddenly loosing power completely)... it is actually a hardware issue.
I've been reading a lot regarding this problem and learned this also happens on the Dell Streak 5. Some users say that when Android detects an unstable voltage it auto reboots... and the problem with those ds5 is the battery not sitting completely still and it can be solved just by putting a piece of paper under the battery, great for them with a detachable battery! but not for us with a sealed system.
Do any of you have a service manual? I am willing to take it apart to try to solve this problem. My streak is unusable.
Click to expand...
Click to collapse
Our friend TheManii wrote a thread on how to take apart the ds7. Link below.
http://forum.xda-developers.com/showthread.php?t=1441139
Oh wow this sucks... I mean cool guide but it is so extremely difficult to take it apart without damaging it! It is basically being held together with glue :S
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
seventieslord said:
I complained about this issue originally in the MavRom thread but was advised this isn’t a known issue with the ROM, so after more troubleshooting, here I am. This is the chain of events:
- Bought the Droid 3 unlocked so I could use it on Rogers
- Instantly flashed CM9, lived with the various issues hoping they’d be resolved soon
- They weren’t, so I started looking for a permanent GB rom. Tried MavRom
- Noticed a day or two later the following issue:
Wifi will just randomly encounter an error and turn off. It typically happens without me noticing, and then I’ll be at home and notice I’m on data when I should be on wi-fi. If I try to turn it on using the power widget it will briefly light up as though it’s trying to turn on, but eventually give up. If I try to turn it on through settings, where it normally would say “wifi is on” or “wifi is off”, it just says error. I used to reboot the phone to fix it, but just realized a few weeks ago that I just need to turn airplane mode on and off, then turn wifi back on.
This isn’t the worst thing in the world but it should not happen. There is also no pattern to it, or any apparent triggering event. It can happen half an hour after the last time, or it can go a whole day without happening. My phone is in essentially the same state all night while I am sleeping, so the same thing should happen every time. But sometimes I wake up and the error has occurred, other times it hasn’t.
So as I said, I complained in the MavRom thread, they insisted it wasn’t related to Maverick. So I flashed Eclipse to try it out. Right away I realized that this error was happening in Eclipse too. So, somewhere in all the clearing data and cache and flashing of ROMs, etc, I managed to wreck the wifi in a way that reflashing doesn’t appear to fix.
Realizing this, I tried to go all the way back to stock to see if that would work. I used the .906 to .890 patch (since it’s the only way to go back to .890 or at least mostly), then had to use quick unbrick to fix it when it wouldn’t start up. Everything was fine; it was a stock motobloat Droid 3 again. After a few hours of usage I was pretty convinced that the wifi error was gone.
So I installed Eclipse again. For most of the day everything seemed fine but the same problem reared its ugly head last night just like it used to. It sounds like I need to somehow update the part of the Gingerbread OS specifically related to wifi but I have no idea where to go from here. Has anyone else seen a problem like this before? Any troubleshooting advice?
Click to expand...
Click to collapse
I would sbf and stay on stock, if it reappears, bring it to verizon. Im afraid I've never heard of this problem before. Since it happened with 2 separate roms, it seems more like hardware. Otherwise the sbf should have fixed it.
Sent from my XT860 using xda premium
Odd. I know that this was a problem on most ICS roms. Haven't heard of it happening on a GB rom. This happens to me on Gummy 1.2. Same symptopms: wifi kills with no cause and no pattern. I toggle airplane and keep browsing as I only turn on wifi when I am actively using it.
Sent from my DROID3 using xda premium
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
are you using a custom kernel?
JustusIV said:
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
Click to expand...
Click to collapse
Did you change your Android password within the past 72 hours?
cam30era said:
Did you change your Android password within the past 72 hours?
Click to expand...
Click to collapse
Nope...
its not that i just cant connect, its like the hardware is broken.
and just did a complete factory image flash.
still broken
I had this happen to my N6 last week. It started after running the battery completely flat so the green LED lit when I charged it. The fix having repeatedly wiping seemed to be draining battery completely again until the green LED lit when I charged it. It has worked fine ever since.
JustusIV said:
Tried searching around and have seen others with this issue but nothing has worked. Tried a clean flash of a rom and during the setup wizard its still broken.
I have pretty much done everything but done a clean flash of stock and i am gearing up to do that but i dont have high hopes.
Click to expand...
Click to collapse
I have the exact same issue and have tried everything from fully returning to stock which worked a little better but still not well and also tried different radios etc etc and roms... dont know what the deal is.. nothing on the internet seems to help its almost like no one knows how to fix it or its really rare... ugh
hackahero said:
I have the exact same issue and have tried everything from fully returning to stock which worked a little better but still not well and also tried different radios etc etc and roms... dont know what the deal is.. nothing on the internet seems to help its almost like no one knows how to fix it or its really rare... ugh
Click to expand...
Click to collapse
First contacted square trade as that is my insurance, they said contact Moto because it is still under warranty. Did that, Moto said they would replace it. I said i don't want to go without a phone and they said they can charge me 25 and put a 500 hold on my account but they would send the phone first. Said OK phone arrives on Tuesday.
Just as an FYI they did basically say did you factory reset it.... but that is all the trouble shooting.
If anyone is interested in my symptom. Wifi is just always stuck at "turning on" every once in a while it will be off. but when you try to turn it on it just gets stuck again.
When it is stuck you can not turn it off.
paulwoodhouse said:
I had this happen to my N6 last week. It started after running the battery completely flat so the green LED lit when I charged it. The fix having repeatedly wiping seemed to be draining battery completely again until the green LED lit when I charged it. It has worked fine ever since.
Click to expand...
Click to collapse
Might be worth an RMA. see my previous post.
Don't know if I'm a little too late to this post... .But it happened to my Nexus 6 too, tried everything, wipe cache, factory reset, root, delete /persist/wifi but nothing worked....
However, luck seems to be on my side when I went into Google Connectivity Services under Setting--> Apps... and wipe its cache and tried to disable it (but stopped before I did). Then reboot the phone once i wiped all the data from the Google Connectivity Services Apps and VIOLA! It's working now!
*EDIT... It worked for about an hour (allowing me to dl all the apps) but now it has failed again....
I have the same issue as soon and I unlock the bootloader
any ideas? Im going to root again the device and load a different to see if it makes any difference
I am experiencing this as well. Was working fine yesterday and when I tried to go to Android M Preview 3 this happened. Whats worse is that this is happening right after I switched from Unlimited Data on TMo to Project Fi with 3GB. Making this even more frustrating is that Project Fi support says the preview images are now compatible with Project Fi. Isn't that something they should be telling people up front?!
I'm having the same issue on marshmalow, it suddenly started to happen some weeks ago.
First times was solved with phone reboot.
Then was required to clean cache before restart
Now I've tried reclutance suggestion (delete data from google connectivity services and reboot but the problem persist?
I'm using 6.0.1 stock rom without root
I don't want to perform a factory reset
Any suggestion?
here too...close the wifi
All tried doesn't work,
Wipe cache
Wipe dalvik cache (via fastboot as I do not have a custom recovery neither unlocked the boot or root, my phone is completely original)
Also tried to delete wifi data
Any suggestion?
RMA
I'm continuing to have issues with my Motorola Nexus 6 phone.
It is running stock android 6.0.1
I never unlocked it or rooted (Sadly cause If i do so I were able to backup my apps and settings with titanium backup and restore it before a full device reset )
The problem started some weeks ago.
First symptom was that i was unable to enter on Settings -> Data usage (Every time receives an "unfortunately, settings has stopped" message)
Then some days have difficult to connect to wifi or disconnect (at that moment I didn't investigate the issue, just retry considering the issue was on router side)
After some time I realize that the problem was on the phone, specially cause it started to stuck turning on wifi, but for some days just turning off phone and turning it on again solves the issue.
With the time it becomes more and more frequent and turning it off and on didn't solve anything so I've reboot into recovery mode and perform a clear cache but it doesn't solve the issue.
Looking here and at other forums found that this issue is really common and some people solves it trough ADB with "adb shell pm clear com.android.settings" I've tried it but it didn't solve anything.
Even when many people didn't solve it with a factory reset I want to try it, but I need to be able to backup one app data (If could backup everything will be the best but at least need to backup blockchain app (Also have an issue with them as provider and couldn't log in from another device or website, just this device has a session already approved and open)
Any suggestion?
I've upgraded/downloaded to almost any possible rom and the problem is still here
Looking on forums found that is a very common issue since marshmallow in many devices (Specially Nexus)
Most people couldn't fix it but some could.
the problem is with devices macaddress that shown 02:00:00:00:00:00 and get stuck turning on
there are solutions in forums that seems to be a little bizarre like drain battery to 0 and full recharge (This one works for me once)
,others like deleting Google connectivity services cache, or deleting /persist/wifi folder completely
But I found one for nexus 5 who replaces the full /persist partition with a dump and edit the files and permissions with macaddress information.
This seems to have logic and provides an explanation about why the problem persist after, factory reset or rom changing so I want to try it in nexus 6.
Could someone provide me a dump of it?
There is an app: https://play.google.com/store/apps/d...nam.partitions, that makes the process of making a partition backup easy. The persist partition is on /dev/block/mmcblk0p26
Thanks in advance
Did you solve your problem? Because I have the same. Did you try to change Mac address on device?
Hi,
A while back I posted about my WiFi not turning on... Somehow it sorted itself out, but now the problem has reoccured.
Here's how it begins...
I was on OmniRom and my N6 started rebooting itself. It wouldn't stay on any longer than 5 minutes before restarting. Because I use my phone for work I jumped on the computer and flashed stock 5.1.1 via fastboot. Full clean wipe, system, user data, modem, etc. Afterwards I had no WiFi. I didn't think much of it as I was at work and would deal with it when I got home. When I got home I tried a simple factory reset, didn't work, another clean flash of 6.0, didn't work, a clean flash of cm12, didn't work, multiple recoveries, patches and kernels, didn't work. After several hours I knew there was something else wrong. After trying a few apps and researching for hours on end I have come to a dead end. I have dealt with relying on mobile data for 2 months but now I'm desperate as my work is about to switch over to fully digital automation using a VPN based intranet site that all employers will need to use which we can only access via WiFi on our phones.
The only time I have been able to get WiFi to turn on its after deleting out the WiFi folder in system/data/misc/WiFi, this worked only twice both times only for a few minutes. It no longer works by doing that at all.
Suggestions?
Cooked? Or recoverable?
Many thanks in advance for anyone that can possibly shed some much needed light on my situation.
Lewis (Ork)
Try re-flashing your radio? If you do a full reset from the factory images, part of the process will reflash the radio.
Because I use my phone for work I jumped on the computer and flashed stock 5.1.1 via fastboot. Full clean wipe, system, user data, modem, etc.
Click to expand...
Click to collapse
Modem/Radio... same thing
tried i think about 3 or 4 stock images
Think i may have a corrupted EFS partition.
Bump.. If anyone can let me know and confirm my suspicions that the EFS partition has had it in or any chance of reviving it?
Bump
Most likely your wifi chip is dead or dying. Happened to my N5. I lost bluetooth functionality as well since they both were on the same chip. Mine got so bad that it got locked in a state where even if the phone was off, it would drain battery and heat up the area where that chip was.
Warranty it. Just easier.