So the title says it all really... Only CM7.X series actually works correctly on my device. All other ROMs that I have tried either cause the phone to reboot itself after an undetermined time, or lock up the device and I have to pull the battery.
Sense ROMs are the worst for reliability I've found. They will reboot randomly with seemingly no reason. I've been playing with IceColdSandwich 8.0+8.1 recently and can reproduce a reboot consistently by opening maps and scrolling it.
I would be quite happy to stick with CM if the INC-S was getting CM9/10 in the future, but this doesn't seem to be happening.
So how can I stop the rebooting/freezing in all these other ROMs?
B3rz3rk3r said:
So the title says it all really... Only CM7.X series actually works correctly on my device. All other ROMs that I have tried either cause the phone to reboot itself after an undetermined time, or lock up the device and I have to pull the battery.
Sense ROMs are the worst for reliability I've found. They will reboot randomly with seemingly no reason. I've been playing with IceColdSandwich 8.0+8.1 recently and can reproduce a reboot consistently by opening maps and scrolling it.
I would be quite happy to stick with CM if the INC-S was getting CM9/10 in the future, but this doesn't seem to be happening.
So how can I stop the rebooting/freezing in all these other ROMs?
Click to expand...
Click to collapse
try wiping your partitions when flashing rom. there might be a corrupted system file or something
naathaanb96 said:
try wiping your partitions when flashing rom. there might be a corrupted system file or something
Click to expand...
Click to collapse
I've always fully wiped /data /cache and the dalvik cache when flashing new ROMs since I read that it's safest to do that from a ROM reliability standpoint.
B3rz3rk3r said:
I've always fully wiped /data /cache and the dalvik cache when flashing new ROMs since I read that it's safest to do that from a ROM reliability standpoint.
Click to expand...
Click to collapse
try format everything else except sd card in the list
I've formatted all partitions except SDcard and am still able to reproduce the reboot by scrolling in google maps for 10-15 seconds.
I should mention that the reboots are not limited to this, it will also reboot during phone calls or other general app usage, but no where near as frequently, and it is not reproducible like the GMaps reboot.
B3rz3rk3r said:
I've formatted all partitions except SDcard and am still able to reproduce the reboot by scrolling in google maps for 10-15 seconds.
I should mention that the reboots are not limited to this, it will also reboot during phone calls or other general app usage, but no where near as frequently, and it is not reproducible like the GMaps reboot.
Click to expand...
Click to collapse
Try clearing maps data. Are you on the new just released maps? Because the new Google earth completely froze my phone once I found my house:3
Sent from my Incredible S using xda premium
naathaanb96 said:
Try clearing maps data. Are you on the new just released maps? Because the new Google earth completely froze my phone once I found my house:3
Click to expand...
Click to collapse
I have cleared maps cache and downloaded a map for offline use as well, same problem is present. I have the latest Gmaps but the problem was reproducible well before this as well.
I don't think maps is the problem since it happens with old versions of maps too; but rather causes the phone to use something else, which causes the reboot.
Is there a way to see the kernel logs after a crash like on desktop linux?
B3rz3rk3r said:
I have cleared maps cache and downloaded a map for offline use as well, same problem is present. I have the latest Gmaps but the problem was reproducible well before this as well.
I don't think maps is the problem since it happens with old versions of maps too; but rather causes the phone to use something else, which causes the reboot.
Is there a way to see the kernel logs after a crash like on desktop linux?
Click to expand...
Click to collapse
Do a search mate. There's a way to get a logcat of a crash just not exactly sure how to do it
Sent from my Incredible S using xda premium
If full wipe doesn't work. then try to change your SD card. Without backup your data. Just to see if reboot occur again.
This suggestion maybe sound stupid, at least, you can give a try
Backup your SD-Card on your computer and wipe/format it afterwards (FAT32). Maybe that helps...
Radio
B3rz3rk3r said:
So the title says it all really... Only CM7.X series actually works correctly on my device. All other ROMs that I have tried either cause the phone to reboot itself after an undetermined time, or lock up the device and I have to pull the battery.
Sense ROMs are the worst for reliability I've found. They will reboot randomly with seemingly no reason. I've been playing with IceColdSandwich 8.0+8.1 recently and can reproduce a reboot consistently by opening maps and scrolling it.
I would be quite happy to stick with CM if the INC-S was getting CM9/10 in the future, but this doesn't seem to be happening.
So how can I stop the rebooting/freezing in all these other ROMs?
Click to expand...
Click to collapse
My guess is that the issue is Radio related. What's your version?
amitizle said:
My guess is that the issue is Radio related. What's your version?
Click to expand...
Click to collapse
I have wiped all partitions (save for the SDCard) and reinstalled IceColdSandwich 8.1.1 and have currently gone over 24hrs without a reboot, even trying to force one using the GMaps scroll.
Radio is: 20.2810.30.085AU_3805.06.0316_M
I would link to a pic showing all the info but it seems I'm not allowed.
If you copy the text below and remove the brackets around the dot com then you can see it:
i.imgur{.}com/nHxgE.png
Hi, sorry for breaking in, but seems like I have a somehow similar problem with my Incredible s:
The phone starts up fine, but will run only for 1-5 minutes before spontaneously rebooting when on battery power.. This never happens when connected to PC or charger, and phone seems to stay alive "forever" in Bootloader (Revolutionary-screen), but leaving that even for Recovery does the "trick", and again it will reboot after a short while. :crying:
Doesn't matter if SD and Simm are inserted or not!
Have tried all I can think of:
Fix permissions, different roms (GingerBread (stock/ some other) and Ice Cream Sandwich (IceColdSandwich)), of course cleared and formatted all partitions, tried different Recovery's (currently Touch Recovery) and radios (S-OFF'ed to do this after problem started), even have heat-gunned soldering for battery-connectors (yes cleaned connections as well), and heated a little where charger and battery seems to "relate", and have also tried another battery with similar 4-point connection (works, but same same) so what else to do??
The problem started two days after replacing a smashed digitizer with new one (from eBay), and after a two hour car-trip with GPS and Navigate on, but no charger, in a hot front-window; the phone just exactly reached to run flat out of power, and when I recharged it shortly after arrival, the "fun" began..
It clearly looks like a battery problem, but the battery seems in perfect condition. Could it be the unoriginal (cheap) digitizer? Mind you the phone worked flawlessly for two days with that ting..(?) Or should I invest in a new battery even so (please see pic.)?
Again sorry for intruding the string, but have searched a lot without finding anything more similar, and didn't want to open a new string for this.. Maybe this one will come to live again, with a new post... :fingers-crossed:
Current config
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Battery
Greetings from Denmark, and please HELP!:cyclops:
seek4 said:
Hi, sorry for breaking in, but seems like I have a somehow similar problem with my Incredible s:
The phone starts up fine, but will run only for 1-5 minutes before spontaneously rebooting when on battery power.. This never happens when connected to PC or charger, and phone seems to stay alive "forever" in Bootloader (Revolutionary-screen), but leaving that even for Recovery does the "trick", and again it will reboot after a short while. :crying:
Doesn't matter if SD and Simm are inserted or not!
Have tried all I can think of:
Fix permissions, different roms (GingerBread (stock/ some other) and Ice Cream Sandwich (IceColdSandwich)), of course cleared and formatted all partitions, tried different Recovery's (currently Touch Recovery) and radios (S-OFF'ed to do this after problem started), even have heat-gunned soldering for battery-connectors (yes cleaned connections as well), and heated a little where charger and battery seems to "relate", and have also tried another battery with similar 4-point connection (works, but same same) so what else to do??
The problem started two days after replacing a smashed digitizer with new one (from eBay), and after a two hour car-trip with GPS and Navigate on, but no charger, in a hot front-window; the phone just exactly reached to run flat out of power, and when I recharged it shortly after arrival, the "fun" began..
It clearly looks like a battery problem, but the battery seems in perfect condition. Could it be the unoriginal (cheap) digitizer? Mind you the phone worked flawlessly for two days with that ting..(?) Or should I invest in a new battery even so (please see pic.)?
Again sorry for intruding the string, but have searched a lot without finding anything more similar, and didn't want to open a new string for this.. Maybe this one will come to live again, with a new post... :fingers-crossed:
Current config
View attachment 1201735
Battery
View attachment 1201736
Greetings from Denmark, and please HELP!:cyclops:
Click to expand...
Click to collapse
Your problem sounds like its hardware based. I was unable to prevent the phone from rebooting and so have gone back to CyanogenMod 7.2 where the frequent reboots do not occur.
B3rz3rk3r said:
Your problem sounds like its hardware based. I was unable to prevent the phone from rebooting and so have gone back to CyanogenMod 7.2 where the frequent reboots do not occur.
Click to expand...
Click to collapse
Thanks for your quick reply mate!
This http://forum.xda-developers.com/showthread.php?t=1553654 one? I'm back to my old S-E X10i, so anything is worth trying.. Which BB and kernel do you use for that iso?
B3rz3rk3r said:
Your problem sounds like its hardware based. I was unable to prevent the phone from rebooting and so have gone back to CyanogenMod 7.2 where the frequent reboots do not occur.
Click to expand...
Click to collapse
Well thanks again for a plausible suggestion, but just now tried my guess (from post here above), and sadly still no go! Didn't even let me finish Setup (after installing Gaps) before rebooting itself ..
Already had a thought about HW power management myself, but kinda fought it off, as the idea didn't become me, however that probably is the thing..
Who knows a little something about the s710e PCB, to guide me messing the right thing(s)??
seek4 said:
Well thanks again for a plausible suggestion, but just now tried my guess (from post here above), and sadly still no go! Didn't even let me finish Setup (after installing Gaps) before rebooting itself ..
Already had a thought about HW power management myself, but kinda fought it off, as the idea didn't become me, however that probably is the thing..
Who knows a little something about the s710e PCB, to guide me messing the right thing(s)??
Click to expand...
Click to collapse
There is a stable release of CM 7.2 out now on the official site. I would provide you a link but I'm not allowed to yet.
I would suggest checking the MD5 sum and full wipe before installing it. If you are still having troubles then I would look at the hardware as the problem.
B3rz3rk3r said:
There is a stable release of CM 7.2 out now on the official site. I would provide you a link but I'm not allowed to yet.
I would suggest checking the MD5 sum and full wipe before installing it. If you are still having troubles then I would look at the hardware as the problem.
Click to expand...
Click to collapse
Once again tanks! Found it and tried it (I always do full wipe between roms), unfortunately still same result.. But what MD5 sum am I supposed to check?? (Where, how?)
seek4 said:
Once again tanks! Found it and tried it (I always do full wipe between roms), unfortunately still same result.. But what MD5 sum am I supposed to check?? (Where, how?)
Click to expand...
Click to collapse
Mate, your problem is obviously hardware-related. You should go to htc service center if you want your device to run again.
Agreed.
Now and again you can get a bad download, which is why you check the MD5 sum against the orginal, but if this is happening with every ROM you use, plus the fact that you have already replaced parts on your phone with non-original hardware, leads me to the conclusion that you have a hardware defect.
Related
First I thought that I'm crazy but now I can confirm that my NC will boot on it's own after about 5 minutes after power OFF. I have to shut down 2nd time and than it will stay OFF. Any idea what's wrong ?
Thanks
(Yes I did confirm after first shut down that it's actually OFF since no buttons will respond)
Any weather Apps running? Many of them have an option to wakeup in order to update. Check your mail, twitter and facebook apps. It has to be something you installed, I have run every update, tried all the froyo images and both Honeycomb releases and I have not seen that.
To expand on what gedster wrote, it seems kind of crazy and out there but what about any devices on your network that might send Wake on Lan requests? What if something on your network had located your NOOKcolor. I don't even know why a eReader Tablet would have a function for Wake on Lan but it's just another crazy avenue to jog down.
I do have weather app installed but I find it hard to believe that it can wake up OS that is not in standby but completely off. WIFI is also not enabled before shutdown.
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
lifeisfun said:
Looks like the problem is there only if I used market, if market is not used it will shut down fine and it will not boot on its own.
Click to expand...
Click to collapse
Seems that's unlikely if you're the only one having the issue, I'd keep digging if I were you.
Looks like you're right I can't replicate the problem every time
The timing when it will boot also varies 5, 15 and even 35 minutes.
Don't know what to do, it's hard to imagine how it can boot on it's own from
complete power off state
I can't believe I'm the only one with this problem
lifeisfun said:
I can't believe I'm the only one with this problem
Click to expand...
Click to collapse
I just posted a thread about this issue for me less than an hour ago! Funny, no one replied to mine: http://forum.xda-developers.com/showthread.php?t=940713. It was pretty long...guess I should've added a TL;DR.
It happens to me on any (or no) power source. Timing varies like yours as well. I'm going to pull my weather app based on the above recommendation, and I will try your Market theory out. Knowing someone else has this issue makes me hopeful that we can find something that we have in common as the culprit.
I did download the newest Honeycomb image yesterday and I'm going to put that SD card in and see if I can get it to turn itself back on on a Market-less, user App-less build. If successful I'll Titanium my 1.1 apps and remove everything non-system, then slowly add until I get this figured out. Keep me posted if you figure something out, I'll be sure to do the same!
In case it matters I bought mine about a week ago and the serial number starts with 20046.
EDIT: Testing with Honeycomb SD now so if that's the case here it should just stay off. I booted into Honeycomb at 9CST and turned it off at 9:01. I'll give it a couple of hours.
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
woot1524 said:
I used to have this same problem. I would randomly find my 1.0.1 auto-nootered 950mhz rom nook on, when I knew I had turned it off. interesting part is, this problem completely solved itself after I flashed my emmc with the custom nookie 5.9 img. so it must be an eclair issue and not a hardware issue
Click to expand...
Click to collapse
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
oscillot said:
Really? I've been putting that off because I don't like the idea of not having Clockwork Recovery. I understand there are ways to do the same things using IOMonster's things but I'd really rather just have Clockwork Recovery working. Unless there's a way to get it going that I missed?
Click to expand...
Click to collapse
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
woot1524 said:
you are correct that clockwork does not work with froyo. however the bootable sd card that you would burn automatically starts up clockwork first. you can run a backup and restore, as far as i know, without having to reflash froyo. on a personal note, froyo still has some issues but overall I'm exteremly pleased so far. i really just wanted to get rid of all of the b&n stuff (mainly the status bar) along with any possible way of them pushing an update to break root. I would recommend it, but CM 7 with gingerbread will probably be out sooner rather than later.
Click to expand...
Click to collapse
Which I guess brings us back to, why is Eclair doing this, and why does it seem to be limited to lifeisfun and myself?
I'm glad I'm no longer special
My serial # is 200503 .....
Removing all application that I have installed didn't help.
Only 100% way to shut down is to let it boot and immediately shut down.
unknown.soul said:
Yup, I've been having this issue as well. I really want to flash NF but I want hardware video acceleration.
Click to expand...
Click to collapse
Now that I understand the power of this things SD slot and that CWR can be run off of an SD, I can totally live with that. Hardware Video isn't a must for me yet, so I may take the plunge tonight after work...BTW, what are people's favorite video apps? I have been playing with VLC stream and convert, which works somewhat with my media server's samba shares. I have the share mounted to a directory on the sdcard since many apps look there exclusively.
More on topic, I couldn't get SD Honeycomb to start itself on its own. I tried booting then shutting down. 2 hrs of nothing 15mins light activity then shutting down. 2 more hours of nothing. About an hour of heavy use, seeing what could be installed, sideloading, testing, editing things like build.prop and rebooting often and trying to get swype working (don't think it's supposed to, but that's "heavy use" for me.) Powered down. Went to bed. Still not on this morning. This looks indeed to be an issue with the B&N stock Eclair.
Mine doesn't turn itself on with no interaction at all, but will turn on every time when you plug in the charger or cable hooked to USB port in computer.
I can turn it off once it is already plugged in and it will stay off, but remove and replug the charger and it is on again.
Strange.
Well, strange that only two or three of us noticed this strange problem.
Yeah, started for me after 1.1 update. Turned it off last night, tonight it was on with 40% battery! I think its 1.1 related, this didn't happen with 1.0.1 ...
I'm sure there's a condition that's causing or exasperating this issue, something common to us all. But at this point since I don't use the Nook as a video player (I actually bought it to read books, but I use Aldiko and the open epub format) I will likely flash Nookie to the eMMC and call it a day. Honestly can't wait to get a clean notification bar on this thing anyway.
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
At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?
interesting, try to catch the evnts in the logs, use elixer/logcat/android tuner for that.
Check the battery dude.
I had similar problesm due to bad battery.
Phone was closing itslef. And before it closesi thescreen was turning crazy
Then no boot at all....
ardicli2000 said:
Check the battery dude.
I had similar problesm due to bad battery.
Click to expand...
Click to collapse
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?
JolyonS said:
Thanks. Did your problems occur even if the phone was on mains power? Does the battery have enough 'smart' features to affect the phone even if it is not required for powering the device?
Click to expand...
Click to collapse
I was outside when faced such a big problem. It was happening before like reboobs and stucks on logo. But after i took out the battery for 15 min I was able to boot the phone.
However, eventually, one day phone got stuck with a flickering screen and then it never booted. Tired nandroid restore. Did not help. Changed kernels etc. It was no good either. Then I changed battery. Did not work again Then made a factory reset. It worked. Using it without any problem now. But even at that time I was able to see my files in the phone via Qadb. This could be your case as well.
Try changing battery if it is older than 9 months. Make a full pit fresh Stock install.
Then Reboot. I hope t will work
JolyonS said:
At least I think this is. I have recently moved from stock to Asylum's CM10.1 but did flash a known safe kernel before any wifing occurred so I do not think this is the standard EMMC bricking.
The onset of this was gradual - phone reboobed itself a couple of times (that I noticed) but this was no huge deal for me, then a few days later the screen digitizer stopped working and I had to take the battery out - from there it degenerated fairly rapidly with more reboobs, more often returning with the digitizer not functioning and finally it is at the point where it will not boot - stuck at the loading logo.
I can reboot into recovery (CWM 6.0.3.2) but can't do a lot there - fleshing a new ROM errors out saying the package is invalid or crashes (often with a brief flickering of the screen in either case).
I can run through hg42s partition scanner - if it completes it does so without report a problem otherwise it crashes, it's about 50/50 which although it seems more reliable if mains power is connected.
If I leave the phone in CWM it will eventually reboob itself after a few minutes.
I haven't seen any magic smoke escape.
I never experienced the EMMC brick so I don't know if it was progressive as this seems to be but I get the impression it was not - and I can't rule out the same sort of problem even if the original cause is different but at the moment I am unsure about the best way to progess - I will at some point pop over to Samsung's store but ideally I'd want to get to the bottom of this with the help of the community.
So any ideas? Does this sound like a corrupt partition somewhere? Thermal sensors triggering shutdowns when they shouldn't?
Click to expand...
Click to collapse
Me too, i have some problem.
delete-
ardicli2000 said:
if it is older than 9 months.
Click to expand...
Click to collapse
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.
JolyonS said:
Yup. This was indeed the problem - new battery in and after a few repeats of the same behaviour it kicked into life and has been fine since.
Thank heavens for replaceable batteries.
Click to expand...
Click to collapse
Glad to hear that problem is solved
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?