Issue with the checkbox

[Cyclu]

Tick or unpick the checkbox in the app lists make that it moves to left
Go into detailed app view then return to the app lists it returns to its initial place.
It happens in the all category here Calendar even "All"

[M66B]

I cannot reproduce this.

[M66B]

I can reproduce this, with global on demand disabled. Looking into it ...

[Cyclu]

Thanks! Exactly I have global on demand settings disabled I prefer "old school" method ;)

[an0n981]

Sometimes we should embrace the future, especially given the added security features of onDemand

[M66B]

Please test this version thoroughly: http://d-h.st/uaj

[Cyclu]

@an0n981 I think embrace the future soon It rejuvenates me! What interests me the largest number
it's white-lists future.
@M66B Unfortunately bootloop with this version quietly :) I restore my Nandroid backup.

[M66B]

This version is not very different from the last release and will certainly not cause new boot problems, so please try again and provide a logcat if it fails another time.

[Cyclu]

Tried again bootloop I will send a logcat at your contact (privacy stuff)

[M66B]

Can you please try to boot without restrictions?
Which XPrivacy version are you currently using?

[M66B]

Looking deeper into the logcat I found this:

android.database.sqlite.SQLiteDiskIOException: disk I/O error (code 3850)

This means there is something wrong with device /data/system is mounted on.
Maybe the data partition is full or corrupted.

[Cyclu]

Really bad luck now when stable version coming I have this problem never had bootloop since version 0.34, have latest version .72 when open issues.

-Clear restrictions update from ver.72 to 72-5 or 2.0 bootloop
-Return to version .71 update to .72 no bootloop

Data partition has 68% free space I checked dmesg not error here because I had long time ago bad block in data partition which going after nandroid restore.
This is the error I've had in data partition:
EXT4-fs error (device mmcblk0p35): ext4_ext_check_inode:350: inode #876: comm installd: bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)

I rechecked again dmesg not trace of this error or something other.
What I do to found what the problem?

[Cyclu]

Wait I'm wrong? like I said never had the bootloop I think when we stuck on boot screen logo (like in this issue #1543) is a bootloop. Sorry for the confusion I go to install version 2.0.1 which surely fix the issue.

[M66B]

Be aware that your problem might have been different.

[Cyclu]

Ouf! the ver. 2.0.1 works! Happy end and happy user :) I would like to know regardless what happened?
Know you a good method to check the partition like checkdisk on PC?

[M66B]

Apparently the newly added time zone restriction was doing more bad than good.

[Cyclu]

Ah ok I assure you that traverse my mind! so next step I will test the on demand whitelists.
what I like almost with usage data with parameters it makes us understand many things
and how Android works. Good continuation!

[an0n981]

I believe the commit referenced here has the (unwanted?) side effect of removing the onDemand question mark in the app overview. I noticed it yesterday while testing the provided test version, at the time it didn't really dawn on me, but with v 2.0.1 I have now noticed it again.

[an0n981]

confirmed fixed in 2.0.3