I bought my Blade 4 months ago and i have been noticing for the past few weeks that the touch sometimes has become less responsive, and only gets fixed until i reboot the device.
I noticed this behavior with SS RLS5, FLB, CM7 stable and a few nightlys. With CM7 sometimes it got worst being almost impossible to unlock the device, my finger goes to the right and the sliding tab goes to the left. And i have to press really hard until the touch responds. After i reboot it all runs normally for a while.
I am running gen2 (since almost i noticed this situation, maybe it has something to do with it...) and i always wipe everything when installing new roms.
Is this hardware failure?
Thanks.
I think when bugs like this happen after flashing a custom ROM a hard reset will fix them.
I think hard resetting after installing a new ROM is always good practice. Fixed my Galaxy Europa up when I upgraded it to 2.2
I don't think it's your ROM because I have the stock Orange ROM and have the same issues. The screen will become entirely unresponsive to touch and only a restart will fix it. Does anyone else have this problem?
How strange, I've had my phone for a while now and this has yet to happen. Too many apps running?
Modaco is probably a more likely place to find the answers you're after.
Related
So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?
Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
helloworld1 said:
Anyone using CyanogenMod or Desire Rom encounter the random touch misalign problem that has flooded the google's forum http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en
Click to expand...
Click to collapse
happens occasionally, but now rarely (almost never) with the latest cyanogenMod (5.0.3.1) - turn off the screen and turn on fixes it.
i think it will be eradicated completely with the next offical (and cm update)
yes, it is better for me too with CyanogenMod 5.03.01, I feel it is more due to the new .32 kernel
Now that you mention it--yeah, the problem has all but disappeared ever since I flashed CM and now Modaco's Desire. I think I encountered it a grand total of once in two-three days, though admittedly I still haven't spent enough time with the Desire ROM.
I wonder whether the touch screen driver in CM is the same as the one in the official ROM>
No problems at all with Desire image and rarely using latest cyan. It was making my stock unusable.
Ha, id totally forgot about that issue, I havent experienced it at all since switching to Cyan, atleast not that I can remember
I noticed that the alignment/calibration problem has been improved. not perfect...but improved.
I've been actively trying to palm-wrap and tilt the screen at an angle that usually gave me calibration problems on stock. Nothing; touch alignment etc remains perfect. I guess it was a software and not hardware issue after all!
So the CM does not eliminate the problem. I hope google will fix the driver in the source code, or the problem will not be gone.
i have a question, does it fix the 3g dropping/switching to edge problem?
I still have it on cyanogen 5.0.3. Actually quite often and this really annoys me, I did a wipe install.
So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?
CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.
I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.
I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.
So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.
perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.
Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).
i'm running on a darkside prefinal rom for about a month.
suddenly the soft stopped responding(don't work at all), and the screen sometimes think i'm touching it when the phone lays on the table far from me.
i think i should mention that before the darkside i had a gingerbread at&t stock rom and after that a cm7 nightly rom.
i read on the internet and even in this forum that i need to run a pds fix.
i tried that it fixed the phone for about day or two and then everything went wrong again.
i returned to the store where i bought the phone. they burned me a at&t original stock rom. that fixed the problem for two hours at most.
i wanted to know if someone knows how to fix it or did anyone encounter this problem.
thanks
Nir
Looking for some help and insight. Have an Acer A500 that haven't had any issues with until recently. Was running stock ICS and one day the screen was unresponsive. Can't unlock it, or if it is unlocked can't touch on any icons, etc. Far as I can tell it is almost like being at 100 percent CPU utilization. After a while, the responsiveness will come back for a while anywheres from a few seconds to 10 minutes.
I have started with a soft reset, hard reset, using APX to reload Android and still same issue. Don't act like a physical touch screen problem because it does work hit or miss.
Do have kids in the house and the tablet has been dropped and knocked around a bit.
Really not wanting to throw away a $500 tablet that I bought 18 months ago...
So any ideas would be greatly appriciated on how to fix this problem!
SOD issues
I've been using FLEXREAPER-RF1-EXTREME revision2 since it came out and it has been rock solid but when I try to update to RE-FLEX or CM10-FLEX I get a SOD almost instantly. I couldn't do a REAL format on TWRP 2.1.3 like civato suggested in his forum so I flashed Thor 1.7.3 and formatted /data, reinstalled and I still get a SOD almost every time the screen turns off. If I reinstall flexreaper-rf1 the SOD issue is gone. I tried sleeping without a SD card installed but that didn't help and I'm running out of ideas. If anyone has any ideas please let me know. Thanks to everyone that works on these custom roms because they are a thousand times better than the stock ones.
Hi i had the same problem with mine but after rooting and custom rom my acer is better than ever.
Sent from my A500 using xda app-developers app
weidnerj said:
Looking for some help and insight. Have an Acer A500 that haven't had any issues with until recently. Was running stock ICS and one day the screen was unresponsive. Can't unlock it, or if it is unlocked can't touch on any icons, etc. Far as I can tell it is almost like being at 100 percent CPU utilization. After a while, the responsiveness will come back for a while anywheres from a few seconds to 10 minutes.
I have started with a soft reset, hard reset, using APX to reload Android and still same issue. Don't act like a physical touch screen problem because it does work hit or miss.
Do have kids in the house and the tablet has been dropped and knocked around a bit.
Really not wanting to throw away a $500 tablet that I bought 18 months ago...
So any ideas would be greatly appriciated on how to fix this problem!
Click to expand...
Click to collapse
Same problem here, stock ICS as well. When the screen becomes unresponsive I have to use a mouse to be able to utilize the tablet, not sure if it's hardware or software problem...
Answer (for me at least)
Found that it seems to be a grounding issue. If when the screen locks up, I hold the tablets by the stainless steel edge then the screen responses. Not sure if that will help others that have had the screen that becomes unresponsive - but interested to see if others notice this too.