Related
This is the only thing stopping me from getting this phone.. I'm trying to determine how wide spread the issue is. I figured a poll was the best way to see how wide spread the issue was, and whether its worth it to shop around to try and find a working phone
Mine seems to work fine Its not as sensitive as say my girlfriends Incredible buttons, the ones on the Epic seem to work more like physical buttons but they aren't. You have to use a little force for it to recognize and I actually prefer that because I always found myself coincidently hitting the buttons on my girlfriends Incredible when i didn't mean to/meant to press another button
It is really a non issue for me. Haven't noticed it.
I think if you used one of the defective phones, it would have been obvious.. All the other buttons worked without issue. The back button on the one I tried wouldn't register no matter how hard or how long you pressed it - some times. Some times it would register for a light little hit, other times I'd be pressing down pretty hard and nothing. By the second or third time, you'd feel the feedback buzz (which was pretty cool), and it would actually work..
It was sort of funny, the rep who was trying to sell me the phone started off to try and down play it and say "I'd just have to get used to it"... until I gave it to him. In the end, he agreed there was something wrong.
I didn't want to make the guy try other phones because I was planning on purchasing the phone from my business' phone retailer... It would have been sort of wrong to make the guy go through 3 phones and just leave if I found one that worked..
Not sure if it matters, but what state are you guys in? I'd imagine that similar batches ship to the same region.. I'm in LI, NY
Absolutely never had a problem with the backbutton.
All 4 of my capacative buttons work with light taps AND full presses.
Its hard to tell wherethe buttons are when the lights time out, and you have to hit the button in the right spot for it to register. My nexus was the same with its capacatives.
beamed from the stars on a Epic 4G
While I don't think there is an issue with the buttons persay. I was doing some testing and seems there might be some "lag" I was having this issue more with the home button at times. One time after i knew i clicked it i let is sit. took a few seconds but continued to do its thing... So maybe its the same with the back button as well. Next time after you click it once let is sit and see if it proceeds.. that way we know its a lag issue vs button issue. A lag issue would be easier to fix I would think.
First of all NeonMonster, thank you for being awesome with the Nexus One back in the day of rooting it and changing things! Haha.
Secondly,
I had a defective Epic 4G. The back button was the worst of the bunch. I would have to hit it 10-15 times to get it to work. But it wasn't the only faulty button. All of the capactive buttons seemed to falter just about anytime I went to use them.
I went to Sprint the next day and explained the problem and she said I was the first to bring it to their attention. But long story short, she exchanged it and the buttoms work perfectly. There aren't as sensitive as say the EVO or Incredible but they work as intended and the phone I once thought was hopeless and I hated, is now a phone I'm contemplating keeping.
So there are definitely defective devices out there but it is as simple as going in and getting a replacement.
Thanks for everything you guys do!
I picked my Epic on launch day and all was well..my brother on the other hand just got one this afternoon and after we got it activated i hvae noticed his has this same problem.
lithid-cm said:
While I don't think there is an issue with the buttons persay. I was doing some testing and seems there might be some "lag" I was having this issue more with the home button at times. One time after i knew i clicked it i let is sit. took a few seconds but continued to do its thing... So maybe its the same with the back button as well. Next time after you click it once let is sit and see if it proceeds.. that way we know its a lag issue vs button issue. A lag issue would be easier to fix I would think.
Click to expand...
Click to collapse
I didn't notice any lag... Again, I think if you have a defective phone, it would be obvious. A press just didn't register, even if you'd wait..
Yeah, there isn't a lag. It just straight up does not register any contact. You have a defective phone. I took mine back and got a new one and it works EXACTLY like it should. Night and Day!
Buttons work great.
I bought the cheap screen protecter at RS and had it put on in store, my button presses were instant. When I got home and decided I didn't like or really need the screen protector, I took it off and then my button presses didn't register as smoothly may be a quick fix for some that want to use a screen protector.
asiana_jones said:
First of all NeonMonster, thank you for being awesome with the Nexus One back in the day of rooting it and changing things! Haha.
Click to expand...
Click to collapse
Aww from the nexus forum?? That was such a fun time! The nexus is truly a phone meant to be rooted. kinda miss that thing but the keyboard on the epic is too good.
But yes, there will always be phones that are defective and need to be replaced.
yeah i noticed some lag on mine. i also tripped out when then home and menu buttons were switched (compared to the evo) and kept pressing the wrong buttons.
its looking like a 50/50 so far on getting a phone without tis problem :-\
nicknomo said:
its looking like a 50/50 so far on getting a phone without tis problem :-\
Click to expand...
Click to collapse
That logic doesn't work.
1. Most people that don't have the problem won't vote.
2. Remove the people on the last option and it's 70/30 (at the time I write this).
You might be right with #1 (I don't know), but as for #2 it is 15-14 for people who are and aren't having some sort of problem with the back button (or other buttons)..
I do agree that this is far from scientific, as people who have never used the phone are likely to be voting..
Only read because I had the issue
Yep. I think you might just skip over this thread all together unless you've had the issue. Personally, I got one phone with the issue, exchanged it, and got another with the same problem - although not as bad as the first. However, I haven't returned the second one yet and the problem seems to have gone away. I'm not sure exactly how these buttons are engineered, but I'm wondering if more people with this problem will simply see it go away. FYI: the first phone I had was getting better but it started out as more of a 70% fail/only work with hard mashing.
My back button has a mind of its own :-( it presses itself when it wants to. Very annoying.
Sent from my Epic 4G - Rooted for My Pleasure!!
My first phone didn't have a working 4g radio. The second had this problem and it is very annoying if your used to a working button I returned it to radio shack. My third phone is perfect in every way.(hardware wise) this was all in the first week of the phone release. I would deffinetly go back and return it.
Sent from my SPH-D700 using XDA App
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.
Ok.. so this is the second time this has happened..
My phone was fully charged and for no apparent reason turned itself off. Then when I attempted to turn it back on, the power button would not do ANYTHING at all.. even after multiple presses (like 20).
I plugged the charger back into my phone, and the light wouldn't even come on indicating that it was connected to the charger.
Finally pulled the battery, put it back in, and viola - it powered up.
Then I was talking to my buddy and the same thing has happened to his MT4G. Except he never pulled that battery - but he said it took 15 minutes before the power button worked.
I think this is a BIG problem, because when I started searching the net for similar situations, I found one.. with the G2. Now that's TWO T-Mobile phones with the same problem.. Both made by HTC.. both with several Quality Control issues
Anyone else have this problem? I'm starting to think about going with a different phone now, which is crazy because I was absolutely in love with this phone... but I am not about to have a phone that decides to shut itself off and won't power up. Especially since my friend has the same problem which tells me this isn't something specific to my phone only which means potentially any device I get can have this issue.
I was deeply saddened to read the G2 has the same problem. What's going on HTC????!
Are you rooted? Overclocked? It really sounds like phone couldn't handle amount of OC (which happened to me several times). However, if it's a stock phone - hurry up and bring it back to T-mo and ask for replacement. This is not a common issue for these phones, first time I hear about it. Of course, there always will be cases of QC but, once again, this is not a common behavior.
I can say this has never happened to me so it sounds like an issue with your setup. Do you have anything modded ie overclocking is the one I'm thinking. Maybe pushing phone to hard.
Edit: sorry just realized I was in the general section.
Sent from my HTC Glacier using XDA App
borodin1 said:
Are you rooted? Overclocked? It really sounds like phone couldn't handle amount of OC (which happened to me several times). However, if it's a stock phone - hurry up and bring it back to T-mo and ask for replacement. This is not a common issue for these phones, first time I hear about it. Of course, there always will be cases of QC but, once again, this is not a common behavior.
Click to expand...
Click to collapse
No, I am not rooted. Stock running Launcher Pro Plus and Live Wallpaper.
After checking around, it appears this has been an issue for many G1, G2 and even a few Nexus Ones.
It appears the general consensus is that either the contact pins for the battery are not making firm contact when the battery shifts (supposedly on some phones the battery prongs not protruding enough, I have not checked mine yet but I intend to shortly)
I really don't want to return my phone.. my screen is the good one and my FFC is centered..
This happened to me just an hour ago. Only had the phone since friday and had this happen for the first time. Wouldn't respond at all. Everthing stock on phone.
Sent from my HTC Glacier using XDA App
Well I would return it because you chances of getting another good one are pretty good.
Sent from my HTC Glacier using XDA App
jjjackson56 said:
Well I would return it because you chances of getting another good one are pretty good.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Yeah, but what are the chances of getting one with the good screen, a centered FFC and no gaps in the metal bezel/side of the phone?
I'll wait it out and see what happens. There's always the warranty.
Same thing happened to mine. I took it back. It wouldn't charge and the power button didn't work.
I pulled the battery and it still wouldn't cut on or charge.
Phone was stock.
It magically came on by itself 5 minutes later without me touching it.
Sent from my HTC Glacier using Tapatalk
Please post questions in Q&A section.
I had a NS with a back button that used to get stuck and i exchanged that NS for a new one. Since then i did not have the issue. Here comes 2.3.3 and the little monster is back. I have seen it twice in the past few hours. Google fix this ASAP or this phone is going back for good.
Anyone else with this problem?
Sent from my Nexus S using XDA App
FlyingRequin said:
I had a NS with a back button that used to get stuck and i exchanged that NS for a new one. Since then i did not have the issue. Here comes 2.3.3 and the little monster is back. I have seen it twice in the past few hours. Google fix this ASAP or this phone is going back for good.
Anyone else with this problem?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
That's not good!! I had this issue occasionally (never exchanged the phone though) and so far since 2.3.3 it's not happened.
I would strongly suggest raising the issue on the google support forums - there is an existing thread from before the 2.3.3 update which as it happens was meant to fix the problem......
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=455215ff8747658b&hl=en&start=40
Mine is N1, I also got back button problem occasionally since 2.3.3. I press the Back, I feel the vibration, but there is no action. I should retry few times.
I guess this is 2.3.3 bug.
kikikaka said:
Mine is N1, I also got back button problem occasionally since 2.3.3. I press the Back, I feel the vibration, but there is no action. I should retry few times.
I guess this is 2.3.3 bug.
Click to expand...
Click to collapse
u know i had this issue on stock 2.3.2, both home and search was not working, then i wiped data & cache from stock recovery, and then it started working again, worth giving a try!!!
back button is very irresponsive in 2.3.3 !!! i thought google was supposed to fix that s**t. instead it has got even worse for me.
deeren said:
back button is very irresponsive in 2.3.3 !!! i thought google was supposed to fix that s**t. instead it has got even worse for me.
Click to expand...
Click to collapse
my back button is very responsive maybe you need to reflash.
OK I take back what I said previously, this has started happening to me again now. In fact I'd say it's worse than it was before.
I have no idea what to do other than trying to exchange the phone which will probably be a nightmare because I've had it since early January..........
weird cause i read people saying that if their phone had a back button issue it was fixed with 2.3.3
Well I've taken it back to the carphone warehouse where I bought it, they are going to attempt a repair..............will hopefully end up with an exchange for a new handset - i'll keep you posted.
Well the nexus one never had this problem at all, never. And now since the update it too has this issue. So that's pretty solid proof to me that this problem exists and needs to be fixed by Google.
I have non rooted nexus s 2.3.2 and noticed this for the first time last night. Back button key would either stick and/or be un responsive (light would turn off).
I wonder I'd this be a memory issue in that it might occur more frequently when the device is low. Notice a lot of apps run services around midnight and in the morning when this is happening for me..
I have also seen problems with green screen from flash when memory is low.
Closing some apps seems to solve this.
Just a thought. Hope this is not a sign of a hardware failure.
I'm waiting to collect my "repaired" Nexy - wondering what if anything they will have done to try and fix it.....
Feel naked without my phone........
Take off battery cover. Tighten up a bit the screws on the back of the phone. See if that changes anything. I experienced that a little while ago, tightened the screws and now all's good. Haven't seen a single issue since. 2.3.2 and 2.3.3
Sent from my Nexus S using XDA App
bogdi1988 said:
Take off battery cover. Tighten up a bit the screws on the back of the phone. See if that changes anything. I experienced that a little while ago, tightened the screws and now all's good. Haven't seen a single issue since. 2.3.2 and 2.3.3
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Well I dont have the phone right now but I'll certainly give this a try if the problem happens again once I have the phone back.
Out of interest what size/type of driver do you need to fit the screw heads??
Thanks!!!
moon-unit said:
Well I dont have the phone right now but I'll certainly give this a try if the problem happens again once I have the phone back.
Out of interest what size/type of driver do you need to fit the screw heads??
Thanks!!!
Click to expand...
Click to collapse
a small philips head screw driver
same problem with me. I upgrade to 2.3.3, the back button will stick for several seconds especially when you hit back key very fast and repeat after fast scrolling the screen.
I flash back to 2.3.2, change rom, not install apps, the problem is still there. And even in bootloader, the issue is still there.
I've just been told my phone is being sent to some central repair hub and might take 28 days to get back to me :-(
will probably get scratched to bits and still wont be fixed.....
Guess I'll have to dig out the old Sony handset to keep me going for a few weeks..today is a bad phone day...
Well I picked up the phone today and noticed a few things where different, firstly I now have an unlocked padlock icon at the bottom of the bootscreen - On checking recovery it would seem my bootloader has been unlocked....
Secondly it was running 2.3.1 which I also found odd?
Going charge it up and do a manual update to 2.3.3 using the full 90mb ROM, wonder if the back button issue has been fixed......? the repair notes said the PCB had been checked and cleaned......
I'll keep you posted.
I noticed tonight that my touchscreen stops working when I slide the keyboard all the way out. It looks like when you slide it, when it gets about 1/2 way, the lights under the touch keys (home, search, etc) turn off, then 3/4 of the way out, they come back on, but you can't touch anything on the screen. No scrolling, no selecting, nothing. When you start to close it, the lights turn off 3/4 of the way open, then 1/2 the way open they turn on and the touch screen starts working again.
I've been watching videos on how to replace the digitizer and they look easy enough for me to do, but is it really the digitizer if it is working when the phone is closed? This sounds more like a loose cable, eight? Anyone else have this happen?
That does sound more like the flex cable
Michigan rockin the forums again :O
one by one the penguins steal my sanity
CodeMonk said:
I noticed tonight that my touchscreen stops working when I slide the keyboard all the way out. It looks like when you slide it, when it gets about 1/2 way, the lights under the touch keys (home, search, etc) turn off, then 3/4 of the way out, they come back on, but you can't touch anything on the screen. No scrolling, no selecting, nothing. When you start to close it, the lights turn off 3/4 of the way open, then 1/2 the way open they turn on and the touch screen starts working again.
I've been watching videos on how to replace the digitizer and they look easy enough for me to do, but is it really the digitizer if it is working when the phone is closed? This sounds more like a loose cable, eight? Anyone else have this happen?
Click to expand...
Click to collapse
Sounds like it's most likely the Flex Cable. Which is easy enough to change. They usually don't just come loose. Has been know to happen, but it's rare. You can repair it yourself, you just have to have the proper tools. If you do attempt it, be sure to take your time. You can pick the Flex Cable / Tool Kit up on Ebay, or Amazon fairly cheaply.
prboy1969 said:
Sounds like it's most likely the Flex Cable. Which is easy enough to change. They usually don't just come loose. Has been know to happen, but it's rare. You can repair it yourself, you just have to have the proper tools. If you do attempt it, be sure to take your time. You can pick the Flex Cable / Tool Kit up on Ebay, or Amazon fairly cheaply.
Click to expand...
Click to collapse
I personally wouldnt touch it... I had a bad flex cable and brought it to sprint and they bricked my phone while changing it... If sprint can brick that easily changing a flex cable, imagine your odds...
Sent from my PG06100 using Tapatalk
drob311 said:
I personally wouldnt touch it... I had a bad flex cable and brought it to sprint and they bricked my phone while changing it... If sprint can brick that easily changing a flex cable, imagine your odds...
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
That's very true. There is a chance you can damage, or even "Brick" the device if you don't know what your doing. I've changed about about five already. The first one took forever, I was so nervous. But after about the third one it was all good . Same with the digitizers, first one is like Ahhh . After about the 10th one it's not that scary. No I do not damage my phone that often. Just know a lot of people who do. That also do not have TEP Insurance.
TEAM MiK
Mik Roms Since 3/13/11
Ok, in the immortal words of Eminem, "I'm not afraid." Or wasn't, at least. I took it apart tonight and yep, the flex cable is broken. Taking it apart made it worse and I've lost my earpiece. The good news is the touch screen works while the keyboard is slid out... But it doesn't with it in. lol
I did find some on ebay, but does anyone know of a place that sells the sliding mechanism? Mine is pretty sloppy and I'd like to fix that while I have it open to replace the cable.
Your best bet is going to be a damaged Shift. I don't know of any place that sells just the parts. But I would still hunt around on the net. Maybe check Amazon, or Craigslist.
TEAM MiK
MikROMs Since 3/13/11
I mean nobody disrespect I am just as intrigued by taking things apart and just as satisfied with self repair as the next tech guy, but you don't even need to have TEP to get a shift with a broken flex cable replaced. This is a warranty issue. By no fault of yours, the phone is broken. Sprint replaces these without push back, I'm on my 3rd shift. Now that you've opened it though, you may be out of luck.
HTCotta said:
I mean nobody disrespect I am just as intrigued by taking things apart and just as satisfied with self repair as the next tech guy, but you don't even need to have TEP to get a shift with a broken flex cable replaced. This is a warranty issue. By no fault of yours, the phone is broken. Sprint replaces these without push back, I'm on my 3rd shift. Now that you've opened it though, you may be out of luck.
Click to expand...
Click to collapse
You can always tell them you took it to a third party store to get looked at.
It was out of warranty. I already tried the warranty route.
Anyway, got the cable today, put it in and the jawbone connector for the LCD is jacked up. It won't go all the way in no matter what you do. So I put the old one back in and now the touch screen is completely gone.
My wife called sprint while I was messing with it cause she wanted to see if there were any repair stores that had parts and they offered me an early upgrade. $105 bucks and I get up to a $150 discount as long as I re-up for 2 years. Since I'm pretty happy with Sprint, this is probably a win-win situation for me to do it, so I did.
Now I just have to decide... Moto Photo, Nexus 4g, or Samsung Galaxy 2. Any opinions?
*edit: I use CM7 on my shift and would like to continue to use CM7, I don't NEED CM9, but the option would be nice.
I have a shift for sale mint condition only 2 months old...
Sent from my PG06100 using Tapatalk
Sorry, I already signed up for the upgrade. I just need to go pick one up.
Wait for the Galaxy Nexus, that's what I'm doing. The development is too awesome on nexus devices for me to stay away any longer. Even if the specs are already somewhat outdated, I just want one
HTCotta said:
Wait for the Galaxy Nexus, that's what I'm doing. The development is too awesome on nexus devices for me to stay away any longer. Even if the specs are already somewhat outdated, I just want one
Click to expand...
Click to collapse
You will miss your Shift . Once the Shift has you, it will never let you go .
obe1kobe said:
I have a shift for sale mint condition only 2 months old...
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
How much? ....
obe1kobe said:
I have a shift for sale mint condition only 2 months old...
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
BOOOO! Try the marketplace on xda instead of advertising it here btw what's you next device? I'm trying to see if I should even bother staying with sprint now that LTE is on hold it seems like I might never get 4G speeds in my town.
Ok, didn't want to clutter things up and start a new thread so I'm gonna hijack this one. Hope thats ok.
I've been having troubles with my touch sceen the last few weeks and its very sporadic. So first issue it just simply stops responding all together. Like for instance i go to pull notification bar down and it stops part way down and i cant slide it up or down nor do the home back keys work. I have to hit power button to lock then hit power button and unlock then all is fine for awhile. And to be clear i dont have to power it off, just lock it. Another instance I'll be browsing the web and i go to scroll down it starts acting goofy. As if i got 2 fingers on the sceen trying too pinch to zoom when i clearly dont. Another silly thing happens where it acts like some one is remotely using my phone. For instance I unlock my phone and then it just hitting buttons. It's actually made a phone call for me before. Also happens when browsing or anything else.
I run miui build 112300 with sparks patch. I have ran this rom for a very long time so something tells me it aint the rom. I really dont remember what I've installed lately so don't know if an app would be causing this. Something tells me its a hardware issue but i was hoping to get some suggestions before flash something new or worse running the ruu to stock. Also, i dont think it would be the flex cable because it happens mostly without the keyboard out. Plus i rarely use my keyboard, although I'm using it right now.
Any suggestions would be appreciated.
Thanks in advance.
Sent from my PG06100 using XDA App
^^^ same thing happens to me. I think flashing the touchscreen firmware update would solve it but i haven't had time to try and fix it.
Shifted from my EVO
tbag1122 said:
Ok, didn't want to clutter things up and start a new thread so I'm gonna hijack this one. Hope thats ok.
I've been having troubles with my touch sceen the last few weeks and its very sporadic. So first issue it just simply stops responding all together. Like for instance i go to pull notification bar down and it stops part way down and i cant slide it up or down nor do the home back keys work. I have to hit power button to lock then hit power button and unlock then all is fine for awhile. And to be clear i dont have to power it off, just lock it. Another instance I'll be browsing the web and i go to scroll down it starts acting goofy. As if i got 2 fingers on the sceen trying too pinch to zoom when i clearly dont. Another silly thing happens where it acts like some one is remotely using my phone. For instance I unlock my phone and then it just hitting buttons. It's actually made a phone call for me before. Also happens when browsing or anything else.
I run miui build 112300 with sparks patch. I have ran this rom for a very long time so something tells me it aint the rom. I really dont remember what I've installed lately so don't know if an app would be causing this. Something tells me its a hardware issue but i was hoping to get some suggestions before flash something new or worse running the ruu to stock. Also, i dont think it would be the flex cable because it happens mostly without the keyboard out. Plus i rarely use my keyboard, although I'm using it right now. If not, time to take it to Sprint.
Any suggestions would be appreciated.
Thanks in advance.
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
The first thing you can try is the latest Radio and Touchscreen Firmware HERE. If that does not work and the screen is still acting strange I would RUU back to Stock Unrooted. See if that resolves the issue. If not it's time to take it back to Sprint.
OK, thanks for the suggestions. Just flashed the new firmware. Like I said it was very sporadic so time will tell. Hopefully this works cause it's been a long time since I rooted my phone and I'd hate to unroot it.
Sent from my PG06100 using XDA App