01-27-2014 04:08 AM
aLogcat as well as logging in ported Android apps not working on some BB10 devices. Can't figure out what can be the problem?
Any help will be highly appritiated.
01-29-2014 06:00 AM
Looks like it can be related to OS version. On OS 10.2 and up(?!) logcat not working. Somebody encountered this problem? Is there any wake to make logcat work on OS 10.2?
I really hope this forum alive and somebody checking our questions.
01-29-2014 03:19 PM
Could you further elaborate on what you mean when you say LogCat isn't working?
(Assuming you're using Eclipse) If you go to the DDMS perspective and select the device, does the LogCat show up?
01-29-2014 04:39 PM - edited 01-29-2014 04:40 PM
aLogCat is an application from BlackBerry World(Ported from Android). I noticed that it worked on OS 10.0,10.1 but not working on OS 10.2.
I also using logcat command to collect log from within application and send it via email. This doesn't work on OS 10.2 either.
01-30-2014 12:59 PM
Ah, my apologies. I thought you were referencing normal LogCat output.
I believe aLogCat is failing due to a missing native dependency. I have submitted a bug report against it.
Thanks for letting us know!
01-30-2014 02:23 PM
It appears I was incorrect in my initial assumptions.
The app behaves similarly on real Android devices. There was a change in Android 4.1 core that modified the behaviour of reading logs.
The developer of aLogCat will need to update their application.
01-30-2014 04:34 PM
Thanks for response.
I'm have no much expirience with Android and I use same technic as aLogCat to capture logs in my application.
I can't see the code right now, but from what I remeber it should be something like in this link:
It works fine on Android 4.x, but not on the ported application when runing it on OS 10.2. I will be gratfull if you could point out how to get it work on OS 10.2.
03-14-2014 02:00 PM
There are two issues here.
#1, aLogcat in the Gingerbread timeframe (so our 10.1 and lower timeframe) was able to access all logs. This is a security concern, and so Google changed logd in a later release so unprivledged applications could only access their own log entries.
So aLogcat can only access logging it's written (which isn't much, try it out on stock 4.2+)
#2, when we ported these changes to our version of logd, we missed something, so unprivledged applications don't get access to any logs.
#1 makes sense, and we intend to behave this way as well with our port of logd. We can address #2.