-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
New app for users accidentally hitting buttons in a call
DanDroid
Well-Known Member
Downloaded, installed, made a test call. Works perfect. Its the best soultion so far for accidental face hangups. I think the easiest way to solve this is to just remove the soft "End Call" key and just use the regular hard button end call key. They added the mute and speaker phone soft buttons on the last update, so I would assume removing "End Call" should not be that difficult.
nathanotis
Android Enthusiast
And i think this is the best idea I've ever read on a forum. +2 internets for you, my friend.
Anyone having any odd phone issues after installing? I've started getting the "HTC" boot-type screen after pressing the home hard button from various apps, the weather widget setup keeps popping up randomly, and every now and then when I press the home or phone buttons I get asked what app I want to be default (i.e., HTC Sense or Home, SuperDial or Phone...). Seems like my defaults are getting erased.
I had also downloaded and tried LockBot Pro around the same time, so I'm not really sure which is responsible. I've uninstalled LockBot for now since I really want Proximity Sensor to work out... hopefully that fixes things.
What's up with the Android Market? I like the idea of the whole community being free to create and post apps, but man... so many that I've tried are just buggy as hell. Is there any kind of official Google testing program before they hit the market, or is it just up to the community to determine which work and which don't?
I had also downloaded and tried LockBot Pro around the same time, so I'm not really sure which is responsible. I've uninstalled LockBot for now since I really want Proximity Sensor to work out... hopefully that fixes things.
What's up with the Android Market? I like the idea of the whole community being free to create and post apps, but man... so many that I've tried are just buggy as hell. Is there any kind of official Google testing program before they hit the market, or is it just up to the community to determine which work and which don't?
tatonka_Hero
Android Expert
Unless I'm mistaken, it's a completely open market. Anything can go up there regardless of testing.
Nice application. Working perfectly.
TS
TS
Hi guys
Thanks for the feedback!
Just wanted to explain why the screen never turns off, its not my fault! Because HTC only use the light sensor for the auto backlight they have made it so it only reports a value when the screen is on, so when the screen goes off it just reports a constant value of 0!
I'm working on an update at the moment which should fix a couple of issues hopefully including the auto backlight feature bug. Although as far as I know this only affects the CDMA Hero, the GSM one works regardless of what setting you have it on.
If anyone finds bugs please email me, I'm especially interested in people who have tried it on other phones! I've only been able to test on my Hero but if it works on other devices then I can add them to the list of supported phones!
Thanks
Tom Reay
Thanks for the feedback!
Just wanted to explain why the screen never turns off, its not my fault! Because HTC only use the light sensor for the auto backlight they have made it so it only reports a value when the screen is on, so when the screen goes off it just reports a constant value of 0!
I'm working on an update at the moment which should fix a couple of issues hopefully including the auto backlight feature bug. Although as far as I know this only affects the CDMA Hero, the GSM one works regardless of what setting you have it on.
If anyone finds bugs please email me, I'm especially interested in people who have tried it on other phones! I've only been able to test on my Hero but if it works on other devices then I can add them to the list of supported phones!
Thanks
Tom Reay
Hey Tom... I'm no programming guru, but I had a suggestion for a future update or for you to play with. Not sure how your code works at the moment, but I'd guess you just have a threshold value set below which the app kicks in and locks the screen? Right?
How about trying a modification that reads the sensor value when the phone app is open or an incoming call is present, but before the call/answer button is pressed. Read the sensor value again after a call is initiated/answered, and do a quick calc to compare the delta (either absolute or percentage, would have to play with it to see which worked better). Set the lock behavior for a delta threshold, not an absolute threshold. Might help with variable environmental light levels.
How about trying a modification that reads the sensor value when the phone app is open or an incoming call is present, but before the call/answer button is pressed. Read the sensor value again after a call is initiated/answered, and do a quick calc to compare the delta (either absolute or percentage, would have to play with it to see which worked better). Set the lock behavior for a delta threshold, not an absolute threshold. Might help with variable environmental light levels.
Hi,
Thats a good idea but unfortunalty the problem with it being too sensitive is with the hardware. I do use a threshold, but the threshold is 0! It seems to take a lot of light for the sensor to read anything but 0. Might look at using the g-sensor in low light situation but have more immediate bugs to fix first!
Wow, bummer about the sensor. Not your fault, you made it do something cool it wasnt originally designed for.
Another thought/request. Since you have the framework for an app that intercepts the call screen, how about tackling the slider idea many here have said would be nice? Have the screen immediately lock when a call is initiated/answered and on that lockscreen is a slider to bring up the keypad, another to hang up, maybe one to mute or go to speaker or just bring up the stock call screen, etc
I would pay for that, so would everyone in my family and probably many here.