[Q] Need help again....CM7 - Android Software/Hacking General [Developers Only]

I know I have asked before but I haven't seemed to get a good explanation of why or how to fix it. Every so often, sometimes for no apparent reason, my Dinc will reboot and/or get stuck in a rebooting loop. I am running CM7 and it seems to happen most often when I have it charging.

What RC are you running? Are you running a stable version? What phone do you have?

I am running CM7. 0.3 and it is not a nightly. My phone info. is;
Kernel: 2.6. 37.4-cyanogenmod+
Baseband: 2.15. 00.07. 28
Rom: cyanogenmod 7.0. 3-inc
Anything else?
Sent from my Droid Incredible CM7 using XDA Premium App

Not sure if it helps the diagnosis or is relevant but after it goes through this fit my LED will stay on. Like this am (about 20 minutes ago it went through the fit, I unplugged it) and my LED has been lit orange ever since?
Sent from my Droid Incredible CM7 using XDA Premium App

Nothing?
Sent from my Droid Incredible CM7 using XDA Premium App

I think you should try in the official CM dev forum

Related

NS4G Random Reboots and Screen Freezes?

Hey guys, my Nexus started having these weird moments where the screen would freeze and turn a weird sickly green color. I also just experienced a couple of random reboots. This happened on CM7 and OpenSoju...
Is this a hardware issue or did something go wrong with my software? Should I return to stock and start over with rooting and whatnot?
Please help
P.S. I'm still within in my 30 days from Best Buy
bump 10 char
First, I should emphasize that my Nexus S is the garden-variety i9020T as used on T-Mobile, so it's not the same as yous. I never tried OpenSoju but I did try CM7 several times, both the stable 7.0x releases and the nightlies, and had very little luck with it, with symptoms similar to yours. The worst thing that happened a few times was finding that the phone apparently rebooted in the middle of the night and got stuck in the dreaded boot loop - a dim frozen Cyanogen boot logo showing on the screen and feeling hot to the touch.
I'm now on Jonathon Grigg's Infin1ty ROM and it's been very stable for me. I see that it's not one of the available ROMs for your 4g http://forum.xda-developers.com/showthread.php?t=1071500 but there are some deodexed stock ROMs you can try. See if they get you stable, and then you can try some of the more bleeding-edge ROMs later. The 4G is a very new phone so there isn't too much available for it yet.
Yeah is probably the roms I haven't rooted my nexus s 4Gbut I got stock and I don't have any problems at all
Sent from my Nexus S 4G using Tapatalk
I bet you are running out of ram. Been running cm7 on mine since the first build for it and it is smooth as butter.
Sent from my Nexus S 4G using Tapatalk
styckx said:
I bet you are running out of ram. Been running cm7 on mine since the first build for it and it is smooth as butter.
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Thanks for the replies, everyone.
Responding to the quoted one in particular, I don't know how I'd run out of RAM really, I'm only using the same number of apps as I did on my EVO and I didn't have problems with RAM ever. Is it just because of the ROM?
As for using rooted stock ROMs, I would but I -really- love Facebook sync to the point that I almost don't wanna go without it.
i had this issue once too with the nightlies cm7. its software related i guess.
Seems better now. Using nightly 5
Sent from my Nexus S 4G using XDA App

Screen Rotation

Can't figure out how to even find out how to figure out why my screen doesn't rotate seams a lot of sensors aren't working after it downloaded one of the test apps from the market. PS I pre thank any who help seems very hard to thank people for me for some reason. That also first work LOL..
Sent from my Inspire4G using xda premium
Try this. Menu, settings, display. Is there a check-box for auto-rotation?
Sent from my Inspire 4G using the power of the dark side
Doesn't work sometimes it will rotate the screen but it stays rotated compass also doesn't work
Sent from my Inspire4G using xda premium
You rooted? Any other info?
*ins>rt sig here*
Yeah Core Droid 8.1 and whatever else it came with really new so not all familiar with terms and stuff just got in here read the directions... Flashed, bricked, and flashed again not even sure when it stopped working
Sent from my Inspire4G using xda premium
I haven't had Sense in a while, but look for G-Sensor calibration in settings and do it. Reboot afterward.
Sent from my ENG S-OFF, CM7, HTC Desire HD/Inspire 4G on AT&T.
It aborts everytime
Sent from my Inspire4G using xda premium
29rolla said:
Yeah Core Droid 8.1 and whatever else it came with really new so not all familiar with terms and stuff just got in here read the directions... Flashed, bricked, and flashed again not even sure when it stopped working
Sent from my Inspire4G using xda premium
Click to expand...
Click to collapse
Sometimes it just may need a restart to fix the auto-rotation. Reboot should fix it.
Sounds like you have a broken accelometer or its on its way going out. I had same problem g sensor won't calibrated at all now says abort everytime restarts do nothing.
I can't do anything that requires accelometer/g sensor and sounds like you have same problem.
Sorry man .
Reset your phone to default settings there's a great download in inspire development that will revert everything for you the call HTC and they will fix it for free as long as you restore everything to stock froyo or gb ruu. And you havnt tampered with anything etc etc .
HTC said 6-9 days for my phone to get fixed and back to me
Sent from my Desire HD using xda premium
Thank you
Sent from my PC36100 using xda premium

Phone issue

Currently the phone is on CM10, but this would happen on any rom. The phone is frozen with the bottom 4 touch buttons lit up. The only way to fix it is a battery pull and power the phone back on. Not sure what is causing this, but would like to know if anyone has found a fix for this issue yet. Thanks.
Its a known bug in CM10 and probably not a hardware problem. CM10 is still a beta (though a very good one) and quirks like this are expected.
Some versions of cm10 are more stable than others. Ive been using the 8 - 14 build and it has a minimal amount of freezing like this.
Sent from my HTC Sensation using xda app-developers app
Thank god
My phone has the same issue, I thought it was H/W issue because I accidentaly dropped my phone very often. Glad to know it's just a rom bug, or I'll have to buy myself a new phone.
It was happening on stock ics also though. Did you guys see that on stock also?
Set your min cpu to 384Mhz, That fixed mine for sure.
Sent from my HTC Sensation using xda premium

[Q] Random Shutdowns Cyanogenmod 10 Stable?

Hello all,
Semi-noob here, I've rooted and flashed my phone to the Stable version of Cynogenmod, on Android 4.1.2. I haven't added the Lightning Kernel, only because of a pretty annoying issue: the phone randomly shuts down for no apparent reason. I ran a search and didn't see much about this issue so here goes: doesn't matter what's going on with the phone, it will suddenly (and very randomly) freeze for a moment, then go black, the Samsung logo will appear, it'll vibrate, then kaput.
To turn it back on, I have to do one of 2 things:
-hold the Power button for a LONG time;
-remove battery, reinsert, hold Power button normally.
So what gives? Did I flash something wrong? Should I reflash the ROM? Any assistance would be greatly appreciated,
Cheers!
I'd think it's the screen of death.
But when I look at this more, I think of what the oc, governor and scheduler are.
Sent from my SGH-T769 using Tapatalk
The stable version is not very stable. Look for the latest nightly, its much better.
For the latest cm 10 10.1 and 10.2 go here http://www.goo.im/devs/cm/t769/nightly
Look closely at the dates to get the right one.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Somcom3X said:
I'd think it's the screen of death.
But when I look at this more, I think of what the oc, governor and scheduler are.
Sent from my SGH-T769 using Tapatalk
Click to expand...
Click to collapse
In retrospect, I should have thought of that, thanks! I changed it to Performance from Interactive after reading this last week and since then no shutdowns at all. Hopefully this is the end of that annoying bug. Merci! :good:
Whoops, no sooner had I written that than my phone shutdown again. WTF? Anything in particular I should do to stop this?
Try the latest cm 10 nightly? That is what I'm running on 2 phones with no shutdowns like your describing.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
tommyboy8125 said:
Try the latest cm 10 nightly? That is what I'm running on 2 phones with no shutdowns like your describing.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I might flash it when I get back to the US, I am on a long-term business trip and last thing I need is to brick the phone while in France!
I've had similar issues with CM10 "stable". I knew the rom was at fault. I haven't tried the nightlies, but that would have been my next guesses too. I've been looking for a daily driver, and despite some hiccups with MIUI, I've been pretty happy with it.

Moonraker issue.

So I tried the Moonraker Rom yesterday, was awesome IMO. I just had one issue, when I would reboot my phone it would register my battery as dead and shut off before reaching the UI. But if I plugged it in, turned it on, then unplugged it it would read the correct percentage and stay that way until reboot. Is there a fix for this floating around? Kinda reminds me of the depressing "iOS x.x.xx tethered jb" days lol. Thanks in advance
Sent from my HTC Inspire 4G using xda app-developers app
Yes, no, maybe so? I'm currently using "dr no v3.0" and its great. Smooth, reliable, fast. But I would really like to experiment with the moonraker rom, just don't want to deal with the battery issue, am I the only one having it?
Sent from my Htc Inspire 4G using xda app-developers app
No fix that I'm aware of
Sent from my One X using Tapatalk
Pretty sure it was a log issue. I cleared battery logs with a recalibrator and it didn't happen anymore.

Categories

Resources