tuhatinhvn Active Member Licensed User Longtime User Mar 23, 2014 #1 When we code and debug , we often use. Function Log(something) to show value of it But i want to ask when apk run on real phone,this function can make app run slowly??
When we code and debug , we often use. Function Log(something) to show value of it But i want to ask when apk run on real phone,this function can make app run slowly??
DonManfred Expert Licensed User Longtime User Mar 23, 2014 #2 LOG is only written when compiled in debug. An working app should be compiled in Relese-mode. LOGs are not written to log in release-mode. So you can let the LOG-commands in. Upvote 0
LOG is only written when compiled in debug. An working app should be compiled in Relese-mode. LOGs are not written to log in release-mode. So you can let the LOG-commands in.
thedesolatesoul Expert Licensed User Longtime User Mar 23, 2014 #3 Unless you are dumping a significant amount of data it should make no noticeable difference. Upvote 0
thedesolatesoul Expert Licensed User Longtime User Mar 23, 2014 #4 DonManfred said: LOG is only written when compiled in debug. An working app should be compiled in Relese-mode. LOGs are not written to log in release-mode. So you can let the LOG-commands in. Click to expand... Logs are written to log in release mode. Upvote 0
DonManfred said: LOG is only written when compiled in debug. An working app should be compiled in Relese-mode. LOGs are not written to log in release-mode. So you can let the LOG-commands in. Click to expand... Logs are written to log in release mode.
DonManfred Expert Licensed User Longtime User Mar 23, 2014 #5 thedesolatesoul said: Logs are written to log in release mode. Click to expand... Ahh, ok. But the log is not shown in b4a when running an app in release-mode? Upvote 0
thedesolatesoul said: Logs are written to log in release mode. Click to expand... Ahh, ok. But the log is not shown in b4a when running an app in release-mode?
thedesolatesoul Expert Licensed User Longtime User Mar 23, 2014 #6 You mean in the B4A IDE? It is shown there too. Upvote 0
DonManfred Expert Licensed User Longtime User Mar 23, 2014 #7 I have something in mind i have read that somewhere here in forum from erel... Excuse me if i´m wrong. It could be this what i have in mind... Upvote 0
I have something in mind i have read that somewhere here in forum from erel... Excuse me if i´m wrong. It could be this what i have in mind...
thedesolatesoul Expert Licensed User Longtime User Mar 23, 2014 #8 Ah I see. You mean the B4A Bridge does not read the logs? I thought it uses the 'READ_LOGS' permission just to do that. I always use USB Debugging which always reads the logs. Thank you for correcting me. Upvote 0
Ah I see. You mean the B4A Bridge does not read the logs? I thought it uses the 'READ_LOGS' permission just to do that. I always use USB Debugging which always reads the logs. Thank you for correcting me.
Erel B4X founder Staff member Licensed User Longtime User Mar 24, 2014 #9 The explanation is here: B4A-Bridge and Android 4.1+ logs Starting from Android 4.1 each process can only read its own logs. The "read logs" permission no longer works. The only exception is when you are connected in USB debugging mode (ADB). When you run your app in debug mode with B4A-Bridge connected it send the logs to the bridge app. Upvote 0
The explanation is here: B4A-Bridge and Android 4.1+ logs Starting from Android 4.1 each process can only read its own logs. The "read logs" permission no longer works. The only exception is when you are connected in USB debugging mode (ADB). When you run your app in debug mode with B4A-Bridge connected it send the logs to the bridge app.
