danijel Active Member Licensed User Longtime User Oct 21, 2018 #1 Why I can't see any logs? I have this problem since B4A v8.0 Updated to v8.50 now... still the same problem. I am using B4A-Bridge v2.53
Why I can't see any logs? I have this problem since B4A v8.0 Updated to v8.50 now... still the same problem. I am using B4A-Bridge v2.53
Geezer Active Member Licensed User Longtime User Oct 21, 2018 #2 Check the buffer size for logging in your developer options menu. Upvote 0
mcqueccu Expert Licensed User Longtime User Oct 21, 2018 #4 Add the code when you are using B4A-Bridge Code: Copy #BridgeLogger: True Upvote 0
danijel Active Member Licensed User Longtime User Oct 21, 2018 #5 Add #BridgeLogger: True to enable logs in Release mode. This is for Release mode. I am trying get logs in debug mode. However, I tried and I can't get to logs in any way. Upvote 0
Add #BridgeLogger: True to enable logs in Release mode. This is for Release mode. I am trying get logs in debug mode. However, I tried and I can't get to logs in any way.
Erel B4X founder Staff member Licensed User Longtime User Oct 21, 2018 #6 mcqueccu said: Add the code when you are using B4A-Bridge Click to expand... This is true but only relevant when compiling in release mode. My guess is that logs are disabled on your device. Enable the developer settings and look for any setting related to the device logs. Upvote 0
mcqueccu said: Add the code when you are using B4A-Bridge Click to expand... This is true but only relevant when compiling in release mode. My guess is that logs are disabled on your device. Enable the developer settings and look for any setting related to the device logs.
danijel Active Member Licensed User Longtime User Oct 21, 2018 #7 Developer options are enabled. This is all related to logs. Changing buffer size didn't help. Upvote 0
Sandman Expert Licensed User Longtime User Oct 21, 2018 #8 I don't know if this is true for your case also, but I've seen some really strange things from some phone brands. So I would recommend doing a quick test with some other phone brand also, if you have it. Upvote 0
I don't know if this is true for your case also, but I've seen some really strange things from some phone brands. So I would recommend doing a quick test with some other phone brand also, if you have it.
Erel B4X founder Staff member Licensed User Longtime User Oct 21, 2018 #9 Also worth switching to USB debug mode instead of B4A-Bridge. Upvote 0
danijel Active Member Licensed User Longtime User Oct 21, 2018 #10 Sandman said: I don't know if this is true for your case also, but I've seen some really strange things from some phone brands. So I would recommend doing a quick test with some other phone brand also, if you have it. Click to expand... I found some old device and finally logs are showing... so something is wrong with my Huawei device. Upvote 0
Sandman said: I don't know if this is true for your case also, but I've seen some really strange things from some phone brands. So I would recommend doing a quick test with some other phone brand also, if you have it. Click to expand... I found some old device and finally logs are showing... so something is wrong with my Huawei device.
danijel Active Member Licensed User Longtime User Oct 21, 2018 #11 I made fresh new project and copy/paste old code to new project. Not sure what type of conflict issues caused the problem but logs are now showing on all connected devices. Thank you all for trying to help. Upvote 0
I made fresh new project and copy/paste old code to new project. Not sure what type of conflict issues caused the problem but logs are now showing on all connected devices. Thank you all for trying to help.
