Related
My heartbeat sensor will turn on whenever it's covered. Almost like a proximity sensor in a reversed fashion.
In the one call I've placed since the update I've also noticed the front proximity sensor having a major delay in turning the screen off after putting the phone to my face to talk.
Anyone having these issues? Any fixes?
I've used S health to measure my heart rate in an attempt to correct the issue like one guy mentioned but I think he spoke to soon as it is not a fix.
Sad to say, it was merely a temporary fix, I did speak too soon. I have since tried disabling S Health altogether and that still didn't fix it. Today, I'm going to attempt flashing all the way back to original firmware via odin and then taking the OTA's back to lollipop to see if anything changes.
phobia09 said:
Sad to say, it was merely a temporary fix, I did speak too soon. I have since tried disabling S Health altogether and that still didn't fix it. Today, I'm going to attempt flashing all the way back to original firmware via odin and then taking the OTA's back to lollipop to see if anything changes.
Click to expand...
Click to collapse
I did a factory reset, and have yet to launch S Health again since. So far, the sensor has not lit up again. I'm afraid to start S Health though. I will just use Runstastic for now
I don't have this issue. Before I updated to lollipop I did do a factory reset.
Sent from my SAMSUNG-SM-N910A using xda premium
To report back: I backed up, flashed back to 4.4.4 via Odin, took OTA to 5.0.1, factory reset, then restored data and signed into all my accounts again. It seems the solution lies in waiting for AT&T to clean up their mess. The problem has come back for me.
Sent from my SAMSUNG-SM-N910A using Tapatalk
phobia09 said:
To report back...The problem has come back for me.
Click to expand...
Click to collapse
Thanks for tanking one for the team!
At least we have gained the knowledge that going through a full wipe won't help :good:
i noticed this today when i was wearing gym shorts. restarted the phone and it disappeared, for now.
i use the sensor a couple times a day out of curiosity.
please report back if you find a fix
update: after reboot it went away, then i noticed as soon as i plugged it in to charge, it came back. i used s-health to check heart rate, then it went away again. unplugging/replugging into charger did not make it come back.
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
hamza786 said:
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
Click to expand...
Click to collapse
Uninstalled Google fit about 2 hours ago and have yet to see the issue return, thank you very much. I have yet to reinstall, though.
So are u guys with the sensor issue. Was Google fit installed with lollipop update?
Sent from my SAMSUNG-SM-N910A using xda premium
hamza786 said:
I was having the same problem and did a search online that I found fixes the issue. Just uninstall Google fit. If you need it, just re-install and the issue is resolved.
Click to expand...
Click to collapse
phobia09 said:
Uninstalled Google fit about 2 hours ago and have yet to see the issue return, thank you very much. I have yet to reinstall, though.
Click to expand...
Click to collapse
Uninstalled Fit, opened S Health, checked pulse, then had hr light stay on lol
But I like the idea of removing the app that causes it, I just think it's S Health, I tried disabling S Health and so far so good (but I'm pretty skeptical)
Good evening, just lately I have encountered a bug when trying to install APK's. When I go to install via Package Installer it will open up the screen and when I go to press next it doesn't do anything, I have tried rotating the screen and pressing Next and it just doesn't work whatsoever...
I powered off my device and powered back on and this seemed like it fixed the problem.
Is/has anyone else encountered this? I've also noticed ometimes when typing on the keyboard the sound goes tinny for 5 seconds or so and go back to normal, it's been like this since unboxing too.
I haven't had this issue exactly, but when I install a new app and it asks for permission to access my location/storage/etc.. I can't press Allow.. I can press Deny though no problem at all. Right now I'm manually going into apps/permissions and granting all my apps whatever I think it needs.. Just a pain to do it that way though!
I had this issue the other night. It seems an invisible overlay gets stuck sometimes. Not sure what app or why, but clearing all the recent apps fixed it for me. Try that if it happens again instead of waiting for the phone to restart.
Sent from my G3223
Also had this problem two days ago and restarting seemed to fix it. I was disabling some of the stock apps at the time so I wondered if that had something to do with it but I don't know, don't think I re-enabled any of the apps or anything before or after the reboot and so far it's been working since.
mikeandjaimie said:
I haven't had this issue exactly, but when I install a new app and it asks for permission to access my location/storage/etc.. I can't press Allow.. I can press Deny though no problem at all. Right now I'm manually going into apps/permissions and granting all my apps whatever I think it needs.. Just a pain to do it that way though!
Click to expand...
Click to collapse
Thanks for your feedback and I have also had that problem too. Of course yes we can go into app settings and enable and like you stated it's a pain haha. I know this isn't the place to point these problems out and get them fixed but it's nice to know I'm not the only one ??
redincali said:
I had this issue the other night. It seems an invisible overlay gets stuck sometimes. Not sure what app or why, but clearing all the recent apps fixed it for me. Try that if it happens again instead of waiting for the phone to restart.
Click to expand...
Click to collapse
Yes dude, that's correct and thanks for that valuable information I do clean my cache regularly and can't say I've come across the problem for a while, so thanks again.
exonym said:
Also had this problem two days ago and restarting seemed to fix it. I was disabling some of the stock apps at the time so I wondered if that had something to do with it but I don't know, don't think I re-enabled any of the apps or anything before or after the reboot and so far it's been working since.
Click to expand...
Click to collapse
I'd like to mention I have disabled and uninstalled quite a lot too, but I can't say if this adds to the problem. It'd just be really nice to hopefully get the new build of software that was recently announced on Xperia Blog but I can't say if this will fix the problems etc. I don't know? ??
Sent from my Sony Xperia XA1 Ultra using XDA Labs
LevsOG said:
Good evening, just lately I have encountered a bug when trying to install APK's. When I go to install via Package Installer it will open up the screen and when I go to press next it doesn't do anything, I have tried rotating the screen and pressing Next and it just doesn't work whatsoever...
I powered off my device and powered back on and this seemed like it fixed the problem.
Is/has anyone else encountered this? I've also noticed ometimes when typing on the keyboard the sound goes tinny for 5 seconds or so and go back to normal, it's been like this since unboxing too.
Click to expand...
Click to collapse
I've experienced this issue as well and the culprit seemed to be an overlay permission from another app. As I'm sure everyone knows, this phone's screen is very bright even at it's lowest setting. I like to read at night and the light bothers my wife so I started using an app called Nightowl that further dims the screen. Nightowl produces a overlay that dims the entire screen. If i happen to be running nightowl and try to install the app, I can't tap install. Once I turn off the app I'm able to install like normal. Hope that helps lead you in the right direction as restarting the phone every time a problem presents itself is kind of a bummer.
I'm so fed up with these phones.
Is anyone else still having issues where when you go to make a call the screen goes black and you can't get out of it? No way to get into speakerphone mode, no way to hang up the call, no way to do a thing even after the call is finished.
This is with the June update which supposedly fix this issue.
If anyone has any insight I really appreciate it.
Never had the issue while on Oreo or while now on Android P DP3. Do you have a screen protector on it? Even pressing the power button doesn't wake the screen up while in call?
pilotgav said:
I'm so fed up with these phones.
Is anyone else still having issues where when you go to make a call the screen goes black and you can't get out of it? No way to get into speakerphone mode, no way to hang up the call, no way to do a thing even after the call is finished.
This is with the June update which supposedly fix this issue.
If anyone has any insight I really appreciate it.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
EeZeEpEe said:
Never had the issue while on Oreo or while now on Android P DP3. Do you have a screen protector on it? Even pressing the power button doesn't wake the screen up while in call?
Click to expand...
Click to collapse
No screen protector, and nope. Even power button won't get me back.
Very strange. It's replicable with every phone call? Any 3rd party dialer or display adjustment apps that you may be using that could affect it?
pilotgav said:
No screen protector, and nope. Even power button won't get me back.
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
pilotgav said:
No screen protector, and nope. Even power button won't get me back.
Click to expand...
Click to collapse
I know you probably already did this but make sure your screen is clean around the sensor area, I've had a false reading before when the top of my screen was dirty.
Sent from my Pixel 2 XL using XDA Labs
I had the same issue a few months back. Did the online support and they RMA'd it.
It seems it was TrueCaller causing the issues. Thanks for all the advice guys!
pilotgav said:
I'm so fed up with these phones.
Is anyone else still having issues where when you go to make a call the screen goes black and you can't get out of it? No way to get into speakerphone mode, no way to hang up the call, no way to do a thing even after the call is finished.
This is with the June update which supposedly fix this issue.
If anyone has any insight I really appreciate it.
Click to expand...
Click to collapse
I had the problem with the proximity in dp3 it would not turn off while I was on the phone! After doing a FDR it worked great!
I had a feel you might've been using that or something similar. Glad you got it figured out.
pilotgav said:
It seems it was TrueCaller causing the issues. Thanks for all the advice guys!
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
I have gone the whole day testing this issue.
I hard reset my phone 3 times and tested this.
On every hard reset and fresh start the proximity sensor works perfectly well, as soon as I install true caller, the dead screen issue starts.
But I use truecaller without any problems on my other 3 non pixel phone without any issues. This problem is only with the pixel 2 and pixel 2 XL.
There is no resolution as of now. Does anyone know of anyways to get this resolved ?
hypermaster said:
I have gone the whole day testing this issue.
I hard reset my phone 3 times and tested this.
On every hard reset and fresh start the proximity sensor works perfectly well, as soon as I install true caller, the dead screen issue starts.
But I use truecaller without any problems on my other 3 non pixel phone without any issues. This problem is only with the pixel 2 and pixel 2 XL.
There is no resolution as of now. Does anyone know of anyways to get this resolved ?
Click to expand...
Click to collapse
I stopped using the pro version for issues I can't recall.
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
v12xke said:
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
Click to expand...
Click to collapse
I didn't have the issue on Pie and haven't installed any additional apps. It mainly happens after I haven't used the device for a while. It feels like it won't wake up so I have to hold the power button to force a reboot.
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
Yes.
I was just peaking to a buddy with a 2xl and he is having the same issue since 10.
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
bobbyphoenix said:
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
Click to expand...
Click to collapse
I just had a random reboot while taking my dog for a walk. Was only listening to SiriusXM. Think I'm going back to Pie until Google gets the kinks ironed out on 10.
https://support.google.com/pixelphone/thread/14074635?hl=en
Booted into safe mode last night and had to force a reboot this morning to get the screen to respond. This is definitely an issue with 10 and not an app. I'm going back to Pie since having my phone turn off every night is unacceptable, especially since my phone is my alarm clock.
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
droidstyle said:
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
Click to expand...
Click to collapse
I flashed the A10 Oct factory image and wiped data. Still have the issue. The only thing that fixes it is going back to Pie.
So this happened to me twice now since being on 10. My screen would go black while using the phone, and then the phone would be unresponsive, so I would need to force a reboot, but after the Google splash screen it goes into recovery, and this message shows "Could not load Android OS. You can try again, or factory reset.". I did "Try again" both times, and it booted fine. Really irks me since I can't afford to do a factory reset since I use a lot of apps that have special info in them (Like Google Auth App that has many devices I need, and resetting I would have to redo every device). I hope Google can fix these issues with the next update.
I think my issue is due to the sensor bug that was introduced in 10. I have disabled the sensors on my phone and it hasn't froze since!! Hopefully Google fixes on the Nov update.
I'm having the issue that after my screen turns off, after a certain amount of time, I cannot get it to turn back on. The phone is still on, but is unresponsive to my input. I have to hard reset.
I have tried reflashing, and tried disabling sensors. I did not have an issue with the 10 September updated, but since updating to the November update, I had the issue non-stop all day.
Platform-Tools fully updated, not using gesture navigation, but the 2-button.
@MeetFace, yes! Same here since the November update. Something isn't right.
I'm still dealing with the black screen issue. Nov update didn't fix it.
https://issuetracker.google.com/issues/143288447
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
MeetFace said:
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
Click to expand...
Click to collapse
Can you share the tasker script? I love darkmode, but have never used tasker.
darkstar73 said:
Can you share the tasker script? I love darkmode, but have never used tasker.
Click to expand...
Click to collapse
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
How can you tell this is working? I've got it setup ??
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
Thanks for this! Phone hasn't gotten a frozen black screen since I loaded the script!
after each lock when i turn the screen on with double tap or power button screen is unresponsive for good 3 seconds. This started happening after the latest camera fix update. When if i use aod and use the fingerprint through the aod this doesnt happen. tried reboot and factory reset with fresh install (no backups) tried safe mode. Same thing happens.
S20 plus exynos.
Yup happening to me too (s20+ exynos). For me the time of unresponsiveness is around 1-2 seconds. Happened after the latest update.
Yes, have been facing the same issue since "ATCH" update.
Yeah has been driving me nuts. Same problem.
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Glad to see it's not only my device. Waiting for fix.
I have similar situation
I'ne noticed the same after the last update.
Chris_c81 said:
Yeah has been driving me nuts. Same problem.
Click to expand...
Click to collapse
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
Chris_c81 said:
I'm surprised this isn't gaining more traction? Can't be the only few experiencing this!?
Click to expand...
Click to collapse
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
anfederin said:
I have similar situation
Click to expand...
Click to collapse
Mine is Exynos
sjandroiddeveloper said:
Seriously when it happens(which it does like 90% of the time i wake the screen) i feel like i'm using a cheap 100$ phone and not a 1000$+ flagship.
This. I'm afraid if it goes unnoticed by samsung we may have to face this issue for longer.
BTW any user here with Snapdragon that has this issue. Or is this exynos only ?
Click to expand...
Click to collapse
Is there any channel to communicate this bug to Samsung? Anyone know?
Chris_c81 said:
Is there any channel to communicate this bug to Samsung? Anyone know?
Click to expand...
Click to collapse
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
sjandroiddeveloper said:
There is an app called samsung member where you can send error reports. I have already done it, its currently under review. I suggest everyone affected to do it.
Click to expand...
Click to collapse
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
turn off the battery optimized for apps: com.samsung.android.biometric.
Go to Settings>Apps>Select "Special Access" from three dot menu>Optimise Battery Usage>select All from drop down menu>Search for "com.samsung.android.biometric"> Turn it off and Restart.
Click to expand...
Click to collapse
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Did accordingly as above.
For a moment it felt like the issue is resolved!
But after checking several times I can confirm the issue still exists.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Sent from my SM-G986B using Tapatalk
verynuclear said:
Unlock is now super faster. Issue is completely gone. Thanks [emoji4]
Click to expand...
Click to collapse
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Virgo_Guy said:
While using the sidekey and turning off and on the screen and checking consecutively, the unresponsiveness persists in mine.
Click to expand...
Click to collapse
Have you restarted the phone? It didn't work until I restart mine.
Sent from my SM-G986B using Tapatalk
verynuclear said:
Have you restarted the phone? It didn't work until I restart mine.
Click to expand...
Click to collapse
Ofcourse I did. In fact restarted one more time since it didn't resolve after the first restart, post disabling the optimization.
eaglerazor123 said:
Seems like a pertaining issue for Note 10 Users too. They found a trick and seems it works better now. Can you try this and let me know if it works better?
Report back if it works? I didn't check it yet because, I'm on root and didn't update it yet. (G985F/Exynos)
Original Thread
Credits to @wj_johnson
Click to expand...
Click to collapse
I did this already and while it feels like fingerprint is faster, unfortunately this is a screen issue. You see if the screen is off and i put the finger in the correct spot it always scans my finger without any lag. The issue is occurs when -
a) I have unlocked the phone using above way, then the screen becomes unresponsive right after unlocking.
b) The screen is off and i either press the power button or double tap to wake, then the screen will be unresponsive and its during this time the fingerprint scanner doesn't scan (because the scanner doesn't know it needs to scan since the touch is unresponsive)
so TL;DR its not a FP scanner issue.
I am quiet sure Samsung is already addressing this issue for next update.