M66B / XPrivacy

XPrivacy - The ultimate, yet easy to use, privacy manager

Home Page:http://forum.xda-developers.com/xposed/modules/xprivacy-ultimate-android-privacy-app-t2320783

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Olympus Image Share can not connect to camera with XPrivacy active.

iansmith6 opened this issue · comments

When the XPrivacy module is active the Olympus Share app can not connect to the camera. Clearing ALL restrictions and data in XPrivacy does not help, only disabling the module and rebooting.

Another user has verified that they have the same problem. This problem began with an update a few weeks ago. I can't install older versions to track down which one but I think it was the big upgrade. The GoPro app does not worth either anymore, both apps are for communicating with non-router devices which seems unlikely to be a coincidence.

Included are two logcats, one with XPrivacy enabled and one disabled, both accessing the Olympus Share app. I put the UID of the app at the top of both. Both logcats were started from a fresh boot.

XPrivacy enabled... http://pastebin.com/s1dyNVCu

XPrivacy disabled... http://pastebin.com/txKuW41n

Thanks.

Please capture a new logcat with XPrivacy enabled and XPrivacy debug logging enabled (main settings).

Sorry, I noticed that right after I submitted. New logcat is up with XPrivacy debugging on.

Unfortunately the logcat is very difficult to read, given that all line breaks are missing.

Hmm, must be some UNIX<->DOS conversion issue, I see line breaks when I go to the links on my Win 7 machine. I captured them in a DOS window.

I did a Unix EOL conversion and edited the two links, any better?

Looks like the line feeds were getting messed up all right. I uploaded two new ones, this should be better. Sorry about that.

Disabled... http://pastebin.com/sLxRscby

Enabled... http://pastebin.com/uf6GUG89

I cannot find anything in the logcat that could explain the problem. Maybe it is a timing problem that XPrivacy introduces. My suggestion is to ask support from the author of the application.

Ok, thanks for looking into it. It seems odd that both the Olympus and GoPro apps have the same problem. They are both similar apps, I wonder if they used the same library or code somewhere.

Not sure how GoPro works, but Olympus communicates via HTTP and I can open a browser and type in the exact same URLs that die in the app and they work fine. I can't see why it fails on the HTTP requests but the browser doesn't.

I meet the same issue and same situtation. In the newest version, it isn't still resovled.

hello I tried old version 1.11 there is no issue

The technical architecture of 1.x and 2.x is quite different, so this does unfortunately not help to solve the issue. Please note that only the latest version is supported.

You can read here how to disable restrictions to pinpoint the restriction that is causing this:
#1751 (comment)

Can somebody try if this problem can be solved by using the quirk "noresolve" as described here:
http://forum.xda-developers.com/xposed/modules/test-xprivacy-2-0-37-ultimate-privacy-t2320783/post54076739

hi, thanks for you great work! the issue has fixed now. I have verified the version 2.1.25 with olympus image share v2.3