This repository has been archived by the owner on Sep 6, 2019. It is now read-only.
Error on start #2300
Comments
|
What is the bug? |
|
Doesn't seem to hook anything, no fake data provided to apps, no xprivacy popup and so. |
|
Please provide a logcat capture from your PC, with capturing started before powering on the device. |
|
Ok, let me some time to download Android SDK and so (slow connection here) :) edit : Should an "adb -d logcat>mylogfile.txt" enough with phone booting with USB debugging previously activated? |
|
Please find enclosed the result of a "adb -d logcat > log.txt" with phone cold booting. I notice something strange here: lot of "Success to oxygen resources /system/framework/oxygen-framework-res.apk" Could it be that this ROM is "handmade" to the point that the name of the Android framework got changed, thus preventing a normal function of xprivacy? |
|
Is this logcat file giving you an idea about the bug encountered? |
|
Like in the previous logcat, I don't see Xposed initializing XPrivacy, so this is most likely an Xposed problem. To be exact, thus method is not being called, which sets up most hooks: |
|
I did update to the latest xposed (rev 78) today. Still same problem. Every Here is the log from xposed: 11-17 14:17:15.277 I/Xposed ( 2060): ----------------- I don't see any errors there? P.S.: I deleted other modules lines, but no error were there, and they're |
|
I need to see the logging from 'Init path=...' Do you have LBE installed? If so, that is the reason: |
|
No, LBE not installed, FOSS FTW ! ;) How/where could I find this "Init path" ? |
|
Somewhere in the logcat. |
|
It's there. |
|
Nothing wrong here. I am wondering which problem you have with XPrivacy. |
|
I got a popup from XPrivacy while openind it : "Encountered an internal And I just don't get any XPrivacy popup for the on-demand feature. I know But now, just nothing. And each time I fresh start the XPrivacy app, I got
|
|
You can ignore the popup. For the on demand popups not appearing: make sure this is enabled globally and for the application. |
|
So I did clean out every data from XPrivacy using the app option and start from clean base. Still no on-demand popups so far :o I did generate several logcat files with the following commands:
I was starting dozens of apps during 1 minutes each time. Didn't find any occurences of the "demand" word in any of these files (and still no on-demand popups so far...). It's like the "on demand" is never attempted? |
|
On demand restricting is handled here: If there is no on demand restricting logging, then on demand restricting is most likely disabled, either globally (main settings) or in the application specific settings (per restriction). Note that on demand restricting for system application can only be enabled by using a quirk. Another note: the upgrade process need to have been executed, so you might need to reboot once after installing XPrivacy. As a last possibility, but I have never received a report about this, your ROM is incompatible with on demand restricting. |
|
I for sure did check that the on demand setting is set globally and within the app also. Still not getting any popups anyway. But here the problem isn't directly linked to the on demand feature. It's just that XPrivacy isn't basically working at all. Like I fake the location for globally and every apps are still able my real location (even with WiFi location disabled and "WiFi search on idle" disabled). For this test, I did the test without using the on demand feature, but just filtering apps on location permissions, select all app, and restrict selection. Now I get a solid cross on the applications (for this permission) and not the question mark. I did fake the location within the "global" settings, and did reboot my phone. Still, every apps is able to get my real location (using only GPS/cellular network since WiFi is off). Any idea ? I think we're hitting something not so obvious here :p |
|
Restricting locations is not something simple with Google Play services around. |
|
I juste did download an app called "Device ID" (com.thanh.informationdevice) from the Play Store. Before even starting it, I did restrict every functions of the Device ID category of permissions, and set the settings for this app to the default one (DEFACE, etc.). I started the app, and it still got my real IDs displayed, not "DEFACE" on sight. |
|
This is just a warning. |
|
Yep, but from the 3 last line of his logcat, we can see: So it seems the ZygoteInit (and not InitZygote?) is called no? So the problem should be elsewhere? |
|
ZygoteInit is where Android is being initialized. All call stacks in Android are part of ZygotInit. |
|
Ah ok, my bad. That was misleading ;) |
|
I have the same problem. I'll capture a log later, today. Let me start with the error popup message XPrivacy wants to send: Privacy: 3.6.19 Brand: OnePlus Method not found hook=null/inputDispatchingTimedOut (com.android.server.am.ActivityManagerService) |
|
First, many thanks for XPrivacy. It's for sure the most important App for me. I would be really happy if we could find a solution to make it work. Otherwise this would be a reason to sell this phone. I can't provide a boot log. adb didn't detect my device. After start "adb -d logcat>my.log" it says "waiting for device" but never finds one. If I exit adb and call "adb devices" it finds one. I'm sure is this crappy Windows. I must manualy install the driver and it might be the wrong one. I choosed "Oneplus ADB Interface" Anyway. There is a log under xposed framework app. I checked this one and I found four lines regarding XPrivacy: 11-22 08:01:16.898 I/Xposed ( 296): Loading modules from /data/app/de.live.gdev.xprivacyappinfo-2/base.apk I used a simple App "DeviceID" to try restrictions and checked the log found in XPrivacy. Means I opend the App settings in XPrivacy and pressed "Activity Log" in Menu. Hope this helps. Let me know if I an do something else. |
|
Your logcat will be more than usefull to @M66B Issue "adb -d logcat > logcat.txt" in your command prompt, then reboot the phone. |
|
Tried it without success. |
|
Looking again I seem to have missed the cause of this problem: This will result in XPrivacy not being initialized properly. This ROM has a non standard activity manager service, which I haven't seen before. |
|
No, OxygenOS is not opensource unfortunately. If you need anything specific, I'll try to get it. |
|
I need the layout (fields and methods) of com.android.server.am.ActivityManagerService. |
|
Aaahh nice, an hint! I was thinking that was the AppOps part that was interfering. But something as crucial as the Activity Manager is not standard ?
|
|
Here is the smali file for ActivityManagerService extracted from oxygenos. I do see systemReady method in it. |
|
@ukanth still there is this message Which means the class is found, but the method is not. I cannot really debug this issue, since I don't have a device running OxygenOS. |
|
OnePlus has open sales {no invite needed} until 30 Nov. Later you can send the phone to me via snail-mail. |
|
@Phoost thanks for the offer, but it is too complicated. |
|
I installed H2OS on my OPX. Same result. Error on startup and resrictions not working. Don't know if this helps but want to let you know. |
|
@M66B , I've setup XPrivacy locally and able to debug it. I've not worked with xposed at all, so with little help from your end , I could help fixing it. Please let me know if that works ? Update: No error on start when I bring it up. Also I can see it's working properly except ondemand feature |
|
Debugging Xposed modules is not easy. First check: is this being executed: Second check: is this being executed: |
|
@M66B, You are right. it's not executing those lines and exception is been thrown from that line. |
|
This is not a real exception, but a warning. The privacy service is in in any case registered and system hooked. Next step: concentrate on one of the hooks for which a restriction is not working. Check it out if it is being hooked and being executed. Since the privacy service is running, you should be able to turn on XPrivacy debug logging using the main settings, so you can see a lot more on the next reboot. |
|
You are awesome guys. |
|
Hi, I'm encountering exactly the same issue on my Oneplus X on OxygenOS 2.2.0: @Phoost , have you found a workaround to this problem? |
|
Yes, install cm12. Works good. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi there,
I'm encountering bug on XPrivacy startup.
I'm using a OnePlus X running OxygenOS 2.1.2 (Android 5.1.1), which is its official ROM it get shipped with.
Doesn't seem to be an xposed bug since other modules are working as intended.
Maybe could be related to the integrated applications permissions featured in OxygenOS (feature which seems to be a little bugged)?
Since this device got released few days ago (no sources released yet, no official TWRP, etc.), I think I won't find similar report anywhere else, so I'm posting here.
Please feel free to ask anything else useful for you to debug. I'm available to test things and so. Thanks again !
P.S. : Keep up the good work, already using pro version, but looking forward to help more :)
XPrivacy: 3.6.19
Android: 5.1.1 (SDK 22)
Brand: OnePlus
Manufacturer: OnePlus
Model: ONE E1003
Product: OnePlus
Device: OnePlus
Host: ubuntu-148
Display: ONE E1003_14_151103
Id: LMY47V
The text was updated successfully, but these errors were encountered: