Related
I suspect that this is related to the many issues with the compass and may be common. Maybe not, though.
I have turned off orientation-mode in the settings because of the inconsistency in getting the phone to go orient properly.
Sometimes, I turn the phone and it goes nicely into landscape and sometimes not.... other times, I turn and nothing happens.
There is a serious lag.
Now, yesterday I applied RyanZA's lag fix and will be turning on orientation rotation to see if it works better, but nonetheless, I wanted to start a discussion and see if others had experienced this.
No problems with mine yet. Although sometimes I feel that the sensors are too sensitive. Nothing to irritating though.
Hello,
apart from several software issues i have following hardware issues:
- vibration stops working from time to time, especially when not having used the device for a day or long. If you shaked the phone it would start working again.
- rotation sucks, as the proximity/acceleration sensor seems to be calibrated wrongly, as apps which need the sensor do not work properly (such as car racing --> car goes for one side though the phone is hold horizontally exactly) or display switches orientation too early/late
- If I used Google maps the blue thing points in a wrong direction (maybe 45°)!
Anyone same there?
stephan902 said:
Hello,
apart from several software issues i have following hardware issues:
- vibration stops working from time to time, especially when not having used the device for a day or long. If you shaked the phone it would start working again.
- rotation sucks, as the proximity/acceleration sensor seems to be calibrated wrongly, as apps which need the sensor do not work properly (such as car racing --> car goes for one side though the phone is hold horizontally exactly) or display switches orientation too early/late
- If I used Google maps the blue thing points in a wrong direction (maybe 45°)!
Anyone same there?
Click to expand...
Click to collapse
Do you still have the stock rom on it if so have you tried a restore to factory after its a call to dell
lufc said:
Do you still have the stock rom on it if so have you tried a restore to factory after its a call to dell
Click to expand...
Click to collapse
Yes and yes. Still the same. So i really got a lemon and the Streak usually is a good device?
The vibration issue certainly is a hardware issue that I would replace my phone over, it sounds like a physical problem with the motor, and bad motors only get worse with age.
Sent from my Dell Streak using XDA App
I have felt my vibration button fade or lag at times. Not sure if that was normal. I had it sometimes where it wouldn't work at all. I did a factory reset and all seems to work ok. I still get the laggy vibration when to many processes going on at the same time.
Sent from my Dell Streak using XDA App
I'm having a couple of issues / annoyances that I cannot seem to find fixes or work arounds for.
Are these normal things that everyone is experiencing or is it a problem just with my N4, and may need to be replaced?
My phone is stock, and un-rooted.
1. Camera (main) continuously refocuses when in camera app. It only locks for a few seconds after taping the screen. A bit annoying but workable. The problem arises in Skype (and I guess in any other app), when using the main (back) camera it continuously focuses and refocuses every couple of seconds which makes it almost useless when trying to use the main camera to show the person on the other end something.
Is there a way to lock the focus, or tweak how often it refocuses?
2. Light sensor sensitivity: When brightness is set to auto, the brightness bumps up and down every minute or 2. The sensor is too sensitive or the software is too aggressive. I'm stationary and lighting in the room is constant, but I guess slight angle changes in my hand are causing enough fluctuations to initiate an adjustment. And the adjustments aren't smooth, they are steps, so they get annoying after a while.
Besides switching off auto brightness, is there a way to tweak sensor sensitivity?
bump.
no one else has these issues or is annoyed by them?
trent25 said:
bump.
no one else has these issues or is annoyed by them?
Click to expand...
Click to collapse
I have the focusing issue too. In Camera if I tap the screen to focus on something, it stays there for 3-4 seconds and then re-focuses at the center of the screen. Very annoying.
For the light sensor, I found that the automatic brightness was awful so I changed to manual brightness. Easier than tweaking I guess
about the camera, i've got the same issues as you
Ok thanks for the replies. At least I know I'm not having a one off issue particular to my unit.
Both of these issues should be software related, hopefully they will come to someone's attention and get sorted out. They're not deal breakers but annoyances that shouldn't be there in a final product imo.
Google is working on a patch for the camera right now. Sit tight and we should have a fix coming soon
spitefulcheerio said:
Google is working on a patch for the camera right now. Sit tight and we should have a fix coming soon
Click to expand...
Click to collapse
Where did you hear that from?
Sent from my Nexus 4 using xda premium
I have two SGS4's. On one, when I place a call, the call screen stays on and it turns off when I raise it to my ear. It then turns on when I pull it away.
On the other, as soon as I place I call the screen goes dark. The only way to get it back is to push the power button and unlock the phone.
The "Turn screen off during a call" setting is set on both phones.
Anyone have any idea what is causing this? Next step is to do a wipe, but that just sucks.
I'm on stock and not rooted.
Thanks!
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Sirchuk said:
Have you tried doing a reset yet? I'm hesitant since it's a pain to restore everything the way I like it. Definitely a weekend task.
Click to expand...
Click to collapse
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
jprocket45 said:
I have done a reset it solved it a little I guess but still having issues once in a great while all works well id blame it on the otterbox case but my wife has one so dunno if that could be the issue you have a case on urs never really played with the phone outside of the case lol
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
Nope, mine is naked for now. I'll have to do a reset today/tomorrow and see if that solves my issue. If not, I'm taking back to the store for an exchange. It's only been a couple of weeks.
To late for me to take it back but suppose to be a update coming soon that does alot of fixes so we will see Good luck like I said reset I did notice fixed it a bit let me know how it goes I'm threw sprint just curious if you have them only reason I ask if it's just a carrier issue with software or something I doubt it but just figured to see who you had lol
Sent from my SPH-L720 using xda app-developers app
Dial *#7353# and make a test
sent from my Galaxy
samersh72 said:
Dial *#7353# and make a test
sent from my Galaxy
Click to expand...
Click to collapse
That's what I was looking for!
Sure enough,the proximity sensor was always on and wouldn't go off.
I'm with T-Mobile and they have a 30 return/exchange policy if you buy it outright, which I had, so it only took about 10 minutes for them to exchange it!
Thanks for the testing code! XDA comes through once again!
Same problem when I'm making a call, the screen goes blank when I put it to my head and when I remove it nothing happens.
I tried *#7353# and the proximity sensor goes of but will not stop..
I'm currently rooted, could it solve the problem to go back to stock?
Possible Fix
jprocket45 said:
Sadly I have the same issue on mine but not my wifes.... hope somebody knows something or maybe the rumored update thats going to be coming out will have a fix?? I dunno...
Click to expand...
Click to collapse
I have had the same problem over the last 3 weeks and decided to take a gamble. I tightened up all the screws on the device and squeezed real hard on the area where the prox sensor is and poof... it works. I have no idea what was up but I feel like the sensor is loose and the pressure resolved the issue. Many other post have talked about cleaning the area over the prox real good and it works but I think its the pressure that is actually fixing the issue. Anyone else have any ideas? Sorry if this was posted incorrectly, I have never posted before but I felt this issue is a PITA.
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
My proximity sensor works - when I go into diagnostic, it goes green when I bring a hand near the sensor - my issue is that it doesn't seem to notice when I remove my hand and there no longer is anything proximal - until I hit the back button to exit the test. Other than blowing out the earphone jack, does anyone have a suggestion?
Thx.
divche said:
I have i9500. Unrooted with latest OTA update installed (Build XXUBMG1).
I've been having the same problem with proximity sensor. When proximity sensor is enabled during phone calls (both regular calls and Viber calls), the screen is disabled. Also, my screen sometimes remains on during the call until I place it to my ear and sometimes it turns off immediately during the call. It wasn't always like this, but I can't remember when it started happening, but I suspect it was since the last OTA update.
I've searched around online and have noticed several comments.
Apparently this is an issue with several Galaxy models over the years (sorry, I lost the reference) and this thread: http://forum.xda-developers.com/showthread.php?t=2208440&page=2 mentions Galaxy Note 2 and SGS3 having the issue where there is something wrong with the threshold setting in the calibration settings. Mine appears to have the same issue where it always reads 0cm (i.e. always covered). However this thread also suggests a fix to input some code to adjust the calibration if your phone is rooted.
One suggestion is there is a misalignment of the sensor and so it might be partially covered by the phone's front fascia, causing the sensor to always read as covered or "1" or 0cm. But looking carefully at mine, it looks centred dead-on.
This thread http://forum.xda-developers.com/showthread.php?t=2417401 indicates that the sensor is always on as can be seen through a digital camera LCD (but not with your naked eye). I've tried this with my DSLR and confirmed this also happens with mine, even when the option is set to turn it off during calls, and also even when air gesture (which uses the prox sensor) is turned off. Not sure if this affects the problem or not though.
Can't remember where I read this, but someone mentioned that when shining a bright light over the phone, it works. So I downloaded two sensor apps from Google Play: Android Sensor Box, and Proximity Sensor Finder. And also used the inbuilt *#7353* feature. All three report that my proximity sensor is always reading that something is constantly covering it..... EXCEPT when a bright light (the sun works) is shining on the light sensor - not the proximity sensor. I tested this by using a torch on both sensors. When blocking light from the light sensor, the problem persists, but not when I allow the light to shine on the sensor. So it appears that they both act in unison.
Similar issue with air gestures, which used to work when my phone was new, even in relatively ambient light (but obviously not in a dark room), but now doesn't under similar conditions, and again... EXCEPT when a bright light is shining on the light sensor, or when I'm out in the sun.
Anyway, I'm not willing to root my phone at this point, just to try the fix suggested in http://forum.xda-developers.com/showthread.php?t=2208440&page=2 (my phone was bought overseas and returning it wouldn't be convenient for me). And since this wasn't always a problem with my phone, I suspect it is a software problem related to one of the recent OTA updates.
Edit: After further testing, it seems that air gestures use the front camera as well as the light and proximity sensors.
Click to expand...
Click to collapse
Proximity sensor
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
I guess what it comes down to is.....for some you can reset the sensor, for some they can blow it out with compressed air, but others actually have to take apart their phone to fix this issue.
marduj5 said:
I had problem with proximity sensor in my galaxy s3 mini but my rear camera had error and fc also.I tried everything and nothing work.Finaly I open device and disconect camera and connect it again and camera started to work.But for my suprise proximity sensor now works perfect and I did not touch it.I can't explain what happend but I am happy.
Click to expand...
Click to collapse
hi
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Shohat said:
i have the same problem. any solution guys ?
( BTW - im on NB3 INS firmware )
Click to expand...
Click to collapse
Hubris2 said:
I think I summarized the available solutions just before your post. There is no single thing which always works, you'll need to go through and see which fixes yours. This happens primarily because of hardware, with the sensor getting dirty - so it comes down to how invasive the procedure to clean it.
Click to expand...
Click to collapse
i'm sorry. i already tried your first solution and it worked like charm ! thank you ! :good:
HOw to solve, none of this works. How cann i clean proximity?
I'm sure most are familiar with proximity sensor issues in calls on 4.2.2 roms. It appears that everyone's experiences differ a bit. I've seen some say that buttons are pressed when the screen is off. For others, and myself, the screen doesn't turn off.
When I first moved to 4.2.2, I was pleased to find the Xposed module that fixes the issue. However, after I activated it, I had a black screen issue. During calls (if more than a few minutes), the screen/device would become completely unresponsive (temporarily). It wouldn't even respond to a long press of the power button. I attributed this to the xposed module and turned it off.
Unsurprisingly, the original issue resurfaced. I noticed that it seemed more pronounced when receiving a call (and the device was previously idle). It seemed as though the device wasn't waking up the proximity sensor when calls were received. I created a Tasker profile (with Secure Settings) to execute a "wake device" action when phone calls (incoming) are detected. It has been a week since I created this, and I haven't seen the problem since.
For anyone still experiencing the issue, this may be a solution.
EDIT: Solution quoted below.
CrazyTrond said:
If your screen doesn't turn off during a call and your ear is pressing buttons it means your sensor is not working. On my phone it works again after a reboot but after some time stops working again (you can check with android sensor box from play store). I found a fix that works, described in this post: http://forum.xda-developers.com/showpost.php?p=44872536&postcount=206
Click to expand...
Click to collapse
Simba501 said:
....It seemed as though the device wasn't waking up the proximity sensor when calls were received. I created a Tasker profile (with Secure Settings) to execute a "wake device" action when phone calls (incoming and outgoing) are detected. It has been a week since I created this, and I haven't seen the problem since.
For anyone still experiencing the issue, this may be a solution.
Click to expand...
Click to collapse
Interesting solution, this drove me crazy on a 4.2.2 ROM..... I'm on 4.3 now, and thankfully the issue isn't present. I really hope AT&T will stumble up to an official 4.3 release and skip 4.2.2.
Only experienced this on 4.1.2, all 4.2.2 roms have been fine for me
Galactus said:
Only experienced this on 4.1.2, all 4.2.2 roms have been fine for me
Click to expand...
Click to collapse
Funny. It was the opposite for me.
Sent from my HTC One
I'm on stock 4.2.2 and I have no proximity sensor issues. I've had some issues on 4.1.2.
Everybody has the proximity sensor issue: plug in the headphones, cover the sensor, make someone call you, after the call, the screen will wake. That will happen in your pocket, which is very bad. The only solution that works for me is copas' proximity tool extension (on Google play), which I enable every time I am using headphones...
Sent from my HTC One using Tapatalk 4
If your screen doesn't turn off during a call and your ear is pressing buttons it means your sensor is not working. On my phone it works again after a reboot but after some time stops working again (you can check with android sensor box from play store). I found a fix that works, described in this post: http://forum.xda-developers.com/showpost.php?p=44872536&postcount=206
No, you didn't understand. Sensor works during phone call. After hanging up, either the other party hangs, or you via the headphones button, screen turns on. This is a bug in all HTC devices, as far as I know. Try it. Make someone call you, cover the proximity sensor with your fingers, tell them to hang up, while still covering the sensor (simulating the phone is in pocket or bag) and see what happens. Screen will turn on.
Sent from my HTC One using Tapatalk 4
---------- Post added at 12:11 PM ---------- Previous post was at 12:10 PM ----------
Otherwise my proximity sensor works perfectly, never had a problem with it.
Sent from my HTC One using Tapatalk 4