Hi everyone, I recently bought a S21 Ultra Exynos version. I previously installed BetterBatteryStats app to monitor for any battery drain.
There's an issue that from what I have searched, a few users are having. When my phone is on standby on a flat surface the battery drain is minimal or roughly 1-2% overnight
However, when my phone is in my pocket and when I'm walking, something is activating (possilby the proximity sensor?) the wakelock "cameraservice_worker" that causes the phone to drain battery even without touching it. I also did some testing and this process also runs in the background whenever I'm shaking my phone around instead of letting it lie still on a table top.
I have tried factory resetting and disabling multiple settings, but none seem to be able to work.
Below is a screenshot of BBS to show what I mean under partial wakelocks
This is causing my phone's battery to drain much faster than normal when in my pocket compared to when lying still on a table. Anyone here has similar issues?
These links also show a similar problem, but no one seems to be able to find a solution.
Standby battery drain when active
I've noticed since owning my phone that when I'm walking around in the day, my phone dies quicker than when I have a day where I'm more static. I've tried deleting apps and did a full reset but the problem still existed. I did some research and tried turning off loads of different settings and...
eu.community.samsung.com
Are Exynos Users Getting Bad Standby Drain?
Hi All, Is anyone getting really bad standby drain on the Exynos version? Soon as I take the phone off 100% charge within minutes of checking it again it falls down to 98% with nothing running or in the background. Last night while I slept for 8...
forum.xda-developers.com
So I have seen this as well, I think it's driven by how doze works - basically there is light and deep doze, and apps will be restricted from accessing data etc. until scheduled maintenance windows.
If you are moving, then the phone will only ever be in light doze (less restrictions, more maintenance windows, more drain). Without knowing what it does, I would hazard a guess that it's something that is blocked in 'deep doze.'
Worth giving Naptime a shot - it forces your phone to doze almost immediately, and you can turn off motion detection to stop your phone waking up.
That said I haven't tested it whilst out and about (turning off motion detection basically does light doze with all the rules of deep doze), so not sure if it will help with that particular wakelock.
Okay I'll try naptime out. Thanks!
Does your phone also have the same problem?
Yea same 'problem' - as in I think it's by design, your phone assumes it's in use so pings for more location updates etc. when moving, and I have cameraservice_worker as my biggest wakelock (haven't checked it overnight when phone is stationary, so will give that a go). I lose about 0.5% an hour without AOD overnight.
What I j haven't really looked at is 4g moving around drain vs WiFi moving around. Obviously stuck in the house atm battery is great, but phone is stationary a lot more than usual. Likely that moving around and on mobile data will make a big difference.
You'll need ADB to use naptime but it's easy enough to do (assuming you used it for BBS)
Did a quick experiment, looks like naptime doesn't stop the wakelock, even with motion detection turned off. Moving the phone I got the wakelock, leaving it still I didn't. (Turning motion detection off in naptime requires it to stay in light doze, but with the parameters of deep doze).
I'll keep it on just to see if it works but otherwise not to sure what you can do about it.
Still worth having as it's near instant doze as soon as you turn off your screen
Yeah same here.. having naptime with motion detection disabled still triggers the wakelock. It's annoying how my standby can be so great when it's on the table, but the moments it's in my pocket the standby drain is noticeably faster.
Hope it gets fixed in those newer updates
hsienjuen said:
Yeah same here.. having naptime with motion detection disabled still triggers the wakelock. It's annoying how my standby can be so great when it's on the table, but the moments it's in my pocket the standby drain is noticeably faster.
Hope it gets fixed in those newer updates
Click to expand...
Click to collapse
Have you tried turning off tap to wake or anything like that? That's the only other logical thing I can think of?
mtm1401 said:
Have you tried turning off tap to wake or anything like that? That's the only other logical thing I can think of?
Click to expand...
Click to collapse
I haven't tried turning off tap to wake yet.. will try it and see
Other options I have disabled like turning off lift to wake, pocket detection, fingerprint scanner off when display off. But still the wakelock is there
Had a quick flick through reddit, looks like it might be something to do with proximity sensor and how it uses the camera, which I guess makes some sense, although might have expected pocket detection to stop it.
I wonder if it is misbehaving or if it's a 'normal' service.
On a side note, any noticeable battery improvements from having the scanner off when screen is off? don't really use it
I noticed this last week too and have been trying to find more reports about it. It's also happening to the Note 20 Ultra, seems to be related to the variable refresh rate.
FWIW - i disabled sensors (Dev options > dev quick tiles > sensors off) the wakelocks stop. Just hoping someonee can figure out if there's a service we can disable without causing any issues.
mtm1401 said:
Had a quick flick through reddit, looks like it might be something to do with proximity sensor and how it uses the camera, which I guess makes some sense, although might have expected pocket detection to stop it.
I wonder if it is misbehaving or if it's a 'normal' service.
On a side note, any noticeable battery improvements from having the scanner off when screen is off? don't really use it
Click to expand...
Click to collapse
Hmm unfortunately turning off pocket detection also doesn't stop the wakelock from triggering. I've tried just about everything but no success.. hopefully it'll get better in the newer updates. I'm still on January update
Oh I think leaving the fingerprint scanner always on/off doesn't seem to have a noticeable impact
jigna said:
I noticed this last week too and have been trying to find more reports about it. It's also happening to the Note 20 Ultra, seems to be related to the variable refresh rate.
FWIW - i disabled sensors (Dev options > dev quick tiles > sensors off) the wakelocks stop. Just hoping someonee can figure out if there's a service we can disable without causing any issues.
Click to expand...
Click to collapse
Yeah I came across some of the note 20 ultra threads... no one can seem to find a solution there either.
Haha I tried the disabling sensors workaround.. I'll report back and see if that helps. But at the moment feels weird not having the camera work without having to re-enable sensors first
hsienjuen said:
But at the moment feels weird not having the camera work without having to re-enable sensors first
Click to expand...
Click to collapse
haha I'd be curious how you go with all the other stuff like proximity, ambient light sensors etc are off. Camera was my only test with it, it failed, so turned sensors straight back on.
So I was having a think, if it is a bug rather than normal operation, wondered if it could be the OIS moving around and triggering something when the device is moving? Will do adb permissions for GSAM on my S10 and see if the same thing happens
I installed GSAM on my partner's S20+ and no sign of this wakelock anywhere. Definitely seems limited to the later models Note20 ultra and S21 ultra. Not even sure if the S21 or S21+ are experiencing it.
hsienjuen said:
Hmm unfortunately turning off pocket detection also doesn't stop the wakelock from triggering. I've tried just about everything but no success.. hopefully it'll get better in the newer updates. I'm still on January update
Oh I think leaving the fingerprint scanner always on/off doesn't seem to have a noticeable impact
Yeah I came across some of the note 20 ultra threads... no one can seem to find a solution there either.
Haha I tried the disabling sensors workaround.. I'll report back and see if that helps. But at the moment feels weird not having the camera work without having to re-enable sensors first
Click to expand...
Click to collapse
Have you raised it with the support team on samsung members? going to submit a bug report tonight after using the phone all day so they can see some usage.
It's the sort of thing that average users wouldn't be able to report because they just wouldn't be aware
Just when I was thinking I'm one of the lucky ones, I see this wakelock under BBS...oh rats! I don't think samsung members would be of much help and if I do post BBS screenshots there, I'm sure there will be a load of crackpots saying that this app could be causing this issue yadi yadi yaa...
mtm1401 said:
Have you raised it with the support team on samsung members? going to submit a bug report tonight after using the phone all day so they can see some usage.
It's the sort of thing that average users wouldn't be able to report because they just wouldn't be aware
Click to expand...
Click to collapse
No I haven't.. I'm wasn't really sure where to report this because it doesn't seem like a widespread issue.
But hmm you're right maybe it's because the average user isn't even aware that their phones are draining battery more in their pockets, and probably even less aware that this wakelock even exists
hsienjuen said:
No I haven't.. I'm wasn't really sure where to report this because it doesn't seem like a widespread issue.
But hmm you're right maybe it's because the average user isn't even aware that their phones are draining battery more in their pockets, and probably even less aware that this wakelock even exists
Click to expand...
Click to collapse
Yea exactly, I think you'd need to be using ADB commands (BBS, GSAM etc.) to even see that level of detail, and I reckon 95% of users don't know what they are
FYI - no such wakelock on my S10 running OneUI 3.1
Comrades, this issue a grave issue and will surely wreak havoc on the battery...This issue has to go global. It wasn't present on AUB6 and I have every mind to downgrade to AUB6 until this issue is fixed in the next update
amirage said:
Comrades, this issue a grave issue and will surely wreak havoc on the battery...This issue has to go global. It wasn't present on AUB6 and I have every mind to downgrade to AUB6 until this issue is fixed in the next update
Click to expand...
Click to collapse
Pretty sure I had it in aub6 tbh
Related
What is everyone experiencing? I have a T-Mobile Nexus 6. I am running stock and not rooted. Apologies if this has already been covered, but I searched a couple of different ways and did not see anything.
Not sure what others are experiencing, but my Nexus 6 display will randomly wake into ambient mode even when I just have it sitting still on my desk or couch. There are no alerts that are driving it, so I am just wondering if others are seeing the same thing or if they have done anything with the settings to clear this issue.
I can't imagine that ambient display is a huge drain on the battery or anything, but it's not nothing. Plus it's distracting when it happens.
I've noticed mine coming on due to vibrations. I had it sitting on a minifridge next to my desk. I thought it was random too, but it turns out I was either knocking the side of my desk with my knee, or the fridge was kicking on/off.
Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.
I saw a weird error message from LightFlow (which I installed and enabled to see what it would do). I wonder if this or other apps that are running in the background and potentially causing the screen wakes.
I will try uninstalling LighFlow to see if it improves the situation and report back with any news.
I think you might be right. I have the same problem but I didn't notice it when I first got the phone. I have installed lightflow and now that you mention it, this problem started soon after. So I just uninstalled lightflow and it already seems better.
When I installed that double tap to wake app it messed with ambient display and would turn it on, especially when the battery was low. I removed that app.
Since then I have also turned off ambient display because I found it fairly useless and feel it is using battery for very little benefit. If it flashed faster or kept flashing until I checked it I think I'd use it.
I turned it off because I had it sitting on a table with nobody touching the table and it kept coming on. I couldn't get light flow to get the light working unfortunately, hopefully there is a fix coming.
Moostafa29 said:
Mine does it all the time. No movement to the phone or even around the phone. Hands no where near it. Just decides to wake up. I find the whole ambient display to be pretty annoying altogether honestly. Hoping devs can disable it and find a way to use the LED.
Click to expand...
Click to collapse
root phone, install light flow, disable ambient display.
it's already been done.
i use light flow and it works perfectly, sans flashing LED but that seems hardware/kernel blocked.
It seems that LightFlow is what was causing the issue as I haven't noticed the screen waking since uninstalling it yesterday.
Sent from my Nexus 6 using XDA Premium HD app
I'm definitely looking forward to getting the LED indicator working.
Sent from my Nexus 6 using XDA Premium HD app
Off late I'm noticing that whenever I turn on the display, it goes completely bright for maybe 5 seconds before adaptive brightness kicks in. Today I completely reset my phone and reflashed the latest factory image (MRA58R, I was on MRA58N previously). It was fine for a while (for a few hours) and now it has started behaving the same way. It works fine if I turn off adaptive display. This happens 90% of the time.
Has anyone else faced this?
---
I have filed a bug report, please star it.
https://code.google.com/p/android/issues/detail?id=196048
I've got the same issue on 6.0 stock not rooted. I've been fiddling around with lux trying to get it to stop going to max bright in low light settings... And it seems that the light sensor is getting incorrect readings in low light and it takes a few seconds for the sensor to start showing accurate levels for the light conditions. I would love to have adaptive brightness work as it used to - don't know what changed.
Same issue here.
Woah. I'm not alone. So for all you guys, it started just recently?
yeah. I noticed it a little less than a week ago
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
foxnutz said:
yeah. I noticed it a little less than a week ago
Click to expand...
Click to collapse
Hmm. Same here. Started last week. Will have to dig out what the root cause is.
altimax98 said:
Do you use Gravity Box?
Issue came with that mod for me and even after removing it my Adaptive Brightness still doesn't work properly.
Click to expand...
Click to collapse
Nope. I'm running completely stock, no root, even locked bootloader (for device protection feature).
I am running completely stock marshmallow no root, boot loader is locked, no gravity box. Same problem.
Is there any program we can use to monitor the readings at the light sensor is receiving?
I have tried two apps but that doesn't seem to gather data while running in background; only works when the app is opened. Still trying to find one that does background logging.
I have the same issue.
And I thought it was Gravity Box.... now I wonder if it's the November patch? Since there is report from people who never root and using stock?
Ok, so I found an app that can log data while in background. It's called Androsensor. It also has a companion app (Androsensor Keep Awake) which helps to hold a wakelock to gather more data. I tried it and I feel it's definitely not the sensor or it's driver/binary malfunctioning, it seems to be reporting proper values. Maybe more people can try it and report back.
i just bought my phone (brand new) update it right away to 6.0 and used it and having thesame issue!
that means this is google firmware problem!
The reason I believed it to be the sensor was because I used lux to try and fix this and noticed when the bug was occurring, as the screen just turned on and went to max brightness, lux showed the values from the sensor above 20000. Oddly enough if I had lux update every 3 sec it would sometimes capture the actual light levels on the second update and adjust accordingly. I'll check out the app you mentioned and see what shakes out.
I'm having it too, also completely stock and unrooted, first noticed it a few days ago. A friend of mine also has it. He is also stock, I'm not sure about his root status though.
Ok got some interesting results this morning using androsensor. First of all I was unable to recreate the bug while using the keep awake helper app... Which leads me to believe that there may be some issue with the sensor values being calculated/averaged by the autobrightness code/program as the device wakes up from sleep. perhaps android is shutting off the light sensor when the device goes to sleep and this causes a reset? So it appears that it's not getting wrong values rather, that the data being drawn from the sensor is reset or perhaps recalculated as the device wakes back up. Almost as if it can't remember the last light level that was observed. I uninstalled the wake lock helper and was able to recreate the bug by letting the device "sleep" (leaving the screen off for maybe 5 seconds). So while the sensor showed readings of 2 lux the screen brightness was increased erroneously until the auto brightness refreshed and then after a few updates on the sensor the correct brightness was applied to the screen. Curious results. Can anyone else try to recreate the bug using androsensor and the wakelock helper program? I'm hoping I didn't run into some user error there.
I too tried without the wakelock helper and got the same result which made me believe it's not the sensor that's causing it. Will try the same with the helper app and report back.
Just tried Androsensor with the helper and I was unable to reproduce the bug, exactly what foxnutz faced.
Alright so we got some results! Just for the sake of being thorough, can anyone else replicate these results that andr0idfreak and myself saw? It seems holding a wakelock on the sensor stops this bug.
Now where do we go from here? It's been an awfully long time since I've done anything with logcat... But I think that may be our best bet to find out what's really going on here. I'll have to do some homework before proceeding. Will report back.
I think we should file a bug report here.
https://code.google.com/p/android/issues/list
I think a bug report is probably worthwhile. I thought it was some combo of xposed and gravitybox as well but I flashed my stock system back and it's doing the same thing.
When I first customized my OP5 settings under OOS 4.5.0 (before the last two OTAs) there was a "Proximity Wake" toggle under "Settings->Display-Ambient display". The feature allowed you to wave your hand near the OP5 and the display lit up briefly so you could see the lock screen. See "How to Enable Proximity Wake" and the accompanying YouTube demo.
Since the first and second OTA that option has been replaced with an "Lift up display" toggle. I'd much rather the proximity Wake feature or better yet, both.
Does anyone know why that feature was replaced? Did it not work reliably?
It's possible it was using too much battery power.
In an effort to save battery the setting was lost on the wayside...
ultramag69 said:
It's possible it was using too much battery power.
Click to expand...
Click to collapse
+1
ultramag69 said:
It's possible it was using too much battery power.
In an effort to save battery the setting was lost on the wayside...
Click to expand...
Click to collapse
A reasonable assertion but maybe they should've let the functionality be limited to "while on charger" like other battery sucking features. Thanks for your input.
All the Moto phones have this including the the Moto Z play and it has the longest battery life of just about any phone. This a a great feature and one of the reasons I bought a OP5 . Can't believe they just got rid of it.
Maybe if enough people complain it will be put back in by another Ota. One plus do seem to at least listen to the Dev community. ..
3DSammy said:
A reasonable assertion but maybe they should've let the functionality be limited to "while on charger" like other battery sucking features. Thanks for your input.
Click to expand...
Click to collapse
Yeah this was a great feature I had on my Nokia 1020, if it was causing battery drain on the OP5 then put an alert when you toggle it that it will have a direct impact on the battery life. Crisis averted then.
Ambient display in general is sort of weird on this phone. It doesn't exactly do what I thought it would. Maybe the removal of this feature is one of the reasons. But with the notification light so dim (maybe this can be altered with a mod or future ROM, I hope), the live display aspect is sort of needed. Is there a post on the OP forums on this yet? Someone should make one.
This is something I really miss from my old Moto
If you are rooted, there is a workaround to have proximity wake enabled. Instructions are provided in this thread: https://forum.xda-developers.com/oneplus-5/how-to/guide-how-to-enable-ambient-display-t3690488/page4
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since
Tap to wake not working for me
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?
Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.
Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.
czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.
I have same two problem with AOD, touch to wake up and screen off/on when calling.
DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?
There is a funny thing about heating issue. On my exynos 21ultra, I have heating(warm) issues from these apps.
Camera.
A simple word game.
Chrome(which I eventually disabled).
Then I have these apps that doesn't generate as much heat:
Asphalt9
Quora
Ludo
YouTube and other video services.
Samsung didnt get their thermal management right in this release of their software.
Yea thats for sure, I get heat from mt S21+ Exynos when opening apps that you dont expect heat from and viceeversa...
welcome to 2021s #exynosgate
Seems okay after a couple of days. First day had some heating issues when using the camera. Alternative, you can set to 60hz to test it.
trapcoder666 said:
Seems okay after a couple of days. First day had some heating issues when using the camera. Alternative, you can set to 60hz to test it.
Click to expand...
Click to collapse
I am using only 60hz with 1080p. I got 2 updates already. Can say thing improved a bit after the second one.
DaGalaxySheep said:
Yea thats for sure, I get heat from mt S21+ Exynos when opening apps that you dont expect heat from and viceeversa...
Click to expand...
Click to collapse
So Is it a hardware issue like the SOC's or just Samsung getting their optimization levels to just average?
I think its optimisation issues...
bobbysidhartha said:
So Is it a hardware issue like the SOC's or just Samsung getting their optimization levels to just average?
Click to expand...
Click to collapse
DaGalaxySheep said:
I think its optimisation issues...
Click to expand...
Click to collapse
no issues at all for mine
I haven't used the Camera all that much, a photo here and there but Chrome doesn't heat mine up at all
Yes it heats up for nothing
Just having the view finder open on AUA4 was enough to cause my G998B to almost melt. Battery life was rubbish too.
AUAC fixed this for me and substantially improved the battery life.
AUAC here, still problems
Go into settings and type in notifications into the search bar
Go into included apps, turn off everything you don't use
Go into settings and type in deep sleeping apps into the search bar
Click onto deep sleeping apps, and put everything you don't use to sleep.
Clear cache and storage from camera app.
Close all apps from background, and reboot your phone.
dazed1 said:
Go into settings and type in notifications into the search bar
Go into included apps, turn off everything you don't use
Go into settings and type in deep sleeping apps into the search bar
Click onto deep sleeping apps, and put everything you don't use to sleep.
Clear cache and storage from camera app.
Close all apps from background, and reboot your phone.
Click to expand...
Click to collapse
This is the fix for stupid heating?
isko01 said:
This is the fix for stupid heating?
Click to expand...
Click to collapse
No
Try completely disabling all power management.
Clear system cache.
If that doesn't get it, one or more apks is at fault. You'll need to track them down.
All cloud/backup apps and Google system apks are suspect.
Try disabling auto brightness.
Try a network reset.
ARcore was a super power hog on my 10+/Pie variant; I disabled it.
Disable any carrier or Samsung apks you don't use. Disable all carrier, Google and Samsung feedback.
d0ce said:
Just having the view finder open on AUA4 was enough to cause my G998B to almost melt. Battery life was rubbish too.
AUAC fixed this for me and substantially improved the battery life.
Click to expand...
Click to collapse
What is AUA4?
Did your phone still get heating?
How did you fix that?
isko01 said:
This is the fix for stupid heating?
Click to expand...
Click to collapse
Yes, it should be, and also for battery.
AUB3 slightly better
I have been experiencing this, it's heating much when camera is on especially during Zoom meetings or other video conference. I have the latest update as of Feb 1.
I just noticed the heat when I lift my phone while on a zoom meeting.