[5.2] Stuck at Boot

[gxgani]

Device: Sony Xperia Z1 Compact Android: Lollipop 5.0.2/(.270)

With 5.2 installed, device doesn't boot. Having look at dalvik-cache folder, I see the process being halt at maxlock's dex file. Clearing it doesn't help either.

[Maxr1998]

Did you clear it multiple times? I had this issue too, but on time wipe doesn't help for me. Also, only clear dalvik, not normal cache.. Though it wonders me that you have the issue on 5.0.X...

[gxgani]

I booted in by deleting maxlock apk. Reinstalled it, uninstalled(clearing data) and deleted the dalvik cache. Installed it again, strangely works but it keeps getting optimized at every boot.

Additionally, could I request you to add an option to lock apps upon screenlock? And also, may I know whats "pausing" as stated in 5.2 update.

[Maxr1998]

That optimizing should only happen once, then it'll go away. Screen off should already work.

Previously, apps got relocked when you cleared them from recents, now you always see lockscreen when you start them, even when they were open before.

[gxgani]

This is disturbing. I had 2 apps(Whatsapp, QuickPick(Gallery Renamed)) protected with knock-code. I had everything removed(Input keys, lines, touch effect), rebooted and phone stuck again at boot.

Also I noticed, if you change settings from Lockscreen UI(such as Show lines, Input), they do not come into immediate effect for the apps under protection but for MaxLock it does.

[Maxr1998]

Changing settings in ML shouldn't cause a bootloop. Did you update any other Xposed module?

That seems to be a bug of Android settings. I cannot tell you why this happens. Though I could force that update, that would significantly decrease performance..

Seriously though, how often do you change your settings? ;)

[gxgani]

I did update, it was the Serajr's Xperia Module. I am back to 5.1.1 which doesn't seem to produce that specific issue but has the slower performance when compared with 5.2(Opening WhatsApp)

[Maxr1998]

Yeah, as I said inb4, this is an Xposed bug which happens randomly on 5.X when updating any Xposed module, MaxLock 5.2 isn't the cause. Sometimes I get bootloopstuck every morning at boot, sometimes it directly boots fine although I did an update..

[gxgani]

Oh. The only bootloop issue I faced was when I had app packages more than 320(http://forum.xda-developers.com/crossdevice-dev/sony/workaround-bootloops-xposed-lollipop-t3089203). After that, I haven't come across any bootloops. And this specific issue, was a bootloop. But with ML 5.2, I am not facing boot loop instead boot process get stuck at creating dex for maxlock.

[Maxr1998]

Sorry, always when I say booloop I mean bootstuck. I only had bootstucks, which were all fixed by wiping dalvik.

boot process get stuck at creating dex for maxlock. That seems to be an coincidence. I also had that bootstuck at dexing another module..

[gxgani]

I got an exam to take tomorrow, will do a test with having only having installed maxlock and get back to this issue soon.

[Maxr1998]

Ok, thank you. I'm on vacation from tomorrow to next Saturday (not this weeks one), but I will respond then.

[gxgani]

Have a good one, you deserve it.

[gxgani]

One Quick update, the bootstuck has to do with Maxlock's settings, since I was able to boot in when I cleared maxlock's appdata. I would like to know if you could reproduce this issue by enabling the following

Lock Mode: Knock Code Lockscreen UI: Hide Input/Title Bar, Untick Show Dividers and Make touches visible Apps: Whatsapp

[gxgani]

Out of all the Lock modes, I can confirm that this issue is being caused by the new Knock Code design.

[Maxr1998]

Hm, thanks for you observations.. That seems just so strange, it has nothing to do with the Xposed classes. I pretty exactly know when the fault started, and it seems the new IMoD is the issue. Could you try again without IMoD and with IMoD to see if it boots? I cannot do any tests, as I need my phone on my vacation and have no Computer for adb..

[gxgani]

The previous observations had IMoD turned off, now I tried booting having IMoD turned on with default values and phone booted for the first time, second boot failed(cleared the dex), it booted the next time and the cycle repeated. Didn't boot thereafter.

[Maxr1998]

So it seems IMoD is definitely the issue? Then I finally know where to take a look at.. Thanks!

[Maxr1998]

Reopened, as no definite fix is available by now..

[Maxr1998]

My testing confirmed that it's definitely the two additional XSharedPreferences from IMod which cause this bug.

[Maxr1998]

Fixed with 5.3