Open crankycoder opened 9 years ago
If the Build.HOST is 'cyanogenmod', we should also throw up a user visible warning that there are known issues on cyanogenmod and the user should pay attention to any permission checks guarded by CM Privacy Guard.
"Known issues" sounds as if MozStumbler would likely have problems with scanning which is wrong. IMO we should have a help/faq page in the app/in the GitHub wiki that explains stuff like this:
If scanning doesn't work: Possible reasons 1. 2.
Doing this at the same time as checking for xposed in #1485 seems to make sense.
We should do a quick check to see that we can actually use all the permissions we need to run properly on startup.
This would alleviate the problems we see on Cyanogenmod and the odd firmware which puts special permission restrictions on us and we could notify the user in a sensible way on application start.