When i got this device i thought how stupid this was and hoped after flashing a custom rom maybe it would eliminate this stupid feature of this device. It seems HTC thinks it's a good idea to turn the screen ON after ending a phone call, WTF?
At work i use my bluetooth headset all day with my phone in my pocket. I will take my phone out, dial the number i want to speak to, press power to turn screen off, put device in pocket and have my conversation. I end the phone conversation with my bluetooth headset and guess what? The dang phone's screen turns on while it is in my pocket. I guess the light sensor has zero effect here! So now since this happens and my device has a timeout of 2min i set before screen turns off my phone accidentally "butt dials" people and without me knowing i'm now calling people randomly while i'm working!
Another case. I have my phone in my car's cupholder, i use bluetooth to make a call with my car, it initiates the call to my phone and again it turns the screen ON to make the call. WHY? I never pressed power on my device to turn the screen on to make a call. So again i press the power button to turn screen off while in call. I hang up the call when i'm done via the bluetooth in my car and again the device turns the screen back ON once i disconnect the call via bluetooth.
I just don't understand the logic behind this? Is this some HTC thing or all android? Coming from iPhone 4 never had this issue so was a first for me with this device. Just don't see the reason or logic for this?
Anyway to prevent this or stop this from happening? I mean isn't that the point of bluetooth to not need to touch your device thus no need for the screen to be turned on????
+1
It seems that this is not a HTC thing because I have the same behavior on my Samsung device. Same problem as well with pocket dialing during/after a call. Really annoying. I had the same thing on my old HTC Nexus One running Froyo, so this is not a new bug. Back then I tried a lot of different apps, and none helped. I even flashed CyanogenMod on it and it didn't change anything.
I really hope someone has run across a fix whether it's an app, a patch or a whole new ROM, because pulling my phone out of my pocket to turn the screen back off TWICE for every call I make or receive is getting to be a pain.
I can't believe this behavior is voluntary on the part of the designers. If it is, please someone explain why.
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
ethanon said:
You can use TASKER(automation app at Play Store ) to Get you screen off after a call or while connected to the bluetooth ..
Click to expand...
Click to collapse
Just downloaded but no idea how to use this thing. Not very saavy with this type of stuff. How can I use tasker to turn the screen off when ending a call ONLY while connected to a Bluetooth headset? This is my biggie since it's in my pocket.
Got it to work
Ok, I downloaded Tasker and I'm impressed.
Here's how I got this to work:
1: Create new profile using STATE, then go to NET, then hit BLUETOOTH CONNECTED. Here you can specify if you want only a specific device or any Bluetooth.
2: Set new task: SET plsLock to ON
3: Set exit task: SET plsLock to OFF
4: Create new profile using EVENT, then go to PHONE, and hit PHONE OFFHOOK.
5: Set new task as: SCREEN, SYSTEM LOCK
6: Hit IF, and specify if plsLock is ON
7: Create new profile using EVENT, then go to PHONE, and hit PHONE IDLE.
8: Set new task as: SCREEN, SYSTEM LOCK
9: Hit IF, and specify if plsLock is ON.
You're done.
Since I had the same problem with the wired headset, I also created a profile with HARDWARE, HEADSET that sets the variable plsLock to ON and exit task sets it back to OFF. You can name the variable anything you want and it will still work.
If anyone has a better/simpler way of programming this, please share. I just started using this program and am still trying to wrap my head around the way this is structured.
As this stands, it works... But it's still a patch on something that should be an option in Android.
Let me know what you think.
Ok thank you I'll give it a try. Yeah could never understand why my device thinks it's a good idea to turn screen back on after ending a call via Bluetooth or not? I receive call, I then press power button to turn screen off bit continue my call, the caller hangs up, boom my screen turns on displaying the phone dialer until my time out settings turn screen off. Dumbest feature I swear. Hello phone I pressed power offbutton to turn screen off, get the hint and keep screen off until I press power button and want it back on again. No sense...
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
ethanon said:
Deeznuts, did you manage to get it working with tasker ? I guess it is the only possible way to get to your objective. Learning Tasker will give a new dimension to your phone. More over I will try to make a profile for your and get working .
For some reading
http://www.pocketables.com/2013/06/...rt-0-tips-and-tricks-for-learning-tasker.html
Click to expand...
Click to collapse
No unfortunately not. I would greatly appreciate that! I would think it's a simple task but honestly I'm very handicapped when it's comes to stuff like this.
Basically a string for tasker that would simply just do this:
When my device is connected to a Bluetooth device whether it be my car kit, headset, stereo headset, etc. and a phone call ends where by me pressing the End Call on screen button, by ending call with car kit, headset, etc, doesn't matter but will make the screen turn off. That's it.
When connected via Bluetooth, a phone call ends, screen turns off.
Now here's a kicker and not sure if this part would be harder. I'm connected via Bluetooth headset or device, I have screen on to manually make a phone call, then while on the call I press the power button to turn screen off while on call and put device in my pocket. Now when the call eventually ends I would want the screen to stay off.
I will read into the link you provided and mess with it somewhere. Thank you for your time and help.
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
ethanon said:
Correct me if I am wrong , you mean to say that no matter what you want your screen to stay off after a call ...
Click to expand...
Click to collapse
Correct BUT only when connected to a Bluetooth device. My gripe is on a Bluetooth call, place a call manually then talk on headset, car kit, etc. I press power button to turn screen off then put phone back in pocket, when call ends the phone turns screen back on for some reason. Never understood this?
Related
I need a way to be able to voice dial at any time even with the phone locked or with some other app the Voice Talk open via Bluetooth, I know this is possible on Android since my old Motorola Milestone could do it and would be legal under the new laws.
My province is now getting distracted driving laws which will make using my phone illegal with how many steps it takes currently.
I refuse to give up locking my phone since I have private info on it but I need to be able to make calls by pressing the button on my Bluetooth even with the phone locked since it could even be in my jeans pocket with no way to get at it when sitting.
Currently on my GS2 I have to unlock the phone then double click the home button to bring up voice dialing or even open the voice talk app if I am in a different app.
Compared to my Milestone where I never touched it and at any time even pattern locked or in a different app I could just press the button on my Bluetooth and say "call jane" or something and it always worked.
How can I get this back? Considering the laws are coming into effect next month for me.
I would like to keep the stock Samsung voice for most time but would be willing to have a second one that works even if the phone is locked.
I also have people that want this phone but willn't buy it until I get this fixed.
Use Tasker to disable the lock pattern when connected to a bluetooth device - therefore when you disconnect from your car bluetooth, your lock pattern will re-activate.
Problem solved!
OK I have that and think I am close to setting it up but can't totally figure it out how to disable the lock screen.
All I have figured out is a profile that runs if a mic headset is connected but when I try to figure out the task it does I get stuck.
I have never used Tasker before.
This is suddenly going to be to expensive since I found out the SGS2 requires extra work to disable the pattern lock which is a extra $10 plugin and I am not even sure if I want to pay for Tasker itself after the 7 day trial.
I might try and find out how it was done on my old phone when locked.
For others that may want to kn ow here is the thread for this on a GS2
http://forum.xda-developers.com/showthread.php?t=1110307
Nope, you don't need the plugin - there's a keyguard action that you would disable, which also disables the lockscreen.
I'm trying to set this up myself, but for some stupid reason, it's not responding when I press my bluetooth button at all...
Fricken Vlingo - you suck!
k1sr said:
Nope, you don't need the plugin - there's a keyguard action that you would disable, which also disables the lockscreen.
I'm trying to set this up myself, but for some stupid reason, it's not responding when I press my bluetooth button at all...
Fricken Vlingo - you suck!
Click to expand...
Click to collapse
Are you sure that would work on our Samsung phones since they modified the locking system to use the /efs partition?
If you do get it working make sure to tell me how.
Not sure why this started happening, but whenever I call my voicemail the phone goes dark and I can't turn the screen back on. Neither pressing the power button or the home button does anything, but I can still hear the phone call. Any ideas?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Now the screen won't even turn back on after the phone call has ended
Do you use a screen protector? Check if the protector doesn't covers the sensor. It is possible that the sensor doesn't react well when it's covered (I had a similar problem with the Dell Streak).
Also try to make a call with a wired headset or if you make a call and you can't turn on the screen plug the headset in.
Terryjgj said:
Now the screen won't even turn back on after the phone call has ended
Click to expand...
Click to collapse
Might be a little bit late, but maybe for others
worked pretty well on my Samsung S4.
download the app "proximity fix" from the playstore and run it.
Job done.
Hope that helps you or anyone who stumbles upon this!
second day and already have many problems:
1. ringtone turned off vibration only. still have ringtone with incoming calls
2. making calls screen turned off once near ear. moving away from ear doesn't turn on the screen. try any button nothing works. have to turn off power to cut
3. smart stay isn't smart. screen still turned black even with bright environment
Am I unluckily with a faulty phone or they are known bugs? thanks
Not to sure mate
I have had NONE! of the problems that you have had, although i have had a few problems e.g. the turn to mute media stopped working and things like that, all i had to do was a restore and it is fine now, i was speaking to the people at the carphone warhouse (phone shop in the uk) they said they have only had 1 return since launch and that was because the screen wasnt big enough and they went for the note, i have also always found that samsung is happy to help you if you have a problem with your phone just give them a ring.
1: you need to explain exactly what you changed.
2: It's supposed to go off near ear because uses proximity sensor to save battery turning screen off.
3: Smartstay just doesn't work as well as it should do.
I am now on my third hands free car kit with my S3 and get the same issue with every one. I pair my phone. Connect my phone and it works ok for some time, could be an hour could be days. When working properly I press button on hands free kit to make voice call. Get a small sound to alert me to speak name of whom I want to call. When it works, it will then call the person I say. When it goes wonky, as it does, regularly, I press the button on hands free and await the signal to say the name. This time however, the sound that is made sounds all distorted and although the svoice screen appears on screen, it does not recognise what I say. I can receive incoming calls and answer them by pressing button at all times it just seems somehow to screw up the Bluetooth function every now and again. I have reset phone, did upgrades, (official ones, not rooted) and still happens. Anyone any ideas what issue is. As I mentioned it has happened with three different hands free kits I have bought so definitely the phone. Thanks for any help.
please read before posting
http://forum.xda-developers.com/showthread.php?t=2240291
Story was a bit messy, so i rewrited it.
Here's the deal.
I'm using headset and bluetooth car audio very often. I'm quite sure that when i bought the phone, i was able to wake the phone up during the call, using the power button, without the call being disconnected.
Now here's the problem, when i make a call, and want to check anythingo on the screen, i have to wake the device up, that needs power button to be pressed, and that immidiately disconnects the call. Any of you guys have a clue what could go wrong or maybe i need to see some settings to fix it?
I thought it only happens on bluetooth but yesterday i found out it happens also when using headset.
thx in advance
Hmm, if you are during a phone call, your phone should be awake?
I just know that you can reject a call by pressing the power button, that's an android feature.
No, it shouldn't be awake.
I'm not talking about rejecting a call either.
I've already solved the problem. It was an option in accessibility options, called "end of connection".
tapatalked