Database Develop

[Q] Cannot receive incoming calls

Sprint HTC Hero
DarchDroid v2.8
Recovery: RA-Darchstar (v1.7... I think)
PRL: 60667
I bought this phone last week, rooted it, and attempted three or four different ROMs before settling on DarchDroid (which is awesome, by the way!). I was initially having issues with multiple FCs and it eventually became unusable until I read up that my device might not be able to handle the OC to 710mhz. I installed the OC widget and throttled it down and now it works like a champ and is still WAY faster than the stock 2.1 ROM. I am still having issues though, that hopefully, somebody can help me with or point me in the right direction. I've spent the last hour scouring almost all parts of the forum and can't find any answers to these issues. Forgive me if I looked them over...
1) All incoming calls go directly to VM. I can make calls and send / receive texts, but no incoming voice calls.
The next one is a two-parter...
2a) The phone will occasionally become so sluggish (borderline non-operational) that I need to reboot it. When I do, I clear the cache and it will reboot then function normally. Could this be a result of a widget that I have installed? (OC widget, battery monitor?)
2b) When I reboot the phone without booting into recovery (normal reboot) it goes into a continuous boot loop. When I try to restore my Nandroid, it still boot loops and I have to wipe and re-flash the ROM. Is this normal?

Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.

I had the same issue with the latest Fresh Rom so I ended up switching to Zen Hero and have never had a FC on an incoming call since. I tried all the fixes for Fresh and never had any luck. I would suggest trying another rom.
p.s. I was able to OC the rom also and it still works fine.

chromiumleaf said:
Have you tried re-flashing the ROM? Sometimes that fixes some of these kinds of issues....occasionally a ROM install won't go perfectly and simply wiping everything then reinstalling can correct some issues.
2b) Those bootloops you're getting are almost definitely because your phone can't boot at OC speeds. Even though you've scaled down the CPU with the OC widget, that doesn't actually take effect until after the phone has already booted and gone through its start-up processes. So until then, the kernel is making the phone boot at 710 or maybe even 768mhz, which it looks like your phone can't handle. Search through the Development forum and look for one of the 691mhz kernels -- flashing that may fix these bootloops for you.
Click to expand...
Click to collapse
Thanks for the advice. I ended up biting the bullet and calling Sprint and it turns out all that was needed was a refresh on my account, the phone works like a champ now! I'm using the OC widget and throttled it down to 595mhz, and even OC'd that little bit, it still BLAZES when compared to the Pre that I came from. No hitches or waiting - when I open a program or app, IT ACTUALLY OPENS QUICKLY... an amazing concept!
One more question though: in case I need to reboot, is there a way to save all of my phone settings? I already moved all of my apps to the SD card so I don't have to download them again, but it would be really helpful if I could just load a save file that would re-set my settings to the way I had them before. Is there an app or setting in the ROM for that?

Make a nandroid backup through recovery. It saves every little detail of your phone and if you ever need to go back to that you can simply restore that backup. Titanium Backup is another popular tool but I've never used it myself so I don't know anything about it.

JAC kernel bug: using audio randomly kills phone

(I figured to post this in Android Development as it wasn't really a fit for any other forum; and made its own thread since multiple ROMs and threads use non-stock kernels.)
I ran into an issue running JAC's OC/UV kernel, as detailed at http://forum.xda-developers.com/showthread.php?t=806116 . Essentially, whenever any kind of audio was playing, whether through headphones or the speaker, local media (i.e. mp3 player) or remote (i.e., Pandora), at some point the phone would just.. die. Capacitive buttons wouldn't light up, no unlock; music would die; and basically a battery pull was required to turn the phone back on. adb logcat reports nothing - you can see the audio streaming, then the logcat shut off with the phone.
Based on the thread above (and searching the Bionix thread), it seems that a non-stock kernel does this. (There are only a couple of posts out of the thousands on Bionix's thread.) I have not tested KingKlick's kernel, only JAC's; perhaps KK doesn't suffer from this. This issue is independent of overclocking/underclocking the phone (verified by setting JAC kernel to 1000/200, then uninstalling setcpu); Voodoo lagfix (verified by disabling lagfix and running audio for about an hour); and ROM (tested using multiple versions of Franken-Twiz and Hybrid - maybe there's an inherent issue with eugene's mods, but I haven't seen any other posts.)
I suppose this thread serves as a warning/bug report for anyone that might encounter this issue if running a non-stock kernel. The best way to resolve AFAIK is to revert to a stock kernel.

Thank you for posting this! My phone had suffered from this at random times since I started using JAC's kernel. I asked about it in a couple of threads but never got a single reply. Glad to know it's not only me

I'm running the same kernal and about 20 minutes ago running pandora my phone just turned off too and had to pull the battery to restart
Sent from bionix 1.9.1 jacs oc/uv kernel

Had that issue at the Gym the other day, not even on Bionix.

I had similar issues, also with the KK Kernel, its not just JAC's kernel. You don't have to pull the battery either to get out of the freeze, you can hold the power button for several seconds and it does a hard reset.
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Just a little work around, try it to see if it works for you.
Sent from my SGH-T959 using XDA App

Actually this is a known problem since even the G1.
If you have anything like setCPU, which I do, and you set the idle or lowest speed lower then 400 Mhz the phone will more then likely freeze up when playing music or when going to idle.
I don't remember off the top of my head what causes it to do this when it goes below that certain Mhz, but Im sure I or someone here can dig the old thread up.

Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App

Ive had this problem to.... but it was ONLY with Jacs 1.1, I revert every ROM back to his 1.0 and have no problems. Everytime I dont, I get a phone freeze.

I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys

jmercil said:
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Click to expand...
Click to collapse
Interesting. I'll try installing JAC OC/UV/Voodoo again and see if this observation is consistent.

r6kid said:
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
Click to expand...
Click to collapse
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.

Would have to agree. There's a bug somewhere. Not sure if its limited to jacs though.
Currently on masters rom kk. Only problem is pandora.

i had this problem too. kinda disappointed cause the kernels make everything run so much better. so i had to go back to using stock cause i listen to music a lot :/

There's definitely some hardware variability, because I can't recreate this bug. I listen to music all day long (MixZing, Slacker, Pandora) running 1.8 w/ JAC's OC/UV Voodoo. Never seen this.

Likewise with Jacs 1.1, had a couple other weird issues running that specific kernel too, not a single problem when I flashed back to 1.0
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo

i get this same thing. ive had it happen with SetCPU both installed and not. right in the middle of a good song bam phone just shuts up. walk over to my toolbox and sure enough the phone is in a state of being divided by zero and only a battery pull lets it return to the world of the living. not greally a good thing when i have sevearl iphone dorks in the shop and they pop on over to my speakers and they say out of the way lets plug in a REAL phone. makes me want to scream LOL. ****ing iphone >_<
i retort with soooo when you get it out of the box....thats it right? nothing can be changed right? oh look that program sucks....what you cant make your own? ...yea...i thought so. hey look im making a call in the scrap room surrounded by 4ft thick concrete walls.... i got full bars lol. they got nothing in the empty parking lot cuz there holding it wrong LOL

Blkegk said:
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Glad it worked for ya!
Sent from SGSV Bionix 1.9.1 KK OC/UV with the quickness!

sxfx said:
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Click to expand...
Click to collapse
I tried that though, as you can see in the thread I linked to above. Uninstalling SetCPU didn't help..

I think it's hardware.... One of the unlucky ones....

Try with a stock kernel. Jac and kk kernels do uv by default, which is like overclocking in reverse. It has the same possible stability issues.

[Q] Weird OC/UV Kernel Issue...

Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.

HTCOmega said:
Ok, so here's the deal - I'm not sure how best to explain this so bare with me... basically I've been running various oc/uv kernels for a while now on my Captivate and have had minimal problems with them. I've had the occasional freeze due to too low uv settings but never anything as weird as the freeze issue I'm having now.
I d/led several kernels to play with and ended up with GB's Steam kernel via Serendipity 4.3 (which is the ROM I'm using now), moved onto Suckerpunch's Suckerpunch-SmR-#27-1280-500hz-CWM to Speedmod-Kernel-i897-k12s-cold-500hz-CWM I think, then to GB's rGB-v.4-011811-voodoo-cwm and now I'm on Suckerpunch-SmR-500mz-#32-CWM (or w/e the full name is...) The issue is that my phone is randomly freezing w/o Voltage Control/SetCPU/Galaxy Tuner running or even installed (as is normally the reason for freezing with me and oc/uv kernels). Now I had VC and GT installed but realized GT wasn't going to be much use so I uninstalled and VC was never set to keep settings at boot so I don't think that VC would be the culprit but I'm not sure...but anyways, I noticed that the freezes started the other night after I tried to add a task widget to my ADW EX launcher via SpringPad with the current screen full. When that happened, my phone lost it's mind...it caused the launcher to repeatedly FC and when you would reopen the launcher w/ the home key it would load to a point where the widgets started to load then it was like it hit what was supposed to be that SP widget but then it would realize the screen was full and would FC again. Well, I FINALLY managed to clear the launcher data, retried, no success, uninstalled SpringPad, launcher still FC'd, uninstalled launcher, no FC (as it wasn't there anymore...) but the phone would now randomly freeze up with little to no provocation. I finally broke down and flashed a different kernel to see if it would help and oddly enough it did. It was only when I flashed a non-oc/uv kernel that it would stop freezing. Now I can't see any correlation between the freaking out launcher and the kernel but who knows, right? I tested my theory by leaving the launcher and app uninstalled and reflashed a ov/uc kernel. About a minute after loading the phone would freeze. The few times it would actually run longer than a minute it would die when I was listening to Slacker Radio and I would get a text. The phone would cooperate until I actually SENT the message and then it'd die. I think I rotated the phone at this point, too, and it did the same freezing deal when I was typing up a comment on Facebook and rotated the phone.
So...in the end, I'm stuck. I'm not sure what it could be. I really don't feel like backing up and reflashing so I may just stay w/ a non-oc/uv kernel until I decided to flash again but if anyone has an idea on what to check then I'll be happy to do it. I saw somewhere that if you had an oc/uv kernel w/ boot settings set that you had to clear those out prior to flashing certain kernels or risk conflicts. Don't see how that would apply here since I didn't have boot settings set but figured I'd throw that out there before someone asked.
I'm running Serendipity 4.3 w/ SuckerPunch SmR 500hz #32 kernel w/ lag-fix enabled and I9088ZNKP1 modem on Android 2.2.1 for reference. VC is installed but obviously won't function on this non-oc/uv kernel. Voodoo v4 is installed for whatever that's worth.
Anyone have any ideas on wtf is going on??
And I apologize for the horribly long, terribly worded post. I've been at work since 8 this morning and I'll be here til midnight...I'm running on fumes at this point. Woo...lol Thanks in advance, guys.
Click to expand...
Click to collapse
Kernel flashing doesn't always go smoothly. Repeated kernel flashing without complete system wipes in between can cause some things to start going horribly wrong.
Don't use SetCPU to set clockspeeds. Just stick with voltage control.
If you forgot to disable any lagfixes at any point along the way, that could explain alot of the problem.
Suckerpunch kernel is a great concept and is showing alot of promise, but I personally have had alot of stability issues while using it, including random freezes (YMMV, of couse).
Just my opinion, but I would just back up all your data, flash back to stock, master clear, wipe all your cache data, reflash your rom, pick a kernel and stick with it for a while. If you want pure stability and battery life, use the most recent version of either DG's Firebird kernel 2 or Hardcore's speedmod kernel. If you want stability and oc/uv enabled, stick with Glitterball's kernel. Those 3 have been the best for me personally (again, YMMV).

Blitzkrieg trouble

FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!

At least you got it installed, I couldn't even get that!
Sent from my Gingervolt-ed VS910 4G using xda premium

Mark Once Again said:
FYI, I installed Blitzkrieg Kernel 1.0. My phone phone was very unstable and would restart often. Guess mine is one on the "picky" ones. Went back to GingerVolt 1.3 and all is well.
Thank you!
Click to expand...
Click to collapse
Was it still unstable if you turned it down to 1GHz instead of keeping it at 1.5GHz?

I never could get that far. As soon as the phone was almost up it would restart. I tried about 5 or six times. I am happy with the phone without Blitzkrieg. Just thought I would pass along the info.
Thanks to all!

Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...

vortmax said:
Make sure it's not plugged in on the initial boot after the install. Mine would reboot as well...until I unplugged it. Once in the OS, then I undercooked to a more stable 1.4GHz...
Click to expand...
Click to collapse
I wonder why of all things, that would make a difference. You must've figured that out by chance? Haha
Sent from my Supercharged, Blitzed LG Revolution using xda premium.

I tried plugged into the usb on my pc, plugged into the charger and not plugged in at all. Same result each time. No complaint, just thought it might help having the info out there.
Thanks again!

You might try first installing a CPU utility like setcpu, and setting it to do no more than 1ghz on boot, and then flash it
Sent from my VS910 4G

Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.

brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
Turn up the min. That fixed it for me

brad08stanggt said:
Guys I have the same issues on GingerVolt 1.3 with the Blitzkrieg kernel.
Random reboots.
The phone starts vibrating randomly for like 10 seconds, then reboots. Happens like 10 times a day.
I tried to play with the SetCPU Over Clock settings, with no luck. I lowered max CPU to 1ghz max, I even removed set CPU, nothing has helped.
going to try to re-flash GingerVolt with the stock Kernel see if that helps. I don't need the OC Kernel if thats causing the issue.
Click to expand...
Click to collapse
You can turn off the haptic feedback to minimize that vibration reboot but it won't solve the issue tho
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p

For those who use blitzkrieg kernel I recommend using cpu tuner instead of setcpu
I've been testing both app extensively for the past 2 weeks and notice cpu tuner is much more stable than set cpu and both have the same features
I use the free set cpu verison that you can download on the xda site that's the same as the paid version you get on the market
BLITZ Bulletproof ledded AWD SuperCharged GV + Nitro ;p

Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?

I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.

keynith said:
I have the same problem, my phone vibrates for ten seconds then resets. Or the screen stops working and I have to lock and unlock the phone for it to begin working again.
Click to expand...
Click to collapse
keynith, try to set the min cpu speed to 768 in setcpu.
So far after changing the min cpu speed i haven't had any issues again.

Did that yesterday and no problems since seemed to work
Sent from my VS910 4G using XDA App

brad08stanggt said:
Guys I seem to still be having the issue, I dont get it.
I did a factory reset, cleared all caches, and reinstalled plain old GingerVolt 1.3 for about 1 week with no issues. But i really didnt set up the phone completely, just installed the basics i need (work email, gmail, contacts, calendar, pandora).
I imagined it was the blitzkrieg kernel at this point, so I wouldn't put it back. so i did a titanium restore of my old apps and system data, but did not re-flash the blitzkrieg kernel. I figured this was my best way to get everything set up with my preferences again. I have specific settings for a lot of stuff, it would take forever to redo.
It was fine all day yesterday and today its rebooting again. Set CPU did reinstall as part of my restore.
Does gingervolt 1.3 do any undervolting/clock speed adjustments by default? My set CPU was set to min 245 and max 1024. I bumped up the 245 to 768, but I am wondering if that even the cause. What are the stock clock speeds? Or does it run at 1ghz all the time in stock form?
Click to expand...
Click to collapse
Best thing I can say to do is to Restore to default and install things one or two at a time. It's likely an App causing the issue. I have had that happen a few times on my Droid 2 Global. Every time I would run the Goggle Nav App, my phone would randomly reboot. Don't have it installed, would be perfectly fine, until I installed Pandora app. Some buggy apps can cause such issue, and also bad settings. So, I would suggest going the 'long way' and starting from scratch and installing only necessary apps one or two at a time. If things work good, move on to next apps. When things go bad, recall the apps you just installed where the problem occurred. Restore your phone, install only those apps and see if you have reboot issues. If so, you are closing in to finding the real problem. I doubt, even by the post you wrote, that it's the phone or hardware. You need a factory fresh restore, including wiping ALL data, including settings for your apps.
-Cybie

Well?
I don't know if you guys fixed your problems yet, but I kinda had some of the same issues and I do not use CPU Tuner or Set CPU! Also I know that when you install Blitz 1.3 It defaults to normal CPU speeds that are already in phone settings as checked by CPU Spy after flashing Blitz. I have been using Antutu CPU Master Pro to set speeds and profiles works great for the price I use it on my Viewsonic G-tablet as well! Anyway what my first issue is the screen locks I had them all the time and the only way I kept them from happening was to set my min at the 245.76 MHz and my all the time max at 1200MHz. I also set the screen off at 122.88MHz - 245.76MHz On demand scaling profile to keep it not wakening from sleep quick enough. Antutu has all kinds of settings in the Pro version and If you want a overclock I think its the best to use.
The only Issue I have not figured out is you guys get a 10 sec vibrate then a reboot I get a Vibrate forever until I reboot I got woke up this morning at 4:00 A.M. by my phone vibrating next to my bed only happens at night and only when I start receiving emails early in the morning. I tried several screen off settings and not having vibration on at all and still happens figure that one out and I will gladly try anything you come up with!!! The only time it doesn't do it is if it is plugged in and charging!

Softkey lights
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
EDIT: charging to 100% fixed this.
Thanks for the quick reply and all your other posts too mt, they are very informative.

anangelablaze said:
I've successfully rooted my revo and have added gingervolt and blitzkrieg.
The softkeys will illuminate about every minute for a second or flash twice when in sleep-mode. I did some reading and tried to reboot and change display settings but they still keep going on and off. Any help is appreciated.
Click to expand...
Click to collapse
Charge it to 100% and it will stop

Cm7 and random freezing

I'm running cm7.1 stable, running off emmc, and every now and then my beautiful NC just locks up, I have it OC to 1.2ghz, I did a search and only end up with results from older nightly threads. Is this a common issue or just me?
PS... I have reflashed and cleared, data,cache, etc..
Thanks
Sent from my NookColor using XDA

Have you always had the issue or did it start recently? I would look at uninstalling any new apps you downloaded prior to the issue starting. There is a good chance you might find a bad app to be your problem.

It wasnt happening before, I tried cm9 with opengl, after I reverted back to cm7(fresh install not nandroid) it started happening, the apps I am running were the same apps I was running before trying cm9(and the freezing problem wasn't happening)
Sent from my HTC Sensation 4G using XDA

Since you are going for a clean install anyway and there is no issue with the CM7 install script did you try the factory reset option or was it just the caches that you cleared? Have you confirmed that you have a good download of the CM7 zip?
Also you might want to try flashing your latest nandroid and make sure that is still running the same as when you created it. If so and you still want to install fresh try it coming off of that one instead of from CM9.
JP

I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.

511pf said:
I've had trouble with both Beautiful Widgets and Google Currents locking up my CM7. Got rid of those and I essentially never get lockups any more.
Click to expand...
Click to collapse
I do have beautiful widgets installed, let me remove it and see if it helps
Sent from my HTC Sensation 4G using XDA

So did removing BW resolve the random freeze? My wife's NC is doing the exact same thing and she has BW too. But I just installed CM7 on hers last night so not sure if BW is the culprit or not yet.

I've been running CM 7.2.0 RC1 from SD card about a month now, and I've experienced a number of freezes. On April 5, I had two freezes within a few hours, and I started keeping track of the freezes, hoping a pattern would emerge.
From April 5 through April 17, there were a total of eight freezes. I don't know what the uptime was when the first freeze occurred on April 5, but all subsequent freezes occurred with less than two days uptime. During those 13 days, uptime got above two days on two occasions; both times a "Sleep of Death" occurred before uptime reached three days.
Was there a pattern? Yes! Every single freeze occurred while I was using Opera Mobile browser, and browsing these forums at forum.xda-developers.com.
On April 18 I started using Dolphin to browse the xda forums, and there has not been a single freeze so far. (I still use Opera Mobile for other browsing.) Uptime had reached five days when I voluntarily rebooted this morning.
I realize this may not be relevant to the rest of the discussion in this thread, which seems to deal with CM 7.1. Then again, maybe it is. This seemed the logical place to report the observation.
Update: Opera Mobile has updated to version 12.00.ADR-1204201824 on April 25. I'll revert to using Opera Mobile on the xda forums, to see if it still freezes.

My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.

threebeers said:
My freezing problem was resolved by moving a bunch of apps from SD back to phone. I left on the SD partition apps I don't use often, and I made sure all apps on my launcher page in ADW were on phone.
Click to expand...
Click to collapse
You really don't gain much and lose a lot by running apps installed to sd. Since everything is automatically on 'sd' with an sd install, those that say they are installed to phone are really still on sd (in /data, which is also on sd). The only reason to install apps to sdcard is if you have so many installed that you have no more room in /data. And with sd installs, usually the /data is made of a generous size. Installing apps to sd slows your system since it has more system overhead to work through.
I know it sounds confusing, but with sd installs, installing to phone means installed to /data which is a partition of your sd. If it says installed to sd, it means it is installed to sdcard, which is another partition of your sd. So no matter where you tell it, it is all on sd and /data is faster because of less system overhead.

For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!

pink401k said:
For anyone else having this problem, I found that if it was overclocked for me, it would freeze a lot more frequently. But, that may have just been bad luck on my part!
Click to expand...
Click to collapse
Came to post the same thing. My nook color will run max OC 1200 but often it will freeze for no reason. After many attempts of uninstalling the many different apps I thought were causing it I started moving the OC lower in small increments and running for a long as possible without a freeze. Finally got down to 975 and haven't had a freeze in days.
Kinda disappointed though since someone got it at 1600 and most run at 1200 and all I can get is less than 1000. I'm probably moving to a Asus Transformer Infinity soon anyways though.

It has been known since the early days of Dalingrin's overclocking kernels that many of the NC's have issues with anything above 1100 MHz and undervolting can create a great deal of instability.
My recommendations are to try 1100 MHz max... and lower voltage .05 mV at each step. I personally never have issues with these settings...
You can then try lowering voltage .05 mV at a time until you start having issues... then increase it back to the last one you had no issues with.
I just leave mine at 1100 and .05 mV lower than the reported "Stock Voltage"