Related
I have noticed recently (perhaps related to the .21 update?) that Google sky was not tracking well with my movements... so I tried 2 compass applications to validate the e-compass performance.
The compass behavior is really squirrely and seems to have very little correlation to which direction the tablet is pointed.
It seems that the compass must have worked better in the past as Google Sky used to work great.
Can anyone else report if their compass is working properly? What app did you use to verify it? What orientation did you hold your TFP to get a good result?
Mine has never worked correctly, and I've been trying off and on since I first got it in December, before any official ICS update was even released. I always assumed it was related to the poor GPS performance.
nategodin said:
Mine has never worked correctly, and I've been trying off and on since I first got it in December, before any official ICS update was even released. I always assumed it was related to the poor GPS performance.
Click to expand...
Click to collapse
Exactly the same for me. And I have the (same) prime ever since December as well.
MNDaveC said:
I have noticed recently (perhaps related to the .21 update?) that Google sky was not tracking well with my movements...
Click to expand...
Click to collapse
No change (for better or worse) with .21 or ... ever
MNDaveC said:
It seems that the compass must have worked better in the past as Google Sky used to work great.
Click to expand...
Click to collapse
It never worked reliably. I'm sorry but I am skeptical about your statement "worked great". Search this forum for my posts mentioning the e-compass as almost unusable.
I once had fun watching the compass readings constantly revolve, making full 360 deg sweeps in just a little over a minute (sic!). A recalibration brought back the unreliable, miserable readings.
Yes this is a problem. But can be fixed by a simple step. Just move, rotate your tab in all directions (up down, left right and on its own AXIS)
This should fix the compass. In my case, thus would fix it but would revert back
Sent from my GT-I9100 using Tapatalk
I also confirm twitchy e-compass... no new news here though, it is all related to our known problems.
Sent from my Transformer Prime TF201 using Tapatalk
Make sure you do not have mock locations enabled in the developer settings....This throws off the compass
google skymap sucks for me too. I'll double check to see if mock locations is on, I don't think it is, I've fiddled with all the skymap settings with no results.
I have to calibrate my compass using GPS Status every time I want to use it. After that, it seems to work fine.
There seems to be a problem with keeping calibration settings for the compass after each reboot...
These e-compasses do not use the magnetic field to give direction. They totally rely on GPS. GPS accuracy requires movement. The compass gets 2 (or more) readings, and then caculates the location and direction from them.
Even a good GPS device like Garmin, will have difficulty. If you are stationary, the gps reading will vary. The best accuracy for consumers is about 10 ft. If you had a test app, and were stationary....you would see that the individual gps readings are grouped in about a 10 ft radius from your position, with a few being outside that.
robertg9 said:
These e-compasses do not use the magnetic field to give direction. They totally rely on GPS. GPS accuracy requires movement. The compass gets 2 (or more) readings, and then caculates the location and direction from them.
Click to expand...
Click to collapse
Please stop diffusing inaccurate information.
Prime is equipped with a physical magnetometer. PERIOD.
You can try to recalibrate the compass by moving the device in a large figure of eight in a horizontal plane, outside and away from any ferrous metal.
Also, beware of any magnetic devices, fastenings or closures in protective cases you might buy. Don't park your Prime on a convenient HiFi loudspeaker top!
FG
ForeignGadger said:
You can try to recalibrate the compass by moving the device in a large figure of eight in a horizontal plane, outside and away from any ferrous metal.
Also, beware of any magnetic devices, fastenings or closures in protective cases you might buy. Don't park your Prime on a convenient HiFi loudspeaker top!
FG
Click to expand...
Click to collapse
The Prime's keyboard itself has a magnet in it, and I'd imagine the Prime does as well to register that field so that the screen shuts off when you close it.
But yes! Keep your Primes off of awesome speakers lol, as well as all your other precious electronics
I haven't actually played with the compass all that much as I've fretted over WiFi/BT and GPS. I know that my accelerometer consistently feels off: until I actually run tests on it. I think many of our issues (outside of the aluminum body and bad choice in wireless module) really are drivers and apps' implementations of h/w as opposed to the h/w itself.
robertg9 said:
These e-compasses do not use the magnetic field to give direction. They totally rely on GPS. GPS accuracy requires movement. The compass gets 2 (or more) readings, and then caculates the location and direction from them.
Even a good GPS device like Garmin, will have difficulty. If you are stationary, the gps reading will vary. The best accuracy for consumers is about 10 ft. If you had a test app, and were stationary....you would see that the individual gps readings are grouped in about a 10 ft radius from your position, with a few being outside that.
Click to expand...
Click to collapse
I do not know why the hell you would post this. The meter does detect magnetic fields. Why do you think they call it an ecompass. Put a magnet close to it and open a compass app. Even your GPS explanation is horrible and incorrect.
sorry I just hate when people give out stupid info
Sent from my ADR6300 using xda premium
ForeignGadger said:
You can try to recalibrate the compass by moving the device in a large figure of eight in a horizontal plane, outside and away from any ferrous metal.
Also, beware of any magnetic devices, fastenings or closures in protective cases you might buy. Don't park your Prime on a convenient HiFi loudspeaker top!
FG
Click to expand...
Click to collapse
Okay I have read this and tried on an android phone with no success. Just to clear things up, do I keep the prime oriented the same way through the figure eights or point it through, kinda like a kid playing with a toy car driving in a figure eight. Also do I keep the prime horizontal as well? sorry to sound like a dolt, but I can see many ways to do a figure eight with the prime. Your Horizontal plane was a help.
As far as I know, just keep the device pointing the same way and horizontal.
If your compass does not respond to this, I suggest it might be stuffed.
FG
I had a bunch of requests for Wave Control to have this functionality. I thought it best to do a dedicated app so here it is!
Flip Case Control was designed to work with Samsung's Flip Case on the I9300 while using as little battery as possible. (I left it running all night ~8.5 hours and the battery dipped 1% more than usual)
IMPORTANT: If your case is black or dark on the inside, the sensor doesn't read correctly when the case is closed. To fix this, put a piece of light colored tape on the inside of the case where it lines up with the sensor (located next to the front camera)
Note: A Samsung based ROM is required. CM won't work well.
Here's a demo video:
Play Store Links:
24 Hour Trial Version
Full Version
Could you guys with the Flip Case test it out?
All feedback is appreciated greatly!
I would like to try it for you but unfortunately i don't have flipping cover for this lovely device as it is not here yet everyday im searching everywhere but nothing
Waiting OP to give us their opinion about this app
Sent from my GT-N7100 using Tapatalk 2
I have the combination.Let me try it and i ll report back
edit: works fine with stock rom and flip case.
Sent from my Galaxy Nexus using Tapatalk 2
afilopou said:
I have the combination.Let me try it and i ll report back
edit: works fine with stock rom and flip case.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Great, thanks for letting me know!
Is there something special about Samsung's Flip Case? I have a generic flip case but can't get this to work. Running rooted Deodexed LJ1.
dosher said:
Is there something special about Samsung's Flip Case? I have a generic flip case but can't get this to work. Running rooted Deodexed LJ1.
Click to expand...
Click to collapse
There shouldn't be but it is conceivable that if the case surface facing the proximity sensor is black and absorbs too much of the IR from the LED on the prox sensor then it wouldn't register a near reading.
The proximity sensor is an IR LED and light sensor. It detects distance by the amount of IR light that get reflected back off the surface in front of the sensor.
If this is the case, you could try to put a piece a light colored tape on the inside of the case where it lines up with the sensor.
Let me know if this works. What's brand of your case?
MarksThinkTank said:
There shouldn't be but it is conceivable that if the case surface facing the proximity sensor is black and absorbs too much of the IR from the LED on the prox sensor then it wouldn't register a near reading.
The proximity sensor is an IR LED and light sensor. It detects distance by the amount of IR light that get reflected back off the surface in front of the sensor.
If this is the case, you could try to put a piece a light colored tape on the inside of the case where it lines up with the sensor.
Let me know if this works. What's brand of your case?
Click to expand...
Click to collapse
I bought the full version ystd. Yes it does work sith my rock flip case but i had uninstalled ot as it does turn off my screen for no obvious reason when im using it.
Hopefully you can come up with a fix for it soon
MarksThinkTank said:
There shouldn't be but it is conceivable that if the case surface facing the proximity sensor is black and absorbs too much of the IR from the LED on the prox sensor then it wouldn't register a near reading.
The proximity sensor is an IR LED and light sensor. It detects distance by the amount of IR light that get reflected back off the surface in front of the sensor.
If this is the case, you could try to put a piece a light colored tape on the inside of the case where it lines up with the sensor.
Let me know if this works. What's brand of your case?
Click to expand...
Click to collapse
It's a cheapo from ebay until I can find a decent one...
http://www.ebay.co.uk/itm/Samsung-G...sPouches&var=540094094344&hash=item4d05abf35b
But you're right - the sensor doesn't like black. If I use a piece of lighter coloured tape on the inside of the cover it works! The only issue I have now is that the app is not auto loading at boot.
Jaemon said:
I bought the full version ystd. Yes it does work sith my rock flip case but i had uninstalled ot as it does turn off my screen for no obvious reason when im using it.
Hopefully you can come up with a fix for it soon
Click to expand...
Click to collapse
I'm working on an update right now to help reduce the unintentional triggers. I need to test it a little bit more but it should be out soon.
dosher said:
It's a cheapo from ebay until I can find a decent one...
http://www.ebay.co.uk/itm/Samsung-G...sPouches&var=540094094344&hash=item4d05abf35b
But you're right - the sensor doesn't like black. If I use a piece of lighter coloured tape on the inside of the cover it works! The only issue I have now is that the app is not auto loading at boot.
Click to expand...
Click to collapse
Are you running the full version? I limited that function to that version. Great to hear the tape fix worked
According to me proximity autolock works well and it is available on play store
Sent from my GT-N7000 using xda premium
It works OK at the moment, I think the sensitivity should be decreased though as something passing an inch or two above the proximity sensor will still turn off the screen. Seeing as flip covers get up close and personal with the proximity sensor this seems a bit too sensitive.
EDIT: Definitely too sensitive, seems to turn off at random at times. Just had a phase where it wouldn't let me keep the screen on.
Maybe a failsafe of sorts could be implemented? Leave the screen on until timeout/power button press if turned on by the power button?
Edit 2: I uninstalled the app to stop it turning the screen off constantly, but it continued even after a reboot, I went into the display settings and saw the screen timeout had been changed to "()"and this was causing the issue, as soon as I changed it back to 30 seconds it was fine. Is this supposed to happen?
MarksThinkTank said:
Are you running the full version? I limited that function to that version. Great to hear the tape fix worked
Click to expand...
Click to collapse
Yeah, just running the trial version - that explains it.
D3_ said:
It works OK at the moment, I think the sensitivity should be decreased though as something passing an inch or two above the proximity sensor will still turn off the screen. Seeing as flip covers get up close and personal with the proximity sensor this seems a bit too sensitive.
EDIT: Definitely too sensitive, seems to turn off at random at times. Just had a phase where it wouldn't let me keep the screen on.
Maybe a failsafe of sorts could be implemented? Leave the screen on until timeout/power button press if turned on by the power button?
Edit 2: I uninstalled the app to stop it turning the screen off constantly, but it continued even after a reboot, I went into the display settings and saw the screen timeout had been changed to "()"and this was causing the issue, as soon as I changed it back to 30 seconds it was fine. Is this supposed to happen?
Click to expand...
Click to collapse
Ah.. crap. I thought I fixed that bug before I released it. I guess there's still a way for that to happen.
I'm working on an update to help filter out false triggers and will patch that bug. It shouldn't happen. Sorry.
garvit18 said:
According to me proximity autolock works well and it is available on play store
Click to expand...
Click to collapse
Proximity Autolock is a nice app with some excellent features but uses too much battery on The Note 1, an additional 8% overnight. And it doesn't work well on my Note 2.
The app works well. I bought it
It's a very useful feature that Samsung should have built in, but hey, I don't mind supporting you.
Gnarfsan said:
The app works well. I bought it
It's a very useful feature that Samsung should have built in, but hey, I don't mind supporting you.
Click to expand...
Click to collapse
Thanks!
I agree Samsung should have made this app. When I first showed it to a friend, he said "Isn't it already supposed to do that?"
A Beta
Here's what I'm playing with right now.
It should hopefully fix the bug D3_ ran into as well as reduce the false triggers. There will still be some due to sensor placement but this should make it much less sensitive. Also response time to turn on the screen should be a little bit faster. It's working well on my I9300, hopefully it should be the same on the Note II.
Let me know if this is performing better for you guys.
Still coming:
Disable in Landscape Mode
Disable when plugged in
[Edit: Removed Old Beta]
Just installed the beta, will report back after some use of it.
V1.05
Just uploaded version 1.05 to the Play Store
Changes:
Reduced false triggers for screen off
Changed button UI
Added notice about dark cases
Updated icon
Sped up screen on response a little bit
Cant you just do this using Tasker? I already spent money on the flip cover, so kinda hesitant to spend more for this functionality (which should be there in the first place!)
Hey Guys,
First time Razr Maxx user here, after all of your input i've made the jump, thanks guys
I want to contribute a simple fix to you all, I've read that some people have their compass sensor stuck on one direction continuously, no calibration can solve it. I myself had this problem today, but it turns out it is fixable easily.
The cause:
The Phone (especially on the top right, right after the front cam part, where the sensor is located) gets too close with a magnetic object for a long period of time
The Tools needed:
Phone Tester app on Google Play Store
Small Fridge Magnet (Magnet doesn't have to be powerful, at least it will stick to fridge door or your PC case)
The steps:
Install and Open Phone Tester app, go to Sensor menu,
you'll find one of the axis is stuck at one value, mine was stuck at Axis X value at 1159.1 uT
Place the phone lying on the table, screen is upside
Place the magnet around the top right part of the phone (it is Maxx version but CMIIW on the standard one), right after the front camera part. You should see the stuck sensor axis fluctuates.
After 2-3 seconds, Remove the magnet, review the axis value again with moving around the phone.
Repeat step 4-5 until the axis value fluctuates continuously with your phone movement.
You're done
If the problem persists, please consult to the dealer, but the above fix was 100% successful for me so you should try it. Below is the attachment to describe which part should be attached with magnet for a while. Hope it helps
G'day!
Thank you, thank you very much.
It works.
Sent from my XT910 using xda app-developers app
In my case, most probably I got the 'stucked compass' syndrome, when I put the phone and earphones in my shirt's pocket. Since the earphones also have magnets, it may magnetized the metal in the phone's component, and affected the compass.
Actually I am almost going to send it to the Motorola service center for the repair, but, not need to. Thanks for the tip.
Thank you.
bahathir said:
In my case, most probably I got the 'stucked compass' syndrome, when I put the phone and earphones in my shirt's pocket. Since the earphones also have magnets, it may magnetized the metal in the phone's component, and affected the compass.
Actually I am almost going to send it to the Motorola service center for the repair, but, not need to. Thanks for the tip.
Thank you.
Click to expand...
Click to collapse
Nice to know it works well for you mate
Confirmed! This works. In my case it's undoubtedly caused by the magnetic lock of the pouch. You saved mi peace of mind, I was starting to think my Razr was defective. Thank you! (button pressed)
Excellent, it worked!
hansip87 said:
Hey Guys,
First time Razr Maxx user here, after all of your input i've made the jump, thanks guys
I want to contribute a simple fix to you all, I've read that some people have their compass sensor stuck on one direction continuously, no calibration can solve it. I myself had this problem today, but it turns out it is fixable easily.
The cause:
The Phone (especially on the top right, right after the front cam part, where the sensor is located) gets too close with a magnetic object for a long period of time
The Tools needed:
Phone Tester app on Google Play Store
Small Fridge Magnet (Magnet doesn't have to be powerful, at least it will stick to fridge door or your PC case)
The steps:
Install and Open Phone Tester app, go to Sensor menu,
you'll find one of the axis is stuck at one value, mine was stuck at Axis X value at 1159.1 uT
Place the phone lying on the table, screen is upside
Place the magnet around the top right part of the phone (it is Maxx version but CMIIW on the standard one), right after the front camera part. You should see the stuck sensor axis fluctuates.
After 2-3 seconds, Remove the magnet, review the axis value again with moving around the phone.
Repeat step 4-5 until the axis value fluctuates continuously with your phone movement.
You're done
If the problem persists, please consult to the dealer, but the above fix was 100% successful for me so you should try it. Below is the attachment to describe which part should be attached with magnet for a while. Hope it helps
G'day!
Click to expand...
Click to collapse
Thanks so much for this, I thought my compass had crapped out and now it's working perfectly.
Thanks!
Beautiful!! Easy solution that worked on both my wife's and my phones. Both were stuck and both now work. I have a geocaching app and we each have Google Sky Map, neither of which were working properly-until we used this extremely simple fix. One suggestion that I remember from my days in radio; rather than just set the magnet on the phone, move it around in circles for a few seconds as we used to do to degauze tapes for reuse.
Not certain but this didn't seem to work until I got the magnet to around the center right side of my RAZR (non Maxx) near the volume rocker. That seemed to unstick it!
:good:
Sometimes if my G5 has not been used for an hour or so, it is refusing to wake up from double tap, power button or volume button quick shortcut. Only plugging it in has seemed to wake it up on these occasions.
Has anyone else had this issue?
Not yet.
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Same problem, same case.
What I have found is if you pull the phone out of the case it wakes up. Thinking proximity sensor.
Sent from my LG-H830 using XDA-Developers mobile app
Yup. It really doesn't take much extra coding for them to allow the power button to "Always Wake" the device... I imagine there will be an update in the near future.
As for me... jumping ship to the S7 edge. I really liked the G3, and was hoping this phone could have been that for me... Well, not like I really swap batteries out often anyway
Same case. Same issue. Take the phone out of the case and throw a blanket over yourself and the phone. (Simulating night) and my screen unlocks easy peasy. Something about this lifeproof case. You would think this issue would have been caught in testing and QC.
Yes the phone has a built prox. override. But it only becomes an issue at night. Outside of the case I have no issues with prox. sensor.
I have experuenced this exact same issue with my g5. Whenever its in the dark the power button nor the double tap will wake the screen when in the lifeproof fre case. When out of the case the phone works just fine.
Word to the wise though if you have a zagg glass screen protector and drop your phone both the screen protector and the screen with shatter even if in the lifeproof case. I just experienced this and now have a replacement phone. Just a heads up.
soninja8 said:
I have also experienced this issue (opened a thread a week ago). I have the exact same lifeproof case and my problem occured at night as well. Phone did not want to wake up at all until I either restarted it or had some light in the room.
Click to expand...
Click to collapse
I have the rs988 variant and I have noticed this behavior when screen is in always on mode: if I suddenly change from light to dark by covering sensors, the always on clock goes out and nothing I do will allow it to wake up, until I allow brighter light again and the clock reappears. and I can use the double tap and power button again to see the screen. I also notice that the always on clock seems to have an auto brightness independent of the screen settings - I leave screen at 50% no auto brightness, yet I still see clock light levels dim in low light, One other thing - I notice that when I answer a call the screen blanks out (the way it is supposed to ) but does not reappear until I press the power button, just taking away from my ear does not bring display back; I also have the lifeproof case. and just removed it and verified my display now works when I take away from my ear; I just took some spray lens cleaner and cleaned all the surfaces of the phone and case with a microfiber cloth and put it back together and has vastly improved the issue, maybe gone, not sure yet. Update: seems like no matter how clean it is there is still a problem with the case doing something to the proximity detector, cleaning made it better. I can always wake up with the power button for the calling screen(sometimes swiping across top sensor too), wonder if the sensor is a passive light sensor or active (rf/infrared emission)
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
There are allot of other cases you can use but not waterproof. That really sucks good thing for this thread I was going to buy a lifeproof case. Using a otterbox defender right now. Thanks for the post guys saved me some grief.
still under warranty?
daniel3016 said:
Same issue here same life proof case however it's getting worse as I am a mechanic and this phone goes through greasy hell. The plastic lenses on the lifeproof case are getting scratched and it's getting worse. It is also having a hard time autofocusing through this case. When you pull it out the phone is gorgeous and looks brand new. Good case but it has some downsides. Still better than a broken phone.
Click to expand...
Click to collapse
if still under warranty, see if they will honor it. They did with mine but that was right at the beginning when these problems were linked to the case; mine was in the first 3 months, but the new one worked well for a while, now a little flakey again but not enough to bother me...too bad, a great case otherwise
mikeythedude said:
I am chocking this up to poor software implementation using the ambient sensor. I found similar issues that the OP was describing, and in my testing, was able to verify something is wonky with how the phone "thinks" it is being looked at or not.
Simply put, if you cover the ambient sensor and the camera (on my device) with your finger, while the phone is asleep/screen off, no matter how many times you press the power button on the back/fingerprint scan, the screen will fail to come up. The moment I introduce some light into the room (open up the sensor), I am able to get response back on the phone.
Ran into this issue last night and for the life of me couldn't figure it out until daylight hit . Also, my case might be obstructing the sensor (lifeproof fre), but I also noticed the issue with no case on.
Logically, I imagine LG was trying to limit power consumption with accidental presses, etc. If the phone knows it is in a dark place, it won't respond (because it thinks it is in a pocket or a bag of some sort). My rebuttle for this is how do they anticipate planning for night-time use of the phone, or are we limited to a daywalker only device?
I am heading down to an AT&T store and seeing if I can replicate this on demo units as well. In which case, we know the issue is inherent in the device (and hopefully addressed in a software update). If I am not able to replicate this at the store, then I bet OP and I got bad units.
Thanks for looking. If anyone has any feedback, or can repro or not repro this issue, please chime back .
Click to expand...
Click to collapse
It's not a bug and not poor implementation. Its not light for "dark rooms" lol.. As far as I know it's the proximity sensor. When it is blocked it means the phone is in a pocket or bag and should not register taps. It really makes sense. If you dont xover the sensor and double tap doesn't work ..well.. Well, eother you have defective device or sensor , or the sensor is blocked (maybe bad screen protector?). This didnt happen with my G5 even once. It works 100% (assuming I tapped the same place)
Are the problems as described in this thread still manifesting on current firmware?
Making this thread so that something pops up in google for other people searching for help with these issues.
Was unable to get auto brightness to work on my Galaxy S8 - it stayed dim outdoors and was impossible to see. The light sensor was working perfectly (showed change using the Sensor Box app), it just had no effect on the screen brightness.
In the course of things (including having my local Samsung repair centre replace the phone) I eventually worked out that it was my phone case. Specifically, the MAGNETS in it.
I can't post links yet, but the eBay item id of the case I bought is 162444029744 so you can see the sort of case I'm talking about.
When held up against the magnets, auto brightness doesn't work. As soon as you move the magnets away, the brightness instantly jumps to the right level. If I held the back of the phone up to the side of the case WITHOUT the magnets, auto brightness would work correctly.
The magnets in the case ALSO stop the proximity sensor from turning the screen off when held up to your face during calls. Just checked it then - put my hand in front of the sensor with no case, screen goes off. Put the phone against a magnet, screen stays on.
Same problem
I noticed the same with mine. I received a follow-up call from Samsung after having my phone for about 1 week. I informed them of the screen auto-brightness function not working. They told me it's normal. I had to convince them and their technician it's not.
I then backed up my phone and was about to take it in, in 2 hours time, until I saw your post. And yup, I have the magnetic case too. Same problem.
Didn't have that issue with my S6 though. Same magnetic case.
Thanks for the post.
S8 phone case magnet fix - Auto-brightness [SOLVED]
This has been bugging me for weeks ever since I got my case from Wish. Restart the phone and it all works for a moment, then the sensors fail again. Thanks to this post I took my case off and all is good.
I found my particular case has 6 small magnets in the back cover to hold it in my wallet. I removed the lower right magnet (as you look at the back) and both my phone and case are now working properly.
Hope this helps
Same issue, although mine comes from a magnetic car mount (diy).
I was just thinking of getting a magnetic wireless-charging car mount (with the metal ring that goes into the phone case)...
Apart from the auto-brightness issue, did you notice anything else behaving quirky? Was the phone getting hot, or the screen misbehaving, etc... Also, where were the mount's magnets in relation to the phone; I suppose vertically centered?
I'd call Samsung and ask, they should know best, but since it's not the engineers on the phone, but just tech support people, they'll probably just repeat the "only buy our stuff" nonsense instead of giving any useful reply