Skip to content
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

[BUG] Not working on OnePlus 9 Pro #10

Closed
AlexV525 opened this issue Mar 30, 2021 · 13 comments
Closed

[BUG] Not working on OnePlus 9 Pro #10

AlexV525 opened this issue Mar 30, 2021 · 13 comments

Comments

@AlexV525
Copy link
Contributor

Just got the new OnePlus device, tested with the plugin and it seems not working well.

matches.last is at 120Hz refresh rate.

image

@AlexV525
Copy link
Contributor Author

Tracking native code, the logic seems solid but it doesn't take effects.

image

image

image

@AlexV525
Copy link
Contributor Author

Do you think whether I should reopen the closed issue in flutter repo again?

@ajinasokan
Copy link
Owner

ajinasokan commented Mar 31, 2021

Did you check the settings to see if there is anything that can block this? From what I read OP9 has a new mode to automatically switch to high refresh rates of its LTPO panel.

Have a look at logcat as well while you try to switch modes.

@AlexV525
Copy link
Contributor Author

Did you check the settings to see if there is anything that can block this?

Checked, currently the factory mode is unable to call, the only place to control the refresh rate is here:

Screenshot_2021-03-31-13-03-48-03

From what I read OP9 has a new mode to automatically switch to high refresh rates of its LTPO panel.

You mean the automatically 1~120Hz mode? Yes it's enabled by default when you choose the 120Hz refresh rate.

Have a look at logcat as well while you try to switch modes.

There are no helpful logs when toggling between modes.

@dJani97
Copy link

dJani97 commented Mar 31, 2021

@AlexV525 I know it's not a proper fix, just curious: does this ADB command work for you?

adb shell settings put global oneplus_screen_refresh_rate 0

On previous OnePlus phones, this command disables optimization and forces the phone to use it's max refresh rate all the time. It works well with the 8T in all Flutter apps and even some games.

@AlexV525
Copy link
Contributor Author

@AlexV525 I know it's not a proper fix, just curious: does this ADB command work for you?

Sure, this global setting works fine in every previous OP devices, I used to use this trick on 8 Pro. But now 9/9 Pro has switched to ColorOS (maybe only in China) so the config list doesn't include the column anymore.

More further info is I tried to switch between modes in settings and see if there is a column being modified, but it didn't.

Anyway thanks for the reply, but it's failed on OP9+ColorOS.

@dJani97
Copy link

dJani97 commented Mar 31, 2021

Right, I forgot about the ColorOS part.

Then I wonder if this issue with changing the display mode is specific to the OnePlus 9 Pro, or rather it's an issue with ColorOS. It would be interesting to see results from older ColorOS devices, and also the OxygenOS version of the OnePlus 9 Pro.

@AlexV525
Copy link
Contributor Author

Yep. Since my new device will be use as a daily driver, I don't have plans to make it Oxygen currently, and I don't have any devices that can both have high refresh rate and ColorOS (my OP8 is going to be recycled).

@AlexV525
Copy link
Contributor Author

@AlexV525
Copy link
Contributor Author

AlexV525 commented Apr 1, 2021

Now I'm pretty sure that this is a ColorOS issue because #6 looks like the same problem. ColorOS is used both on OP9 and OPPO devices.

@AlexV525
Copy link
Contributor Author

AlexV525 commented May 6, 2021

Good news, OP9 now supports to update the display mode manually. So I'm going to close this.

image

@AlexV525 AlexV525 closed this as completed May 6, 2021
@jerboy
Copy link

jerboy commented May 7, 2021

@AlexV525 which version of colorOS has fixed this bug?My colorOS version is V11.2, still not fix.

@AlexV525
Copy link
Contributor Author

AlexV525 commented May 7, 2021

@AlexV525 which version of colorOS has fixed this bug?My colorOS version is V11.2, still not fix.

11_A.06
Screenshot_2021-05-07-11-41-57-09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants