M66B / XPrivacy

XPrivacy - The ultimate, yet easy to use, privacy manager
http://forum.xda-developers.com/xposed/modules/xprivacy-ultimate-android-privacy-app-t2320783
GNU General Public License v3.0
2.08k stars 527 forks source link

NFC default action seems not to work #2073

Closed redsquare50 closed 9 years ago

redsquare50 commented 9 years ago

Using Samsung S5 Mini with XPrivacy Pro. When scanning an NFC tag which contains a URL NDEF it should immediately open that URL in the browser but it does not. If I disable XPrivacy it works.

I have a hunch this is the same issue as issue: 1759

If you need log cat entries, please let me know the command line to use as I am not that familiar with log cat. I have got this so far when scanning the tag:

W/SecureStorage( 1981): [WARN]: SPID(0x00000222)internal error
W/SecureStorage( 1981): [WARN]: SPID(0x00000223)Processing of client command finished with error
W/SecureStorage( 4244): [WARN]: SPID(0x00000000)dynamic libraries buffer length error
W/SecureStorage( 4244): [WARN]: SPID(0x00000000)Could not connect to Secure Storage Daemon
W/System.err( 4244): com.sec.android.securestorage.SecureStorage$SecureStorageException: Error: internal error
W/System.err( 4244):    at com.sec.android.securestorage.SecureStorage.throwJNIException(SecureStorage.java:46)
W/System.err( 4244):    at
com.sec.android.securestorage.SecureStorage.put(SecureStorage.java:309)
W/System.err( 4244):    at
com.samsung.android.providers.context.security.SecureDbManager.initSecureStorage(SecureDbManager.java:140)
W/System.err( 4244):    at
com.samsung.android.providers.context.security.SecureDbManager.initialize(SecureDbManager.java:77)
W/System.err( 4244):    at
com.samsung.android.providers.context.security.SecureDbManager.getPassword(SecureDbManager.java:55)
W/System.err( 4244):    at
com.samsung.android.providers.context.log.db.SecureDbHelper.(SecureDbHelper.java:141)
W/System.err( 4244):    at
com.samsung.android.providers.context.log.db.LogDbHelper.(LogDbHelper.java:39)
W/System.err( 4244):    at
com.samsung.android.providers.context.ContextApplication.getLogDatabase(ContextApplication.java:131)
W/System.err( 4244):    at
com.samsung.android.providers.context.log.BaseLogProvider.getDbHelper(BaseLogProvider.java:388)
W/System.err( 4244):    at
com.samsung.android.providers.context.log.BaseLogProvider.insertLog(BaseLogProvider.java:458)
W/System.err( 4244):    at
com.samsung.android.providers.context.log.BaseLogProvider.insert(BaseLogProvider.java:152)
W/System.err( 4244):    at
com.samsung.android.providers.context.util.ContextLogger.logLocalProvider(ContextLogger.java:45)
W/System.err( 4244):    at
com.samsung.android.providers.context.status.AppUsageMonitor.insertItem(AppUsageMonitor.java:206)
W/System.err( 4244):    at
com.samsung.android.providers.context.status.AppUsageMonitor.handleMessage(AppUsageMonitor.java:238)
W/System.err( 4244):    at
com.samsung.android.providers.context.ContextService$ServiceHandler.handleMessage(ContextService.java:248)
W/System.err( 4244):    at
android.os.Handler.dispatchMessage(Handler.java:102)
W/System.err( 4244):    at android.os.Looper.loop(Looper.java:146)
W/System.err( 4244):    at
android.app.ActivityThread.main(ActivityThread.java:5694)
W/System.err( 4244):    at java.lang.reflect.Method.invokeNative(Native
Method)
W/System.err( 4244):    at
java.lang.reflect.Method.invoke(Method.java:515)
W/System.err( 4244):    at
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1291)
W/System.err( 4244):    at
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1107)
W/System.err( 4244):    at
de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
W/System.err( 4244):    at dalvik.system.NativeStart.main(Native
Method)
M66B commented 9 years ago

XPrivacy does nothing if there are no restrictions are being applied, so I am quite sure this is caused by a restriction. There is a FAQ about finding "bad" restrictions, which might be helpful.

redsquare50 commented 9 years ago

You are absolutely right it was a bad restriction I had made (now found and fixed). For anyone else facing a similar issue - the problem was that I had restricted NFC from the default browser (firefox in this case) - Thank you so much for your help and a great tool.