Database Users

Vibrant turns off in sleep mode

Hey evweryone,
Found a VERY strange issue, that seems to be affecting Captivate users as well. This is my second phone that has had this issue, so its not isolated.
The phone works fine when using it, but when it goes to sleep, occasionally (more and more frequently it seems) it will actually turns off. Meaning, when I pull the phone out of my pocket, its off. Has occurred 3 times today, and I'm SURE i didn't accidentally hold the power key.
First, I thought it was the OC kernel, so I reverted to JAC's non-OC kernel, still turns off. Reverted to stock kernel, still happens. I have a slight hunch maybe SetCPU may be causing it to sleep incorrectly, so I un-installed that.
Anyone else run into this issue? Its a PITA when your phone randomly turns off, cant rely on it at all. Thanks!
EDIT: Phone was ON while sitting on my desk while I was writing this, tried to wake it up....it was off

It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.

Puushiki said:
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Click to expand...
Click to collapse
I will try that and see. Anyone else have this issue on any Galaxy S based device (Captivate, Vibrant or Generic Galaxy-S)?

Oh btw, I have the Samsung Vibrant

Puushiki said:
Oh btw, I have the Samsung Vibrant
Click to expand...
Click to collapse
Okay, confirmed by one user. There is a large number of captivate users having this same issue, and a discussion about it in a SetCPU forum (Link ).

No problems here, stock ROM + RyanZA using SetCPU since day one.
Two profiles: conversative
Battery <100%: 400 min; 1000 max
screen off: 400min; 400 max

Are you guys using SetCPU for OC'ing, or for scheduling?

I was having the same issue, wasn't sure what it was and was going to return my Vibrant, and with that in mind had wiped the phone and gone back to stock. Due to a delay in getting to the store, I did re-install things (hey, I do need my phone) and found that the issue had stopped. I did have SetCPU on originally and have not re-installed it, but it's difficult to recall if I had SetCPU on before or after the issue started. I suspected it could have been SetCPU and since I didn't really feel the need to use it, I just didn't bother to install and and wanted to see what would happen.
It did happen again yesterday, but the phone seemed to just lock up on me while I was using it (was as I was using Navigate, got to my destination, locked up, then shut off, more or less), so it might have just been another fluke due to overheating or something.
Anyway, the problem that I had was that I couldn't get the phone to come back on without having to remove and replace the battery. But fortunately, other than yesterday, the issue has not happened since the past Friday (where it happened 4 times that morning vs once per day the 3-4 days prior). The inability to turn it back on might just be an issue with my phone (and it only happens after this force shut down).

ytj87 said:
Are you guys using SetCPU for OC'ing, or for scheduling?
Click to expand...
Click to collapse
Mainly for stress testing, as the OC kernel doesnt need to be configured to OC, its already running at 100/1200. Mainly for scheduling and stress testing. Occasionally for detailed info about CPU (temp, current speed, etc). Hopefully this issue\bug can get worked out, cause SetCPU is a GREAT app.

I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.

hockeyrcks9901 said:
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
Click to expand...
Click to collapse
Had NO issues today, seems SetCPU was the culprit. Thanks!

Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure

Puushiki said:
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Click to expand...
Click to collapse
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.

I have had the same problem and am using SetCPU. I love it, but this shutting down in sleep mode thing is driving me crazy. Gonna try to turn off notifications and move to conservative and will report what happens.

I use SetCPU regularly on my Captivate and only see issues if I change the governor or polling interval, or if I use profiles.
Sent from my SAMSUNG-SGH-I897 using XDA App

hockeyrcks9901 said:
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
Click to expand...
Click to collapse
**** speed aye?

Don't use setcpu!!!!
Sent from my SGH-T959 using XDA App

xaisomboun said:
**** speed aye?
Click to expand...
Click to collapse
lol. That's swype for ya...
Typos and other gibberish courtesy of Swype

I have this problem several times a week. The phone is NOT rooted. What are my options for curing this problem besides rooting?
Thanks for the help.
Samsung Vibrant, Android 2.1, T-Mobile

I read somewhere that Galaxy S users should NOT use conservative and use on demand instead for this reason... not sure though.

leedroid lag?

Hi, I've just flashed leedroid but I seem to be suffering with some small amount of lag that I didn't experience on the stock Rom..... when I open messages or emails for example there is a small pause, and u can visibly see the screen refresh. I never suffered with this this beforehand. Also I have noticed that I'm getting some lag when changing certain settings, the leedeoid Icon pops up whilst its thinking..... now, so far I haven't gotten around to installing the LeeDrOiD Ace V2.2.5 R2 Kernel, is that likely to fix my little issue?
Cheers
Steve

After flashing, have you done another reboot? Sometimes I find a new ROM doesn't settle until I've rebooted a couple of times. Give it a try and see how it feels then report back either way

Let it bed in steve, should have dropped this in the rom thread

LeeDroid said:
Let it bed in steve, should have dropped this in the rom thread
Click to expand...
Click to collapse
New members aren't allowed to post in Dev section until they hit a certain post count

Yup...reboot will fix your problem..
Sent from my Desire HD using XDA App

Thanks for the reply Lee, but as citizenlee said, I'm unable to post in that section at present.
So far i still seem to be having the slow refresh issue on sms and emails, do u think that the fact I haven't flashed the Ace V2.2.5 R2 Kernel yet could be part of the issue? I'm certainly going to try flashing it to see if it helps..... I know know you've put a heck of a lot of work into this and believe me it is appreciated, just hope I can get it working as well as it was intended.

You could try the kernel... and failing that a full wipe and reflash of the ROM should sort you out

problem
LeeDroid said:
Let it bed in steve, should have dropped this in the rom thread
Click to expand...
Click to collapse
dear lee i have installed your PERFECT rom 2.2 1.8 ghz
but it has frozen 2 times the screen and after rebooting it stays frozen...?
this also happened with coredroid ..any suggestions my friend?
regards(i am new here^^)

Ok, i think i got to the bottom of my lag problems. I have been playing around with set cpu today. I think the minimum speed of 245mhz in smartass was too low and was causing the lag (usually when waking the phone from screen off) I have now changed settings to 'ondemand' with a minimum speed of 245mhz and maximum of 1344mhz but i also created a 'screen off' profile with a working range of 245mhz to 576mhz which seems to give it a bit more poke when waking from screen off No more lag! ( i still have the visible refresh issue i mentioned, maybe i'm imagining that one though, maybe it did do it on the stock rom but i didn't take note of it....??)
So, i really have no idea if i've done the right thing with the way i have set up setcpu so if anyone would care to comment on the settings i've used please do so.
Many thanks again for all the help.
Steve

Questions about standby mode

I may have asked this before, but I'm not sure.
My A500 has a custom ROM on it, but its had this problem on multiple roms. I haven't tried on stock yet, but that's probably my next step. Anyways, here are my questions:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
When I first got it, I remember leaving my A500 in standby mode (it should automatically go into standby when you idle, right?) and being able to wake it by hitting the power button almost a day later. Now I can only do it for a few hours and then it won't come out of sleep. I'll have to turn it off by holding the power button down (even though there is no indication that it is turning off), then I can turn it on again. Sometimes my battery will be depleted, apparently indicating that it did not properly go into sleep mode?

chairhome said:
- How long can you usually leave your A500 in standby mode and still wake it up?
- Is there a way to manually put the tablet into sleep mode?
Click to expand...
Click to collapse
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.

All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..

Moscow Desire said:
Usually I can leave it in sleep mode for well over a day, and it still wakes.
Press the PWR button will put it to sleep.
I would guess, the problem is Kernel related. This sometimes happens with kernels that supply Over/Under voltage. Usually for overclocking. Most of the newer kernels walk a fine line with trying to get maximum battery life, and your tab may suffer "the sleep of death" and require a hard re-boot.
I would advise one of the older kernels, like RTrips 3.4+ or Thors 3.7. Try to stay away from the most recent kernels.
Also, a few of the custom 500 roms, are really "cooked". Lots of changes to the rom itself.
You may want to try a lightly stock rom with a lower version kernel. This will fix the sleep of death issue.
As with your battery, the usual stuff like wifi/gps on, notifications, syncs, these all cause battery drain.
I leave my wifi on, but my syncs are set to every hour. Mail, Sms, and FB (silent). GPS is hard set to off. Widget refreshes also are 4 hrs.
I lose maybe 6% or so overnight.
Click to expand...
Click to collapse
erica_renee said:
All of the above is true there is one more issue that can occur . Google backup and restore.a bad app that you keep getting restored by the above.
if all else fails you can try the fallowing..
download a near stock rom.. with STOCK Kernel .
in cwm
of course wipe all
format all..
flash rom..
wipe all again.. (you know all of that)
if im having a app issue.. to find the app.
when your tablet boots the first time.. when you get to setting up your google account.. untick the boxes for backup and restore of data.. then install your apps one at a time back . to see what app is causing the trouble.. Of COURSE this all only applies if the rom flash does not work.. google often puts the problem back.. Ti backup will do the same .. put issues back.. Trial and Error is only way to solve this issue. ITS THE ONE MOST COMMON AND MOST TALKED ABOUT ISSUE WITH not only our tablet but all of android devices..
GOOD LUCK ..
Click to expand...
Click to collapse
Thanks to both of you. I needed reassurance that my tablet wasn't just messed up. I have a warranty on it and was thinking about getting it replaced and seeing how the new one behaved, but I'll try the suggestions. I'll probably try to reload my ROM after formatting and start with just the base apps and add one at a time as you suggested. If that doesn't work, I'll try a different kernel or ROM with a different kernel. I've already tried not using SetCPU to under/overclock, but that didn't work. Thanks again!

Another (relatively rare) issue is that the kernel you're using actually is flawed and fails to wake the GPU after it went to sleep (this may be a lot later than the device itself, depending on background services!). In this case using a different kernel will solve the issue (stock kernel is works).
EDIT: Posted at the same time... By all means try another kernel, this is a known evil with custom ones.

Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.

OK, before you take your tab back, personally, I wouldn't worry about it.
I have noticed, on some occassions, (yes, I do run stock rooted on occasion), that sometimes, the tab will get what we call the sleep of death. And usually, this may occur over a long period of time. Also, sometimes, I have to hit the pwr button several times, before it wakes.
+1 with the PP on overclocked kernels. This happens with the most recent ones.
Fortunately, System Tuner Pro, will increase MB voltages, so you don't get this.
If it does it again, and you are on stock, try to press the pwr button several times.

cool, thanks. I'll try this today.

chairhome said:
Okay, so I've tried installing the stock, rooted 3.2 ROM which uses the stock kernel. Did not restore any apps from Google Backup. Still getting the same issue. Does this point to a hardware issue? I have a warranty on this tablet, so I want to know if I should try trading it in.
Click to expand...
Click to collapse
Mine has never worked on any rom with any configuration. Turning off wifi helps sometimes.

[Guide][Theory] Samsung Galaxy Note ICS Build SOD Fix!

I have found the fix for SOD's on ICS builds (based on i9220 leak kernel)!!
THIS YOU DO BY YOUR SELF! I TAKE NO PART IF YOU HAVENT READ THIS THRU AT LEAST 2 TIMES BEFORE DOING THESE STEPS!
First of I had a theory of the i9220 kernel and its CWM that in one way it does not represent our hardware right. It has its differences and they are more on a file level then anything. This can be shown easy by trying to format /system. By doing so you will get in to a world of trouble (so don't try it, just trust me)
So my first thing as I have never had a SOD was try to RECREATE a SOD. So my theory is/was that the kernel provided for the i9220 is the real culprit in this scenario and that by flashing RADIOS with its built in CWM is a MISTAKE!
And boy was I right! I installed a random N7000 radio .zip thru CWM (Now when I say CWM I do NOT mean some crappy .apk or app that does it FOR you. I mean the CWM you enter by starting the phone with Power + volume up + home button) and rebooted the phone.
I played around with it and let it rest for 30min. When I was going to wake it up again... SOD!!
Mission Accomplished!! Recreated Error!
So now ... how to fix it...
First off wee need to learn how Mobile Odin works and why this method works to fix it. When Mobile Odin is instructed to flash a ROM or anything else (like a radio) it boots to ITS OWN KERNEL! That is the file that Mobile Odin downloads on first run!
Now IF you are going to use Mobile Odin while on any ICS build (except the original i9220leak! Important! Mobile Odin will NOT work on stock i9220 leak!) you have to be 100% sure that you are PROPERLY ROOTED!
So Steps...
Step1: Get ZCLP1.zip Radio from the Radio Thread and extract the modem.bin file.
Step2: Get Mobile Odin and just flash modem, nothing else. The modem.bin you just extracted.
Step3: It should reboot and enter the Blue Odin Droid Kernel and flash radio.
When its done it will reboot again. And you will probably be SOD Free!
Hit the thanks button if this worked for you guys. Thanks for reading.

Oh btw I don't think that it is locked to use only that modem. I had la3 radio before and I didn't suffer any sods so don't get to blind on just the Chinese radio...
| GalaxyNote ICS | Tapatalk |

im on midnight 2.0 ics.i done what u said in the post.i just had a sod.
here is how it happened.i pressed wifi in pull down notification.it was stuck ..wifi would not turn on after the screen turned off and try to awake by using power button.it was dead.it would not do anything.had to hold power button for couple of min to restart.

Im currently on gb, used ics for a couple of weeks since chinese leak. Im not a 100% sure, but i really think it has something to do with wifi. I never really tested but I always had the most sod at home while connected. Rarely had sod at work, which was cellular data H+.

There is another method and that is to increase min CPU speed from 200 to 500mhz. Has worked for some...
| GalaxyNote ICS | Tapatalk |

Thanks mate, i'm gonna try some of that.
These SOD are making me crazy :/ Some day i can have 0 SOD and the day after 1 per hour...

You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA

super_sonic said:
You can use Wakelock and no more Sod...
Sent from my GT-I9220 using XDA
Click to expand...
Click to collapse
But wouldn't that drain the battery faster?
Sent from my GT-N7000

I only get sods when wifi doesn't activate too. If it doesn't switch on immediately then the phone won't come out of sleep. I just restart manually when this happens instead of letting it sleep.
Sent from my GT-N7000 using XDA

I get SOD with or without wifi completely randomly. I'm going to try increase CPU see if that works.

excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx

It's not specific to the radio. I've done Mobile Odin Pro to try many different radios. Each time, I'd get an SOD.
Folks have also reported getting an SOD WHILE in Airplane mode. This completely puts the baseband issue out of the picture together.
If it's in airplane mode, it can't be a WIFI issue too.
The kernel itself is just bad and it has its quirks.
Due to the inability to get a logcat when it is in a SOD state, it makes it very hard to pinpoint what is causing the SOD.

MaZaGnGy said:
excuse me wt is SOD issue meaning ?
i know its a very stupid Que
but i hoppe to till me wt is it
thnx
Click to expand...
Click to collapse
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!

robmeik said:
SOD is Screen Of Death or Screen Of Darkness; meaning that the screen will not wake up up after you turn the phone on and you have to restart/reboot the device. Various things cause it... Have a search and you will learn more about it!
Click to expand...
Click to collapse
Nope, it's Sleep Of Death. The rest is correct
Sent from my GT-N7000 using XDA

We need a SOD-off app

Look for wake lock power manager in play store. It creates a wake lock, preventing deep sleep, and consequently a SOD. For the price of a low battery autonomy.

I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.

masiullah said:
I was having lots of sod's on aosp v7 and the reason was not related to ROM. it was something to do with the cpu frequency and voltage in the chainfire ics kernel.
Steps I performed to reproduce.
1. Use setcpu or system tuner to set the cpu frequency to 500 mhz when screen off.
2. As soon as the screen is off you can see that note is not responding to keys. Sod reproduced !!!!
In my opinion it has some thing to do with the voltage at frequency 500 mhz, may be the voltage is a little bit less for that frequency and it refused to wake.
Hope it helps some one with the similar sods.
Click to expand...
Click to collapse
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.

Akiainavas said:
We know that ICS leak comes from i9220 and that it's set to work at maximum 1200Mhz.
Now the question is - do i9220 and n7000 use exactly the same CPU ? If so, then we can rule out voltage problems - unless engineers at Samsung f....up.
For all it's worth, that's an early build leak...when official update will be here, i think our problems will be over as we'll just use the proper kernel with our ICS roms.
Click to expand...
Click to collapse
Is there any way or app which stops using certain frequencies.

[Q] Troubleshoot shutdown on 4.3/4.4 based roms

My phone shuts down on 4.3 and 4.4 based roms.
It happens much less often on 4.2 and stock based roms.
It seems to happen when the screen is off. It doesn't shut down when I'm in the middle of doing something. I've seen that on other phones.
If the screen is off, but I'm listening to the music player or Pandora, it does not shut down.
It does not seem to be overheating.
I'm on my 3rd sim card in 2 months and my second class 4 SD card. I only bought a new one b/c used the one from my old phone and thought it was best to start fresh.
Currently I'm running the first CM11, but this has been happening on CM 10.2, AOKP, and a variety of other roms.
My recovery is TWRP 2.6.3.0
I use the regular GAPPS, not PaGAPPS and the appropriate GAPPS for the given AOSP base; 4.2/3/4
I flash SuperSu-v1.65 after a full wipe when installing new roms.
The current apps I have installed in addition to what comes with CM are:
Evernote
Freecell
Google Voice
gReader Pro
Pandora
Quickoffice
Rom Toolbox Pro
Scanner Radio
Shuttle+
SMS Backup+Restore
Solitaire
Tapatalk Pro
UPM - Universal Password Manager
Xposed Installer - I don't have any modules installed at the moment and the last time today it shut down by itself was before I installed Xposed.
I know that logcats are good for tracking down errors for apps that FC, though I don't know yet how to read logs.
Is there an app I can use that can show me activity before the last shutdown?
How can I track down what's causing it?
TIA

please delete
On 2nd thought I did not feel I could contribute well.

Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision

aviwdoowks said:
please delete
On 2nd thought I did not feel I could contribute well.
Click to expand...
Click to collapse
Thanks for trying though.

ATTACK said:
Sounds like S.O.D's (sleep of death). It's a kernel problem and I believe they're cause by qcom's hot plugging. You could rename MPdecision to MPdecision.bak and reboot. That will keep the second core on and it should help. I used to get them as well until I updated to the two latest updates. But SOD's are a well known issue with the RAZR M.
Sent from my XT907 using Tapatalk
EDIT:
Code:
system \ bin \ MPdecision
Click to expand...
Click to collapse
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?

FirePsych said:
Attack,
Thanks for the response and thanks for the clarification.
I found two instances of MPdecision, so that narrows it down.
Sorry, but answers always do tend to lead to more questions.....
What functionality do I lose by "disabling" it?
If it keeps the second core on, does that have a significant impact on battery life?
Does the governor have any impact on that?
Would other kernels make a difference?
Click to expand...
Click to collapse
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.

Thanks,
I had read that the SOD had been reported elsewhere, but never saw any solutions. Just lots of folks replacing their phones.
I haven't had one in the last 24 hrs on the 12/08 CM nightly and flashed the 12/09 this morning.
I also made the MPdecisions change. We'll see if it sticks. I assume since it's a system file, I'll have to make the change every time I flash a new nightly or or new rom, but that's not a big deal.
Oh, and yes SOD is probably more accurate than "shutdown" because I've noticed that the led will flash if I've received a message, but I can't revive the phone, so obviously it's not complete shut down.

ATTACK said:
MPdecision is qcomm's hot plugging service that keeps the second core off when its not needed by the system and turns it on when it is needed. By disabling MPdecision, you'll have better performance and slightly higher battery usage, but it's not very noticeable (battery usage will very on how you use your phone). Governor's have no impact on SOD's and all kernels for the Razr M are basically the same either stock or CM's both use the same MPdecision (which I believe to be the problem).
I could be totally wrong and you could have a hardware / software problem. But I know that when I was having this issue, I disabled MPdecision and the SOD's stopped.
Click to expand...
Click to collapse
@ATTACK.
Thank you!
I hate to jynx myself, butthis seems to have done the trick. Only had 1 or 2 BSOD since your response and I think both times were because I forgot to make the change after flashing a new rom.
Happy Holidays
FP

This thread may have saved my phone. I keep waking up to find my phone with a blinking LED notification and me being unable to get the screen to turn on. I renamed the MPdecision file and I'll hope for the best. (^^)