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] - Restart does not restart the device (ARM64) #1019

Open
n00b69 opened this issue Jan 16, 2024 · 8 comments
Open

[BUG] - Restart does not restart the device (ARM64) #1019

n00b69 opened this issue Jan 16, 2024 · 8 comments
Labels
bug Something isn't working, let’s fix that

Comments

@n00b69
Copy link

n00b69 commented Jan 16, 2024

Description

As the title says, restarting the device does not always restart it. Sometimes it works, but in most cases it does not.

Steps to reproduce

  1. Press the restart button
  2. It will either restart or be broken

Expected behavior

When I press the restart button, I expect the device to properly restart (like it does on normal Windows installations and even heavily unstable ones like Tiny11 Core)

Actual behavior

After the "Restarting..." screen disappears and the screen turns off, the device is still on but idling and it can only be restarted by holding the power button for 8 seconds.

Atlas Edition

Atlas for Windows 11 23H2

Desktop information

AtlasOS has been tested on two ARM64 devices and it has the exact same issue on both;

  • CPU: Qualcomm SM8150AC (Poco X3 Pro) and SM8150 (Mi Pad 5)
  • RAM: 8GB and 6GB respectively
  • Storage: 256GB UFS 3.1
  • GPU: Adreno 640

Additional content

This issue does not exist on Windowssimplify, Tiny11, Tiny11 Core and on regular Windows 11 21h2/22h2/23h2. I already tried changing the few power configs that are in the AtlasOS folder (e.g enabling hibernation), but this made no difference.

@n00b69 n00b69 added the bug Something isn't working, let’s fix that label Jan 16, 2024
@n00b69
Copy link
Author

n00b69 commented Jan 25, 2024

Small addition: this also affects the shutdown option, meaning it is impossible to shut down the system and you are forced to boot to recovery to turn it off.

@he3als
Copy link
Contributor

he3als commented Mar 19, 2024

Is this fixed by enabling hibernation from the Atlas folder? That was a solution someone shared with a similar issue.

@n00b69
Copy link
Author

n00b69 commented Mar 30, 2024

Is this fixed by enabling hibernation from the Atlas folder? That was a solution someone shared with a similar issue.

It is not, as was briefly mentioned in the "additional content" section.

In the meantime I have also installed and actively used ReviOS, which does not have this issue at all (even though it does not even have ARM support).

@the-P1neapple
Copy link
Member

Hello @n00b69, can you confirm the issue is fixed when updating to v0.4.0?

@n00b69
Copy link
Author

n00b69 commented Apr 9, 2024

It is

@n00b69 n00b69 closed this as completed Apr 9, 2024
@n00b69
Copy link
Author

n00b69 commented Dec 18, 2024

This issue is back in AtlasOS 0.4.1 on Windows 24H2.

@n00b69 n00b69 reopened this Dec 18, 2024
@n00b69
Copy link
Author

n00b69 commented Dec 18, 2024

Correction: this bug also exists on 0.4.0, but only in 24H2.

@TheyCreeper
Copy link
Member

0.4.0, but only in 24H2.

Well AtlasOS 0.4.0 is only available for Windows 11 23h2 and Windows 10 22h2, so this is pretty irrelevent

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working, let’s fix that
Projects
None yet
Development

No branches or pull requests

4 participants