[Lollipop] UNSUPPORTED build with latest changes [BOOTLOOP]

[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: https://github.com/rovo89/Xposed/issues/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!

[M66B]

To all: I would like to see feedback on 3.6.8 too, since it is an attempt to fix the not working restrictions.

[walrus543]

I know you need logs but I don't have my PC atm. It works fine with 3.6.6. but boot loop with 3.6.8 (same setup: CM12 nightly 5.0.2 non CAF + permissive kernel at boot). Xposed alpha 2. Thanks for your support.

[alvareo]

Since it doesn't fix bootloops, if the phone doesn't boot, as I said, do you still need logs or is it confirmed that it's the same Xposed issue?

[M66B]

@alvareo https://github.com/M66B/XPrivacy/issues/2162#issuecomment-78920368

[alvareo]

That's what I thought. Thanks.

[M66B]

To be clear just another time: all boot problems I have investigated are caused by the same Xposed bug, which will not be fixed anytime soon and is the same reason why I cannot work on XPrivacy for Lollipop.

[M66B]

Another thing: I am running stock Lollipop 5.1 on my device (a Nexus 5), which works quite good, in contrary to Lollipop 5.0.x (I have disabled most Google services). Unfortunately there will be no Xposed for Android 5.1 anytime soon too, which is another reason I have suspended XPrivacy development for now.

[amakuramio]

I'm going to flash Android Lollipop again and test 3.6.7, and play with 3.6.8 Xposed jit, will report results in one hour.

[amakuramio]

I tried Elixir and it is properly reading the data sent by Xprivacy. I can confirm, 3.6.7 is working without modifying boot kernel and applies permissions properly. However, the ROM I use, the baseband version is unknown thus I cannot see whether the phone restrictions are working...

Next step: allow root through developer options and play with 3.6.8 after I can get the baseband working.

[M66B]

@amakuramio did you check the IMEI? (one of the restrictions complained about #2159)

[amakuramio]

If I can get the baseband working, I can see whether the IMEI restrictions are applied. This will take time. (I need to use an older Lollipop rom)

update: baseband working.

[aOryx]

Making a nandroid backup, I will test 3.6.8 on my htc one 5.0.2 Thanks for ur effort, its really appreciated!

[amakuramio]

XPrivacy 3.6.7 is not working on phone restrictions... Therefore imei data cannot be hidden.

[M66B]

It is no surprise 3.6.7 restrictions are not all working. I am more curious about the same for 3.6.8.

[amakuramio]

I correctly created the XPosed jit cache value, but would it work without reflashing the Xposed module through the jar file? I'm confused

[M66B]

I don't know.

[amakuramio]

After creating jit_reset_offset file, Xposed shows me that Xposed is not correctly installed. Yes, this is clearly a bug on Xposed' side. I will report this. Xprivacy 3.6.8 will not function because Xposed is not found, but the device boots normally. A zygote init failure is the cause.

[aOryx]

still having bootloop with 3.6.8 HTC one ADHD 91.1 5.02 Kernel Elemetal X 19.5 will provide logcat in 4 hours

[aOryx]

log cat for 3.6.8. bootloop http://pastebin.com/Uga7iWEc

[M66B]

@aOryx same as all other bootloops, caused by a bug in Xposed.

[amakuramio]

There won't be anyone be able to get 3.6.8 working, because the Xposed segmentation fault occurs when accessing memory incorrectly, from what I see.

[M66B]

@amakuramio I am not sure if this problem occurs on all ROMs and people tend to report problems only.

[amakuramio]

http://stackoverflow.com/questions/18158694/android-fatal-signal-error-11-sigsegv-on-different-versions-of-jellybean

[M66B]

@amakuramio The question on stack overflow you are referencing is, besides being very old (at least in the ICT world; in this case two major Android releases ago), not about the same issue.

SIGSEGV is a general crash in native code and you need to inspect the details of this type of crash to know what it is about (which can be very hard to do).

[amakuramio]

Can you tell me what I should do to find the source of the error? NDK... or something is needed if I remember correctly

[M66B]

Understand Xposed, but with all respect, I guess this is far beyond your skill set.

Also, I don't see the point in putting energy into this, since rovo89 knows exactly what the cause of the issue is.