Related
I have been having a few issues with my Nexus One during after wifi tethering. Usually it only happens after extended periods of tethering, but sometimes it happens after shorter periods. My phone frequently gets from 100-113F (as measured with CurveFish BatteryLife app. I'm not sure how accurate it is). Perhaps the temperature has to do with the issues I am experiencing. Strange, because my G1 got just as hot and I never had a problem.
Issues:
1) Touch screen does not register correctly and I have to reboot the phone.
2) Microphone does not work properly when making phonecalls. I can hear the person clearly, but they tell me I keep blanking out.
Has anyone else had these issues or any other issues after tethering?
[edit]
I am now using a new Nexus One (RMA'd the last one for a dead pixel) and have not had any of these issues.
Apparently my last device was simply defective.
You do understand that WIFI Tether is still in beta process and will have problems right?
I have also noticed that the phone gets hot when charging and wifi on, I dont see this as a problem unless it is burning hot because components will get warm.
For concern 2, do you by any chance accidentally cover the rear microphone when speaking to someone? It is a nice feature for noise cancellation, but if the rear mic is covered, with your hand or on your shoulder, it will cut out your voice. Just throwing that out there.
I am using wifi tethering with Cyanogen addon.
I see a problem since CPU loading is 99% after wifi tether has started.
I guess we need to wait for bug fix
rydr1 said:
You do understand that WIFI Tether is still in beta process and will have problems right?
I have also noticed that the phone gets hot when charging and wifi on, I dont see this as a problem unless it is burning hot because components will get warm.
For concern 2, do you by any chance accidentally cover the rear microphone when speaking to someone? It is a nice feature for noise cancellation, but if the rear mic is covered, with your hand or on your shoulder, it will cut out your voice. Just throwing that out there.
Click to expand...
Click to collapse
Yes, I realize it is still a beta. This thread is not meant to complain by any means, and I apologize if it came off that way. I'm glad I have tethering at all
I am simply trying to diagnose my problem, and I figured seeing if others experienced similar issues would be a good way to start.
My first thought about the issues with people not hearing me was that noise cancellation was not working properly, but I am 100% sure I'm not covering the mic on the back of the phone.
I'm pretty sure it has something to do with tethering.
I am now using a new Nexus One (RMA'd the last one for a dead pixel) and have not had any of these issues.
Apparently my last device was simply defective.
mhaedo said:
I am now using a new Nexus One (RMA'd the last one for a dead pixel) and have not had any of these issues.
Apparently my last device was simply defective.
Click to expand...
Click to collapse
Nice! Good to hear you got that taken care of.
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)
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
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
so far you are the only one that has ever reported anything like that,ya know it could be a hardware defekt
sent via my bamfed out tbolt
Nope I'm in the same boat as im sure are many others. I have only ever had it actually impact me I think twice on phone calls out of almost a hundred or so that I have had since I purchased the phone. All the others times though it was extremely annoying to keep hearing the click sounds of the screen turning on and off on and off on and off etc.
I keep hoping for a software update that addresses the sensitivity of the sensor, but still no
I also wonder how much the battery is affected by the screen turning on and off repeatedly while in a phone conversation...
I get the same. More on my right ear than my left, but it will often take a digit that I just typed for an automated system and try to dial it, resulting in an alarm tone in my ear during the conversation.
sorry but i have 3 different bolts,the 1st one was rooted stock had that problem but it also went into the brick loop so it got replaced,rooted that one but never had the prob again,this one has the bamf 2 prev 3 on it and no probs that is why i suggested harware cause my first one had major hardware issues
sent via my bamfed out tbolt
i get it too. but i dont call so much. so i dont really care lol
I too had this problem, and did some quick searching on Google. Stumbled upon someone who said to spray it with canned air to clean it out. To my surprise, it worked. There is just enough room between the screen and the body of the phone for dust/crap to get in and it hinders both the light and proximity sensors.
You might be holding the phone in a weird position?
THUNDERBOLT
Damn, you lean something new every day, this thing makes phone calls too!
I've had the issue too recently. But it only started when I returned the last phone to stock. Before that, I had a small issue with it, but it didn't happen often.
pnd4pnd said:
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
Click to expand...
Click to collapse
I have the screen turn on during calls, but I've never had a face hang up. Honestly I think the screen turns on for me, but can't be interacted with.
Scratch that just did a test. I guess I'm lucky. Then again I don't hold the phone flat to my face. So I guess I would never hit it...
i have had hangups, the mute button pressed, and a 3 way call started. i just tried blowing the screen out with some compressed air as someone suggested. it seems better - will give an update after some testing.
No issues with hang ups for me. Had that problem all the time coming from the X.
Sent from B.A.M.F. 1.7 using Tapatalk
I have the same problem and have had it with every Rom I've run and stock. I'm surprised we don't have a way to adjust the proximity sensor yet, that's something I really miss about my Droid X.
After answering a call and putting the tb to my ear, my screen stays on.
Sometimes my ear dials numbers, sometimes the screen stays illuminated but doesn't respond to any touch! I have to toggle the screen on/off with the power button to get the touch response working again.
I have never had an issue. Been on mostly whatever the latest bamf release since rooting.
It happens to me whenever I forget the bluetooth especially after working out or anytime facial area is warmer then normal. I have a screen protector and clean the screen frequently.
I am having the same issue, so I called Verizon yesterday and they are sending me a new phone. I hope it works, because it makes talking on the bolt almost impossible.
Sent from my ADR6400L using XDA App
this is the first I am hearing of this. No problems for me.
Have the same problem...its really annoying man....will not get a refurbished unit until they fix the reboots
I've had 3 Nexus 5's so far due to one RMA and lastly because of a mistake on Google's part. But with all 3 Nexus 5's I have had two bugs that have been driving me nuts. I was curious to see how many people have had the same problems and if anyone knew of a fix. Bugs:
1) Keypad buttons being pressed while on a call. This happens almost every call. It seems that the screen is still active even if the proximity sensor turns off the screen. I haven't been able to reproduce it on purpose, but every single call I take I hear buttons being pressed. Sometimes it's like my notification bar get's pulled down, then the clock is clicked and I feel all these vibrations and ringing sounds and I look down at my phone and I'm in the date/time settings. This happens even if I don't have the dialer keys open. Weird.
2) Say I'm laying in bed and I answer a call. It seems as if there is some sort of setting for the accelerometer that if my head is tilted too much it's as if the microphone stops working... almost like the phone tries to switch to the second microphone (the one not normally used for phone calls). I can't tell you how many times I've been in bed and get a call from my wife (who works night shifts) calling to say goodnight and if I ever put my head back on my pillow she can't hear a word I say. As soon as I lean forward again she can hear me.
These are two problems that I have had with 3 different Nexus 5 phones. I've experienced the same problem with both Franco Kernel and the stock kernel. I don't know what else to do but it's driving me crazy. Anyone else seen these problems or know of a fix?
Thanks in advance.
Try turning your screen off during a phone call and see if there are still key presses being made. Depending how you hold the phone, the proximity sensor might switch the screen on during your call and could register key presses from your ear. The sensor is on the right side of the phone and will "miss" your head if it's behind it.
Unless you're leaving the digitizer enabled (tap2wake etc.) it shouldn't happen.
The mic issue while lying down seems to be common. Your head/pillow blocks the sound and noise cancelation wigs out. You could alter the way you hold the phone while lying down so the secondary mic at the top sticks out more. Personally, I just sit up and haven't had an issue with the noise cancelation since.
Sent from my Nexus 5 using Tapatalk