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

New beta 2.2.11 crashes #1893

Closed
Phylon opened this issue Aug 18, 2014 · 10 comments
Closed

New beta 2.2.11 crashes #1893

Phylon opened this issue Aug 18, 2014 · 10 comments
Labels

Comments

@Phylon
Copy link
Contributor

Phylon commented Aug 18, 2014

What I have done:
start XPrivacy App
enter xpr for filtering
tap on XPrivacy icon
try to scroll up categories quickly
-> screen freezes for a moment, becomes black, then popup: XPrivacy stopped, press o.k.
2 logcats, because adb stopped after switching on the phone, before I could reproduce the crash:
https://drive.google.com/file/d/0B4Mtd9MlTPoNaXE3cE5CSERvT2s/edit?usp=sharing
second logcat: started while phone already running, then opening Xprivacy and reproducing the crash
https://drive.google.com/file/d/0B4Mtd9MlTPoNam9OdjJDN0FKQWM/edit?usp=sharing

@M66B M66B added the bug label Aug 18, 2014
@M66B
Copy link
Owner

M66B commented Aug 18, 2014

E/AndroidRuntime( 3668): FATAL EXCEPTION: Thread-267
E/AndroidRuntime( 3668): java.lang.RuntimeException: An error occured while executing doInBackground()
E/AndroidRuntime( 3668):    at android.os.AsyncTask$3.done(AsyncTask.java:299)
E/AndroidRuntime( 3668):    at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
E/AndroidRuntime( 3668):    at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
E/AndroidRuntime( 3668):    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
E/AndroidRuntime( 3668):    at java.util.concurrent.FutureTask.run(FutureTask.java:137)
E/AndroidRuntime( 3668):    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1076)
E/AndroidRuntime( 3668):    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:569)
E/AndroidRuntime( 3668):    at java.lang.Thread.run(Thread.java:856)
E/AndroidRuntime( 3668): Caused by: java.lang.NullPointerException
E/AndroidRuntime( 3668):    at biz.bokhorst.xprivacy.fo.<init>(SourceFile:53)
E/AndroidRuntime( 3668):    at biz.bokhorst.xprivacy.af.doInBackground(SourceFile:1234)
E/AndroidRuntime( 3668):    at android.os.AsyncTask$2.call(AsyncTask.java:287)
E/AndroidRuntime( 3668):    at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
E/AndroidRuntime( 3668):    ... 4 more

@M66B
Copy link
Owner

M66B commented Aug 18, 2014

Can you please try if this version fixes the problem:
https://crowd.xprivacy.eu/XPrivacy_2.2.11.apk

@M66B
Copy link
Owner

M66B commented Aug 18, 2014

I will release a new version as soon as the fix is confirmed.

@Phylon
Copy link
Contributor Author

Phylon commented Aug 18, 2014

Sorry, but this takes a little while... I was running my own XPrivacy build. I modified some strings to fix a menu display problem. So I had to deinstall XP first (not being aware this also would delete my license file). I am just looking for my backups to get the license back to be able to import my most recent settings...

@Phylon
Copy link
Contributor Author

Phylon commented Aug 18, 2014

I have tested your version, this issue seems to be fixed. Good! I hope my whole deinstall-reinstall-export-import-procedure did not interfere. I have also taken the chance to check the documentation icons. Tapping on the icon on function level works, on category level it does not. Shall I create an issue for thatl?

@M66B
Copy link
Owner

M66B commented Aug 18, 2014

Thanks for testing!

Category help works for me.
Do you block toasts somehow?

@M66B M66B closed this as completed Aug 18, 2014
@Phylon
Copy link
Contributor Author

Phylon commented Aug 18, 2014

I don't know how to block toasts. At least, XPrivacy itself is completely unrestricted. And I have seen toasts ("restricted by XPrivacy") when I recently had put a restriction too much on my calendar app. Where do I have to look for such blockages?

@Phylon
Copy link
Contributor Author

Phylon commented Aug 20, 2014

Thanks, your hint pointed me in the correct direction, Yet it took me hours to find the solution . Since I didn't find anything helpful about blocking toasts with google I made a logcat out of desperation. So I found a message from the notification service that a notification from xprivacy was suppressed by user request. This message and google finally led me to the app manager. Notifications were switched off for xprivacy. I was not aware of the existence of this setting at all and I do not remember to have even touched xprivacy in the app manager. So I am still wondering about how and why, since notifications seem to be switched on by default for other apps. The good thing is: I solved a second issue I had for some time. Searching for updates didn't work for me, I got no respose. Now I know why. :-)

@M66B
Copy link
Owner

M66B commented Aug 20, 2014

Thanks for reporting back about this. I am sure this will be helpful to somebody else in the future.
Which app manager / ROM are you using?

@Phylon
Copy link
Contributor Author

Phylon commented Aug 20, 2014

Then I will also report on XDA. I am still using Samsung stock ROM JB 4.1.2 on my Galaxy Note and stock app manager. However, I have already invested some hours in ROM research. I will lose a few features but since privacy is more important to me it seems I must move to Kitkat now. I am already almost sure I am going to use Omnirom, but I have not made my final decision yet. -- stopping OT talk now :-)

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