Hi XDA communtiy,
I've been breaking my head with the following question:
My responsive buttons stopt working.
It goes better after a factory reset, but then again. No home, back button...
It is a real pain in the *ss.
I don't think it is a hardware problem, more a software problem...
Do you think that if I install a ROM on my device this would clear my problem?
Does anybody has the same problem?
It began shortly after the android update 4.1.1.
Greetings,
Krikke
Hope you didn't dropped your phone?
You can try the roms f you want ...(Dn't forget to backup)
AkumDX said:
Hope you didn't dropped your phone?
Click to expand...
Click to collapse
What do you mean, are the responsive buttons know to break?
No serieus droppings happend, just the occasionally slip!
I also have a second device were the top screen is cracked, maybe put the two together in one?
Krikke001 said:
What do you mean, are the responsive buttons know to break?
No serieus droppings happend, just the occasionally slip!
I also have a second device were the top screen is cracked, maybe put the two together in one?
Click to expand...
Click to collapse
Yeah, you can try inserting the screen assembly of your current device into the one with cracked screen, if the responsive buttons are working correctly there and you don't need the second phone. Otherweise I don't know, can't really call it a software issue. What about logcats?
Related
could anyone be able to help me? im using HD2 normally with android 2.3.4. however recently my touch screen have has a problem is that when i turn off screen by pressing the end button, after that i turn on that screen and u know i couldnt slide to go the main menu . but if the screen turn off automatically and u turn on it immediately, u will slide and use it. So, yesterday i decided to up to another ROM to solve it, but when i did it the screen is changed that situation and that situation worse and worse until now i cant touch to screen. who could give me some cures for this disease. cheers for that !!!
btw, i did up to wm6.5 and nothing had changed ...................................
uppppppppppppp............... help me
What ROM are you running on Android? AND are you NAND or SD??
Sadly it has nothing to do with the rom loaded on your phone. The end button is right on top of the ribbon cable for the digitizer. Your phone needs a new digitizer. I had the same thing happen to me. You are not alone and its a common problem. I would say Its actually a fault in the HTC design since the end button puts direct pressure on the digitizer ribbon and eventually its becomes damaged. I have a new hd2 now, but I use button savior on android. It allows you to use a the touch screen to press the end button.
thx for ur advice . probably i have to buy another screen once (.
aprogressivone said:
Sadly it has nothing to do with the rom loaded on your phone. The end button is right on top of the ribbon cable for the digitizer. Your phone needs a new digitizer. I had the same thing happen to me. You are not alone and its a common problem. I would say Its actually a fault in the HTC design since the end button puts direct pressure on the digitizer ribbon and eventually its becomes damaged. I have a new hd2 now, but I use button savior on android. It allows you to use a the touch screen to press the end button.
Click to expand...
Click to collapse
Can you please sen us the link for that software..
I would never use that button again knowing that it would harm my device in the future..
Hi guys,
I bought a second hand mini pro, and flashed (rooted, unlocked bootloader)it with the help of one of the several guides. with Simplexity and MiniCM7
It seemed to work fine at first, but now something odd happens.
I can only turn the device on (working) when I keep the keyboard slided out. When I start up with it slided in, The screen is turned on but no image appears: It stays black.
When it is turned on (slided out) I can use the phone normally. But when I slide it back in, the screen is frozen and won't react to touches.
Putting the phone in and out of standby (slided out) will have two possible outcomes: Either its usable as normal. Or it simply won't come out of standby at all. The phone seems to react (sounds) to pressing the buttons on the keyboard though.
I used Seus and manual methods to reflash to stock, try other kernels, but the problems remain.
I think it's the hardware that's failing but maybe this can be caused by the flashing as well?
Are there any methods to rule out one or the other?
Cherek said:
Hi guys,
I bought a second hand mini pro, and flashed (rooted, unlocked bootloader)it with the help of one of the several guides. with Simplexity and MiniCM7
It seemed to work fine at first, but now something odd happens.
I can only turn the device on (working) when I keep the keyboard slided out. When I start up with it slided in, The screen is turned on but no image appears: It stays black.
When it is turned on (slided out) I can use the phone normally. But when I slide it back in, the screen is frozen and won't react to touches.
Putting the phone in and out of standby (slided out) will have two possible outcomes: Either its usable as normal. Or it simply won't come out of standby at all. The phone seems to react (sounds) to pressing the buttons on the keyboard though.
I used Seus and manual methods to reflash to stock, try other kernels, but the problems remain.
I think it's the hardware that's failing but maybe this can be caused by the flashing as well?
Are there any methods to rule out one or the other?
Click to expand...
Click to collapse
I'm responding to the thread's title : It's a hardware failure.Brick means you can't even power it on/flash mode.If I helped click the "Thanks" button.Also,try using nAa-11 my and x10man's ROM called XMP Rom and tell us if you still have this problem.I understand that you posted this here (If you post it in questions section almost no one will respond )so I won't tell about that.
(Oh, my bad. Mods feel free to move my thread)
I was afraid of that. I'll try your ROM as well, but I'm afraid its the hardware too.
Thankfully I only paid 30 euros for it
I think the flex cable is gone bad, i have the same problem here. My mobile doesnt respond to any touches. First it happened only when i would slide the keyboard. But now its dead as a whole
speedsys said:
I think the flex cable is gone bad, i have the same problem here. My mobile doesnt respond to any touches. First it happened only when i would slide the keyboard. But now its dead as a whole
Click to expand...
Click to collapse
The XMP rom didn't fix it, so I guess you're right. Would a flex cable (those are the flat orange ones right?) be expensive?
Cherek said:
The XMP rom didn't fix it, so I guess you're right. Would a flex cable (those are the flat orange ones right?) be expensive?
Click to expand...
Click to collapse
I hope you fix it
This is the cable we are having a problem with, i have given my mobile for replacing this stuff as i couldnt get this locally. This board houses the LCD and the digitizer and the buttons connect to this. The black cable goes to the motherboard. Its pretty simple to take apart the phone, but take care while doing so. Another thing its that, when you are opening the display panel, its better to use a guitar pick instead of a screwdriver and open it at the latches, that would avoid damage to the outer plastics.
http://www.ebay.co.uk/itm/BRAND-NEW...K_Replacement_Parts_Tools&hash=item3f0ddd12f3
Last week i flashed my Vibrant to 4.0.3 and i found some times i can't use half left vibrant's screen, but when i turn off screen and turn on i used ok. Then i tried another ics 4.0 custom but this problem happened again. But when i used stock rom or 2.x.x mod my vibrant is ok. Can you help me what happen with my vibrant.
I'm sorry because i'm not good at english
Siri.nguyen said:
Last week i flashed my Vibrant to 4.0.3 and i found some times i can't use half left vibrant's screen, but when i turn off screen and turn on i used ok. Then i tried another ics 4.0 custom but this problem happened again. But when i used stock rom or 2.x.x mod my vibrant is ok. Can you help me what happen with my vibrant.
I'm sorry because i'm not good at english
Click to expand...
Click to collapse
Just to be clear, do you mean that your phone doesn't register your fingers touching the screen on the left side of the phone sometimes?
I would suggest downloading the free app "Touch Test" which shows a grid that not only shows where you are touching, but the path of your slides across the screen. If the phone begins to act up again, you can open the act and see if and where the screen is cutting out in the grid. Aside from that, it might simply be that you need a replacement and its coincidental that it was acting up along side you running a 4.0 rom.
Xenoism said:
Just to be clear, do you mean that your phone doesn't register your fingers touching the screen on the left side of the phone sometimes?
I would suggest downloading the free app "Touch Test" which shows a grid that not only shows where you are touching, but the path of your slides across the screen. If the phone begins to act up again, you can open the act and see if and where the screen is cutting out in the grid. Aside from that, it might simply be that you need a replacement and its coincidental that it was acting up along side you running a 4.0 rom.
Click to expand...
Click to collapse
Ok i have tried touch test. I found when i sliced from the left to right, i saw the line appeared from the middle of screen, but when i sliced form the right to the left, the line appeared all screen? But it's not happen usualy. Just 10 to 15 second. May some hardware problem
Siri.nguyen said:
Ok i have tried touch test. I found when i sliced from the left to right, i saw the line appeared from the middle of screen, but when i sliced form the right to the left, the line appeared all screen? But it's not happen usualy. Just 10 to 15 second. May some hardware problem
Click to expand...
Click to collapse
That is the oddest thing I have ever heard lol
It really might be a hardware issue man...I can't think of how it could be the rom. I mean, sure you might occasionally
have an unresponsive touchscreen....but only half the screen working?? That's just weird Oo I'll keep looking around for answers though man
but thus far I've found very little.
Good luck
Xenoism said:
That is the oddest thing I have ever heard lol
It really might be a hardware issue man...I can't think of how it could be the rom. I mean, sure you might occasionally
have an unresponsive touchscreen....but only half the screen working?? That's just weird Oo I'll keep looking around for answers though man
but thus far I've found very little.
Good luck
Click to expand...
Click to collapse
Ok! Thanks you so much. I will make a short video when it happen again.
Siri.nguyen said:
Ok! Thanks you so much. I will make a short video when it happen again.
Click to expand...
Click to collapse
I have a video but i'm new member i can't send link to my post. I will sent to your inbox. tk
Okay, so that anyone else that happens to come to this thread is on board, here is the video that shows his problem:
http://www.youtube.com/watch?v=5xDolJhmDog&feature=youtu.be
As you can see in the app, if the origin of the trail is on the right side of his screen, the swipe is recognized across over to the left without problem...if however the origin is on the left side of the screen, no touch is recognized until he reached the middle of the screen, at which point it becomes recognized.
I am still looking around for a similar problem, but thus far have few ideas. Typically, the screen either is totally unresponsive or momentarily unresponsive...never half and half, and especially with such weird rules. By this, I mean that obviously the left side of the device is capable of recognizing touches, since if he begins at the right side, it does just fine....the only problem is if he originally touches the left side, then it doesn't recognize it.
My guess: it could be a kernel issue.
I would try the following:
Pull battery and reboot. Take out any external SD card.
Back up what important apps or data you have and try a factory reset.
You can also try some the options below:
1. Reflashing the kernel.
2. Try a different kernel if available.
3. Factory reset and full wipe and flash a different ics or cm9 rom to see it the problem persist. You can try to isolate the issue to hardware or firmware.
4. Full reset and flash back to complete stock to see if the problem persists. If you are fully reseted and back on stock eclair or froyo and the problem persists, you may have to open up the device to check all the connections.
sometimes a bad battery may also creates some problems
Now i'm using xerxes custom 2.3.6 gingerbread. It's ok but i don't know why when i use ics. I can use half left screen
Sent from my SGH-T959 using xda premium
HI, since I've always had issues (from stock rom up) with hw capacitive buttons (home/back/search/menu), I would like to disable them, maybe my Folio is faulty on them (randomly the back button fires by itself, even if the tablet was left alone on the table).
So I ask Artem or anybody who knows it: I can build from sources, what is the minimal diff I can make to the sources? Is it sufficent to comment out line 'CONFIG_KEYBOARD_FOLIOCAP=y' in tegra_betelgeuse_android_defconfig?
Thank you.
piergi65 said:
HI, since I've always had issues (from stock rom up) with hw capacitive buttons (home/back/search/menu), I would like to disable them, maybe my Folio is faulty on them (randomly the back button fires by itself, even if the tablet was left alone on the table).
So I ask Artem or anybody who knows it: I can build from sources, what is the minimal diff I can make to the sources? Is it sufficent to comment out line 'CONFIG_KEYBOARD_FOLIOCAP=y' in tegra_betelgeuse_android_defconfig?
Thank you.
Click to expand...
Click to collapse
nice question . some times i have the same problem.
+1
Sent from my folio100 using xda app-developers app
raptor92 said:
+1
Sent from my folio100 using xda app-developers app
Click to expand...
Click to collapse
may be its a bug....
when this happens to me, i click one time on power buttom and than wake it up again. but this isnt the fix solution for the problem, just solves it temporarely
ans solution?
one "solution"
Hello, posting for the first time =)
Anyway, i've had a problem with folios crazy buttons and screen response since day one.
Nothing really changed for me with rom updates and different apps. I have tried it all...
I had enough and finally unplugged that little cable that connects into circuitboard
of those buttons and power-led. This is really no solution but takes care of that problem =)
It also disables power indicator led, so that's a little inconvenience =/. But since unplugged,
touchscreen started to work in every way better like its more responsive and doesn't "freeze" anymore.
But this requires you to disassemble your folio to get to touch with the cable to the circuitboard.
Removing plastic back cover isn't enough, but you Dont have to detache the screen from faceplate.
I'll plug it back on when there's a software fix for buttons behavior. Meanwhile enjoying peace from
button madness =D. Sorry if poor english, i'm Finnish
Justuz said:
But since unplugged,
touchscreen started to work in every way better like its more responsive and doesn't "freeze" anymore.
Click to expand...
Click to collapse
After disassemble screen seems to work, but after some time is starts again and I don't have "crazy" buttons though.
I'm using mouse and keyboard and it's comfortable.
Hi,
I'm just posting a new thread to see if this has happened to anyone else.
After upgrading the firmware, the touchscreen is not responding sometimes. It's very strange. Even on the unlock screen... I need to use the keyboard to unlock it.
And then suddenly it would work. Then become unresponsive again.
I've tried:
1. Power down and on
2. Hard reset
3. Cold boot
4. Hard reset x 3 without any account login
It keeps on acting up like this, occasionally just getting stuck on the home screen, and I can't open the config, or move the screen.
Anyone else have this problem after the firmware update?
Thanks
Fortunately no but I got random reboots with JB installed on my side.
With ICS everything is stable.
You should check out a screen test app to make sure the digitizer is not failing!
Sent from my Transformer Prime TF201 using xda premium
asuser said:
Hi,
I'm just posting a new thread to see if this has happened to anyone else.
After upgrading the firmware, the touchscreen is not responding sometimes. It's very strange. Even on the unlock screen... I need to use the keyboard to unlock it.
And then suddenly it would work. Then become unresponsive again.
I've tried:
1. Power down and on
2. Hard reset
3. Cold boot
4. Hard reset x 3 without any account login
It keeps on acting up like this, occasionally just getting stuck on the home screen, and I can't open the config, or move the screen.
Anyone else have this problem after the firmware update?
Thanks
Click to expand...
Click to collapse
Sorry to hear you have issue - but wanted to say - I am running stock (updated OTA + hard reset) and all is wonderful.
you might need to RMA (sorry)
pooblej said:
Sorry to hear you have issue - but wanted to say - I am running stock (updated OTA + hard reset) and all is wonderful.
you might need to RMA (sorry)
Click to expand...
Click to collapse
Thanks for the replies.
It looks as though this only happens when I have the keyboard plugged in! Strange. Wonder if it's affecting the digitizer somehow, as that part of it above the port has bent and cracked a bit. Never dropped it and always careful when plugging it in.
asuser said:
Thanks for the replies.
It looks as though this only happens when I have the keyboard plugged in! Strange. Wonder if it's affecting the digitizer somehow, as that part of it above the port has bent and cracked a bit. Never dropped it and always careful when plugging it in.
Click to expand...
Click to collapse
When you say this only happens when the keyboard is plugged in is the keyboard connected to the power supply the same time? If it is this sound like an earth problem.
flumpster said:
When you say tha only happens when the keyboard is plugged in is the keyboard connected to the power supply the same time? If it is this sound like an earth problem.
Click to expand...
Click to collapse
No I have it on without plugging it in.. I havent tried it plugged in.
Now this backspace key is giving me problems. Never had the problem before but ehen I type quickly or use the backspace key sometimes it exits out of the keyboard or shoots the cursor up a couple ofparagraphs. So strange. Maybe there is something wrong with the digitizer. Looks like this is going to ASUS for a third RMA...