Android Studio code prompts that the error message is invalid (not available in Power Save mode) and androidstudio

Android Studio code prompts that the error message is invalid (not available in Power Save mode) and androidstudio

According to a question raised by a Boyou, I have written it here. It is estimated that many people will encounter this problem, but they do not know how to solve it.

After the Code Automatic prompt function is set, it does not take effect. To set the Code Automatic prompt, stamp this: how to set the Code Automatic prompt in Android Studio.

The reason for the failure is that you set the AS to power-saving mode. If you set it to power-saving mode, the AS will disable some auxiliary functions for power-saving purposes. So the code prompt is disabled.

If you want to modify it back, use the File option, and then click the checksum in front of Power Save Mode.

In power save mode ??? How can this problem be solved?

It may be power-saving. Or you press something on the monitor. enter the self-check system. generally, it is used when the seller checks whether there are any highlights when buying LCD display. I am not sure about the specifics, but it must be okay. it's okay to restart the computer!
(OSD will only work in "normal operation" mode. If you press the plus sign or minus sign when you disable the mode, the following message is displayed.
1. Auto Detect (Analog Input) In Power Save Mode Press Computer Power Button or Any Key on Keyboard or Move Mouse
Or
1. Auto Detect (Digital Input) In Power Save Mode Press Computer Power Button or Any Key on Keyboard or Move Mouse
Or
2. Analog Input In Power Save Mode Press Computer Power Button or Any Key on Keyboard or Move Mouse
Or
3. Digital Input In Power Save Mode Press Computer Power Button or Any Key on Keyboard or Move Mouse
In order to activate the computer, "Wake up" the monitor to enter the OSD .)
 
In power save mode

Step 2: First, check whether the external wiring of the computer is connected, and re-insert the connections to check whether the fault is rectified.
Step 2: If the fault persists, use the Plugging Method to check the memory. It should be caused by loose memory on the way back.