Hi
I have problems sometimes with touch buttons, back and menu buttons are usually put off and stop responding, I must restart the phone for it to work again. Anyone else having that problem? i rooted and flashed the phone but the problem is stil there
falluja said:
Hi
I have problems sometimes with touch buttons, back and menu buttons are usually put off and stop responding, I must restart the phone for it to work again. Anyone else having that problem? i rooted and flashed the phone but the problem is stil there
Click to expand...
Click to collapse
...and screen can only be used with the pen? This is a problem i have.
Just switching ist off and on fixes the problem (i have not to reboot).
Seems to be a software problem.
No the screen works well its only the buttons
Absolutely no problems to report with mine???
Yes I am having this same problem as the poster described (back and menu buttons switch off)
Specifically happens after a phone call
Happens to my brothers phone as well and both phones are sourced from different suppliers
Think a software update may fix this? or should i send it back and buy another one?
Thanks
Pretty widespread problem it seems:
http://forum.xda-developers.com/showthread.php?t=1356115
I tend to believe it's software-based though
Related
This is my first post and I must say that this is a great group of people who know what they are talking about!
Anyways, I have had my 8525 for about two weeks and I am loving it. For whatever reason some of my buttons do not work! The dpad works but the two soft buttons, the start button, ok button, email, PIE, and the green and red buttons don't work. The power, scroller, comm manager, the left ok button and the PTT all DO work. I did a hard reset hoping that would fix it but no luck. I been installing and trying a lot of programs but I thought after the hard reset that any program that screwed this up would be gone. Please help I love this phone and really don't want to take it back.
Thanks,
Dan
I took it back and that solved all of my problems.
you took back , what?
i am having the same issue with a HTC Tytn.
terracot said:
i am having the same issue with a HTC Tytn.
Click to expand...
Click to collapse
My hermes has a similar problem, buttons under the screen sometimes won't work, but if I turn off backlight and turn on, it works... but not very well because if I press green button then red button continually, buttons don't work again after few pressions....
I have changed my ROM but it's the same, it isn't a hardware problem because if I turn the scroll it works again...
This problem is known?
Thank you very muche for your help and sorry for my bad english.
same issue with my TyTN...
Same issue here with Tytn, buttons won't work but if I use scroll button a bit then buttons work again.
Hey guys,
Exactly the same problem here and it's infuriating when I'm trying to make calls on the run and sometimes I can't even pick up calls.
I have an I-mate Jasjam ROM 1.31.305.2.
If anyone has any fixes or solutions that would be great. Or do I have to send it in for repair or something?
So has anyone managed to fix this? Anyone tried a hard reset?
I have no idea how to diagnose the issue and even whether it's a software or hardware fault.
Jasjam- Same here
Also my screen turnes white some times
mattytj said:
So has anyone managed to fix this? Anyone tried a hard reset?
I have no idea how to diagnose the issue and even whether it's a software or hardware fault.
Click to expand...
Click to collapse
I'm also having these problems with the front buttons not working. Very frustrating. The problems seem to be platform independent.
I really cannot believe this. When I used the search function I noticed so many people are having these problems with the TyTN, and no resolve.
It's my second machine I received from HTC, first one also had these problems.
HTC sucks BIGTIME.
so I just noticed the lights for my hardware buttons are stuck on, happens from the moment the phone turns on, and nothing changes it (though they seem to dim slightly) I've tried reflashing the phone (using mdj cyanogen 2.7, nand with magldr 1.12)
I tried searching and havent seen anything like this. Only thing I can think is maybe it got a little wet(?) while I was recording video during a snow storm here, but nothing else seemed wrong, just got home and noticed it. Any ideas?
I have the exact same problem. I've flashed back to the original windows mobile rom and the problem is still there! I've searched and yet to find the solution. Anyone got any ideas?
Check to see if you have a voicemail - you may have read it but closed VM before listening to all the message, it can on occasions do this - it I'm right just ring your phone leave a fresh VM then go into VM and listen to the whole message
Thanks for the reply, but no dice on this one. I tried the voicemail thing and I have no voicemails.
To clarify it's the bottom 5 buttons (call, home, windows, back and power) that are constantly lit up. Even when the phone goes on standby those buttons stay lit. I'm looking to see if there's an app that can just shut them off.
I got the same problem. My hd2 got some water on it and the problem started. The hardware keys now getting dim but not getting completely off. There is no other problem
Please help.
same problem on my father htc click
Ok guys try the bottom of post 4 here:
http://forum.xda-developers.com/showthread.php?t=926507
I use that rom (the 1.7) version and the fix works
johnerz said:
Ok guys try the bottom of post 4 here:
http://forum.xda-developers.com/showthread.php?t=926507
I use that rom (the 1.7) version and the fix works
Click to expand...
Click to collapse
Thanks, I will try the rom.
But do u really think its a rom problem ? The keys light were working fine before the water hazard in the same existing rom. Besides the problem is also there when u are in the boot menu of MAGLDR or Clockwork menu.
any updates from anyone? On miy HD2 the vol up, start, back & end call key don't respond to any presses but seem to be active. Calls will randomly end, vol up acts as if the button is kept pressed!
Help!
Hi guys,
A little bump in this thread, but is there already found a solution for this problem?
After a hard reset and replacing the digitizer of my htc HD2, the buttonlights remain on. Even when the phone gets in standby mode.
I'm using cyanogenmod 7. (bought it like this. Didn't put android on it myself)
After the hard reset and digitizer replacement there also came another problem.
When pushing the windows logo (key 158) the volume up button also reacts (key 115). Thesame problem occurs when pushing the dial button. With that key (231), key 114 (volume down) reacts.
So when i want to open a menu or make a call the volume goes up or down.
Do you guys think I screwed something up when replacing my digitizer or is it just an software issue caused by the hard reset?
All right guys, it was an hardware failure.
I reopened my htc and checked all the connectors and (re)placed some of the yellow tape. After the reassembly, my phone just works as it should. All problems are solved.
My HTC HD2 also got the keys stuck after only a week of use. T-Mobile is sending me a replacement phone today.
Is this a common problem? I'm afraid it may happen again.
Hey guys I'm having same issue. Going to try opening up and check connectors.
Hello! Just bought an Optimus 7! Really good phone for the price!
But i got one problem! When im going to turn on the phone with the windows button its sometimes not responding!
Somebody else got this problem?
Yes. Happens to me all the time, but I always use the power button to turn on the screen so it doesn't bother me that much...
Sounds like a known issue.
techno-update said:
Sounds like a known issue.
Click to expand...
Click to collapse
Same here. It must be a software bug because the button is always working when the phone is unlocked.
If you still hold for a while it works
One reason for the screen not turning on is that you may be blocking the proximity sensor at the top left of the phone. The reason behind that is probably to avoid turning on the screen when the phone is e.g. in a pocket.
for me the start button for screen unlock always works, but many times screen is unlocked and all black, the systems listen to the touch input but doesnt show nothing at all....it happens very often usually when the phone is hot...
On some rare occasion, when I turn on my phone the touch screen works and it let me unlock the phone but every time I get into the home screen the touch screen stops working. When I press the home screen the home button the touch screen works again. Then I turn the phone off and on again same thing happen. Restart and it works back normally. Is this a software issue with kitkat or is this a hardware problem? I am on stock rom. I hope someone know the answer to this weirdness or maybe I don't know something. Thanks.
hfl12 said:
On some rare occasion, when I turn on my phone the touch screen works and it let me unlock the phone but every time I get into the home screen the touch screen stops working. When I press the home screen the home button the touch screen works again. Then I turn the phone off and on again same thing happen. Restart and it works back normally. Is this a software issue with kitkat or is this a hardware problem? I am on stock rom. I hope someone know the answer to this weirdness or maybe I don't know something. Thanks.
Click to expand...
Click to collapse
i get the same thing once in awhile. ever since KitKat. and i'm on a custom ROM to me its almost as if the phone is in some kind of wait state and i have to "kick" it to get it going. I've seen other in my ROM's forum talk of it. so now i know its not just our custom ROM, sounds like a KitKat thing..
Thanks. "Wait state" reminds me of finite state machine. Glad this isn't a hardware issue.
Hello all,
I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed.
Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear.
Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates.
I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue.
This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input.
Thanks.
Hi there, i am facing the same issue since two days now
First i am unable to come up with the physical home button issue and now there is this new issue. The phone does not respond after a call and the screen remains off and does not respond to any touch (double tap) or even the power button and home button pressed. I had to take the mobile into the recovery mode via home buttons power button and volume rockers. Is there any possibility of this getting fixed. I think i made a huge mistake purchasing this phone.. Slowly getting into problems one by one.. First the physical home button issue then this screen off issue. Checking for updates daily but seems like ZUK officials and Cyanogen are sleeping! Highly disappointed!!!!
In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue.
Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen?
ingtrans said:
In the meantime, I uninstalled most of the applications and the issue was still there Then I tried to play with different settings and it seems I have nailed it. After disabling turning on the screen by double tap (I'm not sure how the setting reads in English, I'm using the Russian interface), I cannot longer reproduce the issue.
Sydarij, could you, please, check whether the setting is on in your case and, if it is, turn it off and try to reproduce the issue with the screen?
Click to expand...
Click to collapse
Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue?
Sydarij said:
Do you mean after turning off the tap to wake option on your ZUK, you are no longer facing such issue?
Click to expand...
Click to collapse
Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all.
ingtrans said:
Yes, that's what it seems. With the option turned on I could reproduce the issue (just 1 or 2 tries were needed), while with the option turned off I could not reproduce the issue at all.
Click to expand...
Click to collapse
After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy!
Sydarij said:
After turning off this feature, the device unlocks by itself without me waking it up. Turning the feature off doesn't seem to help buddy!
Click to expand...
Click to collapse
This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. )
In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that...
ingtrans said:
This seems to be a different problem. How the option for preventing accidental wake-up is set? (It's just below the double tap option. )
In any case, one owner on another forum complained about the accidental wake-up issue despite the setting was on, but he meddled with the firmware before that...
Click to expand...
Click to collapse
Yes, the accidental wake up is set yet the issue cannot be resolved. Any other way you can resolve this and prevent the issue from reproducing? In my opinion, ZUK and Cyanogen officials are asleep after launching their new flagship. Dont see any updates coming from them since last 2 months. highly disappointed with this!
Sydarij said:
Any other way you can resolve this and prevent the issue from reproducing?
Click to expand...
Click to collapse
No idea. The solution I found seems to work well for me, at least I have not had any issues since I applied it.
Please turn on adaptive brightness. Issue will be resolved
ingtrans said:
Hello all,
I've been using ZUK Z1 for just about a week now and everything was fine until a couple of days ago when I could not unlock the phone after a call - the power button and the home button turned the screen on for a split of a second and then the screen went off again without reacting to any taps. I had to restart the phone by pressing the power button + the volume down button. I tried to reproduce the issue, but did not succeed.
Yesterday, I had the same issue twice and then I finally got it how to reproduce the problem The main condition seems to be ending the call when the screen is off. That can be achieved by holding the phone close to your ear when the call it ended by the other party or ending the call by pressing the power button (you need to turn on that setting beforehand) again while holding the phone close to your ear.
Another guy on another forum wrote that had experienced the same issue once and yet another guy mentioned that there was such an issue with Cyanogen on OnePlusOne, but it was fixed in one of the updates.
I'm currently on 12.1-YOG4PAS3OH and I'm not sure whether it is a Cyanogen issue alone or an issue caused by interaction of Cyanogen and some of the applications installed. I'm inclined to believe that it's the latter, otherwise there would be a lot of people who ran into the issue.
This weekend, if time permits, I'm going to try uninstalling the applications one by one to find out whether any of them contribute the issue, but maybe some of you have already done some investigation or know how fix the issue. I would appreciate your input.
Thanks.
Click to expand...
Click to collapse
Hi! I'm facing the same issue for the last 3 days. I felt everytime there is any moisture of sweat on the ear piece the phone hangs and doesn't get unlocked.
Will try shutting the double tap options. Hope it works! This is the first time I've brought anything in the launch sale without reading reviews. Hope I don't regret this.
sir when call come rintone accor but calling display doesn,t show
when i press phone icon in menu then it shows
phone is lenovo zuk z1
screen freezes during/after call !!
did you solve this problem?
i too have posted the same problem here ..
any sugesstions?
i am facing a black screen while calling and receiving calls on my zuk z1 .. any solution? and where do i find the proximity setting in my settings?