Android Question Logs not showing

[canalrun]

Hello,

My two main developer phones are an LG G3 (Android 5.01) and an LG G4 (Android 6.0).

I am using B4A 7.30; version 2.36 of B4A bridge on both phones.

The logs don't show (log window, right side) when I debug an application with the LG G4, but the logs do show debugging the same application using the LG G3.

I went back to B4A version 4.30. Debugging the same application (same B4A source), the logs do show for both the LG G4 and LG G3.

I noticed there was some discussion around 2015 about logs not showing. Has there been a solution to this? It seems that the logging may have stopped working sometime for certain phones for B4A versions greater than 4.30.

Thanks,
Barry.

 

[Erel]

It is strange that it is working with the older version of B4A. Are you sure that there weren't several instances of the IDE open when you tried it?

 

[canalrun]

Thanks, but nope there were not two instances running.

I just ran another test – rebooted the PC, restarted both phones, opened the B4A file and then alternated bridge connections between my two phones, the G3 and G4.

When compiling, downloading, running under debug to my G3 I got debug log statements. Without closing B4A when compiling, downloading, running under debug to my G4 I got no debug log statements. I did this back and forth several times with the same results.

I am using a Windows 10 computer to run B4A version 7.30.
I am using a Windows 7 computer to run B4A version 4.30.

Tomorrow I will try loading B4A version 4.30 on my Windows 10 computer to see if debug logging works with both the G3 and G4 as it did with Windows 7.

Searching with Google I found G4 posts concerning MTP and PTP USB modes when using USB debugging. There also was some mention of Enable OEM Unlock in Developer Options. These suggestions did not seem to apply.

Barry.

 

[canalrun]

I installed B4A 4.30 on my Windows 10 computer. This is the same computer that has B4A 7.30 installed. The paths are configured the same for the two B4A versions.

Using B4A 4.30 when I debug the project on the LG G4 the logs show as expected.

This is the same project, same code, where the debug logs did not show on the LG G4 when using B4A 7.30.

The debug logs showed correctly when using 7.30 debugging on my LG G3.

I have several other phones I could try with Android versions varying between 4.4 and 7.0, but my guess is that they will all work with both B4A 4.30 and B4A 7.30.

If I search Google I find people who have had problems debugging with the LG G4 – there doesn't seem to be a definite solution.

Something in the B4A bridge debugging chain must changed between 4.30 and 7.30 that is causing this problem on the G4. The B4X forum suggestions from 2015 suggest trying USB debugging. This is not an option in my case, since my phone USB ports are usually occupied by charging or other devices.

Any suggestions?

Thanks,
Barry.

 

[Erel]

Something in the B4A bridge debugging chain must changed between 4.30 and 7.30 that is causing this problem on the G4.

Many things were changed. The logs should work better in most cases. Previously the logs were sent from the running app to B4A-Bridge and then to the IDE. This caused all kinds of problems. Now they are sent directly to the debugger.
They also work in release mode (With #BridgeLogger: True).
Make sure that you are using the latest version of B4A-Bridge on your device.
Do this test, change the package name and run it. Does it help?

 

[canalrun]

Yes, amazing.
I changed the package name and debug logs showed up when when compiled with B4A 7.30 executing on my LG G4.

Why on earth would that work?

Unfortunately, I cannot continue with the new package name since updates will not work properly in Google Play.

I tried uninstalling the old and new package named apps and then reinstalling the old package name app. Once again debugging logs did not show on my LG G4 (but they did show on a couple other phones I tried, LG G3 (Android 5.01), XGODY Y19 (Android 7.0)).

Why would changing the package name make a difference?

Can I somehow continue with the old package name, but do something that mimics what occurred when I switched to the new package name to make it work?

Thanks,
Barry.

 

[Erel]

You can create a "debug" build configuration with a different package name.

The network port used for the remote logger is based on the package name. Can you send me a private message with the package name?