Database Develop

Keylock imideately after hanging up a call

Hi.
I have an odd behaviour of my S730/Wings. Say i make regular phonecall. No matter how long it is, 5 seconds or 5 minutes, the moment i hang up the call, the keyboard lock kicks in. A co-worker with the same phone doesn't have this issue, and i cant seem to figure out a way to switch it off. It is rather annoying
Anyone know how to solve this issue, so that the phone locks up only when left alone for some time, or with holding down the red button?
Any help is deeply appreciated
- Ulyd

When you end a call... are you holding the end call (red) button, or just tapping it?

I just tap it, i'm aware of the hold-down-red-button-to-lock-keypad. So i cant understand why it locks up...
- Ulyd

its hard to answer calls on hd7 when phone is acting up

hey guys sometime when i get and incoming call my phone start acting up and i cant slide up to take the call, my screen wont respond and no hard keys to press if some one know how to fix this please let me know if not im giving this wp7 a 2nd software update a chace to get this right. ms should be a genieus when it comes to software not apple or google. you never know when a emergency call comes in and you could not get it, im so concern about this. i had enough with 6.5 now this. but the problem is that i love ms i keep coming back. ****tttt

if a soft reset doesn't fix it you could hard reset. Just make sure you make a list of installed apps to make sure you get them all back on there.
I hadn't heard of this happening before.

I had the same problem once. I just switched the display off and on again (while the phone was still ringing) and then I could take the call.

chr5s11 said:
I had the same problem once. I just switched the display off and on again (while the phone was still ringing) and then I could take the call.
Click to expand...
Click to collapse
+1 this happens from time to time.
hit the POWER button to shut of screen, this just powers of the sound and display and does not efect the incoming call.
Press the POWER button to turn the screen back on where you still see the incoming call and the screen will now respond correctly allowing you to answer.
no need to rest or anything.

xma1e said:
+1 this happens from time to time.
hit the POWER button to shut of screen, this just powers of the sound and display and does not efect the incoming call.
Press the POWER button to turn the screen back on where you still see the incoming call and the screen will now respond correctly allowing you to answer.
no need to rest or anything.
Click to expand...
Click to collapse
+1 Me too.

Is there any remedy to this issue???, i'm having the same thing

[Q]

So I've been using my HTC one for about half a year, however most of the time when i call someone or answer a call, my HTC one keeps pressing the back button. To make sure, i turned off power safe so the buttons would vibrate when pressed. When i tried calling someone with power safe off, the moment i hit call, my phone constantly vibrates as if the back button was constantly being pressed. I tried a factory reset and nothing helps. I don't know if i should send my phone back or if there is a solution to this.

Unable to "wake up" HTC One M7 screen but the phone is/was ON

Hi All,
This will be my first post in this forum.
This morning i was using the phone after it was 100% charged. It was good until when i wanted to make a phone call, tried to switch on by pressing the power button, then i realized the screen didn't turn ON. To check if phone is ON, i made a phone call from my office desk to my HTC one and i heard ringing sound over the desk phone. But my mobile HTC one did not wake up. I also didnt hear any sound in my HTC one. Later on i believe the phone switched off and now any trial calls go direct to HTC's voice mail.
Steps tried:
1. Tried to hold the power button for long, doesn't work.
2. Tried the Volume Down + Power button long hold to see if it comes up. But it didn't.
3. Also, tried Volume Up + Power button long hold, which also doesn't work.
I read in the same forum that I need to let go off the power button after 2 seconds after the long press, when the phone is switched OFF. I need expert suggestion.
Thanks!!

Black Screen, won't do anything.

Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?

Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..

Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.

Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?

Buy a new one. Send yours in as defect. Done.

erase111

I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!