Related
Rather odd, never happened to me with any ROM previously.
Devices is a Korean Note 3, rooted, running the latest X-Note. Pin lock is enabled.
Randomly the screen will turn on, and right to the apps, no lock at all.
I disabled xposed, tasker, anything that might be interfering or have special tweaks that could have a bug. I have wakeup detector installed, keeping an eye on screen wake events. There is nothing suggesting what might be causing the screen on, and the strange part of it all bypassing the lock screen altogether.
I usually just read existing topics to find answers, but this one leaves me confused. Is there another logging solution to find out what is activating the screen and bypassing lock?
wayandrs said:
Rather odd, never happened to me with any ROM previously.
Devices is a Korean Note 3, rooted, running the latest X-Note. Pin lock is enabled.
Randomly the screen will turn on, and right to the apps, no lock at all.
I disabled xposed, tasker, anything that might be interfering or have special tweaks that could have a bug. I have wakeup detector installed, keeping an eye on screen wake events. There is nothing suggesting what might be causing the screen on, and the strange part of it all bypassing the lock screen altogether.
I usually just read existing topics to find answers, but this one leaves me confused. Is there another logging solution to find out what is activating the screen and bypassing lock?
Click to expand...
Click to collapse
After days of messing about, found something that appears to stop it. Revoking admin rights from Greenify. Still works otherwise, as it appears.
Also, eight hour standby time, loosing zero % battery. Amazing xnote + some tweaks.
I don't wish to entirely disable the front buttons, I only want them to stop responding when the phone is locked (I want them to function when the phone is unlocked). Don't misunderstand: I am not looking to simply disable the light. I want the buttons to be completely 'dead' when the phone is locked up. It's actually my bf's phone, and the buttons get accidentally pressed a lot when it's in his pocket. The phone will drain 60% in just 5 hours with no screen time, just locked and in his pocket (at work). I'm tweaking the phone to last longer, but I feel that having the buttons able to be pressed even while locked can't be good for the battery. :/ Someone correct me if I'm wrong with that (but even if I am, it's still annoying... what is the purpose of the buttons being 'live' while the screen is off???). The phone is a i9505, rooted on CM12.1 with Xposed, so modules could be suggested if any such fix exists. I have the home button disabled from waking the screen, but there doesn't seem to be an option anywhere about the back and menu buttons. I know the battery on my own phone, a Huawei, is much larger, but I only experience about 6% battery loss when the screen is off for 7-9 hours, so losing 60% seems excessive to me. I've checked battery stats on the Samsung, nothing seems abnormal. Is it even possible to fix what I'm asking? Thanks to anyone who helps!
zombunny said:
I don't wish to entirely disable the front buttons, I only want them to stop responding when the phone is locked (I want them to function when the phone is unlocked). Don't misunderstand: I am not looking to simply disable the light. I want the buttons to be completely 'dead' when the phone is locked up. It's actually my bf's phone, and the buttons get accidentally pressed a lot when it's in his pocket. The phone will drain 60% in just 5 hours with no screen time, just locked and in his pocket (at work). I'm tweaking the phone to last longer, but I feel that having the buttons able to be pressed even while locked can't be good for the battery. :/ Someone correct me if I'm wrong with that (but even if I am, it's still annoying... what is the purpose of the buttons being 'live' while the screen is off???). The phone is a i9505, rooted on CM12.1 with Xposed, so modules could be suggested if any such fix exists. I have the home button disabled from waking the screen, but there doesn't seem to be an option anywhere about the back and menu buttons. I know the battery on my own phone, a Huawei, is much larger, but I only experience about 6% battery loss when the screen is off for 7-9 hours, so losing 60% seems excessive to me. I've checked battery stats on the Samsung, nothing seems abnormal. Is it even possible to fix what I'm asking? Thanks to anyone who helps!
Click to expand...
Click to collapse
The keys are never on by default when the screen is off. So you either applied a setting to enable it or you have some mod applied.
Lennyz1988 said:
The keys are never on by default when the screen is off. So you either applied a setting to enable it or you have some mod applied.
Click to expand...
Click to collapse
I wouldn't have enabled a setting for this purposely, as it's quite annoying. I may also be wrong, but if I remember correctly, this was existent even on stock non-rooted. I have CM12.1 on it, Xposed modules are: Always Correct, APM+, BootManager, Secure Settings, Xposed Additions, YouTube AdAway, and YouTube Background Playback.
If there is a setting for this, let's say he or I accidentally enabled it, so would you know any suggestions of how to find such a setting, so it can be switched back? I appreciate you taking the time to answer.
zombunny said:
I wouldn't have enabled a setting for this purposely, as it's quite annoying. I may also be wrong, but if I remember correctly, this was existent even on stock non-rooted. I have CM12.1 on it, Xposed modules are: Always Correct, APM+, BootManager, Secure Settings, Xposed Additions, YouTube AdAway, and YouTube Background Playback.
If there is a setting for this, let's say he or I accidentally enabled it, so would you know any suggestions of how to find such a setting, so it can be switched back? I appreciate you taking the time to answer.
Click to expand...
Click to collapse
When the screen is off then menu and back don't work. Do you have ambient display enabled by any chance? Disable it.
Did you try a different battery? Maybe his battery needs to be replaced.
Lennyz1988 said:
When the screen is off then menu and back don't work. Do you have ambient display enabled by any chance? Disable it.
Did you try a different battery? Maybe his battery needs to be replaced.
Click to expand...
Click to collapse
Oh no, you're right about that. Back and menu doesn't actually do anything when touched while locked, but they do light up and respond in that sense (interestingly, they do also wake the screen while it's locked in TWRP, though perhaps that's irrelevant). Ambient display isn't enabled. We haven't tried a different battery, he just got the phone about a month ago. Then again, I also haven't the health of the battery. Maybe it came with a bad one.
When the screen is off, the back and menu buttons should not work. Not even the lights.
zombunny said:
Oh no, you're right about that. Back and menu doesn't actually do anything when touched while locked, but they do light up and respond in that sense (interestingly, they do also wake the screen while it's locked in TWRP, though perhaps that's irrelevant). Ambient display isn't enabled. We haven't tried a different battery, he just got the phone about a month ago. Then again, I also haven't the health of the battery. Maybe it came with a bad one.
Click to expand...
Click to collapse
I understand you now. Yes when they the phone is locked and the screen is on, they will light up. That's normal and does not give any battery drain. Post some battery screenshots and post screens of the app betterbatterystats.
Lennyz1988 said:
I understand you now. Yes when they the phone is locked and the screen is on, they will light up. That's normal and does not give any battery drain. Post some battery screenshots and post screens of the app betterbatterystats.
Click to expand...
Click to collapse
Ah got it. Good to know it's not impacting his battery, but that also leaves it open as to what IS (though, the buttons lighting up while it's locked still makes me scratch my head at what Samsung was thinking). Currently going to sleep at the moment, so I'll have to take a look at it tomorrow. I know Opera Max, a VPN data compression app, was chewing up battery (did this on my phone too, but eventually it settled down with the ROM), but I froze it for the moment so it won't run until I figure out what else is causing the problem. Battery life was poor even before the installation.
Other than that, battery stats have been normal, with the display taking the majority followed by Opera browser and the Android system, with some others. Nothing outrageous.
But since you mentioned about the battery, I did start noticing more things about the phone today. Perhaps it runs so hot because of it, and I also saw that when he unplugs it from the wall charger, it will immediately drop from 100% to 90-some% (varies). Might be the calibration, but with everything else, I ended up ordering an Anker replacement from Amazon to test.
The S4 heating is normal.
Also, it's not healthy for the battery to spend extended periods of time at 100%. That is why it drops faster from 100%.
From the box, the always on display (AOD) shifted around every minute or so to prevent burn in.
Two days ago I installed the T-Mobile update for my s7 edge. Last night, I was trying out my new wireless charger when I noticed the AOD no longer moves around. I tried charging directly, rebooting, powering off, changing themes/styles to see if it would start shifting around.
Did the update cause this change? Is anybody experiencing the same thing? Is this a bug or intentional (didn't see anything in patch notes). Thank for any input.
I love the AOD but now super paranoid about burn in.
Have you tried turning AOD off, waiting a bit, and turning it back on? Maybe reboot while it's off, then turn it back on.
Yeah, reports circulating that the T-Mobile update is causing the AOD to remain stationary. If you're on T-Mobile, definitely turn off AOD until they release a fix.
Yea I've tried disabling AOD and rebooting but it's still stationary. I went ahead and disabled it entirely and hoping a fix will be released soon. Thanks all.
Damn, disabled mine until it's fixed. Didn't even notice, thanks.
Sent Via My Samsung S7 Edge
Is it dimmed more like the night clock mode? I was thinking maybe they did that and figured it's not a problem any more, but just guessing. I have Verizon version and I jist use the night clock mode all time as the regular clock seems too bright.
hp79 said:
Is it dimmed more like the night clock mode? I was thinking maybe they did that and figured it's not a problem any more, but just guessing. I have Verizon version and I jist use the night clock mode all time as the regular clock seems too bright.
Click to expand...
Click to collapse
The brightness of the AOD is still determined by ambient lighting. The only time the AOD moves to a different position now is when I power up the screen then lock it. If I don't power up the screen, it will stay in that same position with auto brightness in effect.
DNx714 said:
The brightness of the AOD is still determined by ambient lighting. The only time the AOD moves to a different position now is when I power up the screen then lock it. If I don't power up the screen, it will stay in that same position with auto brightness in effect.
Click to expand...
Click to collapse
Yeah, definitely must be a bug then.
I'm annoyed of the Night Clock where it shows the time of an alarm that's set out few days out. I now disabled all alarms so I don't see that. lol.
Also, the stupid + sign on the icon groups in TouchWiz is really awkward and wastes so much space. They didn't have this in Galaxy S6.
Had this issue on a Fresh install (Not present on the Same Version previously (I rolled back after a upgrade)
My default was stuck in the middle and did not move, I went in and change the clock style to the round clock and hands, and mine is moving around the screen as normal
I have the Galaxy S8+ on Sprint as well as my gf. We are on the latest update on Sprint and the auto brightness on both phones doesn't work anymore. Does anyone else have this issue?
yes its a bug...last update not fix it completely
Always found that auto brightness was a battery suck. I've never had problems with setting it to 50% and being able to see it while indoors or out. Checking your phone at 3am with 50%, however, might blind you though.
I was having trouble since the update a couple of days ago. I just found a link that walked me through calibrating the sensors again, which seems to have done the trick. I'll keep an eye on it and update if there are any changes, but hopefully that takes care of it for you too! PM me if you'd like the link, as I am unable to post it because I have not been active enough on XDA.
This could help
https://recomhub.com/blog/galaxy-s8-and-galaxy-s8-plus-how-to-calibrate-auto-brightness/
Sorta.... Not really.... No
This partially..... No, with this, it's all or nothing. I've tried this in a pitch black room to set the low light. When I flip the might on, set it to maximum and switch auto brightness on, everything appears fine. When I flip the might off again thing into complete darkness, the auto brightness does not return to the lowest setting. It stops at approximately 15-20%.
Thanks for the resource, but a different calibration method must be used to restore true accuracy. There was absolutely nothing wrong with it before, but leave it to Samsung to mess with something in good working order and which no one asked to be "fixed."
I've started having this happen after locking my phone. The AOD appears for a few seconds and then this. Started happening a couple of days ago.
paulrgod said:
I've started having this happen after locking my phone. The AOD appears for a few seconds and then this. Started happening a couple of days ago.
Click to expand...
Click to collapse
Samsung support suggested a soft reset and also to clear cache. This seems to have solved it for now. Will keep an eye on it.
For anyone interested, this did reoccur though I've figured out the cause.
I've set up Bixby routines to change certain apps to QHD 60hz, this is caused if I lock the screen while leaving one of these apps open. It seems to be the transition back to HD 120hz for the lock screen / AOD.
Disabling Bixby Routines this no longer occurs.
paulrgod said:
For anyone interested, this did reoccur though I've figured out the cause.
I've set up Bixby routines to change certain apps to QHD 60hz, this is caused if I lock the screen while leaving one of these apps open. It seems to be the transition back to HD 120hz for the lock screen / AOD.
Disabling Bixby Routines this no longer occurs.
Click to expand...
Click to collapse
It may be trying to force the screen to QHD 120Hz which it cannot support, likely why Samsung never gave us that option