[Q] No optical button working - HTC One S

Hi everybody! Hope someone can help me with this little problem.
A month ago I had a problem with the vibration on my One S, the engine was broken, so my uncle decided to change it by himself (the phone was bought via aliexpress). Then, there was a problem with the screen and he also changed it. At that moment the phone had CyanogenMod 11 installed.
The problem is that after reparing it, and when I change to a sense based rom, the optical keys for home, back and multitask aren't working, whereas those keys do work when I'm on TWRP or in CM 11.
Does anybody knows what may happen?

Related

D-pad not working properly on RAPH

I have spent hours searching to see if someone else has had this problem and haven't been able to find anything.
My lower D-pad and its buttons/touch panel have stopped working properly. The touch part of it doesn't work at all and the buttons have reduced functionality. Only the up/down and the home buttons work. From what I can tell this was after flashing Tael's latest Sense2.5 ROM.
I have reset the phone back to standard, using an original HTC Rom, going back to standard SPL, and standard radio. This has not fixed the problem.
The only thing I can find that seems to be related, is when I go into the bootloader there is a line that says "PSOD-wrong platform". I'm guessing that a code somewhere has changed somehow telling the phone that it doesn't have a touchpad, possibly because the phone the ROM was ported from didn't have the touchpad. It might be a longshot but that is my best guess.
I have no idea how else to troubleshoot this and any help would be great.
Thanks in advance.
Craig

Touch screen problem on Motorola Defy

Hello, I have recently discovered a very annoying problem with the touchscreen on my Motorola Defy:
I have noticed that the touch screen acts strange sometimes, so I have installed a touch test application(Touchtest by Hermit). In this application I have noticed that if I touch the screen in two different points in a fast succession, a line appears between these two dots. This makes a lot of application that require multitouch pretty much useless, because I have to restart the application to have the touch screen working again.
Is there any solution for this? I have heard that this may be a software issue, so I have e-mailed Motorola, but they have not answered yet.
I have attached two pictures to illustrate what I am saying, one taken before this strange error, and one after pressing on two spots very fast. You can see the line connecting the dots in the second picture. I can make a video if you still can't figure out what I am saying.
Thank you.
Im having a very similar problem here on my defy. When I play games on psx4droid and when I keep pressing x key, it stops working for a while then I have to release the button and when I press it again, it stops working and it continues
I encounter similar problems with my Defy.
When for instance using slide to unlock , 1 / 5 sildes fails. I have to slide 2 - 3 times until it unlock.
It also scrolls very slow in applications and the same thing happens when typing a message.
Solution : Unse lock button.
It currently runs Pays ROM, but the situation appeared since I installed 2.2.1.
I don't remember having this problems on 2.1.
Don't know if the situation is only related to software but it is really annoying.
Found this info regarding touchscreen slowness, but I am using the original charger so it doesn't apply for me.
Motorola Defy Touchscreen Problem
I recently got my Motorola Defy,my Defy's touchscreen acts sometimes really weird, on keyboard it's hard to enter 'r' or 'b' and some other characters, it takes little while to unlock the phone, it automatically opens applications, I don't know if it's due to faulty handset or software, I am considering it returning to Phone4U and get a replacement handset.
What version of Android are you using ?
Same problems here, but I think it is a software issue.
I'm having the same problem on my Defy.
After a while, the multi touch stops. I posted on the Motorola Forums
https://supportforums.motorola.com/thread/44733
but no response.
I used YAMTT and when having two touches, after 20 seconds, one of them disappears
This is repeatable
2.51.1 UK with 2.1 Android
Well, it is clear that this is a problem that affects many Motorola Defy users. But I wonder if someone could fix this thing?
Looks like the new software version 2.51.1 did not fix this bug. I haven't tried it yet, but I see some of you have.
So it looks like our only solution could be a developer from XDA. Could someone help please?
This is ridiculous...i've sent my phone to motorola only because it was giving this problem and basically what i think is that their own software is causing this problem so i'll be waiting for 3 weeks and when i get my defy...it'll still have that problem...Ridiculous...
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
efpob said:
I did a bit more experimenting.
I flashed the 2.2 Finnish blur, multitouch still disappears after 20 seconds using the touch testing programs
I also booted into Safe Mode (vol up + vol down during boot)
The same problem persists; I was using gallery image zoom to test.
However, I got my friend who has a Motorola Droid to install YAMTT. The multitouch lasted about 30-40 seconds. Not sure what to make of that. He's running some version of Cyanogen Mod on Android 2.3
Click to expand...
Click to collapse
Defy doesn't support cynogen mod and 2.3
I was messing around today and even the single touch disappears after a while
30 seconds or so
Mine sometime stop response after few seconds
really wierd
Tell me who is on stock rom and is having problem..because im on 2.2 leaked..so i cant really say if u hv this problem on 2.1...
I got this response from a Motorola employee. Anyone know of a way around this?
Motorola Employee said:
If you touch the screen and don't move for a long time, the screen will eventually try to ignore that touch as it'll be considered invaild. That's what you're seeing. If you continue to move your finger(s), touch will continue to work. Also, when you release the screen, it acts to clear the invalid touch region that you generated earlier.
Click to expand...
Click to collapse
https://supportforums.motorola.com/thread/44733
have simular problems............100 procent hardware problem..... if i twist phone a little it will go back to normal for a while
any ideas for disable it?changing some parameter or something?
I have the same problem. screen sometimes go crazy. i am using stockrom eclair SEA 2.59. sometimes it seems that it tap icons or part of the screen even without I actually tap on something. and it seems it affect the capacitive button under the screen. I am not touching the search button but the search box suddenly appear.
I have to push the power button and unlock the screen to make it normal.
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
brjshshrma said:
somebody please help us. I am also having this weird problem. Touchscreen gets pressed itself not everytime but it happens very frequently. Tried everything, hard reseted too.
At least I gotta hope that its not a hardware problem as many of u are also facing this problem. Any body please confirm if flashing cm7 has helped u or any other solution.
Click to expand...
Click to collapse
i returned my defy months ago but what you can do is, try to flash cyanogenmod on your defy...that should fix the problem.
Hi, I've registered myself just a minute ago, reading the link that efpod left here and I've remembered that I charged my Defy with a Galaxy S i9000 charger friday (I've charged it once the batery was drained later with my original charger) and today it is failing A LOT, it's really anoying.
I got Cyanogen Mod (latest) installed on my phone so that doesn't fix the problem.
I'm uncharging it with "StabilityTest - CPU / GPU Test" and when the battery drains out I'm gonna charge it with the original one, after that, I'll test it during the day and I'll leave a messege to keep you informed.

[Q] Capacitive buttons dead after first screen off CM11 M10 an later

I've the issue that with some nightlys between CM11 M9 am M10 my One S has got issues with the capacitive buttons. After the first screen off they completly stop working. No light and no reaction. If I prevent the screen from turning of all is fine.
I'm currently running M9 with Bubba kernel, but as Bubba isn't working for me with the new nightlys or milestone releases, I'm currently stucked at the M9 impossible to update.
I've tried M10, M11 and some nightlys between without success. The One S is S-OFF but I've also flashed the included boot.img in fastboot without no help. Even a clean system/data wiped installation immediately reveals this issue after the first screen off.
Does someone else have this problem or know possible fixes I can try?
I've encountered the same problem. There used to be somewhere in settings where you can turn capacitive buttons on and off. I've previously set my capacitive buttons off, but after an update, the onscreen nav buttons aren't showing after the screen turns off, and the capacitive buttons remained at their disabled setting.
I need to figure out how to turn capacitive buttons back on at least.
I think I've got a kind of insane hardware issue with my ville.
Tried CM12 yesterday with the same behavior. Then decided to do an RUU and tested in the original HTC Sense rom.
And I've still got the same issue in the original rom.
Now only my CM11 M9 backup with the Bubba kernel is working for me.
As I also noticed some screen burn-in from Google Maps on the AMOLED I think the time for a new mobile has come.

Capacitive Buttons Problems: pls HELP!!

Hi All,
The capacitive buttons of my OPO suddenly stopped working. My phone didn't drop and has no physical damage. I tried an hard reset by flashing CM11s (from COS 12) via unlocking bootloader and executing the right commands in Fastboot mode, but the problem still persists.
I switched to screen buttons, but I prefer the physical buttons for my usage.
My phone is 9 month old and It's very strange that an hardware problems materialize in this way (no new app installed when the problem arose).
Has anyone experience the same problem or someone know how to fix it?
Thanks in advance for help
F

[Q] [PROBLEM] (Broken Digitizer) + Touchscreen TWRP

Hi guys,
I currently have to use my SPen to navigate my phone because my touch screen doesn't work.
Using TWRP is one of the biggest headaches in the world if you use an SPen to navigate because it's super sensitive and anything you hover your SPen over, will automatically open up and it happens in a blink of an eye.
I remember older versions of TWRP had a way to operate the phone via hardware keys (Volume Up and Down and Power).
I am not able to find much information about this anywhere online, I need this phone to last for another 2 months before I can replace it with something better.
Anyone have any idea how to get this version of TWRP without compromising having firmware issues by using something that is not meant for the Sprint Note 5?

Categories

Resources