Invalid Auto reboot issue after two hours of screen lock

[rednotec]

I am reporting a persistent issue encountered on my Xiaomi 15 device after installing EU ROM.

Issue Description:
The device functions normally during active use (screen on) and short periods of screen lock.
However, if the screen remains locked for two hours, the device will automatically reboot.

After rebooting, the device successfully enters the system and functions normally again, if the screen is locked for another two hours, the device will reboot once more.

 

[Igor Eisberg]

Seems like some problem related to storage (vold/volume daemon), but there's nothing informative about it in the log.

 

[rednotec]

Seems like some problem related to storage (vold/volume daemon), but there's nothing informative about it in the log.

what should I do next?
would it help to collect more detailed logs or provide specific device/storage details? Let me know how I can assist further.

 

[Igor Eisberg]

what should I do next?
would it help to collect more detailed logs or provide specific device/storage details? Let me know how I can assist further.

No clue. Never seen an issue like that, and nothing like that was reported. Doesn't look like an issue we are equipped to debug, not to mention fix without source code.

 

[rednotec]

No clue. Never seen an issue like that, and nothing like that was reported. Doesn't look like an issue we are equipped to debug, not to mention fix without source code.

I noticed you mentioned that the issue might be related to storage (vold/volume daemon), which gave me a hint. It might be connected to my modification of /vendor/etc/fstab.qcom to disable data encryption. Specifically, I deleted two instances of

fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,

in the file. After restoring the original fstab.qcom, the auto-reboot issue no longer occurs.

However, I previously applied the same modification to a Xiaomi 14 with HyperOS 1 (EU version) to remove its data encryption, and no issues arose. I don't understand why this approach causes auto-reboot issues on the Xiaomi 15. My intention was simply to disable data encryption to allow TWRP to access the data partition.

The only difference I can think of is that HyperOS 1 on Xiaomi 14 is based on Android 14, while HyperOS 2 on Xiaomi 15 is based on Android 15.

I don't know what else needs to be done to disable data encryption in Android 15 besides removing the encryption configurations in fstab.qcom.

 

[budibanyu778]

I am reporting a persistent issue encountered on my Xiaomi 15 device after installing EU ROM.

Issue Description:
The device functions normally during active use (screen on) and short periods of screen lock.
However, if the screen remains locked for two hours, the device will automatically reboot.

After rebooting, the device successfully enters the system and functions normally again, if the screen is locked for another two hours, the device will reboot once more.

Bug with the EU ROM causing the reboot. Have you tried checking for updates or doing a clean install? Could also be worth reporting this to the ROM developer.

 

[Igor Eisberg]

I noticed you mentioned that the issue might be related to storage (vold/volume daemon), which gave me a hint. It might be connected to my modification of /vendor/etc/fstab.qcom to disable data encryption. Specifically, I deleted two instances of

fileencryption=aes-256-xts:aes-256-cts:v2+inlinecrypt_optimized+wrappedkey_v0,keydirectory=/metadata/vold/metadata_encryption,metadata_encryption=aes-256-xts:wrappedkey_v0,

in the file. After restoring the original fstab.qcom, the auto-reboot issue no longer occurs.

However, I previously applied the same modification to a Xiaomi 14 with HyperOS 1 (EU version) to remove its data encryption, and no issues arose. I don't understand why this approach causes auto-reboot issues on the Xiaomi 15. My intention was simply to disable data encryption to allow TWRP to access the data partition.

The only difference I can think of is that HyperOS 1 on Xiaomi 14 is based on Android 14, while HyperOS 2 on Xiaomi 15 is based on Android 15.

I don't know what else needs to be done to disable data encryption in Android 15 besides removing the encryption configurations in fstab.qcom.

So you made a significant modification and forgot to mention it? :|
In any case, we had a Xiaomi 15 tester for quite a while prior to the public release, and while there was a different issue (which we fixed for the public release), he never complained about self-reboots.

Bug with the EU ROM causing the reboot. Have you tried checking for updates or doing a clean install? Could also be worth reporting this to the ROM developer.

If you don't have any proof for such a bold claim, better stay silent.

 

[rednotec]

So you made a significant modification and forgot to mention it? :|
In any case, we had a Xiaomi 15 tester for quite a while prior to the public release, and while there was a different issue (which we fixed for the public release), he never complained about self-reboots.

Apologies for not clearly mentioning the modification earlier. Since the same change worked without issues on the Xiaomi 14, I overlooked mentioning it and didn't anticipate that it would cause the auto-reboot problem on the Xiaomi 15.
I only made this one modification and did not change anything else.