-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when device is on low memory (was: "Camera") #8
Comments
What device and Android version are you using? How do you know it terminates (and not just hides)? Does a message gets displayed? Does this happen with other apps too? Also does this happen when taking a photo or when starting the camera app? |
Hi,
Android 7.1, moto 2015g
LineageOS nightly builds.
I retested it once again. And it is less deterministic than I was observing before.
Today, AAT went gone (gone from status, and new track staryed when I launched app)when tracking was paused. But repeated test did not confirm it.
I do not understand it, maybe there is some other factor I'm missing.
I've some experience with troubleshooting but nothing related to android.
I'll plan test and count nubers.
Maybe you have some tip how to create meaningful report.
On other hand if you think it is just my device, then close the case.
Regards
Jan
Dnia 21 maja 2017 16:07:14 CEST, bailuk <notifications@github.com> napisał(a):
…What device and Android version are you using? How do you know it
terminates (and not just hides)? Does a message gets displayed? Does
this happen with other apps too?
Also does this happen when taking a photo or when starting the camera
app?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#8 (comment)
-- Wysłane za pomocą K-9 Mail.
|
In my case track was not restored... Thus maybe it was something different. |
Thank you for your debugging effort. There was a bug that gets triggered when the device is on low memory. |
Thanks for fixing it. |
Hi,
I've problem that taking photo stops/terminates aat. Is this observed elsewhere? What kind of log/data could be helpfull to diagnose case?
Regards
Jan
The text was updated successfully, but these errors were encountered: