Hello all,
many of you probably have no idea, that there's a small issue with our phones regarding tmd4906 proximity sensor. But first things first. Since I switched to oreo, I've noticed that something's eating up the battery and its sth related to system process. So I installed gsam battery monitor and started checking the lists. I came across that in android system, there's an entry regarding proximity sensor which is taking battery like crazy. Then, I was searching for the cause of it. And i found that's pretty easy to reproduce for us all. So I ask you to check something:
switch on your mobile data, find a dark place, turn on, i.e Spotify and start listening to music (mobile data has to be in use), turn off the screen, and point any other's phone camera to your phone where proximity sensor is (left to the speaker, up.). You should be able to see that proximity sensor is constantly working when mobile data is in use.
Another question - is there any other way to get rid of this? I have switched off everything which may make use of this sensor - no go. Since I'm unrooted, I cant do nothing about it. It's keeping making wakelocks like crazy and draining a lot of juice. My Samsung A5 2016 uses half less juice when i keep mobile data on.
Yes, I've tried many clean flashes from scratch - nothing. I came across that similar issue was found in s7.
Have you tried disabling "Block accidental touches" in Settings / Display ?
I my S7 Edge i had that too. Made my "Android System" wake like crazy. Only working solution was install different ROM (official)
Related
Hi all,
I've had this issue for about 2 weeks or so. The proximity sensor on my Nexus 5 randomly stays active no matter what app is on or if the screen is locked. So whenever the screen is active and I put my hand/finger near the proximity sensor it will blank the screen. You can see how this would be annoying when you're just checking notifications and the screen blanks out. Any thoughts or suggestions? It definitely seems software related as a reboot solves the issue until it happens again. I've tried to consistently recreate the issue, but I can't tie it to any one app that was/is active, or any combination of events that causes it. After a few hours when I unlock my phone to check a notification I notice it's active because the screen will go dark. Is there a way to see what app(s) could be doing this?
My phone is unlocked and rooted, but stock rom. No screen protector at all. I can't think of any non mainstream apps that I have installed.
Thanks!!
I have this issue exactly. Did you ever find the fix for it?
Are you using any app that uses the proximity sensor to turn on the screen? (e.g. Shake Screen-On). Those apps keep the proximity sensor on (if using near receiver mode).
One way to see if an app is using the proximity sensor is by checking the battery options. One of those apps might be the one draining your battery.
Same here. Reboot makes it work fine for a couple days, then the proximity sensor just stays active til the next reboot. Has done this on CM, PA, and Cataclysm.
This problem shows up periodically when I leave my S7 stationary on a desk or table while in discharge mode. I found an xda thread describing the exact symptoms, but for the S6. My phone is an S7, of course. That S6 thread is here: http://forum.xda-developers.com/galaxy-s6-edge/help/push-notifications-stop-screen-off-t3071248
I have my device set so notifications will appear on the lock screen. And under Settings > Notifications I have about 5 apps set for priority mode. That works consistently to bring notifications from those apps to the top of the notification list. The problem is that occasionally when the screen turns off --not consistently-- all push notifications are suppressed until I turn on the screen again. At this point, all of the suppressed, pending notifications fire off their associated alert sounds and each of their alert banners pop onto the lock screen. I can never know when the notifications are going to be suppressed like this when I toggle off the screen or when it times out on its own.
Am I the only one who experiences this issue on the S7? I had possession of some other S7's some months back and at least two of them demonstrated similar intermittent push notification behavior. However, I had no idea exactly what was happening at the time (i.e, whether it was the individual apps malfunctioning or perhaps a lagging issue with the servers/networks they were using). But from my experience to date, it appears that the absence of notifications on those devices during screen off mode may have been the same issue.
There was a great deal of concern about this within the S6 thread I've cited above. But no definite solutions were given; the general hope was that a future update would correct the problem on the S6 and that the S7 with android 6 marshmallow would hopefully not include the intermittent notification problem. If I've missed an informative thread on this issue relevant to the S7 (or the S7 edge) please direct me accordingly.
Thanks
Used to happen with my S5, afaik it's Marshmallows new low power mode, 'Dose' that causes it as it didn't happen with Lollipop
*Detection* said:
Used to happen with my S5, afaik it's Marshmallows new low power mode, 'Dose' that causes it as it didn't happen with Lollipop
Click to expand...
Click to collapse
In that case, how is the best way to disable this mode? Package Disabler perhaps? And why am I the only one who seems to have posted about this matter as far as the S7? Timely notifications are pretty important... so I would think that if this were a typical power saving side effect on the S7 that many S7 owners would be speaking out about the notification lapses. It's fairly puzzling.
Thanks
Dose being the cause is just my take on it, I couldn't think of anything else it could be with my S5 either, and as I said it never happened with Lollipop, and Dose only arrived with Marshmallow, so I put two and two together
Not sure you can disable Dose, other than have something running in the background causing a wakelock, which would drain your battery
Might be something else causing it, but I couldn't see any other explanation
Something I did notice though was if the phone was on 4G Data instead of WiFi, notifications were instant, but I was only on 4G while I was out, and when the phone is moving, dose doesn't work, it has to be completely stationary
*Detection* said:
Dose being the cause is just my take on it, I couldn't think of anything else it could be with my S5 either, and as I said it never happened with Lollipop, and Dose only arrived with Marshmallow, so I put two and two together
Not sure you can disable Dose, other than have something running in the background causing a wakelock, which would drain your battery
Might be something else causing it, but I couldn't see any other explanation
Something I did notice though was if the phone was on 4G Data instead of WiFi, notifications were instant, but I was only on 4G while I was out, and when the phone is moving, dose doesn't work, it has to be completely stationary
Click to expand...
Click to collapse
Hmm... in my case it is happening exclusively on 4G without wifi running. So maybe it's something else. Most of the time notifications come though immediately. I'd say that during only about 10 or 20% of the phone's stationary time they are repressed until screen on.
Have a solution!
Faced the same issue, you have to exclude the apps you need notification at 2 places in the settings.
For the doze settings, go to settings, battery, battery usage, more ( top right), optimize battery usage , select all apps and select the apps you need to show notifications.
Second place, settings, battery, go down to app power saving, click details, set app you wish notifications to disabled.
Hi guys,
after several days of research on google and in this forum I still couldn't find out what's the issue with my new Galaxy S7 device so I'm posting it here and hope for you to help me out.
I also had the same issue on my Galaxy S6 before but it was way worse because of the smaller battery.
The phone is not even a week old and I have issues with it to go into deep sleep mode since day one. I even installed BBS and Wakelock Detector with granted rights for the battery stats but I wasn't able to find out what causes the problem (it's the exynos model by the way).
The Kernel Wakelock stats in the Wakelock Detector App don't show unusual usage anyway, those who are always on top (also with my Galaxy S6) are the "PowerManagerService.Display", "13960000.decon_f" and "PowerManagerService.WakeLocks" followed by "mmc0_detect" and "bbd_wake_lock" (I will post a photo later, I am currently at work in my break) which hold the phone awake around 20-25% so it isn't always in deep sleep or doze mode.
All the google research said that the decon_f thing is connected to the DOT/SOT which I cannot confirm in my case. I still don't understand what the problem could cause because I didn't even use it for a week. When I set up the phone I did it clean without copying apps or using the backup from my Google account so I don't think that could be a reason for it.
I appreciate your help guys, thanks!
I don't really now much about your problem (sorry for that), but if you're rooted i can really recommend you the app ForceDoze. It activates the Doze Mode right after you turn off your screen and lets you black-/whitelist apps, which are/aren't allowed to make wakelocks. It also gives you the ability to control other doze related settings.
It's not rooted and I don't want to trigger the Knox counter so I think I will stay with the stock configuration. I'm really wondering what could cause it, never had those issues on my Redmi Note 4
During calls the proximity sensor isn't working properly. The display keeps going on and off and many times you end up having accidental touches which can lead to the pulling down of the notification drawer and even cause apps to open randomly.
However, it behaves differently with every single occasion I get to make a call. Sometimes it works better and sometimes it's worse. It also seems to be influenced by the environment I'm in. If for example I'm inside my apartment talking on the phone, when I move from a darker area of the room towards the open window and vice-versa, it seems to be triggering the light sensor which is somehow communicating with the proximity sensor, thus causing the display to go on and off.
Can anyone confirm this issue?
Yes, even I have observed the same, sometimes it works like a charm and sometimes it just keeps toggling very badly.
Same thing happens with my device. It's comman with many Xiaomi devices I purchased in the past. Maybe a software update will fix it.
My Proximity Sensor always turn off screen after click "Call" without near my face. I just got a new redmi note 7 pro replacement because that.
Just updated to the latest MIUI China Stable 10.3.5.0 version and the bug appears to have been solved. I've tested it in different lighting conditions and the screen stays off in each and every scenario. So that's one less bug to deal with.
Apparently this is a fairly common issue with the Samsung Galaxy S10 range and after doing some simple tests I'm hoping my insight can help.
The first test I did was to dial *#77692# to access the proximity sensor test menu. While I was on this menu I covered the sensor with my hand and got a proximity reading of 1.0 everytime the sensor was covered and 0 when it wasn't, which to me suggests that the sensor is working fine.
the second test involved ringing up my voicemail and basically doing the same thing, now here is where it gets interesting; if I cover the sensor for a few seconds and then lift my hand the screen stays turned off. But if I then recover the sensor an inconsistent number of times (sometimes once, sometimes a bunch of times) it'll turn the screen back on.
Additional: I also tested this on Skype and the behaviour was identical.
To me it looks like the issue is purely on a software level rather than a hardware level as this only seems to happen during phone and Voip calls, but not during tests.
Now I'm not a developer so I can't begin to understand how this issue could be fixed, but I'm hoping my little tests can help matters along.
Had the Problem also, fixed it by rebooting into recovery and wipe cache partition.
Same issue here..
I have had S10e, but i sold because of this issue.. now i want to buy it again, but i don't know if exists an S10E series without the proximity sensor issue.. anyone with ans S10E without this bug? (just try to hear a whatsapp audio near the ear)