Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Option to see core logging #28

Open
M66B opened this issue Dec 11, 2012 · 3 comments
Open

Option to see core logging #28

M66B opened this issue Dec 11, 2012 · 3 comments

Comments

@M66B
Copy link

M66B commented Dec 11, 2012

Option to see the core PDroid logging to pinpoint problems like the Go SMS problem.
A logcat contains mostly too much noise (not PDroid logging) to easily identify problems.

@wsot
Copy link
Collaborator

wsot commented Dec 11, 2012

I can understand why you would want a feature like this, but to be honest I don't think I'll include it for a couple of reasons.
First, there are good on-device logging apps like CatLog Log Reader and aLogCat, which provide filtering by app name and those sorts of things.
The second reason is that viewing the logs of other apps now requires root access, so it would mean PDroid Manager requesting root privileges.

An alternative, which would require changes to the core, would be for PDroid core record its own logs internally, and then PDroid Manager could read the logs from the PDroid core.

Feel free to respond if you disagree, or want to raise other points.

@tamcore
Copy link
Contributor

tamcore commented Dec 12, 2012

Maybe it would help if PDroid Core, etc would write it's logs to a different 'buffer'.

Changing stuff like System.err.println(....); to something like Log.d("PDroid", ...); would allow it to use adb logcat -b PDroid to get the correct logs.

@wsot
Copy link
Collaborator

wsot commented Dec 13, 2012

TamCore: That would certainly be better. I'm actually going to do a bit of code clean-up on the core sometime soon so I'll probably try to do something about the logging then.
Right now, there is just not enough useful detail to diagnose problems, and some annoying bugs (e.g. sending an intent directly to a class causes a null pointer exception stack trace).

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

No branches or pull requests

3 participants