Bridge Log duplicates output

[qsrtech]

I believe after switching to 2.2 and bridge 2.07 my log(...) seems to get output twice. It was really confusing at first cause I thought my subs were being called twice. Just tried with emmulator and it seems ok...

 

[Erel]

Which device are you using?
This is most likely related to this change:
B4A-Bridge and Android 4.1+ logs

 

[qsrtech]

I am using s2 with 4.0.3...

 

[Erel]

Are you running the beta version?

 

[qsrtech]

yes 2.20 (help actually says 2.14) and bridge 2.07

 

[Erel]

Fixed for the stable version.

 

[ValDog]

I am using v2.52 of B4A and v2.07 Bridge, and am also seeing duplicate log entries. Can this be corrected?

 

[klaus]

Me too, I get double Logs.
B4A V2.52
B4ABridge V2.07
Android 4.1.1

Best regards.

 

[ValDog]

So, can this be corrected?

 

[Erel]

This is strange. Starting from Android 4.1 the permission log should be rejected. Do you see the logs (once) when you run in Release mode, when B4A-Bridge is connected?

 

[klaus]

Two times in Debug mode.
One time in Release mode.

Best regards.

 

[ValDog]

Yes.

 

[Erel]

The permission change is described here: Issue 34792 - android - Android Jelly Bean / 4.1: android.permission.READ_LOGS no longer works - Android - An Open Handset Alliance Project - Google Project Hosting

Are your devices rooted? On most Android 4.1 devices there will be no logs at all when running in Release mode as B4A-Bridge cannot read the logs of other applications (USB debugging can read all the logs).
In Debug mode the application sends its logs to B4A-Bridge which then sends the messages to the IDE.

 

[klaus]

My device is not rooted.

Best regards.

 

[ValDog]

Nor is mine...

 

[ValDog]

I've been seeing this behavior on my Motorola RAZR phone which is running Android v4.1.2. When I used my Google Nexus 7 (which is running v4.2.2) I did not see the duplication.

 

[Dave O]

Was this ever resolved? I'm getting it in B4A 3.50 on my Galaxy S3 running Android 4.3, not rooted.

Makes debugging a bit harder.

 

[Erel]

Download and install the attached B4A-Bridge. It removes the workaround for Android 4.1+ devices.

 

[Dave O]

Yep, that fixed it. Thanks Erel!