When you say "respring" do you mean cycling reboot the lock screen? I installed from 7.17 to 7.21 and every firmware have this bag. The restart/shutdown menu works, but the launcher and lock screen does not work. Changing launcher doesn't help.
Yes this is exactly what I'm referring to. I think it might have something to do with the repartition sizes being to small but I'm unsure
Ummm and what are the settings you change?
I'm currently on 7.24 however this is happened with all versions. I've tried it on. I have a 16 GB. FLO device. It works well on every other custom rom. I'm except for this one and the only things I really change are the customizations Crdroid settings are messing up in some way. Which shouldn't happen considering it doesn't happen for you rather than sticking to the regular settings. I would like to figure it out if it's possible but that would require a lot of testing to find out which setting it's messing up on because I'm not doing anything I shouldn't be. I use the wrong with microgUmmm and what are the settings you change?
Maybe I can replicate the problem and see what is wrong, or maybe you can live with default settings as it runs ok that way
BTW: I have just uploaded 7.25 with December Android security patches.
This has also happened on the flo versions of Crd v7.2 that followMSI made back in the day. For some reason upon booting up after using crd settings and fully customizing the device. I will send a video shortly of what exactly it does. Most times it boots up but sometimes it comes. It fails utterly and I can't even use it
Sorry for the video length but it takes that long to boot up. As by what can be seen in the video the device does not start system ui correctly. Most times it takes a few tries and then the tablet works fine until I reboot it again in which it does the same thing . Occasionally the systemui will refuse to start at all after multiple restarts with no way to fix it other than to keep trying or let it calm down and attempt again hours later I don't have any idea for the cause. Hope this helps, I use most customizable option that Crdroid offers with microg but nothing that should be modifying the rom so I don't believe its an issue with my deviceUmmm and what are the settings you change?
Maybe I can replicate the problem and see what is wrong, or maybe you can live with default settings as it runs ok that way
BTW: I have just uploaded 7.25 with December Android security patches.
Well, I see what you mean, mine is much faster, first thing I see is that mine doesn't show the open lock on google's screen. Then I can tell you I'm running mindthegapp apps, not microg, don't know about the firmware versions from google or partitioning :-(
No its definitely not, I've tried multiple things. If signature spoofing was the issue I'd say otherwise but I have used this rom with Gapps in the past.
Would it be simpler to take a TWRP backup and let you restore it? I can sign out of my Google accounts. The device isn't encrypted so theoretically that is possible
No watch the video provided to understand more about that. But regarding deb devices this is for flo so I doubt that it would although you could try
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warnedActually it does, or at least it should. Chances are your using the Twrp Flox build provided by Ud4 which means there aren't any custom kernels for flox or at least not using this codename.
See this post if I wasn't clear enough here. Cheers!
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
you need to use the Exkernel to enable dt2w. Here's the latest one: Link.
