I have tested my app on my on phone and the behaviour is very stable. But on the Samsung S3 (4.1.1) is crashes sometimes without any message? Is there any whay to find a crash report or is this something I need to implement?
When I use the log(..) command is this also loging to some file on the device? or is it removed after you compile as release?
A way to find out is to plug in your device to the PC and check the unfiltered logs, you might not see a message on the device but you will see it on the unfiltered logs.
A way to find out is to plug in your device to the PC and check the unfiltered logs, you might not see a message on the device but you will see it on the unfiltered logs.
Somehow I think that in general, crashes are not model dependent. I'm sure you have your reason to suspect s3's behavior (or maybe not), but from my personal experience, I noticed that 100% of crashes at users' devices, (for which I was swearing it was due to their 'cheap' devices) turned out to be my coding fault, or anyway, an error (or big loop) I missed to trap.
Somehow I think that in general, crashes are not model dependent. I'm sure you have your reason to suspect s3's behavior (or maybe not), but from my personal experience, I noticed that 100% of crashes at users' devices, (for which I was swearing it was due to their 'cheap' devices) turned out to be my coding fault, or anyway, an error (or big loop) I missed to trap.
I agree. I think it is the OS version. But in the emulator everything works fine and my test device I cannot upgrade to 4.1.1. So I would like to have some general exception handler that log to a file or something...
perhaps you could use a logcat from inside your app? then, you could log all unfiltered logs to a file. But I think this will consume much space. Well, you never know, I would give it a try if this was the case
You can use messagebox to find the problem, when your app crash, memorize the last messagebox, after search in your code the last messagebox.
Sorry for my bad english
You can use messagebox to find the problem, when your app crash, memorize the last messagebox, after search in your code the last messagebox.
Sorry for my bad english
I don't think there is a general exception handler, but if you have an idea of where it is occurring, you could use Try/Catch like this:
B4X:
Try
' Do whatever you think may be causing an error
Catch
ToastMessageShow ("Error while doing whatever. Reason = " & LastException.Message, True)
End Try
Did it work fine before they updated? The S3 update was really a let down and I'm glad I had returned my device for the bad screen it had. My brother kept his though and has all kinds of issues since the update with things crashing and such. He has been thinking of going back to the original version since they didn't even add Multi-Windows or Popup Browser...only the popup video which isn't much.
Did it work fine before they updated? The S3 update was really a let down and I'm glad I had returned my device for the bad screen it had. My brother kept his though and has all kinds of issues since the update with things crashing and such. He has been thinking of going back to the original version since they didn't even add Multi-Windows or Popup Browser...only the popup video which isn't much.
Well, this user has a brand new system. So he didn't update. But I have never crahses only on this version of android. But in the emulator I cannot reporduce it. It has someting to do with the change from the gps from the state not fix to fix. I am looking for a way to do good logging...