I use an older Samsung Note 4 with the latest stock OS allowed for it. I have had an issue since day one that I can't seem to find a solution.
I want to be able to disable the screen from turning on, unless I hit one of the physical buttons (typically Home or Right side button). The reason is that notifications and other background processes keep lighting up the screen. Sometimes, the screen will just stay on and not timeout. Also, if the phone is in my pocket, it senses my body and starts interacting as though its my fingers. I am only aware of this once the phone heats up and then all my icons are messed up. The biggest problem is the battery drain from all this. Setting the timeout short does not really help and is kinda annoying itself.
I have not been able to find a setting or app than can suppress this. All of my searches just turn up the opposite solution to keep the screen active constantly.
Is it possible to disable the screen until an actual physical button is pressed? If so, what is the solution? New OS, new phone, app?
Thanks.
Related
I just started having this "bug" yesterday. Basically, what happens (randomly) is that when I press the power button, remove the stylus, or slide the phone open to wake it up I'll be met with a black/blank screen. The backlighting will be on, and the phone is responsive (can receive messages, make calls, sounds/notifications work), but I won't be able to use the screen. If I use the power button to turn the screen back off and wait a few seconds, the screen might start working again. This is completely random and I cannot duplicate it with any guaranteed process, but it seems to be when the phone is waking up from standby. After a soft reset, probably half of the time I'll be met with this same delima, which leads me to believe it's hardware and not completely software.
At the same time the phone is also struggling to re-paint the screen from the change of Landscape-to-Portrait and visa versa. Also opening and closing windows to get back to the today screen also cause a problem. I've disabled TF3D to see if that makes a difference, it doesn't. I have a blank today screen with no plugins to free up the system resources, and am still having this issue.
I'm using JD's Rom (probably around 1.3, it's been running fine with no issues up to this point).
I'm also using S2U2 1.35 (if that makes any difference, haven't had any problems until recently)
The phone has never been dropped, it's in InvisibleShield, and normally sits on my desk charging all day.
This started happening last night for no apparent reason and it's really starting to irratate me.
Any advice is appreciated. Thanks.
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
After more testing..
After some more fiddling around with the phone I'm about 90% certain it's a hardware issue. I noticed that when I slide the keyboard out if the slide portion is past the number line then the screen will stay on, but not update. I don't know how well I can explain it. If I'm typing and hold the screen to keep it from opening all the way then I can see the letters/words appear (in txt msg/email), but if I let the screen goes and it slides all the way open then the screen will stay on and only show what has already happened, any more typed characters will not appear, but if I move the screen back to the number row then the screen will re-draw and update what has happened.
Is this something that Sprint should fix no questions asked?
lulugirl896 said:
Re the black screen:
Sounds like its software related. For example, I sometimes have this if I leave PocketTwit in the foreground and turn off phone. What software did you install yesterday? Also, do you try to press the home key and see if that clears the screen?
Click to expand...
Click to collapse
The last piece of software I installed was Gyrator 2 on Friday-ish. Thinking that it was the problem, I removed it using MemMaid. I'm going to give the phone a flash tonight and see if it is software related (hoping for the easy fix) but as the post above says, I'm almost certain it's a hardware issue. I just wish I knew how it happened. . . So much for that time putting those InvShld on.
Final Update (this can be closed)
I took it into a Sprint store and they replaced the "flip" on the top for free (I have insurance).
Point of the story/thread, this can be closed, it was a hardware issue, and now it's fixed.
Ok so I have a little problem with my HTC Diamond. In options I set to turn-off the backlight after 10s of inactivity which is standard. The problem is that after those 10s I can see that the screen backlight is fading out but it doesn't fade out completly - if you look from an angle it might appear that it's off but if you look at the front of the phone or simply in the dark you can see that the backlight is still on only set to something near 10 or 5%. As you know the battery just sucks in this device and I don't want the backlight to drain it so any ideas or tips on this matter? Of course I can put the phone to sleep mode but I'd just prefer to make the backlight turning off so I can take a look at the screen to for example check the time without having to press any buttons...
Same problem here
After those 10s the screen is not turning off completly, just fading to 5, 10 %. The screen with all the info, the home page let us say, is still visible and drains the battery. I also could just press the power button to turn is completly off, but I would also prefer it to do this manually after ten second.
Did you find a solution to this problem yet?
Help Battery Drain
Same thing here, and my Backlight is stuck to 100% i think,
anyone found a solution to this? any hints?
Guys, i assume youve set the "turn off device if not used for xxx mins" correctly whilst in battery and external power correctly?
If you have, what roms are you using as you give us no information to help any further
Hello,
I had the same problem with ROM 2.03.421.2, date 12/24/08.Back then I had SPB mobile shell installed and a very few applications and I couldn't find the problem. I made a hard reset so now, with nothing installed, the device also enters standby. You should take care because it is possible that the device is not entering standby either and it is making calls. When I had this problem my friends were complaining that I kept calling them and not talking. It is strange as I'm sure I put the device to sleep with the power button. But still, somehow, it was making calls...
Had to use Google Nav to get across town tonight, after sunset. I usually drop the phone in my center console after it locks location and begins giving directions. On my old Moto Droid, I could turn the screen off and just listen to the voice directions.
On the Thunderbolt, it seems to keep the screen on, regardless of what the time out is set for. If I hit the power button, the screen turns off, then powers back on in a second.
This is just a complete waste of battery. If I was sitting the phone in a car dock, it'd be different, but this is a waste. Anyone experiencing this, or know how to get the screen to turn off when Navigation is active?
idk if this works but have you tried hitting the home button to get out of google nav (while it's still running) then hit the power button?
I have experienced the same feature. It doesn't bother me too much though cuz I have my phone plugged in.
I bet the above idea works.
this is not a signature I type it in every time maybe sent from my phone or my computer
Bateluer said:
Had to use Google Nav to get across town tonight, after sunset. I usually drop the phone in my center console after it locks location and begins giving directions. On my old Moto Droid, I could turn the screen off and just listen to the voice directions.
On the Thunderbolt, it seems to keep the screen on, regardless of what the time out is set for. If I hit the power button, the screen turns off, then powers back on in a second.
This is just a complete waste of battery. If I was sitting the phone in a car dock, it'd be different, but this is a waste. Anyone experiencing this, or know how to get the screen to turn off when Navigation is active?
Click to expand...
Click to collapse
It only keeps the screen active if you are in the navigation program. Just back out, or go to any other screen and it will turn the screen off normally. Working as intended.
akanatrix said:
It only keeps the screen active if you are in the navigation program. Just back out, or go to any other screen and it will turn the screen off normally. Working as intended.
Click to expand...
Click to collapse
Have to test this. Thanks.
I have experienced the same issue with the thunderbolt. The screen stays on weather I have the phone plugged in or not.
I see hitting the home button as more of a workaround than a solution here. It's easier for me while driving to turn the display on and off with one physical button.
I'm hoping that cyanogenmod will fix the issue when it's released but I feel like there should still be a way to set the screen to stay off when the power button is pressed in navigation.
I think its a feature, keep screen alive. As mentioned, going to home screen allows you to put it to sleep, but you cannot while navigation is active.
I can see your point though, keep it off, then a quick on shows you where you are without the need to open the app from the tray.
In order to reduce battery drain while navigating and streaming audio, I used to turn the screen off on my Nexus One whenever I had a long uninterrupted stretch ahead with no turns; the audio prompt gave me plenty of time to turn the screen back on before I needed to see the road configuration. That doesn't work on the G2x; the screen only stays off for a second or two before coming back on, like one of those trick birthday candles that keeps relighting itself. I can turn the screen off if I change to another application before hitting the power switch, but that means more fiddling in traffic to get the navigation display back.
Is there a setting I'm overlooking, or is it just a peculiarity of this version that I will have to live with?
This was bothering me also,
With the navigation still running, press the home button to back out to the homescreen and keep the navigation still running in the background. This allows you to turn the screen off
omarsalmin said:
With the navigation still running, press the home button to back out to the homescreen and keep the navigation still running in the background. This allows you to turn the screen off
Click to expand...
Click to collapse
Yeah, that's a variant of the "switch to another application" technique I mentioned. Unfortunately, that still leaves a good deal of fiddling with the phone while driving to get back to the navigation screen.
Thanks for the reply, though; I'm glad to hear I'm not alone in this concern.
Hi all!
I have the fingerprint locked option enabled. I find that sometimes, somehow the phone vibrates when it is in my pocket. When i take the phone out of my pocket, it will say fingerprint lock disabled. It's as though it is detecting the inside of pocket as a print, that's trying to unlock the phone. I also find that the flashlight turns it self on whilst it is in my pocket and also the bluetooth and wifi.
Is anyone having similar issues?
Finding it really annoying.
I've found some of my settings changed before, and I've noticed that the double tap to wake will work through thin material . . . like a jeans pocket.
When you put it in your pocket, turn the screen towards your body and see if that helps. Failing that, try disabling double tap to wake.
I've not had the fingerprint sensor disabled message myself, but the sensor can also trigger through thin material too. It obviously won't read any fingerprint, so if it happens a few times, it just temporarily disables the sensor.
I had to disable the double-tap to wake screen option as it was always triggering in my pocket (screen facing in). I only have screen lock set to swipe though so walking/climbing stairs was waking the screen, pulling down the notification panel and going to town changing settings. I even somehow managed to change the time display setting from 24 hour to 12 hour. I mean, how the hell can that happen in a short few minutes in a pocket?!
Glove mode is/was off if anyone thinks that might be the cause. No screen protector either.
I only have the sensor lock if my finger fails to unlock the phone after a few tries. Every time the fingerprint is not properly read it will vibrate, after about 4 go's, it locks and you need to type in your pin. I'm guessing something is pressing the power button in your pocket and it's trying to scan your finger but failing, so by the time you pull it out, it's locked itself!
I too had to diable double tap to wake because it kept coming on in my pocket. even if it does not get past the fingerpring lock it still wastes some battery.
it would be nice if something could be done in tasker to:
if phone is flat on table(accelerometer)
then enable double tap to wake.
else disable it.
DT2W is wayyy too sensible at the moment. I hope Sony will fix it. A touch or double touch shouldn't be detected through clothes when the screen is off.
That feature was perfectly tweaked on my OnePlus One running CM12.1, and I liked to use it
Yeah I find the screen touch, fingerprint and rotation all way too sensitive. I have already disabled 2 of them, fingerprint is next....
Sent from my E6653
Ditto with the tap to wake frustratingly waking my phone constantly in my pocket. Never had the problem with the Z3. So many issues with this phone that were perfect on the Z3 feel like I've gone backwards.
same issue here, tap to wake activated and called the cops on me LOL...OMG
This is so annoying. My phone always wakes (through dt2w) when in my pocket and does weird stuff: changes settings, calls people, etc...
The one thing I found working for me is keeping the screen facing away from my body while in my pocket. It doesn't wake the phone up then.
I have this problem as well.
Try gravity screen app. It should turn off the screen in 1 second or less should it accidentally turn on while in the pocket.
This has bothered me loads so i've disabled the feature. You'd think they would make use of the light sensor to detect if the phone is in the pocket and then not unlock the phone on double-tab. There's the standard Google 'on-body' feature which can be used to disable security when the phone is detected as on your person.
and this is how a very useful feature quickly became most annoying issue... because of a defective light sensor or its faulty software development.
another thing I don't understand: if screen is locked, why notification access isn't ?!? at least they should put an option to enable or disable it.
sony customer care ?!?
...
sadonlyone said:
another thing I don't understand: if screen is locked, why notification access isn't ?!? at least they should put an option to enable or disable it.
sony customer care ?!?
Click to expand...
Click to collapse
That's actually standard Android behaviour would you believe - both Lollipop and Marshmallow. Don't expect a "fix" for this anytime soon...
It's configurable on iPhone though. Go iOS!
I had to disable the double-tap to wake screen option as it was always triggering in my pocket (screen facing in). I only have screen lock set to swipe though so walking/climbing stairs was waking the screen, pulling down the notification panel and going to town changing settings. I even somehow managed to change the time display setting from 24 hour to 12 hour. I mean, how the hell can that happen in a short few minutes in a pocket?!