I'm new to S21 FE. I was surprised when I saw the option "Keep screen on while viewing" in Settings. I enabled it because it should be a nice feature, but I can't see it working.
I change the display time to 15 seconds and the phone always switches the display off after 15 seconds (yes, I was looking at the phone).
Am I missing something?
Sorry, but the display time has nothing to see with the option "keep when on when viewing".
This option means that the screen won't shutdown while you're reading something on it (like a long text)
I just set this option on and give a try... a kept the phone in my hand looked the screen more than 30' (of course I didn't touch anything on it, I just looked it ) and he stayed on...
My English isn't good, and probably I wasn't clear enough.
Your test showed the behavior I expected. But it simply doesn't work on my phone. It uses time set in Settings. I expect that enabled "Keep when on when viewing" will override the time settings.
OK, it means that maybe he doesn't wields on your phone
What is the version of your ROM ?
Did you try to unset the option, restart the phone and set it again?
Did you receive a system update recently? If yes, did you do a wipe cash partition from the recovery? (recommended after major updates)
I got my phone a previous week and its firmware was updated in the process of preparing an Android for use with my account. In the first walk-through Settings I enabled the option "Keep screen on when viewing" because it looks interesting to me, but it didn't work. Two days ago I got a new firmware (G990BXXS2CVC6) and it still doesn't work.
I tried enabling/disabling but it didn't help. I also restart the phone and didn't help.
I didn't wipe the cache partition from the recovery.
And here is some additional info from this morning. I noticed that the screen keeps on (if I look at the screen of course) if the phone is charging! When I pull off the cable, this feature doesn't work anymore.
That's strange! On mine it works even he's not charging
Maybe you can try to do the wipe cache partition... but if he works like that from the begin, maybe it will be useless.....
Your phone is also a snapdragon one?
Strange, I agree.
Yes, it is a snapdragon dragon.
I will carefully follow the behavior in the next days.
Once (or twice) today I noticed that function worked (without charging). But it is very rare.
Related
Hi folks, having a slight issue with my TP2. It is running the preinstalled vodafone rom for the UK. (version 1.14.161.6 (50207) WWE)
Over the last two days it has stopped automatically powering down the screen when not being used. The backlight switches off as normal, but the screen does not shut down until i press the power button. So if I forget, the screen can stay on all night, killing the battery.
Have been into the settings,on the power screen, and checked all 4 boxes are checked for the times to shut off the backlight and screen on both battery and mains power, and they are.
Any ideas? I have not installed any new software so am stumped. Any common causes of this behaviour?
Cheers
Jon
did you change it through the manila settings tab or start/settings/system/power/backlight ? the reason why i ask is because sometimes when you set settings through manila tab settings, the settings dont work. try deactivating manila, then start/settings/system/power/backlight , then reactivate manila. hope that helps. if not im stumped too.
Is manila part of touchflo? If so I don't have it enabled, I just use spb shell on top of winmo 6.1, so yes was using start/settings/power method.
However, not sure if I have hit upon the problem - I use a program called g-alarm (which is one of the best programs ever), and in it's settings there is a way to keep the screen on when the alarm is snoozed. I recently enabled this, and wonder if it might have messed up the os settings somehow.
I tried uninstalling g-alarm last night and it made no difference, but since restoring a backup, and changing the screen-on setting within g-alarm to off the phone is working normally.
I daren't re-enable the setting to test it, just in case the phone gets messed up again for good this time so this might be a total red herring, and perhaps it was just the restore that did the trick (although have restoring before at least 3 or 4 times with no joy). Will report back when I dare to mess again.
cool to here you are back to normal lol. it would have been a major hassle if you had alot of apps, accounts and whatnot to reinstall. i got really pissed at g-alarm one time when it wouldnt stop going off (phantom alarm) so i will never use it again. you might want to find the thread from where you got it and report the bug. maybe someone else has the same problem and the developer came out with a patch or upgrade for it.
Had same problem on 2 phones
I had same problem on 2 phones- Tilt2 and Kaiser (Tilt). Problem was.... Microsoft Live. When mail account set to ..As Arrived... phone doesn't go to sleep and keeps screen on permanently. Battery was empty in half of the day. After I switched to use POP or IMAP mail and stopped using Live, everything became normal and works excellent.
Here is the Answer
Maybe you have played some games and did not close it by the normal way..
Try to change the registry:
自动关屏时间
HKCU\ControlPanel\BackLight\
"BatteryTimeOut" = 10
Then
另一种方法是在HKCU\ControlPanel\Power\
Display=25 改成自己想要的值
If there is not one,create it by yourself..
Well, it still happened today, so I think that rules out the g-alarm backlight setting. However, it worked fine most of the time, so intermittent.
Papasha, I think you could be onto something there, I do use MS live. Be a shame to lose the push mail though, but that's the next thing i'll try disabling if it recurs again.
Will try that too fishman if problem comes back, the backlight key is present but the display setting is not. Easily created though.
*post Updated on 28-1-10*.
The problem did start recurring again, so I tried the suggestion to disable the hotmail pushmail (sync items as they arrive) and that has definitely sorted the problem. As a very welcome side effect the phone suffers major slow downs far less now, if at all. I still use livemail but just set it to sync every 60 mins.
Hi,
When i get a call and i click on "decline" button, i should get a pop up allowing me to send a quick message or make a reminder about calling back.
I checked and the relevant options are ticked on in the phone settings section.
What happen though is that i decline the call and the pop up shows for a split second and disappear :\
I attached a picture of the evasive pop up.
I tried ticking the option on and off, rebooting, nothing helps.
The only thing that seemed like it changed was resetting the phone (on power menu, you can reboot and delete temp files or something like that). That made the feature work once, but on the seconds time i declined a call it dissapeared again.
I did make sure the "Don't show this again" option is UNCHECKED.
I searched XDA forums and google, and only found one relevant topic which did not solved my issue.
Help...?
yrufset said:
Hi,
When i get a call and i click on "decline" button, i should get a pop up allowing me to send a quick message or make a reminder about calling back.
I checked and the relevant options are ticked on in the phone settings section.
What happen though is that i decline the call and the pop up shows for a split second and disappear :\
I attached a picture of the evasive pop up.
I tried ticking the option on and off, rebooting, nothing helps.
The only thing that seemed like it changed was resetting the phone (on power menu, you can reboot and delete temp files or something like that). That made the feature work once, but on the seconds time i declined a call it dissapeared again.
I did make sure the "Don't show this again" option is UNCHECKED.
I searched XDA forums and google, and only found one relevant topic which did not solved my issue.
Help...?
Click to expand...
Click to collapse
You might just have to do a complete factory reset. Sometimes, system functions can get screwed up for no apparent reason (it is usually something else you installed). Are you stock or on a custom ROM?
Hi, thanks for your reply.
I guess that deep inside me, i knew you would recommend that...
The device is new. Bought it last week. it's stock, unrooted, untouched.
I did a lot of rom changes before with my other device (GS3) so i'm no stranger to factory reset, but every time i used it was to completely change a rom. I have never done it on a brand new device in order to actually reset a glitch...
Can you tell me what exactly will factory reset delete? What will i loose? any personal data? apps? app setttings? what else?
Thanks :cyclops:
So this is driving me nuts. I just picked up an S7 Active, and restored my data from Samsung Cloud. Everything restored fine except for Settings. That part fails every time. No big deal, I thought. I just set it up again how I like it. As soon as I got everything how I wanted it, Do Not Disturb immediately started acting super-weird. It turns on by itself, and it takes 2-3 times of turning it off to get it to stay off. When I finally get it off, it resets the settings (stays custom, but turns off all alarms, calls, and messages). I want it to allow alarms and calls/messages from favorites, and as soon as I enable those, it automatically turns Do Not Disturb back on. Turning it off again starts the whole loop over. Clearly, my Do Not Disturb settings are corrupt. Is there a way to wipe those settings, without wiping the phone and starting fresh?
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Acinko said:
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Click to expand...
Click to collapse
Yes, factory reset, or worst case, ODIN flash the firmware. I just wanted to see if it was something anyone else had run into. I'll tackle this over the weekend. Thanks for the response!
bug
I had turned facebook and gmail to silent notifications. DND has not turned on and media volume has not turned to zero since allowing these apps to show with sound again.
Think every time a notification comes in media volume is set to 0 and DND turned on.
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
It seems the problem is more severe than just Android.
Because even in TWRP, I noticed the display need to wait ~1 minute from the last time I turn off the display (push the power button) to reactivating it.
If I try to turn it on, the display will give black color, but I still can actually interact with the system.
ArcOnFire said:
I've gotten this problem since 20 days ago where my Google Maps get frozen in the middle of my trip. And I had reboot the device multiple times (4-5 times, sometimes skipping the LineageOS booting animation).
After fiddling over 2 weeks, I finally switched to LineageOS 17.0 now (previously using 15.1). The problem still persists.
The problem is : the screen froze, I seem able to tap something on screen but the display doesn't change anything despite my interaction with screen. This especially pronounced when I stop my screen interaction (i.e. not scrolling) on these apps
- Google chrome (say, reading any articles on web)
- Quora (especially when I about to scroll down on author bio)
- Google Sheets
- Maps
but this unresponsiveness doesn't appear at all when I:
- Play any kind of games
- watching YouTube (with the app)
In general, it seems anything that uses webview can cause the screen freezes if I leave it couple seconds. At first I thought changing from android webview to chrome webview implementation changes this. It doesn't.
The "cure" I found is simply turning the display off for 40 seconds ~ 75 seconds, and turning it back on, where I can interact with lock screen fine again. Any time lower than 40 seconds will simply show the frozen display again the time I turn the screen on.
Is it possible it's a hardware problem? (faulty RAM/storage) after using this for 2.5 years) Since full system wipe and re-install doesn't entirely solve the problem. The first time I encountered this is when I navigate with my Google Maps and the screen simply froze out during drive, and I had to restart the device multiple times, worrying that my device is broken. The next time I drive, I leave it only on Ambient Display and it didn't freeze at all.
So... any idea how to troubleshoot this?
Click to expand...
Click to collapse
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Shimizux said:
Can you enable "Show Tap" option in developer settings and see if theres any ghost touch happening, sometimes ghost touch can "freeze" the screen while you want to interact with it
Click to expand...
Click to collapse
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
ArcOnFire said:
Thanks for responding.
I already enable "Show taps" on developer options. But the problem is that the screen freeze happened when there was no touch at all (i.e. I just looking at the screen, reading)
There's new observation I made today that : usually the screen doesn't want to immediately awaken when I just turn the screen off.
Today I tried to remove fingerprint from lock screen, the screen now is able to respond quickly again upon pressing power on button. It's still as responsive to power on when I add pattern to the device lock mechanism.
I'm not too sure whether this is OS level problem or even closer to hardware problem because this kind of unresponsiveness is also apparent even when I boot to TWRP.
Click to expand...
Click to collapse
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Shimizux said:
That is one big weird problem, i've never encounter something like that since i ever using a smartphones.
It does really sound like, it just a software problem. But if it also happen in TWRP, it doesn't look like it.
I also have installed LOS17 by Arian before too, and i dont have that problem.
Sorry man i have no idea nor expert about it
It could be your battery is dying?, if your battery cant give enough power to the screen already, screen gonna act like crazy i.e ghost touch etc.
I have a broken battery been using it for 2Year + because of the battery my screen has a problem too. I replaced it last december 2019 and everything went normal again.
Click to expand...
Click to collapse
I don't think it's a battery problem. I see that I can play game for 1hr+ fine. A game that require exact timing of 2 touches on top of that. So that ghost touch really doesn't appear.
But yeah, it's really 2 contrasting sign
- In one hand, it seems an OS problem because I can simulate an environment where the screen definitely won't be frozen for hours, while on specific other environment, the screen freeze can happen very quickly between release and re-occurence.
- On the other hand, the problem seem doesn't stop on OS level because it can be found in TWRP.
If I read an answer on Quora that shows GIF image on the section I read, the screen freeze 100% won't happen. I tried the same thing on imgur too, the screen freeze won't happen.
So it seems that as long as the screen is showing dynamic content, it won't freeze (that's why game and YouTube doesn't show this kind of problem, but reading a web full of text/static images can)
A bit of update : I have left my phone in off state for 4-5 days. And I have been using it again, albeit, less extensively since my main phone has changed to K20 Pro.
Long story short : I haven't encountered screen freeze again. But this is just after 2 days playing with less intensity.
I wonder what really went wrong.
I had been playing with some settings in the hidden menu and developer options sometime before this problem began but AFAIK I returned everything back to default and the phone was working fine for a while afterwards. So I am not sure exactly why the Wifi and bluetooth stopped working. When I dragged down the notification bar to toggle the Wifi icon it just flashes like a strobe light and never turns on. If I go to toggle the slider in the Settings menu, it's either greyed out, or immediately slides back to Off. Discovered that the bluetooth also did the same thing, but Data connection still worked. Also for some reason the phone now took a solid 60 seconds to boot up when it used to take 30 or less.
I did a factory reset in case I had overlooked changing some option back to default, and when that didn't work I flashed stock ROM H815-20g-00-1023 (I'm ~ 95% sure it was running 20g to begin with but it might have been another letter instead) with LGUP. But the problem still persists --- I can't complete the LG setup process because the page for setting up the internet connection is either completely blank or if it does come up the checkbox for Wifi is greyed out... and even if the mobile data option is able to be selected the setup wizard will not let you proceed without Wifi.
Any idea what might be the problem and how to fix?
Many thanks!
I've looked every which way on Google for possible solutions but none of them match the scenario I'm describing. Is this really a problem that no one else has ever had? :-O