Hi Sir
I have configured and running the app using Windows Xp (eclipse indigo and
NDK) the bigbluebutton client for Android Devices.
I don't have any Comile time error not any runtime error.
Apps came successfully but when i click on to the bigbluebutton app then i
got the error message.
*The
Can some one please tell me , how do u read the log file or logs ...
which the Log.i methods writes to ?
Also , I have used the exact code as documented at Android site for
Hello View , to load google.com and load a basic html page created by
me . The app does not show any error ,BUT
it does not
On Wed, May 20, 2009 at 1:37 AM, abhinav gnroses.infla...@gmail.com wrote:
Can some one please tell me , how do u read the log file or logs ...
which the Log.i methods writes to ?
You read the log by connecting your phone to a computer and running
'adb logcat' (or adb shell logcat) from the
Hi,
You can try out 'adb logcat' in terminal, to see the logs when emulator is
started.
Best Regards,
Bindu
On Wed, May 20, 2009 at 2:07 PM, abhinav gnroses.infla...@gmail.com wrote:
Can some one please tell me , how do u read the log file or logs ...
which the Log.i methods writes to ?
Hey guys!
So i found the solution to debug this. Apparently ADB has a tool to
show the debug logs of the OS, when I did that I saw the Out of
memory error. Apparently, Android limits apps to use only 16megs of
memory before automatically killing it. It'd be nice though if this
error were shown
The user will get a nice This applicated failed and will now close and
that's why you need to debug and see the log for errors because we are
developers.
I don't really see the need of a more friendly way to do that.
What you can also do is be writing the log to a file for later reading.
Somebody
Let's say this.
You dump the log to a file during the running and if it crashes, next time
the user loads the app he/she has an option of sending the report to you.
That's should be a very good option.
Ivan Soto Fernandez
Web Developer
http://ivansotof.com
On Tue, Apr 28, 2009 at 11:26 AM,
Good workaround. However, technically the OS should be able to
gracefully kill an app should it eat too much memory. As such an out
of memory specific message is better than a generic one to reduce
ambiguity. Remember, users of this OS aren't necessary developers, as
such, they're not smart
Most users don't care whether your app crashed because it was out of memory
or for some other reason, and probably wouldn't even understand the
difference. They just know it broke.
On Tue, Apr 28, 2009 at 1:05 PM, Kenn Min Chong kmch...@gomez.com wrote:
Good workaround. However, technically
Have you looked at the stack crawl in the log? Nobody can give help unless
you at least provide that.
On Wed, Apr 22, 2009 at 5:03 PM, Kenn Min Chong kmch...@gomez.com wrote:
Hi there!
For some reason I can't explain, when my app runs, I will on
occasion get the following error message:
To try catch the whole code is not a good practice but... have you tried to
catch exception or throwable?
It is not necesserly the system that is bugging but your thread may
eventually be candidate to garbage collection if no reference is made to it
and your parent thread has closed.
Are you
Best bet is to post a log and than we can help you narrow it down
On Apr 22, 7:03 pm, Kenn Min Chong kmch...@gomez.com wrote:
Hi there!
For some reason I can't explain, when my app runs, I will on
occasion get the following error message:
“The application (process xx) has
12 matches
Mail list logo
