I am having an app in the store which runs fine on most devices but on one particular
Samsung Galaxy S2 running Android 4.1.2 (version JZO54K.I9100XWLSS).
It crashes on startup without a crash-report from google or from crashlytics which i integrated. Its not actually a crash it just flashes the main activity a while until the phone shuts down:
A video of that behavior:
https://dl.dropboxusercontent.com/u/523370/20131004_115027%5B1%5D.mpeg
Its a device from a user, so I cannot debug it locally. (Is there something to get a live logcat stream from the phone over the air?)
Has anyone experienced such a "crash" on start only affecting one particular device?
I have a SGS2 where it works without flaws. Could there be any hardware reasons resulting in such a crash e.g. Memory issue.
I know this problem is not likely to be resolved without any further source code / crashreports, but maybe someone can point me in the right direction.
best regards,
Mike
Actually shoe rat saved my day!
Because shoe rat just commented on the case I am answering it for completeness.
The user enabled the option
"Do not keep activities" which lead to this strange behavior, because an activity was killed during the splash screen.
As a future reminder to myself I will get rid of the splash screen because its not holo-style anyway.
Cost me a lot of time to figure this out and i probably wouldn't have found it without your help.
Related
App Crash on Android Tablet and when ever tried to open it again it open a blank black screen there after. This is happening with android debug build.I have tried to replicate the issue on simulator and it didn't happen. Please let me know if any clues about this issue. Is it something related to inefficient memory usage or something else. Is there any tool I can use to narrow down this issue. This is not happening on IOS devices and even Android Phones.
Guys I have an application that works on the tablet.That is a smart house application.I root the tablet because I want to forbid the customers to use anything else but application on the tablet.Application is always visible and working non stop on the screen whenever tablet is on.But there is a problem.The problem is when application running about 1 day sometimes 2 days tablet collapses.That's why it needs to be restarted each time when that happens.I think it might be a problem of ram aka main memory.I just wonder about your thought.If I use garbage collector or some ram cleaner or ram expander, will it be a solution for me ?
Thanks in advance.
Your problem appears to be a memory leak in your application.
Since this is a complex issue to identify and/or resolve, you could try some common tools to aid you, such as:
https://medium.com/freenet-engineering/memory-leaks-in-android-identify-treat-and-avoid-d0b1233acc8#.z178mon4s
http://android-developers.blogspot.ch/2009/01/avoiding-memory-leaks.html
https://github.com/square/leakcanary
First off, this has never happened before on any other android device I've used (multiple devices have been tried and tested before this).
Now I have an app that I have worked on for a little over a year now, it is called AutomatedId (on the app store) and it has worked quite well for my company for quite some time.
Recently I have been given a device to add compatibility to the app (specifically for reading UHF tags) but that isn't the problem.
The problem comes whenever you open the app, the screen stops reading inputs completely, as well as buttons cease to function. I turned on developer options to see the screen inputs and as i suspected, it completely stops and does not read any of the inputs after the app is opened. Clicks don't work, buttons don't work, keyboard doesn't open, hardware buttons on the device stop working. It's a mess, does anyone know what could have caused this?
This is a S98 from here: http://www.wepoy.com/product_view_18.html
moved my comment to the answer as you said. This may be due to memory leak. Here are some references that may help you fix them: Fixing-Memory-Leaks-in-Android-Studio & use this library from square to detect memory leaks early: leakcanary
I just learned Android from scratch and built an app with simple process using Android Studio.
The app has one process with repeating Alarm manager which will toast a message after 10 mins. That's it.
However, once I install it on a real device, after an hour or so, the device will ask to Share Bug Report. When I do share it,(via e-mail to my self), it is just a blank black screen..!
This happens with any device. I tried it on 3 devices so far. It is like:
Device before my app: Normal functioning.
Device after installing my app (after an hour or 2): A pop up comes
up with 'Share bug report'.
PS: I have not written any code to call or share bug report or any popup.
Has anyone come across this strange behavior?? Any idea on what is happening here??
EDIT 1: It is not just a blank screen but there is a word doc with lengthy set of code. It basically contains the entire lump of data of entire system. Not just my app..!
Probably your app is freezing or stops responding.
Analyze your app logs, you will find the cause.
Did you read these threads ?
What does it mean with bug report captured in android tablet?
http://android-developers.blogspot.com/2010/05/google-feedback-for-android.html
I am developing an application for Android ICS's 7 inch tablet. In application there is use of camera function to capture image. I allocate camera when somebody opens activity and after work completes camera releases. This is working fine. When I test this thing for 50 times continually with 4~5 frequency of opening and closing activity, application do not respond to application, Neither for in built applications and suddenly screen gets black and I need to restart system again to continue previous work. Why this problem is coming in system? Is any solution. Thanking you for reply.
It could be to do with the Nexus 7's lack of a back facing camera. This can cause problems as specified here
I can't think of anything else right now. Try adding a stack trace to your answer so we can see what went wrong.