I have been having a problem lately, I feel like it was started after the last OTA (Verizon). After a while, some of my sensors stop producing data. Most notably the compass, magnetic, and gyro. I use the magnetic sensor in a tasker task to launch car mode when I stick my phone to the car dock (it is a Spindo magnetic dock). I was having troubles with the task executing and exiting car mode when I removed my phone and noticed that the magnetic sensor wasn't producing data anymore. I looked closer using an app and noticed that a lot of my sensors stop working at this time. I am not sure if it only happens now when I use the dock, or if it just happens after a period of time. But rebooting it will bring the sensors back to life.
Anyone see this before? Any ideas on causes/fixes?
Just an update, it does not seem to be tied to using the magnetic dock. I rebooted my phone before lunch and I used the dock twice after and it was still working. On my way back from lunch I noticed the sensors had stopped working at some point after that.
Anyone have ideas on this?
Sent from my SM-G935V using Tapatalk
Any solution?
Have you found any solution? My at&t s7 started having this same problem. All the sensors just stop working and I have to reboot my phone for a temp fix. I have also noticed it gets hot around the same time it happens. Does your phone become noticeably hot?
Nope. Haven't found a solution. I haven't noticed my phone getting hot either though.
Related
Hey guys! First time poster here! So please excuse me if i make some silly statements.
I got my Nexus 4 back in the beginning of December, but has started using it until very recently (a few days ago). Everything worked fine, until a few days ago when I realized that when I rotate my phone, the screen will no longer rotate. I went into settings and made sure that auto-rotate is still on. But still, nothing happens when I rotate my phone. I have not tampered with the device in any way, and haven't dropped it or anything (in fact, because I don't have a case for it yet, I don't even carry it with me)
I then downloaded sensor box from the app store, and I realized that not only is the accelerometer not working, but neither is anything other sensor (light, orientation, proximity, gyro, magnetic, pressure), the only sensor that seemed to be working is sound, and for everything else it just says "no change detected." I rebooted the device, even reset it to factory settings, but still, nothing seemed to work.
Yesterday when I tried to turn on the phone again, I realized that the battery has died. So I recharged it and stuff. And after recharging, the sensors started to work again! all of them! So I was really happy, until a few minutes ago, when they stopped working again.
Something I noticed is that the sensors stopped working after I play games on my phone. The first time it was NFS, and the second time it was fruit ninja. The phone got quite hot when I played games, and in the case of NFS, as I was playing I realized that the accelerometer has stopped working.
Any suggestions???? Thanks in advance guys!
Ive had my vs980 for about a month now, and a problem that pops up from time to time is my phone will almost immediately turn itself off a second or two after i turn it on. It tends to happen more often after I've not used it for awhile, say turning it on first thing in the morning after it's been sitting overnight. Tap on will not respond, that's my first clue, and when i use the rear power button, it will turn on very briefly then turn off. If i reboot it, it will usually start working again, and tap on will work, etc. It did this a few days into owning it, then worked fine for awhile, but just creeps in randomly. Anyone else had theirs do this?
Banquo22 said:
Ive had my vs980 for about a month now, and a problem that pops up from time to time is my phone will almost immediately turn itself off a second or two after i turn it on. It tends to happen more often after I've not used it for awhile, say turning it on first thing in the morning after it's been sitting overnight. Tap on will not respond, that's my first clue, and when i use the rear power button, it will turn on very briefly then turn off. If i reboot it, it will usually start working again, and tap on will work, etc. It did this a few days into owning it, then worked fine for awhile, but just creeps in randomly. Anyone else had theirs do this?
Click to expand...
Click to collapse
don't cover the proximity sensor on the upper left hand side
Banquo22 said:
Ive had my vs980 for about a month now, and a problem that pops up from time to time is my phone will almost immediately turn itself off a second or two after i turn it on. It tends to happen more often after I've not used it for awhile, say turning it on first thing in the morning after it's been sitting overnight. Tap on will not respond, that's my first clue, and when i use the rear power button, it will turn on very briefly then turn off. If i reboot it, it will usually start working again, and tap on will work, etc. It did this a few days into owning it, then worked fine for awhile, but just creeps in randomly. Anyone else had theirs do this?
Click to expand...
Click to collapse
Assuming the sensor is not blocked, you might have a bad one. I had this same issue on my phone and it got worse and worse. Eventually I returned it for another and now all is well. Your problem is definitely the proximity sensor. It's either blocked or bad.
Try swiping your finger over the sensor 3 or 4 times and then a knock on or hit the power button. That was my work around until I swapped phones.
Maybe it doesn't like you.
Thanks for your helpful response. I will try your swipe idea the next time and see what happens. It's so hit and miss when it will occur, I am thinking it is probably bad. It gets better, then bad for a stretch, then ok again. Probably will need to visit with VZ for replacement. I had heard this happening to some samsung users and it usually came down to a bad battery in their case. I've been getting battery messages, either can't charge with a certain charger or getting the slow charge message even when using its stock charger. I dunno. Like new cars with all the latest features, more things can go wrong w these fab new devices.
Sent from my VS980 4G using xda app-developers app
I am not sure what is going on, but my screen rotation just dies randomly throughout the day, sometimes multiple times per day. When it happens my proxmity sensor also stops working. A reboot fixes both issues then they will naturally happen again. When they both stop working, apps that try to use the gyro wont work they come up with a error that says it cannot be accessed. Im wondering if its a hardware issue, but its hard to believe since it works upon reboot? Ive tried pulling the battery for 30 seconds and other tricks, also dropping the phone with a case on (maybe the weight is stuck) Not sure what else to try, but next step is to swap it out i guess
Hi everyone, i'd like to post my experience with Android Lollipop on my GS5 which is awesome except that since the first day i have the last Lollipop update ( ....L9) my heart rate sensor is always ON . Yep, if the screen is on, even in the lock screen mode, the HR sensor is always ON and if i touch with my finger the sensor, the red light turns on. The big problem is if i place my phone on the table, the red light will be always on. I've noticed that the red light remains turned on the time S Health takes to measure the heartbeat and then it turns off for like 2 mins then turn back on and the problem starts again. I've tried to kill S Health process and Health Service process, but nothing.
It really makes me annoyed.
Thanks everyone.
Tried a factory reset after updating to Lollipop?, heard a few people suggest that it fixes issues with left over trash files from KK
After 2 days trying to figure out and making a lot of factory reset, i found a partial solution ( because i like the app ). The problem is Google Fit. When it is installed on the phone, i don't know why it keeps the proximity sensor of the Heart Rate always on, when the screen is turned on. Disinstalling Google Fit and wiping the cache app, as i said, i solved the problem.
Sballa said:
After 2 days trying to figure out and making a lot of factory reset, i found a partial solution ( because i like the app ). The problem is Google Fit. When it is installed on the phone, i don't know why it keeps the proximity sensor of the Heart Rate always on, when the screen is turned on. Disinstalling Google Fit and wiping the cache app, as i said, i solved the problem.
Click to expand...
Click to collapse
I have the same problem, but i solved it with a disable of activity detection in google fit and a reboot.
It sucks since i have a smartwatch, but i don't want to burn out the heartrate monitor.
Strange Ive heard a few people saying the HR sensor is stuck permanently on, not had that problem this end
Just noticed the same issue with the red light from the heart rate sensor. It was lit when I put down my S5 when the screen was on, will go out as soon as the screen goes black. I do have Google Fit installed, going to disable that next.
Had the same issue with the heartbeat sensor turning on. Turned off Motion Detection in Google Fit and rebooted - issue resolved. Thanks for the tip
Happened twice since picking up my phone Saturday. The fingerprint sensor just stops working altogether. The phone makes no acknowledgment of tapping the sensor when on AOD or lock screen, and swiping the sensor to pull down the notifications does nothing. Reboot the phone and all is well again, so it doesn't seem to be a hardware issue.
Anyone else have this problem, any idea how to fix?
Phone is S8 on Verizon.
I think samsung just want to release update there are soo many bugs i also getting the same bug with fingerprint and iris scanner
Fingerprint sensor works fine on mine but iris scanner does not, times out during setup, i got it as far as 75% once
New phone, a lot of new software, will take time to iron everything out. On a positive note, I have not found any major issue that would actually bother me and some are my errors, I just don't know yet how to do it right. Sometimes clearing cache fixes problems like this, but since I don't have the issue, can't test it.
I guess I could try clearing cache the next time it happens. Happened twice yesterday about an hour apart.
There's a solution that I haven't tried yet in this thread:
https://forum.xda-developers.com/galaxy-s8/help/fingerprint-scanner-issue-solution-t3602551