Related
Hey guys i currently upgraded from the nokia n900 to the nexus one. I had this great app on the n900 where it used the proximity sensor to switch the phone call to speaker when its away from your face and then switch back to the regular phone "ear" speaker when its against your face. I tried looking for something like it i downloaded "smart call" and it kinda works but it uses the accelermeter to determine the phones orientation. any help is appreciated THANKS!
This is a surprisingly good idea...
I really want this function also.
I had this in my Touch Pro2 but that used both proximity sensor and accelerometer so when i put the phone on a table with the screen down it started speakerphone. As soon as I picked it up it changed back.
Really good feature if you´re put in hold, waiting for someone to answer.
+1
Brilliant idea.
Ya its great! so basically when the screen turns on when you pull it away from your face so does the speaker lol i think its simple enough for the developers to create right?
nothing?
deng 200 views and no love.
You might want to try asking this in the Tasker thread. I'm not familiar with the program, but it might be able to do what you want.
+1 This is a great idea. I just spent 45 minutes on the phone with Time Warner and was on hold 5-6 times, this would have been handy.
I know for a fact this would suck on my n1. The only noticeable problem i have on my n1 is my prox. sensor sucks, alot of the time it thinks that my head is away from my phone and i end up muting myself and not realizing it and then getting hung up on. Very annoying
_-..zKiLLA..-_ said:
I know for a fact this would suck on my n1. The only noticeable problem i have on my n1 is my prox. sensor sucks, alot of the time it thinks that my head is away from my phone and i end up muting myself and not realizing it and then getting hung up on. Very annoying
Click to expand...
Click to collapse
Mine does the same thing, but like djstoffe had on his Touch Pro2 we should implement the accelerometer so we don't get any 'false alarms'.
After a 12 hours working day I needed to relax a bit...
I just decided to write the app as I like the idea but I'm not sure on the concept how to use it... have to sleep about it.
Anyway you can play with the attached apk and if you would post me a logcat, that would be nice and i can see on which devices/rom's it doesn't behave like on my Nexus with CM6...
Code:
adb logcat|grep SpeakerProximity
Just fire up the app and there is a preference view where you can set it on or off with a combobox.
It's working on my phone but as I'm sleepy I can't test it any further but if you like the app and think it could be usefull, just post your comments and I see that I turn it into a optimized app (this is just a quick afterwork writedown)
Before I forget, I will post the sourcecode after I cleaned up my mess and maybe also write a short tutorial on how I did write this app ;-)
Added a new Version in post #27 => http://forum.xda-developers.com/showpost.php?p=7972710&postcount=27
WORKS GREAT THANKS!!!
Sent from my Nexus One using XDA App
Thanks so much for stepping up and making this, rac2030. I just tested it on my phone and it works great!
Works like a charm!! Thumbs up!!!
Hmmm... scary that it's working without probs... did test it today a bit but expected bugs: because I was tired and just wrote out of my head.
Could you guys feed me some lolcat to see if the values are always right or as I asumed?
Ok came across a problem. Is there a way that the app keeps running but disables when the Bluetooth is connected to a headset? The other day I was using my jawbone and it kept switching from speaker to the jawbone.
Sent from my Nexus One using XDA App
k0shi said:
Ok came across a problem. Is there a way that the app keeps running but disables when the Bluetooth is connected to a headset? The other day I was using my jawbone and it kept switching from speaker to the jawbone.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I will take a look at it, sounds like a good idea...
Note to myself:
- Disabling the speaker switch if headset is connected (bluetootht and wired)
- proximity monitoring should be handled in a proper service that starts with the accept broadcast of the call and ends itself after the end call broadcast
- grabbing it upsodedown (based on G senseor) switch microphone on and off (as a second option in app)
I'm running into a couple problems with the app on my Nexus CM6.
It is functioning properly except for the screen and speaker button. I called myself from Gmail and answered like normal with the phone up to my ear, working so far, then I took the phone away from my head and the screen came on and switched to speaker perfectly, but after that if you put the phone back up to your face the screen doesn't turn off and the speaker button remains green (as if it were still on speaker phone).
Like I said, it switches back and forth from speaker to no speaker flawlessly, so that part is working great. Any one else experiencing this?
Also, it would be amazing if we could utilize the tilt sensor so that if you wanted to set the phone on the table, screen down, it won't switch back to in ear.
dailydR1ver said:
I'm running into a couple problems with the app on my Nexus CM6.
It is functioning properly except for the screen and speaker button. I called myself from Gmail and answered like normal with the phone up to my ear, working so far, then I took the phone away from my head and the screen came on and switched to speaker perfectly, but after that if you put the phone back up to your face the screen doesn't turn off and the speaker button remains green (as if it were still on speaker phone).
Like I said, it switches back and forth from speaker to no speaker flawlessly, so that part is working great. Any one else experiencing this?
Also, it would be amazing if we could utilize the tilt sensor so that if you wanted to set the phone on the table, screen down, it won't switch back to in ear.
Click to expand...
Click to collapse
Have to test this, thx for the info.
Note to myself:
- add tilt Sensor and dont switch back if in speaker and get flipped (make this optional in settings screen)
Hey guys,
I've just receieved my third HTC handset with what I'd consider to be a major issue.
HTC Touch2 in 2009 - would often power off during calls (probably due to WinMo). Hardware buttons quickly became loose after about a month of use, and the backlighting stopped working.
HTC Legend in 2010 - this phone is two months old and the top speaker is so broken I can barely hear somebody on a call. Everything crackles and pops and, according to people on the other end, they can barely hear me either. It's annoying as when I bought it the call quality was great but gradually the speaker got buzzier and buzzier.
HTC 7 Trophy - the most serious of the bunch. Yesterday, whilst web browsing, the phone displayed a still multicoloured screen of static. None of the buttons would work. After taking the battery out and restarting, the static re-appeared. I've managed to power on the phone since - you have to wait an hour with the battery out - but you get the same static lock ups when web browsing or using search after about five minutes. Having had a similar experience on my laptop, it looks to me like a GPU failure.
Am I the only one who has experienced incredibly shoddy hardware quality control from HTC? I'm going to have to replace the HTC Trophy and, at the moment, I'm starting to seriously question going with an HTC. The touch2's button issues were forgiveable because that was relatively cheap, the Legend's speaker was incredibly annoying but the Trophy's GPU failures are completely unforgiveable IMO. They render the phone completely useless.
Am I just unlucky or have others experienced similar concerns?
Cheers
My Hero has been fine, along with my touch... Although that met a washing machine in the end
Finally ~ Someone With A Similar Issue
Finally, someone that doesn't purely worship HTC... Although I haven't experienced issues to the magnitude of your's, I haven't been 100% happy with my phone since the day I bought it. I have a HTC Desire, and I got this phone in confidence after reading many reviews about how good the phone was, these reviews were clearly written from people with 0% experience with the phone.
I will number the issues I have had with the build quality of this phone...
1) The case on the back of the phone, has only ever been took off about 4 times, I have never dropped my phone or anything, however it starting to come off, yes, I can take the back of my phone off, without using the finger slot.
2) The screen is so easy to scratch? It was in a pocket with an Asthma spray, and there was no vigorous shaking of my pocket, yet somehow the screen just completely f****d up man... wow.
3) This is probably the worst issue I have. Every time HTC releases an update for my phone, I run into some sort of issue. I got my phone in May/April 2010 (it's on Orange UK however de-branded and now due to update issues, running a custom ROM) and immidiatley I found that an update had been released. After downloading the update the phone started to install the update, however it restarted and nothing happened. Left it for about an hour, nothing... So yes, I did the worst, took the battery out and messed it up completely. The shop I got it from forced me to send it to HTC, it took them 5 weeks (VERY poor customer service) and when I got it back they had barely fixed it, as when I turned it on, it finished installing the update?
4) I have had some other software issues, such as the system occasionally locking up and having to remove the battery to get anything to work. Occasionally the screen will lock up, like I won't be able to click any icons, however I'll be able to swipe from screen to screen, and it really can be quite annoying. As far as battery goes, it will last me an entire day, but will require a charge at the end of the day.
However, I think me and you are in a minority. I'm 14 years old, and I talked my Dad into buying a HTC Desire HD. He hasn't had a single problem with his, it installs updates perfectly without and issue, and the software performs seaming-less (except for a problem with a process that took up 80.9% of the RAM, fixed by turning the USB Debugging on?) So I believe HTC are good, theres just a few really, really bad apples in there, and unfortunately HTC won't admit this, and don't want to do anything about it... I hope I helped, I'm fairly new on here...
Cheers, Michael.
Well guys,you are a minority indeed.This Tuesday I received my Desire HD,which is my fourth handset from HTC.I have had a Diamond,a Hero,a Desire and now the Desire HD.The only problem I ever had was with my Diamond which,after one year and a half took some water in it without getting exposed to any water,but it was because the climate here is very humid.Other than that I have never had an issue.And I am no fanboy,if I had problems I would change without second thought.
I'll just tell you that a friend of mine punched my Desire HD with his full strength(don't ask why) while it was in my pocket.I thought the phone was done for,scrap,but the phone is like nothing happened.My friend's hand wasn't so lucky however,it still needs ice!
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
as i'm a developer i didn't this it's a bug ithink it's accidentaly and you were at that place again like other time
But that's quite too big to be jusn an accident. I had this phone for half a year and nothing. Well i'll try this Friday not to put it on top of the receiver and will post what happened. This thing scared my quite big, i thought that mmc is broken but i have checked the bootloader (i don't know how the screen with 4 colors is called, i think it's bootloader) and it showed my mmc working perfectly. If it was not because of microphones what could then be the problem?
OK tried that this Friday too. Same think - phone near the receiver - phone dies and i must hard reset it to work again. How is this possible? Which part of the phone messes?
Very possible that a strong magnet could do this. Internally the surround uses a microsd (there are guides here for upgrading it but taking the phone apart). I imagine a strong enough field could corrupt a microsd pretty easily. When u say wireless mic do you mean bluetooth?
No no no, i mean microphones which are used on stages, i work as a sound engineer and my phone always is close to receivers, close to controlers and other stuf i use. So to avoid further coruptions i should put my phone further from all equipment right?
OK after this other few tries i have found out that it does indeed mess my phone, i have tried holding it near wireless microphone receiver and my phone have frozen and when i placed my phone further from receiver nothing happened. So look out for that
r0mka said:
Hello all. I have HTC Surround from AT&T with updated 8107 firmware. I have spoted some strage bug (i don't know how else i could call it) and wanted to ask if thisone is possible and if i do think right. So i have this phone for about half a year and i'm pleased with it, nothing happened to it until now. Last week i was typing an SMS message and suddenly it just froze. I tried to restart it but the phone got stuck in the white HTC screen. My firmware then was 7720. I have done the hard reset and everything seemed to be ok but today the same thing happened with updated version too. I thought a bit and remembered that both times my phone was lying on top or near by wireless microphone receiver which was in working state. So can it be possible that some sord of electromagnetic waves is causing my phone to do this? Or it's just a coincidence?
Click to expand...
Click to collapse
Is frozen screen? Still completely can't use? I feel a little bit like WM6 era's problems. After a certain amount to you. May is hardware have dark disease.
Hello All,
Last night after I S-Offed my Desire S I instantly installed Custom ROMS for HTC Desire S and encountered a problem.No matter what ever I do,while I call or be called,I can't hear a voice neither the opposite party can hear a thing.Is there any fixes to this bug ? Neither whenever I get a call or SMS I cant hear the ringer-tone!
I also have encountered this same bug in many Custom ROM'S.
Neither I can't hear sound in any Media or Radio,Nor the loud speaker works!
Somebody please help me out!
Thanks in advance!
mgfneo labour
What rom are you on? cm7 seems to be working fine.
Try putting on the ear phones to see u have sound.
Try turning off your phone and removing the battery for a few minutes then putting them back on.
I have found the fix but unfortunately it is quite troublesome for me right now!
If I change the back cover then all seems to be working fine,I changed my back cover and put on a friends back cover and voila ! All is OK.
After inspecting the back cover I see there is two narrow metalic parts maybe used as the antenna/connect to the antenna,my one's seems very shaky and somewhat broken in the middle.
Guess it's time for HTC RMA ....
If you've got some skill (+dexterity) in using a soldering iron, the fix is easier than you think. The problem also says something about the effort you put into getting the cover loose in the first place