Develop Bugs

[Q] Anyone having issues with the automatic screen shutoff?

I am running CM 6.1 Stable, and have been for a while, yet this issue just popped up a few days ago.
I cannot get the phone to auto shutoff the screen when idle. I have it set to 5sec off and 1 sec lock, (down from 30 sec off, 5 sec lock before).
I have looked at the stock settings and all are in order.
The only thing different is I was trying to play with the setting on my Alarm Clock Plus regarding screen setup, but have reverted to original settings and even rebooted several times with no success.
Anyone else having issues with this? Any way to enable screen off again without having to flash a recovery?
It's really killing my battery fast!
Thanks for you help!

Crey23 said:
I am running CM 6.1 Stable, and have been for a while, yet this issue just popped up a few days ago.
I cannot get the phone to auto shutoff the screen when idle. I have it set to 5sec off and 1 sec lock, (down from 30 sec off, 5 sec lock before).
I have looked at the stock settings and all are in order.
The only thing different is I was trying to play with the setting on my Alarm Clock Plus regarding screen setup, but have reverted to original settings and even rebooted several times with no success.
Anyone else having issues with this? Any way to enable screen off again without having to flash a recovery?
It's really killing my battery fast!
Thanks for you help!
Click to expand...
Click to collapse
In the android display settings, 15 seconds is the least amount of time to turn off display. how is yours set to 5?
In cyanogenmod settings, theres options to tell the lockscreen to kick in after the screen has automatically turned off and when the user has pushed the power (sleep) button. what is your time set to in the android settings? (settings - display - screen timeout)

Nissan350 said:
In the android display settings, 15 seconds is the least amount of time to turn off display. how is yours set to 5?
In cyanogenmod settings, theres options to tell the lockscreen to kick in after the screen has automatically turned off and when the user has pushed the power (sleep) button. what is your time set to in the android settings? (settings - display - screen timeout)
Click to expand...
Click to collapse
Um....finding rock, and hiding underneath it!!!
Turns out I am a moron that can't read.....but I swore that I had the display set to 30 sec....It was disabled. I will test again, over the next few days if for some reason it reverts to disabled.
Thanks!

Crey23 said:
Um....finding rock, and hiding underneath it!!!
Turns out I am a moron that can't read.....but I swore that I had the display set to 30 sec....It was disabled. I will test again, over the next few days if for some reason it reverts to disabled.
Thanks!
Click to expand...
Click to collapse
Lol no prob. Happens to the best of us!

[Q] Screen Timeout and Brightness Settings not Persistent

I am using LG G3 D855, up to date version. My problem is if i set Brightness Auto , and Screen timeout 30 sec. After every restart it keeps Brightness resetting to 100% And Screen timeout to 2 mins. Did Factory reset, Without Signing in to Google too. Still the same.
Should i Flash the orignal firmware again ???

rohanhole said:
I am using LG G3 D855, up to date version. My problem is if i set Brightness Auto , and Screen timeout 30 sec. After every restart it keeps Brightness resetting to 100% And Screen timeout to 2 mins. Did Factory reset, Without Signing in to Google too. Still the same.
Should i Flash the orignal firmware again ???
Click to expand...
Click to collapse
I was doing without sim card !! got a sim card inside and worked ! so dont forget to insert a sim card

I'm having a similar issue with my AT&T version. I set the screen timeout to never turn off and every time I restart the phone it's back to 30 seconds.

I have a couple of LG G3 D852's...both exhibiting the same issue. Another D852 saves the settings just fine even after reboot/restart. Thing I also noticed is that when powering off the 2 D852's, I'm unable to power them back on unless I do a battery pull as well. Not sure if this is just coincidental.

Screen keeps auto dimming even when set to 100% - Eonon 5.1.1

Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!

brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.

halloj said:
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.
Click to expand...
Click to collapse
Whoa, thanks for the quick reply and useful information. Is there absolutely no way to bypass having to do that method? As that would be a chore doing it multiple times after exiting and entering my car multiple times a day. Maybe a simple build.prop edit possibly? Just naming ideas.

There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.

miffymiffy said:
There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.
Click to expand...
Click to collapse
You could disable brightness control entirely or just alter the brightness levels.
It's in file /system/etc/install-recovery.sh - at its end, comment out all 14 lines after comment line reading "#Brightness control (last, always)", in order to disable the algorithm.
OR, change line reading "nb=5 ### Night Brightness ###" to a different value for the night brightness (nb), eventually equal to day brightness (db, on next line).
Use a root explorer, or edit a copy of file on PC (with notepad+ if on Windows) and copy it back - with a root explorer or manually, if you can. File mode: 0755, owner & group: root:root.
If script /system/etc/install-recovery.sh gets "damaged", you must reinstall the firmware, but with NO wipe all, so fairly quickly and no loss of settings and apps.
Editing of script could also be done with @devilsoft app (with a name I can't recall).

brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
Hi @brian117 !
In fact, there is a simple fix I found lately.
You need to enter factory settings first.
Go to SETTINGS -> Factory settings -> enter code: m123456
When you're there, go to last page, and tick the "Key light" option.
Now press "Apply" and "Exit". Confirm reboot.
It worked with me - now the screen has full brightness regardless of the car lights on or off (in Poland we need to have the lights on whole day, as well). Now you can use a software dimming, like MTC to auto dimm the screen according to actual day time. I did this. Works like a charm! (I set dimming after sunset to 75% brightness)

Display timeout keeps reverting to 30s

Display time out keeps going back to 30 s. I changed my power modes quite a bit so far. It may be when I turn OFF the battery in the settings dropdown toggle. It calls itself optimizing, when it's turned off. I was able to carefully set options for battery saving with toggle on, and checked that turning ON the battery toggle didn't cause the 30 s reversion.
I need a fixed 10 minute set. I can't stand the 30 s reverting because the fingerprint sensor has been so faulty so far with waking it back up.

Same problem as me, we need to report to samsung to solve in next sw update

Right. Back to 30 s time then off after every other restart. Latest updates too.

well according to settings>device care it says that optimization happens once a day. That's probably why it is happening.

I may disable it. I def recommend that you set an extremely long time (files(Samsung A70s native file manager app)>settings)before it auto delets your files. Like 200 months would be probably ok.

Always on display "flickering" when activated (on tap)

Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)

Frans1897 said:
Hey everyone!
As the title say i'm facing a issue with my always on display.
I'll try to make it as simple as possible:
When I set the always on display to be always active it works flawlessly.
When I set the always on display to activate on tap (and last for 10 seconds according to the settings) it appears for roughly 3 seconds and then disappears for 3-4 and reappears flickering for 2-3 times sometimes showing the desktop wallpaper between each flicker.
Did anyone experience the same issue?
What I did to try and fix it was:
- tested both on battery and while charging
- factory reseted and then restored backup (which was stupid, that lead me to the second point)
- start in safe mode (to check whether it was an app causing troubles) but no such luck, problem still occurs.
- uninstalled "nice lock" apps
- changed some settings under the always on display tab
- cleared cache of the always on app
What you should know:
- I'm running android 9, not rooted and have nova launcher as default home
- After I factory reseted the phone I wanted to stop always on display from updating to test whether it was a new version issue but I forgot and didn't make it in time so I'm currently running the latest version
Does anyone have any idea as of why it's behaving like this?
edit: just wanna be a little more clear, flickering is not meant like a lightbulb it's more something like it turns off and back on after a delay (I'm sorry english is not my native language I can't really explain it any better)
Click to expand...
Click to collapse
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?

xprzs said:
i also experience the same.
this phone has many strange bugs.
when i restart my A70, tap to show always on display works for me for 2-3 times.
after 2-3 times working correctly, the bug starts.
after i tap the screen, it shows AOD for 2 seconds. then turns the screen off and then at the end of the 10th second, screen just flashes itself for the last time and turns off completely.
i think it is related to the fingerprint scanner.
because after i registered my fingerprints and turned on unlocking the screen by the FP reader, this bug ends.
after i tap the screen it shows both the clock and fingerprint icon at the bottom of the screen.
after 2 seconds fingerprint icon disappears. and the clock is continued to be shown until the end of 10th second.
but there is a minor issue, when the fingerprint icon disappears, the AOD screen brightness changes. dims or brighter slightly.
can you please try tap to show AOD, by enabling the fingerprint unlocking?
samsung ?
Click to expand...
Click to collapse
Hey! Thanks for the answer, I can confirm we have the exact same issue. I also have the same brightness issue you described
Anyway, I have always used fingerprint unlock though so I don't know what to answer you.. I only recently noticed the weird behavior. I did a couple things to test and I found out that enabling the "fingerprint" icon showing in the always on display seems to "fix" the issue of the flicker but not the one of the brightness change (after enabling it i've yet to see the problem occur), you should try it and let me know if you see any improvement. It's probably on samsung's end though and hopefully we get it fixed with android 10 or earlier
I'll take this chance to ask you another question; two weeks ago I received a software update and ever since that day I noticed my battery to be lasting waaaay less than it used to, did you update your phone as well? Did you notice a battery drain?

I have the issue both of you talking about.

hello, I had this same issue and what I did was turn the phone off, and booting it up while pressing "Volume Up", after entering a black screen with many options, I selected wipe cache. It has worked without a flaw since then. There's lots of bugs with this phone. I recently had a problem where the USB port will detect a device and "plugged and unplugged" it, making my phone unable to dim. Thankfully I was helpful.