Richard Goh Active Member Licensed User Longtime User Aug 5, 2015 #1 I am using B4A version 5.02(i) and encountered that the logs doesn't work very well during debugging mode. Sometime the logs screen does not display error exception when it hit into error and terminate the debugging. Is there any missing setting? The filters option been check or unchecked also giving same issue. Another problem encountered is the Designer screen will somehow hanged or took over the hand phone screen after I stopped the screen designer connection. Ended up need to reboot the handphone. I am using Samsung Grand i9082. Any advice on this? Thank you.
I am using B4A version 5.02(i) and encountered that the logs doesn't work very well during debugging mode. Sometime the logs screen does not display error exception when it hit into error and terminate the debugging. Is there any missing setting? The filters option been check or unchecked also giving same issue. Another problem encountered is the Designer screen will somehow hanged or took over the hand phone screen after I stopped the screen designer connection. Ended up need to reboot the handphone. I am using Samsung Grand i9082. Any advice on this? Thank you.
Erel B4X founder Staff member Licensed User Longtime User Aug 5, 2015 #2 Richard Goh said: Sometime the logs screen does not display error exception when it hit into error and terminate the debugging Click to expand... The expected behavior in rapid debug mode is that the process terminates when there is an unhandled error. The error message with the stack trace should be printed in the logs (in red). Are you using USB debug mode or B4A-Bridge?
Richard Goh said: Sometime the logs screen does not display error exception when it hit into error and terminate the debugging Click to expand... The expected behavior in rapid debug mode is that the process terminates when there is an unhandled error. The error message with the stack trace should be printed in the logs (in red). Are you using USB debug mode or B4A-Bridge?
Richard Goh Active Member Licensed User Longtime User Aug 5, 2015 #3 Sorry the exception error is not showing on my Lenovo A5500-HV (8" pad). But on the Samsung it's does shown. I am using wifi connection.
Sorry the exception error is not showing on my Lenovo A5500-HV (8" pad). But on the Samsung it's does shown. I am using wifi connection.
Erel B4X founder Staff member Licensed User Longtime User Aug 5, 2015 #4 Are you testing it with debug (rapid) mode?
Richard Goh Active Member Licensed User Longtime User Aug 5, 2015 #5 Erel said: Are you testing it with debug (rapid) mode? Click to expand... Yes. I debugging in rapid mode. The exception details will shown when i debug using my samsung mobile. But no exception will show when using my lenovo 8" pad. Everything is the same except the mobile devices used is different only.
Erel said: Are you testing it with debug (rapid) mode? Click to expand... Yes. I debugging in rapid mode. The exception details will shown when i debug using my samsung mobile. But no exception will show when using my lenovo 8" pad. Everything is the same except the mobile devices used is different only.
Erel B4X founder Staff member Licensed User Longtime User Aug 5, 2015 #6 Try usb debug mode. It will most probably work.
Richard Goh Active Member Licensed User Longtime User Aug 6, 2015 #7 Sorry Erel, where can I find the option for usd connection? I only have IP connection in B4A Bridge connection.
Sorry Erel, where can I find the option for usd connection? I only have IP connection in B4A Bridge connection.
Erel B4X founder Staff member Licensed User Longtime User Aug 6, 2015 #8 See the first part of this tutorial: https://www.b4x.com/android/forum/t...w-way-to-connect-to-your-device.7978/#content
See the first part of this tutorial: https://www.b4x.com/android/forum/t...w-way-to-connect-to-your-device.7978/#content
