[Q] Android won't wake up - HD2 Android Q&A, Help & Troubleshooting and Genera

Hey all,
I hope I am asking this in the right place, and that no one else has asked this question. When I boot into Android and I leave it off for a while (in standby), then sometimes either the phone or the screen will not come back on. Sometimes the keys light up and the screen gets power (I can tell the screen is illuminated, but it is still completely black), and other times nothing comes on at all, forcing me to reset the phone to boot into Android again. My phone is running mdeejay's rEVOlution version 2.3, and the installation is fresh. I am not sure if the problem exsists for other Android versions, but I am really liking the current installation; I don't want to change it unless I have to. What could be the issue?

Related

[Q] Help Needed =(

Hey Xda,
For some minutes now my phone is acting real crazy.
If i turn it on (out of standby) it normaly goes to the Slide Lock Screen.
It Does but after a few seconds (even without sliding) it goes off into Standby mode again.
If i slide i doesnt goto the Sense home Screen it just stay there and goes into Standby.
I tried re-installing the device, i did and the phone works for a limited amount of time and then it happens again.
I have a CleanEX UDT HyperROM v15.0
Hope i can get this fixed =(
Oyeah this is the first time something like that happend to me.
The phone is not even a year old,
Thnx all.
Have you just installed the custom ROM? If it keeps happening regularly even after soft-resetting, there are probably conflicts between your ROM and certain other programs. You might want to choose another ROM or go back to your previous one.

[Q] Android Completely shutting off?

I used to have a problem with the SOD until i changed to my current radio. My current problem is whenever i start up a fresh build of android, it always freezes during the set up screen. After i restart and boot up android again, its works like new for a couple of hours and then completely shuts off. I dont think its like the SOD, when i try to turn the screen on nothing, not even the buttons light up. After another reset, all my widgets and apps i have on the home screen are reset. Anyone know whats going on here? I am running Energy ROM and shubcraft 1.5 but it seems to do the same thing regardless of android build. Also i should mention this is after i formated my sd card.

[Q] I need help with my android foya based htc hd2

im pretty new in this i uploaded the android, and energy rom, in the phone. after 10 mins of non use the screen goes blank and will not come back on unless you remove the battery. when the screen goes blank you can press the command buttons at the bottom and the backlight comes on but no visual image on the screen. has anyone encountered this issue and if so is there a fix for this. please help im willing to donate to fix for the issue.
I have a HD2 with froyo on it as well. The darkstone build. It has this issue some times, but it doesnt completely crash. If I turn the screen off, wait 5 seconds and turn the screen on, it comes up.
It actually does it quite regularly.
Did you turn off automatic backlights on WM settings before booting android, also make sure the keypad lights are on when u run haret.... that will probably solve the problem .
Sent from my HTC HD2 using XDA App

[Q] Serious Touchscreen Lag Issue [UPDATED]

First of all, sorry if this thread is out of place, but I'm not sure where else to turn.
My HD2 worked terrifically with FroyoStone 3.2, Hastarin 7.6 up until last Wednesday (5 days) ago. Then I started to experience, and have not been able to fix, serious TS lag issues.
Symptoms: I hit the unlock button, swipe to unlock, and the touchscreen will be responsive if I KEEP using it...if I pause for up to 3 seconds, the screen is no longer responsive. I have to relock the phone, unlock, and then swipe again to get it to work.
The touchscreen works perfectly fine in Windows Mobile 6.5. (Energy 2361X)
Attempts to fix: I've formatted the SD Card inbetween trying all of the following items-
1) Switch to MDJ ROM with MDJ kernel
2) Switch to Bluetopia ROM (0.5, 0.6 & 0.6.1) with Hastarin 8.0 OR 8.1
3) Switch back to FroyoStone 3.2 with kernel that comes with it
4) Update Radio ROM
5) Update to new Energy WinMo ROM -- after running Task 29 first.
Today, I purchased a new SD Card, loaded it with a clean install of Android, still have issues.
Also tried:
1) Turning off all LED notifications
2) Disabling Auto brightness in WinMo and Android
3) Disabled Screen Auto-Rotate
Honestly, I'm all out of ideas, and I hope someone in the community has a way to help out. I find it so odd that the touchscreen works great right after a "wake-up" as long as I keep it constantly stimulated...then fails to respond if I let it sit for more than three seconds. Is this a polling issue?
All ideas are appreciated. Thank you
UPDATE:
Followed another thread that suggests using the exact same WinMo ROM as the Builder -- matched my ROM with cmylxgo's WinMo ROM (author of Bluetopia) after another Task 29...no fix.
More Information
UPDATE 2:
Also tried 32K clusters and 64K clusters when formatting the card. Problem exists with either size.
There are G-Scripts to disable the G-Sensor and then re-enable it without rebooting.
If you want to jump to the extreme and want to remove all the sensors entirely.
Code:
su
rm -rf /system/lib/hw/*.sensors.so
Terminal
Thanks for your quick reply.
Unfortunately, I'm not the best with working with Linux/Terminal commands -- I tried typing in your code, and it returned that there was no such file/folder as -rf, and then I removed that section, and it said that it could not find the system/...
So obviously, there's something I'm missing, or an error in the syntax, that I cannot debug.
Any help is appreciated.
Are you having any data freezes or are you on an area with poor to no signal? I get really bad system lag when I loose signal while my phone is trying to download. Ppp will freeze and the phone will be unresponsive till reboot. Only way I avoid this is to turn off data if I got into a building I know I will loose connection in.
Sent from my HTC HD2 using XDA App
Updates
Thank you for your reply --
I checked into the disconnects being an issue by enabling Airplane Mode and seeing if I still had the same results, and unfortunately I do. I tried by disabling the Wifi and Mobile network separately, and still same issues.
But, here's an update on the issues:
Installed TYTUNG's NexusHD2-FRG83 V1.6, and this thing is very, very lightweight. Great battery life, great data (went to sleep, woke up, and not only was my phone still on...but I didn't have to reset data to check email...nice). The issues still remain. These are the newest things I've tried:
1) Remove Boxwave screen protector
2) Run from Airplane Mode.
I did however notice something really, really important: when the screen freezes, if I simulate a multi-touch gesture (pinch to zoom, etc), sometimes it wakes up! This is not a guaranteed thing (like 60%), but definitely something to work with.
Also, I noticed that one time that the touchscreen stopped responding, I tried the multitouch, no help...but I stayed on it. Multitouch tapped like crazy for a solid 6 seconds...then tried to shut the screen off -- and that button didn't respond. It was as if I saturated some bus of some sort that it had to clear out before it could finally shut the screen off.
Finally, I've noticed that the screen just needs to shut off for the touchscreen to unfreeze -- not go into a full lock situation. So, if the screen goes black, and I hit the lock key immediately, it'll unfreeze the TS.
Thanks to everyone who is trying to think of an idea!
i seem to be having the same issues as you right after i wake the phone up to unlock it. locking the phone is a habit for me to try and save as much battery as possible and also to not press any buttons while in my pocket.
im running a cyanogen rom and i changed the setting to allow me to unlock the phone by pressing the center windows key. i noticed that when the phone will not allow me to unlock it i can press the menu key and unlock it but i cannot use the touchscreen at all until i relock and unlock.
sometimes i have to do this a few times before the touchscreen comes back. i was thinking it could be my sd card but this started to happen today. i have been using android on my hd2 daily for the past 12 days without any problems. its weird that it started all of a sudden.
so it seems we still dont have a fix for the touchscreen freeze yet, right ?
Same problem here
Hi, I am experiencing the same problem.
Tried few versions of Android, The same problem repeated itself.
So I had to return to WM6.5 - there it works good. Only I have to reset the phone twice a day :-(
Hope someone will find brilliant solution for the sad problem that prevents using Android...

[Q] Screen Black / Auto Powered Off Frozen?

I seem to have the most bizarre issue that started happening last night. Ive been running XNote v3 and AEL kernel fine for a long time now.
Whenever my screen turns off (when i hit the power button or the timer runs out to turn screen off) The phone will after x minutes, either auto reboot or turn off (without shutdown animation)
It then remains off black screen and you do not know this unless you try use it again as you cannot power it back on at all, no sound and the phone is off as if you call you get voicemail.
Anyone any ideas what it might be?
I cant work out if it is software/ hardware related as nothing has changed software config wise and i have not done any updates.
I was thinking of maybe going to a stock kernel and see how that lives.
Its very easy to replicate and the only way to bring the phone back to life is to take the battery out.
If i am using the phone its perfectly fine, no reboots, freezes etc. Its only when screen is off.
OK since no one replied back but a lot of people viewed i thought i would provide an update.
Since factory resetting it
changing battery
wireless charging
removing sim
removing SD card
changing rom
changing kernel
changing back to stock
remove root
boot loader etc
all failed! a new replacement motherboard fixed the problem. i am unsure what caused the fault as it was working perfectly for over a month.

Categories

Resources