Reset brightness to system when app closed, instead of waiting 4 hours

[Spok1]

Checklist

• I am able to reproduce the bug with the latest version given here: CLICK THIS LINK.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected version

0.25.2

Steps to reproduce the bug

1.Open some video;
2.Turn down brightness;
3.Quit the application;
4.Unload from RAM or reboot the phone for completeness.
5.Open the application and see that the brightness remained at the level of the previous adjustment, but was restored to the system value, as you stated.

Expected behavior

So that the brightness values ​​are restored to the system default value.

Actual behavior

Brightness does not reset to default after starting a new session.

Screenshots/Screen recordings

Details

8c582cfe-ca1a-4085-a5b6-3d59a7aee1f3.mp4

Logs

No response

Affected Android/Custom ROM version

Android 10

Affected device model

Xiaomi Redmi 7A

Additional information

No response

[Pentaphon]

@Spok1 try using the newest 0.26 first

[Spok1]

Nothing changed! Do you know why? Because no one has reported this before. Therefore, there is nothing to fix.

[Pentaphon]

This is expected behavior. Why would you want the brightness to keep going back to the system value? I like Newpipe having its own brightness that I set myself.

[Spok1]

Because this behavior is in the video assistant Samsung internet browser And I liked it. Also, on my old tablet the brightness is set to the minimum brightness to save battery, and the brightness in the new pipes will remain the same as I did, for example, and since I have Not the brightness percentage, I can't adjust exactly the same.Therefore, I have to disable the adjustment gesture so as not to accidentally touch the control, otherwise I will never return to the desired value again.

[opusforlife2]

It was normal behaviour for Newpipe to reset to system brightness when swiped away from Recents or closed in another way. This no longer happens. I'm not sure when this behaviour was changed.

[Pentaphon]

It was normal behaviour for Newpipe to reset to system brightness when swiped away from Recents or closed in another way.

This doesn't make any sense to me because it forces many users to keep changing their brightness every time Newpipe gets closed in some way. It's much more convenient for Newpipe to have its own brightness level so I can set it once and never have to set it again when watching videos. This behavior is welcome by many users and should stay as an option at the very least.

[Spok1]

This behavior is welcome by many users and should stay as an option at the very least.

In this case, a choice is needed, otherwise it can be considered incorrect behavior. It’s easy to swipe left and change the brightness to the desired value.

[Pentaphon]

In this case, a choice is needed, otherwise it can be considered incorrect behavior.

It's not incorrect if many people like me prefer it. I'd like it to stay as an option. Plenty of people seem to enjoy it as it is, considering you are the only person to file an issue about this behavior being "incorrect" in a long time.

[opusforlife2]

in a long time

That's simply because the current behaviour is fairly recent.

There was a slightly different but related behaviour in earlier versions where taking the brightness down to zero would actually revert it to system brightness. But this was also seen as a bug of sorts because it was weird to first go down and then up in brightness. So that was changed.

Hmmm. Maybe that change is actually the culprit here. @XiangRongLin what's your opinion?

[Spok1]

@opusforlife2

it was weird to first go down and then up in brightness. So that was changed.

This is not strange, but quite adequate behavior. Similar behavior in Samsung browser. And I think this is true!

@Pentaphon,

considering you are the only person to file an issue about this behavior being "incorrect" in a long time.

I may have been silent and not sent a report in the hope that the developers would fix it, but this did not happen for a long time, so I decided that this was a bug and they were not aware of it, but as it turned out, it was passed off as a feature! Extremely depressing!

[XiangRongLin]

@opusforlife2

where taking the brightness down to zero would actually revert it to system brightness

I remember this, but I can't find any commit from me related to that.

---

I found this code block, but the behaviour exists since the preunified player, which was dec 2019

NewPipe/app/src/main/java/org/schabi/newpipe/fragments/detail/VideoDetailFragment.java

Lines 2030 to 2036 in 1d8850d

	// Restore already saved brightness level
	final float brightnessLevel = PlayerHelper.getScreenBrightness(activity);
	if (brightnessLevel == lp.screenBrightness) {
	return;
	}
	lp.screenBrightness = brightnessLevel;
	activity.getWindow().setAttributes(lp);

Note that the brightness only gets saved for 4 hours. After that i defaults to the system value

NewPipe/app/src/main/java/org/schabi/newpipe/player/helper/PlayerHelper.java

Lines 362 to 374 in 1d8850d

	public static float getScreenBrightness(@NonNull final Context context) {
	final SharedPreferences sp = getPreferences(context);
	final long timestamp =
	sp.getLong(context.getString(R.string.screen_brightness_timestamp_key), 0);
	// Hypothesis: 4h covers a viewing block, e.g. evening.
	// External lightning conditions will change in the next
	// viewing block so we fall back to the default brightness
	if ((System.currentTimeMillis() - timestamp) > TimeUnit.HOURS.toMillis(4)) {
	return -1;
	} else {
	return sp.getFloat(context.getString(R.string.screen_brightness_key), -1);
	}
	}