Related
Hi there,
I am a little ticked off with the way the phone switches the light off and you HAVE to press a button to get it back up when in the middle of a call.
Is there any way to keep the phone awake while on a call? Ofcourse, I HAVE tried out "Shake Awake", but thats a little buggy too.
And also, the buttons for Hold, Mute, Speaker mode and all those options come up only when you press the menu button. Is there any alternate dialler available or something which can get all these options on the screen while on the call like the iPhone as its easier to use it than press the button to get the options?
just install keepscreen.
edit: this will keep the screen alive. about the alternative dialer i don't know. but be aware that the phone has no proximity sensor, so you are prone to accidentally press random buttons.
Cool. Will check it out man. Thanks.
I have a different problem - since, sadly, Hero has not got a proximity sensor, I constantly drop my calls by accidently touching the end call button with my cheek. I believe that's a reason the screen backlight goes off so quickly during a call - when the screen is off, it does not react to touch too, so that accident call drops would be less likely.
There are still some serious problems though. First of all, screen timeout during a call is not short nough - while you can know that you must wait a few seconds before you can actually touch the phone with the face, others can't, so call drops are, sadly, unavoidable in such cases. The fact that hold, mute and other buttons are hidden under the menu button is a good thing not only because it keeps Android phillosophy straight, but reduces chances of unwanted misc. actions. The solution of this problem could be an option to disable the end call button, since there are dedicated hardware keys for that.
I have also noticed that if you minimize the dialer during a call with home button, the screen timeout will not be quick, so before continuing a call it's a good idea to bring the dialer back by tapping the hardware call button so the screen timeout becomes quiick again.
Very true. I thought about all these before I posted, but on the other end, I just said 'f it' to myself and asked it here.. hehe.
I wonder if iPhone users have such issues.
As someone in this forum mentioned, it is best to have the screen switched OFF during a call, unless you have something to do. This way, it prevents you from fiddling with the controls.
Not just the hero, earlier models too have this feature. It quite odd in the beginning, but you will love it later.
subhramani said:
Hi there,
And also, the buttons for Hold, Mute, Speaker mode and all those options come up only when you press the menu button.
Click to expand...
Click to collapse
Not necessary!
During a call
- Press "Call" to hold (will also mute)
- Press and hold "Call" to activate speaker mode.
After i hang up on a call (when the phone is in sleep mode and the screen is locked) the screen unlocks. this is quite contrary to what is mentioned in the phone manual chapter 1 page 45. this becomes an issue since i use a bluetooth headset and the phone remains in its sleeve/case and after every call, a whole bunch of applications will launch since the case is in contact with the screen. have i overlooked some settings or are there other owners who have faced this issue?
ideas and suggestions welcomed
did you check it out if any of the hardware buttons being pressed against the case hence wakening up the phone.?
i had it to only closed al my apps in taskm and it stoped flickering
My HD2 is also behaving in the same way even in controlled test conditions - the phone unlocks when a call comes in (I'm presented with slide to accept or reject call) The phone unlocks during the call, but fails to lock again on disconnect (either by pressing "end call" or hang up via bluetooth).
Can anyone verify this? Is it interacting with something I installed?
I believe I found a (complicated) workaround.
What I want: leave HD2 inside pocket, answer calls with bluetooth headset, hang up and phone will go back to lock.
Problem: After I hang up using bluetooth or press the big red "End Call" button or the other party hangs up, the phone stays unlocked! It stays powered on and all kinds of buttons gets clicked.
Practically all lock sw uses their own lock screen (which I don't want to install). CSDevCtrl does not trigger by phone. TouchLockPro uses its own transparent lock screen but can respond to phone events. Using the !SUSPEND for TAPI\Ended under settings does not seem to work when the screen dims about 50 secs into the call.
Solution: Use TouchLockPro together with LockAndOff. Get TAPI\Ended to run LockAndOff will turn phone off, whether by bluetooth, big red "End Call" button, or the other party hangs up.
BTW: I think there is some confusion on whether the phone locks when you
1. press the big red "End Call" button, or
2. the hard "End call" button
in the forums.
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
linivan said:
I noticed that HD2 have a light sensor next to the top ear speaker.
During a call, if the phone is put near the ear and cover the light sensor , the screen become non-active which is good.
If anyone can come up with a lock sceen using this light sensor , then the problem with random launch of program when phone inside pocket will be solved.
This lock screen should only activated right after an end of call, beacuse , sometime you may want to use the phone in a dark place.
Click to expand...
Click to collapse
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
johncmolyneux said:
It's the proximity sensor that turns the screen on and off during a call, not the light sensor. How else would it work in the dark? (which it does)
Click to expand...
Click to collapse
My proximity sensor does not work, when I am getting a call my screen turn off and when I am taking the phone out from my face it turn on only when I am out side at the sun!! the screen stay off when I am inside room. I tested it with flsh light and it is working also.
I have a T-Mobile US version of the HD2. I am having the same problem when using the bluetooth system in my car. After answering or making a call the phone stay unlocked. And then starts making random calls while I am driving!!!!
There has got to be an easy fix for this!!!
Buy pocketshield, problem solved.
i have this unlock problem with 1.48 rom and i solve it by pressing start button and lock. after that everything works fine unless i change theme in settings. then just repeat first step.
Solved
Same trouble with me until I use the following software. I tried it and it's almost perfect. unzip it and just copy to your HD2, run CallerLoc.exe and click Yes, you'll find:when you hang up, or he/she hang up a call, or a call is established, the screen will turn off.
Why say 'almost perfect', the software is in chinese, but the filename is in english. and it's a call location software but with the function we need.
To stop or before you delete the software, run Callerloc.exe and click Yes again.
Hope this will help you. Sorry I don't find a English version of this software. I esure and I'm using this software perfectlly with my Leo.
theciscokid said:
Buy pocketshield, problem solved.
Click to expand...
Click to collapse
Same for me
Greetings.
I understand this is quite an old thread I'm digging up but I need a little help as well and I didn't want to start a new topic just for that.
I've this silly problem, appeared right out of the blue:
You all know the standard manila behavior, when the phone is idle, the screen first dims and after some more time, depending on your preferences, the screen locks. It also locks if you press the power off button. This all was happening to me till this morning.
I added an event in the calendar (the only change I made today) and after that, my phone dims and then goes in sleep mode after the designated period of time, but DOESN'T lock!!! It doesn't even lock when I press the power off button. I can still lock it by pressing Start and then lock or by press and hold the power button and choose the lock phone option. So one would say that it's still operational, so why bother about it, but I kinda liked the standard function and I have to freaking idea why it changed!!!
I'd be most appreciative if you could offer some help with that.
Oh, I forgot to mention. Soft reset didn't solve the problem. Erasing the calendar event didn't either.
My phone runs the factory ROM (1.66.482.1 ELL), I haven't changed anything other than user settings (yeah, I'm a noob... )
Thanks in advance!
Nasos
Pocketshield could be the end of your problems. You can try it for 10 days and see how it goes...
But why do I need to buy third party software in order to revert my phone to it's original operation?
No, this is not the answer I am looking for. I was wondering if you know of any kind of settings that might have changed by accident and caused this undesired behavior.
Thanks.
The best to return to normal operation would be a hard reset. Or you can spend a while trying.
You can try
HKLM\Software\Microsoft\Shell\Lockscreen\Enable=1
HKLM\Software\Microsoft\Shell\Lockscreen\Active=1
Thank you very much. I opted for the hard reset option... I hope it stays ok this time!
My HD2 also had some strange unlocking and unwanted calling.
I noticed it appeared when using the android style lockscreen.
When I changed back to the original one, problem solved
i had this too. the andriod lockscreen seems to be a bit buggy last time i used it, i accidentially called 7 random numbers
Hi guys
Had a search and nobody else seems to be having this problem, but seems so basic that I'm sure I must be missing something obvious!
When I'm in a call (either incoming or outgoing) I can't get the screen to turn on properly in order to hang up or use other programs (check calendar etc). This is particularly annoying on outgoing calls as it makes hanging up very difficult!
To be more detailed, a single tap on the power button has no effect on the screen - it stays off. If I repeatedly click the power button, sometimes the screen will flash on for a miniscule moment - this is my hang up method at the moment, repeatedly press the power button and tap the screen near where the hang up icon will be, and eventually I'll catch it while the screen's on. Once I'm off a call, things act as normal.
I have Pattern Lock set up, and am prompted to unlock the phone once I'm off a call, this is what I'd expect from previous Android phones but might be causing problems here?
I found this previous thread where people have had very similar symptoms because their screen protector is over the proximity sensor, but I don't have a screen protector. Might I have a dodgy proximity sensor? Is there any way of testing it?
Cheers for the help!
Moved to Q&A
Sent from my Nocturnalized One XL using Forum Runner
DJGibbon said:
Hi guys
Had a search and nobody else seems to be having this problem, but seems so basic that I'm sure I must be missing something obvious!
When I'm in a call (either incoming or outgoing) I can't get the screen to turn on properly in order to hang up or use other programs (check calendar etc). This is particularly annoying on outgoing calls as it makes hanging up very difficult!
To be more detailed, a single tap on the power button has no effect on the screen - it stays off. If I repeatedly click the power button, sometimes the screen will flash on for a miniscule moment - this is my hang up method at the moment, repeatedly press the power button and tap the screen near where the hang up icon will be, and eventually I'll catch it while the screen's on. Once I'm off a call, things act as normal.
I have Pattern Lock set up, and am prompted to unlock the phone once I'm off a call, this is what I'd expect from previous Android phones but might be causing problems here?
I found this previous thread where people have had very similar symptoms because their screen protector is over the proximity sensor, but I don't have a screen protector. Might I have a dodgy proximity sensor? Is there any way of testing it?
Cheers for the help!
Click to expand...
Click to collapse
I have the same problem. It doesn't happen all the time, naturally, but it's been frequent enough to be irritating. If anyone figures this out, I'd love to hear a solution.
Frustratingly this does seem to happen to me every time - although it might only be once the timeout has activated the pattern lock. Or I could be barking up the wrong tree entirely!
Think I might have to do some testing tonight . . .
After some fiddling it does seem that it's a problem with the proximity sensor - Elixir 2's settings show the proximity sensor always showing "near"
If someone could run Elixir 2 on their N4 and confirm that they do get changing settings, it would be a great help!
I have searched and then made this thread. There were some people with home button issue but None of those were related to my problem.
PHONE MODEL - GT-I9505 ( International version)
I have had my S4 for a couple of months now and I am addicted to flashing. I flash a test lot of new roms.
MY PROBLEM
When i make or I get a call, Once i pick the call and put my phone to the ear and after the proximity sensor turns off the screen i cannot use my home button or powerbutton to wake the screen during call. For example if i want to cut the call During a call. I simply cannot do it. Sometimes the home button will respond, Some times it wont
For the home button to work The other party has to cut the all only when my phone detects that the call has been disconnected it wakes up. Looks like the home button stops functioning ?
I dont know what is happening.
I thought it was the rom issue, But it isnt. I tried two different roms. Did the same behaviour.
Any advice or anything to help me will be appreciated. Is my hardware damaged?
My phone is never dropped and is very new like .
ROMS I TRIED
Wanam Lite.
Cynogenmod 10.1
same problem. any solutions?
I am having the same issue with my home button. Won't press during calls. Did you ever find a solution? Thanks!
rdhalla said:
I have searched and then made this thread. There were some people with home button issue but None of those were related to my problem.
PHONE MODEL - GT-I9505 ( International version)
I have had my S4 for a couple of months now and I am addicted to flashing. I flash a test lot of new roms.
MY PROBLEM
When i make or I get a call, Once i pick the call and put my phone to the ear and after the proximity sensor turns off the screen i cannot use my home button or powerbutton to wake the screen during call. For example if i want to cut the call During a call. I simply cannot do it. Sometimes the home button will respond, Some times it wont
For the home button to work The other party has to cut the all only when my phone detects that the call has been disconnected it wakes up. Looks like the home button stops functioning ?
I dont know what is happening.
I thought it was the rom issue, But it isnt. I tried two different roms. Did the same behaviour.
Any advice or anything to help me will be appreciated. Is my hardware damaged?
My phone is never dropped and is very new like .
ROMS I TRIED
Wanam Lite.
Cynogenmod 10.1
Click to expand...
Click to collapse
jasonbosch said:
I am having the same issue with my home button. Won't press during calls. Did you ever find a solution? Thanks!
Click to expand...
Click to collapse
Go to Apps - Settings - My device - Call - Untick Turn off screen during calls :highfive:
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?