Logs on Jelly Bean and Log Viewer

[pas]

:sign0085:
I am having problem where Log() output does not seem to work (nothing is output in the IDE logs pane) when running on a Google Nexus 7 with Jelly Bean. The same application running on a Samsung phone with ICS works as expected. Is there a problem with catlog on Jelly Bean? I read somewhere that a new permission is required but it is not clear to me what needs to be done on a B4A application.

My second question is with regard to the stand alone Log Viewer (v1.3). I can not get it to do anything on either Jelly Bean or ICS. When I click Start, the response dialog says: "No devices Connected!" The B4A Bridge and debugger are working as expected when this error is displayed so I do not understand what else needs to be connected.

I am using the B4A in WiFi mode if that matters.
Thank you for any assistance.
-Paul

 

[Erel]

It works fine here, tested on Galaxy Nexus running 4.1.1.
Though according to this discussion: https://groups.google.com/forum/?fr...S/android-developers/6U4A5irWang/8xOi74KfRIYJ this change should indeed break the logs functionality when connected with B4A-Bridge. We will need to implement a workaround for this. I already have an idea

Note that you can connect with USB debugging instead.

The logs should show messages from B4A-Bridge app. Don't you see any message at all?

 

[pas]

Thank you for the reply.

I rooted the Nexus 7 (did nothing else) and now the Log() messages show.
I did see some (appeared to be system level) messages prior to rooting but not the ones I specifically added via the Log() function.
I will guess your Nexus is rooted?

I would like to use the separate Log Viewer application but have had no luck with it as when I click Start it says "No Devices Connected". Does it only work via USB debugging?

Not sure USB debugging is an option for me as I am working on a project that uses OpenAccessory.

-Paul

 

[Erel]

I was wrong. It also happens on the unrooted Galaxy Nexus running JB. Only the logs related to B4A-Bridge app are printed.

Any other log viewer will require USB debugging.

 

[joneden]

Hi Erel,

Any progress on this one? I think I'm experiencing the same issue....

Regards,

Jon

 

[Erel]

The logs will be available in the next version, which is not far away. The logs will only include the "filtered" logs as it is not possible to read other logs (without USB debugging).

 

[joneden]

Good stuff thanks Erel. Are we talking weeks away?

 

[Erel]

I hope that the beta version will be released next week.

 

[joneden]

That is good news - I'll certainly try out the beta version

Regards,

Jon

 

[bluejay]

Hi Erel,

Note, ver 2.51 beta still does support logging on my Galaxy S3 Jellybean (using the bridge and WiFi).

Is this fixed in 2.51 final version?

bluejay

 

[Erel]

Are you running your app in Debug mode? Logs will only appear in this mode.

 

[bluejay]

It did not work in debug until I realised this particular App I was revisiting did not have INTERNET permisiions and hence was not connecting to the debugger.

Thanks - it all works now on Jellybean provided:
a) I compile under debug mode
b) make sure INTERNET permission is added to the APP

For older OS I don't need to either of the above.

bluejay

 

[Erel]

I guess that you have set the manifest file to be read-only. This is not recommended and not required.