-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frontlight will turn off after 1-5 min on Kindle Oasis 3 #9409
Comments
What about the autowarmth plugin: Is that disabled, and if not how is it configured? |
I have the autowarmth set to location (sun's position). That works normally. I have auto dark mode turned on after sunset (with maximum warmth). The frontlight will turn off after a random number of minutes during dark mode as well. This problem is only on 2022.06 and 2022.07. |
Double-check that it works with the autowarmth plugin disabled; ping @zwim for actual ideas ;). (We're going to need verbose debug logs too, so feel free to catch the issue in those :)). |
We are fishing in the dark! We need more infos. So first of all we need some crash.log. A cash.log has a lot of infos for debugging. It is more than a crash.log (although the name suggestsit ), it is a log of whats happenig. So please go to filemamager-tools-developer options and enable all of the debuggoimg stuff. Which plugins are enabled? Second disable all plugins. Does it work. If no: crash.log if yes, enable one plugin after the other ... tell us what plugins work and what not and post a crash.log for the not working. |
Ok. So I reinstalled 2022.07, disabled the auto frontlight plugin and the auto dimmer plugin. Now I have a new problem. Adjusting the auto warmth settings cause koreader to crash. Crash.log below:
| |/ / _ | _ \ ___ __ _ | | ___ _ __ It's a scroll... It's a codex... It's KOReader! [] Current time: 08/04/22-22:30:09 ffi.load: blitbuffer --- 192.168.1.1 ping statistics --- |
I erased koreader folder and logs completely when I went back to 2022.05 so lost the original crash.log for the randomly turning off front light bug. Doh! |
Copying the autowarmth.koplugin from version 2022.05 seems to fix autowarm settings crash. |
Can you add
This should only fix the crash. The original problem with frontlight turning off might still consist. |
Hi. I've added this line into main.lua finally. I can confirm this stops the crash from adjusting the 'warmth and night mode settings' in the autowarmth plugin from 2022.07. With the 2022.05 autowarmth plugin and auto frontlight OFF the screen frontlight turning off problem stopped. I'll do a bit more testing with the edited 2022.07 plugin. The front light did still appear to be adjusting to the ambient light even with the auto frontlight plugin turned off though. |
Thank's for confirming, the crash has stopped with #9411. For the frontlight turning off problem, a complete |
Thanks for the suggestions. So something strange is happening. I reinstalled the stock 2022.07 autowarmth plugin, the one that caused the crashes, for testing. It now no longer crashes. I re-enabled all plugins, including auto frontlight. The front light turning off bug doesn't happen any more either. The only difference in the last couple of days is that the kindle auto updated to 5.14.3.0.1 from 5.14.2. I've attached the crash.log and settings.reader.lua (renamed to a txt file to enable upload) below. Bear in mind doesn't have the frontlight turning off bug (due to a complete delete and reinstall) but does have the autowarmth plugin repeated crashes. |
Another update. Managed to recreate the crashing with the stock 2022.07 autowarmth plugin. It happens at night (I have dark mode on as the autowarmth setting). Using the modified plugin with the altered line 310 fixes this crash. |
Fixes the crash mentioned in #9409 (comment)?
Issue
The frontlight will turn off after 1-5 min. Every time. I've turned off the automatic dimmer.
Steps to reproduce
It happens every time for me.
crash.log
(if applicable)Koreader doesn't crash. I can turn the frontlight back on. It will turn off again after a few minutes.
Restoring version 2022.05 gets rid of this bug. I've had to revert to the old version.
The text was updated successfully, but these errors were encountered: