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] Iconify causes bootloops on QPR 1 U1B2 #313

Closed
ASPNyan opened this issue Oct 15, 2023 · 4 comments
Closed

[BUG] Iconify causes bootloops on QPR 1 U1B2 #313

ASPNyan opened this issue Oct 15, 2023 · 4 comments
Labels
bug Something isn't working

Comments

@ASPNyan
Copy link

ASPNyan commented Oct 15, 2023

Describe the bug

Applying modifications in Iconify or having the Iconify Companion Magisk module installed cause bootloops with the error: Cannot load Android System (this is the same error, but a different device). This started since I updated to QPR 1's U1B2 update (latest as of Oct. 15), and seems to happen on both Pixel 6 and 7 boots.

Steps to reproduce

Steps to reproduce the behavior:

  1. Update to latest Android version (currently U1B2.230922.006); Pixel images can be found here.
  2. Install Magisk (duh), and install Iconify (duh, the sequel).
  3. If at this stage you also want to try the Companion module, install that now.
  4. Restart
  5. If you installed the companion module, expect a weird boot sequence followed by a failed boot, a restart, and a display then showing the aforementioned error. If you don't install the companion, try applying a setting. You should then have a System UI restart, followed by a System UI (or at least I assume to be) crash, causing a restart, and then following the same sequence as the Companion module.

Expected behavior

Not to bootloop? Just to apply the settings like normal.

Screenshots

Well no screenshots, but there is the previous photos of the error so here's the raw link: https://storage.googleapis.com/support-forums-api/attachment/thread-185178025-4009211010012833086.jpg

Device information

  • Device: Pixel 6
  • OS: Stock Pixel 6 (and 7) ROM(s), Android 14 U1B2
  • App version: 6.5.1

Additional context

From my limited analysis, since the device restarts pretty quickly after the first boot (before the failure to load boot error message), it seems that System UI is removed from the device. This could indicate some misbehavior with System UI and the module. Additionally, since the module fails instantly and the base app only on apply, there could be correlation? I only tried the base app once, and I did import my settings so if there's a correlation between what the companion does and my settings, here's the file for it (just in case). Unfortunately I don't know a thing about Java and Kotlin, and especially not for root, so I can't help by looking through code. But if you need more info, let me know.

@ASPNyan ASPNyan added the bug Something isn't working label Oct 15, 2023
@Mahmud0808
Copy link
Owner

Thank you for the detailed report. The bootloop issue on A14 QPR builds is already known. It happens when you enable any QS Tile Styles. Other customizations should work fine. Can't really fix without getting the source code which is still far away.

Didn't know about the companion module also causing issue, I'll investigate.

@5thofjuly
Copy link

5thofjuly commented Oct 17, 2023

Thank you for the detailed report. The bootloop issue on A14 QPR builds is already known. It happens when you enable any QS Tile Styles. Other customizations should work fine. Can't really fix without getting the source code which is still far away.

Didn't know about the companion module also causing issue, I'll investigate.

May I ask if the Transparency and Blur mod also trigger the issie?

@Mahmud0808
Copy link
Owner

May I ask if the Transparency and Blur mod also trigger the issie?

No, these should work fine. Atleast in my testing, there wasn't any issue.

@Mahmud0808
Copy link
Owner

Duplicate of #278

@Mahmud0808 Mahmud0808 marked this as a duplicate of #278 Dec 7, 2023
@Mahmud0808 Mahmud0808 closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants