Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

Logcat location /settings error #1094

Closed
an0n981 opened this issue Jan 10, 2014 · 22 comments
Closed

Logcat location /settings error #1094

an0n981 opened this issue Jan 10, 2014 · 22 comments
Labels

Comments

@an0n981
Copy link
Contributor

an0n981 commented Jan 10, 2014

01-10 18:28:51.990 E/XPrivacy(2415): java.lang.ClassCastException: android.location.LocationManager$ListenerTransport cannot be cast to android.a.a uid=1000
01-10 18:28:51.990 W/System.err(2415):  at biz.bokhorst.xprivacy.XLocationManagerService.d(Unknown Source)
01-10 18:28:51.990 W/System.err(2415):  at biz.bokhorst.xprivacy.XLocationManagerService.a(Unknown Source)
01-10 18:28:51.990 W/System.err(2415):  at biz.bokhorst.xprivacy.XPrivacy$1.beforeHookedMethod(Unknown Source)
@M66B
Copy link
Owner

M66B commented Jan 10, 2014

Can you please try if this version fixes the error and if location restriction still works: http://d-h.st/9ib

This version should also be able to restrict locations acquired through the Google Play services again.

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 10, 2014

That error has disappear. However now it is logging this error:

01-10 19:05:04.615 E/XPrivacy(5481): java.io.FileNotFoundException: /data/data/biz.bokhorst.xprivacy/shared_prefs/biz.bokhorst.xprivacy.provider.settings.xml: open failed: ENOENT (No such file or directory) uid=10064

UID 10064 is SuperSu and the settings.xml is there and readable

Locatons are being blocked properly for Google Maps and Maps With Pro is able to access GPS location

@M66B
Copy link
Owner

M66B commented Jan 10, 2014

Thanks for testing and reporting back!

I have no explanation for the other error.
Can you please post some more log lines (before and after the message) ?

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 10, 2014

https://mega.co.nz/#!d15FkDaJ!x4uYcfqxaFCt7o2nBngTcfcRLHl6hE49JBdzNsyXFTw

here's the whole log. Sorry can't really format it down right now as I am on the train

@M66B
Copy link
Owner

M66B commented Jan 10, 2014

Thanks for the log file.
I will look into it tomorrow.

@M66B
Copy link
Owner

M66B commented Jan 11, 2014

Did you clear data and then reboot?

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

Xprivacy data? Definitely not. I just installed the new version over the old and rebooted.

@M66B
Copy link
Owner

M66B commented Jan 11, 2014

Do you still have these errors on subsequent reboots?

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

yes

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

Should I clear data to see if that helps?

@M66B
Copy link
Owner

M66B commented Jan 11, 2014

No, don't clear data.
It is good that this can be reproduced.
It is a more serious problem than it looks like, so I like to solve it.

Can you please post the output of:

ls -al /data/data/biz.bokhorst.xprivacy/shared_prefs/biz.bokhorst.xprivacy.provider.settings.xml

And a more complete logcat, with more than only the XPrivacy logging?

Does your Android version have SELinux (Fort Knox) enabled?

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

Output:

 -rw-rw-r-- u0_a93   u0_a93     160638 2014-01-11 10:35 biz.bokhorst.xprivacy.provider.settings.xml

No SELinux here.
Please provide a secure upload location for logcat

@M66B
Copy link
Owner

M66B commented Jan 11, 2014

You can use this contact form: http://forum.faircode.eu/contact/

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

Logcats sent. The strange part is it did not occur when I was connect to PC adb (Logcat.txt)

@M66B
Copy link
Owner

M66B commented Jan 11, 2014

It looks like this problem is caused by restricting /proc.
I have not figured out how yet, but could you try without this restriction?

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

still the same error. Xprivacy doesn't even show usage data for wanting access to proc

M66B pushed a commit that referenced this issue Jan 11, 2014
@M66B
Copy link
Owner

M66B commented Jan 11, 2014

Can you please try again with this version and make a new logcat: http://d-h.st/EUE

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

Logcat sent, I have also completely unrestircted ID.

@M66B
Copy link
Owner

M66B commented Jan 11, 2014

I didn't receive the log file ...

@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

sorry. captcha error. now

@M66B
Copy link
Owner

M66B commented Jan 11, 2014

@an0n981 Thanks to your help I have figured out what is going on. The latest test version I have sent has almost fixed this problem. I will release a new version today that will have this problem fixed.

Your device seems not to be very fast (or the exact opposite of that), which device are you using?

@M66B M66B closed this as completed Jan 11, 2014
@an0n981
Copy link
Contributor Author

an0n981 commented Jan 11, 2014

Thumps up. Thanks for your dedication.
I have a Samsung Galaxy Note 2 running OmniRom 4.4.2. No performance issues here

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants