When debugging in the blackberry simulator, the console prints out a lot of other information relevant to the simulator along with the debug information printed in the application I develop. Is there a way to print only the debug messages of the application I am running in the simulator?
I always format my debug messages in specific way:
System.out.print(" ---RTP:"+message);
So it's easy to find specific message from my app.
Also, it's great to scrollock console searching or reading messages.
Related
I use Debug.WriteLine in Xamarin to view some responses to user interaction (for example), but Xamarin is writing several messages on it.
How can I reduce the number or avoid Verbose and not important messages that Xamarin send to the console?
Change to Release is not valid for me!
If i have an alert in my app
alert("howdy");
What do i have to do to view that alert using the adb logcat command? I've tried adb logcat *:v but nothing shows up - even though I can see the alert in the running app!
alert() shows a dialog in Android, doesn't do any console/adb.
However, if you want things to show up you should use logging tools
If you dive into documentation you need to use the debug, info and error methods to insert different levels of logging.
console.log(), console.warn() and console.error() work too.
I am trying to debug my game in logcat but when I add the script debugger in the build settings my logcat gets flooded with profiler is only supported in Unity Pro.. Since I'm not using the profiler and only use the Google Play Services as a 3th party script I suspect it of starting the profiler.
If so, how do I turn that off so I can debug properly? If not, what else could it be?
I have been trying to filter the text message profiler is only supported in Unity Pro. out of logcat but without success. I'm using the UI monitor.bat in the tools map that come with the Android-SDK. This should be a workaround.
According to the documentation: http://docs.unity3d.com/Manual/Profiler.html - the profiler is a Pro only feature.
The profiler is different from the debug log messages.
To get debug messages out of my app, I call Debug.Log("....") in my scripts, and just run adb logcat and the messages show up:
I/Unity (12241): Status Update: Starting sign-in...
I can't find much documentation around this issue. All other running apps on my pebble have a connection to my phone, and work as expected. However, a Pebble.js application I'm currently working on simply displays Disconnected - run the pebble phone app.
I have noticed that in my Developer Settings that the Connection Manager is listed as Disconnected. Is this part of the problem? I see nothing in the logs.
For reference, the application is doing a simple ajax request and displaying the result.
This message is often caused by the JavaScript crashing on the phone (undefined reference, unknown function, etc) and so the watch thinks it is not running.
Some ideas to debug this:
Replace your code with one very simple console.log("hello world") statement and see if this works.
Look at the Logs (View Logs button in CloudPebble or pebble logs on the command line).
Very rarely, on Android, I have seen situation where the Pebble app is in a bad state where it cannot execute the JS for only one app. When this happens, you need to force-kill the Pebble app and relaunch it.
I have had the same experience.
I usually kill and restart the pebble app on my phone and then I also do refresh the browser. Sometimes you have to log out of and then log back into Cloudpebble.
When a Blackberry phone is connected via USB and in debug mode, calls made to System.out.println() are visible in the log.
But is there any way to get access to "stdout" even from a program not in debug mode? Attaching with some command line program perhaps?
I worked around the issue by creating an over-the-network logging function.
If you have the JDE installed and BB plugged in via a USB:
JavaLoader.exe -usb eventLog > theLog.txt
This is often much more convenient for accessing the logs during dev.
There's no way to programmatically get the content though.