You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I keep having to download iconify over and over, it goes through it's setup process and then asks me to reboot, then I reboot click iconify and makes me restart set up. How to fix??
I was actually asking you how I fix it, and where is it outputting a log? It’s not like it’s shooting an error, it’s just doesn’t install, so I would love to know where I find the log output so I can magically fix it, I was just assuming it didn’t play well with kernelSU or APatch, or any other rooted method other then magisk, I don’t have any issues with magisk. But please let me know about this log, it would help me greatly to know your module is logging information somewhere in my file system. I definitely wouldn’t be responding back. But clearly this is a bug, the root method should not matter considering it’s gaining the same privileges, in fact it get more privileges with kernelSU. So it’s something in your code idk that’s why I’m asking. Tell me where you’re logging the info. Because I actually think your module is probably top 5 and I don’t want it on my device I need it. lol you did a good job.
Steps to reproduce
Steps to reproduce the behavior:
Go to '...'
Click on '....'
Scroll down to '....'
See error
Expected behavior
Install process works fine, the I reboot and go back to iconify app and it has me restart the process. No root error messages, nothing it’s installs, even shows in my file system. But for some reason after the reboot it acts like it was never installed then overwrites previous install.
What Is expected to happen after dependency’s are met and they are is I install it, it goes through its cycle of writing to my files system, then it tell me to re boot, I push reboot, my phone then reboots, I first see the google logo, maybe followed by whatever OS I’m testing, then I see my Lock Screen, I enter my password, go to iconify app, click iconify app, iconify app opens, I am then greeted by all your beautiful customization options, but instead I open your app and I’m greeted with
Got Bored of stock UI
Lets customize everything to our liking
AGAIN!
No log, your docs don’t mention a log and this module is bad ass and the only one I actually use. If you wanna close this bug report because it’s not concise then fine. At least tell me where to find the log. If I have to go back to magisk, so be it, I’ll do that just for your module. But don’t close this because I didn’t provide a log when your documents don’t mention any log output and it’s just your module not playing well with other rooting method.
I don’t even ask people for help ever, but I like your module. So give me something! Or if there is another way to reach out other then a big report, let me know.
Screenshots
No response
Device information
Device: [e.g. Google Pixel 6]
OS: [e.g. stock ROM Android version 13.0 QPR3]
App version: [e.g. v6.5.1]
Magisk/KernelSU: [e.g. Magisk Delta 25.2]
Additional context
No response
The text was updated successfully, but these errors were encountered:
Do you think that's a valid title for a bug report?
The logs are not saved anywhere. You can use an app like LogFox to see the ongoing logs of iconify. And disable all other modules before installing iconify, also make sure you disabled unmount modules in ksu, and enabled overlayfs if you are using ksu next. Sometimes other modules conflict with the installation process.
Mahmud0808
changed the title
?
Iconify keeps asking for module installation
Feb 23, 2025
Describe the bug
I keep having to download iconify over and over, it goes through it's setup process and then asks me to reboot, then I reboot click iconify and makes me restart set up. How to fix??
I was actually asking you how I fix it, and where is it outputting a log? It’s not like it’s shooting an error, it’s just doesn’t install, so I would love to know where I find the log output so I can magically fix it, I was just assuming it didn’t play well with kernelSU or APatch, or any other rooted method other then magisk, I don’t have any issues with magisk. But please let me know about this log, it would help me greatly to know your module is logging information somewhere in my file system. I definitely wouldn’t be responding back. But clearly this is a bug, the root method should not matter considering it’s gaining the same privileges, in fact it get more privileges with kernelSU. So it’s something in your code idk that’s why I’m asking. Tell me where you’re logging the info. Because I actually think your module is probably top 5 and I don’t want it on my device I need it. lol you did a good job.
Steps to reproduce
Steps to reproduce the behavior:
Expected behavior
Install process works fine, the I reboot and go back to iconify app and it has me restart the process. No root error messages, nothing it’s installs, even shows in my file system. But for some reason after the reboot it acts like it was never installed then overwrites previous install.
What Is expected to happen after dependency’s are met and they are is I install it, it goes through its cycle of writing to my files system, then it tell me to re boot, I push reboot, my phone then reboots, I first see the google logo, maybe followed by whatever OS I’m testing, then I see my Lock Screen, I enter my password, go to iconify app, click iconify app, iconify app opens, I am then greeted by all your beautiful customization options, but instead I open your app and I’m greeted with
Got Bored of stock UI
Lets customize everything to our liking
AGAIN!
No log, your docs don’t mention a log and this module is bad ass and the only one I actually use. If you wanna close this bug report because it’s not concise then fine. At least tell me where to find the log. If I have to go back to magisk, so be it, I’ll do that just for your module. But don’t close this because I didn’t provide a log when your documents don’t mention any log output and it’s just your module not playing well with other rooting method.
I don’t even ask people for help ever, but I like your module. So give me something! Or if there is another way to reach out other then a big report, let me know.
Screenshots
No response
Device information
Additional context
No response
The text was updated successfully, but these errors were encountered: