Develop Bugs

HELP! Phone doesn't wake up

My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!

rossle12 said:
My phone goes to sleep
and does NOT wake up, the bottom row of buttons and keyboard both light up if I open them or press them.
Help please!
Click to expand...
Click to collapse
Stock ROM or custom? Any overclocking?
The phone powers up if you soft reset, correct?

Well, I found out it was a small problem with the rom.
It was a custom rom, and I just installed a different one and it works flawlessly.
With the other one, the light sensor did not work either.
Also, I dropped my phone the other day, and a really small spring fell out.
And the back plain on my screen is loose and opens up easily..

Which ROM?

I hate to hijack this thread but i am having the exact same problem. Basically when i put my phone to sleep its hit or mess as to if it will wake. It seems to have started when i flashed Energy ROM. It was terrible after that, so I switched back to the stock ROM available from the HTC website and all seemed well at first. Now its back to hit or miss.
I cant really rule out a hardware issue such as a broken sensor or something because I'm not sure how the mechanics of it work. When i push the power button on top the phone wakes but not the screen I know this because the 4 lights on the bottom light up and the keyboard as well. I can hit the button repeatedly but it doesnt help. At other times it works flawlessly, but usually does not.
Can anyone give me a suggestion as to what it could be, or a way to rule out a hardware issue?

Exactly my problem!
It was perfectly fine for the first day or so before it started crapping out again..
Can someone please help us with this problem?
It's mind consuming and it's making me worry.
Until TP3 is out, I won't get a new phone ):

Well, the problem is discussed in great detail on the internet, but no one can give a definitive answer. ..
I've been a touch pro 2 user for exactly 3 days... My new HD2 from T-Mobile is in the mail... This is a un acceptable flaw with no real solutiion... Good Luck TP2 users....

Good luck to you.
I've had mine for over two years and it was flawless
Just one recent drop determined everything
Although I Must say, it was one hell of a durable phone

Yea, dont get me wrong. I really like the phone. Thats why I'm getting the HD2. Great OS and big beautiful screen. I'm gonna miss the slide out keyboard but I think thats what breaks these phones.
I'm excited that there's the possibility of running Windows Mobile 7 on it.

rossle12 said:
Can someone please help us with this problem?
Click to expand...
Click to collapse
I'd like to try to help. But you never answered my question of what ROM you are on (and which one you tried previously).

I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now

djowen6565 said:
I've determined my problem is 100% hardware related. If I open my keyboard and then grab the screen and tweak it while pressing the power button it comes onn 100% of the time. Sux, but at least I know the cause now
Click to expand...
Click to collapse
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.

HELP: Same problem Phone not waking up
Hi saw this thread and was wondering if anyone can help me.
I have an HTC Touch Pro 2 for some month now...
Using the following details:
OS Version: 5.2.21887 (21887.5.0.86)
ROM Version: 2.07..401.1 (80303) WWE
ROM date: 02/04/10
Radio ver: 4.49.25.91
stock ROM basically...
THe issue is that the phone doesn't wake or when using it just freezes/hangs.
Not much software/apps installed... and memory is good as well.
I just don't know what's going on...
Help please.
Thanks

rossle12 said:
Every once in a while my phone would turn on and I wouldn't know why
But yeah, I think it is hardware related.
I previously used Energy then went to Jacko's.
Both were perfectly fine, just the upsetting sleep function and light sensor would keep the phone off.
Click to expand...
Click to collapse
I'd agree with the notion that its likely hardware related. I've flashed maybe 10 different builds of Energy over the last 7 months or so, and never once had and issue with the SOD (sleep of death) that I can recall. A bad flash can sometimes happen. But since you flashed another reputable ROM (Jackos), that somewhat eliminates the possibility that a bad flash is the culprit.
You can start from scratch, by running Task29 to format the ROM area of the phone's memory, and reflash the ROM. But this would be just to eliminate the possibility of a bad ROM flash. My gut says that you won't see any different results.
Running the phone "clean" for a while (to see if you still have the SOD) without any software installed or any other modifications will eliminate the possibility that any software or mods are responsible for the issue.

are you sure its hardware related? because my phone started doing this yesterday too...I had an energy rom from october, and it was really buggy. I am only able to keep my phone from sleeping when it is plugged in to some power, so i flashed the newest energy rom and still having the same problem...wont wake up from sleep
EDIT:
I dont see how this can be hardware related because everytime i soft-reset, the screen works again. this problem only happens when the device goes to sleep...

Any overclocking?
As I already mentioned, I never had any SODs on Energy that I can recall, except when using OCT (OverClocking Tool).

I have done no overclocking...I just flashed the newest energy rom like 15min ago...is there anything else I can do or check? it looks like the phone works still, just no backlight...

After flashing the ROM, maybe try running it "clean" for a day or two, don't install any software or do any mods, reg edits, etc. If you still have problems with the phone waking up with a new ROM, and no other software or other mods, than it may indicate a hardware problem.
And be sure to run Task29 before you flash the new ROM, if you don't already do that.

You guys should read the following thread:
http://forum.xda-developers.com/showthread.php?t=648134
You're not the only ones (by any means) with the SOD issue. But it isn't at all clear what causes the issue. Lots of different theories in that thread about various software or ROMs, with no clear solution.
Lots of conflicting info, but some comments on the thread suggest (as I mentioned) that Task29 may help (certainly can't hurt).
moto2000 said:
are you sure its hardware related?
Click to expand...
Click to collapse
Nope, definitely not sure, especially after reading the thread linked above. But as I suggested before, Task 29, try a different ROM, and run it clean with no software or mods, and start eliminating the variables.

[Q] reboot random

Hello,
I had random reboot before with my leedroid 2.3b, and I had one also 30 minutes ago with AuraxTSense, so I'm asking if the cause is the rom or not.
When he reboot, he's not hot, I see it reboot sometimes and the phone was at normal temperature (approximately with my hands lol). it reboots max 1 time per day.
So I'm tellng myself that's it could be due to:
- radio
- S-OFF
- one app
For radio, I try tu update from 32.48.00.32U_5.11.05.14 to 32.47.00.32U_5.10.05.23, and I'll see.
For apps, the problem is that I would have not to restore all my apps, to see if one app cause it.
What do you think of it?
Thanks

My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore

Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
Or as fnotsje said, could be hardware related

fnotsje said:
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Click to expand...
Click to collapse
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
eden2812 said:
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
It's installed but not configured in smatass mode, you advise me to uninstall it and to test?
Or as fnotsje said, could be hardware related
Click to expand...
Click to collapse
What is surprising, that if it's that, i t should reboot many more times than one time per day no?
Thanks

thierry_b said:
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
Click to expand...
Click to collapse
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..

fnotsje said:
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
Click to expand...
Click to collapse
Yes and always only one time per day, just one time maybe 2.
I desinstalled SetCPU, it changes nothing.
What do you advise me to do?
Wipe and install minimum apps, and see if I've that, and little by lttile, reinstall one new app...test few days again...?, it will be long :-(
Thanks.

Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.

GoogleJelly said:
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
Click to expand...
Click to collapse
With the minimum of apps, for example to see if it reboot or not?
Because if t's an hardware problem due to the radio, it censed to reboot even with few apps no?
For carrier as I'm at Orange like you, I think, they could change fastly my phone maybe. I will try that if anything works. You think that if I do that, I've to find an orange rom? I'm asking myself if they accept an HTC even restored with RUU.
Thanks

I have the same issue and ITS DRIVING ME MAD!!!!!!!!!!!!
I never experienced this with my stock ROM... so I firstly tried a gingerbread ROM... when it started... i then moved to a Sense Rom and still reboots occured... I'm now on my 2nd cooked sense ROM and still having reboots!!
WTF? is there a quick sollution?
thank you!

SO MANY follks seem to be having problems with [email protected]! Is there seriously no sollution to this or a common cause..?

had the same problem & is with HTC getting fixed
there are a few posts about it if you search - the only fix seems to be to send it to HTC for a new motherboard as some presume that it's overheating.

11 march still waiting on return of my Desire

I can relate to your issues. Mine kept rebooting when I tried to use the GPS. Like you I had mine rooted, S-off and was using a custom ROM.
After many tests, I downloaded a stock RUU, installed a different navigation app and once again, it rebooted.
Bottom Line: take it back. Its probably defective. Just make sure you're running a stock ROM. Download an RUU.

Blank screen on my Desire on pretty much any 2.3 ROM

After originally sending Tillus a PM as he had a similar issue with another ROM I thought I had better post here.
I have tried Oxygen, CM7 and Redux but I get this problem with all of them. Everything runs fine for a few days and then I go to unlock my phone and the screen stays blank. The keys light up but the screen stays just blank. Tried Back-Trackball-Vol down (as suggested in post linked to in PM below) but it didn't work. I then have to take out the battery and restart.
Once it starts happening the gaps between it happening get smaller and smaller. It has happened 4 or 5 times today alone.
First time, on Oxygen, my phone eventually wouldn't turn on any more and I had to get HTC to fix it under warranty.
Then I tried Redux where it happened after a few days. Someone on here suggested I look at the CPU settings. I did and saw that Redux had a power save mode, so I tried that and it seemed to work but after a few more days the same thing happened. Although this was after a reboot so perhaps the phone didn't retain power save mode afterwards.
On Sunday I loaded CM7. Worked for about 24 hours before the blank screens started.
Running ONDEMAND governor, Min 245 Mhz, Max 998 Mhz.
Any ideas?
Here is the PM I sent to Tillus for info:
Tillus said:
d10brp said:
Tillus,
Hope you don't mind me sending you a PM. I noticed you had the same issue as me (screen not turning on from lock screen http://forum.xda-developers.com/showthread.php?p=9652281#post9652281). Did you ever find a permanent solution? I'm getting this issue with Oxygen, Redux and CM7.
Thanks
Alan
Click to expand...
Click to collapse
Hi,
uhm, I think this was a specific Auraxtsense issue which was resolved eventually. I never experienced this fault again - neither in a later auraxtsense version nor in oxygen (2.0.3) which I am using now.
Are you overclocking your cpu? Maybe you set the screen-off frequency too low? Or are you using a undervolt-kernel with very low settings, especially in low cpu frequencies?
As I said, I haven't experienced this issue for a while now.
Click to expand...
Click to collapse

Did you try keeping the power button pressed for a few seconds? I know, it sounds silly
Are you sure you don't have this problem on a 2.2 rom? I don't see you mentioning it in your post. Only that you have this issue with 2.3 roms.
What kernel do you use? Try a SVS kernel, don't use a HAVS kernels for now.
Also are you sure you tried the latest version for let's say Oxygen? From the oxygen changelog:
v2.0.3
Fixed font bug introduced in previous version
Fixed pmem exhaustion *
* The pmem exhaustion was causing the so called 'black screens'
at random intervals
Click to expand...
Click to collapse

I'm fairly new to this so I have only tried 2.3 ROMs since rooting. Obviously phone has been running official sense just fine on both 2.1 and 2.2 for about a year.
Also, apologies for this, but I don't know what the kernal is. Just followed the noob video tutorial. Is it Alpharev?
Haven't tried Oxygen since RC7 so I might try it out.
Seems to be memory related as just after I posted, something slightly different happened, I pressed the lock button and the lock screen appeared but then froze. After a couple of minutes the screen eventually locked again with a very slow jerky animation. So I have just removed a couple of apps that seem to be running all of the time, App protector pro and StumbleUpon. No crashes since then (2 hours).
Sent from my HTC Desire using XDA App

So that worked for about 2 days. Now thinking maybe it is the SD card. Ordered a new one.

[Q] Defy grinds to a halt

Really hoping someone can help me. I have had my Defy for a few months and have always been on a custom SBF but continue to experience problems with the Defy working amazingly for hours and then sometimes I turn the screen on and the Defy is working in some kind of super slow mode and opening anything takes ages, everything does eventually open so it’s not crashed but just going super slow!
I am currently on SBF 3.4.2-177 Nordic but have had the same problem on different SBF’s so either my phone has a hardware issue or its some software I have on my phone, I am currently on Beta 6 of CM7 and have had this issue on other betas of CM7 but have never heard of anyone else with this issue. The phone will sometimes go a whole day without the issue also which is weird. It is not overclocked either. When it goes into what I now call superslow mode I have checked to see what the processor and memory usage are and both are around 60% used not being topped out at all. I have even used StabiltyTest to test the memory and CPU when the problem is occurring and both run through fine.
I really would love to know if anyone else had a similar problem or if they know what is causing it or how I can find out what is causing it without removing every bit of software I use. The only piece of software I use regularly that runs in the background is Juicedefender so I am going to remove this now and see what happens over a few days.
Any help would be amazing
Many Thanks
Bob

Did you install the latest patch for the auto-brightness issue? or Did you turn off the auto-brightness?

Thanks for the fast reply I have already installed the latest patch for auto-brightness issue but still have the problem

Was the phone slow in the stock ROM? I mean that's really wired that the problem appears on each SBF

Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers

I have this same problem. Only fix seems to be a reboot whenever it happens

bobdigby said:
Hi mys_721x, I only had the stock ROM for a matter of days when I first had the phone so really cant remember but I am thinking I may have to go back to see if I do still have problems if no one else can suggest anything else. Cheers
Click to expand...
Click to collapse
Same here, my phone suddenly becomes sluggish and unusable. Yesterday it was stuck on 100% cpu usage, I entered the task manager to see what was wrong and there wasn't any application that was using the cpu.
Only solution is to reboot everyday.

Glad to see I am not the only one, yea a reboot does the job sometimes it can be twice a day sometimes I don't see it for a few days, do you guys have juice defender installed by any chance as thats the only real program which stays running in my background which is extra to the roms I have used, cheers for your input, lets hope we can figure out whats going on.
Bob
Sent from my MB525 using XDA Premium App

I had it to in the past. When i tried to lock the phone it took long time and it wouldn't unlock for a wile 1-2min what is verry long if your waiting and afterwards scrolling was lame.
Don't know what I did, but it's gone now. Now only when out of memory(dhuu!)
I think I wiped it cleen, went to a 2.2 and didn't have it again, now on CM.
Do you see in spare parts any apps using mutch cpu?

Weirdest thing that happens to me..
Every hour/day the phone loads up some applications prepared to start when I turn on the phone..
That means that if I close say, tigertext or Skype, the following day, without turning off the phone, hey are running again.. wtf?
EDIT: A way of checking what's using the CPU, if you're on Froyo, is check the application manager to check for services CPU usage

Yea I have no idea what is causing it but little to no cpu usage when it happens, when I lock on cm7 the tv effect for screen off is super slow motion its really strange, did a clean wipe yesterday and did its first slow down today just before post, cheers
Sent from my MB525 using XDA Premium App

Anyone have any luck with this? Mine just seems to be getting worse and worse on CM7.
Update: I've opened a issue for this on Github. You can go there to post new information / symptoms so that hopefully it can be fixed: https://github.com/Quarx2k/android_device_motorola_umts_jordan/issues/204

Hi dasbin,
Since uninstalling Juicedefender from my phone I have not had this issue once, it has now been 3 days which is probably a record for me so I would say that it was causing me the issue, do you have juicedefender installed? I am now using green power it is much better so far.
Cheers

Strange Force Closes/Lag/Unresponsiveness

I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?

TheManCalledX said:
I'm pretty new to the root scene in general, only since about September when I got sick of not getting the GB update to my phone.
When I first started flashing roms, I started out with Nil's Business Gingersense 2.1/3.0 hybrid, and basically kept sticking to Nils roms from then on. I used a couple different Sense roms, but always came back to Nils with a gingertiny kernel.
A couple weeks ago, I decided to go with a CM just to get a taste of AOSP without Sense. I was using an incredikernel with it, and never seemed to have any problems.
Because I was a fan of the Sense 3.0 lockscreen, I was using MagicLocker on CM, and noticed it was somewhat of a battery hog. I was actually getting better battery life on sense roms with tiny over aosp with incredikernel.
I decided to switch back to Nils 3.0 ROM that I loved and used numerous times. It worked fine upon first flash. I let google restore download my apps *none from my time on CM autorestored?* and after it was all finished, I went back to Tinys 10/23 kernel. Upon flashing, it immediately started force closing everything, and it got to the point where my touchscreen was completely unresponsive, I couldn't even get the screen to turn on/off with the power button. I had to battery pull.
I eventually got the Nils 3.0 rom settled down with a Tiny 10/15 kernel, though only after using the v6 SuperCharger script in Multitasking mode.
I'm once again running into my power button no turning ont he screen, hitting an app and waiting for 3 minutes for it to force close before I can open it again.
What is going on here? I always factory wipe, clear cache, boot/system/davlik at least 3 times. And then battery stats at the end.
I've never had my phone become completely unresponsive when using the same ROM/kernel in the past. Any ideas?
Click to expand...
Click to collapse
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.

That's the min for gingertiny right? If so, then yes. But I've literally never run into this problem since going from CM back to Sense. Never once had it happen during all my different Sense ROM flashes. Could it be something to do with the way CM does it's storage tree vs sense? I'm at a loss right now and just want some ideas on what to look into.

Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?

TheManCalledX said:
Just randomly got a notification upon reboot that says Package File is Invalid with the standard Triangle with the Exclamation Point in it. First time I've ever seen this error/notification. Is my Inc on the verge of death?
Click to expand...
Click to collapse
Flash amon ra recovery from rommanager. Then go into the recovery and select other anf fix apk uid mismatches, and fix permissions. You can flash back to clockwork when your done. I would also raise your min freq to 245000, and try that for awile.

Okay, I flashed a Nandroid backup from the very first day I rooted my phone. Then a couple others from other sense ROMs I have run. Every once in a while I'm still dealing with a little lag loading something, and I'm trying to let things settle in for a couple days before I flash a new kernel.
But, a friend at work also has an Inc, and after going from Sense to CM back to Sense, he's experienced similar problems. So I have a vague idea of what the problem is, but literally no idea how to fix it.

cmlusco said:
Are you using 128 as your min frequency by any chance? When i use 128 as my min frequencie my phone sometimes becomes unresponsive for seconds at a time, will hotboot it self, or just totally shut down and will require a battery pull to power on again. I ditched thr 128 and havent had the issue since.
Click to expand...
Click to collapse
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
Sent from my ADR6300 using Tapatalk

tiny4579 said:
You think its the 128 min causing the freeze issue? I don't have the issue on cm with incredikernel. So it must be something with the GB kernel but i'm not sure what yet and don't want to release a new one until that's fixed.
EDIT: I thought i would also mention that this happens on all governers except performance, not just on sa or sa2.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.

cmlusco said:
I believe it is. I have tried a couple of times to use 128 as the min, and every time i have issues with it. Usually a random long freeze followed by an automatic hotboot, or just a freeze that requires a battery pull. I have tried raising and lowereing the voltages for 128 with the same results. It usually happens when using system intensive apps like games, google earth, or watching videos on the net. When i go back to 245 i get no issues at all, no freezing and no reboots.
EDIT: I also thought i should mention that this happens with every governor except performance, not just in sa and sa2.
Click to expand...
Click to collapse
I never had the problem using 128 before I switched to CM and back to Sense.

TheManCalledX said:
I never had the problem using 128 before I switched to CM and back to Sense.
Click to expand...
Click to collapse
Well i have never used CM, i have always used sense roms.

Try smartass governor (not smartass v2) and see if it helps. I don't know about reboots but there is no wake lag or virtually none.
Sent from my ADR6300 using Tapatalk

Ok, I posted a test release in the kernel thread. Please test it if you're having lag issues.

to themancalledx
I had the exact same problem going from aosp to sense. For me it was a pretty simple fix. I hope it works for you. Go into recovery select advanced and then fix permissions. Good luck.

New kernel released. Try that one.
Sent from my ADR6300 using Tapatalk