jgilfelt / ghostlog Goto Github PK

Your empty IntegrationService constructor does not chain to the superclass. At present, that does not pose a problem, but it could in future versions of Android. I would either delete the IntegrationService constructor or have it chain to the superclass to be safe.

vdu

1. I installed the app from the PlayStore
2. Added compile 'com.readystatesoftware.ghostlog:ghostlog-integration:+' to build.gradle
3. Turn it on, but it doesn't work.

I can confirm the JAR + manifest code works.

Am I doing something wrong?
Thoughts?

Thanks!

In light of this aosp-mirror/platform_frameworks_base@719c44e it's probably not a good idea to use a long running AsyncTask in a 3rd party lib.

I have android device which is rooted. I need to perform Runtime.getRuntime().exec("su") .and I have added READ_LOGs permission in manifest also. But even though i have root device its still gives me access denied. I have seen most of the blogs still the issue remains same. Can you please tell me Is there anything missing here

Characters to the right of the first space are displayed in the message.

I use AS 1.5

Symptons: I turn GhostLog on, SuperSu dialog popups but is unclickable.

I believe that maybe the overlay is starting showing before the SuperSU 'dialog box' and that makes the 'dialog' unclickable for security reasons...

Right now, AFAICT, anyone can listen in on broadcasts from an integration-enabled app to GhostLog and therefore sniff on log messages. In theory, that should not happen in production, as nobody should ship an app with GhostLog integration enabled.

In theory, I'd have hair. :-)

Three ways come to mind to help limit this:

1. Have the Intent for the broadcast specify the component name, instead of (or in addition to) the action string. This will limit your ability to refactor this portion of GhostLog, so as not to break prior integration code, but it would preclude other apps from receiving the broadcast. However, this would require you to move your BroadcastReceiver into your manifest, as opposed to the registerReceiver() that you have today.
2. Use an IntentFilter that sets the priority to Integer.MAX_VALUE and use an ordered broadcast, aborting it after you receive it. This means that a potential sniffer would have to set up their receiver first. However, again, I think your use of registerReceiver() may be a problem here -- while I have not tried playing with competing apps, one registered in the manifest, one registered via registerReceiver(), I would not be the least bit surprised if the manifest one gets in first, at least in certain circumstances.
3. Use a custom permission that integration-enabled apps must request via <uses-permission>. This would at least alert users to other apps that want to listen in on GhostLog broadcasts. Alas, you cannot use signature-level permissions, since the integration-enabled apps aren't written by you, in general.

ope
n

Be sure to put full instructions and documentation within the app. Sometimes we are offline and have no way to look up what the app is supposed to do.