[Lollipop] UNSUPPORTED build with latest changes [BOOTLOOP]

[Droidphilev]

No description provided.

[M66B]

Since I cannot test this release myself, please report if it works for you or not, stating your device/ROM type/version.

Version 3.6.7 UNSUPPORTED
https://crowd.xprivacy.eu/XPrivacy_3.6.7.apk

Please read also this:
http://forum.xda-developers.com/showpost.php?p=59352424&postcount=14092

[Droidphilev]

Unsupported version is reporting data usage on GT-9205 with Temasek CM12. (it worked before with 3.6.6-1). This kernel is permissive.

[Droidphilev]

GT-I9205 with CM12 Temasek build with untouched kernel (ENFORCED and NOT edited!) and alpha 2 of xposed framework WORKING!

[wbedard]

I installed your test build on my GNex testing device running a custom ROM that holds as close to possible to AOSP (5.0.2). When booting with SELinux in permissive, XPosed crashes during boot throwing the same error you posted on XDA and I posted on Github. Interesting that it seems to fail under AOSP LP but "work" under CM 12. I have a CM 12 build available for my device that I will try next. Stay tuned.

[Droidphilev]

GT-I9300 with CM12 Temasek (was not working with 3.6.6-1) is not working. Hangs at bootscreen (as before)

[wbedard]

Interesting! Xposed (w/ XPrivacy installed and active..) does "boot" under CM12 on my device, at least under SELinux permissive. I am able to launch the XPrivacy app with no errors being displayed. Marcel, if you can tell me what you would like in terms of diagnostics, I'd be more than happy to provide them to you. I'm assuming a full logcat with XPrivacy in debug mode, etc but please let me know so I don't miss something important or provide more than you need/want. I'm going to look around and see if I can boot it under enforcing to see if there are any issues there.

[M66B]

@wbedard I think the problem is clear and known. We just have to wait until Xposed is fixed.

[wbedard]

Oh...well then nevermind! We'll just wait on rovo then.

[alvareo]

XT1095 on stock 5.0 gets a black screen after "Android is upgrading" window which I must say is a first (I did get black screens but before that window)

[M66B]

Version 3.6.8 UNSUPPORTED
https://crowd.xprivacy.eu/XPrivacy_3.6.8.apk

This version will not solve any bootloops/black screens (please provide a logcat), but might fix the phone number restriction (#2141) and/or the device ID (IMEI) restriction (#2159), because XPrivacy will run in compatibility mode. I figured AOSP mode might not be needed anymore, since unhooking with Xposed for ART will probably be not possible anymore.

[M66B]

Changelog: https://github.com/M66B/XPrivacy/blob/master/CHANGELOG.md

[Droidphilev]

3.6.8 not booting anymore on GT-I9205 with CM12 Temasek. It hangs at welcome screen. I cannot make a logcat because i need a pc for this. Not allowed to put software on my pc :(

[M66B]

Interesting, it seems that compatibility mode, which means different restrictions, is triggering a bug in Xposed, likely this one: rovo89/Xposed#29

[Droidphilev]

I was just planning to try 3.6.8 on an empty rom. I guess that's not needed then.

[amakuramio]

CM12
Xposedα2 + Xposed-arm 20150308
Xprivacy 3.6.8

result: booting won't complete

ARMv7-A CPU

[M66B]

@amakuramio please provide a logcat

[amakuramio]

http://pastebin.com/FP6XPuwC

[M66B]

@amakuramio this is caused by the same bug in Xposed as referenced earlier and the same reason I cannot run/test XPrivacy myself.

[amakuramio]

A bug on Xposed side I guess... There is nothing more we can do, right?
Good job!

I could play with the jit_offset values till it functions, do you want me to try...?

[M66B]

As said on XDA I am not very satisfied with the situation at all.

[lecterno]

version 3.6.7 unsupported working on Nexus 5, SlimLP, Xposed 3.0 alpha 2 (SELinux Enforced, boot.img NOT edited)

[amakuramio]

@lecterno are all the restrictions working? and if they seem to work, does restricting really restrict?

[lecterno]

@amakuramio all the restrictions seem to work. Does restriction really restrict? good question and I don't have an answer because I upgraded ot 3.6.8 and is in a boot loop. Will go back to 3.6.7 and report back later.

[KlausSC]

Xperia Z3 (D6603) with CM12 now works with the v.3.6.7 without modifying the boot.img; SELinux mode is "strict" and it is working as well. Thanks, Marcel!

[amakuramio]

http://bit.ly/1CV5AXG 5.1 bootloop
only sigsegv is missing but error looks the same~

[M66B]

@amakuramio it is the same crash as all other ones, only the crash part is missing. Recognized by:

E/art     ( 2428): Tried to mark 0xffffffff not contained by any spaces
E/art     ( 2428): Attempting see if it's a bad root

There is an additional thing which needs to be fixed on Android 5.1: the activity manager service has been changed.

[ghost]

Which version is recommended for testing on 5.1? I know xposed iisn't supported yet, but it's pretty stable on my device. There's just 3.6.5-3.6.8 or something, that's like 4 versions, half of which are unsupported and all of them have very little said about them.

[M66B]

No version of XPrivacy is supported on Android Lollipop, until Xposed is more stable. Most or all versions of XPrivacy will cause Xposed to crash and to bootloop your device. Read the comments in this issue for more details.

[ghost]

Anything fixed with the new xposed alpha?

[M66B]

For XPrivacy nothing has been changed.

[M66B]

You can find the Xposed changes here:
https://github.com/rovo89/Xposed/commits/master
https://github.com/rovo89/android_art/commits/xposed-lollipop

[M66B]

Here is a new (unsupported) version to try, but be prepared for bootloops:
https://crowd.xprivacy.eu/XPrivacy_3.6.9-2.apk

[M66B]

This version will likely resolve the bootloop problems on Lollipop:
https://crowd.xprivacy.eu/XPrivacy_3.6.9-3.apk

Thanks @dk-zero-cool for the workaround #2193 !

[burkele57]

Brillant guys it works!!!
N5 + stock 5.1 + xposed-sdk22-5.1.0-arm-20150514.
Had to remove previous version Xprivacy (1.1.15 or something like taht).
Seems I have to redo all my restrictions...
Many thx to all :)

On Thu, May 21, 2015 at 8:49 AM, Marcel Bokhorst notifications@github.com
wrote:

This version will likely resolve the bootloop problems on Lollipop:
https://crowd.xprivacy.eu/XPrivacy_3.6.9-3.apk

Thanks @dk-zero-cool https://github.com/dk-zero-cool for the workaround
#2193 #2193 !

—
Reply to this email directly or view it on GitHub
#2162 (comment).

Eric Burkel
Mob. + 33(0)6 20 34 66 54

[danube]

Oneplus One, CM 12.0, Android 5.0.2: No bootloop anymore, fantastic. Restriction selection in App seems not to apply until reboot, but then it's fine. Internet access seems not to be detected nor restricted (though selected to be). Restrictions seem to work: IPC, Location, Identification.

[ghost]

+1, sorry I didn't get back sooner. LG G2 with 5.1.1 AICP built by me working PERFRCTLY. Not only that, stock (thoigh still quite AOSP) NVIDIA Shield Tablet on 5.0.1...about to take the 5.1 OTA, thanks man, you guys nailed it. Hope you don't mind I share this on reddit.

[M66B]

I am closing this issue, since version 3.6.10 should solve the most important problems :-)
https://github.com/M66B/XPrivacy/releases/tag/3.6.10

[twenty-thr23]

Still bootloops on m7 santod 5.0.1 built. Only way to get back to your system is restoring from nandroid backup, or having deleted all xprivacy related content (using twrp rec file manager) in your system folder and cache/dalvikcache.

Cheers

[M66B]

@twentythree- Logcat?

[twenty-thr23]

I can't seem to provide one, sorry.

[antgiant]

Works great on my M7 5.0.2 (Stock Sense install).

Also, escaping bootloops can be done without such extreme measures
(although it took me wiping to realize it). You can turn off Xposed by
renaming /system/bin/app_process32 to anything else and renaming
/system/bin/app_process32_original to /system/bin/app_process32 (I do it in
recovery.) then your phone will boot. Start Xposed, disable Xprivacy,
reverse the file renaming, reboot and you now have a normally booting phone
with a functional Xposed.
On Sun, May 24, 2015 at 7:42 AM twentythree- notifications@github.com
wrote:

I can't seem to provide one, sorry.

—
Reply to this email directly or view it on GitHub
#2162 (comment).

[wbedard]

There is an easier way to recover from bootloops caused by either Xposed or one if it's modules. During boot, hold down one of the volume buttons until your phone vibrates. At that time, press that same button 4 more times quickly (you only have a few seconds window...). After the last button press, you will feel a longer vibration, which indicates that XPosed has been disabled. While I am not a fan of this from a security standpoint, it is much easier than renaming the XPosed files, which I have also done in the past.

[twenty-thr23]

@wbedard Thx, since less hassle, I might give it a go once more.

[Furchendackel]

3.6.10 works fine - unlike on 3.6.9-3, location can now be controlled on more (all?) apps.

However, XPrivacy claims it has not been activated in the Xposed installer, but it is and it works fine.

Sony Xperia Z3, LP 5.0.2 stock, XPosed alpha 4.

[M66B]

@Furchendackel Why not use 3.6.12 ?

[Furchendackel]

Shame on me, didn't notice the new version. 3.6.16 works fine!

[burkele57]

Hi gang.
Anybody else been experiencing a drop in battery-life with the new Xprivacy
LP 5.1 betas ??
Cheers.

On Tue, May 26, 2015 at 9:41 AM, Furchendackel notifications@github.com
wrote:

Shame on me, didn't notice the new version. 3.6.16 works fine!

—
Reply to this email directly or view it on GitHub
#2162 (comment).

Eric Burkel
Mob. + 33(0)6 20 34 66 54

[M66B]

@burkele57 if there is any difference in battery use between KitKat/Lollipop with XPrivacy it is probably due to Xposed.