Ok after a couple of days with little to no problem I am having a weird problem that I just want to report. While locked my phone will do a weird reboot. No splash screen, no sound. The menu keys stay lit. When the screen comes back up everything is restarting and the phone is locked still.
Sent from my SPH-D700 using XDA App
Sounds like you are running Nebula ROM. Update it to 1.0.2
http://forum.xda-developers.com/showthread.php?t=863154
I am running stock update.zip, not even rooted.
Edit: I am going to be giving this ROM a try asap.. Looks like my type of ROM. None of that BS. Simple and professional.
I wanted to post this in the Core Droid dev page but apparently I cannot. Just wanted to let those guys know.
Core Droid v4.6 reboots my DHD randomly. Thought it was an install problem so I re-installed several times clearing the cache each time with the same result. Sometimes after 20 minutes or 5 hours it just randomly shuts off. Quick press of the power button boots it right back up. Rinse and repeat.
I like the rom but cannot use it as m phone just turns off for itself. This can't work. Thanks anyway guys.
Same here on android revolution 3.3 :/
Sent from my Desire HD using XDA App
Thanks man. Now looking for an alternative so you saved me the trouble (and a few days) of trying this one only to find it has the same issue.
So after 2 days of flawless operation, v5 Coredroid just started doing the same thing, random cutoff. What could it be??
Updated the wife's phone to CM7 some time ago because stock was getting really sluggish and unreliable for her. Wanted to give it some new life. Been running ok (a bit better than stock) but still not great. Kinda flaky, she says. I haven't had a lot of hands-on with it since setting it up, but she says it has poor battery life, likes to freeze up, etc... But overall, an improvement.
Today, she gets up, and her phone won't power on. I know her charger can be a bit temperamental, so pull and replace the battery, then hook it up to mine to try and get it to boot.
It powers up long enough to show her she has a lost call, then spontaneously reboots again. Now it's stuck in a loop while plugged in. It boots, gets to the lock screen, reboots. I can get into recovery (but it looks like stock recovery, not clockwork, so I can't reflash CM7 to see if that helps).
I wanted to try flashing a stock SBF so I could get it booting again, (or at least take it into Verizon), but it doesn't even power up when plugged into a USB cable hooked up to the computer, only on the charger.
Any thoughts? I'm kinda stumped, and not as familiar w/ the Droid 2 as I am w/ my HTC G2.
*Edit*
Eh, after sitting on the charger for awhile while I typed this, it actually came up and seems to be staying up. I guess the battery was just very VERY low? Nevermind!
Sbf the phone back to stock and use a more stable rom. Custom roms from what i am noticing can have 2 installs of the same rom and give 2 completely different results. I had this problem with my current rom miui 2.2.10. On my first install it was complete garbage, crashing constantly even with system apps. Then i Sbf'd back to GB using the newly released GB sbf file you can find in this forum. Then re-installed miui and it works fine now. So it could just be you got a bad install. Try miui 2.2.10 over at rootzwiki, its a solid rom.
http://rootzwiki.com/topic/17285-ne...tt-charge-while-off-updated-bootmenu-scripts/
I just got my update to ICS 4.04 and it's made my xoom worse! Things have got really laggy, it sometimes freezes when selecting things and typing has become a nightmare again! Has anyone else experienced any problems :-(
Iam a bit annoyed now, might just go and root.
Sent from my Xoom using Tapatalk
Well its just gone from bad to worse...my xoom went to sleep and when I tried to wake it up it would not come back on. I had to do a soft boot but now its stuck on the Motorola screen. I have tried to go into android recovery and do a factory restore but it comes up with an error
I am really stuck on what to do next, can somebody help please?
Thanks
Hmmm mine went to 4.0.4 and I was thinking the opposite! it seem alot smoother and faster
Mines seems to run slow too after the OTA, but i'm not sure if that's the tTorrent app, when it's running it makes the xoom lag out like crazy, when its off everything runs fine.
burt_ie said:
Well its just gone from bad to worse...my xoom went to sleep and when I tried to wake it up it would not come back on. I had to do a soft boot but now its stuck on the Motorola screen. I have tried to go into android recovery and do a factory restore but it comes up with an error
I am really stuck on what to do next, can somebody help please?
Thanks
Click to expand...
Click to collapse
You could go into Developer settings and switch off animation or set to .5. That should help with lag. I never use live wallpaper either. A big download may also make it lag .
Well the lag didn't last long because I actually had a complete failure after installing 4.0.4. My Xoom went to sleep and would not wake up, had to do a soft reboot and then could not get passed the motorola boot screen, was stuck on it for hours! Tried to go into recovery to wipe and reset but that would not work either. Tried to push a rom image from my pc but then my xoom decided that it didn't want to be detected by my pc anymore so it looked like my xoom was bricked :-(
Luckily I had some help from some great people over at xoom forums who helped me to get it back up and working by using RSD Lite and a stock Rom SBF file.
I now have a working xoom updated to 4.0.4 with no problems at all
Not sure but I think it may have been a freak accident that just happened to me.... I just hope it doesn't happen to anyone else
Sent from my Xoom using Tapatalk
My Xoom went to sleep today also, couldn't get it to power up for anything, I then held power and Vol up and down all at same time and she booted right up.
Bone stock wifi Xoom by the way, incase happens to anyone else
Sent from my SCH-I500 using Tapatalk
Mine has gotten really bad with scrolling lately...
Seems that I can only scroll either up or down (or both) for no more than a couple seconds. Ive been able to move my finger up and down on a scroll area and it only lasts a couple seconds and seems to "lose" my finger press even though my finger never left the screen or the area. I have to wait a couple seconds before I can scroll again or else it doesnt recognize the finger press.
Sometimes I think the lags just android its never constantly smooth. You'd think dual core would be as smooth as butter but it really makes no difference. Still waiting for Google to fix it. I've had months of smoothness then the odd time something slows it down
I agree, 4.03 was great with no lag issues then nightly 90 had some lag again with scroll issues, so far on #91 I'm not having any issues. I had the biggest problem when I was trying the OC @1600, I slowed it back to 1408 interactive and all is smooth as glass:thumbup:
Sent from my DROIDX using Tapatalk
Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).
GronHog said:
Should I reflash kernal or ROM or what?
At 11pm tonite my screen turned on by itself, it read 7:09pm with 51% battery. When I picked it up to check it the screen was locked up, after 5minutes of letting it sit screen still on did a battery pull. When I turned it back on is when I noticed it wasn't 7 o'clock but 11 showing 41% battery. This is the first time my phone has done this. Have gotten the upside down lock sreen from wake up, and a little hesitation when it rights itself but never this. Not sure if it is my phone or what, but decided to post this info incase it has happened to someody else.
SyNthetic_aospX 1.0.0-MR1 with patched kernal
good screen
"bad" eMMC chip
min freq=268
max freq=1036
gov=smartassV2 switched to this after patch of kernal from interactiveX
recov= 4ext
Going to stick wih this ROM, as my phone has isssues with ICS roms after about a week, this one has broken three weeks smooth as butter(fingers crossed).
Click to expand...
Click to collapse
Has it happened again since? If it has try and study your phone's behaviour whenever it happens (does it only happen when plugged in? and so on). Once you manage to get an idea of what actions cause it to happen, start up a logcat and replicate it and send it here. Also, if you've restored anything, downloaded a ton of apps, etc. try a clean install (w/ no restores, minimal apps, and so on) and see if it continues. I don't like to just leave things as "it's a hardware issue" because sometimes it can be difficult to tell.
Hasn't touched the phone for several hours, been on computer, when the incident happened. Had installed a flashlight app earlier in the day, TeslaLED. Also installed Google now M6 offline earlier in the week. Will keep an extra eye open to provide you with any info I can. No TB restore done between BR7 and MR1, as update was done OTA automatically with just ok'ing a cache wipe. The update went smooth, to me, from notification to download to flash and reboot on its own.
sent from Glacier under control of SyNthetic_aospX
again
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use
GronHog said:
Well it happened again, this time it didn't wait four hours before screen turn on and freeze, this time was about 15 minutes. Again was not doing anything with phone it was just siting there screen off. This time I have reflashed ROM to get back to original mint choc kernal, and will not reflash google now this time. How long can I run a logcat for? can it run for the day during normal use
Click to expand...
Click to collapse
Whoops I meant I'll need a last_kmsg from after you pull the battery. That will tell me the last thing that happened before the battery pull. The op in my thread has a link that shows you how.
Sent from my MyTouch 4G using xda app-developers app
Been two days now, everything running as should, smooth. Reflashed Rom to get back to unpatched kernel, and did not reinstall gNOW. Later will install your patched kernel and keep an eye on it. Still getting the occasional inverted lockscreen, but that is no big deal, as this is the most stable ICS Rom that has run on my phone. All other ics Roms have barely made it past a week, cept Awesome's vanilla ics which hit the two week mark before giving me "unfortunately so an so has stopped working" and would cascade from there with errors. Will post up another logcat and kmsg log for you on the invert screen when I make happen again.
sent from Glacier under control of SyNthetic_aospX
Inverted lockscreen from yesterday, should be towards end of logcat=http://db.tt/YOl1UM78
A freeze up while using XDA app and following a link into Maxthon browser. Touched link in XDA auto launched browser then froze, let it sit there for a minute as back button did not kill app. Then phone rebooted itself, so found last_kmsg and saved it=http://db.tt/767lXrNH
Saved both files to dropbox
sent from Glacier under control of SyNthetic_aospX
Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX
GronHog said:
Another last_kmsg log=http://db.tt/hTottjoq
Had just updated BeWeather pro and as weather icon was not showing in widget I did a force close to restart app, which I shouldn't of done, the phone froze. after couple of minutes pulled battery.
Had already flashed your overlay for the kernel. I am really thinking having the "bad eMMC" is causing me these issues, hardware issue.
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
BeWeather was spamming that last logcat you gave me. That might be a part of the problem.
That thought popped into my head, don't know what the logcat was saying but seeing that much from BeWeather didn't look right. Thank you again for t the work you have put into this Rom.
sent from Glacier under control of SyNthetic_aospX
Self wake and freeze happen again, checked for last_kmsg there wasn't one, just last radio. Removed BeWeather widget, and unchecked auto update in the app this morning. I installed the kernel overlay last night, two days without overlay since reflash. Going to leave phone as is for now and run kernel log to see if it happens again.
sent from Glacier under control of SyNthetic_aospX
Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX
GronHog said:
Phone just rebooted by itself, had kernel log running while it slept. Was also able to get last_kmsg log too. So here's a before and after self reboot.
KMSG= http://db.tt/u2tFjwTm
Last_kmsg= http://db.tt/E8F9ORUq
sent from Glacier under control of SyNthetic_aospX
Click to expand...
Click to collapse
Okay. Now bear with me on this one. Because it may seem odd... but try getting a new sim card (it's free) and see if it works. I noticed your logs were different but both had to do with ARM9 crashing due to WCDMA (both times with varying feedback after ARM9 crashing, but both keeping WCDMA common in the kmsg). I looked it up and came across THIS in the cyanogenmod forums. It worked for both of these guys and the other dude basically flipped out on the other because he thought he was dumb, but it worked and ended up looking like a jerk lol.
Another log= http://db.tt/0dfJ4nYJ
Thank you very much for even bothering with my issues. Not to long after my last post the phone froze with screen off and did battery pull. Was able get another last log. I have done a format of everything and reflashed. Installed a few apps and did not do titanium restore. Going to look into getting new sim. Again I thank you and bow to your superior intellect:beer:
Sent from my MyTouch 4G using xda app-developers app