-
Notifications
You must be signed in to change notification settings - Fork 527
Xprivacy is incompatible with LBE Security Master #1231
Comments
I have tested with 1.99.24 and it works for me. |
I see 1.99.24 imprint is compatible, but I have installed 1.99.24 1.99.25, performance status still # 1167 is described. |
I have just tested with 1.99.25 too and it works for me. |
Are you sure LBE is causing the problem? |
I just tried again to close the LBE root privileges, 1.11.6 1.99.24 upgrade, restart the phone, waiting for database import, restart the phone again and give LBE root privileges, the phone system built-in program to stop. All cases consistent with the description of # 1167. |
I am very very very confident that the problem occurs when LBE root authority when given. I once again try to upgrade from 1.11.6 1.99.25, restart the phone, giving LBE root authority, the question arises again. My phone note3 N9009 |
I'm just a user is not technical staff. I am very happy to help you find the problem, but I do not understand technology. I was in Beijing 4:12 |
You can help me with a logcat captured from your PC. You need to start capturing before turning your phone on. What does that mean "Beijing 4:12" ? |
“Beijing 4:12”means nanhir lives in beijing and the time he commented is 4:12 a.m. |
Can you please try again with this version: http://forum.xda-developers.com/showpost.php?p=49979466&postcount=6550 |
Xprivacy 1.99.26 is still incompatible with LBE Security Master. i get logcat and upload it to googledrive(https://drive.google.com/file/d/0B6oAA05W5KfDelN3QTA5WjBVUHM/edit?usp=sharing). |
I have requested access to the document ... |
sry i didn't change the access.now you can download it. |
LBE is crashing, maybe you can ask for support to the LBE authors. |
Can you try if it is better with version 1.99.28? |
it's better now.it seems that LBE cant get root access when booted,but when i give root access to LBE manually, the OS still crash.... |
1.99.25 is normal, but 1.99.28 can't fake data |
@xzhlksh 如果你的note3刷的不是miui,为什么你要同时安装LBE和xprivacy?不能理解。LBE在miui里是系统应用,而在note3里面是可以卸载的。 |
@xzhlksh English please. |
1 Safety meaning. |
@nanhir English please |
I have repeatedly contact LBE developers, because now is the Chinese holidays, LBE developer has not given feedback how to deal with compatibility issues xprivacy LBE |
My point compatibility problem lies in the xprivacy. 1.11.6 xprivacy compatible LBE. LBE version does not change when, after xprivacy upgrade compatibility issues. These are only a user perspective. |
1.99.25 is normal too |
in miui 1.99.25 is normal too。 |
1.i'm always speaking english to M66B |
Any news from the LBE developers? |
it works,1.99.32.but: Android version: 4.1.1 (SDK 16) Model: MI 2S (aries) com.android.browser: class not found: com.android.browser.provider.BrowserProvider for browser/BrowserProvider uid=10005 com.android.browser: class not found: com.android.browser.provider.BrowserProvider2 for browser/BrowserProvider2 uid=10005 |
No idea why it works now, but if it works it works. |
1.99.32 is still incompatible with LBE. The second problem is not resolved, but close. |
note3 n9009 android 4.2.2 |
@nanhir do you mean you still have a boot problem, or that you have the support info popup? |
yes, I just tried again to close the LBE root privileges, 1.11.6 to 1.99.32upgrade, restart the phone, waiting for database import, restart the phone again and give LBE root privileges, the phone system built-in program to stop. |
I have been communicating with LBE Software CEO, LBE feedback follows: xprivacy has not supported art, before lbe same. Later lbe done a lot to support the art work (previously overturned a lot of code). |
LBE Software CEO admitted that indeed two software compatibility problems. If you want to communicate with LBE software developer, I can help to communicate. |
|
Please give me a your email, I will give to LBE's CEO, led them to communicate with you. |
OK,I will contact them |
I have never heard anything back about this. |
Xprivacy is incompatible with LBE Security Master 1.99.24 !
The text was updated successfully, but these errors were encountered: