New problem

ronaldheld · #1 (**permalink**) 05-19-2010, 08:25 PM

Starting last Monday, I noticed this. Phone was booted and a hour later did not turn on the screen with the power button or slider. Pulled the battery and rebooted all was well. It just happened again, with the same recovery procedure. Any ideas as to what is going on and a more permanent solution?

**blazingwolf** · #2 (**permalink**) 05-19-2010, 08:33 PM

More info from you is necessary for any good help. What ROM are you using? Did you install a program recently that might be the culprit? Have any error messages been showing?

ronaldheld · #3 (**permalink**) 05-19-2010, 08:58 PM

Droidmod 1.0. The only app I recently installed was a linpack for Android, which I will uninstall soon. There was a new version of SetCPU And the ATK.

**blazingwolf** · #4 (**permalink**) 05-19-2010, 09:47 PM

Well, we know that Droidmod is pretty stable so I wouldn't think that would be the problem. ATK can be the problem if it is just closing all apps. So I would look there first. It's also possible that Linpack could be the issue so I would see if it happens again after you install that.

ronaldheld · #5 (**permalink**) 05-20-2010, 07:09 AM

Linpack is gone, so I will see if it is the cause. I would guess it might be SetCPU before ATK, although why it seems to shut down due to either is a mystery. Is there a system shutdown mechanism if the temperature gets too high?

IwireRobert · #6 (**permalink**) 05-20-2010, 10:31 AM

Mine will do some random reboots when im over clocked to much. I would see if you took it down a notch and see if the problem is still there.

tvandyck7 · #7 (**permalink**) 05-20-2010, 11:24 AM

Mine has done this once or twice on me. I chalked it up to a random occurance with DroidMod 1.0. The phone will sleep and not wake but the status light still blinks. A battery pull is the only way to reset it. I don't think a particular app is causing it. I also do not have linpack.
As far as SetCPU goes, it could be the culprit. If I remember correctly, I had the custom profile for sleep/standby set at the lowest value when this happened to me. If it's not DroidMod, I'd say SetCPU could be doing it.

ronaldheld · #8 (**permalink**) 05-20-2010, 11:27 AM

It may be random. I have been overclocking at 1.0 Ghz for months, without this problem occuring. if it is Droidmod 1.0, has anyone else using this ROM seem this occur?