Related
Hi,
I just received my Touch Cruise yesterday and I've found it takes quite a while to wake from standby when I push the power button, is anyone else experiencing the same problem? Does anyone have a fix for it?
Thanks
I don't have the same problem. My guess: backup your data and hard reset your device.
Sorry if this just makes you feel worse but it is a datapoint. For what it's worth, my device wakes up pretty much instantly from standby so I'm afraid it sounds as if it's a problem somewhere in your device or setup.
How many 3rd party applications and/or today plugins do you have installed? I wonder if one of them is trying to do some processing on wakeup and has a bug that is slowing things down.
If noone comes up with a better idea then I'd suggest uninstalling your third party apps one at a time to see if one of them is causing the issue.
- Julian
Thanks for all the info. Strangely enough the problem only seemed to occur yesterday, waking it from standby this morning was fine. If it happens again I'll get rid of the 3rd party apps as suggested.
I've had a similar issue 2 times, where I cannot wake the device at all. Nothing happens, I have to soft reset. I hope it isn't ongoing---I never had similar issues with the Touch.
teride said:
I've had a similar issue 2 times, where I cannot wake the device at all. Nothing happens, I have to soft reset. I hope it isn't ongoing---I never had similar issues with the Touch.
Click to expand...
Click to collapse
I had the same issue as you, after standby the device would not turn on, and I had to soft reset it, it happen a couple of times, I'm not sure why, but I noticed last time it happenned that the battery was low, maybe that's what caused it to happen.
Is there anyone out there with the same issue? Is it a hardware issue or some software or 3rd party issue?
palmbluetooth said:
I had the same issue as you, after standby the device would not turn on, and I had to soft reset it, it happen a couple of times, I'm not sure why, but I noticed last time it happenned that the battery was low, maybe that's what caused it to happen.
Is there anyone out there with the same issue? Is it a hardware issue or some software or 3rd party issue?
Click to expand...
Click to collapse
The first time this happened to me the device had charged all night. In fact the green light was constant when I removed from the charger. Usually it starts to blink immediately after unplugging..I couldn't get it to wake. The 2nd time battery was also fully charged although it had been off the charger for a few hours.
Hello, it happenned to me few more times this past few days, I try to turn it on from standby and it just not wake up.
Did it happenned to anyone else? Does anyone knows if its a hardware problem?
The firs time it happenned to me I had no programs installed.
Hey everyone,
This is my second HTC Touch Pro 2 for Verizon Wireless and I returned the first one because the phone would shut off when I closed the slider. This happened once every few tries. I received my replacement phone last Thursday and just discovered the second phone does the same!
Has anyone experienced this issue with their Touch Pro 2? Open and close it a few times in a row and see if it shuts down. I'm two for two so far. I'm going to return the phone and get my money back and wait till Verizon releases the new HTC Imigio or the Samsung Omnia II.
Just curious to see if anyone else has witnessed this issue.
Dan
ive got the verizon tp2 and i dont have this problem...i just tried it to be double sure...sorry
Open and close the keyboard over and over and it turns off? Why would you do that anyway? My VZ TP2 doesn't do that.
I bet his finger is hitting the power button on top when he is closing the KB. I was doing that and it drove me nuts. There is a cab file that disables the button when the KB is open. Solved it for me.
nylaw said:
I bet his finger is hitting the power button on top when he is closing the KB. I was doing that and it drove me nuts. There is a cab file that disables the button when the KB is open. Solved it for me.
Click to expand...
Click to collapse
this, very common for people to bump it on accident
nylaw said:
I bet his finger is hitting the power button on top when he is closing the KB. I was doing that and it drove me nuts. There is a cab file that disables the button when the KB is open. Solved it for me.
Click to expand...
Click to collapse
power button? are you referring to the backlight ? on verizon the power button is the end key.
also, wheres this cab!! ?
thanks
Actually, it's definitely not the power button or the backlight button. I understand you would never shut and close the slider a few times in a row, but the reason I said that it to see if anyone else is seeing this problem. For example, I just replied to a text, sent it out and shut the keyboard and the phone shut off and started the boot screen instantly. I'm very surpirsed no one else is seeing this as this is my second phone. I want to stay with the Touch Pro 2, but I'm concerned the 30 day warranty from Verizon will pass and I'll be stuck with this issue.
http://www.youtube.com/watch?v=LKmDOkRJrfw
Check out the video. This is exactly my situation.
I thought there was a one year warranty? That's how it was with my ENV2.
Also, this doesn't happen with mine either.
Mine does not have this issue either, but I'd like the cab mentioned that prevents screen sleeping when kb is open. I'm hitting that button by accident when writing emails. It is mildly irritating having to be so careful. If a cab would prevent it , that'd be great.
Loose battery? It does get a little bump when it opens and closes, could it be the battery area is a bit bigger then it should be and the battery wiggles? See how flush it is.
Also in the video that's the sprint TP2, not verizon. Or is that not you and it happens on both?
I'll check the battery. It's an issue across all brands (Verizon, Sprint, etc.). Not just the Verizon version. The video is just an example of what's going on. I'm really surprised no one else has witnessed this problem. I love the phone and want to keep the Touch Pro 2, I just don't want a defective phone which I just paid $489 for. It should work perfectly.
Now that you mention the battery, I'm curious if the battery I received with the original phone is physically smaller in dimensions. The first phone had the issue along with the second phone. However, Verizon ships you a new phone without the battery since you're supposed to use your original. Now I'm really curious....
I have expierenced the same problem he is talking about. These phones are real sensitive to moisture. That's the cause I had the tech open it and blue dry it out and it started working again. Then it was raining and it left it in my hand and the mositure got back into the phone and the tech had to do it again. Then it got a little bit of moisture from the car wash I work at and I had to have the tech do it again.
l.waples said:
I have expierenced the same problem he is talking about. These phones are real sensitive to moisture. That's the cause I had the tech open it and blue dry it out and it started working again. Then it was raining and it left it in my hand and the mositure got back into the phone and the tech had to do it again. Then it got a little bit of moisture from the car wash I work at and I had to have the tech do it again.
Click to expand...
Click to collapse
So you got the phone wet working in a car wash and you are still hitting the backlight buton?
A wet phone is not a VZ problem, sorry son!
This has nothing to do with moisture from what I can see. I'm going to cntact tech support tonight. The only connection I can make between phone no. 1 and no. 2 are the batteries. Going to see if they can ship me a new battery instead. Not sure if that's possible. They currently only have replacement phones available and not new ones. So not sure if I can get just the battery.
I can guarantee you it's not because of moisture though.
Just contacted Verizon... they're shipping me a brand new battery for free. Going to test it to see if that solves the problem. Not sure if it will, but at least I'll have a second battery when I finally have a phone that's working!
I'll put my vote in for the link for the CAB to disable backlight button when keyboard is out....
please provide.
Just an update. I received my new battery and the phone seems to work fine. Some how the sliding feature of the phone would jiggle the battery and some how turn the phone of because of loss of power.
Interesting.... So I guess I never had two defective phones huh?
Hi
I upgraded with the official WM 6.5 rom from HTC yesterday,and the unit shuts down when I close the slider(and I do not touch the power button).I then went back to the original WM 6.1 and the problem was gone.I then assume this is a software issue? Anyone else with this experience?
Regards
Steinar
stvervaag said:
Hi
I upgraded with the official WM 6.5 rom from HTC yesterday,and the unit shuts down when I close the slider(and I do not touch the power button).I then went back to the original WM 6.1 and the problem was gone.I then assume this is a software issue? Anyone else with this experience?
Regards
Steinar
Click to expand...
Click to collapse
the official wm 6.5 for USA CDMA is out already?
I am on sprint and am having the same exact problem!!!
Lost touchscreen handling in upper and lower part of my screen!!!Pls Help!
I have a rooted device with xsba's custom rom (4.0.4). The problem started before this ROM. I am pretty sure that this is no rom issue. I have flashed the phone several times with numerus roms. Problem persists.
I already have changed touchscreen once because of a serius fall (broke) approximately 6 months ago.
These are all the facts. Before xsba's rom i used thiaiz o3d. (2.3.7). The problem started one day that i hadn't charged the phone up. When the battery fell under 5 % the phone went berserk. (Numerus button presses all the time)
I couldn't even reboot. When I finally turned it off by removing battery and restarted the phone the upper field of touchscreen of the phone never worked again.
Yesterday i failed to charge again.ASfter finally restarting the same issue appeared in the lower field of touchscreen. Please advice!!!!!!!!
Is there a way to solve this problem without changing the touchscreen?
dim2004 said:
Lost touchscreen handling in upper and lower part of my screen!!!Pls Help!
I have a rooted device with xsba's custom rom (4.0.4). The problem started before this ROM. I am pretty sure that this is no rom issue. I have flashed the phone several times with numerus roms. Problem persists.
I already have changed touchscreen once because of a serius fall (broke) approximately 6 months ago.
These are all the facts. Before xsba's rom i used thiaiz o3d. (2.3.7). The problem started one day that i hadn't charged the phone up. When the battery fell under 5 % the phone went berserk. (Numerus button presses all the time)
I couldn't even reboot. When I finally turned it off by removing battery and restarted the phone the upper field of touchscreen of the phone never worked again.
Yesterday i failed to charge again.ASfter finally restarting the same issue appeared in the lower field of touchscreen. Please advice!!!!!!!!
Is there a way to solve this problem without changing the touchscreen?
Click to expand...
Click to collapse
Now , you need to go to developer options in the settings and enable show touches option. Then you touch and slide to the parts that don't work . If you see the line going there , then it's a problem with your ROM. If it's not , then you possibly have a broken touchscreen. Check the contact of the touchscreen ribbon and see if it's tightly sitting on the slot , press it down and try again.
If it's not working , you have no choice but to replace the touchscreen. You can buy one off eBay for 19 dollars and free shipping. It's made in China but it works well without problems for the past 6 months with my device.
Hope I helped.
Cheers!
Sent from my LG-P920 using xda premium
boltthrower56 said:
Now , you need to go to developer options in the settings and enable show touches option. Then you touch and slide to the parts that don't work . If you see the line going there , then it's a problem with your ROM. If it's not , then you possibly have a broken touchscreen. Check the contact of the touchscreen ribbon and see if it's tightly sitting on the slot , press it down and try again.
If it's not working , you have no choice but to replace the touchscreen. You can buy one off eBay for 19 dollars and free shipping. It's made in China but it works well without problems for the past 6 months with my device.
Hope I helped.
Cheers!
Sent from my LG-P920 using xda premium
Click to expand...
Click to collapse
I have already checked the rom.the problem is not there.I have checked the contact of the ribbon yesterday and everything was fine.The touchscreen that i have is a chinese one.And it lasted for 6 months or so. So you might want to get ready for a new one as well!!!!!
I am going to buy one for me from ebay today. I have no choise as it appears.
I feel the need to thank you for your time and for the solutions that you provided me with.!
You have been most helpful.
HI did you ever solve this? I have the same problem, or very similar with middle and lower sections of screen dead, strange ghost touches and screen going crazy every so often, all started after I rooted phone. Was it just a broken touch screen? Cheers
gadget9192 said:
HI did you ever solve this? I have the same problem, or very similar with middle and lower sections of screen dead, strange ghost touches and screen going crazy every so often, all started after I rooted phone. Was it just a broken touch screen? Cheers
Click to expand...
Click to collapse
My friend i changed touchscreen and problem solved.
Thanks for the reply, good to know that it solved your problem, I have a new screen ordered, hopefully will solve mine too:good:
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Something similar ....
I had a similar experience on the 15th .... took my N5 off the Qi charger and the screen froze when i tried to unlock it.
I hit the power button and was able to unlock and get a few touches in before it froze again.
I was finally able (after much screen off/on cycles) to get down to the developer options and turn on show touches & show cpu usage.
... background processes looked fairly normal when the screen was frozen(touches showed as frozen) ...
I was rooted, stock rom except for xda user Jishnu Sur's N5 camera mod and running a couple tried & true root apps(Stickmount & QuickBoot). Thought some software issue might be jamming up the digitizer i/o causing it to freeze.
Reverted entirely to stock (the Team Win recovery was also experiencing screen freeze - buttons worked fine) including removing TRWP and re-locking the boot loader!!
The screen freezing problem persists ... my conclusion is that it's a hardware issue. :crying:
It's possible you are seeing the same thing, but I haven't seen anything in the forums to indicate it's a widespread problem.
Returning it for a replacement phone ... :fingers-crossed:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
biggiephat said:
Was at about 30% battery and the screen froze as in it wouldn't take any touch events. The backlight would react as if the screen wasn't touched. It seems like the touch events just were not registering but the phone worked in the background. Kernel issue maybe? I have been using faux.
Click to expand...
Click to collapse
Freezes tend to happen on custom kernels specially if you under-volt it too much. have you done that?
Screen Freeze
canaillou2k5 said:
Hi,
same problem here from France.
I already returned a Nexus 5, after multiple freeze I tried to format data partition via bootloader, (no rooted phone, following google instructions for stock reset) then the phone crash wile formatting, it never wake up gain.
When I get a new one from google after one or two week same problem appears, and it's append more and more often, since monday my phone crash one time more every night, and all the day today.
A this time I'm still trying to load it sine I came back from work seven hour ago, battery still at 49%.
I think it's and hardware issue too.
I'm very disappointed about Google and I'll never by anymore LG products.
Thanks for reading.
Click to expand...
Click to collapse
Last week I had the same problem with my new NEXUS 5. IT’S TOTALLY A HARDWARE ISSUE.
LG products are however not so bad in the JAPAN market but still we are expecting a lot from LG technology.
LG services suck.
I am facing the same problem with my Nexus 5. Unrooted, bought 7 months back from India itself, was working fine till around two weeks back,when the lags, screen freeze, blacking out n all appeared. Got it repaired twice at the LG centre. They changed the front display touchpad as well as the charging connector strip. The problem still persists.
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.
This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED
ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.
I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet
I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.
I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:
I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet
Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.
So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk