Related
Well for some reason, at random times, when I press on my screen the notification bar will drop down. This gets annoying because It won't allow me to do anything. For example, if I were to bring up google and type something, each letter I try to type the notification bar will drop! ugh.. what could be causing this problem? is it the screen needed to be replace? any advice?
also I have to hold the phone in a upright angle in order for it to work properly. If I leave it,for example, flat on the table it won't really pick up anything I push. But as soon as I lift it up and tilt it, works fine.
I kinda have the same prob but mine will type different letters then i push and will even take overat times but I think mine has to do with the bad seal I got cause I have one of the first model's
Sent from my HERO200 using XDA App
Screen covers often times will cause this. Happened to me every few days when I had one. And fyi, I'm a mechanic, not had a screen protector in months, and no scratches. This screen is pretty resilient.
Sent from my HERO200 using XDA App
I too have the first model however is there a fix for this?
EclipseTouchPro said:
I too have the first model however is there a fix for this?
Click to expand...
Click to collapse
Well it could be a lose connection for you with having to hold it a certain way
Sent from my HERO200 using XDA App
rulyskull said:
Well it could be a lose connection for you with having to hold it a certain way
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
know of a step by step how to fix it? but before I do anything like that, how can I tell if I'm still under the 1 year manufacture warranty, I got this phone from private seller at a low price.
EclipseTouchPro said:
know of a step by step how to fix it? but before I do anything like that, how can I tell if I'm still under the 1 year manufacture warranty, I got this phone from private seller at a low price.
Click to expand...
Click to collapse
Call sprint
Sent from my HERO200 using XDA App
Mine did this over time eventually my touch screen just gave out and i had to go get a refurbished one
I am having the same issue with Sprint Hero CDMA. I tried clearing all factory settings, delvick cache, and anything else I could find to clear in recovery. I then used a RUU to clear it completely back to factory, still no luck. I noticed that what it is actually doing is for some reason it is sensing the touch only at the top. I figured this out while playing 'alchemy classic'. If i tried to touch any of the top icons, (for those that do not play it, these are in the same are of the notification bar) it wouldn't work. When it stopped letting me move the elements around, if i clicked anywhere below one of the top icons, it would select the icon above it, regardless of how far down on the screen I touched. I will be going to the sprint store to have them look at it, hopefully they will have decent news.
Okay, so I am having issues with my power button, mainly because when I go to put my phone to sleep or wake up, it very oftenly pushes the button twice, thus I sometimes have to push it several times to get it to turn the screen off or on.
My question thus being (the reason I put this in the developer forum) is there a way to fix it via putting a delay on how often the button recognizes being pushed?
Pretty much putting a 100ms delay on each press so it can't wake up and put it self back to sleep in a split second.
And if this IS possible, is it possible without needing a custom ROM? or could I put in a fix via temp-root and push it through with ADB?
Man I thought I was the only one with this problem, thank god im not it wasnt a biggie, but it starts to get annoying after a while :/
mrpandainc said:
Man I thought I was the only one with this problem, thank god im not it wasnt a biggie, but it starts to get annoying after a while :/
Click to expand...
Click to collapse
Yeah, it seems like it would be an easy software fix. But no1 has address the issue that I've seen D:
sometimes i have problem also, issue cant be replicated but it happens....
I don't know. I just pushed my power button several times in a row and I don't see a problem. Never had since day one. Could be the way you're holding it. The button is kinda back a little compared to other devices.
Sent from my T-Mobile G2 using XDA App
mdayjr said:
I don't know. I just pushed my power button several times in a row and I don't see a problem. Never had since day one. Could be the way you're holding it. The button is kinda back a little compared to other devices.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Thats the crazy part, when you realize it happens, you try to replicate it and it works flawlessly, but if you happen to be just using the phone and you click the button it sometimes skips randomly.
Border-line being locked
mdayjr said:
I don't know. I just pushed my power button several times in a row and I don't see a problem. Never had since day one. Could be the way you're holding it. The button is kinda back a little compared to other devices.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I can actually replicate it, mine must be really sensitive. And yes, I have tried holding it many ways. I see it most often when its on my desk and I'm using it tho. but its not uncommon at all for me.
It wouldn't bother me if it wasn't all the time, but its pretty much every other time for me :[
Never had the problem until few days ago, and it's starting to happen quite often now. I'm a little bit worry being a hardware problem rather than a software problem.
Well? Whatever problem, just remember, you have 1yr warranty
Sent from my T-Mobile G2 using XDA App
I think it wouldn't be so much of a problem if we had trackpad wake embedded already, but if ur using visionary isn't there some trackpad wake/or maybe trackball wake for the nexus that will work?
Sent from my T-Mobile G2 using XDA App
demallic said:
Never had the problem until few days ago, and it's starting to happen quite often now. I'm a little bit worry being a hardware problem rather than a software problem.
Click to expand...
Click to collapse
Well I am sure its a hardware problem that can be fixed with software. If the hardware is sending multiple presses then software can compensate and tell it to only actually register lock presses once every few milliseconds.
My question is it possible to do it with a minor tweak to the code?
TMo already has a replacement in the mail for me because of this exact reason...The guy said I was the only person who said something like this was happening. Guess he was wrong, seeing other people with this issue makes me happy.
Sent from my T-Mobile G2 using XDA App
JRG1392 said:
TMo already has a replacement in the mail for me because of this exact reason...The guy said I was the only person who said something like this was happening. Guess he was wrong, seeing other people with this issue makes me happy.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Yeah, I did the same thing. However, if my new one can't overclock to 1.42ghz at least, I will probably ask for another one
I want my G2 more future proof.
ditto. bump.
Sent from my T-Mobile G2 using XDA App
Yeah same here....sometimes freaks me out cuz I'm like oh no my screens black...I feel my heart fall a lil lolz
Sent from my T-Mobile G2 using XDA App
I'm glad I'm not the only one. Too bad no1 knows if this can be fixed in software.
I believe this issue is with people who did the temp root and OC'ed it to 1.42ghz. I noticed when I press power to unlock the screen, the screen will not light up right away, than it does for a faint second and shuts back off. I have to press the power button again and the unlock screen shows up. I hope this does not cause any other issues with the phone. Otherwise ill have to leave it at the stock speed.
I have had this issue since I got the phone, so it's not anything to do with overclocking.
all right. I've found various things about this on the web regarding other HTC phones, but I can't seem to find if anyone else has had this problem with their shift... This morning I realized that the "clear" button in the notification dropdown on CM7 wasn't working for me. I wrote it off as a weird bug. But then I tried to play angry birds, and I can't drag them back, they just fall right off the slingshot.
So I zoom in and I can pull the birds back, but when I get to this strip on the screen, they fly off without my picking my finger up.
Besides the clear button, screen presses generally seem to work, atleast when I'm selecting icons in landscape mode from my home screens. But the n1 style live wallpaper will respond to touches in this "strip" of screen by shooting off the lines around it instead of in it. Also, when I tried to drag to a different homescreen and stop in this strip, it will bounce back. same thing with notification bar. If I try to start dragging the screen from this "strip" I get no movement. The weird thing, of course is that this part of the screen isn't completey dead in terms of responding to touches, because it does register on my device that it is being touched, but drags, the notification menu clear button, the live wallpaper, and, of course, angry birds act funky when I use this part of the screen.
I guess I have to go back to sprint. I think I'm just going to flash a stock rom, but not unroot it.
I also don't have time, so I'm kind of just hoping it will go away.
ANYWAYS... anyone else having touchscreen issues with their HTC EVO shift?
PS: I think clocking my kernel at 800 instead of the 1200 I was using might have something to do with this?
Was running at 800 to preserve battery life, but back at 1200 after a nandroid restore and the problem seems fixed.
2 be clear, I had this issue on CM7 and MikFroyo, so I don't think it could be software related. But CPU clocking related.
Yeah, I also doubt that is the case.
My screen had a freek out. With out touching the screen it would open and close apps jump screens and when I touched the screen I would get no response at all. Had to RUU and send it in for a new phone it was in the connection with the screen. So the sooner you ask for a replacement the better.
Sent from my PG06100 using XDA App
did you just call? any tips? I'm wondering if I can handle this over the phone or not. Also - what did you do while you were waiting for the new phone to come in?
turns out it was the friggen screen protector. however, before I realized that I called my local repair shop and they said that they would be able to swap my phone out for a new/refurb one for $35. Too bad it isn't actually an issue, because I've noticed that the phone is a little less responsive to touch even with the screen protector off... it's just that its not clearly an issue at this point.
I actually had a similar issue with a replacement phone where the left side about 1/8" wouldn't respond (couldn't press q button on keyboard at all). After some research I found out about a great lil app to test screen touch response and any bad areas and it helped me diagnose that it in fact was the screen having a fault...look up "touch test" in the appstore and it should narrow down where and if your screen has a bad area that's not responding...it helped to get my in-store replacement in and out the store since I could show them the issue right away along side an in-store model. I hope this helps and I that I read the post correctly. Let me know if it helps you.
Sent from my PG06100 using XDA App
My screen had a dead line going across the middle of the screen but only when swiping side to side, for some reason vertically it was fine....
unrooted, went to sprint store repaired in less than 30 minutes...
onefasttreopro said:
I actually had a similar issue with a replacement phone where the left side about 1/8" wouldn't respond (couldn't press q button on keyboard at all). After some research I found out about a great lil app to test screen touch response and any bad areas and it helped me diagnose that it in fact was the screen having a fault...look up "touch test" in the appstore and it should narrow down where and if your screen has a bad area that's not responding...it helped to get my in-store replacement in and out the store since I could show them the issue right away along side an in-store model. I hope this helps and I that I read the post correctly. Let me know if it helps you.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Awesome tip, dude. This will help me get a replacement for sure. The issue came back and this is solid proof it exists. Gonna make it hard for anyone to pretend there isn't a problem. Thanks!
Sent from my PG06100 using XDA App
No problem...glad to help...it definitely saved me time...I installed it on my phone and the stores phone and compared them side by side...that way they can't give you a BS answer of "screen needs calibration" etc etc. Lemme know how it goes.
Sent from my PG06100 using XDA App
Sorry didn't respond faster. I just called them and they sent me a new phone next day and I sent them the old phone. Easy as pie no problems with the reps or the techs they didn't argue about it at all. It did take a long time on the phone because they were checking the phone settings no sure what this was but oh well. Just remember to ruu back.
Killer Shift
So they ended up still pretending that there wasn't an issue, saying that maybe it was just the touchtest app. It took a while to convince them that it wasn't just an app.. but after I left it with them for an hour (an hour where I'm sure they did nothin) I came back and showed them the issue again, compared it to the shift that they had, and they finally agreed to order me a refurb. A hassle, but a necessary one.
Sent from my PG06100 using XDA App
Sounds like they just hated looking bad and that you had proven them wrong so they put up a wall...nonetheless I'm glad it ended up working out and hope the replacement phone works out for ya...
Sent from my PG06100 using XDA App
onefasttreopro said:
so they put up a wall...
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Agreed..It's awful how there is no set policies when it comes to service. Your fate pretty much rests with the tech you happen to get. Some are easy to get along with and some (obviously) aren't.
Sent from my PG06100 using XDA Premium App
The Refurb is great... oh, and FYI - don't use displex on touchscreens hahaha.
Hi guys...Just bought a N7 for my GF as a X-Mas gift and while it's great when working, there is a major touchscreen issue going on.
Let me first say I have searched and searched and came up with a lot, unfortunately it seems the problem was "fixed" by google with official updates. Well not in this case. I am on latest 4.2.1.
The issue is, the touchscreen will completely rearrange itself somehow. Example- if you click on something in the upper end it will click something randomly at the bottom of the screen. Another issue it, if you click on search/browser address bar and start typing, there is a ton of lag , and any number of things happen like, again, something else will get pressed at the bottom, or it will do nothing, and then suddenly start hitting a key (again, with the keyboard popped up at the bottom) like x over and over again, filling the page with 10-20 X's...
As soon as I put it to sleep and wake it up/unlock...it immediately goes away, just to come right back in a few minutes.
She does have a case on it with a magnet to auto wake, so I told her to take it off and see if it keeps doing it. It does...so no go there...
I want to call google for support, but am scared of getting a dumb rep that will tell me to power off the device etc...you know the drill...by the book pre-written crap they tell you to do, that solves nothing.
Any help would be much appreciated...and again sorry if this is something well known and simple to fix, but again, all my research dates back to june posts about issues already fixed via updates.
Thanks in advance!
Have you already tried a factory reset as after most recent update? You will lose all data but worth a shot. May need to RMA.
Sent from my Nexus 7 using xda premium
Ill try it
Sent from my SGH-T999 using xda app-developers app
Factory reset...ok for a while..then it started again...
Got it all figured out tho....if you ever so slightly twist the body to the left the screen will not respond at the bottom and will start pressing itself randomly....sometimes even touching the bezel will do something. ..then twist it a bit to the right and all is well...
Sh*t built product obviously. Had it in a case before even turning it on.
Going back...hopefully replacement will be better.
Sent from my SGH-T999 using xda app-developers app
accordex said:
Factory reset...ok for a while..then it started again...
Got it all figured out tho....if you ever so slightly twist the body to the left the screen will not respond at the bottom and will start pressing itself randomly....sometimes even touching the bezel will do something. ..then twist it a bit to the right and all is well...
Sh*t built product obviously. Had it in a case before even turning it on.
Going back...hopefully replacement will be better.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Ahh. You got the floating screen issue. Asus knows of it and will fix it.
Sent from my Inspire 4G using xda premium
I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)
mikeinaus said:
I have a small line on my screen that is unresponsive. It goes straight across the top of the screen exactly where the install button is in the play store (about 1" from top of screen at roughly 1/4" thick). Its in a pretty awkward spot and causes a lot of problems. For some reason it has also disabled the tap to wake feature of my phone.
I installed the "Touch Test" app which shows that my entire touch screen is working. However it shows the phone recognizing 2 pointers (touches) being active whenever I touch that area of my screen. I've been having this problem for 2 or 3 months now and all of a sudden today on my lunch break it went away. I was able to tap to wake the screen (worked perfectly the 20 or so times I attempted it), I was also able to hit the install button in the play store and life was great... Or so I thought. A few hours later on my next break my phone went back to annoying piece of junk that I completely dislike using.
Now I dont know exactly when this started happening. I did notice it sometime soon after the 4.4 update, and flashing a custom rom/kernel has made no improvement. Anyone got any ideas? I loved this phone before this started, and my phone is so frustrating now that I completely disrespect the thing and have scratched the crap out of the screen. I'm really hoping this can be fixed so I can go on with enjoying whatever life I have left with the g2, if not I'll probably just abuse it until it breaks then switch over to a water proof z2 or something along those lines... Phone was very well taken care of before the problem started, wasnt dropped or exposed to water (other then using outside in the rain for a few min at a time)
Click to expand...
Click to collapse
I have this problem too, any fixes?
Well I am in shock as to how we all have the same exact problem.
I first thought it was hardware failure on the screen itself and was pretty bummed. But now I see people have the exact same unresponsive touch screen in the exact same spot as mine? What ROM/Kernel are are you guys running? I am running what is in my sig and had not noticed it before until a couple of days ago. Coupled with the unresponsiveness, my Knock on does not work and the phone becomes mildly warm faster than usual. I think it might be a kernel software issue.
Ugh... I was hoping this wouldn't turn in to this big of a problem. I've got the same thing here, VS980 after flashing a Cloudy ROM.
I took over a thread here recently http://forum.xda-developers.com/showthread.php?p=52858791 , but I'll post here again anyways. I wonder if it's the same spot with you guys too. It's right where the install button is on the Play Store, right? For a few hours after it started it went back to normal, then messed up again permanently.
TOT'ing back to 12B didn't help, so I got a replacement device from Verizon. I've yet to send back my old one because I'm worried about the unrooted flag in the bootloader and settings.
I don't have enough posts yet to be able to do this, but can someone alert a dev about this? Particularly in the thread of whatever ROM it was that you last used? A lot of people in the last thread said it came from Cloudy, and I figured it might make sense as Knock Code was supposed to be a feature on there even though the VS980 source wasn't out. Then again I probably have no idea what I'm talking about, but I'd love to hear from someone who does.
I dont think my blacked out area is quite as thick as yours but yes its in the exact same place. To confuse things even more my phone just started working properly again (for how long is another story). Its very odd that It hasnt worked once in 2 months or so and now twice in 2 days its started working.
As a side note I'm pretty sure I started having this problem immediately or very shortly after the OTA kitkat update. I'm now running cloudypro II 2.0 with 3.4.0 kernel, which as i said before didnt fix the problem in the 1 month ive been using this rom.
I originally thought it may have been a software issue, but for it to randomly start/stop working all of a sudden after so long of no function (with no software being added or changed) I'm thinking its more likely a hardware problem? When I fly home on Monday I'm going to try opening up the phone and cleaning the contacts to the from the touchscreen to the mainboard.
If it is software related it may have something to do with air plane mode. I get almost no signal where I'm working at the moment and the constant searching for signal kills my battery pretty fast so I've started using air plane mode the past few days. Thats the only thing out of the ordinary that i've done software wise.
Having the same issue!!
Has anyone found a solution ?
Please reply.
hashir1296 said:
Has anyone found a solution ?
Please reply.
Click to expand...
Click to collapse
Yes, we've sent it to LG for repairs and they were able to fix it easily.
Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app
Had the same today but at the middle of the screen, I pressed on the corners and around the screen pretty hard and it is back to normal(for now).
Hope it wont come back.
You can unroot the device by flashing original rom with LG flash tool.
THISISINSANE said:
Sfkn, was your phone rooted when you sent it to them? I'm having the same issue, and it either started happening today, or I just noticed it today, but it's bugging the crap out of me. I'm running stock kk, rooted with twrp and on the cloudyfa kernel.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
No, I am completely stock.
Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app
THISISINSANE said:
Yeah I used the LG mobile support tool and that unrooted it. Now I'm just waiting for my replacement phone to arrive.
Sent from my LG-D801 using XDA Free mobile app
Click to expand...
Click to collapse
You claimed insurance rather than with LG repair?
Sfkn2 said:
You claimed insurance rather than with LG repair?
Click to expand...
Click to collapse
I went with T-Mobile's warranty replacement. I already sold my backup phone so I couldn't send the phone to LG for repairs and still have a phone
Sent from my LG-D801 using XDA Free mobile app