I have a problem that in my mobile Recents Buttons is being pressed automtically i dont know what is the issue. is it ROM related issue or Hardware. Is anybody facede such issue. Please Help me
99percent of times its problem with touch, does it happen more aggressively when on charge? or it could be problem with your unclean wet hands, screen, screen protector, etc. but i think its hardware probably you need to change usb flex.
Related
Hello, I have had this TYTN I for a long time without any major problems. It was originally with WM5 but then I upgraded to WM6. Lately I had a strange problem whereby the front buttons stop responding intermittently.
The below mentioned buttons stop working:
1. The Internet Explorer button.(Above on the right)
2. The Message button.(Above on the left)
3. The Call buttons. (The call picking and disconnecting button, below left and right) And the 4 keys along it.
During this time I have to resort to the pointer or the side wheel to use the phone, which is very frustrating.
If I press the reset button at the bottom, the keys work again for a few times, then stop to respond again.
I have tried to flash again with both WM5 and WM6 but did not help. I have opened the phone and reseated all connectors but did not help either. Do you think I should try replacing the ribbon cable?
I have searched the forum and found several threads with the same problem, but never a solution.
Your help is much appreciated. Thanks.
I have been struggling the last few months with the same exact problem. Sometimes the buttons work other times they don't, and in the last couple of weeks the frequency of button failure has increased (every couple of minutes).
I found a few users yesterday over on the HTC forum who were having the same problem and 1 user who actually reported a fix that worked for him.
Go to Start/Settings/System/Key Lock and select "Do Not Lock Buttons". Exit Key Lock and soft reset your device. You may know return to the Key Lock options and re-select your choice (I used "Lock all buttons except Power button").
Worked for the HTC user and is working for me as I have had no button failure now in the last 24-hours with repeated use of the device.
I hope this works for you because if you are like me I getting very close to trashing the unit.
Hi,
the problem could be the Xilinx chip (a BGA chip) on the pcb underneath the buttons.
As the buttons are pressed the board is flexed and some of the solder pads under the xilinx chip must have become detached from the xilinx chip itself.
I had the white screen problem. An while i got the white screen the front buttons where not working too.
In the whte screen threat i found that it could be the Xilinx chip, and figured out when pressing on this chip the white screen was gone and the buttons where working.
So i resoldered (refloated) the chip with a heatgun and some liquid flux last Sunday and since then i had no problems anymore.
I would suggest disassembling the phone down to the pcb and try starting it on with the ribboncables connected while keep some pressure on the Xilinx chip. And then trying the buttons if they work.
See
http://forum.xda-developers.com/showpost.php?p=2382665&postcount=134
in
http://forum.xda-developers.com/showthread.php?t=321163&page=14
Greets
jtf
I have the same problem with the same phone. The instructions above for "key lock" didn't fix it for me. I was assuming that it was hardware; but I just tried installing the Android port for this phone and under Android the buttons work fine.
I know that Android has some good stuff going for it, but I don't think it's awesome enough to circumvent a bad circuit... How exactly do these buttons work? Is there a process that should be running to handle them? Any other pointers?
Any one else had issues with the centre windows button not working?
I'm not sure if it's hardware as in the button is actually not working or more of a software freeze. An example would be on the home screen pressing the windows button and literally nothing happens. touching start in the top left however works everytime.
A simple power on/off of the device solves the issue but its been happening a few times this week and is becoming annoying.
The more apps and tweaks I do to my phone, the more unstable it seems to get. Has anyone else noticed this? Just little things, like for example a few times my lock screen with "password" has reverted to windows classic style but then a screen off / screen on will bring it back again to the WM6.5 lock screen with slider.
Just overall slightly odd behaviour.
I may have recently installed something that the device doesn't like too much, but if so I am unsure what software it is. I'm tempted to save all patches I have, and write down the adjustments I've done and perform a hard reset, the phone definitely was not like this when I got it only 2 weeks ago.
I wonder if anyone else has had anything similar or if its just my phone?
Seems like a hard reset is required. My o/s seems very stable, the only problem I have in that regard is the odd freezing of the messaging app.
It just happened to me after reading this post :-O
another hardware failure case...good job HTC...
dgtel2 said:
another hardware failure case...good job HTC...
Click to expand...
Click to collapse
Elmo-85 said:
A simple power on/off of the device solves the issue
Click to expand...
Click to collapse
@dgtel2
Could you please explain how this "hardware failure" is temporarily fixed by a reset?
Another "reading failure", and simply blame HTC. Good job dgtel2.
When we reset, we need to hold the "call-off" button. That's not a good design due to excessive pressure to the edge of the "capacitive" screen. They should have introduced separate turn-off button. Over time, the buttons/screen will get affected (but for new unit, it's pretty unlikely...).
So, to reset using the red reset button, it is located underneath the "so-hard-to-open" back cover. Over time, again, will affect the capacitive screen.
But, the problem could be due to both hardware and software issue. Just send it back to the vendor. Less headache...
Yeh its definitely not a hardware fault. Its more like a freeze or slight confusion between WM6.5 and sense somewhere along the line....
I've thought of another thing which would also come under this weird behaviour category.
I noticed today whilst watching a video on the youtube app, using the up and down volume buttons on the side of the device would make the video freeze for abpproximately 1 second each time the button was pressed, it would change the volume up or down, but the bar would not appear on the screen so you have no idea what the level of volume actually is.
again soft reset solved this, but its just another on of those weird things
Back up and hard reset all the way.
dgtel2 said:
When we reset, we need to hold the "call-off" button. That's not a good design due to excessive pressure to the edge of the "capacitive" screen.
Click to expand...
Click to collapse
Don't use excessive pressure.
Why the "" round capacitive?
just a "make-up" ...lol ... again...those "..."
at first i want to tell djsteve my congratulations for his streakdroid 1.9.0 rom. i think it's really amazing. unfortunately now i've got a problem with the touchscreen. when i awake the phone from the standby, sometimes the screen doesn't answer to my touch. the physical buttons work, but the touchscreen is dead. it turns on, but when i touch it nothing happens. is it a problem of the rom or it phone's fault. the only way to solve the problem is to pull the battery out and restart the phone. i hope someone can help me thanks to everybody will answer my request.
I'm having the same issue with the screen becoming unresponsive during or after a call. Pulling the battery is the only known fix
I had the same problem when listening to music with the phone in my pocket. Apparently its a known fault with the phone. Something about static causing the screen to heat up and therefore making it unresponsive. My work around was to put my phone in my pocket with the screen facing outwards, instead of inwards, think the heat from my leg and the static from pocket movement froze the screen. It doesn't do it anymore, with the screen facing outwards.
asusgarb said:
at first i want to tell djsteve my congratulations for his streakdroid 1.9.0 rom. i think it's really amazing. unfortunately now i've got a problem with the touchscreen. when i awake the phone from the standby, sometimes the screen doesn't answer to my touch. the physical buttons work, but the touchscreen is dead. it turns on, but when i touch it nothing happens. is it a problem of the rom or it phone's fault. the only way to solve the problem is to pull the battery out and restart the phone. i hope someone can help me thanks to everybody will answer my request.
Click to expand...
Click to collapse
I have noticed this as well, however I just updated to the 351 rom so it's not a streakdroid problem. I think it might have something to do with AndroidAssistant app I just installed.
Recalibrate
To fix this issue usually all you need to do is recalibrate the screen by holding vol up,vol down and the power button while the phone is off and then when the text on the screen appears select screen calibration and follow the instructions after it says successful calibration wait for the menu to comeback up and scroll down to power off(you may need to select it more than once) . This problem is caused by the screen being affected by heat and sometimes after updating the screen needs to be re-calibrated so it wont be affected.
ajairola said:
To fix this issue usually all you need to do is recalibrate the screen by holding vol up,vol down and the power button while the phone is off and then when the text on the screen appears select screen calibration and follow the instructions after it says successful calibration wait for the menu to comeback up and scroll down to power off(you may need to select it more than once) . This problem is caused by the screen being affected by heat and sometimes after updating the screen needs to be re-calibrated so it wont be affected.
Click to expand...
Click to collapse
Thanks for sharing that
Do calibration!!!
ajairola said:
To fix this issue usually all you need to do is recalibrate the screen by holding vol up,vol down and the power button while the phone is off and then when the text on the screen appears select screen calibration and follow the instructions after it says successful calibration wait for the menu to comeback up and scroll down to power off(you may need to select it more than once) . This problem is caused by the screen being affected by heat and sometimes after updating the screen needs to be re-calibrated so it wont be affected.
Click to expand...
Click to collapse
worked great on my streak never had a problem again!
Hey there,
I've a big issue for a few months already.
My S4 jflte always wakes up whenever the screen turns off.
I tried to figure out where it's caused by and when I cut off the soft buttons (home/menu/back) and started the phone, the screen didn't wake up anymore.
As far as I know there is no way to repair this w/o damaging the screen itself.
So could I block the buttons from waking up the screen?
As you can see when a app is opened and the screen turns off automatically and turns on again, the home screen appears and puts the app in the background.
youtube(.)com/watch?v=Bhul9UMJ8l4 (I don't have 10 posts yet so I have to post it this way. Sorry)
Could anyone help me? I've been researching for a long time and found no solution.
Says video not found.
Are you on a stock rom?
The Video is working fine for me. Did you copy the whole link and did you remove the brackets? ( )
I'm on AOSP 6.0.1 Kernel 3.4.110-Alucard-PWR-CORE from JDCTeam.
I tried different ROMs so far (including the Stock) and it's definitely a hardware issue.
http://www.youtube.com/watch?v=Bhul9UMJ8l4
have you been doing full wipes inbetween roms ? if you have then maybe it's a hardware issue.
Yes, I've always done full wipes. I'm pretty sure it's a hardware issue. Is there any way to block the keys from waking up the phone? I usually use the power button anyways to wake up the phone.
You can probably disable the keys altogether. Or maybe just the menu and back key, and leave only the home button functional.
There is no way to do it with that rom yet, but you could use Xposed and Gravity Box.
Most apps nowadays offer inbuilt menu and back options anyway.
Before you try to disconnect any buttons, try to clean the phone. That has solved many problems in the past.
Look for disassemble S4 videos on youtube, and for cleaning use a small paintbrush, or a very soft toothbrush, and Isoprophyl Alcohol(70% clean alcohol, 30% pure water), you can buy that in the Apotheke.
Clean the board an all other reachable electronics. Let it dry, reassemble and see if it helped.
Thanks for the tips, but I've already done that before (twice) without success.
I'm looking for a way to disable the keys from waking up the screen. I've tried it with the key configuration files in the system, but it didn't work.
Example: When I press the home button the screen wakes up. I just want to disable the wake up for all buttons except for the power button.
Does anyone know a app for this? Or a mod for xposed?
There is no actual "wake up" function assigned to the back and menu key. Only the home button has one. So there's nothing you can disable, except for the keys altogether. I already suggested you how to do that in the 5th reply to this thread.
I've found a work-around. I disabled the keys with 'Xposed Additions' while the screen is turned off or locked.
Thanks alot for your help guys!
Some basic info before i begin:
Phone: Moto X Style/Pure on android 5.1.1 (XT1572)
It is rooted, but no custom roms are installed.
So basically what happened was I dropped by phone, then all of a sudden the on screen (Home, Back and Multitasking) buttons started to become unresponsive and started ghosting. I have restarted so many times just to exit an app. After several restarts, my on screen (home, back and multitask) buttons have stopped working.
Firstly my basic and short term solution was to install a 3rd party on screen button app from the play store, this would put a second set of on screen buttons above the stock on screen buttons. But before this I noticed that the on screen buttons actually worked when rotated so that instead of being on the bottom of the screen they would be on top. The on screen buttons also work when i boot into recovery mode, my custom recovery is TWRP. I also wiped dalvik cache and reinstalled my apps through the recovery setup.
I dont know whats going on, I even made it so that when my on screen buttons moved to the top of the screen, i would click on apps from the bottom of the screen and it would work. It doesnt seem to be a hardware issue as i have confirmed it to be working through TWRP and tapping on apps from the bottom of the screen, confirming that my touch screen is working perfectly. The on screen buttons also work and it being detected when TalkBack is enabled.
Help me plez.
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
valest said:
Common hardware problem, use developer option to see your input and tap, if it brake when on nav bar, then IT IS HARDWARE PROBLEM.
Click to expand...
Click to collapse
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Houndz said:
Hi, I enabled Show Touches in my Developer Options and when I put my finger on the actual nav bar, the pointer stops just above it.
Idk if its a hardware problem, but i did drop it. And it still works in TWRP and TalkBack enabled.
Click to expand...
Click to collapse
The touch screen issue of this device is hardware related, born with such flaw, you will have it even you didn't drop it.
No sure how it happened, but it helps if you can take it apart and clean the connector a bit and make sure you reconnect it firmly, if that doesn't work, you will have to replace the touch screen part or the whole screen and touch screen and rear frame and stuff, but do notice: it's likely to happen again.
https://forum.xda-developers.com/moto-x-style/help/solved-navbar-responding-t3993049