Autodark option by romanseidl · Pull Request #6 · micw/OpenPhotoFrame

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

romanseidl · 2026-03-11T14:26:45Z

This implements an option where you can set a lux value below which the screen will turn dark and an offset from which it will turn ob again. So the photo frame will automatically appear to be off when the lights are off.

The implementation is not perfectly clean, so this will need some review. I was happy to get it working and wanted to share the idea and implementation.

micw · 2026-03-15T13:09:06Z

Great Idea. Did you check if it works together with the auto display off option (since this puts the device in sleep mode and sets a wake-up timer?

romanseidl · 2026-03-15T13:53:55Z

Yes, that should work fine. It's an "OR", so darkness or the schedule both set the screen to dark. This option only activates dark screen and never puts the device into sleep mode though as this would deactivate the light sensor AFAIK. But this could certainly need some more testing.

I was unhappy with the frame going off from me just standing in between the light source and the frame for some seconds making the screen go off when there is low light. So I now added some timer based delay / hystereis I would like to commit before a review.

micw · 2026-03-15T13:58:28Z

 void dispose() {
 WidgetsBinding.instance.removeObserver(this);
 _nextcloudUrlController.dispose();
+ //_luxSubscription?.cancel();


Why is it commented? I think it should be canceled in dispose, otherwise it's a resource leak.

micw · 2026-03-15T14:05:21Z

+ _darkScreenThreshold = config.darkScreenThreshold;
+ _darkScreenOffset = config.darkScreenOffset;
+
+ LightSensor.hasSensor().then((has) {


Better:
final has = await LightSensor.hasSensor();
(less nesting levels)

This is an async call to the then. Do you think it's a good idea to block by waiting for it?

micw · 2026-03-15T14:07:14Z

+ Future<void> _initLightSensor() async {
+ final hasSensor = await LightSensor.hasSensor();
+ if (!hasSensor) return;
+ _lightSubscription = LightSensor.luxStream().listen((lux) {


This is called multiple times but never cleaned. So multiple Listeners are created.

You are right on the lifecycle problems. I think this happened because I has issues with the lux subscription in the config page somehow killing the one in the slideshow display and I didn't really figure out why. One would have to sort this out.

May it be that only one listener per App is allowed?

I am not sure. In a virtual device it worked fine, in a real device with Android 15 it failed. .

I think I figured out the issue but I'll need some more testing. '
I suspect it's the order of events, when the settings screen gets closed. The "then" on the settings screen closing is fired before the "dispose" of the settings screen. So when I set up a new subscription in the "then" and then cancel the subscription in "dispose" there might be an issue. Using "pop" in the settings screen might help. But I'll have to test on a real device as the emulator is not too reliable with this.

micw · 2026-03-15T14:13:58Z

I reviewed it and found some minor issues.

There's one larger obstacle that needs to be discussed. When the "auto" mode is on, the device never goes to sleep mode. That should at least be very clear to the user.
Ideally, sleep mode would still be supported (e.g. using wakeup timer to check the brightness from time to time). But I don't know if this will work reliably.

Edit: also please rebase to master, I increased the flutter version.

romanseidl · 2026-03-15T14:18:56Z

What do you mean by "sleep mode"? Android power saving not starting? If that's the problem then one could solve that by a timer, that's a good idea.

romanseidl · 2026-03-17T14:57:39Z

I replaced this with #7

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

roman added 3 commits March 11, 2026 15:17

Autodark option
56254f7

Autodark option
1aae535

Autodark option
cb19266

micw requested changes Mar 15, 2026
View reviewed changes

romanseidl closed this Mar 17, 2026

Conversation

romanseidl commented Mar 11, 2026

Uh oh!

micw commented Mar 15, 2026

Uh oh!

romanseidl commented Mar 15, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

romanseidlMar 16, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

micw commented Mar 15, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

romanseidl commented Mar 15, 2026

Uh oh!

romanseidl commented Mar 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

romanseidl commented Mar 11, 2026

Uh oh!

micw commented Mar 15, 2026

Uh oh!

romanseidl commented Mar 15, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

romanseidlMar 16, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

micw commented Mar 15, 2026• edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

romanseidl commented Mar 15, 2026

Uh oh!

romanseidl commented Mar 17, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

romanseidlMar 16, 2026•
edited
Loading

micw commented Mar 15, 2026•
edited
Loading

romanseidlMar 16, 2026•
edited
Loading

micw commented Mar 15, 2026•
edited
Loading

romanseidlMar 16, 2026•
edited
Loading

micw commented Mar 15, 2026•
edited
Loading