MisterZtr / PixelOS_gsi

Script and patches for building PHH-Treble based PixelOS GSI
110 stars 15 forks source link

Enabling Data Saver causes system to be stuck loading with boot animation #85

Open 1987tl opened 1 month ago

1987tl commented 1 month ago

I just started using PixelOS, so I have only used Pixel 14 June build (20240630). Not sure whether the issue occurs in earlier builds as well. I am using a Samsung Galaxy Tag S6 if it matters.

Basically when enabling "Data Saver" in the "Network and Internet" section within the settings and accepting the confirmation prompt, the boot animation screen appears and remains endlessly (it is not frozen, but the loading bar keeps moving forever). The system isn't restarting here, the boot animation appears immediately. When forcing a restart, the system appears to start the boot process but then gets stuck with the boot animation again and never recovers. So it is stuck loading forever.

I tried booting into recover to clear the cache and even reflash the system image, but the it is still stuck on the boot animation screen. I couldn't figure a way to disable this option via reocvery. The only way I could recover from this state is to format the data start fresh again.

If more information or logs are required, let me know how to do so, keeping in mind I can't find boot into the system anymore when the issue occurs.

MisterZtr commented 1 month ago

I think, problem is with old kernel 4.14. You can use February release, where google hasn't removed support for that kernel yet

1987tl commented 1 month ago

No problem, thanks for the reply. I ok with sticking on the latest build and not enabling data saver, just need to make sure I don't enable it by mistake in the future :)

Byteintosh commented 1 month ago

No problem, thanks for the reply. I ok with sticking on the latest build and not enabling data saver, just need to make sure I don't enable it by mistake in the future :)

Have you tried February release yet? I encountered the same problem. But got soft restart in kernel 4.19. #63