Related
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
My camera is weird, sometimes it will work (tried roms, kenals, camera mods, fixes you name it) This is what happens when it works, fine in one area like my house for example, go out, come back then it crashes. Looked all over this thread and like i said tried everything. Or have i missed something. For the love of God, what IS going on?.......................
What ROM's have you tried with it?
Not sure what the problem is exactly. Might be a hardware fault if it occurs on different ROM's.
Have you tried using another SD Card?
Maybe some big temperature differences between outside and in the house?
That was just an example, It will work one minute then crash the next, then nothing. different SD card makes no difference
phux ache said:
That was just an example, It will work one minute then crash the next, then nothing. different SD card makes no difference
Click to expand...
Click to collapse
Hi,
Firstly,great name.
What ROM are you using ,and did it work on your previous ROM?
I'm using revolution hd 4.1.13 bricked kernal 1.4 with camera fix (yea) Tried insertcoin ICS but camera always ends up playing up (3.5 sense android version 2.3.5) Tried Faux kernal and stock kernal. Well phukt ov
phux ache said:
I'm using revolution hd 4.1.13 bricked kernal 1.4 with camera fix (yea) Tried insertcoin ICS but camera always ends up playing up (3.5 sense android version 2.3.5) Tried Faux kernal and stock kernal. Well phukt ov
Click to expand...
Click to collapse
Hi,
So, you are saying that no matter which ROM you are running,you are having camera problems?
That sounds like an hardware issue,and you should consider returning the phone...
i have suspected hardware, but why does it work on occasion? Not working at moment btw. But did three days ago, no problem. Went out for a bit, phone in me pocket, came home. Camera, snafu
Latest on camera problem. Fixed!!!
Here's what you do..
1. Find a hard surface
2. Hold phone in your thumb and first finger (important! face down)
3. Your phone needs to be approx six inches above hard surface (face down)
4. Drop the 'kin thing square on flat on surface
Voila!! Camera fixed
IMPORTANT NOTE!
It worked on mine probably because of hardware problem,
If you try it and it phux your phone it's not my fault,
phux ache said:
Latest on camera problem. Fixed!!!
Here's what you do..
1. Find a hard surface
2. Hold phone in your thumb and first finger (important! face down)
3. Your phone needs to be approx six inches above hard surface (face down)
4. Drop the 'kin thing square on flat on surface
Voila!! Camera fixed
IMPORTANT NOTE!
It worked on mine probably because of hardware problem,
If you try it and it phux your phone it's not my fault,
Click to expand...
Click to collapse
Hi,
Nice fix
Bookmarked
Hi everyone/anyone,
I can't post in the developer sections so I'd like to comment here then.
Have used IColdS on my Desire S for about 6 months as a work phone with heavy email and talk usage. The biggest pain was email not showing the email body and then not responding - alot. Every now and again other apps stop responding.
Anyway, I came back here and tried Jellytime as a random pick. Worked great after a week of use. Even USB tethering and Wifi hotspot works. Apart from the 5mp camera photo issue and Bluetooth not working at least email and general stability is good. The 2 issues are known and being worked on. Great upgrade I think and extended the life of the old girl a little longer.
Axel
How is battery life on this ROM? I am currently on Pacman 19.3, but have issues with 3G battery draining. So I only use 2G of wifi.
Otherwise, I like the Pacman ROM a lot. Now and then a spontaneous reboot when the phone is idle, but until now, it hasn't disturbed me.
zertyx said:
How is battery life on this ROM? I am currently on Pacman 19.3, but have issues with 3G battery draining. So I only use 2G of wifi.
Otherwise, I like the Pacman ROM a lot. Now and then a spontaneous reboot when the phone is idle, but until now, it hasn't disturbed me.
Click to expand...
Click to collapse
I must say I haven't run on battery alone for a whole day yet. At my work desk it's always docked and charging. This weekend I'll be running off the battery so will report back how it goes.
Axel
axelmasok said:
I must say I haven't run on battery alone for a whole day yet. At my work desk it's always docked and charging. This weekend I'll be running off the battery so will report back how it goes.
Axel
Click to expand...
Click to collapse
Phone was about 70 odd % Friday night. It was 2% Monday morning after only 2-3 phone calls over the weekend with no charging. My un-scientific conclusion would be it's battery life is worse than IceColdSandwich. Bothers me none. I prefer the stability (so far).
And is this with 3G activated or do you use WiFi all weekend? At home my battery lasts long, but when I leave and put 3G on, it's terrible. 2G is ok.
Verstuurd van mijn Desire S met Tapatalk
3g, data and WiFi all on. All weekend. I live in an area that requires 3g or I lose reception.
Upgrade
axelmasok said:
Hi everyone/anyone,
I can't post in the developer sections so I'd like to comment here then.
Have used IColdS on my Desire S for about 6 months as a work phone with heavy email and talk usage. The biggest pain was email not showing the email body and then not responding - alot. Every now and again other apps stop responding.
Anyway, I came back here and tried Jellytime as a random pick. Worked great after a week of use. Even USB tethering and Wifi hotspot works. Apart from the 5mp camera photo issue and Bluetooth not working at least email and general stability is good. The 2 issues are known and being worked on. Great upgrade I think and extended the life of the old girl a little longer.
Axel
Click to expand...
Click to collapse
Some of the custom rom builds like the one build by @blindndumb (jelly time 4.2.1) has a new release every third day. Is it possible to upgrade to latest release over the air if u have previous release on the device?
I'm not sure. I would probably update from recovery myself.
Cheers
battery
The battery life in JellyTime is great.
maxmax195 said:
The battery life in JellyTime is great.
Click to expand...
Click to collapse
Yes I see that there is a new version as of a few days ago. I'll update to it this weekend and hopefully enjoy Bluetooth and better battery life. As it stands with JellyTime R.4.0 the battery lasts me 7:30am to about 7pm before the battery goes into red < 20%. Can't complain but it used to be better.
Ah also, some users reporting their phone locks up requiring the battery to be removed. This has happened to me about 4 times. I'm pretty sure every time it happened when I rebooted or powered off/on the Desire S. I'm not keen on removing the battery but waiting for 10min or so it wouldn't reboot itself. Holding down all the buttons didn't work either. I might try connecting via adb next time it happens.
I just changed to Jellytime from Icecold sandwich. I'm having a problem with AOSP roms. Taking screenshot in some screen seems impossible unlike sense roms where u just need to push POWER +HOME to take screenshots. on AOSP roms, i cant take screenshots of a zoomed pic,zoomed webpage etc. anyone knws any app that can assign keys to take screenshots?
its_Khal said:
I just changed to Jellytime from Icecold sandwich. I'm having a problem with AOSP roms. Taking screenshot in some screen seems impossible unlike sense roms where u just need to push POWER +HOME to take screenshots. on AOSP roms, i cant take screenshots of a zoomed pic,zoomed webpage etc. anyone knws any app that can assign keys to take screenshots?
Click to expand...
Click to collapse
I just tried it then with JellyTime and it works here bud.
Held down volume button and then held down power button until the screen shot captured. Worked fine.
I have also had the one earphone side only issue. Only when I have answered the call and then plug the earphones in. I work around that by selecting loudspeaker on then off. Then I can hear audio in both earbuds.
Cheers
axelmasok said:
I just tried it then with JellyTime and it works here bud.
Held down volume button and then held down power button until the screen shot captured. Worked fine.
I have also had the one earphone side only issue. Only when I have answered the call and then plug the earphones in. I work around that by selecting loudspeaker on then off. Then I can hear audio in both earbuds.
Cheers
Click to expand...
Click to collapse
Worked great!!!! Thanks buddy!
Sent from my Desire S using xda app-developers app
Jellybean ASOP Feedback
as other users i don't have the rights to write on the dev threat to report issues and experiences, then lest do it here.
Upgraded from Saga to ASOP jellybean a week ago, the process pretty strain forward and no issues.
Bugs I've found so far:
- The battery drains very quick (less than 24h on normal use), despite of the settings on not altered from default ones.
- The wifi and phone signal meter it's showing very low values, but no issues or loss of signal at all, seems more like a signal meter calibration.
- The proximity sensor when on call in progress is not working, i mean, display doesn't turn off and the ear can mess up with commands on the phone screen.
-Time to time background apps (google now, google +, swift keys) crashing and restarting, no loss of data noticed.
-Some random problems when shooting videos.
In general the ROM is very responsive, a big improvement from ICS, and can be used for a daily basis, still need to be improved but stable enough to adopt it.
JellyTime feedback too
Hi,
I can't write to dev section, so here's my problems with JellyTime. I can't adjust screen lights, buttons change but there is no diffrence. I have MDDI panel, so it might be related to it. Thanks again to pointing it out. Battery drains a little bit faster than I expected, but it's generally really good and stable ROM.
ROM: JellyTime R6.1 - Saga Edition
aliegm said:
as other users i don't have the rights to write on the dev threat to report issues and experiences, then lest do it here.
Upgraded from Saga to ASOP jellybean a week ago, the process pretty strain forward and no issues.
Bugs I've found so far:
- The battery drains very quick (less than 24h on normal use), despite of the settings on not altered from default ones.
- The wifi and phone signal meter it's showing very low values, but no issues or loss of signal at all, seems more like a signal meter calibration.
- The proximity sensor when on call in progress is not working, i mean, display doesn't turn off and the ear can mess up with commands on the phone screen.
-Time to time background apps (google now, google +, swift keys) crashing and restarting, no loss of data noticed.
-Some random problems when shooting videos.
In general the ROM is very responsive, a big improvement from ICS, and can be used for a daily basis, still need to be improved but stable enough to adopt it.
Click to expand...
Click to collapse
I did a complete wipe/format of everything before install of 6.1.
- Battery drain seems normal to me coming from ICS
- Wifi and Network levels look and behave normally for me
- The proximity weirdness was apparent to me and solved after installing the Sweep2Wake app and disabling.
- I get no crashing of any apps. None since moving to Jellytime 4.x and now 6.1. I don't have any games. Just news/weather/email/web apps.
- I must admit I don't film videos. The camera and video control is so slow and clumsy I don't bother.
Sounds like your issues all relate to something local with your phone IMO.
Hemmodeli said:
Hi,
I can't write to dev section, so here's my problems with JellyTime. I can't adjust screen lights, buttons change but there is no diffrence. I have MDDI panel, so it might be related to it. Thanks again to pointing it out. Battery drains a little bit faster than I expected, but it's generally really good and stable ROM.
ROM: JellyTime R6.1 - Saga Edition
Click to expand...
Click to collapse
I'm not sure what you mean. The backlight/LCD brightness? Works fine for everyone else. If you have the Sony LCD then your in another boat altogether and yes I'm pretty sure changing brightness doesn't work which will make your battery life interesting. eBay out your phone and buy find another one there if your a fan of the Desire. Otherwise upgrade to another model.
Hi, i did not find any related to my problem, that's why i am opening this thread.
I did a brick on my tf700 at last September and the cheapest solution it was to buy a new board on ebay.
i did the replacement that it was easier than i supposed and it started to work like new, like the first time the system ever boot.
After some days i did again unlock and install cromix and during several weeks it was perfect until yesterday when I detected that it was not good WiFi.
It is like half of intensity compared with htc one. Just works up to 8m from router.
I open it again to verify contacts, board. Everything is normal.
Do anyone know about antenna problem on tf700 (on my last prime it was a lot)? or hardware problem that in a moment reduced the intensity, if it was no WiFi at all i understood as a hardware problem, but half is strange.
Another thing is sound. When i started tf700 no sound, just on phones. After some hours (from night to morning) tablet working, sound appear.... i don't understand.
I tried different firmwares, now i am on cmb 4.3, and it is the same.
Any help?
antonio3073 said:
Hi, i did not find any related to my problem, that's why i am opening this thread.
I did a brick on my tf700 at last September and the cheapest solution it was to buy a new board on ebay.
i did the replacement that it was easier than i supposed and it started to work like new, like the first time the system ever boot.
After some days i did again unlock and install cromix and during several weeks it was perfect until yesterday when I detected that it was not good WiFi.
It is like half of intensity compared with htc one. Just works up to 8m from router.
I open it again to verify contacts, board. Everything is normal.
Do anyone know about antenna problem on tf700 (on my last prime it was a lot)? or hardware problem that in a moment reduced the intensity, if it was no WiFi at all i understood as a hardware problem, but half is strange.
Another thing is sound. When i started tf700 no sound, just on phones. After some hours (from night to morning) tablet working, sound appear.... i don't understand.
I tried different firmwares, now i am on cmb 4.3, and it is the same.
Any help?
Click to expand...
Click to collapse
If you use a different rom and you still have the same problems, then you may have a defect motherboard..
You can try to install a stock rom to verify the issues that you have. If you still have the problems, then you can confirm that you have a bad board.. Good luck..:fingers-crossed:
LetMeKnow said:
If you use a different rom and you still have the same problems, then you may have a defect motherboard..
You can try to install a stock rom to verify the issues that you have. If you still have the problems, then you can confirm that you have a bad board.. Good luck..:fingers-crossed:
Click to expand...
Click to collapse
I already ordered another board from other guy.
My doubt is if the problem is at the ROM level, or kernel level.
Is not possible to take a log to see what Android reports at startup for sound and WiFi?
antonio3073 said:
I already ordered another board from other guy.
My doubt is if the problem is at the ROM level, or kernel level.
Is not possible to take a log to see what Android reports at startup for sound and WiFi?
Click to expand...
Click to collapse
Did you do a clean installation of your rom? If you flashed different kernels, you may have messed up the wifi modules.
Or it is another bug that has been discussed lately in the CROMi-X forum. If you turn wifi off and then on again: Does that change anything?
Some people had bad download speed when waking from sleep, whereas it was fine on a fresh boot or after toggling WiFi on/off.
If that is your problem, try turning off WiFi Optimization in the WiFi settings.
Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
What app are you using? This looks like a bug in an app, than in Android itself.
I had this problem even before installed any apps. In android l developer preview I didn't have sensors also, so after installed final version of lollipop the first thing I made was check sensors. On kitkat everything worked perfect.
Wysłane z mojego Nexus 5 przy użyciu Tapatalka
i don't have light and proximity sensors too...
i did full wipe and flash stock OTA
hope they will fix it soon
Since upgrading to Lollipop my proximity and light sensor also stops working after a few minutes. It works again after a restart, but only for a few minutes.
I have flashed 4.4.4 again and the problem is not present there. After upgrading to 5.0 again the problem came back.
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
gamer.11 said:
the apps are the issue here gentlemen.
1.On call as you bring your phone to ear, screen turns off?Proximity working
2.Adaptive brightness enable and use the phone on same brightness settings in bright and dim areas, screen brightness intensity change?Light sensor working.
3.Screen rotates views?Accelerometer working.
4.Play asphalt or any other motion requiring game, car turns?Gyro working.
5.Open maps, get pointing direction?compass working.
6.Use pedometer, counter change?step counter working.
Click to expand...
Click to collapse
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
m4nic4ndroid said:
No sir, it's definitely not the apps in my case. After a restart the light and proximity sensors work as expected, but a few minutes later they stop working. I could confirm this with the Sensor Box app as well as with no's 1&2 in your post.
I noticed it first because my adaptive brightness did not work and the screen did not switch of in call. I only installed Sensor Box to see if the sensors still work, this confirmed that they actually stop working and that it is not a calibration issue because Sensor Box shows no reading from these sensors.
This is definitely an issue with Lollipop because I flashed 4.4.4 again and everything worked fine confirming that it is not hardware, but after once again upgrading to 5.0 the sensors stop working few minutes after the phone starts up.
Click to expand...
Click to collapse
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I haven't tried any other Lollipop ROMs, I thought about it and I might actually give it a go to see if the problem persists on other ROMs as well, but I would prefer to have stock Android running on my phone, so I'm really hoping for a fix from Google. I'm on few other threads about the same issue, so I know there's a lot of people with the same problem. I had this on the dev preview as well.
gamer.11 said:
That's interesting, have you tried any other custom roms or kernels based on lollipop? I know that is a long shot or even that best advice but could you, or have you checked on other roms?
SO only your Proximity and light sensor the issue? Or all the other sensors a bust?
Click to expand...
Click to collapse
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Light Sensor & Proximity Sensor Error
m4nic4ndroid said:
I have tried Code-Blue kernel as I have heard it's a good one, but the problem is still there. I might try a different ROM in the near future.
For me it is only the Light and Proximity sensors, all other sensors work 100%
Click to expand...
Click to collapse
The Same Problem For Me As Well, My Light Sensor & Proximity Sensor Arent Working. I have downloaded the Final Image from Google Website for 5.0 hammerhead. But still the problem persists.
Nyk
After I got the Play services (with secure locations) update two days ago my light and proximity sensors are gone too. They will work for a while after reboot, but eventually they die.
All other sensors are working fine and only other updates have been to Skype, SwiftKey and TuneIn Radio.
Edit: I'm on stock OTA, no root and never unlocked the bootloader.
Sent from my Nexus 5 using Tapatalk
So uninstalling the play services update resolve the issue? I'm back to KitKat as without light sensor I find uncomfortable to use the phone. Will await the fix before moving to lollipop..
Sent from my Nexus 5 using XDA Free mobile app
"Clean install" using factory images? I did, no issues here.
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Did you reboot after disabling update?
Sent from my Nexus 5 using XDA Free mobile app
rawimage said:
It seems to be working until I get a phone call, after that the sensors will die.
Have uninstalled the Play services update now and the phone has been up and working 100% for a little more than 4 hours now. Will try to make a phone call to see if it still works after that.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Uninstalling Play Services and Play Store update made no difference here. Problem still persists.
michalnied said:
Hello,
After clean install Android 5.0 on Nexus 5 I have lost all sensors.
Do you have similar problem?
Is there any solution to fix it?
Click to expand...
Click to collapse
Hi I have the same problems . Sensors are working after restarting my phone random time. Also you can read here
Uninstalling Play services didn't do it for me either. Sensors work for approximately 4-5 hours then they die.
Sent from my Nexus 5 using Tapatalk
Installed Play services update again after a few days and now my phone has been running fine for 50 hours with all sensors working 100%.
Sent from my Nexus 5 using Tapatalk